WIP: Noble migration instructions

[legoktm]

Status

Work in progress

Description of Changes

• Description: Documentation for the noble migration.

• Resolves #

• Related Issues

Testing

Release

Checklist (Optional)

• Doc linting (make docs-lint) passed locally
• Doc link linting (make docs-linkcheck) passed
• You have previewed (make docs) docs at http://localhost:8000

[legoktm]

Still WIP; needs some links and other stuff added. A few placeholders around dates need figuring out. Just wanted to post this so people can see the general direction.

[nathandyer]

Thanks @legoktm, this looks great! I think it covers all the questions I would have as an admin. The only thing missing that I'm seeing is a recommendation for folks to take a backup, just to be on the safe side. Is there any reason we wouldn't want to advise that beforehand?

[legoktm]

The only thing missing that I'm seeing is a recommendation for folks to take a backup, just to be on the safe side. Is there any reason we wouldn't want to advise that beforehand?

The upgrade script already takes a backup, except it leaves it on the app server. Transferring it to the Admin Workstation could be slow, especially if it's SSH-over-Tor. Of course, people who don't have local access probably benefit the most from having a backup on the AW.

It didn't really hit me until now, but in the manual case, we can just automatically start the backup for them as step 0. And then clean it up once we're done. The server will generate its own backup still, but that's not an issue.