Home Explore Help
Sign In
ffdo-infrastruktur
/
ffdo-ansible
mirror of https://github.com/ffdo/ffdo-ansible.git
5
0
Fork 0
Files

Ansible roles and playbooks to support the Freifunk Dortmund Infrastructure

Tree: 952a314cfc
Branches Tags
ffdo-ansible
ZIP TAR.GZ
Till Klocke 952a314cfc Fixed problem in template of role debops.radvd. Our interface bat0 is not always available as a fact in ansible, therefore the variable ansible_bat0 is then missing 9 years ago
galaxy-roles 952a314cfc Fixed problem in template of role debops.radvd. Our interface bat0 is not always available as a fact in ansible, therefore the variable ansible_bat0 is then missing 9 years ago
roles b4bfc3c37b role supernode-interfaces now also sets sysctl parameters (which is not an optimal solution 9 years ago
test 8d8499de95 ff-supernode role now configures radvd 9 years ago
.gitignore aaee961897 git will now ignore files containing secrets 9 years ago
.kitchen.yml 47b3cdd459 Renamed test suite from fastd to supernode to reflect what it is actually doing 9 years ago
README.md 6d238e7590 Added smal getting started guide to ease others into the development here 9 years ago
Vagrantfile 495fff799b The Vagrantfile can now easily create multiple machines 9 years ago
playbook.yml 3727e147c1 Test playbook now uses the ff-supernode role for testing 9 years ago
requirements.yml 538e896e80 Added role to manage radvd 9 years ago
update-third-party-roles.sh 76e5ef8c47 Added very small script to make updating third party roles more abvious 9 years ago

README.md

Ansible roles for Freifunk Dortmund

This repo contains roles which should ease the creation of supernodes and other services for Freifunk Dortmund (and eventually for other Communities)

Since some software components like fastd and B.A.T.M.A.N. are not always easily available via a packet manager on all platforms, the basic idea in this repo is to create roles for this software and eventually fall back to building from source.

Getting started

This project is based on ansible, vagrant, VirtualBox and test kitchen. Although it is possible to get all this working on windows, it is easier to do on Linux or Mac OS

Prerequesites

  • Install ansible for your operating system
  • Install VirtualBox for your operating system (Version 5 seems to work)
  • Also install the extension pack for USB support etc. in VirtualBox. Some machines depend on this.
  • Install vagrant for your operating system
  • Install test kitchen for your operating system
  • Install ansible for test kitchen: sudo gem install kitchen-ansiblepush kitchen-ansible
  • Install vagrant driver for test kitchen: sudo gem install kitchen-vagrant

First steps

After you installed all necessary tools and gems you change in the checked out directory of this project and simply type kitchen test. This will create multiple virtual machines execute the ansible roles and test everything via serverspec. After all tests are successfull the machines are destroyed again.

Simple development workflow

Since creating the machines can take some time (several minutes) is doesn't make sense to destroy them after each run. You can call kitchen setup to create all defined machines and keep them running. Then you can start editing roles or creating roles and if you want to check your changes you can execute kitchen converge && kitchen verify to execute the roles on all machines and run the serverspec tests on all machines. All commands can be combined with the machine name (available via kitchen list) if you want to manipulate only one machine. If you need to analyse problems on one machine you can login with kitchen login [machine name]

The Vagrantfile

The Vagrantfile and the host and group vars in this repo should be used to quickly create a "test community" in the future.

TODO

  • batman role needs to enable build from source
  • we need a way to get batman compatibility mode as a fact and be able to configure it
  • Add support for more platforms (don't force a linux distro to others)
  • Everything else I forgot
  • Add CI via travis: