This is a new noble server that will take over mirror content
management from mirror-update02. Since all of the locking for AFS writes
is done on the host level we need to ensure that mirror-update02 is
sufficiently disabled (locks held and/or server shutdown) when we deploy
mirror-update03. It is probably also a good idea to have mirror-update02
in the emergency file so that automated changes don't undo any of the
lockout we've performed.
Then once we've confirmed that mirror-update03 is happily AFSing things
we can remove 02 from our inventory and delete it.
Depends-On: https://review.opendev.org/c/opendev/zone-opendev.org/+/953139
Change-Id: Ia4d80a68df51e33f8cc32f462e19f4663c604b91
4461ae7047