Document how to access all OSA group_vars
Some of the variables used the templates are in the OSA group_vars, or are composed using other variables from group_vars. These are not accessible using the embedded ansible. In addition, a deployer may have referenced group_vars in user_variables. Adding the whole OSA group vars tree via a symlink covers all of these cases. Change-Id: I7c842b0d41f24e7c192ab196eb2cfc133bb548a5
This commit is contained in:
1 changed files with 11 additions and 1 deletions
@@ -317,7 +317,8 @@ deploy logstash, deploy Kibana, and then deploy all of the service beats.
* The `openstack-ansible` command can be used if the version of ansible on the
system is greater than **2.5**.
system is greater than **2.5**. This will automatically pick up the necessary
group_vars for hosts in an OSA deployment.
* If required add ``-e@/opt/openstack-ansible/inventory/group_vars/all/all.yml``
to import sufficient OSA group variables to define the OpenStack release.
@@ -325,6 +326,15 @@ deploy logstash, deploy Kibana, and then deploy all of the service beats.
Rocky, and hosts only for Rocky onwards. If the variable ``openstack_release``
is undefined the default behaviour is to deploy Journalbeat to hosts only.
* Alternatively if using the embedded ansible, create a symlink to include all
of the OSA group_vars. These are not available by default with the embedded
ansible and can be symlinked into the ops repo.
.. code-block:: bash
ln -s /opt/openstack-ansible/inventory/group_vars /opt/openstack-ansible-ops/elk_metrics_6x/group_vars
The individual playbooks found within this repository can be independently run
at anytime.
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.