Build images and boot ubuntu-noble everywhere we do for
ubuntu-jammy. Drop the kernel boot parameter override we use on
Jammy since it's default in the kernel versions included in Noble
now.
Change-Id: I3b9d01a111e66290cae16f7f4f58ba0c6f2cacd8
This is the last step in cleaning centos-7 out of nodepool. The previous
change will have cleaned up uploads and now we can stop building the
images entirely.
Change-Id: Ie81d6d516cd6cd42ae9797025a39521ceede7b71
This removal of centos-7 image uploads should cause Nodepool to clean up
the existing images in the clouds. Once that is done we can completely
remove the image builds in a followup change.
We are performing this cleanup because CentOS 7 is near its EOL and
cleaning it up will create room on nodepool builders and our mirrors for
other more modern test platforms.
Depends-On: https://review.opendev.org/c/opendev/base-jobs/+/912786
Change-Id: I48f6845bc7c97e0a8feb75fc0d540bdbe067e769
The cloud name is used to lookup cloud credentials in clouds.yaml, but
it is also used to determine names for things like mirrors within jobs.
As a result changing this value can impact running jobs as you need to
update DNS for mirrors (and possibly launch new mirrors) first. Add a
warning to help avoid problems like this in the future.
Change-Id: I9854ad47553370e6cc9ede843be3303dfa1f9f34
This should be landed after the parent chagne has landed and nodepool
has successfully deleted all debian-buster image uploads from our cloud
providers. At this point it should be safe to remove the image builds
entirely.
Change-Id: I7fae65204ca825665c2e168f85d3630686d0cc75
Debian buster has been replaced by bullseye and bookworm, both of which
are releases we have images for. It is time to remove the unused debian
buster images as a result.
This change follows the process in nodepool docs for removing a provider
[0] (which isn't quite what we are doing) to properly remove images so
that they can be deleted by nodepool before we remove nodepool's
knowledge of them. The followup change will remove the image builds from
nodepool.
[0] https://zuul-ci.org/docs/nodepool/latest/operation.html#removing-a-provider
Depends-On: https://review.opendev.org/c/opendev/base-jobs/+/910015
Change-Id: I37cb3779944ff9eb1b774ecaf6df3c6929596155
This should be landed after the parent chagne has landed and nodepool
has successfully deleted all opensuse-15 image uploads from our cloud
providers. At this point it should be safe to remove the image builds
entirely.
Change-Id: Icc870ce04b0f0b26df673f85dd6380234979906f
These images are old opensuse 15.2 and there doesn't seem to be interest
in keeping these images running (very few jobs ever ran on them and
rarely successfully and no one is trying to update to 15.5 or 15.6).
This change follows the process in nodepool docs for removing a provider
[0] (which isn't quite what we are doing) to properly remove images so
that they can be deleted by nodepool before we remove nodepool's
knowledge of them. The followup change will remove the image builds from
nodepool.
[0] https://zuul-ci.org/docs/nodepool/latest/operation.html#removing-a-provider
Depends-On: https://review.opendev.org/c/opendev/base-jobs/+/909773
Change-Id: Id9373762ed5de5c7c5131811cec989c2e6e51910
This removes the fedora image builds from nodepool. At this point
Nodepool should no longer have any knowledge of fedora.
There is potential for other cleanups for things like dib elements, but
leaving those in place doesn't hurt much.
Change-Id: I3e6984bc060e9d21f7ad851f3a64db8bb555b38a
This will stop providing the node label entirely and should result in
nodepool cleaning up the existing images for these images in our cloud
providers. It does not remove the diskimages for fedora which will
happen next.
Change-Id: Ic1361ff4e159509103a6436c88c9f3b5ca447777
kolla wants to have testing parity between Ubuntu and Debian, so add a
nested-virt-debian-bullseye label to nodepool matching the existing
nested-virt-ubuntu-bionic label.
Change-Id: I27766140120fb55a2eab35552f0321b1da9c67ff
Our various nodepool launcher configs have gotten out of sync with
recent additions. Try to match them up better by adding rockylinux
and openeuler to places where they were missing. In particular, this
addresses an inconsistency on nl04 which caused the service to crash
at last restart due to rockylinux missing from the main diskimages
list.
Change-Id: Ie157ab7f667dbdc313b7fdbfc1df71874e8bd0fc
kolla-ansible has switched to Jammy in master, create nodes that allow
their kvm tests to continue to run.
Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: I97b59a1dad032665db986ffaf9f7d6fdb45caf26
OVH will upgrade the GRA1 region to a new OpenStack release on
2022/03/28.
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: I5bfc7af472f94c74e6fd6234c1e8e0205109a50d
Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com>
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