Zuul is deployed by scap from integration/zuul/deploy which hold all the python dependencies in a tarball. Refreshing the dependencies is done via a Makefile and a docker image. As part of upgrading the underlying OS from Buster โ Bullseye (T334517) we need to make sure the system still works properly and adjust it for Bullseye.
There are a few steps:
- Last time I wanted to be able to reuse wheels (T259611) wish has lead to https://gerrit.wikimedia.org/r/c/operations/docker-images/production-images/+/605653 . That is doable by using PIP_FIND_LINKS instead of messing up with the upstream container.
- We need a python2.7 build image based on Bullseye
- Build artifacts for Bullseye
- The python2.7 provided by Bullseye is a minimal one, we might be missing modules?
-
Test it on a WMCS instance!In the end we tested the generated Python wheels using containers. We managed to install and start a basic Zuul server/merger pair on bullseye containers