kolla-ansible/ansible/site.yml
Sam Yaple 0007d3325d Properly use groups throught Ansible
Additionally, make each service optional witha config option allowing
for extreme flexibility should the deployer want to replace a service
with a non-kolla one (the database for example).

Change-Id: I7b644da7cfa7e8e6b6878eb1b1aa97db830504ae
Closes-Bug: #1478509
2015-07-30 19:35:33 +00:00

29 lines
810 B
YAML
Executable File

---
- hosts: haproxy
roles:
- { role: haproxy, tags: haproxy, keepalived when: enable_haproxy | bool }
- hosts: mariadb
roles:
- { role: mariadb, tags: mariadb, when: enable_mariadb | bool }
- hosts: rabbitmq
roles:
- { role: rabbitmq, tags: rabbitmq, when: enable_rabbitmq | bool }
- hosts: keystone
roles:
- { role: keystone, tags: keystone, when: enable_keystone | bool }
- hosts: [glance-api, glance-registry]
roles:
- { role: glance, tags: glance, when: enable_glance | bool }
- hosts: [nova-api, nova-conductor, nova-consoleauth, nova-novncproxy, nova-scheduler, compute]
roles:
- { role: nova, tags: nova, when: enable_nova | bool }
- hosts: [neutron-server, neutron-agents, compute]
roles:
- { role: neutron, tags: neutron, when: enable_neutron | bool }