Change-Id: Idf1e7b1e7018d1324326c3b8b8cb04f2e27ee0d2

Connections default to 'public' interface when attempting to run
openstack commands.  This breaks setups where the network hosts are
separate from the controllers.

This change adds an ``openstack_interface`` variable to select the
correct endpoint to use, which defaults to ``internal``.

Co-Authored-By: Michael Senizaiz <michael@r-hpc.com>

Change-Id: Ifa766d2cc3ed7077f03c571398072ad5117701c6
Story: 2006814
Task: 37374

Hopefully this provides access to relevant information without breaking
the flow.

Change-Id: I40b71cdf782dda6971dafb5894670c30e446ccb0
Story: 2004337
Task: 37387

Diskimage builder supports specifying a list of packages to install via
-p. We currently support this for the root image, but not IPA images.

This change adds a new configuration option, 'ipa_build_dib_packages',
that should be a list of additional packages to install in locally built
IPA images. This affects the following commands:

kayobe seed deployment image build
kayobe overcloud deployment image build

This depends on
https://github.com/stackhpc/ansible-role-os-images/pull/25.

Also adds an example to the documentation for the equivalent option for
root image.

Change-Id: I04191d9541894b6a264e966c9ecb1056e0edade4
Story: 2006855
Task: 37446

The kolla-ansible CLI now requires the kolla_ansible python module to be
importable. We need to activate the virtualenv to make this work.

Change-Id: I43d4761409df3eea146dc7ff16b4c8d80855a91b

Kolla ansible now uses the correct path when templating admin-openrc.sh.

Change-Id: I2a38c91811ea5976c0065f6f28a85c3d911e9e9d

We no longer need to cd to the kayobe repo path, since all tested
versions of kayobe support pip installation.

Change-Id: Id7b574cbc6bb5195eee16cfc8443075712ce3254

Ideally we will fix these issues, but documenting them is a good first
step.

Change-Id: I9a840005d62b974f0681ac39e1ff02ae3ff0120e
Story: 2004967
Task: 29410

Also reorder upgrade documentation to make it clear that configuration
migration is something that should be done as a preparatory task.

Change-Id: I97ada3c6fd94a9ab7b5add97e90717f2a56bc8f3
Story: 2006677
Task: 36953

Depends-On: https://review.opendev.org/690559/

Change-Id: I4e766424607317e5817d26461f7a1e180e9b2146
Story: 2004337
Task: 37378
Task: 37381

This variable is mentioned in "Host Configuration" but was missing from
the Docker extra-vars file.

Change-Id: I22cf878c99824372adc17582f9bbba2db98b3eb0

If the kayobe overcloud provision command is executed with overcloud
ironic nodes without names, cloud-init will fail with the following
Traceback when the deployed image boots:

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 447, in find_source
    if s.get_data():
  File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 132, in get_data
    self._get_standardized_metadata())
  File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 110, in _get_standardized_metadata
    'local-hostname': self.get_hostname(),
  File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 317, in get_hostname
    if util.is_ipv4(lhost):
  File "/usr/lib/python2.7/site-packages/cloudinit/util.py", line 544, in is_ipv4
    toks = instr.split('.')

This is a bug [1] in cloud-init. The symptom is that hosts provision
successfully, but are not accessible via SSH. A solution is to ensure
that all nodes are named.

Until we have a release of CentOS with the cloud-init fix included, we
should at least mention this limitation in our documentation.

[1] https://bugs.launchpad.net/cloud-init/+bug/1852100

Change-Id: If54f56fb9f0b626d9fae80db622b0feeae5464b9
Story: 2006832
Task: 37405

Add a note to base customised inventory on a kayobe kolla-ansible
inventory template.

Change-Id: I75ace6878d36cb523c38a33daa9eecd62826fe43

Change-Id: I5a1bebf1f8b4f96fc593afde8d224073916a704d