System Administrator Guide
Welcome to The Fedora Infrastructure system administration guide.
Getting Started
If you haven’t already, you should complete the general
getting-started guide. Once you’ve completed that, you’re ready to get
involved in the
Fedora
Infrastructure Apprentice group.
Fedora Infrastructure Apprentice
The Fedora Infrastructure Apprentice group in the Fedora Account System grants read-only access to many Fedora infrastructure machines. This group is used for new folks to look around at the infrastructure setup, check machines and processes and see where they might like to contribute moving forward. This also allows apprentices to examine and gather info on problems, then propose solutions.
|
Note
This group will be pruned often of inactive folks who miss the monthly email check-in on the infrastructure mailing list. There’s nothing personal in this and you’re welcome to re-join later when you have more time, we just want to make sure the group only has active members. |
Members of the Fedora
Infrastructure Apprentice group have ssh/shell access to many machines,
but no sudo rights or ability to commit to the
Ansible repository (but they do
have read-only access). Apprentice can, however, contribute to the
infrastructure documentation by making a pull request to the
infra-docs repository. Access is via the
bastion.fedoraproject.org machine and from there to each machine. See
the ssh-sop for instructions on how to set up SSH. 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 Ansible
repository. The Ansible repository is hosted on pagure.io at
https://pagure.io/fedora-infra/ansible.git.
Selecting a Ticket
Start by checking out the easyfix tickets. Tickets marked with this tag are a good place for apprentices to learn how things are setup, and also contribute a fix.
Since apprentices do not have commit access to the
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.