Adds a flag ``kolla-ansible octavia-certificates --check-expiry <days>``
to the ``octavia-certificates`` command to check if the certificates
will expire within a given number of days.

Change-Id: I869b8afd85fe282d823ecf3593aa22f94a61b2a0

This reverts commit 9867060b.

Reason for revert: seems this broke some jobs

Change-Id: I1ca81214ece403351c0a522ea05bf07802e4c4c0

Change-Id: Ibc9cc91f64b0450de3cae6e2830b4ff2c52c0395

Make sure to actually test IPv6 connectivity to our test instance in the
IPv6 jobs.

Change-Id: I7845448804e191af356e82f8ad33c563ffd8ebd5

Change-Id: I115b491eca413437926f5bcaf53336151f9a7c0b

Change-Id: I40021caf3f94e718ea42d9ef77e5d9c77c3133de

This change replaces ElasticSearch with OpenSearch, and Kibana
with OpenSearch Dashboards. It migrates the data from ElasticSearch
to OpenSearch upon upgrade.

No TLS support is in this patch (will be a followup).

A replacement for ElasticSearch Curator will be added as a followup.

Depends-On: https://review.opendev.org/c/openstack/kolla/+/830373



Co-authored-by: Doug Szumski <doug@stackhpc.com>
Co-authored-by: Kyle Dean <kyle@stackhpc.com>
Change-Id: Iab10ce7ea5d5f21a40b1f99b28e3290b7e9ce895

Kolla Ansible is switching to OpenSearch and is dropping support for
deploying ElasticSearch. This is because the final OSS release of
ElasticSearch has exceeded its end of life.

Monasca is affected because it uses both Logstash and ElasticSearch.
Whilst it may continue to work with OpenSearch, Logstash remains an
issue.

In the absence of any renewed interest in the project, we remove
support for deploying it. This helps to reduce the complexity
of log processing configuration in Kolla Ansible, freeing up
development time.

Change-Id: I6fc7842bcda18e417a3fd21c11e28979a470f1cf

Container image naming scheme has changed

Change-Id: I775ea3f796290c670e4b04640f4429304dae609c

Change-Id: Ie09bf108250a71d539002dd5ccfa63dd71bcfe90

CentOS 9 Stream images are not getting published so we need to build
them every time.

Change-Id: I782ab105da4f23979dcbe2348c7141a1ae272b9a

The kolla user is not obligatory and the docs default to keeping
using the existing users.

Needed-By: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/854985
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/855071
Change-Id: I917f493d395cc7efcbf95bc55af8191d70ec3edb

This avoids polluting the module path for other deployed projects,
like Tenks.

Change-Id: I17802f628e1e7db8d1f5caaa815170a8415e995c

This way it works closer to what Tenks does in its own CI.

See-also: https://review.opendev.org/c/openstack/tenks/+/856296
Change-Id: I5bebcb3520aada3abc8b7d0d4087e7a3f9277df2

This patch follows upstream and disables linuxbridge testing.
Users are notified of the situation via the release note.

Change-Id: I524682ceb5287c14ef0ba99baae0c081850f4c5e

Change-Id: If9b40079d42cdabfd14d27603357dd0aa027a49b

R-17: Switch source images to current release

Disable rocky8 and openeuler jobs as master no longer works with
python3.6.

Change-Id: I89dd99b5f25502f5ebe15a9e90ccecc4bd6feafa

Depending on the way the testing script is called, it may sense
stdin being available and not being a tty [1]. The logic in the
Glance part of the client is then broken [2] as it detects both
volume and stdin as sources of the image and fails.
The proposed approach uses the script module for these tests.
This fixes the cephadm upgrade jobs where this script was called
using the shell module which causes this behaviour. The script
module is not affected. FWIW, the command module is affected
the same as shell because shell extends the command module.

[1] https://opendev.org/openstack/python-openstackclient/src/commit/6810414e45a32dd44263dff47fec161989508ef0/openstackclient/image/v2/image.py#L114-L120
[2] https://opendev.org/openstack/python-openstackclient/src/commit/6810414e45a32dd44263dff47fec161989508ef0/openstackclient/image/v2/image.py#L414

Change-Id: I3ce4059063e3a51eb1c5b42bda79893b56bd85f0
Story: 2006294

Follow-up to [1].
This unbreaks CI which was broken by a recent change to
master upper-constraints. [2]

[1] I82c4ff3b246c7db65ac8660b096d4a9a15dda8d7
[2] https://review.opendev.org/c/openstack/requirements/+/843722/3/upper-constraints.txt#b244

Change-Id: Idc7a893f53c6975cc4a3f6090020d973fa2288bb

Change-Id: Ic55a7384c298ef517aa4b7f0eaa67d53b5d70df0

