This enables the nodepool delete-after-upload option with keep-formats
set to qcow2 on x86 image builders. This should clear out vhd and raw
files after uploads for those formats are completed keeping only qcow2
longer term. This should reduce disk space overhead while still enabling
us to convert from qcow2 to the other formats if that becomes necessary.
Note that we do not enable this for arm64 before arm64 builders
currently build raw images only and we still want at least one copy of
the image to be kept even if it is raw (and not qcow2).
Change-Id: I6cf481e0f9a5eaff35b5d961a084ae34a49ea6c6
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 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
This was the old timeout then some refactoring happened and we ended up
with the openstacksdk timeout of one hour. Since then Nodepool added the
ability to configure the timeout so we set it back to the original six
hour value.
Change-Id: I29d0fa9d0077bd8e95f68f74143b2d18dc62014b
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
In order to reduce the load on our builder nodes and reduce the strain
on our providers' image stores, build most images only once per week.
Exceptions are ubuntu-jammy, our most often used distro image, which we
keep rebuilding daily, and some other more frequently used images built
every 2 days.
Change-Id: Ibba7f864b15e478fda59c998843c3b2ace0022d8
Release is done, mirror is in place, ready to go.
Adopt using systemd-timesyncd like we do for recent Ubuntu releases.
Change-Id: I3fbdc151177bf2dba81920a4a2e3966f271b50ad
I have left the -regionone off this, making its naming inconsistent.
This adds it.
Since this cloud is in its bringup phase, I will put the builder in
emergency, clear out the images for the "linaro" provider and then
apply this by hand, so that we don't have old ZK nodes lying around.
We can then merge this to make it consistent.
Change-Id: I23328cbc53b87e1e81d26cc56f99aaad33b415c0
Drop the linaro-us cloud from nb04 uploads and launcher; it is
replaced by the new linaro cloud. Region is not running any nodes
since I6ef17bb517078de363286ecad9749cb321b4c92c.
nb03 is still in the inventory, but shutdown and in emergency. We can
remove the config here and cleanup will follow.
Change-Id: Ia049a2e44d2c4add0346e8262b60cdfb2c976539
This should remove nodepool's tracking of the diskimages in this
cloud, in preparation for it's removal.
Change-Id: Icf7b00f88a9de8a91510ee231c47eef207da4ea8
nb03.openstack.org and nb04.opendev.org have been cleaned up. Remove
their host specific configs.
Depends-On: https://review.opendev.org/752740
Change-Id: I310534a45a88546ae5537d3016a76693266212bc
We'd like to delete nb04.opendev.org and go back to running two x86
image builders. In order to do that gracefully we need to pause all
image builds on nb04 so that nb01 and nb02 take up the slack. Then once
nb04's images are no longer in use they can be deleted and the builder
can be removed.
Change-Id: Ibe00252de4f602a6c9f48ad1799d844710ddc6dc
With nb01/02.opendev.org now being Ansible/container builders, all
builders can use the same config. This moves the nb04 config back to
nodepool.yaml and unpauses everything except gentoo, which is still
constantly failing.
Change-Id: I55cfedb9ac7fa06ba1725f0ec92f7247237dc74b
We took a slightly different approach for tumbleweed and dropped
support for the pip-and-virtualenv element for it (and Fedora 31+)
with I7a6a342461d6001c25e55638ba9b7438c28f2519. So there's no need
for the -plain image now; switch the main image to using the base pip.
This is currently failing to build due to this.
Change-Id: I3333b475ff9d2f2fb96ad5588c6250cba2593e06
Focal is released. Let's start building images for it.
Only build on nb04 - we need newer debootstrap.
Don't built plain images - and don't put pip-and-virtualenv
on these.
Change-Id: I53444cbbd8c46ca4d6919fa7b924134c4d0464a4
This reverts commit 03a2a71984f921fdc73466cd7781799d2982369d.
Change I0887a801bb6dd4ce992c39d9e332a18f8194a7b9 merged in nodepool,
which should work around the problem we saw on nb04. Try again.
Change-Id: I4a13d4f0f07d755a12557b50ec24ba59df51fe97
Something about the debootstrap processes destroys the nodepool
container, making not only this Ubuntu builds fail but then every
build after.
Move them back to regular builders while we debug further.
Change-Id: I48eb721bffafe2404a332192976848dba2ca80cc
Add more images without pip-and-virtualenv we can test on. Build all
-plain images on nb04 (the containerised builder) as an additional
test of that environment (the existing bionic-plain build is moved
here too).
Change-Id: Ic29a25527e259a61ca025325b74acbe64a71774c
This uses the job inheritance feature in the dependent change to
update the config file and remove a lot of duplicated content for
diskimages.
The status-quo is kept with this change; nb04 has everything paused
but the Fedora builds, and vice-versa for the main config file.
Depends-On: https://review.opendev.org/713157
Change-Id: I2e1803d77e702f325c3c4b2af0000bffe98c3e0b
This reverts commit cc19b638d6c73e1973544128699f3872c589d051.
This has broken keystone jobs.
Change-Id: Id6377d7196f3e57c0729d88aec458dbd4f4ae776
Depends-On: https://review.opendev.org/#/c/720227/
Move these images to nb04, the container-based builder. Pause them on
the other builders. Due to upstream changes the pip-and-virtualenv
element doesn't work on them any more; remove it. Work is in progress
to fix our base jobs to operate on platforms such as this, but in the
mean time devstack tests should work.
Change-Id: I0b5ccf6f0b441bdb752b5f066b69edda92f4b37a
As part of [1] we are removing pip-and-virtualenv. dib 2.35.0 merged
an accidental breakage for Fedora [2]. We might as well use this as
an opportunity to have this as a "bare" test platform; where we leave
configuration of pip/virtualenv up to jobs. This will be alongside
the ubuntu-bionic-plain images (see
I85438baf5bb31790a56fe5b38327361f0a2398e9).
[1] https://docs.opendev.org/opendev/infra-specs/latest/specs/cleanup-test-node-python.html
[2] https://review.opendev.org/716795
Change-Id: I56a2495e9c768d744ac39073c42a5a1754612f70
Add Fedora 31 to the opendev builder, which is currently the only
container builder that can build this image.
Depends-On: https://review.opendev.org/716104
Change-Id: I811aa3f796e3d1a3a17832bdc038853537f48497
Add a config for nb04.opendev.org that has *only* the Fedora image
unpaused. This is to be the new container-based builder, where we
only want it to build/manage this image, for now.
Change-Id: I7fce3a616ce52dce3bd3639bad37124a8bb1909b
Story: #2007407
Task: #39064