~sircmpwn/sr.ht-docs

9c6dbc7f86f615bde1398bb66a565243df30ce52 — Drew DeVault 14 days ago 3e3e83d
Update hg.sr.ht migration plan
1 files changed, 7 insertions(+), 7 deletions(-)

M ops/hg.sr.ht-migration.md
M ops/hg.sr.ht-migration.md => ops/hg.sr.ht-migration.md +7 -7
@@ 1,13 1,13 @@
hg.sr.ht migration plan

1. Build & install the new server (sakuya1) as VM host gen 2
1. Announce planned outage a week in advance
1. Spin up an hg.sr.ht stack and restore from the last backup. This is a
   good opportunity to test our backups in action.
1. ~~Build & install the new server (sakuya1) as VM host gen 2~~
1. ~~Announce planned outage a week in advance~~
1. ~~Spin up an hg.sr.ht stack and restore from the last backup. This is a
   good opportunity to test our backups in action.~~
1. Test everything!
1. Set up pgbouncer on hg.sr.ht¹
1. Copy over host keys from hg.sr.ht¹ to hg.sr.ht²
1. Move root image back to ZFS on sakuya1
1. ~~Set up pgbouncer on hg.sr.ht¹~~
1. ~~Copy over host keys from hg.sr.ht¹ to hg.sr.ht²~~
1. ~~Move root image back to ZFS on sakuya1~~
1. Await planned outage date
1. Set hg.sr.ht¹ to read-only mode (via pgbouncer, probably, and disable
   the hg SSH login account)