infra/docs
19
1
Fork 26
Code Issues 57 Pull requests 7 Projects Releases Packages Wiki Activity Actions

Update pagure links where replacements are available

Browse source
This commit is contained in:
Ruilai Ma 2026-03-19 22:33:23 +01:00 • committed by Michal Konečný
commit 24c8196ddd
64 changed files with 134 additions and 138 deletions
Download patch file Download diff file Expand all files Collapse all files

2
modules/ROOT/pages/apprentice.adoc
View file

@ -64,7 +64,7 @@ there and close it or rework it as needed. You can add to the next meeting agend
* Make patch for fix from git ansible repo
Most any task will require changes to ansible. You can check this out on batcave01.rdu3.fedoraproject.org
(just "git clone /git/ansible" there) and make edits to your local copy. Then you can create a PR with your changes into link:https://pagure.io/fedora-infra/ansible[]
(just "git clone /git/ansible" there) and make edits to your local copy. Then you can create a PR with your changes into link:https://forge.fedoraproject.org/infra/ansible[]
== Matrix Tips

2
modules/ROOT/pages/communishift.adoc
View file

@ -22,7 +22,7 @@ With the namespace provided you will get following default resources:
[NOTE]
====
Default resources were taken from communishift
link:https://pagure.io/fedora-infra/ansible/blob/main/f/roles/communishift/tasks/create-resource-quota.yml[ansible playbook].
link:https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/communishift/tasks/create-resource-quota.yml[ansible playbook].
====
== Accessing and using OpenShift

2
modules/ROOT/pages/gettingstarted.adoc
View file

@ -67,7 +67,7 @@ The message body should include:
**** Systems administration skills, certifications, and technologies you have or have used (or wish to learn)
**** Any associations you have (e.g. local hackerspace/makerspace, Linux User Groups, employer, etc.)
** What you want to learn
*** What you would like to work on and quite possibly which link:http://pagure.io/fedora-infrastructure/issues[outstanding issues] you would like to help resolve
*** What you would like to work on and quite possibly which link:https://forge.fedoraproject.org/infra/tickets/issues[outstanding issues] you would like to help resolve
** Any initial questions you have for the team
*** Look at the link:https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/[Fedora Infrastructure Best Practices] document
*** Be patient, as sometimes folks are busy and might not reply to your email quickly. You may get a faster response on Matrix.

2
modules/ROOT/pages/map_critical_services.adoc
View file

@ -46,7 +46,7 @@ when any error happens.
|===
|Name |Description |Why it's critical? |Hostname
|https://pagure.io/fedora-infra/toddlers[toddlers]
|https://forge.fedoraproject.org/apps/toddlers[toddlers]
|Toddlers are a collection of fedora messaging consumers that are listening for various fedora messages
and trigger tasks based on those messages.
|Some of the tasks executed by toddlers are essential for whole Fedora Community.

2
modules/ROOT/pages/overview.adoc
View file

@ -9,7 +9,7 @@
Most of the tooling we use in Fedora infrastructure is described in
xref:developer_guide:index.adoc[Developer Guide]. Above that we also use Ansible
to maintain our https://pagure.io/fedora-infra/ansible[ansible repository].
to maintain our https://forge.fedoraproject.org/infra/ansible[ansible repository].
== Good Practices

2
modules/developer_guide/pages/ci.adoc
View file

@ -4,7 +4,7 @@ CI is an important part of development and it helps to keep the project maintain
Fedora infra is using https://fedora.softwarefactory-project.io/zuul/status[Fedora CI].
This CI is hosted by Fedora and open to any Fedora project.
Fedora Infra also maintains their own https://pagure.io/fedora-infra/zuul[zuul jobs repository].
Fedora Infra also maintains their own https://forge.fedoraproject.org/infra/zuul[zuul jobs repository].
This repository is open to contributions and every project in Fedora can use these jobs.
== Setting up CI for new project

2
modules/developer_guide/pages/dev-environment.adoc
View file

@ -27,7 +27,7 @@ You can install https://vagrantup.com/[Vagrant] on a Fedora host with:
$ sudo dnf install libvirt vagrant vagrant-libvirt vagrant-sshfs
....
You can combine your https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks[Ansible playbook]
You can combine your https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks[Ansible playbook]
with https://vagrantup.com/[Vagrant]
very easily. Simply point Vagrant to your Ansible playbook and it will
run it. Users who would prefer to provision their virtual machines in

2
modules/developer_guide/pages/getting-started.adoc
View file

@ -40,4 +40,4 @@ particular setup.
Fedora Infrastructure applications are either on Github in the
https://github.com/fedora-infra[fedora-infra] organization, or on
https://pagure.io/[Pagure].
https://forge.fedoraproject.org/[Fedora Forge].

4
modules/developer_guide/pages/openshift.adoc
View file

@ -54,9 +54,9 @@ $ oc logs librariesio2fedmsg-28-bfj52
=== Deploying Your Application
Applications are deployed to OpenShift using
https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps[Ansible
https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/openshift-apps[Ansible
playbooks]. You will need to create an
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps[Ansible
https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps[Ansible
Role] for your application. A role is made up of several YAML files that
define OpenShift objects.
To create these YAML objects you have two options:

2
modules/howtos/pages/restart_datacenter_server.adoc
View file

@ -2,7 +2,7 @@
This guide is for restarting machines in RDU3 datacenter using `ipmitool`.
This only applies to bare hardware instances
(see link:https://pagure.io/fedora-infra/ansible/blob/main/f/inventory/hardware[ansible inventory]).
(see link:https://forge.fedoraproject.org/infra/ansible/src/branch/main/inventory/hardware[ansible inventory]).
[NOTE]
====

10
modules/release_guide/pages/index.adoc
View file

@ -8,7 +8,7 @@ team.
* matrix: link:https://matrix.to/#/#releng:fedoraproject.org[Matrix Fedora releng channel]
* Mailing List: https://admin.fedoraproject.org/mailman/listinfo/rel-eng[rel-eng@lists.fedoraproject.org]
* Issue tracker: https://forge.fedoraproject.org/releng/tickets[Fedora Releng Pagure Tickets]
* Issue tracker: https://forge.fedoraproject.org/releng/tickets[Fedora Releng Tickets]
If you want the to get something done (e.g. moving packages to
buildroots or into frozen compositions) by the ReleaseEngineering Team,
@ -71,7 +71,7 @@ Fedora people new to rel-eng will usually get access a little bit at a
time. Typically people won't immediately be granted the ability to sign
packages and push updates for example. A couple of tasks you could start
out with are troubleshooting why builds are failing (and if rel-eng
could take actions to fix it) as the requests are submitted to pagure or
could take actions to fix it) as the requests are submitted to Forge or
help with scripts for various rel-eng tasks.
There are also a number of tools that Fedora Release Engineering uses
@ -95,8 +95,8 @@ For requests, please consult the <<releng-contact-info>>
Rel-eng holds regular meetings every Tuesday at 16:00 UTC in
link:https://matrix.to/#/#meeting-3:fedoraproject.org[Fedora Meeting 3 channel on matrix].
link:https://pagure.io/releng/issues?status=Open&tags=meeting[Meeting
agendas] are created from open tickets in pagure that contain the
link:hhttps://forge.fedoraproject.org/releng/tickets/issues?q=&type=all&sort=relevance&labels=979&state=open&milestone=0&project=0&assignee=0&poster=0[Meeting
agendas] are created from open tickets in Fedora Forge that contain the
meeting keyword.
=== Meeting Minutes
@ -110,7 +110,7 @@ Meeting Minutes for 2007-04-16 to 2009-05-04].
== Current activities
See our https://pagure.io/releng/issues[ticket queue] for the things we
See our https://forge.fedoraproject.org/releng/tickets/issues[ticket queue] for the things we
are currently working.
See https://fedoraproject.org/wiki/Releases[Releases] for information

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

