This distro release reached its EOL December 31, 2021. We are removing
it from our CI system as people should really stop testing on it. They
can use CentOS 8 Stream or other alternatives instead.
Depends-On: https://review.opendev.org/c/opendev/base-jobs/+/827181
Change-Id: I13e8185b7839371a9f9043b715dc39c6baf907d5
This removes the label, nodes, and images for opensuse-tumbleweed across
our cloud providers. We also update grafana to stop graphing stats for
the label.
Depends-On: https://review.opendev.org/c/opendev/base-jobs/+/824068
Change-Id: Ic311af5d667c01c1845251270fd2fdda7d99ebcb
OVH will upgrade the BHS1 region to a new OpenStack release on
2022/01/05.
During this operation, all API are going to be down (for few hours).
A proper communication will be done, but this commit should be merged
just before.
Change-Id: Ie002852ecb39dcdf942e132f0cb5e2e89ac2d0c0
Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com>
CentOS Stream 9 repos are ready and support for it is included in
diskimage-builder [1]. This patch is adding centos-9-stream diskimages
and images to nodepool configuration in opendev.
[1] https://review.opendev.org/c/openstack/diskimage-builder/+/811392
Change-Id: I9b88baf422d947d5209d036766a86b09dca0c21a
This is a followup change to the previous change which removed fedora-32
node launches. Here we cleanup the disk image configs
Change-Id: I459ec47735550e4adcc912bd707836582223b075
Since Debian Buster can not be used with nova 23.0.0 because of the
min required libvirt version, we should make Bullseye available for CI
to ensure that OpenStack Wallaby release will run on it smoothly.
Depends-On: https://review.opendev.org/c/openstack/diskimage-builder/+/783790
Change-Id: I9c1bb7aaa02ba60ee52e2d7b990e2e6e1212317f
This is a followup change to the previous change which removed fedora-31
node launches. Here we cleanup the disk image configs.
Change-Id: Ic72e324c65ee9d18e9c4cf6627ea6c147b9f484b
A followup change will remove the diskimage configuration for fedora-31.
The current fedora releases are 32 and 33 so we should clean up 31.
Change-Id: I0dde34ab005f48ac521d91e407ac437d3cec965f
Our system-config roles for nodepool update the zookeeper configuration
for our nodepool hosts. The content in the files here is merely a
placeholder. Make that more apparent via the addition of comments and
use of dummy data.
Change-Id: I4e35088a04f6393409963f841f2e9ba174c69598
Once these new servers are up and running in a happy idle state we are
clear to flip the configs around so the new focal servers take over node
provisioning duties. This change makes that happen.
Change-Id: I6ad57218805e28b555e1e3a0dc959ee4f00428cc
These configs will allow us to bring up the nodepool-launcher service on
new focal nodepool launcher nodes in an idle state. Once we are happy
with them in the idle state we will land the next change which flips the
old hosts to idle and puts these new servers in production.
Change-Id: I0d0a30c49c1336b33dd969b039544e10d98dad0e