This is in the hope to avoid random "Unable to validate token" in
AIO upgrade jobs which restart the Keystone container while
other services are trying to use it (most notably Placement but
also Nova and Neutron).

Change-Id: Ie6a95c3ca84df82ca8463cf76054e125cb1ffff1

For Swift, CI was still using DockerHub, directly.
The issue with DockerHub itself is that we publish there only
weekly.
The issue with not using infra's mirror is that we waste precious
resources.
Time to end that drama.

Change-Id: I928090c24f0eb24f8fab9b7412b58e854246fe80

We have only one value for install_type now and it gets removed from
image names.

Change-Id: I8bf95fd7aa9dd26b80d618ca0fcb097003b4cb0a

This avoids polluting job logs.

Depends-On: https://review.opendev.org/c/openstack/kolla/+/837872
Change-Id: I0bf134cd91ba35083a59787c537fc49dce998597

With the install_type going away and actually removed from job
definitions, we have to stop relying on it - to fix otherwise
broken jobs (swift and when doing kolla builds with k-a).

Change-Id: If13c4e276d3eec29a552ed229af95f5cf016100c

Venus is a new service for log processing.
This patch adds a CI scenario which tests Venus deployment.

Depends-On: https://review.opendev.org/c/openstack/kolla/+/793795
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/793897


Co-Authored-By: jinyuanliu <liujinyuan@inspur.com>
Change-Id: I0c7ba9e1ae23623b690a213c91ab3a12524d73f8

Installs Tenks [1] and uses it to create virtual machines to pose
as bare metal compute nodes.
The nodes are registered in Ironic, and used to provision
instances.

[1] https://docs.openstack.org/tenks/latest/

Depends-On: https://review.opendev.org/c/openstack/tenks/+/830182
Depends-On: https://review.opendev.org/c/openstack/tenks/+/830675
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/831055


Change-Id: Idfb8fbb50dc7442225967b2a2ec38ae7114f3c11
Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>

This change adds an Ansible Galaxy requirements file including the
openstack.kolla collection. A new 'kolla-ansible install-deps' command
is provided to install the requirements.

With the new collection in place, this change also switches to using the
baremetal role from the openstack.kolla collection, and removes the
baremetal role from this repository.

Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/820168

Change-Id: I9708f57b4bb9d64eb4903c253684fe0d9147bd4a

Also bumps the minimum to 4.

Change-Id: Ia373f9cc3bb69eba0288bbb3e497e8cadb7cc4d3

Change-Id: I7b1e36edb1680220c6fe082fbf5eefdd633c8cfa

Curl would not work without -L on old openstack.org URLs.

TrivialFix

Change-Id: I7ed7bd336f4b874fc6027cb9ad20669b08e4a7e9

This change bumps up max supported Ansible version
to 4.x (ansible-core 2.11.x) and minimum to 2.10.

Change-Id: I8b9212934dfab3831986e8db55671baee32f4bbd

Related-Bug: #1941982
Change-Id: I0e03db1177931ee6d17b21f614573575c3493eef

Swift is a major OpenStack project. It could use testing upgrades.

New jobs are placed in the experimental pipeline to avoid
excessive CI load on general changes.

Change-Id: I8a089fdd1f21eb4c3e00c38ea9dfcecc77565bf5
Related-Bug: #1874691

We use the cinder key for Nova by default, so a separate nova key is no
longer used.

Change-Id: I49ce6d36747e6c7d3a389d0afd2d034e8afdf8ed

Zuul 4.6.0 does not allow to set ansible_python_interpreter. [1]
Instead, with the current Zuul and Ansible, this should be
automatically set to the proper python.

This patch is required to restore the jobs which are ignored
otherwise. [2] [3]

Additionally, this change avoids the use of Ansible's pip
module because it tries to use setuptools from the
ansible_python_interpreter first even if another executable is
set.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023291.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023326.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023321.html

Change-Id: I53e666d59d0cce26e38c6f66a39eb204bda502d3

OVS upgrade jobs failed due to assigning an IP on the br-ex interface
(which is recycled during OVS upgrade). This change introduces a bridge
and veth pair for Neutron to use.

Change-Id: Ib3bee6e810fb8d31552d4c72c2a1ccae382c51f0

One missed previous scenario name occurence turned off OpenStack
testing in multinode scenario.
This patch to fix that.

Change-Id: I58275a2fa1490307858d45855255bb8e3a05043c

Change-Id: Ie9e2463a1b405453c8ae7caaee6ad57e0562ee47

Often cephadm jobs fail with:
Mar 30 13:01:21 primary bash[75459]: debug 2021-03-30T13:01:21.844+0000 7fa30431f700 -1 error: monitor data filesystem reached concerning levels of available storage space (available: 4% 1.8 GiB)

Let's check if 5G OSD helps and also print df -h output for reference

Change-Id: I6960fd0f378aea5a14a73d9228edf86fb86cac6c