ref: 14fde22c85fd0bf5d5c05a0ae319dada273266dc sr.ht-docs/ops/hg.sr.ht-migration.md -rw-r--r-- 1.0 KiB
14fde22c — Bitbake Tester Add hg.sr.ht migration plan 7 months ago

hg.sr.ht migration plan

  1. Build & install the new server (sakuya1) as VM host gen 2
  2. Announce planned outage a week in advance
  3. Spin up an hg.sr.ht stack and restore from the last backup. This is a good opportunity to test our backups in action.
  4. Test everything!
  5. Set up pgbouncer on hg.sr.ht¹
  6. Await planned outage date
  7. Set hg.sr.ht¹ to read-only mode (via pgbouncer, probably, and disable the hg SSH login account)
  8. rsync any changes which have occured between steps 3 and 6 to hg.sr.ht²
  9. Cut DNS over to hg.sr.ht² and monitor as users get transferred over
  10. Disable cronjobs on hg.sr.ht¹
  11. Monitor hg.sr.ht¹ and shut it off when traffic is more or less done hitting it
  12. Remove backup credentials for hg.sr.ht¹ from konapku.sr.ht
  13. Wait 2 weeks and then decommission hg.sr.ht¹

Things to double check on hg.sr.ht²:

  • Is monitoring working? Double check node exporter
  • Are backups working?
  • Are ZFS snapshots being taken correctly?
  • Are ZFS scrubs being run? Double check on the 1st