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

DC move: iad => rdu3, 10.3. => 10.16.

Browse source 
And remove some obsolete things.

Signed-off-by: Nils Philippsen <nils@redhat.com>
This commit is contained in:
Nils Philippsen 2025-07-04 11:55:02 +02:00
parent f3756ceb83
commit b4afb2f945
83 changed files with 386 additions and 429 deletions
Download patch file Download diff file Expand all files Collapse all files

2
modules/release_guide/pages/beta_RC_compose.adoc
View file

@ -97,7 +97,7 @@ $ screen
+
The first time any user account executes a compose the pungi-fedora git
repository must be cloned. The compose candidate script that invokes
pungi should be run from `compose-x86-01.iad2.fedoraproject.org`.
pungi should be run from `compose-x86-01.rdu3.fedoraproject.org`.
+
....
$ git clone ssh://git@pagure.io/pungi-fedora.git

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

@ -14,7 +14,7 @@ These are to be running on `bodhi-backend01` machine.
[source, bash]
----
$ ssh bodhi-backend01.iad2.fedoraproject.org
$ ssh bodhi-backend01.rdu3.fedoraproject.org
----
[source, bash]
@ -475,7 +475,7 @@ You may wish to do this in a tempoary directory to make cleaning it up easy.
=== Koji
Log into koji02.iad2.fedoraproject.org by way of bastion.fedoraproject.org.
Log into koji02.rdu3.fedoraproject.org by way of bastion.fedoraproject.org.
Verify that ``/etc/koji-gc/koji-gc.conf`` has the new key in it.

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

@ -86,7 +86,7 @@ should increment each time a new compose is created.
. Log into the compose backend
+
....
$ ssh compose-x86-01.iad2.fedoraproject.org
$ ssh compose-x86-01.rdu3.fedoraproject.org
....
. Open a screen session
+
@ -97,7 +97,7 @@ $ screen
+
The first time any user account executes a compose the pungi-fedora git
repository must be cloned. The compose candidate script that invokes
pungi should be run from `compose-x86-01.iad2.fedoraproject.org`.
pungi should be run from `compose-x86-01.rdu3.fedoraproject.org`.
+
....
$ git clone ssh://git@pagure.io/pungi-fedora.git

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

@ -169,7 +169,7 @@ The `mass-rebuild.py` script takes care of:
+
____
....
$ ssh compose-branched01.iad2.fedoraproject.org
$ ssh compose-branched01.rdu3.fedoraproject.org
....
____
. Start a terminal multiplexer (this ensures if user gets interrupted due to various reasons, the script can continue in a tmux session)
@ -203,7 +203,7 @@ publicly available URLs for stakeholders to monitor.
+
____
....
$ ssh compose-x86-02.iad2.fedoraproject.org / compose-branched01.iad2.fedoraproject.org:22
$ ssh compose-x86-02.rdu3.fedoraproject.org / compose-branched01.rdu3.fedoraproject.org:22
....
____
. Start a terminal multiplexer (this ensures if user gets interrupted due to various reasons, the script can continue in a tmux session)

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

@ -68,7 +68,7 @@ a sidetag will leave it in a weird state where it cannot be removed.
* Purge from disk the signed copies of rpms that are signed with the
EOL'd release key. To achieve this, add the release key to
*koji_cleanup_signed.py* script in https://pagure.io/releng[releng] repo
and run the script on compose-branched01.iad2.fedoraproject.org:
and run the script on compose-branched01.rdu3.fedoraproject.org:
....
tmux
@ -178,7 +178,7 @@ Otherwise, alert the quality team to do so.
+
____
....
ssh bodhi-backend01.iad2.fedoraproject.org
ssh bodhi-backend01.rdu3.fedoraproject.org
sudo su
su - ftpsync
....

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

@ -53,7 +53,7 @@ Remove release candidates and unnecessary composes that are no longer needed to
[discrete]
=== Steps
. SSH into `bodhi-backend01.iad2.fedoraproject.org` or any server where Koji is mounted.
. SSH into `bodhi-backend01.rdu3.fedoraproject.org` or any server where Koji is mounted.
. Perform the following:
** Remove all directories related to Beta and Final RCs in `/pub/alt/stage/`.
** Clean up old composes by removing all but the latest in `/mnt/koji/compose/branched/` and `/mnt/koji/compose/{branched}/`.

8
modules/release_guide/pages/sop_mass_branching.adoc
View file

@ -81,8 +81,8 @@ The recommended method to achieve this is by adding firewall rules to both koji0
[source,bash,subs="attributes"]
----
iptables -I INPUT -m tcp -p tcp --dport 80 -s proxy01.iad2.fedoraproject.org -j REJECT
iptables -I INPUT -m tcp -p tcp --dport 80 -s proxy10.iad2.fedoraproject.org -j REJECT
iptables -I INPUT -m tcp -p tcp --dport 80 -s proxy01.rdu3.fedoraproject.org -j REJECT
iptables -I INPUT -m tcp -p tcp --dport 80 -s proxy10.rdu3.fedoraproject.org -j REJECT
----
These commands reject incoming traffic on port 80 from the specified proxies, preventing external submissions. Internal connections routed via proxy101 and proxy110 will continue to function as expected.
@ -91,8 +91,8 @@ To reverse the firewall changes and allow external submissions again, use:
[source,bash,subs="attributes"]
----
iptables -D INPUT -m tcp -p tcp --dport 80 -s proxy01.iad2.fedoraproject.org -j REJECT
iptables -D INPUT -m tcp -p tcp --dport 80 -s proxy10.iad2.fedoraproject.org -j REJECT
iptables -D INPUT -m tcp -p tcp --dport 80 -s proxy01.rdu3.fedoraproject.org -j REJECT
iptables -D INPUT -m tcp -p tcp --dport 80 -s proxy10.rdu3.fedoraproject.org -j REJECT
----