Due to the playbooks provided by the project considered “read only” to make updates easier, it's a good idea to pick good host definition in the hosts variable of each playbook. Since there are many playbooks, synchronization is a must.

Here you can find names of the host groups used by DebOps. This list is not yet used by the project, right now it's just a proposal which might be implemented.

These host groups are expected to be in all Ansible inventories.

This host group contains all hosts in the inventory managed by DebOps.

Each playbook related to a service managed by DebOps has its own host group (some playbooks will be executed on all DebOps hosts). This should help prevent installing and configuring services on wrong hosts.

These are example Ansible inventories which can be used with DebOps playbooks.

[debops_all_hosts]
alpha.example.org
beta.example.org
other.example.org

[debops_all_hosts:children]
new-york
london
 
[new-york]
ec2-host1 ansible_ssh_host=ec2-ip1.amazon.com
ec2-host2 ansible_ssh_host=ec2-ip2.amazon.com
 
[london]
do-host1 ansible_ssh_host=do-ip1.digitalocean.com
do-host2 ansible_ssh_host=do-ip2.digitalocean.com

[debops_all_hosts]
control.example.org ansible_connection=local
other.example.org