You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Stephen Smoogen b72c46c607 according to iteritmes is not in python3. changing old items 3 weeks ago
callback_plugins callback_plugins: try and run a simple 2to3 over the logdetail plugin 4 weeks ago
ci Zuul: Verify that local jobs are namespaced 1 month ago
files iad2: For some reason python3 ansible catches this. Cast FedoraBranchedNUmber to int here. 1 month ago
filter_plugins filter_plugins/fedmsg: make the filter work with python3 1 month ago
handlers chrony: add handler to restart on config changes 1 month ago
inventory clean up download usage 3 weeks ago
library Spring cleaning time. :) 1 month ago
playbooks clean up download usage 3 weeks ago
roles according to iteritmes is not in python3. changing old items 3 weeks ago
scripts Start porting vhost-info to python3 3 weeks ago
tasks iad2: adjust a bunch of things that were delegating directly to phx2 hosts 1 month ago
vars move the standard workers down to 256 2 months ago
.gitignore [release-monitoring] Add librariesio consumer 2 months ago
.mailmap Add a .mailmap to map all my commits to one author in git shortlog. This is purely for my sanity, but also demonstrates how someone else could do similarly if needed. 1 year ago
.zuul.yaml Zuul: use correctly namespaced parent job name 1 month ago
CONVENTIONS conventions: you guessed it, another whitespace change 2 months ago
README Convert README to a symlink to 2 months ago README: Clean out some old cgit paths. 4 weeks ago
STYLEGUIDE style: add initial style guide 1 year ago
master.yml inventory/master: Clean up master and drop a bunch of old playbooks for things we no longer have. 1 month ago

Fedora Infrastructure

Welcome! This is the Fedora Infrastructure Ansible Pagure project.

This repository is also mirrored for production runs to

If you would like to help out with Fedora Infrastructure, see:

Ansible repository/structure

files - files and templates for use in playbooks/tasks
      - subdirs for specific tasks/dirs highly recommended

inventory - where the inventory and additional vars is stored
          - All files in this directory in ini format
          - added together for total inventory
          - per group variables set here in a file per group
          - per host variables set here in a file per host

library - library of custom local ansible modules

playbooks - collections of plays we want to run on systems

  groups: groups of hosts configured from one playbook.

  hosts: playbooks for single hosts.

  manual: playbooks that are only run manually by an admin as needed.

tasks - snippets of tasks that should be included in plays

roles - specific roles to be use in playbooks.
        Each role has it's own files/templates/vars

filter_plugins - Jinja filters

master.yml - This is the master playbook, consisting of all
             current group and host playbooks. Note that the
             daily cron doesn't run this, it runs even over
             playbooks that are not yet included in master.
             This playbook is usefull for making changes over
             multiple groups/hosts usually with -t (tag).


The public path for everything is /srv/web/infra/ansible

The private path (which is sysadmin-main accessible only) is /srv/private/ansible

In general to run any ansible playbook you will want to run:

sudo -i ansible-playbook /path/to/playbook.yml

Scheduled check-diff

Every night a cron job runs over all playbooks under playbooks/{groups}{hosts}
with ansible --check --diff. A report from this is sent to sysadmin-logs.
In the ideal state this report would be empty.


All playbooks should be idempotent. Ie, if run once they should bring the
machine(s) to the desired state, and if run again N times after that they should
make 0 changes (because the machine(s) are in the desired state).
Please make sure your playbooks are idempotent.

Can be run anytime

When a playbook or change is checked into ansible you should assume
that it could be run at ANY TIME. Always make sure the checked in state
is the desired state. Always test changes when they land so they don’t
surprise you later.