3fec5b02eca1d8e2a3fe17735026b6641df958e5
Jesse Pretorius
3fec5b02ec
Move database creation into role
There is no record for why we implement the database creation outside of the role in the playbook, when we could do it inside the role. Implementing it inside the role allows us to reduce the quantity of group_vars duplicated from the role, and allows us to better document the required variables in the role. The delegation can still be done as it is done in the playbook too. In this patch we implement a new variable called 'cloudkitty_db_setup_host' which is used in the role to allow delegation of the database setup task to any host, but defaults to the first member of the galera_all host group. We also document the variable cloudkitty_galera_address which has been used for a long time, but never documented. Change-Id: I7bb3f38556558ef14723361d3672a1d06f839b52
Team and repository tags
OpenStack-Ansible CloudKitty
- tags
-
openstack, cloudkitty, cloud, ansible
- category
-
*nix
This Ansible role installs and configures OpenStack cloudkitty.
- This role will install the following Upstart services:
-
- cloudkitty-api
- cloudkitty-processor
Required Variables
cloudkitty_service_password
cloudkitty_rabbitmq_password
cloudkitty_container_mysql_password
cloudkitty_galera_addressExample Playbook
-name: Install cloudkitty server
hosts: cloudkitty_all
user: root
roles:
-{role:"os_cloudkitty",tags:["os-cloudkitty"]}
vars:
external_lb_vip_address:172.16.24.1
internal_lb_vip_address:192.168.0.1
cloudkitty_galera_address:"{{ internal_lb_vip_address }}"
cloudkitty_container_mysql_password:"SuperSecretePassword1"
cloudkitty_service_password:"SuperSecretePassword2"
cloudkitty_rabbitmq_password:"SuperSecretePassword3"Description
Languages
Python
56.4%
Jinja
43.6%