Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

MirrorManager: update the move-to-archive command

Browse source 
Signed-off-by: Aurélien Bompard <aurelien@bompard.org>
This commit is contained in:
Aurélien Bompard 2024-08-06 07:14:14 +02:00 • committed by kevin
parent 3afbe34974
commit 0606efe590
3 changed files with 19 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

14
modules/howtos/pages/archive-old-fedora.adoc
View file

@ -97,14 +97,22 @@ $ rsync -avSAXHP --delete 21/ /pub/archive/fedora-secondary/updates/testing/21/
. Announce to the mirror list this has been done and that in 2 weeks you
will move the old trees to archives.
. In two weeks, log into mm-backend01 and run the archive script
. In two weeks, run the following playbook from batcave:
+
[source]
----
$ sudo -i ssh root@mm-backend01.iad2.fedoraproject.org
$ sudo -u mirrormanager mm2_move-to-archive --originalCategory="Fedora Linux" --archiveCategory="Fedora Archive" --directoryRe='/21/Everything'
$ rbac-playbook -v /srv/web/infra/ansible/playbooks/manual/mirrormanager/move-to-archive.yml --extra-vars="product='Fedora' version='38'"
----
. This will start a job named `move-to-archive-fedora-38` on Openshift.
The playbook will output two commands to view the job's logs and to cancel it if needed.
You can run those commands on os-control01 or on any host logged in to OpenShift.
Alternatively, you can follow the job's execution on the Openshift WebUI and cancel it from there.
The playbook will wait for the job to complete.
. Note that the `Fedora Codecs` will not be archived, because we currently don't do that.
This category is explicitely excluded in the MirrorManager command itself.
. If there are problems, the postgres DB may have issues and so you need
to get a DBA to update the backend to fix items.

4
modules/release_guide/pages/release_eol.adoc
View file

@ -191,12 +191,12 @@ $ rsync -avAXSHP {old_release}/ /pub/archive/fedora-secondary/updates/testing/{o
____
. Announce to the mirror list this has been done and that in 2 weeks you will
move the old trees to archives.
. In two weeks, log into mm-backend01 and run the archive script
. In two weeks, run the following playbook from batcave:
+
____
[source,subs="attributes+"]
....
$ sudo -u mirrormanager mm2_move-to-archive --originalCategory="Fedora Linux" --archiveCategory="Fedora Archive" --directoryRe='/{old_release}/Everything'
$ rbac-playbook -v /srv/web/infra/ansible/playbooks/manual/mirrormanager/move-to-archive.yml --extra-vars="product='Fedora' version='{old_release}'"
....
____
. If there are problems, the postgres DB may have issues and so you need

4
modules/sysadmin_guide/pages/mirrormanager.adoc
View file

@ -74,11 +74,11 @@ contact the Mirror Wrangler.
Once the files of an EOL release have been copied to the archive
directory tree and enough mirrors have picked the files up at the
archive location there is also a script to adapt those paths in
archive location there is also a playbook to adapt those paths in
MirrorManager's database:
....
sudo -u mirrormanager mm2_move-to-archive --originalCategory='Fedora EPEL' --directoryRe='/4/'
$ rbac-playbook -v /srv/web/infra/ansible/playbooks/manual/mirrormanager/move-to-archive.yml --extra-vars="product='EPEL' version='7'"
....
== mirrorlist containers and mirrorlist servers