We will meet with this agenda on February 3, 2026 at 19:00 UTC in #opendev-meeting:
== Agenda for next meeting ==
* Announcements
** Service Coordinator Nominations Opened Today (February 3)
*** https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/t…
* Actions from last meeting
* Specs Review
* Topics
** Upgrading Old Servers (clarkb 20230627)
*** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades
*** https://etherpad.opendev.org/p/opendev-focal-server-upgrades
*** https://etherpad.opendev.org/p/opendev-server-replacement-sprint
**** wiki.openstack.org: https://etherpad.opendev.org/p/opendev-mediawiki-upgrade
**** tonyb looking at cacti after wiki
*** Next on the list are graphite and backup servers
*** Can probably spin up new backup servers alongside the old ones then migrate the old volumes off the old servers to the new ones and finally delete the old servers. Just need to double check borg version support matrix details and also what adding new backup servers will do to our cron job setups for backups.
*** Remember to use launch-node's --config-drive flag when booting new Noble nodes in Rax Classic
** Moving OpenDev Synchronous Communication to Matrix (clarkb 20250520)
*** We have moved to Matrix
*** Minimal traffic has remained on IRC
*** Tools like Gerritbot, statusbot, and eavesdropping seem to be working well
*** Have we noticed any problems?
** zuul-registry Image Pruning of OCI Images (clarkb 20251216)
*** The problem now is that we aren't handling manifest lists so they get pruned and 404
*** https://review.opendev.org/c/zuul/zuul-registry/+/975088 handle manifest lists in addition to manifests themselves.
** Adding Bad Crawler Honeypots to our Sites (clarkb 20251216)
*** https://review.opendev.org/c/opendev/system-config/+/974942 More aggressive lure setup via comment in the html
** MariaDB backups over TCP instead of Unix Socket (clarkb 20260127)
*** We noticed that if mariadb's container image is updated during mysqldumps for backups that backup may never exit and conclude
*** Theory is that this is happening because the unix socket is held open by the linux kernel then nothing further is written to it so everything hangs around
*** Proposed fix is to run mysqldump over TCP. We are testing this with lodgeit to start.
*** https://review.opendev.org/c/opendev/system-config/+/973541 This will apply the change to all services if lodgeit looks happy.
** Updating All of Our Containers to Trixie (clarkb 20260203)
*** Trixie has been working well on services like Etherpad and Gerrit
*** Let's update all of our containers to Trixie so that we can drop bookworm builds
*** https://review.opendev.org/c/opendev/system-config/+/975319 Update the base python images First
*** https://review.opendev.org/q/hashtag:%22opendev-trixie%22+status:open
*** Should we retire Gear rather than update its container image? Or maybe just stop building a container for geard?
** Gerrit 3.11.8 (clarkb 20260203)
*** There is a new Gerrit 3.11.8 bugfix release available.
*** https://review.opendev.org/c/opendev/system-config/+/975176 Upgrade to Gerrit 3.11.8
*** This change also converts us from building from stable-3.11 to checking out the v3.11.8 tag
*** The idea is that this will prevent unexpected Gerrit updates from sneaking into Gerrit image rebuilds if those happen for unrelated reasons.
** Gerrit change.maxUpdate (clarkb 20260203)
*** Gerrit's notedb by default allows 1000 updates to a single change. This is configured by change.maxUpdates in the gerrit server config
*** This Cinder change has hit that limit: https://review.opendev.org/c/openstack/cinder/+/926844
*** The limit is set for performance reasons. It looks like Cinder may have a number of possibly outdated and never succeeding third party CI systems. Maybe we can disable those before we think about updating limits.
** Checking CPU Counts in Our Base Zuul Job (clarkb 20260203)
*** https://review.opendev.org/c/opendev/base-jobs/+/975474
** Pre PTG Planning (clarkb 20260203)
*** Would March 2-4 or March 9-11 work for a few days of snyc up on meetpad?
*** We would probably do two or three hours a day and the Tuesday sync up would replace our regularly scheduled team meeting.
* Open discussion