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

MirrorManager: update the move-devel-to-release command

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

7
modules/release_guide/pages/final_release.adoc
View file

@ -141,12 +141,11 @@ In the first week after the release MirrorManager still uses the files
at `fedora/linux/development/<version>` and not at at `fedora/linux/development/<version>` and not at
`fedora/linux/releases/<version>` `fedora/linux/releases/<version>`
Once enough mirrors have picked up the files in the release directory Once enough mirrors have picked up the files in the release directory,
following script (on _mm-backend01_) can be used to change the paths in run the following playbook from batcave to change the paths in
MirrorManager: MirrorManager:
[source,subs="attributes+"] [source,subs="attributes+"]
.... ....
sudo -u mirrormanager mm2_move-devel-to-release --version={branched} --category="Fedora Linux" $ rbac-playbook -v /srv/web/infra/ansible/playbooks/manual/mirrormanager/move-devel-to-release.yml --extra-vars="version='42'"
sudo -u mirrormanager mm2_move-devel-to-release --version={branched} --category="Fedora Secondary Arches"
.... ....

6
modules/release_guide/pages/release_post_cleanup.adoc
View file

@ -35,13 +35,11 @@ After the release, update MirrorManager to redirect requests from the developmen
[discrete] [discrete]
=== Steps === Steps
. SSH into `mm-backend01.iad2.fedoraproject.org`. . Run the following playbook on batcave to update the paths in MirrorManager:
. Run the following commands to update the paths in MirrorManager:
+ +
[source,subs="attributes+"] [source,subs="attributes+"]
.... ....
sudo -u mirrormanager mm2_move-devel-to-release --version={branched} --category="Fedora Linux" $ rbac-playbook -v /srv/web/infra/ansible/playbooks/manual/mirrormanager/move-devel-to-release.yml --extra-vars="version='{branched}'"
sudo -u mirrormanager mm2_move-devel-to-release --version={branched} --category="Fedora Secondary Arches"
.... ....
== Cleanup of RCs and Unnecessary Composes == Cleanup of RCs and Unnecessary Composes

4
modules/sysadmin_guide/pages/fedora-releases.adoc
View file

@ -360,5 +360,5 @@ After release:
* post to infrastructure list that freeze is over. * post to infrastructure list that freeze is over.
* Move MirrorManager repository tags from the `development/$version/` * Move MirrorManager repository tags from the `development/$version/`
Directory objects, to the `releases/$version/` Directory objects. This is Directory objects, to the `releases/$version/` Directory objects. This is
done using the `move-devel-to-release --version=$version` command on done using the `playbooks/manual/mirrormanager/move-devel-to-release.yml`
_bapp02_. This is usually done now a week or two after release. playbook. This is usually done now a week or two after release.