@ -114,7 +114,7 @@ $ cd pungi-fedora
....
+
If the clone step above was not required then fully update the existing
repository checkout from pagure.
repository checkout from Forge.
+
[source,subs="attributes+"]
....

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

@ -42,8 +42,8 @@ bodhi
=== Update Ansible vars
Set the infra ansible https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/FedoraBranchedBodhi.yaml[_FedoraBranchedBodhi_ variable] to `prebeta`
and the https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/Frozen.yaml[_NextReleaseFrozen_ variable] to `True`.
Set the infra ansible https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/FedoraBranchedBodhi.yaml[_FedoraBranchedBodhi_ variable] to `prebeta`
and the https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml[_NextReleaseFrozen_ variable] to `True`.
=== Run the playbooks

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

@ -65,8 +65,8 @@ $ bodhi releases edit --name F{branched} --state pending
== Update Ansible vars
Set the infra ansible https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/FedoraBranchedBodhi.yaml[_FedoraBranchedBodhi_ variable] to `postbeta`
and the https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/Frozen.yaml[_NextReleaseFrozen_ variable] to `False`.
Set the infra ansible https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/FedoraBranchedBodhi.yaml[_FedoraBranchedBodhi_ variable] to `postbeta`
and the https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml[_NextReleaseFrozen_ variable] to `False`.
== Run the playbooks

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

@ -23,7 +23,7 @@ as a reference.
Most of the branching process is controlled by ansible playbooks.
Before these are run some changes will be needed in the
https://pagure.io/fedora-infra/ansible[ansible repo].
https://forge.fedoraproject.org/infra/ansible/[ansible repo].
Set these up ahead of time in a pull request,
which will be merged on branching day.
These changes include:
@ -34,7 +34,7 @@ These changes include:
* disable syncing of the centos-{epel_major}-snapshot directory
You can use
https://pagure.io/fedora-infra/ansible/pull-request/2813#request_diff[this pull request]
https://forge.fedoraproject.org/infra/ansible/pulls/2813/files[this pull request]
as a reference.
== Branching day

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

@ -2,7 +2,7 @@ include::_partials/attributes.adoc[]
= Final Release candidate
When Quality Engineering (QE) requests a Release Candidate (RC) they do
so by opening an issue in the releng repository on pagure. Release
so by opening an issue in the releng repository on Forge. Release
candidate composes are not currently automated.
[cols=",,",options="header",]
@ -109,7 +109,7 @@ $ cd pungi-fedora
....
+
If the clone step above was not required then fully update the existing
repository checkout from pagure.
repository checkout from Forge.
+
[source,subs="attributes+"]
....

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

