Ansible roles

These Ansible roles are simple in style and work well together on many distributions and many Ansible version.

Integration tests

A weekly test to verify if roles work well together.

Build Status ARA report.

Unit tests

A monthly test to see of the role still works on the current distributions. Some roles contain a version that requires frequent changes and tests.

#Role nameBuild statusVersionIssuesPull requests
1alternatives
2anaconda
3ansible
4ansible_lint
5apt_autostart
6ara
7artifactory
8at
9atom
10auditd
11awx
12backup
13bios_update
14bootstrap
15buildtools
16ca
17ca_certificates
18cargo
19clamav
20cloud9
21cntlm
22common
23container_docs
24core_dependencies
25cron
26debug
27dhcpd
28digitalocean-agent
29dns
30docker
31docker_ce
32dovecot
33dsvpn
34earlyoom
35environment
36epel
37etherpad
38fail2ban
39firewall
40git
41gitlab_runner
42glusterfs
43go
44gotop
45haproxy
46haveged
47hostname
48httpd
49investigate
50irslackd
51java
52jenkins
53kernel
54kubectl
55locale
56logrotate
57logwatch
58lynis
59mediawiki
60memcached
61minikube
62mitogen
63molecule
64mssql
65mysql
66natrouter
67nginx
68npm
69ntp
70obsproject
71omsagent
72openssh
73openvas
74openvpn
75owncloud
76packer
77php
78php_fpm
79phpmyadmin
80postfix
81postgres
82powertop
83python_pip
84reboot
85redis
86release
87remi
88restore
89revealmd
90roundcubemail
91rpmfusion
92rsyslog
93ruby
94rundeck
95scl
96selinux
97service
98snort
99sosreport
100spamassassin
101squid
102storage
103stratis
104subversion
105sudo-pair
106sysctl
107sysstat
108terraform
109tftpd
110tomcat
111travis
112ulimit
113update
114update_package_cache
115users
116vagrant
117xinetd
118y
119zabbix
120zabbix_agent
121zabbix_proxy
122zabbix_repository
123zabbix_server
124zabbix_web
-skeletonnot tested

Dependencies

Most roles have a “soft dependency” described in requirements.yml. You can choose to use those roles if you like them. Here is an overview of these soft dependencies.

Overview of dependencies

The dependencies are soft for these reasons:

Because these dependecies are loose, you have to include them in your playbook yourself:

- name: make the best machine ever
  hosts: all
  become: yes

  roles:
    - role: robertdebock.bootstrap
    - role: robertdebock.java
    - role: robertdebock.tomcat

Some roles have a hard dependecies” on another role, mainy for a shared handler or variables set in the parent role, used in the child role. More details on how to use these roles. These hard dependencies are describe in meta/main.yml under dependencies.

Role Depends on Reason
ca httpd inherited variable
common reboot A reboot is used in tasks/main.yml with include_role.
openvpn selinux SELinux is configured in tasks/main.yml with include_role.
openvpn ca OpenSSL keys are created in tasks/main.yml with include_role.
php httpd handler
phpmyadmin httpd handler
roundcubemail httpd handler
selinux reboot A reboot is used in tasks/main.yml with include_role.
spamassassin rsyslog handler
tftpd xinetd handler
update reboot A reboot is used in tasks/main.yml with include_role.
zabbix httpd handler & inherited variable

Here is an overview of the hard dependencies:

Overview of hard dependencies

Tests

Unit tests and integration tests are use to verify the quality of the roles, read more about testing

Distributions

The goal is to let all Ansible roles work on as many distributions as possible, but this is sometimes not possible. For each distribution, the current and previous release is tested. A role may work on diferent distributions, like Red Hat Enterprise Linux (RHEL), but it’s not tested against it. By default these Linux distributions are included in the tests:

Distribution Version(s)
Archlinux latest
Alpine latest & edge*
CentOS 7 & latest
Debian stable & unstable*
Fedora latest & rawhide*
OpenSUSE leap & tumbleweed
Ubuntu latest, devel* & rolling

Ansible version

The goal is to let all roles work on these Ansible version:

See errors? Please help and make a merge request on git.