The launchers have had this label removed and if things look over there
the last step in the nodepool retirement of this image type is to remove
it from the builders.
Change-Id: Ic9e29cfdc6d8a7e2a009f524ecfb0f93b60e3724
The Leap 15.2 has happened and we should catch up. This depends on our
mirrors being updated first.
Depends-On: https://review.opendev.org/745251
Change-Id: I738f7037d85bd1898770af0a13509aa98a134720
These are no longer necessary after the merge of
I76befd9e2a054798e8e36500b723870f7c7ae328.
Depends-On: https://review.opendev.org/735774
Change-Id: Id98743d6d2884a15e8496bdefb764287f37cd248
We've enabled https on our mirrors. Take advantage of this during our
image builds everywhere we set a mirror but xenial and stretch (they
don't do https out of the box).
Change-Id: I955f47392623c4af9a6f788d078f6d088a0d62cc
As discussed at [1] this removes the pip-and-virtualenv element from
images that still have it.
For now we leave the old templating bits so we can easily revert an
image if there are unavoidable issues.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-May/015157.html
Change-Id: I76befd9e2a054798e8e36500b723870f7c7ae328
Ansible's auto python detection doesn't have logic for SUSE, so it
picks python 2. This means Ansible is running under Python 2 on our
SUSE nodes, which is not what we want. Override this to Python 3
explicitly. If Ansible gets auto-detection for SUSE, we could revert
this.
Change-Id: I9e7074a48bf02d564fecb5d77e0c2d582c261105
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 are ready to drop pip-and-virtualenv from SUSE 15. zuul-jobs is
passing for plain nodes [1] and devstack-based jobs are working
(e.g. keystone jobs tested with [2]).
[1] https://review.opendev.org/724776
[2] https://review.opendev.org/723762
Change-Id: I9fed82a2ba02d5d7882c280645ef7b04a36e0563
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 03a2a71984.
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
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 a follow-on to I811aa3f796e3d1a3a17832bdc038853537f48497; fedora-31
is now built and working on nb04, images are uploaded. Add it to the
main config file, but paused, so the launchers know about it.
Change-Id: I1688b4eb60e35e47d086a3be6c6476aa413497d7
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
We had been relying on the ssh pubkey configured in the nodepool user's
homedir. This being an implicit config caused containerized nodepool
builders to break as they didn't have this config. Switch to explicit
config to avoid this in the future. This is unfortunately quite verbose,
but that will improve with future changes to nodepool.
Change-Id: I67d0c61be9cd05c90a5be937fa4bf77678f89ce5
Story: #2007407
Task: #39072
This reverts commit 9d7592df75 which was
meant to make nb01.opendev.org the only builder of fedora-30, but did
not quite work as expected. This replicated what we do on the ARM64
builds; but what I missed was that the ARM builds have exclusive use
of the ARM clouds -- in this case the new nb01.opendev.org thought
that all the other images in the existing clouds were foreign and
tried to delete them.
Take a different approach; replicate the nodepool.yaml file to a
nb01.opendev.org specific one, but pause everything *but* the
fedora-30 builds. This should make the builder leave everything else
alone, and just try building Fedora, which is what we want for the
initial POC.
Change-Id: I2ccb6aaad5866561fd6ec4118c718ee131c3a5f0
Since all platforms have Python 3, use the new ensure-venv element
from the dependent change to install bindep and os-testr.
Since we are no longer using pip to install anything during the
builder, this drops the dependency on pip-and-virtualenv from
nodepool-base. Avoiding this element is our long-term goal, as it's
modification to system state are problematic in a number of ways. To
maintain the status-quo, the pip-and-virtualenv element is added
explicitly to each build's element list, with a note on it's future.
The current plan for backwards compatability is to replicate the
environment pip-and-virtualenv provides in a base role/job that can be
optionally included. To test this, provide a new node type
"ubuntu-bionic-plain" that will not include the pip-and-virtualenv
element. This is put on just one provider (rax) to minimise impact.
The dependent-change (and a dib release) is required before merge so
the ensure-venv element is available.
Depends-On: https://review.opendev.org/707513
Change-Id: I85438baf5bb31790a56fe5b38327361f0a2398e9
All jobs using Fedora 29 have been removed, we can remove it from
nodepool and thus OpenDev now.
Depends-On: https://review.opendev.org/711969
Change-Id: I75c0713d164c29a47db9a0cdfc43fadb370e81f8
There was a lack of indentation which led to:
Traceback (most recent call last):
File "/usr/local/bin/dib-block-device", line 11, in <module>
sys.exit(main())
File "/usr/local/lib/python3.5/dist-packages/diskimage_builder/block_device/cmd.py", line 120, in main
return bdc.main()
File "/usr/local/lib/python3.5/dist-packages/diskimage_builder/block_device/cmd.py", line 115, in main
self.args.func()
File "/usr/local/lib/python3.5/dist-packages/diskimage_builder/block_device/cmd.py", line 30, in cmd_init
self.bd.cmd_init()
File "/usr/local/lib/python3.5/dist-packages/diskimage_builder/block_device/blockdevice.py", line 260, in cmd_init
self.config = config_tree_to_graph(self.config)
File "/usr/local/lib/python3.5/dist-packages/diskimage_builder/block_device/config.py", line 134, in config_tree_to_graph
"Config entry top-level should be a single dict: %s" % entry)
diskimage_builder.block_device.exception.BlockDeviceSetupException:
Config entry top-level should be a single dict:
{
'base': 'image0',
'partitioning': None,
'partitions': [{'flags': ['boot', 'primary'],
'mkfs': {'mount': {'fstab': {'options': 'defaults,nobarrier,noatime', 'fsck-passno': 1}, 'mount_point': '/'}},
'size': '100%', 'name': 'root'}],
'label': 'mbr'}
Note the paritioning value is None rather than a dict with those keys in
it.
Change-Id: I543222402a8e4d08cf075b2ed7f7c45d705799ca
It appears that the cloud launcher has configured networking on this
cloud. Next step is to uplaod images and plan out labels. We'll start at
max-servers 0 in order to get images uploaded. Then work with cloud
provider and airship to sort out quotas and max-servers values from
there.
Change-Id: Ic2f8acb64dc23c238676729839f55d7b592e0d15
This is an attempt to get better fs IO performance out of our images.
Start with this on the buster image as this gives us a low impact test
if things go wrong, but also provides a system similar ish to ubuntu.
Specifically we disable barriers and set noatime as we don't care about
data reliability after crashes on our test nodes (they are single use)
and atime shouldn't matter for our CI system.
Change-Id: Ied44590c6260691a738ed105f8da0f4765b6c162
This removes trusty from the repo and thus from OpenDev.
Afterwards the AFS volume mirror.wheel.trustyx64 can be deleted.
Depends-On: https://review.opendev.org/702771
Depends-On: https://review.opendev.org/702818
Change-Id: I3fa4c26b0c8aeacf1af76f9046ea98edb2fcdbd0
The opensuse-150 image is being removed as the 15.0 release is EOL.
Similar to centos the expectation is that users keep up to date with
minor releases. For this we have the opensuse-15 image which should be
used instead.
Depends-On: https://review.opendev.org/#/c/682844/
Change-Id: I8db99f8f2fd4b1b7b9a5e06148ca2dc185ed682b
This provider has already been disabled in these config files by
setting max-servers to 0 and diskimages to []. There are errors
in the nodepool logs about not being able to contact this provider
now since it appears disabled/gone, so time to remove the entries.
Change-Id: I2adbb575592eefe6958157d8fb007d0b50998e82
A long time ago in a galaxy far far away there existed the planet
hpcloud. In order to breath the atmosphere of this planet VM images had
to be compatible with the qcow2 0.10 version specification. Since then
this planet has been visited by a death star and none of our images are
expected to visit planets with this requirement.
Go ahead and stop producing VM images that can live on HPCloud.
Note that our Ubuntu and Debian images had already stopped doing this so
this should be safe. Improvements we should see as a result include
smaller images.
Change-Id: I6888b478e93021bbede4a647af990774126b0245
Diskimage-builder defaults to a assuming the Debian security
archive's suite name will be something like stretch/updates or
buster/updates but ours are just stretch and buster without any
second subcomponent, so override this to an empty string instead.
Depends-On: https://review.opendev.org/688816
Change-Id: I34488e55c1b9bfe4c253c4d51346966fa69f1170
This becomes the default with
Ic996956da4b85f7d95179b8df9881d5f52c091af, so the explicit set is not
longer required.
Change-Id: I26d19a5518ff69af2cbe6eed44be43c25d291314
Diskimage-builder defaults to a separate mirror value for the Debian
security archive, so override it independently of our general mirror
URL. It's really a different URL anyway.
Change-Id: Ia500f564d761f56bc55acc9b1c969dbd364a0eba
Depends-On: https://review.opendev.org/686328
Gentoo has updates it's system profiles, we need to follow this in order
to make our builds work again.
TODO: Update the image name accordingly or switch to a more generic
name.
[0] https://review.opendev.org/677290
Change-Id: Id062f61b82242220e0105d3ef4c7ff53efceb587
Carlos Goncalves
Clark Boylan
Lee Yarwood
Ian Wienand
Dr. Jens Harbott
Monty Taylor
James E. Blair
Andreas Jaeger
Donny Davis
David Shrewsbury
Jeremy Stanley