Drop the python3.9 container images (python-builder, python-base,
uwsgi-base). At this point nothing is building off of these images and
we should be using python3.11 for anything new.
Note that python3.10 can be cleaned up once zuul-registry and
openstackclient stop building on top of python3.10. Everything else
appears to be python3.11 at this point.
Change-Id: Id30b616ec336a5599766fb808f55e228da686439
This adds a python-base:3.11-bookworm-debug image, which is built
on the normal python:3.11-bookworm upstream image instead of the
slim upstream image. The normal image includes debug symbols for
the python interpreter which is compiled during its build phase,
so this is the best way to get an opendev python-base image with
debug symbols.
Change-Id: I1d89ac947cd3bea8a468f3ee022fb4cc93bece1f
Refstack doesn't rely on much in the base operating system as far as I
can tell. That said refstack seems to test with python3.10 and not 3.11
so this may not work, but our testing should give us a good idea. Bump
these things up as we are updating all the services we can in order to
eventually cleanup image builds for old debian and old python.
Change-Id: Id39027691484e8f81bd097c174f0a4a1e81463af
Gerrit just released new point versions for all supported branches
including an update of 3.7 to 3.7.5. We also bump our 3.8 image up to
3.8.2 (note this isn't used in production, only for testing of the
upgrade to 3.8 currently).
Release notes can be found here:
https://www.gerritcodereview.com/3.7.html#375https://www.gerritcodereview.com/3.8.html#382
The updates look minor for us, but there are some bug fixes so worth
updating. We might want to land this change as well as the bookworm
update together in order to do a single short gerrit downtime to get all
of these updates deployed in production.
Change-Id: Ib4ccfe12db94d032fc4743a7aafdf90735aecfa3
We keep the same python 3.11 version we had on bullseye but switch the
rest of the userspace to bookworm. Since the python version doesn't
change this should have minimal impact.
Change-Id: I59ad8c2a92159f51d567dd0212e2ab8bec1b45b1
In "Add a uwsgi-base container image"
(08a807/Iaf6d31a3d119f6b7e87b54cda1969a9994110dad) The uWSGI containers
added an explicit, but redundant, trailing '.*' for the files settings
of the uWSGI containers. This change is largely cosmetic but for
style consistency let's remove them.
Change-Id: I04162384fbf6a09cffc1aec76777dd6e21752a0e
With the merging of [1] we observed that the images built
(python-3.{9,10,11}-bookworm) were not then promoted. This was fixed
in [2] as the assumption is that the promotion jobs didn't trigger
because the files modified in [1] don't match the needed files. This
change adds the zuul configuration file to the list of relevant files.
We're not 100% sure that this will work but it's worth a try.
[1] https://review.opendev.org/c/opendev/system-config/+/888102
[2] https://review.opendev.org/c/opendev/system-config/+/888633
Change-Id: I958a0af6fbad80f8152438aaee6b7268432f64d5
Gerrit 3.8 has been released for a bit. Update our 3.8 image builds to
pull the latest 3.8.1 version for testing.
Gerrit 3.7.4 has also been released. We update our 3.7 images to 3.7.4.
Note this is our production image and this update will affect prod
unlike the 3.8.0 update. Changelog is here:
https://www.gerritcodereview.com/3.7.html#374
The only breaking change is related to prometheus metrics which we
aren't using (yet).
Change-Id: I52854ed097e295c070e642808e9dae793dc8a716
The Current python*bullseye container provides lack the distribution
name. This prevents zuul from correctly identifying and using new
images in speculative builds.
Fix that.
Change-Id: Iad2d84f217f4b807bf967ef28c32b2c1d05f16c5
This reverts commit 5842ce3ea61db14ce450b8ec9a19eb744f58fb2f.
OpenDev is moving back to docker.io in order to keep functional
speculative container image testing.
Change-Id: I748772eb92ddb608df8e10b84ce814ae17af9e18
This reverts commit 4a762a6a8a9bc6c4364e8a4b3588326e4fc40982.
A partial revert of 13cfceaea43f1ddc1dc4431da843e9d92e73e426 is also
performed to swap out zookeeper-statsd without affecting other images.
We perform this revert because Docker cannot do speculative gating of
images hosted anywhere but on docker.io. Speculative testing of
container images is an important feature that we wish to keep so revert
until we can stop relying on Docker.
Change-Id: I7ceafdb7cf1dfd4812ea8f12f273f01045ca89a2
This reverts commit 7f88fc7d4aa332ba51ed45f2689d15819ed19692.
We found a deficiency in Docker when working with images hosted outside
of docker.io which necessitates this revert.
Change-Id: I8b16fe3e5297cab04685e0ceb6b8277a2754b3fb
This reverts commit b3a861c0e00b409496ded5c774ac3cb2382f319b.
We found deficiencies in Docker when operating against images hosted
outside of docker.io. We are reverting as a result.
Change-Id: Ic690fc7ff9eb5b5ed9c1162d1f4b97edf6f2cd6c
This moves accessbot, ircbot, and matrix-eavesdrop to quay.io. We also
update the base image location to source from quay.io as these images
have moved.
Change-Id: I03fdfd382e42542f1da25188deabe017d0cbd772
The migration of the zookeeper-statsd image itself already happened as
it was our test case. That said I found a small typo that needs fixing
(and will clean up the extra image that was created later). We also
update zookeeper-statsd to pull the base python image from quay.io
The real fun happens with haproxy-statsd. We update the image to pull
the python base image from quay.io and set it up to publish to quay.io
itself.
Change-Id: Ie0c119ac309837baef850236f7d5ba6b9da97ce0
We are moving our images to quay.io. The assets image is used by other
image builds so we want to treat this like a base image and update it
early in the process. This will reduce overall churn in the process.
Change-Id: Id9630243f60b280647c493abaccf0ece3d56d40c
We are moving our images to quay.io. This makes the move for our base
python images. Note once we move these images we should attempt to
quickly update any of the images that depend on these images. This will
minimize the time period where we might be pulling outdated base images.
Change-Id: I03c8053345abf6c94a8e904917f53caa5693ce89
This adds new jobs for publishing our images to quay.io. We also add a
secret with the necessary items (password for images pushes, API token
for repo creation). Then we update the zookeeper-statsd image as the
first image to get moved to quay.io. This should exercise things and
ensure it is working for us.
Note we don't try to update all of the images at once as we have many
images managed in this one repository and debugging every one of them
after a single merge just seems like pain. Instead, we'll start with one
image and go from there.
Depends-On: https://review.opendev.org/c/opendev/base-jobs/+/881522
Change-Id: I5198942f184df72543185a0ea88d50f9dc2d9421
This commits update haproxy-statsd Dockerfile to use Python 3.11 images
instead of older 3.9 one. It's part of the effort to update Python
version to 3.10 or later.
Change-Id: I65d469d18d1cf10d7f404b12afdeb5e6d8580bd6
Gerrit 3.8 isn't officially released yet, but they have relaesed their
third release candidate. Seems like a good time to start building a 3.8
image and testing it.
Change-Id: I11bcd35379cecde135f471a840b03937166b6663
We've been running Gerrit 3.7 for some time now and seem very unlikely
to revert at this point. Clean up the Gerrit 3.6 image builds as we
don't need them anymore.
THis change also comments out the 3.6 -> 3.8 upgrade job. Followup
changes will add 3.8 image builds and test the 3.7 -> 3.8 upgrade
process.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/881595
Change-Id: I759b34e48dcede7ffaa66c83da01b81c4fed4b4f
This commits update hound Dockerfile to use Python 3.11 images instead
of older 3.9 one. It's part of the effort to update Python version to
3.10 or later.
Change-Id: Idf5076709c55d3327c69c6e8160a8348b6640ca7
This commits update accessbot Dockerfile to use Python 3.11 images
instead of older 3.9 one. It's part of the effort to update Python
version to 3.10 or later.
Change-Id: I983ca73237b8a11ae3885505f549d8b0b16c144f
This is mostly a bookkeeping update, but it reflects that upstream made
a release to fix the related changes issue.
https://www.gerritcodereview.com/3.7.html#372
Change-Id: Iecbda339d0af4cc625df7be3925010ce643808bd
We actually just build 3.6.4 and 3.7.1 images using 3.6.3 and 3.7.0
versions of plugins. We also deployed the resulting 3.6.4 image to prod.
Luckily for us 3.6.3 plugin tags match 3.6.4 and 3.7.0 tags match 3.7.1.
There was one exception which we were alredy checking out master for in
order to fix build errors. Now that there is a new reviewnotes tag for
3.6.4 we can drop the master checkout for that plugin and use the tag.
TL;DR this should be a noop for our images but is nice bookkeeping to
avoid surprises.
Change-Id: Ica8b3605ecb0f3f93747b904c39913800d1eee4e
This is done for a number of reasons. First it will allow us to update
the python version used in the images as we can have a 3.10 builder and
base images (but not a 3.10 openjdk:11 image). Second it will allow us
to easily switch to openjdk 17 by simply updating the package we install
and some paths for the jdk location.
The goal here is to have more control over the images so that we can do
things like change python and java versions when we want to.
Depends-On: https://review.opendev.org/c/opendev/jeepyb/+/870873
Change-Id: I7ea2658caf71336d582c01be17a91759e9ac2043
This checks out master of the reviewnotes plugin which includes fixes
for flogger compile time log string checks brought in by a recent Bazel
update. Unfortauntely no 3.6.x tag includes these fixes yet. Judging by
the change log this should be safe though.
Change-Id: I71d4e7732a49236af9f8f558743c19f3dad9818e