Change-Id: I2546d714d1e6a1b648a4c6242ece18a2108b9183

This adds an extra resize operation to core OpenStack tests. This should
be fast since we are only increasing the number of cores of the VM and
could help catch additional errors in CI tests.

Change-Id: Ia61b995dbffcda4f1e6494548df457231cb67bd7

Change-Id: I4d09018f4e921e90cbe7457c1f7fb025ef3acfa8

Change-Id: Id5c53b63e88502c999b89cbc62405bb8953fef3a

Adds a precheck to fail if non-quorum queues are found in RabbitMQ.

Currently excludes fanout and reply queues, pending support in
oslo.messaging [1].

[1]: https://review.opendev.org/c/openstack/oslo.messaging/+/888479

Closes-Bug: #2045887
Change-Id: Ibafdcd58618d97251a3405ef9332022d4d930e2b

Change-Id: I46c05a54171cbf43a51594998561db94af7d17e6

Change-Id: I373f6d13809674c521155ca51962785a8b1ac598

Similar to [1].

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

Change-Id: I254f71d607353e0cf4d3d5ebafd6813287c4fa9f

Change-Id: I54f94c383ae5a1185b364495422e1ab79cbd1afb

This implements a global toggle `om_enable_rabbitmq_quorum_queues`
to enable quorum queues for each service in RabbitMQ, similar to
what was done for HA[0].

Quorum Queues are enabled by default.

Quorum queues are more reliable, safer, simpler and faster than
replicated mirrored classic queues[1].

Mirrored classic queues are deprecated and scheduled for removal
in RabbitMQ 4.0[2].

Notice, that we do not need a new policy in the RabbitMQ definitions
template, because their usage is enabled on the client side and can't
be set using a policy[3].

Notice also, that quorum queues are not yet enabled in oslo.messaging
for the usage of reply_ and fanout_ queues (transient queues).
This will change once[4] is merged.

[0]: https://review.opendev.org/c/openstack/kolla-ansible/+/867771
[1]: https://www.rabbitmq.com/quorum-queues.html
[2]: https://blog.rabbitmq.com/posts/2021/08/4.0-deprecation-announcements/
[3]: https://www.rabbitmq.com/quorum-queues.html#declaring
[4]: https://review.opendev.org/c/openstack/oslo.messaging/+/888479



Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: I6c033d460a5c9b93c346e9e47e93b159d3c27830

Change-Id: Ie3963f5ed20f7fb61ef2e03f0cf12a4ea1c87c9c

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

Change-Id: Ia1de6d9452e2c900169e9b4ccb7dfc1280283909

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

This reverts commit b86c304a.

Reason for revert: We want to enable Quorum Queues by default in Caracal, without requiring two queue migrations between releases. See etherpad for details: https://etherpad.opendev.org/p/kolla-ansible-rmq-quorum-queues-proposal

Change-Id: Ia19ab97f538125475297976347c5da332a7fdda7

Change-Id: Id6ca24c058fabf0c68bcb5b6d1e58175aaf531eb

Changes name of ansible module kolla_docker to
kolla_container.

Change-Id: I13c676ed0378aa721a21a1300f6054658ad12bc7
Signed-off-by: Martin Hiner <m.hiner@partner.samsung.com>

docker_restart_policy: no causes systemd units to not get created
and we use it in CI to disable restarts on services.

Introducing oneshot policy to not create systemd unit for oneshot
containers (those that are running bootstrap tasks, like db
bootstrap and don't need a systemd unit), but still create systemd
units for long lived containers but with Restart=No.

Change-Id: I9e0d656f19143ec2fcad7d6d345b2c9387551604

Copy cat of I2cfd2667abb1ae8988b7a7fd9761b75c20a0eaa4

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

Octavia now requires redis - see [1].

[1]: Iec3c8a4b4e257557dc8ec995c41d0ad7e88e13e2

Change-Id: I5aa489209984974b2345b1f5f7608db022a1405e

Change-Id: I7df734cf15eba1af4da92f9c4ef12cc761442ca1

Collections version taken from official Ansible 7 package [1]
and limited to the same major version.

[1]: https://github.com/ansible-community/ansible-build-data/blob/main/7/ansible-7.7.0.yaml

Change-Id: I0f1ea9717397adc2d2c3215d74ec3759f351a57a

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

This avoids the need to use a proxy, or some other means, to connect to
Prometheus. This is disabled by default and can be enabled by setting
enable_prometheus_server_external to true.

Change-Id: Ia0af044ff436c2a204b357750a16ff49fcdfec45

This allows us to share variables between jobs without inheriting any
of the pre-run, post-run or cleanup playbooks of the parent job. These
run due to the zuul inheritance rules, see:

https://zuul-ci.org/docs/zuul/latest/config/job.html#job



Signed-off-by: Will Szumski <will@stackhpc.com>
Change-Id: Id0a34778accafdc62ebe916e81d69f31c6274d4c

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

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

In order to drop docker pip package from requirements.txt in Kolla
we need to start installing that here.

Change-Id: Ifd3b86afb65760c3b3ce7f26feebdaf0789fb525

This change adds basic deployment based on Podman
container manager as an alternative to Docker.

Signed-off-by: Ivan Halomi <i.halomi@partner.samsung.com>
Signed-off-by: Martin Hiner <m.hiner@partner.samsung.com>
Signed-off-by: Petr Tuma <p.tuma@partner.samsung.com>
Change-Id: I2b52964906ba8b19b8b1098717b9423ab954fa3d
Depends-On: Ie4b4c1cf8fe6e7ce41eaa703b423dedcb41e3afc

This reverts commit d3c4ff8b.

Reason for revert: workaround is present

Change-Id: I40f794ce5f401a7357099dff10f7f8e05e1c4826

Change-Id: I5df9cf14f16a7c08cccf053302bbda227526a4a8

Change-Id: I7b1a5bef0cb1dc1dfad1c6c4ca486e6ead847f12

It seems latest ansible-core 2.14 and 2.15 breaks a filter
in kolla-ansible - let's pin for now and fix the issue in a
separate patchset.

Change-Id: I200ad775094230e4bf8bb40988c12ea03471008f

Change-Id: Ic153a91beb30daa334ccbb0430ce8340bd6c480f

Following Monasca initial removal in [1]

[1]: I6fc7842bcda18e417a3fd21c11e28979a470f1cf

Change-Id: I94d6f102e8da3882f37f3007639b917c49f907a9

Currently we don't really know what is the OVN cluster status
when test-core-openstack fails on Neutron operations.

Change-Id: Id8ca7c7cd6d741e406f609527016edff592352d7

Closes-Bug: #2036741

Change-Id: Ib448d04e43dff78e344064161beadae917c41206

Initially Ubuntu/Debian used /var/run/openvswitch as default OVN run dir,
it seems it has changed long time ago - but we haven't picked that up on latest
OVN DB refactor.

Adding in OVN and OVN upgrade Debian jobs to enhance coverage.

Closes-Bug: #2035584

Change-Id: I78967c4499269578ac921ad9a553946b65e1293f