pagure infra tickets to forge
I've tried to adjust any places in our docs where we were pointing to a specific ticket to the new forge link. Also, any places that mentioned where tickets are located. The tickets sop needs a ton of work, I will do that in another PR. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
parent
00c1a2b344
commit
3c6fe7c27b
21 changed files with 30 additions and 45 deletions
|
|
@ -55,7 +55,7 @@ them. Be sure to discuss in meeting or in a issue whatever you find.
|
|||
|
||||
* Pick a ticket
|
||||
|
||||
Look in link:https://pagure.io/fedora-infrastructure/issues[] for a ticket that looks interesting to you. If the ticket is already assigned, but hasn't
|
||||
Look in link:https://forge.fedoraproject.org/infra/tickets/issues[] for a ticket that looks interesting to you. If the ticket is already assigned, but hasn't
|
||||
had any action in a while, feel free to ask on the ticket if it's still being worked on, and if there is no reply in a week or so, take it over.
|
||||
Some tickets can be worked on by several people, so feel free to ask in ticket if this is one of those kinds of tasks and what part you can work
|
||||
on. If a ticket seems really old and like it may no longer be needed, please add it to the agenda of the next meeting and we will discuss it
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ by Fedora. It is meant to host PoC or test deployments for Fedora related projec
|
|||
== Request new namespace
|
||||
|
||||
To request a new namespace in Communishift go to
|
||||
link:https://pagure.io/fedora-infrastructure/issues[Fedora Infrastructure ticket tracker], open a
|
||||
link:https://forge.fedoraproject.org/infra/tickets/issues[Fedora Infrastructure ticket tracker], open a
|
||||
new issue and use `communishift` template (look at the `Types` field).
|
||||
|
||||
If you need any help with your OpenShift project, please refer to official
|
||||
|
|
@ -35,14 +35,14 @@ https://docs.openshift.com/dedicated/web_console/web-console.html[OpenShift web
|
|||
|
||||
All the projects on Communishift will be deleted every Fedora Linux release (6 months). If you need
|
||||
more than 6 months for your project, please open a ticket on
|
||||
link:https://pagure.io/fedora-infrastructure/issues[Fedora Infrastructure ticket tracker] and explain
|
||||
link:https://forge.fedoraproject.org/infra/tickets/issues[Fedora Infrastructure ticket tracker] and explain
|
||||
why your project should not be deleted.
|
||||
|
||||
== Request for additional resources
|
||||
|
||||
There is a quota set per project. In case you need additional resources for your project please
|
||||
open a ticket on
|
||||
link:https://pagure.io/fedora-infrastructure/issues[Fedora Infrastructure ticket tracker] with
|
||||
link:https://forge.fedoraproject.org/infra/tickets/issues[Fedora Infrastructure ticket tracker] with
|
||||
information about how much resources you need and why you need them.
|
||||
|
||||
== Service usage requirements
|
||||
|
|
|
|||
|
|
@ -21,16 +21,16 @@ a change asap) or is your issue/problem such that you cannot file a ticket
|
|||
say '!oncall' and explain the issue or problem to the oncall person.
|
||||
|
||||
* If no one is available there:
|
||||
** If you cannot authenticate to link:https://pagure.io/[], send an email
|
||||
** If you cannot authenticate to link:https://forge.fedoraproject.org/[], send an email
|
||||
to admin@fedoraproject.org
|
||||
** Otherwise: go to next step.
|
||||
|
||||
=== Ticket tracking
|
||||
|
||||
By default, the infrastructure team tracks its work in tickets at:
|
||||
link:https://pagure.io/fedora-infrastructure/issues/[].
|
||||
link:https://forge.fedoraproject.org/infra/tickets/issues/[].
|
||||
If you need something from us, please
|
||||
link:https://pagure.io/fedora-infrastructure/new_issue[open a new ticket] with
|
||||
link:https://forge.fedoraproject.org/infra/tickets/issues/[open a new ticket] with
|
||||
as much information as you think is needed to process this request.
|
||||
|
||||
Once created your ticket will follow the following flow:
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ options] for this in fedora-messaging.
|
|||
|
||||
Clients require certificates issued by Fedora Infrastructure. If you're
|
||||
not using the external, read-only user, file a
|
||||
https://pagure.io/fedora-infrastructure/issues[ticket] requesting a
|
||||
https://forge.fedoraproject.org/infra/tickets/issues[ticket] requesting a
|
||||
certificate for the AMQP broker and be sure to provide the username you
|
||||
plan to use. This is placed in the Common Name of the client certificate
|
||||
and must match the name of the user you create in AMQP. Consult the
|
||||
|
|
|
|||
|
|
@ -10,8 +10,8 @@ NOTE: Should these best practices be something maintained by the kube-sig? If so
|
|||
- [3] Prometheus metrics format https://github.com/prometheus/docs/blob/main/content/docs/instrumenting/exposition_formats.md#text-based-format
|
||||
- [4] Fedora Kubedev SIG https://fedoraproject.org/wiki/SIGs/KubeDev
|
||||
- [5] Openshift oauth-proxy https://github.com/openshift/oauth-proxy
|
||||
- [6] Fedora Infra migration tracker DeploymentConfig to Deployment https://pagure.io/fedora-infrastructure/issue/12142
|
||||
- [7] Fedora Infra ticket tracker: https://pagure.io/fedora-infrastructure/issues
|
||||
- [6] Fedora Infra migration tracker DeploymentConfig to Deployment https://forge.fedoraproject.org/infra/tickets/issues/12142
|
||||
- [7] Fedora Infra ticket tracker: https://forge.fedoraproject.org/infra/tickets/issues
|
||||
- [8] 42 Prod Best Practices The Complete Guide for Developers https://medium.com/@mahernaija/docker-2024-docker-compose-2024-master-best-practices-the-complete-guide-for-developers-aaf851349240
|
||||
- [9] Semantic Versioning https://semver.org/
|
||||
- [10] Resources https://docs.openshift.com/container-platform/4.17/scalability_and_performance/compute-resource-quotas.html
|
||||
|
|
@ -80,7 +80,6 @@ RUN rm -f 2 \
|
|||
|
||||
== DeploymentConfig migration to Deployments
|
||||
- DeploymentConfig is depreciated and is being phased out (very) soonish, we should replace all DeploymentConfigs with Deployments.
|
||||
- This is being tracked with a board on pagure: https://pagure.io/fedora-infrastructure/issue/12142
|
||||
- We should consider breaking this epic up into smaller tickets and creating individual tickets to track each instance of DeploymentConfig deployed app in Fedora Infra.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ git commit -s -a -m 'Added fedora-messaging certs for <service>'
|
|||
git push
|
||||
----
|
||||
|
||||
Source: https://pagure.io/fedora-infrastructure/issue/8638
|
||||
Source: https://forge.fedoraproject.org/infra/tickets/issues/8638
|
||||
|
||||
== Regenerating TLS certificates
|
||||
|
||||
|
|
|
|||
|
|
@ -58,4 +58,4 @@ This needs to be run on the `os-node` that is running out of space.
|
|||
|
||||
|
||||
|
||||
Source: https://pagure.io/fedora-infrastructure/issue/8643
|
||||
Source: https://forge.fedoraproject.org/infra/issues/8643
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ and function of these types of groups remains.
|
|||
== How to request a group to be created?
|
||||
|
||||
The short answer is to open a ticket on the fedora-infrastructure issue tracker:
|
||||
https://pagure.io/fedora-infrastructure/
|
||||
https://forge.fedoraproject.org/infra/tickets/issues
|
||||
|
||||
It is unlikely you will need to create "shell" group, but you can ask for the
|
||||
creation of a "tracking" or "pkgdb" group.
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ You need to have the following information handy to follow the process.
|
|||
== Steps
|
||||
|
||||
1. Connect with the
|
||||
https://pagure.io/fedora-infrastructure/[*Fedora Infrastructure*] team to
|
||||
https://forge.fedoraproject.org/infra/tickets/[*Fedora Infrastructure*] team to
|
||||
request the credentials for the web interface of the iDRAC management
|
||||
controllers.
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ key, but we need to resign everything with the f{rawhide_next} key for rawhide.
|
|||
{% endif %}
|
||||
```
|
||||
This allows robosignatory to sign packages in the f{rawhide} tag with the f{rawhide_next} key.
|
||||
* git clone https://pagure.io/releng
|
||||
* git clone https://forge.fedoraproject.org/releng/tooling
|
||||
* confirm the new key fingerprint is in scripts_new/release-process/signing/koji_rpm_signer.py
|
||||
* run koji_rpm_signer.py to gather list of packages to sign:
|
||||
```
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ have an automation user associated with it.
|
|||
|
||||
=== Request a new loopabull user
|
||||
|
||||
File a ticket with https://pagure.io/fedora-infrastructure/[Fedora
|
||||
File a ticket with https://forge.fedoraproject.org/infra/tickets[Fedora
|
||||
Infrastructure] making sure to satisfy the following requirements:
|
||||
|
||||
* Provide a justification for these permissions being needed (What are
|
||||
|
|
@ -23,5 +23,5 @@ you trying to do and why?)
|
|||
`loopabull_` username needs it's pre-existing permissions enhanced
|
||||
|
||||
For reference:
|
||||
https://pagure.io/fedora-infrastructure/issue/5943[Example
|
||||
https://forge.fedoraproject.org/infra/tickets/issues/5943[Example
|
||||
Infrastructure Ticket]
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ be allowed to host.
|
|||
=== Non Official Hosting
|
||||
|
||||
People wanting to host unofficial bits may request approval for hosting.
|
||||
Create a ticket at https://pagure.io/fedora-infrastructure/ explaining
|
||||
Create a ticket at https://forge.fedoraproject.org/infra/tickets explaining
|
||||
what and why Fedora should host it. Such will be reviewed by the Fedora
|
||||
Infrastructure team.
|
||||
|
||||
|
|
@ -61,7 +61,7 @@ more.
|
|||
* Make sure you have a Fedora account
|
||||
-https://accounts.fedoraproject.org/
|
||||
* Ensure you have signed the Fedora Project Contributor Agreement (FPCA)
|
||||
* Submit a hosting request -https://pagure.io/fedora-infrastructure/
|
||||
* Submit a hosting request -https://forge.fedoraproject.org/infra/tickets
|
||||
** Include who you are, and any group you are working with (e.g. a SIG)
|
||||
** Include Space requirements
|
||||
** Include an estimate of the number of downloads expected (if you can).
|
||||
|
|
|
|||
|
|
@ -334,7 +334,7 @@ https://github.com/fedora-infra/mirrors-countme/issues/new
|
|||
Anything concerning the cron jobs or other scripts should probably go into our
|
||||
Infrastructure tracker:
|
||||
|
||||
https://pagure.io/fedora-infrastructure/new_issue
|
||||
https://forge.fedoraproject.org/infra/tickets/issues
|
||||
|
||||
== Are there any GDPR related concerns? Mechanisms to deal with PII?
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
|
||||
=== Overview
|
||||
This SOP shows some of the steps required to troubleshoot and diagnose a power issue with one of our servers. A ticket was opened Infra Ticket: https://pagure.io/fedora-infrastructure/issue/11950
|
||||
This SOP shows some of the steps required to troubleshoot and diagnose a power issue with one of our servers. A ticket was opened Infra Ticket: https://forge.fedoraproject.org/infra/tickets/issues/11950
|
||||
|
||||
Symptoms:
|
||||
- This server is not responding at all, and will not power on.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ A ticket should come in to the relevant issue tracker as usual. This ticket will
|
|||
Search for the mini initiative tag on the relevant tracker
|
||||
|
||||
* https://pagure.io/releng/issues?status=Open&tags=mini-initiative&close_status=[Releng]
|
||||
* https://pagure.io/fedora-infrastructure/issues?status=Open&tags=mini-initiative&priority=0&close_status=[Fedora infra]
|
||||
* 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]
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -105,7 +105,7 @@ Once you've been sponsored for a team its generally your job to find
|
|||
what work needs to be done in the ticketing system. Be proactive about
|
||||
this. The tickets can be found at:
|
||||
|
||||
https://pagure.io/fedora-infrastructure/issues
|
||||
https://forge.fedoraproject.org/infra/tickets/issues
|
||||
|
||||
When you find a ticket that interests you contact your sponsor or the
|
||||
ticket owner and offer help. While you're getting used to the way things
|
||||
|
|
@ -140,20 +140,6 @@ only important when troubleshooting things. When you first get granted
|
|||
access to one of the sysadmin-* groups, the first place you should turn
|
||||
is bastion.fedoraproject.org then from there ssh to batcave01.
|
||||
|
||||
We also have an architecture repo available in our git repo. To get a
|
||||
copy of this repo just:
|
||||
|
||||
....
|
||||
dnf install git
|
||||
git clone https://pagure.io/fedora-infrastructure.git
|
||||
....
|
||||
|
||||
This will allow you to look through (and help fix) some of our scripts
|
||||
as well as have access to our architectural documentation. Become
|
||||
familiar with those docs if you're curious. There's always room to do
|
||||
better documentation so if you're interested just ping your sponsor and
|
||||
ask about it.
|
||||
|
||||
== Our Rules
|
||||
|
||||
The Fedora Infrastructure Team does have some rules. First is the
|
||||
|
|
|
|||
|
|
@ -171,7 +171,7 @@ Phase III
|
|||
|
||||
* *SOP link*: <https://docs.fedoraproject.org/infra/sysadmin_guide/.....>
|
||||
* *Application Security Policy self-evaluation*: ....
|
||||
* *Audit request*: <https://pagure.io/fedora-infrastructure/issue/....>
|
||||
* *Audit request*: <https://forge.fedoraproject.org/infra/tickets/issues/....>
|
||||
(can be same)
|
||||
* *Audit timeline*: <04-11-2025 - 06-11-2025> (timeline to be provided
|
||||
by the security officer upon audit request)
|
||||
|
|
@ -181,4 +181,4 @@ Phase IV
|
|||
* *Ansible playbooks*: <ansible/playbooks/groups/myservice.yml>
|
||||
* *Fully rebuilt from ansible*: <yes>
|
||||
* *Production goal*: <08-11-2025>
|
||||
* *Approved audit*: <https://pagure.io/fedora-infrastructure/issue/....>
|
||||
* *Approved audit*: <https://forge.fedoraproject.org/infra/tickets/issues/....>
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ This SOP documents step by step, of what was required [14] to add Zabbix monitor
|
|||
- [11] Zabbix added to Releng Hosts PR: https://pagure.io/fedora-infra/ansible/pull-request/1653#
|
||||
- [12] Zabbix kvm Virtual Host template: https://www.zabbix.com/integrations/kvm
|
||||
- [13] Releng Ansible cronjob installation: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/releng/tasks/main.yml
|
||||
- [14] Fedora Infra Ticket: https://pagure.io/fedora-infrastructure/issue/11577
|
||||
- [14] Fedora Infra Ticket: https://forge.fedoraproject.org/infra/tickets/issues/11577
|
||||
- [15] Failed Compose Monitoring: https://pagure.io/releng/failed-composes/issues
|
||||
- [16] Fedora Infra Releng Compose Monitoring Software: https://pagure.io/releng/compose-tracker
|
||||
- [17] Zabbix Production Server: https://zabbix.fedoraproject.org
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ menuentry 'RHCOS 4.8 worker staging' {
|
|||
}
|
||||
----
|
||||
|
||||
Any new changes must be made here. Writing to this file requires one to be a member of the `sysadmin-main` group, so best to instead create a ticket in the Fedora Infra issue tracker with patch request. See the following https://pagure.io/fedora-infrastructure/issue/10213[PR] for inspiration.
|
||||
Any new changes must be made here. Writing to this file requires one to be a member of the `sysadmin-main` group, so best to instead create a ticket in the Fedora Infra issue tracker with patch request. See the following https://forge.fedoraproject.org/infra/issues/10213[PR] for inspiration.
|
||||
|
||||
== Pushing new changes out to the tftpboot server
|
||||
To push out changes made to the `grub.cfg` the following playbook should be run, which requires `sysadmin-noc` group permissions:
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ The following SOPs are related to the administration of the fas2discourse operat
|
|||
== Resources
|
||||
- https://pagure.io/cpe/fas2discourse/[Code]
|
||||
- https://quay.io/repository/fedora/fas2discourse-operator[Image]
|
||||
- https://pagure.io/fedora-infrastructure/issue/10952[Initial ticket]
|
||||
- https://forge.fedoraproject.org/infra/tickets/issues/10952[Initial ticket]
|
||||
- xref:sop_fas2discourse_operator_installation.adoc[Install the fas2discourse operator]
|
||||
- xref:sop_fas2discourse_operator_testing.adoc[Testing the fas2discourse operator]
|
||||
- xref:sop_fas2discourse_operator_build.adoc[Building/releasing the fas2discourse operator]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
= How to handle new tickets in fedora-infrastructure
|
||||
|
||||
This SOP describes the process of handling incoming tickets on
|
||||
https://pagure.io/fedora-infrastructure.
|
||||
https://forge.fedoraproject.org/infra/tickets/
|
||||
|
||||
== Contact Information
|
||||
|
||||
|
|
@ -10,7 +10,7 @@ Owner::
|
|||
Contact::
|
||||
#fedora-admin, #fedora-noc
|
||||
Location::
|
||||
https://pagure.io/fedora-infrastructure
|
||||
https://forge.fedoraproject.org/infra/tickets/issues
|
||||
Purpose::
|
||||
Fedora infra ticket tracker
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue