The prometheus-msteams project is no longer maintained [1]. As a result
support for deploying prometheus-msteams via kolla-ansible has been
dropped. Users are encouraged to migrate to the native Prometheus
Alertmanager integration with Microsoft Teams [2].

[1] https://github.com/prometheus-msteams/prometheus-msteams/issues/343
[2] https://prometheus.io/docs/alerting/latest/configuration/#msteams_config

Change-Id: I93d28ef138b4e784465f3a7eaa11101ea5877050

Interface names with dashes can cause problems in Ansible since dashes
are replaced with underscores when referencing facts.

Change-Id: Ib15f81120d353ebcf8965dc0aaba90f3a9b0ec44
Related-Bug: #1927357

As our CI is ipv6 only and using cirros for tests.
Therefore we need to set force_config_drive = true.

Change-Id: I07058a4b30d0de1aaf8e82656024c5f6a99b290b

ansible-core 2.16 and later requires python 3.10+ (see [1])

[1]: https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix

Change-Id: Id5e10872de413e7b476c5343360d73c109b9667a

This reverts commit 0ec71d87.

Reason for revert: fixed now

Change-Id: I33d62e910ff6151eb03c814ee7b8984c6f4e5308

It was deprecated in Antelope cycle.

Change-Id: I499e69ec6db63e4067e49376e2a1f3e01e48fe62

It's inactive and hasn't produced a 2024.1 release [1].
In addition to that, there's a CVE that hasn't really been patched [2].

Also drop outward_rabbitmq that was used only with Murano.

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects
[2]: https://lists.openstack.org/archives/list/openstack-announce@lists.openstack.org/thread/4FYM6GSIM5WZSJQIG4TT5Q3UBKQIHLWX/

Change-Id: I691205730b0e10a42ce61f3340cc39ee51bd1010

It's inactive and hasn't produced a 2024.1 release [1].

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects

Change-Id: I217b3633f07e5b2c657e20b19aaa4fbb46535a97

It's inactive and hasn't produced a 2024.1 release [1].

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects

Change-Id: I888963751b6e1ed080588297c2889e700431516c

It's inactive and hasn't produced a 2024.1 release [1].

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects

Change-Id: Ic988295bc5b8acb19df008fe0d52a3bcc6de2135

It's inactive and hasn't produced a 2024.1 release [1].
There are some efforts to restore Freezer, but let's remove it for now.

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects

Change-Id: Ie42012af9e5c64bca23a6e6826bfc4651fd194bd

Fix existing spelling errors

Change-Id: Ie689cf5a344aaa630a4860448b09242333a8e119

This reverts commit 0b1a59dd.

Reason for revert: Upstream Fix available at https://github.com/containers/podman-py/pull/351

Change-Id: Iadb74ffb5a747bd16e6acebd6a9c22b3b7198fd0

Some multinode jobs have been failing due to galera suspecting inactive nodes
Tweak it as per [1].

[1]: https://galeracluster.com/library/documentation/recovery.html

Change-Id: I5577ea2c23d6dbd440bd52899a30ea9531996256

Change-Id: I5b4a30e605bb143cf342f83f0c811c25046269ef

Currently RMQ 3.13 fails on ipv6 multinode scenario, use 3.12 from 2023.1
until [1] gets resolved.

[1]: https://github.com/rabbitmq/rabbitmq-server/issues/10728

Change-Id: If11710e99cf2e340e558d68e2071c1bb16825e55

The upgrade job needs the haproxy exporter group, which
was missing from the inventory.

Change-Id: Ie4ecf283a2f4ac056ace5e76f2acc4ba1a8fe0b4

Default timeout is 5 and we're often hitting that on our poor man's
Ceph.

Change-Id: Ide92b3c32150c0045b0723155f94b21ea9cdce66

etcd is flakey and complaining over slow disk

Change-Id: I1f5191015b53bdb218cfeaa43586ecf2d71a161e

This patch adds tests for neutron and designate DNS
integration.

Tests are based on scenarios described below in [1][2].

[1] https://docs.openstack.org/neutron/latest/admin/config-dns-int.html
[2] https://docs.openstack.org/neutron/latest/admin/config-dns-int-ext-serv.html

Change-Id: I3953f760458285e5c9a818599492c6176e857dde

Change-Id: I3501e6bf17ccb94adfcdb62956dceba9d67b0881

This reverts commit 94a74f58.

Reason for revert: Zun/Kuryr-libnetwork has switched to "local" scope which doesn't require docker 20 anymore. It should work for latest docker version. Related patches:
https://review.opendev.org/c/openstack/zun/+/903884

Change-Id: Ieb545ae5a5917322f599728587c3f04ea8356126

In Kolla CI K-A upgrade job needs docker_custom_config override
as docker_registry var is being used both for docker daemon
config - for kolla images build, and kolla-ansible container images
sources - where we're using quay.io mirror.
docker_custom_config gets precedence in docker daemon
configuration.

