The /dev/ram0 + XFS + format-ramdisk.service approach was unnecessary complexity from a migration confusion — there was no actual tmpfs bug with io_uring. tmpfs is simpler (no format-on-boot), resizable on the fly, and what every other Solana operator uses. Changes: - prepare-agave: remove format-ramdisk.service and ramdisk-accounts.service, use tmpfs fstab entry with size=1024G (was 600G /dev/ram0, too small) - recover: remove ramdisk_device var (no longer needed) - redeploy: wipe accounts by rm -rf instead of umount+mkfs - snapshot-download.py: extract download_best_snapshot() public API for use by the new container entrypoint.py (in agave-stack) - CLAUDE.md: update ramdisk docs, fix /srv/solana → /srv/kind/solana paths - health-check: fix ramdisk path references Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .pebbles | ||
| ashburn-relay-lab | ||
| docs | ||
| inventory | ||
| inventory-switches | ||
| playbooks | ||
| scripts | ||
| shred-relay-lab | ||
| .gitignore | ||
| CLAUDE.md | ||
| README.md | ||
| ansible.cfg | ||
README.md
biscayne-agave-runbook
Ansible playbooks for operating the kind-based agave-stack deployment on biscayne.vaasl.io.