In [0] some repos from the x/* with persistent config errors were
dropped from zuul. Now we also need to remove these repos from the
project definitions within this repo.
[0] I7cfeda034f65056b265ff58acd4607b200152cdc
Change-Id: I2dc3398273f9bf9ca735349fa7809a2f62a34e7d
Define permissions for manila-unmaintained-core, which will
override the global openstack-unmaintained-core for manila
and manila-ui repositories, as allowed by TC resolution 2023-11-14.
Change-Id: I23b445164f8ad82310c0536c29679368631b7616
Signed-off-by: Carlos Eduardo <ces.eduardo98@gmail.com>
On changes like https://review.opendev.org/c/opendev/base-jobs/+/922653
the volvocars tenant is running jobs for the base-jobs repo because that
tenant is loading the project definition for base-jobs. We really only
want the opendev tenant to be running those jobs so we limit what we
include in the volvocars tenant to jobs, secrets, and nodesets. This
matches what we've done in other tenants like zuul and pyca.
While we are in there we update the comment associated with this config
in other tenants to make it a bit more accurate.
Change-Id: Iea24607def728bfd170a6f43da2eb4960d0c89e4
We are trying to phase out this node type. We don't need to have a ready
node sitting around at all times for it.
Change-Id: I74da8de9b9776f2f33e921f3566e5f1c134be88d
In preparation for centos-8-stream cleanup we want to ensure we are not
going to automatically boot more nodes that we need to clean up.
Followup changes will more completely remove the node from nodepool.
Change-Id: I4ea6b7ab449124325cf22129663f86ef7117a5b9
There are some repositories in the openstack tenant which are having
persistent errors in their zuul configuration and nobody seems to be
around to fix these errors. Drop these repos from being handled by zuul
in order to get rid of these errors. They can be added back once fixes
have been proposed to fix the errors, which can still happen in gerrit
despite this change.
Change-Id: I7cfeda034f65056b265ff58acd4607b200152cdc
Following the Vancouver 2023 Forum discussion [0], give the ironic-core
and nova-core gerrit groups -2..+2 votes (but not Workflow) to [access
"refs/heads*"] for python-openstackclient and openstacksdk.
[0] https://etherpad.opendev.org/p/oscsdk-vancouver-forum-2023
Change-Id: I73926490f6b0a8ce4d7b1f86b27210e79868ddb0
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
- Update all ironic-related projects to no longer advertise storyboard
use
- Add proper tag to metalsmith indicating it's a project in the ironic
group
Closes-bug: #2056146
Change-Id: Ic843113c48c109ff6e55acc4252da41176fcc5e6
Address spurious "no valid host" errors for nodes booted in
openmetal-iad3 by specifying the availability zone we intend
Nodepool to use. There is another one which is reserved for our
control plane project/mirror server, and it doesn't allow resource
creation by Nodepool's project.
Change-Id: I3507f5b4557d64c7ebe779743ef397cb4e846cfa
The new openmetal cloud should be ready for production, but let's be
cautious and start with just a single server for now.
Change-Id: I7252dc394b1c2f41991278eacf3b7eb32b886dcd
centos-8-stream is EOL and the upstream repos have been cleaned, thus
the periodic build jobs are failing and we should drop then.
Actually cleaning up the related AFS volume should be done later, when
all other centos-8 jobs have been deleted.
Change-Id: I7c9bc3fcb5aa178c5af44da8a47eb882598c6c3e
There are currently some image upload issues for the rax-dfw region.
Since there is an issue in nodepool that causes uploads to other
provider getting blocked by this (see [0]), move the rax providers to
the end of the list, so all other providers will be updated before
hittinh the issue.
[0] https://review.opendev.org/c/zuul/nodepool/+/922242
Change-Id: Ib8bec7ea2afd5b4569bddb9a4feea6bb07a280f3
When we had some issues with image uploads to rax-iad last year, we
needed to configure it with a dedicated list of diskimages in order to
be able to add "pause: true" statements to those. When the issue was
resolved, we only dropped the pause statements instead of reverting to
use the original list shared across all providers [0]. This is getting
fixed now.
[0] Ia2b737e197483f9080b719bab0ca23461850e157
Change-Id: Ibc1a11d04d5258ca503f8cd5b5fe7a30eb99bc56
The images for centos-8-stream and gentoo are no longer buildable and
nodepool deleted the old "raw" versions of it in order to save space, so
these currently cannot be uploaded to the new openmetal cloud.
Add a reduced list of images as a temporary workaround, this can be
reverted once the old images have been cleaned out globally.
Also add an explicit "pause: true" stanza to the gentoo image build
which so far has only been paused manually.
Change-Id: I4c67940cb0ff9ead6ae2274e00e6f48e7cbcce89
Each individual repo of Puppet OpenStack project has its own launchpad
project. Drop the project group so that each project is linked to
the appropriate project.
Note that the group override is kept for puppet-openstack_extras but
adjusted, because of difference between the repository name (_extras)
and the project name (-extras).
Change-Id: Iabaaaf678ccb1c2e08999268fc0f4937bb93437e
This is essentially reverting commits bd15ddc and cb4b99b which were
the final stages of winding down and cleaning up the old InMotion
cloud which OpenMetal has replaced, with the cloud name updated (but
region kept the same) and grafyaml data regenerated. It stops short
of actually booting nodes in the new environment until we have a
chance to spot check things once images get uploaded.
Since this is re-adding diskimages back to nl02, I refrained from
including centos-8-stream which is in the progress of being removed,
so that we don't unnecessarily upload images we're not planning to
boot.
Change-Id: If8e9b7105b4c7a13e87ebb4f6c985e821c30a842
CentOS 8 Stream is EOL and they cleaned up the repos for this release
which our mirrors happily mirrored. This means the nodes are no longer
functional without significant intervention. Intead of fixing things we
start the process of removal by stopping the image builds.
Change-Id: I5642a8dd3d539563caeba7a09cb86fe19769b38e
This is the last step in inmotion cloud cleanup. It does leave nl02 as a
nodepool launcher with no active providers. I suspect this is fine and
we'll add the new OpenMetal cloud to nl02 at some point in the future.
The grafana graphs will also need to be manually deleted at some point
as removing the yaml file doesn't remove the dashboard from grafana.
Change-Id: Ib33e0c45c277f77013fe5820b898df03da58b558
Step two in removing the old inmotion cloud is deleting the old images
from the cloud so that Nodepool isn't trying to clean things up after
the cloud has gone away. This should hopefully avoid the need for manual
db cleanup.
Change-Id: Ia1451df866a7c91a652a4d9083e6c78cbfde678e
This is the first step in winding down this cloud. We plan to redeploy
the cloud on top of an entirely new platform and openstack version. We
can't do that in a new cloud adjacent to the existing one; instead we
must tear down the existing cloud and redeploy on the same hardware.
Wind it down gracefully in Nodepool first.
Change-Id: Icdaca06b2a2737f74daf60cb29674f06160c7faf
WanderTracks is an Open Source project for collecting and tracking
information journeys taken.
The intent is for it to support both normal (walking, hiking, driving)
and specialty (sailing, diving) activities, along with collecting
technical information about vessels involved where appropriate. The
existing systems are either hyper-focused on one veritcal, like
saillogger for sailing, or TelsaMate for driving a Tesla, or are *super*
generic GPS trackers, like Traccar, which are great but are essentially
key-value stores.
WanderTracks will allow importing and managing trips either directly
from live collectors, or via import from geojson files. The web
interface will support displaying individual trips or collections of
trips overlaid onto a map. The very-very manual proof of concept of the
collection of trips display can be seen at
https://waterwanders.com/where ... wandertracks is going to be the
generalized and multi-user version of that.
To keep the work on infra-root to a minimum, create all the repos we're
going to need up front:
wandertracks/system-config - Ansible for Zuul CD
wandertracks/signalk-wandertracks - SignalK Data collection Plugin
wandertracks/wandertracks - API service
wandertracks/wandertracks-web - Web UI
wandertracks/wanders.cloud - Multi-tenant site built on wandertracks
waterwanders/waterwanders - Single-tenant site using backend APIs
Change-Id: I72f0491fa96c97cfac1bf20e6b92912dd087b589
This is part of the post Gerrit 3.9 upgrade. We need to keep jeepyb in
alignment with the state of our gerrit and have it trigger the correct
jobs.
Change-Id: Ic383f538c42307f2de552f17cfd13e1bd1e37924
Latest git packages on Ubuntu (and possibly other locations in the
future) don't allow locally cloning repos owned by a different user by
default. Attempting to do so results in this error:
fatal: detected dubious ownership in repository at '/opt/git/opendev.org/foo/bar/.git'
To add an exception for this directory, call:
git config --global --add safe.directory /opt/git/opendev.org/foo/bar/.git
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Currently the /opt/git repos are owned by root:root. We expect that
zuul will be the most common user to interact with these cached repos so
we chown to zuul:zuul in order to avoid these problems as much as
possible. Any cases not using zuul will have to determine a path foward
for that special circumstances.
Change-Id: I7cb21869bae42baed5027a9380f60762ab8944e0
as a slight tweak to:
https://review.opendev.org/c/openstack/project-config/+/910212
reasoning: we don't need voting for backports
on stable or unmaintained branches
Change-Id: I10587e0ebd3872a208c04554e17fa44f3a5547f2
Signed-off-by: Sven Kieske <kieske@osism.tech>
dns-root-data has been demoted to a "Recommends" dependency of
unbound, which we don't install. Sadly the default unbound
configuration is broken without it.
Change-Id: Ie285d1c058c4ad7c6579f25cf24884d8e396e1dc
The provider-specific label variants designating nested virt
acceleration support or larger flavors are unused by nl02, so delete
them to reduce confusion.
Change-Id: Id3ac994216624e32d83ae9066d3e77f713cc7245
Build images and boot ubuntu-noble everywhere we do for
ubuntu-jammy. Drop the kernel boot parameter override we use on
Jammy since it's default in the kernel versions included in Noble
now.
Change-Id: I3b9d01a111e66290cae16f7f4f58ba0c6f2cacd8