Skip to content

Playbooks

This document lists all playbooks and the roles they call. Skip variables allow you to disable specific roles or dependencies within a playbook. Set them to true in your inventory to skip the corresponding role.

All skip variables are booleans and default to false unless noted otherwise.

For playbooks with role injections (typically setup_* playbooks), two types of skip variables are available:

  • playbook__role__skip_role: Skips the role entirely and disables its injections into other roles.
  • playbook__role__skip_injections: Only disables the injections, the role itself still runs.

See the main README for details.

acme_sh.yml

Calls the following roles (in order):

aide.yml

Calls the following roles (in order):

alternatives.yml

Calls the following roles (in order):

ansible_init.yml

Calls the following roles (in order):

apache_httpd.yml

Calls the following roles (in order):

apache_solr.yml

Calls the following roles (in order):

apache_tomcat.yml

Calls the following roles (in order):

apps.yml

Calls the following roles (in order):

at.yml

Calls the following roles (in order):

audit.yml

Calls the following roles (in order):

bind.yml

Calls the following roles (in order):

blocky.yml

Calls the following roles (in order):

bootloader.yml

Calls the following roles (in order):

borg_local.yml

Calls the following roles (in order):

chromium_headless.yml

Calls the following roles (in order):

chrony.yml

Calls the following roles (in order):

clamav.yml

Calls the following roles (in order):

cloud_init.yml

Calls the following roles (in order):

cockpit.yml

Calls the following roles (in order):

collabora.yml

Calls the following roles (in order):

collect_rpmnew_rpmsave.yml

Calls the following roles (in order):

core_dumps.yml

Calls the following roles (in order):

coturn.yml

Calls the following roles (in order):

crypto_policy.yml

Calls the following roles (in order):

dnf_makecache.yml

Calls the following roles (in order):

dnf_versionlock.yml

Calls the following roles (in order):

docker.yml

Calls the following roles (in order):

duplicity.yml

Calls the following roles (in order):

elastic_agent.yml

Calls the following roles (in order):

elastic_agent_fleet_server.yml

Calls the following roles (in order):

elasticsearch.yml

Calls the following roles (in order):

exoscale_vm.yml

Calls the following roles (in order):

fail2ban.yml

Calls the following roles (in order):

fangfrisch.yml

Calls the following roles (in order):

ffmpeg.yml

Calls the following roles (in order):

files.yml

Calls the following roles (in order):

firewall.yml

Calls the following roles (in order):

freeipa_client.yml

Calls the following roles (in order):

freeipa_server.yml

Calls the following roles (in order):

github_project_createrepo.yml

Calls the following roles (in order):

gitlab_ce.yml

Calls the following roles (in order):

glances.yml

Calls the following roles (in order):

glpi_agent.yml

Calls the following roles (in order):

grafana.yml

Calls the following roles (in order):

grafana_grizzly.yml

Calls the following roles (in order):

haveged.yml

Calls the following roles (in order):

hetzner_vm.yml

Calls the following roles (in order):

hostname.yml

Calls the following roles (in order):

icinga2_agent.yml

Calls the following roles (in order):

icingaweb2.yml

Calls the following roles (in order):

icingaweb2_module_businessprocess.yml

Calls the following roles (in order):

icingaweb2_module_company.yml

Calls the following roles (in order):

icingaweb2_module_director.yml

Calls the following roles (in order):

icingaweb2_module_doc.yml

Calls the following roles (in order):

icingaweb2_module_incubator.yml

Calls the following roles (in order):

icingaweb2_module_pdfexport.yml

Calls the following roles (in order):

influxdb.yml

Calls the following roles (in order):

infomaniak_vm.yml

Calls the following roles (in order):

kdump.yml

Calls the following roles (in order):

keepalived.yml

Calls the following roles (in order):

kernel_modules.yml

Calls the following roles (in order):

kernel_settings.yml

Calls the following roles (in order):

kibana.yml

Calls the following roles (in order):

kvm_host.yml

Calls the following roles (in order):

libmaxminddb.yml

Calls the following roles (in order):

libreoffice.yml

Calls the following roles (in order):

login.yml

Calls the following roles (in order):

logrotate.yml

Calls the following roles (in order):

logstash.yml

Calls the following roles (in order):

lvm.yml

Calls the following roles (in order):

lynis.yml

Calls the following roles (in order):

mailto_root.yml

Calls the following roles (in order):

mailx.yml

Calls the following roles (in order):

mariadb_server.yml

Calls the following roles (in order):

matomo_import_logs.yml

Calls the following roles (in order):

maxmind_geoip.yml

Calls the following roles (in order):

mirror.yml

Calls the following roles (in order):

mod_maxminddb.yml

