Jesse Pretorius 19f299854e Move MQ vhost/user creation into role ... There is no record for why we implement the MQ vhost/user 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 two new variables: - cloudkitty_oslomsg_rpc_setup_host - cloudkitty_oslomsg_notify_setup_host These are used in the role to allow delegation of the MQ vhost/user setup for each type to any host, but they default to using the first member of the applicable oslomsg host group. We also adjust some of the defaults to automatically inherit existing vars set in group_vars form the integrated build so that we do not need to do the wiring in the integrated build's group vars. We still default them in the role too for independent role usage. Finally, we remove the test mq setup tasks and clean up any unused or unnecessary variables configured in tests. Change-Id: Iac217b80df3da79a944185a90ba4c1ff5409945b		2018-07-31 08:31:19 +01:00
..
main.yml	Move MQ vhost/user creation into role	2018-07-31 08:31:19 +01:00