337371f69d
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 'sahara_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 sahara_galera_address which has been used for a long time, but never documented. Change-Id: I594ef44b2943dc9d7a45771bd1e8592595bd0efc
17 lines
563 B
YAML
17 lines
563 B
YAML
- name: Install sahara server
|
|
hosts: sahara_all
|
|
user: root
|
|
roles:
|
|
- { role: "os_sahara", tags: [ "os-sahara" ] }
|
|
vars:
|
|
external_lb_vip_address: 172.16.24.1
|
|
internal_lb_vip_address: 192.168.0.1
|
|
sahara_galera_address: "{{ internal_lb_vip_address }}"
|
|
sahara_container_mysql_password: "SuperSecretePassword1"
|
|
sahara_service_password: "SuperSecretePassword2"
|
|
sahara_rabbitmq_password: "SuperSecretePassword3"
|
|
galera_root_user: root
|
|
vars_prompt:
|
|
- name: "galera_root_password"
|
|
prompt: "What is galera_root_password?"
|