Calls the following roles (in order):

mongodb.yml

Calls the following roles (in order):

monitoring_plugins.yml

Calls the following roles (in order):

monitoring_plugins_grafana_dashboards.yml

Calls the following roles (in order):

motd.yml

Calls the following roles (in order):

mount.yml

Calls the following roles (in order):

network.yml

Calls the following roles (in order):

nfs_client.yml

Calls the following roles (in order):

nfs_server.yml

Calls the following roles (in order):

nodejs.yml

Calls the following roles (in order):

open_vm_tools.yml

Calls the following roles (in order):

opensearch.yml

Calls the following roles (in order):

openvpn_server.yml

Calls the following roles (in order):

php.yml

Calls the following roles (in order):

podman_containers.yml

Calls the following roles (in order):

policycoreutils.yml

Calls the following roles (in order):

postfix.yml

Calls the following roles (in order):

postgresql_server.yml

Calls the following roles (in order):

proxysql.yml

Calls the following roles (in order):

python.yml

Calls the following roles (in order):

python_venv.yml

Calls the following roles (in order):

qemu_guest_agent.yml

Calls the following roles (in order):

r.yml

Calls the following roles (in order):

redis.yml

Calls the following roles (in order):

repo_baseos.yml

Calls the following roles (in order):

repo_collabora.yml

Calls the following roles (in order):

repo_collabora_code.yml

Calls the following roles (in order):

repo_debian_base.yml

Calls the following roles (in order):

repo_docker.yml

Calls the following roles (in order):

repo_elasticsearch.yml

Calls the following roles (in order):

repo_epel.yml

Calls the following roles (in order):

repo_gitlab_ce.yml

Calls the following roles (in order):

repo_gitlab_runner.yml

Calls the following roles (in order):

repo_grafana.yml

Calls the following roles (in order):

repo_graylog.yml

Calls the following roles (in order):

repo_icinga.yml

Calls the following roles (in order):

repo_influxdb.yml

Calls the following roles (in order):

repo_mariadb.yml

Calls the following roles (in order):

repo_mongodb.yml

Calls the following roles (in order):

repo_monitoring_plugins.yml

Calls the following roles (in order):

repo_mydumper.yml

Calls the following roles (in order):

repo_opensearch.yml

Calls the following roles (in order):

repo_openvpn.yml

Calls the following roles (in order):

repo_postgresql.yml

Calls the following roles (in order):

repo_proxysql.yml

Calls the following roles (in order):

repo_redis.yml

Calls the following roles (in order):

repo_remi.yml

Calls the following roles (in order):

repo_rpmfusion.yml

Calls the following roles (in order):

repo_sury.yml

Calls the following roles (in order):

rstudio_server.yml

Calls the following roles (in order):

rsyslog.yml

Calls the following roles (in order):

schedule_reboot.yml

Calls the following roles (in order):

selinux.yml

Calls the following roles (in order):

setup_basic.yml

Before the first role changes the host, the playbook validates the variables of every role it runs, checks that the Firewall Builder repository has a compiled firewall for the host, and that the Icinga2 master is reachable. A missing prerequisite aborts the run there, while the host is still reachable with the bootstrap user.

Calls the following roles (in order):

setup_grav.yml

Calls the following roles (in order):

setup_graylog_datanode.yml

Calls the following roles (in order):

setup_graylog_server.yml

Calls the following roles (in order):

setup_icinga2_master.yml

Calls the following roles (in order):

setup_keycloak.yml

Calls the following roles (in order):

setup_librenms.yml

Calls the following roles (in order):

setup_mastodon.yml

Calls the following roles (in order):

setup_moodle.yml

Calls the following roles (in order):

setup_nextcloud.yml

Calls the following roles (in order):

setup_rocketchat.yml

Calls the following roles (in order):

setup_shiny_server.yml

Calls the following roles (in order):

setup_wordpress.yml

Calls the following roles (in order):

shell.yml

Calls the following roles (in order):

snmp.yml

Calls the following roles (in order):

squid.yml

Calls the following roles (in order):

sshd.yml

Calls the following roles (in order):

system_update.yml

Calls the following roles (in order):

systemd_journald.yml

Calls the following roles (in order):

systemd_unit.yml

Calls the following roles (in order):

telegraf.yml

Calls the following roles (in order):

timezone.yml

Calls the following roles (in order):

tmux.yml

Calls the following roles (in order):

tools.yml

Calls the following roles (in order):

trend_micro_v1es.yml

Calls the following roles (in order):

unattended_upgrades.yml

Calls the following roles (in order):

valkey.yml

Calls the following roles (in order):

vsftpd.yml

Calls the following roles (in order):

yum_utils.yml

Calls the following roles (in order):