We will meet on November 12, 2024 at 19:00 UTC in #opendev-meeting with this agenda: == Agenda for next meeting == * Announcements * Actions from last meeting * Specs Review * Topics ** Zuul-launcher image builds (corvus 20240910) *** Configs are going in opendev/zuul-jobs *** Need jobs to build additional images. Currently only x86 Debian Bullseye is being built ** Backup Server Pruning (clarkb 20241008) *** The smaller of the two backup servers is needing manual pruning multiple times a month now (the interval is between 2 and 3 weeks) *** There are older server backup dirs present on that server that we could delete (as well as removal of the corresponding login user for that server) **** ask01, ethercalc02, etherpad01, gitea01, lists, review-dev01, and review01 **** https://review.opendev.org/c/opendev/system-config/+/933700 Backup deletions managed through Ansible **** https://review.opendev.org/c/opendev/system-config/+/934768 Handle backup verification for purged backups ** Upgrading Old Servers (clarkb 20230627) *** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades **** wiki.openstack.org: https://etherpad.opendev.org/p/opendev-mediawiki-upgrade **** tonyb looking at cacti after wiki *** https://etherpad.opendev.org/p/opendev-focal-server-upgrades ** Docker compose plugin with podman service for servers (corvus 20241001) *** https://review.opendev.org/923084 is a demo (in the Zuul repo) of using docker compose v2 plugin with system podman service *** This would let us host opendev images on quay.io (or any non-dockerhub site) and use speculative images *** Some caveats (seen in the change): **** unconfined apparmor profile to work around https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/2040483 **** buildx startup probably not an issue since we don't use docker compose image builds: https://github.com/docker/buildx/issues/344 **** need to set DOCKER_HOST env variable (system-wide bashrc? maybe a docker context? other options?) *** Do we want to proceed? Any blockers? **** Plan is to test the switch with a less consequential service (paste maybe). Upgrade the hosting server to Noble first if necessary. ** Enabling mailman3 bounce processing (frickler 20241030) *** This would help getting rid of subscriptions that are no longer valid *** Example configuration page: https://lists.openstack.org/mailman3/lists/openstack-discuss.lists.openstack... (needs admin access) *** Enabled on service-discuss without changing any defaults. Next step is to enable elsewhere once we are happy service-discuss isn't negatively impacted. ** Intermediate Insecure CI Registry Pruning (clarkb 20241112) *** Backing swift container hasn't been pruned in many years *** Recent bugfix as well as addition to dry run pruning have landed in zuul-registry's prune command *** Announced date for Friday pruning. Do we want to start a dry run sooner (tomorrow?) ** Gerrit 3.10 Upgrade Planning (clarkb 20241105) *** https://etherpad.opendev.org/p/gerrit-upgrade-3.10 *** Feedback welcome on the process and listed concerns as well as the mitigations or assertions they don't affect us. *** Pencilled in 1600UTC December 6, 2024 for the upgrade to occur. ** RTD Build Trigger Requests (clarkb 20241005) *** RTD build requests are failing but when manually reproduced seem to work. Appears to be some problem specific to the Ansible uri module. *** New theory is that it could be client fingerprinting by the CDN. *** https://review.opendev.org/c/zuul/zuul-jobs/+/934243 switch to curl instead of ansible uri module ** promote-openstack-manuals-developer fails with Ansible errors (clarkb 20241112) *** promote-openstack-manuals-developer job promotes developer documentation that live in a different location from the typical openstack docs *** https://zuul.opendev.org/t/openstack/build/1a84db5d173c4777b9d730923721b04a Example failure * Open discussion