Once the opendev launchers are handling these duties and these servers
have all been removed from the system-config inventory we can go ahead
and land this change to clean up the unused config files.
Change-Id: I9792620eea81a07b6cbbfee37c08807114d2b390
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
This reverts commit a7edbb7a18.
Merge once the mirror server in citycloud-kna1 is reachable and
working correctly.
Change-Id: I72c8344d60a3f6fe184b1ffc8a64c8f8a8d78c80
Our mirror server in citycloud-kna1 is unreachable, even after a
reboot. The console log shows it booted fine and started services,
but connectivity seems to die somewhere in Citynetwork's KNA3 core
routers. For now, stop booting new job nodes here until we and the
provider can work out what's transpired.
Change-Id: I7336ecc4c7b0ea39c49aa501c1d0e4f96c9eb2a8
Although the servers are turned down to 0, the lack of response from
the cloud is causing problems for nodepool-builder trying to upload
images. Remove the entries completely to avoid this.
Change-Id: I8a82e852b389f3499e32f822cd7aa9e5792ea7c6
This reverts commit ef5cc14205.
We now automatically discard nodes which lack working IPv4
connectivity, the condition which was previously causing occasional
failures in this provider.
Change-Id: I7a7db0dbc1ff6203855eb5dee40d234a26335db0
We keep getting nodes than don't have an IPv4 address which
breaks various jobs. Disable until we can get that fixed.
Change-Id: I5e6b44cbe9a33fe29dc3c989b43c107a1a26599a
The cluster has been upgraded to Bionic. Wore out SSDs have been
replaced. And all nodes are now configured with RAID0 instead of RAID1
to provide additional I/O to nodes.
This reverts commit dd62a5e81e.
Change-Id: I97237aecf2d00ebf8c23f931d7079333d90927fb
This serves as a sanity check that we don't have any fedora-30 usage
hiding somewhere. If this goes in safely then we can remove the image
from the builders.
Change-Id: I09b21e812081f5855a069ca8ab1eedadf090c1b8
We will be working to upgrade the nodes from Xenial to Bionic over
the coming weeks, as well as performing hardware maintenance to
replace wore out SSDs.
Change-Id: I8f12e4467b8f7fbc61ecaf975c6ed6cb6f16c2f0
Ubuntu Focal has a newer libvirt version than Bionic (4.0.0 vs 6.0.0).
By adding a Focal-flavored nested-virt label, features made possible
by a more recent libvirt version can be tested in the gate.
Specifically, whitebox-tempest-plugin tests Nova's hw_video_type image
property. Support for the 'none' value was added in libvirt 4.6.0.
Change-Id: Id48fff64d13c258d9f22908debfad86c5f089bf5
Needed-by: https://review.opendev.org/#/c/742014/
Change [1] added nested virtualization labels for Ubuntu Bionic and
CentOS 7. This patch extends that to CentOS 8.
Additionally, we extend nl04 to include these labels too as OVH is a
nested-virt enabled nodepool provider.
[1] https://review.opendev.org/#/c/683431/
Change-Id: Ibf5ac5fa0371cc70dbe58806d147568278afcfea
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 c7576c86b5.
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
Clark Boylan