This should only be landed once we've landed the dependency and
confirmed all clouds have the new key value.
This does our semi regular key rotation.
Depends-On: https://review.opendev.org/727865
Change-Id: Ic55c96ad5dd867b70fa52c396e792d5a2e2e0470
Focal images were built with [0] and the result looks successful, so
let's start launching them.
[0] https://review.opendev.org/720719
Change-Id: I2b825178df230d13d75e782c60dd247e6d65ac8b
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
The new Open Edge provider, replacing Fortnebula, is likely ready
for workloads. Start with a maximum of one for each of its main and
custom pools to make sure things are working as expected before we
try to increase load there.
Change-Id: I5578881d52f56dfeb5c5254bfa417c90fa27ebe5
The airship jobs are expected to need 1x32GB ram instance + 3x16GB ram
instances each. The goal is to run 4 jobs concurrently which gives us 16
max-instances in the airship pool. We set the main pool to max 10
instances of the smaller 8GB ram instances to act as canaries in the
main pool.
Change-Id: Ie0293d0523f8a9a738015035725ea2e40b152d3d
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 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
Now we seem to have issues with IPv6 connectivity from test nodes to the mirror.
This reverts commit c7576c86b5f75b77abaa551f8b53324c163b1316.
Change-Id: I80da39c69d58dc3e57cc49092ed3d5ea6b2d1593
Limestone is currently our only ipv6-only provider. Debugging
issues that only occur in that situation can be difficult depending
on node allocation. Add a debug label so we can request a limestone
node in these circumstances.
Change-Id: I1e431431779a052ebbacaee1cf2b830fdcb2003a
IPv4 network connectivity seems to be restored to the mirror now.
This reverts commit c50fce14a28b70f43c08e361127ea8efd024c600.
Change-Id: I36ef83bc7f3ae2ddde7b86a4c1e33aa5c8035fe9
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
This change adds two new lables nested-virt-ubuntu-bionic
and nested-virt-centos-7 to fort nebula, limestone adn vexxhost.
currently jobs that require nested virt to function mus use provider
specific lables to ensure the job can execute correctly.
The addtion of common nested virt lables will allow more redundency
ensuring that if a specific provider is offline the node requests can
be fullfiled by the remaining providers. These new lables are identical
to the existing centos-7 and ubuntu-bionic lables. it is intended that
most jobs should continute to use the non nested virt lables and only
new jobs that require nested virt will use the new lables.
Change-Id: I3795fee1530045363e3f629f0793cbe6e95c23ca