Skip to content

Latest commit

 

History

History
64 lines (44 loc) · 3.25 KB

README.md

File metadata and controls

64 lines (44 loc) · 3.25 KB

Freifunk Berlin Ansible Repository

This repository currently contains our WIP state for the infrastructure code.

This is a replacement for the old puppet repository.

Keep in mind that we also use ansible to configure the BerlinBackBone, this is done in the bbb-configs repository.

The code is, where necessary, quite debian centric since that's the distribution we use in our infrastructure.

The repository also uses a monorepo structure since all the custom roles are only used in this context.

Managed Infrastructure

This repository currently manages these services:

Requirements

Structure

We follow an adapted version of the ansible alternative layout. Where we put the inventory in an extra directory, but don't use different directories for the stages (Since we don't have any). Also, the roles are divided into 2 directories, one for external ones, and one for our internal ones.

This separation makes using the monorepo approach easier, since we can just exclude all directories in the .gitignore.

├── .config                      # Directory with config files e.g. for github actions
├── .github                      # Directory for github actions
├── ansible.cfg                  # Custom settings for this Repository
├── external_roles               # Placeholder directory for external roles installed through ansible-galaxy
├── files                        # Directory for extra files used on the host
├── inventory                    # Directory for our inventory
├── play.yml                     # The single playbook
├── README.md                    # This Readme
├── requirements.yml             # The dependencies to be used with *ansible-galaxy*
├── roles                        # Directory self developed Roles
├── templates                    # Directory for template files
└── Vagrantfile                  # A Vagrant file to run test machines with Vagrant

Tutorials

We provide step by step tutorials for some common workflows in Tutorials.md.

How to contribute

If you want to help us, you are very welcome.

The easiest way is to ask @akira or @rtznprmpftl in our matrix chatroom.

Alternatively you can use the GitHub bugtracker, if you discover any issues on the infrastructure side.