Updates the minimum version of Ansible from 2.4 to 2.5, and the maximum
supported version from 2.6 to 2.7.

Change-Id: If8071a9b5c85e5e69fbb333e91c84d10c20d80f3
Story: 2006143
Task: 35639

1. Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.
2. Update some URLs to latest
3. Remove unncessary "=="

Change-Id: Idcb616fd3add4d58f22b91865cec8a54fe492092

Using Kayobe with cliff 2.15.0 fails with the following error:

kayobe playbook run playbook.yml
invalid conflict_resolution value: 'ignore'

This change restricts cliff to <2.15.0.

Also, fix git cloning previous release repos in CI to allow this patch
to merge.

Zuul provides repositories with all branches containing all prospective
changes, not just the current branch. We can use this in the upgrade
jobs to include changes to the previous release branch when a patch
depends on them.

Change-Id: I7966cf33f6133090d83232504b8c1da4c7817e0c
Depends-On: https://review.opendev.org/665703/
Story: 2005891
Task: 33748

If password authentication is not disabled on the server, we may be
prompted for a password if the Kayobe Ansible user doesn't exist or
isn't configured for passwordless authentication.

By using BatchMode, the ssh command can fail quickly and proceed to
create the Kayobe Ansible user using the bootstrap user.

Change-Id: If22ed34dc4b6e87f8cf76c302948c955bddf2bc5

This new version makes the kayobe-tox-molecule job fail with:

    ImportError: cannot import name py31compat

Change-Id: Ieddf039483649cc7b575019409257b6ce5b3fb99

Add information on updating package repos and rebooting after a kernel
update.

Change-Id: If6b637a0fac58ac7564c051e15b86a483b040a34

logstash is required for monasca log transformer

Change-Id: I8da3f80b9bc928997fe087b5abe893a867d46aa8

Change-Id: I00ee10bdc7f8c1b6ab8576115c757e27b6c2c397
Story: 2005809
Task: 33549

Change-Id: I291cabd76d92b661b7609c82f18fe3aeda2c50ae
Story: 2005015
Task: 29493

Kayobe has been using upstream kolla images by default since the Queens
release, as configured by the `kolla_docker_namespace` variable.

Change-Id: Ib56256abbadf0b5f22ef7780af2b9de63a8f157a

Switch all dependencies to use the OpenStack Stein release.

This commit should be reverted on the master branch once the
Kayobe stable/stein branch has been cut and RC1 released.

Change-Id: I50a39994c8ffa0c7d65e026ae765973541423476

Both docs-on-readthedocs and build-openstack-sphinx-docs contain a build
job - a different one: the current openstack-tox-docs and the obsolete
build-openstack-sphinx-docs. Remove the obsolete template and thus
avoid building docs twice for each change.

Change-Id: I358641d29304815eec6c699ae7e20da1e069443d

Change-Id: I793251519a5da0e3d1225673c9b3394e738f4336
Signed-off-by: Radosław Piliszek <radoslaw.piliszek@gmail.com>

Change-Id: I0a2cb770c74b7e4e99a1a411990c6ed488efb303

Uses the support [1] for database backups added to Kolla Ansible in the
Stein release.

Adds the following new commands:

kayobe overcloud database backup [--incremental]
kayobe overcloud database recover [--force-recovery-host <host>]

The recovery command is for recovering a clustered database that has
lost quorum.

[1] https://docs.openstack.org/kolla-ansible/latest/admin/mariadb-backup-and-restore.html

Change-Id: Ie16354cd01ea7dd83cd3d4058dd8451b8387600b
Story: 2005015
Task: 29493

Change-Id: I8005dd608bbaed3fcafcce56fc5dd9c307434a77

Change-Id: I4ddf077913ddc620c60c78ca491e70b2e8f59489

Change-Id: I1f76056254454abe2e4dbc49bdb694a67b464299

This was found not to work, and prevents releases from being made.

The cause of the issue is that the trigger-readthedocs-webhook job (in
project-config) is marked as 'final', meaning that a non-trusted Zuul
config source can't override its variables. Instead, you're supposed to
use the trigger-readthedocs-webhook project template, but only one
instance of this can be instantiated by design.

Let's revert to manually updating the release notes for now.

Change-Id: I271c972c7fdde23085f3026137806bb1e3048e5e

```yaml:frontmatter

1. Gather facts for localhost in kolla-ansible.yml
2. Don't include unconfigured networks in network_interfaces
3. Added Keystone configuration extra config merge

```

1. Facts are necessary for the kolla-ansible role,
which references the ansible_user_uid fact

2. It is possible to skip configuring a network,
by setting its name to None

This is done in networks.yml as follows:

admin_oc_net_name:

Currently, these networks may still be included in the 'network_interfaces'
list for each host, despite the fact that they are not in use.

A classic example is when ironic is not enabled, it is currently still
necessary to define provisioning and cleaning networks.

This change avoids including any networks that have their name set to None
in network_interfaces.

3. Added support for Keystone custom configuration

Added tests and documentation to add support for keystone extra configuration

Co-Authored-By: Mark Goddard <mark@stackhpc.com>

Change-Id: Iaa304221b8093ac71f9cdbb23edc84d1517578da

Change-Id: I2495c97455e40cf1f0573cee6ae845da14d762b5

If running 'kayobe overcloud introspection data save' in an environment
where nodes have been registered in the seed's ironic service manually
(rather than through auto-discovery), previously the bifrost ansible
inventory would not have been populated.

This change ensures the bifrost ansible inventory exists prior to
collecting introspection data.

Change-Id: I2ad53aa0db3bab8db6d6d9de4b00c5dac756fb15

Change-Id: Idf94a64b70d4684a75ec8e8ccc38d64fa6274431

Include information on how to test bare metal instance creation.

Change-Id: Ie40f258a31d4b72cd9867d321a3ff712522daec5