ansible-infra/inventories/z9/hosts.yaml

all:
  children:
    debian_11:
      hosts:
        light:
          ansible_host: light.z9.ccchh.net
          ansible_user: chaos
        authoritative-dns:
          ansible_host: authoritative-dns.z9.ccchh.net
          ansible_user: chaos
    debian_12:
      hosts:
    nginx_hosts:
      hosts:
        light:
    ola_hosts:
      hosts:
        light:
    foobazdmx_hosts:
      hosts:
        light:
    infrastructure_authorized_keys_hosts:
      hosts:
        light:
        authoritative-dns:
Add ola and foobazdmx role and add playbook for light.z9 2022-11-11 14:10:43 +01:00			`all:`
			`children:`
			`debian_11:`
			`hosts:`
			`light:`
Use new seach domain for hosts FQDN 2023-01-07 18:29:45 +01:00			`ansible_host: light.z9.ccchh.net`
Use chaos user as ansible user for VMs 2023-05-09 22:33:54 +02:00			`ansible_user: chaos`
Add authoritative-dns to `hosts.yml` 2023-04-27 23:58:23 +02:00			`authoritative-dns:`
			`ansible_host: authoritative-dns.z9.ccchh.net`
			`ansible_user: chaos`
Move keycloak and public-reverse-proxy to new debian_12 group Do this, since they are on Debian 12. 2023-07-30 05:53:39 +02:00			`debian_12:`
			`hosts:`
Combine playbooks for indiviual hosts into one playbook This makes a full deployment of all hosts easier and parallelises execution of roles, which are used for multiple hosts. You can still easily deploy only a subset of hosts using the -l flag for ansible-playbook. 2023-07-30 06:57:30 +02:00			`nginx_hosts:`
			`hosts:`
			`light:`
			`ola_hosts:`
			`hosts:`
			`light:`
			`foobazdmx_hosts:`
			`hosts:`
			`light:`
Add a role for deploying infrastructure authorized keys and use it 2023-11-11 00:23:20 +01:00			`infrastructure_authorized_keys_hosts:`
			`hosts:`
			`light:`
			`authoritative-dns:`