36ec620afd
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 'horizon_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 horizon_galera_address which has been used for a long time, but never documented. Change-Id: I7946c325d87c74e2bd9b1dcc1f92ea09a5386729 |
||
|---|---|---|
| .. | ||
| horizon_apache.yml | ||
| horizon_db_setup.yml | ||
| horizon_install.yml | ||
| horizon_post_install.yml | ||
| horizon_pre_install.yml | ||
| horizon_service_setup.yml | ||
| horizon_ssl_key_create.yml | ||
| horizon_ssl_key_distribute.yml | ||
| horizon_ssl_key_store.yml | ||
| horizon_ssl_self_signed.yml | ||
| horizon_ssl_user_provided.yml | ||
| horizon_translations_update.yml | ||
| main.yml | ||