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 link:https://pagure.io/fedora-infra/ansible[]

  * Feel free to ask questions when you think of them/run into them, but don't expect everyone to drop what they are doing and answer right then.

  Please be patient.

  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.

  is not.

  * Keep in mind many of the infrastructure folks are busy, so do try and avoid 'pinging' them unless there's a specific need or you know they are

  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.

  == Further information

  For further information on this group, please ask in #fedora-admin on irc.libera.chat, the

  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].

\ No newline at end of file

  = Working with Fedora Infrastructure

  Your close attention to this document will help both you and us

  do the work you are asking us to do.

  a change asap) or is your issue/problem such that you cannot file a ticket

  (authentication, no account, ticketing system down)

    ** If you cannot authenticate to link:https://pagure.io/[], send an email

       to admin@fedoraproject.org

    ** Otherwise: go to next step.

  A few notes:

  * Make sure to note if there is a deadline or if this issue blocks you.

    (one more Europe timezone friendly and one more US timezone friendly).

  * There is no need to ping team members or notify us about the newly filed

    ticket.

  == The "Oncall" Role in Our Team

  When available, this person:

  Please provide as much information as you can in your ticket to avoid

  back and forth for information. If you know your issue is going to

  Make sure your ticket:

  ticket (knowing that you can always re-open it or open a new one if the issue

  persists or re-appeared).

  directly. Instead, update your ticket with any new information you have and

  when the team member(s) working on that issue have time/availability, they

  == Direct emails

  items, and require facilities (e.g. dovecots) that most team members do not

  have. Even if the oncall member does have a free dovecot, feed, and is trained

  in handling carrier pigeons, sending a pigeon to a single team member has the

  are still the correct way to report problems.

  In other words, please don't send us any birds.

  ** 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:

  **** 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

  issues for one that is of interest.

  ** 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

  *** Watch link:http://fedoramagazine.org/?p=642[some videos] intended to introduce new contributors to

  the team.

  section] you should:

  * Regularly attend the link:https://fedoraproject.org/wiki/Infrastructure/Meetings[Weekly Meetings]

  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 link:[services]https://docs.fedoraproject.org/en-US/infra/map_critical_services/

  the Fedora Infrastructure Group develops, deploys and maintains.

  * 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.

  If you don't have the time to be involved on a regular basis at this point, please feel free to watch over

  things and report bugs and RFEs as you see fit. Showing interest now is a great way to make it easier to

  == How the team works

  The Fedora Infrastructure Group consists of volunteers and Red Hat employees. Our preferred

  We try to be as transparent as possible and default to open.

  or people are busy we are happy to try and explain how something is setup or works.

  The team is a meritocracy, which means those people who solve issues and do work are given more privileges over time. In

  * Infrastructure Lead   - Kevin Fenzi

  * Development Manager   - Aurelien Bompard

  * Quality Engineering   - Adam Williamson

  The officers generally decide what needs to be done in the day to day operations

  of the various Fedora infrastructure facilities. The officers themselves work

  and fix things but if we refuse for whatever reason, the final decision can be

  made by the Fedora Project Council. Such decisions, however, are rare.

  == Communicating

  The Infrastructure Team coordinates their activities using a variety of tools.

  #admin:fedoraproject.org and the discussion.fedoraproject.org with the #infra-team tag.

  Application development efforts take place in the #apps:fedoraproject.org Matrix room,

  === Meetings

  See the UTC Howto for instructions to convert UTC to your local time.

  See the meetings page for details and historical archives.

  existing pages.

  Notifications https://apps.fedoraproject.org/notifications[apps.fp.o/notifications]::

  +

  * https://github.com/fedora-infra/fmn[Sources]

  * https://fmn.readthedocs.io/en/stable/[Documentation]

  * https://docs.mailman3.org/projects/hyperkitty/en/latest/[Documentation]

  Meetbot https://meetbot.fedoraproject.org/[meetbot.fp.o]::

  https://fedoraproject.org/wiki/Zodbot[zodbot]. Among its many and varied

  +

  * https://github.com/fedora-infra/mote[Sources]

  * Have a clear schedule of reachable hours.

  * Set and take regular vacation time to be rested.

  * If adding a new service, be available outside of normal business hours to

    help debug problems.

  * Follow procedures and checklists when adding or updating services.

  Owner::

    <usually, Fedora Infrastructure Team>

  Contact::

  Location::

    <Relevant URIs, etc>

  Servers::

  [[releng-contact-info]]

  === Contact Information

  * Mailing List: https://admin.fedoraproject.org/mailman/listinfo/rel-eng[rel-eng@lists.fedoraproject.org]

  * Issue tracker: https://pagure.io/releng/new_issue[Fedora Releng Pagure Tickets]

  === Fedora Release Engineering Leadership

  Leadership is currently appointed by FESCo with input from the current

  release team.

  [[join-releng]]

  === Joining Release Engineering

  initially get involved is to attend one of the meetings and say that

  you're interested in doing some work during the open floor at the end of

  the meeting. If you can't make the meeting times, you can also ping one

  https://admin.fedoraproject.org/mailman/listinfo/rel-eng[mailing list].

  Since release engineering needs special access to systems essential to

  === Meetings

  * https://pagure.io/releng/issues?status=Open&tags=meeting[Meeting

  agendas] are created from open tickets in pagure that contain the

  *** A mail about the changes is sent to _sysadmin-members_.

  *** The changes are announced on the message bus, which in turn triggers

  You can check out the repo locally on _batcave01_ with:

  == Internal Contacts

  If we need to contact someone from the RH internal "unified messagebus"

  At this point, you can push the change out to production and be

  publishing messages "okay". Everything should be fine.

  _FMN_, and everywhere else we try to render it. You _must_ then follow up

  and write a new _Processor_ for it in the _fedmsg_meta_

  library we maintain:

  ____

  * #fedora-apps for FMN development

  * #fedora-admin for problems with the deployment of FMN

  * #fedora-noc for outage/crisis alerts

  ____

  saying the request has been received. There is a 'quick response' in the

  pagure issue tracker to note this.

  . Login to FAS and clear the `Telephone number` entry, set Country to

  `GPG Key ID` and set `Time Zone` to UTC and `Locale` to `en` and set the

  user status to `disabled`. If the user is not in cla_done plus one

  group, you are done. Update the ticket and close it. This step will be

  $ git checkout -b develop

  $ git push --all

  ....

  == Add an EasyFix label

  github2fedmsg is a small Python Pyramid app that bridges github events

  onto our fedmsg bus by way of github's "webhooks" feature. It is what

  has two phases of operation:

  * Infrequently, a user will log in to github2fedmsg via Fedora OpenID.

  = mote SOP

  mote is a MeetBot log wrangler, providing an user-friendly interface for

  Production instance: http://meetbot.fedoraproject.org/ Staging instance:

  http://meetbot.stg.fedoraproject.org

  Location::

    Fedora Infrastructure

  Purpose::

  == Deployment

  mote is a Python webapp running on Flask with mod_wsgi. It can be used

  to view past logs, browse meeting minutes, or glean other information

  in addition to a memcached store which is currently not in use with

  Fedora infrastructure.

  disagree with someone, even if you're new and they're an old timer. Just

  make sure you ask yourself what is important to you and make sure to

  provide data, we like that. We generally communicate on libera.chat

  quickest way to get in touch with everyone. Secondary to that we use the

  mailing list. After that it's our ticketing system and

  talk.fedoraproject.org.

  outage (see xref:status-fedora.adoc[status-fedora SOP]).

  Report all information in #fedora-admin. Coordination is extremely

  real-time communication device. If a web site is out please put up some

  sort of outage page in its place.

  Once a sponsor is aquired and all needed packages have been packaged and

  are available in EPEL, we move on to the planning phase. In this phase

  discussion should take place about the application/resource on the

  deployed should be considered:

  * Should the resource be load balanced?