Team Meeting Agenda for May 26, 2026
We will meet with this agenda on May 26, 2026 at 19:00 UTC in #opendev-meeting: == Agenda for next meeting == * Announcements * Actions from last meeting * Specs Review * Topics ** Upgrading Old Servers (clarkb 20230627) *** https://etherpad.opendev.org/p/opendev-server-upgrade-planning Central tracking document which may link to more host specific documents *** Next on the list are graphite and backup servers *** Backup server replacement is in progress. Should proceed soon. We'll then need to double check backups function as expected against the new server. *** Remember to use launch-node's --config-drive flag when booting new Noble nodes in Rax Classic ** Deploying a Prometheus for Server Metrics (clarkb 20260331) *** https://review.opendev.org/c/opendev/system-config/+/980840 *** This change and its child deploy prometheus with node exporter to collect server metrics *** mnasiadka has proposed we use GrepTimeDB in conjunction with Prometheus to collect metrics over a longer period of time ** Upgrade Ansible to v9 (clarkb 20260310) *** https://docs.ansible.com/projects/ansible/latest/reference_appendices/releas... *** This has mostly gone well. *** https://review.opendev.org/c/opendev/system-config/+/989022 and https://review.opendev.org/c/opendev/system-config/+/988698/ should address the last known issue with the update. ** Gerrit Account Cleanups (clarkb 20260317) *** Since the upgrade to Gerrit notedb we've had account inconsistencies that prevent us from push to the external ids ref/table directly. *** clarkb did a bunch of work to get the number down from hundreds to about 33 consistency errors before stalling out. *** The tail was the most difficult as it wasn't clear what the more appropriate fix for each account would be *** Since then it has been years and those accounts are likely inactive and unused. We can rerun the Gerrit consistency check, feed the info back through our audit script then decide if we need to be careful with any of these accounts *** Chances are we can simply disable them all and remove the conflicting external ids. *** If we take good notes we can reconstruct the accounts as appropriate after the fact without Gerrit downtime should one of these users show up and wonder what happened. ** Gerrit 3.13 Upgrade Planning (clarkb 20260414) *** Clarkb would like to target a 3.13 upgrade for the end of May/early June. How does Friday June 5 look for others? *** Gerrit 3.13 removes support for Robot comments so Zuul will start making normal inline comments *** This also means that the Zuul restarts performed as part of the upgrade process are actually required when we upgrade to 3.13 to get Zuul's Gerrit version detection sorted out. *** https://etherpad.opendev.org/p/gerrit-upgrade-3.13 Beginnings of an upgrade plan document *** 3.12.7 to 3.13.6 upgrades looked good. The next steps are announcing the upgrade and working through the minor TODOs in the etherpad plan document. ** Etherpad 3.1.0 Upgrade (clarkb 20260519) *** 2.7.3 introduced session cleanups in the database. But this created OOMs. We have disabled this feature. It should be fixed in the release after 3.1.0. *** 3.0.0 and 3.1.0 have been released *** https://github.com/ether/etherpad/blob/v3.1.0/CHANGELOG.md Big change appears to be the ability for etherpad to self update. I assume we would disable this and control etherpad via container images. ** Gitea 1.26.2 Upgrade (clarkb 20260526) *** https://review.opendev.org/c/opendev/system-config/+/989448 ** Zuul reporting empty public_v6 addresses for test nodes (clarkb 20260519) *** Zuul is reporting public_v6 values of '' for test nodes that do have working ipv6 in clouds like rax classic and ovh *** This may be an openstack api bug, an openstacksdk bug, or a zuul-launcher bug. *** Be aware this may impact the behavior of some test jobs. *** We will need to dig into why this is happening to understand it better. * Open discussion
participants (1)
-
Clark Boylan