@ -5,7 +5,7 @@ include::_partials/attributes.adoc[]
== Make sure all retired packages are blocked in koji
Before the freeze we have to make sure all retired packages have been blocked in koji.
To do this, [run the script](https://pagure.io/releng/blob/main/f/scripts_new/packages/distgit/get_retired_packages.sh) that collects all the retired packages
To do this, [run the script](https://forge.fedoraproject.org/releng/tooling/src/branch/main/packages/distgit/get_retired_packages.sh) that collects all the retired packages
and outputs them into json files in the [lookaside cache](https://src.fedoraproject.org/lookaside).
....
@ -35,7 +35,7 @@ $ sudo -u apache bodhi-push --releases --stable 'f{branched}'
== Update Ansible vars
Set the https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/Frozen.yaml[_NextReleaseFrozen_ variable] to `True`.
Set the https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml[_NextReleaseFrozen_ variable] to `True`.
=== Run the playbook
@ -55,8 +55,6 @@ $ bodhi releases edit --name F{branched} --state frozen
Send an email as mentioned below to `devel@`, `devel-announce@`, `test-announce@`, `announce@` lists as information that the final freeze is now active.
For the reference, you can refer generic https://pagure.io/releng/blob/main/f/mail-templates/06-final-freeze.txt[template] for final freeze from release engineering repo.
[source,subs="attributes+"]
....
Hi all,

12
modules/release_guide/pages/sop_final_release.adoc
View file

@ -72,13 +72,13 @@ for the new release rather than being stuck on the GA compose forever.
=== Update releng roles updates
. Set https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/00-FedoraCycleNumber.yaml[FedoraCycleNumber] to {branched}.
. Set https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/00-FedoraCycleNumber.yaml[FedoraCycleNumber] to {branched}.
. Set https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/FedoraPreviousPrevious.yaml[FedoraPreviousPrevious] to True.
. Set https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/FedoraPreviousPrevious.yaml[FedoraPreviousPrevious] to True.
. Set https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/FedoraBranched.yaml[FedoraBranched] to False.
. Set https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/FedoraBranched.yaml[FedoraBranched] to False.
. Set https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/Frozen.yaml[NextReleaseFrozen] to False.
. Set https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml[NextReleaseFrozen] to False.
Now run the relevant playbooks:
@ -94,7 +94,7 @@ $ sudo rbac-playbook groups/openqa.yml -t testcase_stats
If you do not have permissions to run a playbook, ask a sysadmin-main member for help.
A sysadmin-qa member can run the openQA playbook.
For reference, see the https://pagure.io/fedora-infra/ansible/c/7e501dcb9432885c9ef10e78c0418b0d40c85061[Fedora 41 release PR],
For reference, see the https://forge.fedoraproject.org/infra/ansible/commit/7e501dcb9432885c9ef10e78c0418b0d40c85061[Fedora 41 release PR],
though note it is somewhat old and includes some things that are no longer needed, and leaves out some that should be done.
== Stage Final Release for Mirrors
@ -124,7 +124,7 @@ an email to [.title-ref]#mirror-admin@lists.fedoraproject.org# list.
== Make sure there are no tagging leftovers from bodhi
Sometimes builds are not properly tagged during the freeze process.
Make sure all builds are properly tagged, for more info about the [issue](https://pagure.io/releng/issue/11775)
Make sure all builds are properly tagged, for more info about the [issue](https://forge.fedoraproject.org/releng/tickets/issues/11775)
== Verification

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

@ -138,12 +138,12 @@ As part of the mass branching process, changes were made to the `find_unblocked_
=== Ansible
Apps in https://pagure.io/fedora-infra/ansible[ansible] need to be updated to be aware of a new branch.
Apps in https://forge.fedoraproject.org/infra/ansible/[ansible] need to be updated to be aware of a new branch.
==== Bodhi
Bodhi needs to be updated to add new release. This needs to be done in
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/bodhi2[bodhi2 role] in
https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/bodhi2[bodhi2 role] in
infra ansible repo. This change includes, updating `koji-sync-listener.py`,
`new-updates-sync`, pungi configs for rpm updates, bodhi templates.
@ -152,28 +152,28 @@ infra ansible repo. This change includes, updating `koji-sync-listener.py`,
* `roles/bodhi2/backend/templates/pungi.rpm.conf.j2`
* `roles/bodhi2/backend/templates/koji_sync_listener.toml`
Please check these files from the https://pagure.io/fedora-infra/ansible/c/549e5d3ace41c04fdbef9d81f359f16c2fe0c2fa?branch=main[commit] for your reference.
Please check these files from the https://forge.fedoraproject.org/infra/ansible/commit/549e5d3ace41c04fdbef9d81f359f16c2fe0c2fa[commit] for your reference.
==== Poddlers (formerly known as toddlers)
==== Add new SLA to the poddlers App
Use https://pagure.io/fedora-infra/ansible/pull-request/2449[this PR] for reference and add new version to the config.
Use https://forge.fedoraproject.org/infra/ansible/pulls/2449[this PR] for reference and add new version to the config.
==== Fedora Branched
. Set https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/FedoraBranched.yaml[FedoraBranched] to True.
. Set https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/FedoraBranchedBodhi.yaml[FedoraBranchedBodhi] to preenable.
. Set https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/FedoraBranched.yaml[FedoraBranched] to True.
. Set https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/FedoraBranchedBodhi.yaml[FedoraBranchedBodhi] to preenable.
Please check the file `FedoraBranched.yaml` and `FedoraBranchedBodhi.yaml` from the https://pagure.io/fedora-infra/ansible/c/549e5d3ace41c04fdbef9d81f359f16c2fe0c2fa?branch=main[commit] for your reference.
Please check the file `FedoraBranched.yaml` and `FedoraBranchedBodhi.yaml` from the https://forge.fedoraproject.org/infra/ansible/commit/549e5d3ace41c04fdbef9d81f359f16c2fe0c2fa[commit] for your reference.
==== Koji hub
Update the koji hub config to allow side tags for new koji rawhide (currently f{rawhide}) tag.
Please check the file `roles/koji_hub/templates/hub.conf.j2` from the https://pagure.io/fedora-infra/ansible/c/549e5d3ace41c04fdbef9d81f359f16c2fe0c2fa?branch=main[commit] for your reference.
Please check the file `roles/koji_hub/templates/hub.conf.j2` from the https://forge.fedoraproject.org/infra/ansible/commit/549e5d3ace41c04fdbef9d81f359f16c2fe0c2fa[commit] for your reference.
Also, update the `roles/koji_hub/templates/koji-gc.conf.j2` file to list the new release
keys and retention.
@ -181,13 +181,13 @@ keys and retention.
==== Robosignatory
Robosignatory has two parts, which can be found in
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/robosignatory[robosignatory
https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/robosignatory[robosignatory
role] in infra ansible repo.:
. Disable branched signing, so that we can freeze branched until we get a compose.
. Adding new release.
Please check the file `roles/robosignatory/templates/robosignatory.toml.j2` from the https://pagure.io/fedora-infra/ansible/c/a7dcdbd794e728f7b80b1afc6c142c0196b8c1a3?branch=main[commit] for your reference.
Please check the file `roles/robosignatory/templates/robosignatory.toml.j2` from the https://forge.fedoraproject.org/infra/ansible/commit/a7dcdbd794e728f7b80b1afc6c142c0196b8c1a3[commit] for your reference.
Ask someone in fedora infra to run the robosignatory playbook.
@ -497,8 +497,8 @@ Before running the script, you need to **obtain the script from the Fedora RelEn
**Option 1: Clone the RelEng repository**
```bash
$ git clone https://pagure.io/releng.git
$ cd releng/release-process/mass-branching/fedora/
$ git clone https://forge.fedoraproject.org/releng/tooling.git
$ cd tooling/release-process/mass-branching/fedora/
$ chmod +x get_active_packages.sh
```
@ -547,8 +547,8 @@ The koji build system needs to have some tag/target work done to handle
builds from the new branch and to update where builds from rawhide go.
Run the
https://pagure.io/releng/blob/main/f/scripts_new/release-process/mass-branching/fedora/create_koji_release_tags.sh[create_koji_release_tags.sh]
script in the https://pagure.io/releng[Pagure release engineering repository].
https://forge.fedoraproject.org/releng/tooling/src/branch/main/release-process/mass-branching/fedora/create_koji_release_tags.sh[create_koji_release_tags.sh]
script in the https://https://forge.fedoraproject.org/releng/tooling/[Forge release engineering repository].
[NOTE]
@ -593,8 +593,8 @@ $ bodhi releases edit --name F{branched}F --eol YYYY-MM-DD
==== Creating Empty Repos
To create empty repos on the master mirror, run
https://pagure.io/releng/blob/main/f/scripts_new/release-process/mass-branching/fedora/create_empty_repositories.sh[create_empty_repositories.sh]
from the https://pagure.io/releng[Pagure release engineering repository]. This should be run on
https://forge.fedoraproject.org/releng/tooling/src/branch/main/release-process/mass-branching/fedora/create_empty_repositories.sh[create_empty_repositories.sh]
from the https://forge.fedoraproject.org/releng/tooling/src/branch/main/release-process/mass-branching/fedora/create_koji_release_tags.sh[Forge release engineering repository]. This should be run on
*bodhi-backend01.phx2.fedoraproject.org*
[source,bash,subs="attributes"]
@ -604,7 +604,7 @@ $ sudo -u ftpsync sh scripts_new/release-process/mass-branching/fedora/create_em
[NOTE]
====
Update the link in /mnt/koji/repos/rawhide/latest as per https://pagure.io/releng/issue/12255.
Update the link in /mnt/koji/repos/rawhide/latest as per https://forge.fedoraproject.org/releng/tickets/issues/12255.
====
[NOTE]
@ -718,7 +718,7 @@ We need to update the mirrormanager so that it will point rawhide to the
new rawhide release.
Please follow the instructions in the
https://pagure.io/fedora-infrastructure/issue/9239#comment-671446[fedora
https://forge.fedoraproject.org/infra/tickets/issues/9239[fedora
infra ticket] to update the database of mirrormanager, though note that
none of the 'modular' repos exist any more.
@ -787,7 +787,7 @@ Once, this is done, update the fullfiletimelist as well, this sometime take time
==== ELN related work
Add the new rawhide key to eln pungi config. For example, look at this
https://pagure.io/pungi-fedora/c/e993441164ee83374df7f463777f2bf1d456fd6d?branch=eln[pungi
https://forge.fedoraproject.org/releng/pungi-fedora/commit/e993441164ee83374df7f463777f2bf1d456fd6d[pungi
eln config commit]
Change the trigger notification for DistroBuildSync to the new Rawhide

2
modules/release_guide/pages/sop_post-release_cleanup.adoc
View file

@ -71,7 +71,7 @@ Address and close any open issues related to failed composes to maintain the hea
[discrete]
=== Steps
. Use the script available in the Fedora RelEng repository: https://pagure.io/releng/blob/main/f/scripts_new/release-process/post-release/failed_composes_cleanup.py
. Use the script available in the Fedora RelEng repository: https://forge.fedoraproject.org/releng/tooling/src/branch/main/release-process/post-release/failed_composes_cleanup.py
+
[source,subs="attributes+"]
....

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

@ -177,8 +177,6 @@ Syntax: `sudo rbac-playbook groups/bodhi-backend.yml`
=== Final Announcement
Send the final announcement to `devel-announce@`, `test@`, `test-announce@`, and `announce@` lists.
Use the https://pagure.io/releng/blob/main/f/mail-templates/08-end-of-life.txt[template] from release engineering repo.
NOTE: The above template is the same as the reminder announcement. We should revise it and create a separate one.
=== Other Tasks

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

@ -28,7 +28,7 @@ process. It should be run on a machine that has `koji` and
complete.
`find_unblocked_orphans.py` is available in the
https://pagure.io/releng[Release Engineering git repository] under `scripts_new/packages/orphaned/orphaned-packages-process/` directory.
https://forge.fedoraproject.org/releng/tooling/src/branch/main/packages/orphaned/find_unblocked_orphans.py[Release Engineering git repository].
=== Announcing Packages to be retired

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

@ -91,7 +91,7 @@ executable
+
....
cd ~
wget https://pagure.io/releng/raw/main/f/scripts_new/release-process/torrents/fedora_torrent_ini.py
wget https://forge.fedoraproject.org/releng/tooling/raw/branch/main/release-process/torrents/fedora_torrent_ini.py
chmod 755 ~/fedora_torrent_ini.py
....
. Run the following command from `/srv/torrent/new/fedora/`

2
modules/releng_misc_guide/pages/sop_eol_change.adoc
View file

@ -29,7 +29,7 @@ maintainers], may request that this branch have its EOL extended until
2018-12-01.
When a maintainer wants to change EOL on a rpm, module, or container
branch, they need to file a https://pagure.io/releng/issues[releng
branch, they need to file a https://forge.fedoraproject.org/releng/tickets/issues[releng
ticket] requesting it. They have no way to do it on their own. Releng
must review the request, and then process it.

2
modules/releng_misc_guide/pages/sop_package_unblocking.adoc
View file

@ -11,7 +11,7 @@ engineering needs to "unblock" the package from koji tags.
=== Find Unblock requests
Unblock requests are usually reported in the
https://pagure.io/releng/issues[rel-eng issue tracker].
https://forge.fedoraproject.org/releng/tickets/issues[rel-eng issue tracker].
=== Perform the unblocking

4
modules/releng_misc_guide/pages/sop_remote_dist_git_branches.adoc
View file

@ -16,7 +16,7 @@ So here are the steps to follow to remove the branch `<branch>` from the package
. Clone the releng repo if you do not already have it:
+
----
git clone https://pagure.io/releng.git
git clone https://forge.fedoraproject.org/releng/tooling.git
----
. Pull the latest changes:
@ -40,7 +40,7 @@ cd clone && git checkout <branch>
. Run the script:
+
----
python ../releng/scripts_new/packages/distgit/distgit_branch_unused.py <branch>
python ../tooling/packages/distgit/distgit_branch_unused.py <branch>
----
+
(If needed, see the ``--help`` of the script for more information)

2
modules/releng_misc_guide/pages/sop_unretire.adoc
View file

@ -80,7 +80,7 @@ $ GIT_SSH=/usr/local/bin/relengpush fedpkg --user releng push
Commit message example:
`*Unretirement request: pagure.io/releng/issue/12345*`
`*Unretirement request: https://forge.fedoraproject.org/releng/tickets/issues/12345*`
==== Special Case: Branches That Have An Identical Commit History

2
modules/releng_misc_guide/pages/sop_update_critpath.adoc
View file

@ -20,7 +20,7 @@ steps to update it manually are documented here in case of need.
== Action
. The release engineering script for updating critpath lives in the
https://pagure.io/releng[releng git repository] under `scripts_new/quality-assurance/critpath/` path. Check this out.
https://forge.fedoraproject.org/releng/tooling/[releng tooling git repository] under `quality-assurance/critpath/` path. Check this out.
. Run the script. If run with `all`, it will generate the info for
all current releases, and name the output files as Bodhi expects.
Otherwise you can specify the release to generate info for, and the

10
modules/sysadmin_guide/pages/ansible.adoc
View file

@ -38,16 +38,16 @@ image:ansible-repositories.png[image]
This repository exists as several copies or replicas:
** The "upstream" repository on Pagure.
** The "upstream" repository on Forge.
https://pagure.io/fedora-infra/ansible
https://forge.fedoraproject.org/infra/ansible
This repository is the public facing place where people can contribute
(e.g. pull requests) as well as the authoritative source. Members of the
`sysadmin` FAS group or the `fedora-infra` Pagure group have commit
`sysadmin` FAS group have commit
access to this repository.
To contribute changes, fork the repository on Pagure and submit a Pull
To contribute changes, fork the repository on Forge and submit a Pull
Request. Someone from the aforementioned groups can then review and
merge them.
@ -114,7 +114,7 @@ unavailable.
====
+
You can access it also via a cgit web interface at:
https://pagure.io/fedora-infra/ansible/
https://forge.fedoraproject.org/infra/ansible
* `/srv/git/ansible-private` on _batcave01_.

2
modules/sysadmin_guide/pages/aws-access.adoc
View file

@ -80,7 +80,7 @@ misused.
=== Adding an IAM role mapping in Ipsilon
Clone the git repo available here: https://pagure.io/fedora-infra/ipsilon-fedora
Clone the git repo available here: https://forge.fedoraproject.org/infra/ipsilon-fedora
Edit the file ipsilon/info/infofas.py add the new role mapping following
the examples below

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

@ -1,6 +1,6 @@
= Blockerbugs Infrastructure SOP
https://pagure.io/fedora-qa/blockerbugs[Blockerbugs] is an app developed
https://forge.fedoraproject.org/quality/blockerbugs[Blockerbugs] is an app developed
by Fedora QA to aid in tracking items related to release blocking and
freeze exception bugs in branched Fedora releases.
@ -24,7 +24,7 @@ Persons::
Servers::
* In OpenShift.
Purpose::
Hosting the https://pagure.io/fedora-qa/blockerbugs[blocker bug
Hosting the https://forge.fedoraproject.org/quality/blockerbugs[blocker bug
tracking application] for QA
== File Locations

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

@ -22,8 +22,8 @@ bugzilla2fedmsg is a small service running as a container in Openshift in the `b
== Resources
- [1] Ansible Playbook: https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/bugzilla2fedmsg.yml
- [2] Ansible Role: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/bugzilla2fedmsg
- [1] Ansible Playbook: https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/openshift-apps/bugzilla2fedmsg.yml
- [2] Ansible Role: https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps/bugzilla2fedmsg
- [3] Code: https://github.com/fedora-infra/bugzilla2fedmsg
== Useful Commands

2
modules/sysadmin_guide/pages/coreos-cincinnati.adoc
View file

@ -15,7 +15,7 @@ Contact::
Source::
https://github.com/coreos/fedora-coreos-cincinnati
Playbook::
https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/coreos-cincinnati.yml
https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/openshift-apps/coreos-cincinnati.yml
Location::
OpenShift cluster (production): https://console-openshift-console.apps.ocp.fedoraproject.org/
Project::

2
modules/sysadmin_guide/pages/dnf-counting.adoc
View file

@ -17,7 +17,7 @@ Purpose::
installations.
Repositories::
* https://github.com/fedora-infra/mirrors-countme
* https://pagure.io/fedora-infra/ansible/blob/main/f/roles/web-data-analysis
* https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/web-data-analysis
== What it is

2
modules/sysadmin_guide/pages/dns.adoc
View file

@ -174,7 +174,7 @@ DNS config files are ansible managed
From your local machine run:
....
git clone ssh://git@pagure.io/fedora-infra/ansible.git
git clone https://forge.fedoraproject.org/infra/ansible.git
cd ansible/roles/dns/files/
...make changes needed...
git commit -m "What you did"

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

@ -44,7 +44,7 @@ The schedule will list the date the infrastructure freezes should be
imposed (three weeks before the early target release date, for Beta;
three weeks before, for Final). On this date, some hours after the
release freeze goes into effect, set the InfraFrozen variable in
https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/Frozen.yaml[Frozen.yaml]
https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml[Frozen.yaml]
to True. Then send out an email to the infrastructure list. The subject
should be "Fedora <NN> <Beta/Final> Freeze now in effect!"
(insert release number and delete milestone as appropriate). The body
@ -62,7 +62,7 @@ release Fedora <NN> <Beta> when it's available.
You can always check if an infrastructure freeze is in place by
checking the value of the InfraFrozen variable at:
https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/Frozen.yaml
https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
@ -100,7 +100,7 @@ outstanding tasks related to the release that should be addressed
before the freeze ends.
Set the InfraFrozen variable in
https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/Frozen.yaml[Frozen.yaml]
https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml[Frozen.yaml]
to False. Then send out an email to the infrastructure list. The
subject should be "Fedora <NN> <Beta/Final> Freeze now over!"
(insert release number and delete milestone as appropriate). The body
@ -113,7 +113,7 @@ over.
You can always check if an infrastructure freeze is in place by
checking the value of the InfraFrozen variable at:
https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/Frozen.yaml
https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml
Our next freeze is for Fedora <release> <Beta>, currently scheduled for
<YYYY-MM-DD>.
@ -150,7 +150,7 @@ needed.
You can get a list of frozen/non-frozen hosts by:
....
git clone https://pagure.io/fedora-infra/ansible.git
git clone https://forge.fedoraproject.org/infra/ansible.git
scripts/freezelist -i inventory
....

6
modules/sysadmin_guide/pages/geoip-city-wsgi.adoc
View file

@ -40,13 +40,13 @@ passed IP address instead of the determined IP address of the client.
== Ansible Roles
The geoip-city-wsgi role:
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/geoip-city-wsgi
https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/geoip-city-wsgi
is present in sundries playbook:
https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups/sundries.yml
https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/groups/sundries.yml
the proxy tasks are present in:
https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/include/proxies-reverseproxy.yml
https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/include/proxies-reverseproxy.yml
== Documentation Links

10
modules/sysadmin_guide/pages/greenwave.adoc
View file

@ -40,7 +40,7 @@ then combining those results into an aggregate decision.
The _policies_ for how those results should be combined or ignored, are
defined in ansible in
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/greenwave/templates/fedora.yaml.j2.yml[roles/openshift-apps/greenwave/templates/fedora.yaml.j2].
https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps/greenwave/templates/fedora.yaml.j2.yml[roles/openshift-apps/greenwave/templates/fedora.yaml.j2].
We expect to grow these over time to new use cases (rawhide compose gating, etc..)
== Observing Greenwave Behavior
@ -63,14 +63,14 @@ It relies on `resultsdb` and `waiverdb` for information.
== Upgrading
You can roll out configuration changes by changing the files in
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/greenwave[roles/openshift-apps/greenwave/] and running the
https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/greenwave.yml[playbooks/openshift-apps/greenwave.yml] playbook.
https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps/greenwave[roles/openshift-apps/greenwave/] and running the
https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/openshift-apps/greenwave.yml[playbooks/openshift-apps/greenwave.yml] playbook.
To understand how the software is deployed, take a look at these two
files:
* https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/greenwave/templates/imagestream.yml[roles/openshift-apps/greenwave/templates/imagestream.yml]
* https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/greenwave/templates/buildconfig.yml[roles/openshift-apps/greenwave/templates/buildconfig.yml]
* https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps/greenwave/templates/imagestream.yml[roles/openshift-apps/greenwave/templates/imagestream.yml]
* https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps/greenwave/templates/buildconfig.yml[roles/openshift-apps/greenwave/templates/buildconfig.yml]
See that we build a fedora-infra specific image on top of an app image
published by upstream. The `latest` tag is automatically deployed to

12
modules/sysadmin_guide/pages/index.adoc
View file

@ -35,10 +35,10 @@ group only has active members.
Members of the https://accounts.fedoraproject.org/group/fi-apprentice/[Fedora
Infrastructure Apprentice] group have ssh/shell access to many machines,
but no sudo rights or ability to commit to the
https://pagure.io/fedora-infra/ansible/[Ansible repository] (but they do
https://forge.fedoraproject.org/infra/ansible/[Ansible repository] (but they do
have read-only access). Apprentice can, however, contribute to the
infrastructure documentation by making a pull request to the
https://pagure.io/infra-docs/[infra-docs] repository. Access is via the
https://forge.fedoraproject.org/infra/docs[infra-docs] repository. Access is via the
bastion.fedoraproject.org machine and from there to each machine. See
the xref:sshaccess.adoc[ssh-sop] for instructions on how to set up SSH.
You can see a list of hosts that allow apprentice access by using:
@ -47,14 +47,14 @@ You can see a list of hosts that allow apprentice access by using:
$ ./scripts/hosts_with_var_set -i inventory/ -o ipa_client_shell_groups=fi-apprentice
....
from a checkout of the https://pagure.io/fedora-infra/ansible/[Ansible
repository]. The Ansible repository is hosted on pagure.io at
`https://pagure.io/fedora-infra/ansible.git`.
from a checkout of the https://forge.fedoraproject.org/infra/ansible/[Ansible
repository]. The Ansible repository is hosted on Forge at
`https://forge.fedoraproject.org/infra/ansible.git`.
=== Selecting a Ticket
Since apprentices do not have commit access to the
https://pagure.io/fedora-infra/ansible/[Ansible repository], you should
https://forge.fedoraproject.org/infra/ansible/[Ansible repository], you should
make your change, produce a patch with `git diff`, and attach it to the
infrastructure ticket you are working on. It will then be reviewed.

2
modules/sysadmin_guide/pages/ipa.adoc
View file

@ -55,7 +55,7 @@ To restart the IPA service you simply need to ssh to any of the servers and issu
== Configuration
Configuration is handled by the
link:https://pagure.io/fedora-infra/ansible/blob/5ad386ed6fb30484348848a354d4dfa6b7393f74/f/playbooks/groups/ipa.yml[ipa.yml]
link:https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/groups/ipa.yml[ipa.yml]
playbook in Ansible. This playbook could also be used to reconfigure application,
if that becomes necessary.

2
modules/sysadmin_guide/pages/koji-builder-setup.adoc
View file

@ -18,7 +18,7 @@ upgrade the hub/database first with the playbooks/manual/upgrade/koji.yml playbo
Follow the process to upgrade builders in staging environment:
. Chek with others that there's not any ongoing testing in staging before starting.
. Update the virt-install path on the builders in ansible repository, like in this https://pagure.io/fedora-infra/ansible/c/af94db8ab88588aa8dc2c20893b2487afb7f7777?branch=main[example]
. Update the virt-install path on the builders in ansible repository, like in this https://forge.fedoraproject.org/infra/ansible/commit/af94db8ab88588aa8dc2c20893b2487afb7f7777[example]
. Each builder virtual machine is removed, either via `virt-inst-dest` or manually
. Upgrade and reboot the bvmhost that contains those builders
. Then `buildvm.yml` playbook is run to reinstall them.

2
modules/sysadmin_guide/pages/memcached.adoc
View file

@ -61,7 +61,7 @@ sudo /etc/init.d/memcached restart
== Configuring Memcached
Memcached is currently setup as a
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/memcached[role in the ansible git repo].
https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/memcached[role in the ansible git repo].
The main two tunables are the MAXCONN (the maximum number of concurrent
connections) and CACHESIZE (the amount memory to use for storage). These
variables can be set through $memcached_maxconn and $memcached_cachesize

2
modules/sysadmin_guide/pages/message-tagging-service.adoc
View file

@ -67,7 +67,7 @@ then, run the playbook with environment `prod`.
== Update Rules
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/message-tagging-service/files/mts-rules.yml[Rules
https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps/message-tagging-service/files/mts-rules.yml[Rules
file] is managed along side the playbook role in same repository.
For detailed information of rules format, please refer to

2
modules/sysadmin_guide/pages/mini_initiatives.adoc
View file

@ -6,7 +6,7 @@ A ticket should come in to the relevant issue tracker as usual. This ticket will
== How to find a mini initiative?
Search for the mini initiative tag on the relevant tracker
* https://pagure.io/releng/issues?status=Open&tags=mini-initiative&close_status=[Releng]
* https://forge.fedoraproject.org/releng/tickets/issues?q=&type=all&sort=relevance&state=open&labels=980&milestone=0&project=0&assignee=0&poster=0&archived=false[Releng]
* https://forge.fedoraproject.org/infra/tickets/issues?status=Open&tags=mini-initiative&priority=0&close_status=[Fedora infra]
* https://pagure.io/centos-infra/issues?status=Open&tags=mini-initiative&close_status=[CentOS Infra]

2
modules/sysadmin_guide/pages/mote.adoc
View file

@ -99,5 +99,5 @@ pulled into ansible in order to be deployed.
These files are `name_mappings.json` and `category_mappings.json`. To
deploy an update to these definitions, place the updated name and
category mapping files in
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/mote/templates[ansible/roles/mote/templates].
https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/mote/templates[ansible/roles/mote/templates].
Run the playbook in order to deploy your changes.

8
modules/sysadmin_guide/pages/nagios.adoc
View file

@ -29,16 +29,16 @@ nagios (noc01)::
statistics ansible status, uptime, apache status (up/down), SSH etc.
+
The configurations are found in nagios ansible roles:
* https://pagure.io/fedora-infra/ansible/blob/main/f/roles/nagios_client[ansible/roles/nagios_client]
* https://pagure.io/fedora-infra/ansible/blob/main/f/roles/nagios_server[ansible/roles/nagios_server]
* https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/nagios_client[ansible/roles/nagios_client]
* https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/nagios_server[ansible/roles/nagios_server]
nagios-external (noc02)::
The nagios configuration on noc02 is located outside of our main
datacenter and should monitor our user websites/applications
(fedoraproject.org, FAS, PackageDB, Bodhi/Updates).
+
The configurations are found in nagios ansible roles:
* https://pagure.io/fedora-infra/ansible/blob/main/f/roles/nagios_client[ansible/roles/nagios_client]
* https://pagure.io/fedora-infra/ansible/blob/main/f/roles/nagios_server[ansible/roles/nagios_server]
* https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/nagios_client[ansible/roles/nagios_client]
* https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/nagios_server[ansible/roles/nagios_server]
[NOTE]
====

6
modules/sysadmin_guide/pages/new-virtual-hosts.adoc
View file

@ -157,7 +157,7 @@ git push
== ansible
....
git clone https://pagure.io/fedora-infra/ansible.git
git clone https://forge.fedoraproject.org/infra/ansible.git
cd ansible
....
@ -218,8 +218,8 @@ ifconfig-push 192.168.1.44 192.168.0.44
=== host_vars and group_vars
ansible consults files in
https://pagure.io/fedora-infra/ansible/blob/main/f/inventory/group_vars[inventory/group_vars]
and https://pagure.io/fedora-infra/ansible/blob/main/f/inventory/host_vars[inventory/host_vars]
https://forge.fedoraproject.org/infra/ansible/src/branch/main/inventory/group_vars[inventory/group_vars]
and https://forge.fedoraproject.org/infra/ansible/src/branch/main/inventory/host_vars[inventory/host_vars]
to set parameters that can be used in templates and playbooks. You may
need to edit these

2
modules/sysadmin_guide/pages/openqa.adoc
View file

@ -241,7 +241,7 @@ https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-{rawhide_next}&arch=x86
points to development/rawhide and
https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-{rawhide}&arch=x86_64
points to development/{rawhide}. Check the openqa_hdds_workers section of
https://pagure.io/fedora-infra/ansible/blob/main/f/inventory/inventory[the ansible inventory]
https://forge.fedoraproject.org/infra/ansible/src/branch/main/inventory/inventory[the ansible inventory]
to find the correct hosts: there should be one per arch per openQA
instance. Connect to each host, and from each, run:
```

2
modules/sysadmin_guide/pages/openvpn.adoc
View file

@ -28,7 +28,7 @@ Giving static IP's out in openvpn is mostly painless. Take a look at
other examples but each host gets a file and 2 IP's.:
....
git clone https://pagure.io/fedora-infra/ansible.git
git clone https://forge.fedoraproject.org/infra/ansible.git
vi ansible/roles/openvpn/server/files/ccd/$FQDN
....

2
modules/sysadmin_guide/pages/rdiff-backup.adoc
View file

@ -59,7 +59,7 @@ ssh-add .ssh/rdiff-backup-key
. add the host to the backup_clients inventory group in ansible.
. If you wish to backup more than `/etc` and `/home`, add a variable to
`inventory/group_vars/<app_name>` like: `host_backup_targets: ['/srv']`
See https://pagure.io/fedora-infra/ansible/blob/main/f/inventory/group_vars/pagure#_81
See https://forge.fedoraproject.org/infra/ansible/src/branch/main/inventory/group_vars/pagure#_81
for example.
. On the client to be backed up, install rdiff-backup.
. On the client to be backed up, install the rdiff-backup ssh public key

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

@ -17,7 +17,7 @@ environment <<Resources,[3]>> <<Resources,[4]>> to ensure the host correctly sho
== Resources
* [1] Official Installation Instructions: https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=9&components=server_frontend_agent&db=pgsql&ws=nginx
* [2] Playbook: https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups/zabbix.yml
* [3] Role: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/zabbix
* [2] Playbook: https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/groups/zabbix.yml
* [3] Role: https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/zabbix
* [4] Installation of the Zabbix Agent: https://www.zabbix.com/documentation/6.0/en/manual/installation/install_from_packages/rhel
* [5] Configuration Agent: https://www.zabbix.com/documentation/6.0/en/manual/concepts/agent

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

@ -1,8 +1,8 @@
= Run the Communishift Clean Up Script
== Resources
- [1] Playbook: https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/manual/communishift_send_email_notifications.yml
- [2] Role: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/communishift
- [1] Playbook: https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/manual/communishift_send_email_notifications.yml
- [2] Role: https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/communishift
- [3] Cluster: https://console-openshift-console.apps.fedora.cj14.p1.openshiftapps.com

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

@ -1,8 +1,8 @@
= Onboard a tenant to the Communishift Cluster
== Resources
- [1] Playbook: https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/manual/communishift.yml
- [2] Role: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/communishift
- [1] Playbook: https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/manual/communishift.yml
- [2] Role: https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/communishift
- [3] Cluster: https://console-openshift-console.apps.fedora.cj14.p1.openshiftapps.com
- [4] CAO: https://pagure.io/cpe/communishift/blob/main/f/CommunishiftAuthorization

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

@ -11,8 +11,8 @@ A high level overview of how a baremetal node in the Fedora Infra gets booted vi
== Resources
- [1] https://pagure.io/fedora-infra/ansible/blob/main/f/roles/dhcp_server[Ansible Role DHCP Server]
- [2] https://pagure.io/fedora-infra/ansible/blob/main/f/roles/tftp_server[Ansible Role tftpboot server]
- [1] https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/dhcp_server[Ansible Role DHCP Server]
- [2] https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/tftp_server[Ansible Role tftpboot server]
== UEFI Configuration
The configuration for UEFI booting is contained in the `grub.cfg` config which is not currently under source control. It is located on the `batcave01` at: `/srv/web/infra/bigfiles/tftpboot2/uefi/grub.cfg`.

2
modules/sysadmin_guide/pages/sop_configure_oauth_ipa.adoc
View file

@ -3,7 +3,7 @@
== Resources
- [1] https://pagure.io/fedora-infra/ansible/blob/main/f/files/communishift/objects[Example Config from Communishift]
- [1] https://forge.fedoraproject.org/infra/ansible/src/branch/main/files/communishift/objects[Example Config from Communishift]
== OIDC Setup

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

@ -2,8 +2,8 @@
== Resources
- [1] Code: https://pagure.io/cpe/fas2discourse/
- [2] Playbook: https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/manual/fas2discourse.yml
- [3] Role: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/fas2discourse
- [2] Playbook: https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/manual/fas2discourse.yml
- [3] Role: https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/fas2discourse
== Workload
The operator runs in the namespace: `fas2discourse-operator` on both the staging and production openshift clusters.

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

@ -2,8 +2,8 @@
== Resources
- [1] Code: https://pagure.io/cpe/fas2discourse/
- [2] Playbook: https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/manual/fas2discourse.yml
- [3] Role: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/fas2discourse
- [2] Playbook: https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/manual/fas2discourse.yml
- [3] Role: https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/fas2discourse
== Installation on Fedora Infra

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

@ -2,8 +2,8 @@
== Resources
- [1] Code: https://pagure.io/cpe/fas2discourse/
- [2] Playbook: https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/manual/fas2discourse.yml
- [3] Role: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/fas2discourse
- [2] Playbook: https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/manual/fas2discourse.yml
- [3] Role: https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/fas2discourse
== Overview of the fas2discourse Operator
The role of this operator is to synchronise group membership between IPA and Discourse. It does not synchronise all groups and all members, but only groups which exist in Discourse.

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

@ -105,11 +105,11 @@ On the `batcave01` at the following location: `/srv/web/infra/bigfiles/openshift
=== Update the ansible inventory
The ansible inventory/hostvars/group vars should be updated with the new hosts information.
For inspiration see the following https://pagure.io/fedora-infra/ansible/pull-request/765[PR] where we added the ocp4 production changes.
For inspiration see the following https://forge.fedoraproject.org/infra/ansible/pulls/765[PR] where we added the ocp4 production changes.
=== Update the DNS/DHCP configuration
The DNS and DHCP configuration must also be updated. This https://pagure.io/fedora-infra/ansible/pull-request/765[PR] contains the necessiary changes DHCP for prod and can be done in ansible.
The DNS and DHCP configuration must also be updated. This https://forge.fedoraproject.org/infra/ansible/pulls/765[PR] contains the necessiary changes DHCP for prod and can be done in ansible.
However the DNS changes may only be performed by `sysadmin-main`. For this reason any DNS changes must go via a patch snippet which is emailed to the `infrastructure@lists.fedoraproject.org` mailing list for review and approval. This process may take several days.

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

@ -2,7 +2,7 @@
== Resources
- [1] https://pagure.io/fedora-infra/ansible/blob/main/f/roles/dhcp_server[Ansible Role DHCP Server]
- [1] https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/dhcp_server[Ansible Role DHCP Server]
== Retrieve CACERT
In Fedora Infra, we have Apache terminating TLS for the cluster. Connections to the api and the machineconfig server are handled by haproxy. To prevent TLS errors we must configure haproxy with the OCP4 Cluster CA Cert.
@ -13,7 +13,7 @@ This can be retrieved once the cluster control plane has been installed, from th
oc get configmap kube-root-ca.crt -o yaml -n openshift-ingress
----
Extract this CACERT in full, and commit it to ansible at: `https://pagure.io/fedora-infra/ansible/blob/main/f/roles/haproxy/files/ocp.<ENV>-rdu3.pem`
Extract this CACERT in full, and commit it to ansible at: `https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/haproxy/files/ocp.<ENV>-rdu3.pem`
To deploy this cert, one must be apart of the `sysadmin-noc` group. Run the following playbook:

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

@ -6,5 +6,5 @@ Members of the group `sysadmin-noc` may run this playbook.
== Resources
* [1] Official Installation Instructions: https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=9&components=server_frontend_agent&db=pgsql&ws=nginx
* [2] Playbook: https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups/zabbix.yml
* [3] Role: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/zabbix
* [2] Playbook: https://forge.fedoraproject.org/infra/ansible/src/branch/main/playbooks/groups/zabbix.yml
* [3] Role: https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/zabbix

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

@ -1,6 +1,6 @@
= testdays Infrastructure SOP
https://pagure.io/fedora-qa/testdays-web/[testdays] is an app developed
https://forge.fedoraproject.org/quality/testdays-web[testdays] is an app developed
by Fedora QA to aid with managing testday events for the community.
== Contents
@ -23,7 +23,7 @@ Persons::
Servers::
* In OpenShift.
Purpose::
Hosting the https://pagure.io/fedora-qa/testdays-web/[testdays] for the QA ad the community
Hosting the https://forge.fedoraproject.org/quality/testdays-web[testdays] for the QA ad the community
== File Locations

2
modules/sysadmin_guide/pages/tickets.adoc
View file

@ -139,7 +139,7 @@ Find POC in CPE team for it.
+
In this case Fedora Infra should investigate the situation.
**** Add an investigation to https://pagure.io/fedora-infra/arc[ARC team board], prioritized by Product Owner
**** Add an investigation to https://forge.fedoraproject.org/cle/arc[ARC team board], prioritized by Product Owner
**** Figure out if it's an iniative, or a mini-initiative or just standard ticket

2
modules/sysadmin_guide/pages/waiverdb.adoc
View file

@ -83,7 +83,7 @@ Be careful. You can delete individual waivers with SQL.
== Upgrading
You can roll out configuration changes by changing the files in
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/waiverdb[roles/openshift-apps/waiverdb/]
https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps/waiverdb[roles/openshift-apps/waiverdb/]
and running the `playbooks/openshift-apps/waiverdb.yml` playbook.
To understand how the software is deployed, take a look at these two