Useful if you're configuring your own private repos, and don't/can't
sign them.

Change-Id: I2d592c5479530b2fe9a60c14ee59e817b8402490

Follow-up on I43a9c2a57fcfe2c9d84f39903aac7c258f9a897f. As discussed
before we set slightly more accurate name for the manage containers
role since using 'deploy-containers' role with action 'destroy' can
be a little confusing.

Change-Id: I6d4a3479d492e0fe86ce3de7414fa47c584577ea
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>

Change-Id: I496be412cb536d37e1547bb6f1c54717013b8968

This defines the dates where certain changes must be
made.

Change-Id: I3bfa2909cba9661f542512316e900e75eaa92d6b

This reverts commit b4448d6b.

Change-Id: I76aa0fcf362b77fe22f738b9d1c60cbc363531a4
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>

Change-Id: I546d62490d66a8829fc906e7d021dc056001b4bb

Dalmatian is not a SLURP release. [1]

[1] https://releases.openstack.org

Change-Id: If590fdb59b0d78a8fc52391bc1e9ae64b2371901

Add file to the reno documentation build to show release notes for
stable/2024.1.

Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.

Sem-Ver: feature
Change-Id: If0e5d03825feeed634ee20b802e9663bdd4bf8de

This commit changes seed-images jobs to build seed and overcloud
container images, each with a customisable regex.

The rocky9 job continues to build only the base image, although for both
overcloud and seed instead of seed only.

The other seed-images jobs (centos9s and ubuntu-jammy) now build all
default overcloud images. This takes longer and can fail for various
reasons unrelated to Kayobe, but this is fine since the jobs are marked
as experimental.

This is to attempt to catch bugs in the image build code, such as the
ones fixed by [1].

Note that the ubuntu-jammy job does not build the bifrost-deploy seed
image because the build is currently timing out. The centos9s job builds
it successfully.

Also update release documentation to remind developers to run
experimental jobs.

[1] https://review.opendev.org/c/openstack/kayobe/+/921012

Change-Id: Idf705d9cf41766a897444898ac31c4635b70ec16

Closes-Bug: #2067288
Change-Id: I57fb4c1697a31d4f592d79a31a04507cf91e97c7

This can be useful when using a seed VM that is not deployed by kayobe,
and can therefore not use ``kayobe seed deprovision``, especially when
iterating on kayobe-config during the inital stages of a deployment, or
for development, where you want to re-run the playbooks from a clean-ish
state.

Change-Id: I43a9c2a57fcfe2c9d84f39903aac7c258f9a897f

This allows us to continue execution until a certain proportion of hosts
fail. This can be useful at scale, where failures are common, and
restarting a deployment is time-consuming.

The default max failure percentage is 100, keeping the default
behaviour. A global max failure percentage may be set via
kayobe_max_fail_percentage, and individual playbooks may define a max
failure percentage via <playbook>_max_fail_percentage.

Related Kolla Ansible patch:
https://review.opendev.org/c/openstack/kolla-ansible/+/805598

Change-Id: Ib81c72b63be5765cca664c38141ffc769640cf07

The kolla_enable_letsencrypt variable was undefined, which was causing
overcloud container image build to fail when the variable was not
defined in Kayobe configuration.

The bool filter was missing for kolla_enable_letsencrypt, which was
causing letsencrypt images to be built when kolla_enable_letsencrypt was
set to "false" or "no".

Change-Id: I234b7a0434ba3d533a66b766331fd489078fbcf8

We were still using stream8 images which cannot install packages
anymore, due to the end of life of CentOS Stream 8.

Change-Id: I8604c342e4dbc41dd5bee0f28a92c3c3cd37d631

Change-Id: I65da7cdfd284a01b2e214c2dc0f27a5f45ae0999

This was missed from I2ea9b2ec58913722c4defffbeee88cc420dcbdab.

Change-Id: I84971f8daa4caf2227863810c7b12e59192c2515

Change-Id: Ib12ac0e8dac8804085ea30bac7b4b0e659309cb0

Change-Id: I2737c200ba33d9eabe2c9815766b2a3555827ef5

Change-Id: Ia38fd3e98d5e21fd2a23175661c3a3093c6ca18b

A few long sentences are split up. YAML indentation is fixed.

Change-Id: I60098522e08f0d463d0300beac64476f7b1488e6

This is useful to ensure logs are persisted across reboots.

Change-Id: Ie5ff7536b160196dc57448c3ed982d15826b2cbe
Closes-Bug: #2055299
Co-Authored-By: Piotr Parczewski <piotr@stackhpc.com>

Change-Id: I704b4e79ce5519a57830fbcaa51b8cf19f3f249a

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: I65eccf6bbe13534418c2f5b0aa5397ba170bd17a