openstack/kolla-ansible.git/zuul.d/scenarios/lets-encrypt.yaml, branch stable/2026.1Unnamed repository; edit this file 'description' to name the repository.
https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.12026-04-27T16:52:03+00:00letsencrypt: Switch webserver image to httpd2026-04-27T16:52:03+00:00Michal Nasiadkamnasiadka@gmail.com2026-04-27T11:06:47+00:00urn:sha1:b9fc7a416e0d38f9176c4aac0fe3286bf90ceac7
Switch to httpd image which was introduced for keystone-httpd and
is identical to letsencrypt-webserver image.
The letsencrypt-webserver image will be removed afterwards in [1].
[1]: https://review.opendev.org/c/openstack/kolla/+/986151
Depends-On: https://review.opendev.org/c/openstack/kolla/+/986377
Change-Id: Ica381670de4b157c97be4089eaeb7fe2f7ba039f
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Add support for Debian Trixie (13)2025-12-19T14:55:59+00:00Michal Nasiadkamnasiadka@gmail.com2025-12-05T14:26:02+00:00urn:sha1:536f4ae1a21ee715106dd7435c42935eb06df7ca
Remove /etc/timezone bind mount since Debian does not provide
that file anymore.
Depends-On: https://review.opendev.org/c/openstack/kolla/+/964793
Change-Id: If1a289068093843184f0d7b495815db006f2d563
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
CI: Rework deploy.sh to an Ansible role2025-10-09T13:05:44+00:00Michal Nasiadkamnasiadka@gmail.com2025-10-07T17:57:40+00:00urn:sha1:10e719f9d8b4b8d8efbc00e9a69ae6984b4a0a10
Change-Id: Iecb212c38732d38f704f1a7d43036f8bbade496a
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Update Zuul triggers after group_vars split2025-10-01T14:10:39+00:00Michal Nasiadkamnasiadka@gmail.com2025-09-25T09:52:48+00:00urn:sha1:47214ff28d1fc44673a4430e4edd73f8e43975ca
The basic approach is:
- we test majority in aio and cephadm scenarios
- additional scenario jobs are only triggered on roles
that are not covered by aio/cephadm (and the ones
that are relevant for given scenario)
Change-Id: I56b4e1218092ffcca074fef3ceac8e9d99054b21
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
CI: Reorganise scenarios into project templates2025-09-22T11:52:00+00:00Michal Nasiadkamnasiadka@gmail.com2025-09-15T12:29:39+00:00urn:sha1:5c087f54cff9a7c7fd3d5a6fd3ce622ee415f694
This patch moves into using project templates, which is easier
to organise.
base_distro and upgrade variables are derived from base.yaml
and respective job name - so don't need to be specified in each
job anymore.
All jobs will now also have an OS release specified, so it's easier
to add different OS release jobs (e.g. when backporting new release
support to stable branch).
Change-Id: I1f08f9b9064d9f7e95b07944db0e7ebac3120c57
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>