opendev/system-config
Code Issues Proposed changes

Add note about afs01's mirror-update vos releases to docs

Browse Source 
I tripped over this during recent afs fileserver reboots. Note it in the
docs so that we are aware of this in the future when doing maintenance.

Change-Id: Iac20fa6b9ec17f1eb69c50bc8f5736b34967fd83
This commit is contained in:
Clark Boylan 2021-06-17 09:53:08 -07:00
parent 5bef87f4a4
commit b400dfcb90
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/afs.rst
View File

@ -644,7 +644,9 @@ afs0X.openstack.org
Taking down the actual fileservers is slightly more complicated Taking down the actual fileservers is slightly more complicated
but works similarly. Basically what we need to do is make sure that but works similarly. Basically what we need to do is make sure that
either no one needs the RW volumes hosted by a fileserver before either no one needs the RW volumes hosted by a fileserver before
taking it down or move the RW volume to another fileserver. taking it down or move the RW volume to another fileserver. When
taking down afs01.dfw.openstack.org we must also ensure that the
vos releases that are performed on it by mirror-update are stopped.
To ensure nothing needs the RW volumes you can hold the various To ensure nothing needs the RW volumes you can hold the various
file locks on hosts that publish to AFS and/or remove cron entries file locks on hosts that publish to AFS and/or remove cron entries
@ -671,8 +673,11 @@ of the other servers::
root@afsdb01:~# vos move -id mirror -toserver afs01.ord.openstack.org -topartition vicepa -fromserver afs01.dfw.openstack.org -frompartition vicepa -localauth root@afsdb01:~# vos move -id mirror -toserver afs01.ord.openstack.org -topartition vicepa -fromserver afs01.dfw.openstack.org -frompartition vicepa -localauth
When that is done (use listvldb command above to check) it is now safe When that is done (use listvldb command above to check) it is now safe
to take down afs01.dfw.openstack.org while having writers to the mirror to take down afs0X.dfw.openstack.org while having writers to the mirror
volume. We use the same process as for the db server:: volume. If operating on afs01.dfw.openstack.org you should also hold
all mirror update locks and the release-volumes lock. This ensures
we do not interrupt any vos releases on afs01.dfw.openstack.org that are
run by mirror-update remotely. We use the same process as for the db server::
root@afsdb01:~# bos shutdown afs01.dfw.openstack.org -localauth root@afsdb01:~# bos shutdown afs01.dfw.openstack.org -localauth
root@afsdb01:~# bos status afs01.dfw.openstack.org -localauth root@afsdb01:~# bos status afs01.dfw.openstack.org -localauth