Fixing Links from md format to asciidoc format
This commit is contained in:
parent
7cd5a5305e
commit
b4172a7f22
2 changed files with 35 additions and 35 deletions
|
|
@ -9,9 +9,9 @@ apprentices to examine and gather info on problems, then propose solutions.
|
|||
|
||||
Members of the fi-apprentice group have ssh/shell access to many machines, but no sudo rights or ability
|
||||
to commit to ansible (but they do have read-only access). Apprentice can, however, contribute to the
|
||||
infrastructure documentation by sending pull requests to the [infra-docs-fpo](https://pagure.io/infra-docs-fpo)
|
||||
infrastructure documentation by sending pull requests to the link:https://pagure.io/infra-docs-fpo[infra-docs-fpo]
|
||||
repository. Access is via the bastion.fedoraproject.org machine and from there to each machine. See the
|
||||
[SSH Access Infrastructure SOP](https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/sshaccess/) for more
|
||||
link:https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/sshaccess/[SSH Access Infrastructure SOP] for more
|
||||
info. 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 an ansible repo checkout (see below).
|
||||
|
|
@ -19,11 +19,11 @@ from an ansible repo checkout (see below).
|
|||
== Nagios alerts
|
||||
|
||||
This group does NOT get Nagios alerts. If you would like to see them you can join the #fedora-noc channel, adjust your
|
||||
[FMN notifications settings](https://apps.fedoraproject.org/notifications) or watch the Nagios web interface at:
|
||||
https://admin.fedoraproject.org/nagios/ and https://nagios-external.fedoraproject.org/nagios/
|
||||
link:https://apps.fedoraproject.org/notifications[FMN notifications settings] or watch the Nagios web interface at:
|
||||
link:https://admin.fedoraproject.org/nagios/[] and link:https://nagios-external.fedoraproject.org/nagios/[]
|
||||
|
||||
Nagios access is now controlled by kerberos, so you will need to do a command with “kinit your_fas_name@@FEDORAPROJECT.ORG”.
|
||||
On the use of the kerberos, you can view the page https://fedoraproject.org/wiki/Infrastructure/Kerberos
|
||||
On the use of the kerberos, you can view the page link:https://fedoraproject.org/wiki/Infrastructure/Kerberos[]
|
||||
|
||||
== Length of membership
|
||||
|
||||
|
|
@ -37,13 +37,13 @@ There's a few items we need help with ongoing and apprentices are encouraged to
|
|||
and ask questions, etc. The current list:
|
||||
|
||||
* Update group variables in ansible for CSI standards for machines that don't have any listed. See:
|
||||
https://docs.fedoraproject.org/en-US/Community_Services_Infrastructure/1/html/Security_Policy/index.html
|
||||
link:https://docs.fedoraproject.org/en-US/Community_Services_Infrastructure/1/html/Security_Policy/index.html[]
|
||||
for information on CSI, and look at the ansible repo under inventory/group_vars/ for groups without CSI information.
|
||||
Patches adding this information for groups can be sent to the infrastructure list to be reviewed and applied. Please
|
||||
refer to [standards for documenting CSI variables](https://fedoraproject.org/wiki/Standards_for_documenting_CSI_variables) before submitting patches
|
||||
refer to link:https://fedoraproject.org/wiki/Standards_for_documenting_CSI_variables[standards for documenting CSI variables] before submitting patches
|
||||
for ansible.
|
||||
|
||||
* Our docs aren't all using the same template. See the https://pagure.io/infra-docs-fpo repo and propose patches
|
||||
* Our docs aren't all using the same template. See the link:https://pagure.io/infra-docs-fpo[] repo and propose patches
|
||||
to update documents to use the same templates as the rest.
|
||||
|
||||
* Look over our logs on log01.iad2.fedoraproject.org in /var/log/merged/ and track down issues and propose solutions to
|
||||
|
|
@ -52,13 +52,13 @@ them. Be sure to discuss in meeting or in a issue whatever you find.
|
|||
== easyfix tickets
|
||||
|
||||
There are tickets marked with the 'easyfix' keyword that may be suitable for apprentices to learn how things are setup, and also contribute a
|
||||
fix. See the [pagure.io easyfix report](https://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix)
|
||||
fix. See the link:https://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix[pagure.io easyfix report]
|
||||
|
||||
=== Working on a ticket workflow
|
||||
|
||||
* Pick a ticket
|
||||
|
||||
Look in 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://pagure.io/fedora-infrastructure/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
|
||||
|
|
@ -67,7 +67,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.iad2.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 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://pagure.io/fedora-infra/ansible[]
|
||||
|
||||
== IRC/Matrix Tips
|
||||
|
||||
|
|
@ -77,8 +77,8 @@ The primary ways the infrastructure team communicates are IRC and Matrix. Here's
|
|||
Please be patient.
|
||||
|
||||
* Try to avoid private messages to specific team members. Instead ask your questions in #fedora-admin or #fedora-noc on IRC and
|
||||
[Fedora Infrastructure Team"](https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org) and ["Fedora Network Operation Center"](https://chat.fedoraproject.org/#/room/#noc:fedoraproject.org)
|
||||
on Matrix if at all possible. This allows anyone to help you out and also other folks to see the answer and peer review the answers you get.
|
||||
link:https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[Fedora Infrastructure Team"] and link:https://chat.fedoraproject.org/#/room/#noc:fedoraproject.org["Fedora Network Operation Center"]
|
||||
on Matrix if at all possible. This allows anyone to help you out and also other folks to see the answer and peer review the answers you get.
|
||||
|
||||
* Try and assume best intentions on past decisions. There is often a reason for something being setup the way it is or there's some history
|
||||
behind it. "Have we considered switching from foo to bar?" is great, "Why are you using foo! bar is better, we should switch to it right now"
|
||||
|
|
@ -93,15 +93,15 @@ active in channel. Many people have a IRC 'trigger' that notifies them when some
|
|||
If so, please feel free to chime in in channel that you would be interested in helping out and ask how you could
|
||||
do so.
|
||||
|
||||
* IRC channel #fedora-admin is bridged to [Fedora Infrastructure Matrix room](https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org),
|
||||
#fedora-apps is bridged to [Fedora Apps Matrix room](https://chat.fedoraproject.org/#/room/#apps:fedoraproject.org)
|
||||
and #fedora-nox is bridged to ["Fedora Network Operation Center"](https://chat.fedoraproject.org/#/room/#noc:fedoraproject.org).
|
||||
These rooms belongs to the [Fedora Matrix servers](https://chat.fedoraproject.org).
|
||||
* IRC channel #fedora-admin is bridged to link:https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[Fedora Infrastructure Matrix room],
|
||||
#fedora-apps is bridged to link:https://chat.fedoraproject.org/#/room/#apps:fedoraproject.org[Fedora Apps Matrix room]
|
||||
and #fedora-nox is bridged to link:https://chat.fedoraproject.org/#/room/#noc:fedoraproject.org["Fedora Network Operation Center"].
|
||||
These rooms belongs to the link:https://chat.fedoraproject.org[Fedora Matrix servers].
|
||||
|
||||
== Further information
|
||||
|
||||
For further information on this group, please ask in #fedora-admin on irc.libera.chat, the
|
||||
[Fedora Infrastructure Matrix room](https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org) and/or
|
||||
link:https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[Fedora Infrastructure Matrix room] and/or
|
||||
the fedora infrastructure xref:index.adoc#_mailing_list[mailing list].
|
||||
|
||||
Ansible documentation is available at http://docs.ansible.com/
|
||||
Ansible documentation is available at link:http://docs.ansible.com/[].
|
||||
|
|
@ -42,39 +42,39 @@ Start] section if you just want to submit a single change or fix.
|
|||
== First steps
|
||||
|
||||
* First you will need to read through and understand
|
||||
[how to be a successful contributor](https://docs.fedoraproject.org/en-US/commops/contribute/successful-contributor/).
|
||||
* Next you will need to create a [Fedora Account](https://docs.fedoraproject.org/en-US/fedora-accounts/user/):
|
||||
link:https://docs.fedoraproject.org/en-US/commops/contribute/successful-contributor/[how to be a successful contributor].
|
||||
* Next you will need to create a link:https://docs.fedoraproject.org/en-US/fedora-accounts/user/[Fedora Account]:
|
||||
** This account will be used for just about everything you do as a
|
||||
member of the Fedora Community
|
||||
** You will need it to sign the [FPCA](https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement)
|
||||
** You will need it to sign the link:https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement[FPCA]
|
||||
which is required to contribute to the Fedora Community
|
||||
** You will need it to login to various systems associated with the Infrastructure Group
|
||||
** You will need it to upload code changes, make changes to this wiki and etc.
|
||||
* After you have created your account and signed the FPCA, you should then subscribe to the
|
||||
[Fedora Infrastructure Mailing List](https://lists.fedoraproject.org/admin/lists/infrastructure.lists.fedoraproject.org/)
|
||||
and you should check the [Infrastructure tag at Fedora Discussion](https://discussion.fedoraproject.org/tags/c/project/7/infrastructure-team).
|
||||
link:https://lists.fedoraproject.org/admin/lists/infrastructure.lists.fedoraproject.org/[Fedora Infrastructure Mailing List]
|
||||
and you should check the link:https://discussion.fedoraproject.org/tags/c/project/7/infrastructure-team[Infrastructure tag at Fedora Discussion].
|
||||
** This is the mailing list you will use to send your introduction email to the Fedora
|
||||
Infrastructure Team as well as communicate with other team members on a regular basis.
|
||||
** When you are ready to send a [introduction to the group](mailto:infrastructure@lists.fedoraproject.org),
|
||||
** your subject should be 'Meeting Agenda Item: Introduction _Your Name_'.
|
||||
The message body should include:
|
||||
*** Your IRC/Matrix handle
|
||||
**** [_What's this?_](https://fedoraproject.org/wiki/How_to_use_IRC)
|
||||
**** [Beginner's Guide to IRC](https://fedoramagazine.org/beginners-guide-irc)
|
||||
**** [Fedora's Matrix instance at chat.fedoraproject.org](https://fedoramagazine.org/join-the-conversation/)
|
||||
**** link:https://fedoraproject.org/wiki/How_to_use_IRC[_What's this?_]
|
||||
**** link:https://fedoramagazine.org/beginners-guide-irc[Beginner's Guide to IRC]
|
||||
**** link:https://fedoramagazine.org/join-the-conversation/[Fedora's Matrix instance at chat.fedoraproject.org]
|
||||
*** What skills you have to offer and which you would like to learn. This can include...
|
||||
**** Programming languages you are familiar with or have used
|
||||
**** 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 [outstanding issues](http://pagure.io/fedora-infrastructure/issues) you would like to help resolve
|
||||
*** Look at our [Fedora Infrastructure Easyfix](https://fedoraproject.org/easyfix/#fedora-infrastructure)
|
||||
*** 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
|
||||
*** Look at our link:https://fedoraproject.org/easyfix/#fedora-infrastructure[Fedora Infrastructure Easyfix]
|
||||
issues for one that is of interest.
|
||||
** Any initial questions you have for the team
|
||||
*** Look at the [Fedora Infrastructure Best Practices](https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/) document
|
||||
*** 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 IRC.
|
||||
*** join the #fedora-admin channel on IRC and attend the next IRC meeting.
|
||||
*** Watch [some videos](http://fedoramagazine.org/?p=642) intended to introduce new contributors to
|
||||
*** Watch link:http://fedoramagazine.org/?p=642[some videos] intended to introduce new contributors to
|
||||
the team.
|
||||
|
||||
== What is next?
|
||||
|
|
@ -82,13 +82,13 @@ the team.
|
|||
After you've completed the steps outlined in the xref:gettingstarted.adoc#_first_steps[First steps
|
||||
section] you should:
|
||||
|
||||
* Regularly attend the [Weekly Meetings](https://fedoraproject.org/wiki/Infrastructure/Meetings)
|
||||
* Regularly attend the link:https://fedoraproject.org/wiki/Infrastructure/Meetings[Weekly Meetings]
|
||||
on IRC/Matrix and be sure to introduce yourself the first time you attend. There is a section at the
|
||||
start of the meeting where you can give a short introduction of yourself to the rest of the team.
|
||||
* Take some time to learn about the [services](https://docs.fedoraproject.org/en-US/infra/map_critical_services/)
|
||||
* Take some time to learn about the link:[services]https://docs.fedoraproject.org/en-US/infra/map_critical_services/
|
||||
the Fedora Infrastructure Group develops, deploys and maintains.
|
||||
* Ask about joining the xref:apprentice.adoc[Fedora Infrastructure Apprentice] (fi-apprentice) group.
|
||||
* Read up on [SOPs](https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/#_standard_operating_procedures)
|
||||
* Read up on link:https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/#_standard_operating_procedures[SOPs]
|
||||
you find interesting. These are a good point of reference for hosts related to an app. They give an overview
|
||||
of how things work for that app.
|
||||
* Idle in IRC and chime in with questions or offers to help when you see an interesting problem being discussed.
|
||||
|
|
@ -109,7 +109,7 @@ contributions.
|
|||
|
||||
The Fedora Infrastructure Group consists of volunteers and Red Hat employees. Our preferred
|
||||
method of communication is IRC on Libera.Chat in channel though we also heavily use the Fedora Mailing
|
||||
List. We also have a Matrix room dedicated to us [#admin](https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org).
|
||||
List. We also have a Matrix room dedicated to us link:https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[#admin].
|
||||
We try to be as transparent as possible and default to open.
|
||||
|
||||
New members are encouraged to join the list, use the discourse, IRC, Matrix and attend meetings.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue