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
VEXXHOST no longer offers to flavors of instances, and it makes more
sense to use the standard flavors. This flavor has 8 cores, 32GB
of memory and 160GB of disk space. It doesn't make sense to have
a smaller memory/disk allocation as the hypervisors are ratio'd out
to work with this configuration.
Change-Id: Ie424e7d6236c00678d92b34ed33dafaf966180fa
This reverts commit fa9e37d729.
Still seeing a significant percentage of nodes becoming
unreachable/broken during builds, turn it back off again while we
dig deeper in service logs.
Change-Id: Ib0ba945e91956cb76504893bd9924d4b70d4ffb6
This reverts commit 91d811b005.
We're going to try this again to see if the duplicate IPs (and resulting
ARP fights) persist. This is being done to balance against long queues
in Zuul.
Change-Id: I8d48371b592a54809f9845baf6110dc8fb7deca2
The previously observed problem (looks like rogue server instances
again) still appears to persist there.
This reverts commit 492e9eeba1.
Change-Id: I8c70268af93f4fe32a730834b405942602417a82
We're seeing a high incidence of job nodes return RESULT_UNREACHABLE
mid-build, enough to cause frequent RETRY_LIMIT results for changes.
Temporarily cease running jobs there until we/they can work out
whatever connectivity or rogue instance issues are causing this.
Change-Id: I4afd92ee64911f0611733ed9c92ec0a4bada54f5
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
Nova CPU service fails to boot instances on ARM64 with the following
error log message:
qemu-kvm: cannot set up guest memory 'mach-virt.ram': Cannot allocate memory
This was observed while testing Octavia-enabled devstack deployments in
CI [1]. This patch adds a 16 GB RAM label for CentOS 8, similarly to
existing 16 GB RAM Bionic label introduced in [2].
[1] https://review.opendev.org/#/c/747629/
[2] https://review.opendev.org/#/c/714346/
Change-Id: If594fe44ad739b517ea56ebcd28008406b3b55ad
We will be performing hardware maintenance.
This require us to shutdown some of the compute nodes,
therefore reducing effective compute capacity.
Change-Id: I017511874c98fa7ab27f811674cf67b8cdbd118d
Carrier issues are preventing ca-ymq-1 instances, including the
mirror server, from reaching some IPv6 destinations such as PyPI.
Temporarily stop booting job nodes there until the routing problem
has been addressed.
Change-Id: Iea8b96f4a1551ff8bee5d61163eeb8ddfa57198b
These labels were not migrated when we moved to running inside our new
hardware inside the Montreal datacenter.
Those largely should disappear as soon as we move our operator
development to be multi-node to avoid having a 'unicorn' flavor. We'd
like to use them temporarily to unblock our progress for now.
Change-Id: Ie29a071b1b8916e0d09990b97bf589bf2b0fc50a
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
This has been set to 0 for some time, and after discussion with kevinz
it has been determined this cloud won't come back. Remove it.
Change-Id: Ic19ffc6dda130ecba2e70bed6bac9fe7a8b8cba9
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
DevStack test need a large RAM.
In 8G VM we meet several weird issue.
Change-Id: I10bb5e8d171bbc84baa28678889708c32833d2bf
Signed-off-by: Kevin Zhao <kevin.zhao@linaro.org>
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
We have enough quota for 44 8-node hosts; give ourselves a little
headroom. The mirror host is up and responding.
Story: #2007195
Task: #38357
Change-Id: Ib6797c5bcc90d492c4a47e173b93b3867548879f
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
linaro-london got new Ceph setup so we can go back to 8vcpu per node.
This reverts commit 1900f336f7.
Change-Id: I2e70dd03600e5168eb47d7d2fff2f1c364f0f301
This reverts commit 9776609508.
We've rebuilt the inap mirror with a large local disk. This should be
big enough to house our caches and provide the best possible performance
(local disk is backed against raid'd ssds).
Change-Id: I066a34a459a2d8144c2faa1c1dd569845ab055cd
We are still filling the disk up on the mirror beacuse htcacheclean
isn't able to clean things up quickly enough before activity runs us
into the filesystem size limit.
Let's disable the region again while we sort out how to add more disk
and possibly more io performance to the cache filesystem.
Change-Id: I3051f5c33bf93e390e9e16f36de21de1eb78f0b0
This reverts commit 4fd427f584.
We have updated the mirror node to have a 100GB apache cache and 100GB
openafs cache to match the other mirrors.
Change-Id: Ic0f96b28c9b4481155d85428011568895e63adad
Temporarily stop building new job nodes here until we can add space
for Apache and OpenAFS caches to the new mirror server.
This reverts commit 8b5e738412.
Change-Id: Iecc8e302f8d6ac374a81deaeddf14bcd997829b2
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
Clark Boylan