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 'heat_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 heat_galera_address which
has been used for a long time, but never documented.
Change-Id: I5f3e73af031aad455dbd8555aa054eac804a55bb
In order to make it easier to differentiate between the lists of
python packages, distribution packages, downloaded packages,
package pins and other similar variables the variable names are
being changed to ensure that they have a more explicit suffix
that defines the purpose and makes the naming more consistent.
This is to facilitate a lookup plugin which will be able to look
up all the package lists and present them as a consolidated piece
of data which may be used for artifact preparation.
Change-Id: Iae52d01acd33f6caa91a526f6c19c2ac19161702
The commit changes the heat doc tree to the new structure
we are adopting for each role
Change-Id: I0ea955e3085e965c003af046684bc370b3315b82
Signed-off-by: alextricity25 <miguel.cantu@rackspace.com>
Dmitriy Rabotyagov