Document how to use the utility container for service setup

If the service setup host has been set to the utility container, the python
interpreter needs to be set to the venv rather than the system otherwise the
shade/openstacksdk library will not be found.

In this patch we add a commented set of overrides into user_variables.yml
as a convenience for users as this will be a relatively common requirement.

Depends-On: https://review.openstack.org/620644
Depends-On: https://review.openstack.org/621173
Depends-On: https://review.openstack.org/621171
Depends-On: https://review.openstack.org/621175
Depends-On: https://review.openstack.org/621202
Depends-On: https://review.openstack.org/621178
Change-Id: I16f5145f5d64ebe757ede8b4efeda2ffea5957ca
This commit is contained in:
Jesse Pretorius 2018-11-28 16:16:00 +00:00
parent 89b5b43883
commit e29bc2203f
1 changed files with 12 additions and 0 deletions

View File

@ -21,6 +21,18 @@
## Debug and Verbose options.
debug: false
## Set the service setup host
# The default is to use localhost (the deploy host where ansible runs),
# but any other host can be used. If using an alternative host with all
# required libraries in a venv (eg: the utility container) then the
# python interpreter needs to be set. If it is not, the default is to
# the system python interpreter.
# If you wish to use the first utility container in the inventory for
# all service setup tasks, uncomment the following.
#
#openstack_service_setup_host: "{{ groups['utility_all'][0] }}"
#openstack_service_setup_host_python_interpreter: "/openstack/venvs/utility-{{ openstack_release }}/bin/python"
## Installation method for OpenStack services
# Default option (source) is to install the OpenStack services using PIP
# packages. An alternative method (distro) is to use the distribution cloud