docker_custom_config was removed in [1].

[1] https://review.opendev.org/c/openstack/kolla-ansible/+/904067

Change-Id: I1e890223faf25b1169a49e22a9529f90806d2f3a

HAProxy exposes a Prometheus metrics endpoint, it just needs to be
enabled. Enable this and remove configuration for
prometheus-haproxy-exporter. Remaining prometheus-haproxy-exporter
containers will automatically be removed.

Change-Id: If6e75691d2a996b06a9b95cb0aae772db54389fb
Co-Authored-By: Matt Anson <matta@stackhpc.com>

Change-Id: Id25b4407a8170f69e4cd7278e0aff64c609ace7d

Change-Id: I552fea9f9b461e57611f1d2aa5c767a1f4043ff8

Change-Id: I4d09018f4e921e90cbe7457c1f7fb025ef3acfa8

Similar to [1].

[1]: https://review.opendev.org/c/openstack/openstack-ansible/+/851426

Change-Id: I254f71d607353e0cf4d3d5ebafd6813287c4fa9f

This dependency was added to podman-py in version 4.8.0, but not added
properly to their requirements. Install it explicitly for our tox
and integration testing as a workaround.

[0] https://github.com/containers/podman-py/issues/350

Change-Id: I61a5fdfc4e505f2577185f0c0f1297cf2709be2c

This commit addresses a few shortcomings in the etcd service:
  * Adding or removing etcd nodes required manual intervention.

  * The etcd service would have brief outages during upgrades or
    reconfigures because restarts weren't always serialised.

This makes the etcd service follow a similar pattern to mariadb:
  * There is now a distiction between bootstrapping the cluster
    and adding / removing another member.

  * This more closely follows etcd's upstream bootstrapping
    guidelines.

  * The etcd role now serialises restarts internally so the
    kolla_serial pattern is no longer appropriate (or necessary).

This does not remove the need for manual intervention in all
failure modes: the documentation has been updated to address the
most common issues.

Note that there's repetition in the container specifications: this
is somewhat deliberate. In a future cleanup, it's intended to reduce
the duplication.

Change-Id: I39829ba0c5894f8e549f9b83b416e6db4fafd96f

Copy cat of I2cfd2667abb1ae8988b7a7fd9761b75c20a0eaa4

Co-Authored-By: Pierre Riteau <pierre@stackhpc.com>
Change-Id: If4feec0a86f9a50ed43920ecf4d0da8875c71f4e

Skyline is a new service for dashboard.
This patch adds a CI scenario which tests Skyline deployment.

Depends-On: https://review.opendev.org/c/openstack/kolla/+/826948
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/828464

Implements: blueprint skyline
Change-Id: I48488a24d6c8a03cd129929347b1bdac25f198b0

Add support for automatic provisioning and renewal of HTTPS
certificates via LetsEncrypt.

Spec is available at:
https://etherpad.opendev.org/p/kolla-ansible-letsencrypt-https

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


Co-Authored-By: Michal Arbet <michal.arbet@ultimum.io>
Implements: blueprint letsencrypt-https
Change-Id: I35317ea0343f0db74ddc0e587862e95408e9e106

Enable the jobboard feature for the Octavia amphora provider. This
requires Redis as a dependency, a precheck is added to ensure proper
configuration.

https://docs.openstack.org/octavia/latest/install/install-amphorav2.html

Change-Id: Iec3c8a4b4e257557dc8ec995c41d0ad7e88e13e2

When the kolla-ansible project has a cross dependency on
the kolla project, CI have to build an image from that change
locally. However, Podman refuses to push to localhost, so it is
necessary to set the local repo as insecure for the test.

Change-Id: I786b22ff0cd581f90ba4bec08842651a6509a745

Following Monasca initial removal in [1]

[1]: I6fc7842bcda18e417a3fd21c11e28979a470f1cf

Change-Id: I94d6f102e8da3882f37f3007639b917c49f907a9

Closes-Bug: #2036741

Change-Id: Ib448d04e43dff78e344064161beadae917c41206

Up till now the ARA plugin has been pinned to a very old version,
and is no longer functional.

This installs a much newer version of ARA and adds a README file
to guide developers on how to view the sqlite file.

The ARA plugin is installed by default, but not activated. This
is intended to catch a small amount of regressions and
integration failures.

Developers can enable the plugin by adding the string `#ara`
to their commit message. This avoids extra load on the CI.

Change-Id: Id8328e374c9590b1363026fa2b2b24e191183987

It's not needed anymore, since both Ceph and ansible-collection-kolla
are setting that by default.

Also fix test-core-openstack so it doesn't delete a server before
volume attachment test.

Change-Id: I20bd352479ee5562514084d0d11063e45e8b956a

We've seen issues in CI when keepalived haproxy check script returns
an error and keepalived is switching to backup and then again to primary
on a single node environment.

Closes-Bug: #2025219

Change-Id: Iba62e76b3cf83f3ade6df81288d2d77129ffc725