June 2026 - service-discuss - lists.opendev.org

Team Meeting Agenda for June 30, 2026
by Clark Boylan 29 Jun '26

29 Jun '26

We will meet with this agenda on June 30, 2026 at 1900 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 *** backup03.ca-ymq-1.vexxhost.opendev.org has been launched and is being backed up to **** https://review.opendev.org/c/opendev/system-config/+/995420 Starting backup02 removal here *** 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 *** These two changes simplify the setup and testing of prometheus and node exporter **** https://review.opendev.org/c/zuul/zuul-jobs/+/994564 manage /etc/hosts with public IPs **** https://review.opendev.org/c/opendev/system-config/+/994565 Use public IPs in system-config-run jobs ** Larger VM sizes for tests (corvus 20260618) *** corvus has been testing python 3.14 with zuul; zuul unit tests now use slightly more than 8GB under 3.14 *** We have 16gb nodes, but in two clouds, rax-classic and vexxhost, they have fewer vcpus than their 8gb counterparts, so we need to use 32gb nodes to compensate *** Are we okay with this? Alternatives? ** Dealing with alien zuul config errors in the openstack tenant (frickler 20260617) *** Currently there are still 185 zuul config errors in the openstack tenant, despite my year-long struggle to get rid of them. *** Most of these are from "alien" repos (74 airship, 29 starlingx) that I have no motivation to fix myself with my OpenStack hats on *** Efforts to motivate these projects to clean up their errors themselves have mostly failed *** I still believe that cleaning these up and being able to easily identify fresh errors is important for the healthyness of the CI setup as a whole *** One pretty strong action would be to move these repos into their own tenant(s) or a different shared one like opendev *** I acknowledge that without further work this would break their CI setup, but I'm questioning now whether that impact would be worse than the impact the current situation has on my ability to maintain the OpenStack CI *** Other ideas or opinions are welcome *** clarkb reached out to starlingx and airship about this **** Airship indicated they would like to avoid the extra work involved in setting up a separate tenant **** clarkb pointed out to them that they would need to fix their zuul config errors and be reachable via email or matrix at a bare minumum if we want to make that work. **** https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… ** Gitea 1.26.4 Upgrade (clarkb 20260622) *** https://review.opendev.org/c/opendev/system-config/+/994326 Upgrade Gitea to 1.26.4 *** Its time to upgrade to the next Gitea bugfix release ** Bump Anubis difficult to 5 (clarkb 20260630) *** There is some evidence that bots are regularly solving the Anubis challenge *** The challenges are slowing them down enough that services continue to be mostly responsive *** Should we increase the difficulty one level to slow them down even further? *** This will impact regular users too which is likely the primary consideration we should make. *** https://review.opendev.org/c/opendev/system-config/+/995096 ** Planning Gerrit Project Renames (clarkb 20260622) *** We have a request to rename x/cursive to openstack/cursive *** Any concern with project ownership doing that? The current group membership includes people from Johns Hopkins University and OpenStack Barbican *** Aiming for July 9 at ~2100 UTC * Open discussion

1 0

Team Meeting Agenda for June 23, 2026
by Clark Boylan 22 Jun '26

22 Jun '26

We will meet with this agenda on June 23, 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 *** backup03.ca-ymq-1.vexxhost.opendev.org has been launched and is being backed up too **** clarkb checked paste's backups to the new server and they appear to be working there **** fungi moved wiki over to backup to this server from the old server **** I think we can probably start the tear down of the old server now *** 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 ** 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. ** 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. ** Larger VM sizes for tests (corvus 20260618) *** corvus has been testing python 3.14 with zuul; zuul unit tests now use slightly more than 8GB under 3.14 *** We have 16gb nodes, but in two clouds, rax-classic and vexxhost, they have fewer vcpus than their 8gb counterparts, so we need to use 32gb nodes to compensate *** Are we okay with this? Alternatives? ** Dealing with alien zuul config errors in the openstack tenant (frickler 20260617) *** Currently there are still 185 zuul config errors in the openstack tenant, despite my year-long struggle to get rid of them. *** Most of these are from "alien" repos (74 airship, 29 starlingx) that I have no motivation to fix myself with my OpenStack hats on *** Efforts to motivate these projects to clean up their errors themselves have mostly failed *** I still believe that cleaning these up and being able to easily identify fresh errors is important for the healthyness of the CI setup as a whole *** One pretty strong action would be to move these repos into their own tenant(s) or a different shared one like opendev *** I acknowledge that without further work this would break their CI setup, but I'm questioning now whether that impact would be worse than the impact the current situation has on my ability to maintain the OpenStack CI *** Other ideas or opinions are welcome ** Etherpad 3.3.2 Upgrade (clarkb 20260622) *** https://review.opendev.org/c/opendev/system-config/+/994325 Upgrade Etherpad to 3.3.2 *** Held node at 50.56.159.16 with a test clarkb-test pad. ** Gitea 1.26.4 Upgrade (clarkb 20260622) *** https://review.opendev.org/c/opendev/system-config/+/994326 Upgrade Gitea to 1.26.4 *** Its time to upgrade to the next Gitea bugfix release ** Working with LF IT to get some help in OpenDev (clarkb 20260622) *** clarkb and fungi are meeting internally later this week to see if we can point others at the LF to work that OpenDev would like to get done *** Don't be surprised if you see new faces contributing and please welcome and help them ** Planning Gerrit Project Renames (clarkb 20260622) *** We have a request to rename x/cursive to openstack/cursive *** When we do want to try and do that? *** Any concern with project ownership doing that? The current group membership includes people from Johns Hopkins University and OpenStack Barbican * Open discussion

1 0

Team Meeting Agenda for June 16, 2026
by Jeremy Stanley 15 Jun '26

15 Jun '26

We will meet with this agenda on June 16, 2026 at 19:00 UTC in #opendev-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 *** backup03.ca-ymq-1.vexxhost.opendev.org has been launched and is being backed up too **** Preliminary checks all looked good. Should double check that all expected hosts are backing up to this server and confirm that a backup is mountable and looks accurate. *** 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 ** 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 Followup (clarkb 20260414) *** We upgraded Gerrit last Friday to 3.13.6 from 3.12.7 *** https://etherpad.opendev.org/p/gerrit-upgrade-3.13 Upgrade plan and process that was used *** Seems to be working, but a few things have been noticed **** The lack of robot comment apis has created some questions. This was anticipated and we expect hard refreshes of browser clients to fix this **** The robot comment api removal also broke gertty **** corvus has suggested that Zuul stop using robot comments early as these comments effectively disappear post upgrade **** Custom "Your -> Foo" links in the web ui can be set to open in new tabs. This is configurable through your user preferences in Gerrit **** Some changes show up as conflicting with each other despite having a direct git tree relationship *** https://review.opendev.org/c/opendev/system-config/+/991945/ and children will drop Gerrit 3.12 images, add 3.14 images, and test a 3.13 to 3.14 upgrade just as soon as we're confident we won't rollback to 3.12. ** Upgrading Grafana (clarkb 20260609) *** https://review.opendev.org/c/opendev/system-config/+/991155 This change will upgrade grafana to the latest version *** https://23.253.20.165/ is a held node for testing purposes. Things look good to clarkb and we can probably proceed. ** 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 -- Jeremy Stanley

1 0

Team Meeting Agenda for June 9, 2026
by Clark Boylan 08 Jun '26

08 Jun '26

We will meet with this agenda on June 9, 2026 at 19:00 UTC in #opendev-meeting: == Agenda for next meeting == * Announcements ** clarkb will be out June 15 and 16. Fungi has volunteered to chair the team meeting on June 16 * 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 *** backup03.ca-ymq-1.vexxhost.opendev.org has been launched and is being backed up too **** Preliminary checks all looked good. Should double check that all expected hosts are backing up to this server and confirm that a backup is mountable and looks accurate. *** 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 ** 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 Followup (clarkb 20260414) *** We upgraded Gerrit last Friday to 3.13.6 from 3.12.7 *** https://etherpad.opendev.org/p/gerrit-upgrade-3.13 Upgrade plan and process that was used *** Seems to be working, but a few things have been noticed **** The lack of robot comment apis has created some questions. This was anticipated and we expect hard refreshes of browser clients to fix this **** The robot comment api removal also broke gertty **** corvus has suggested that Zuul stop using robot comments early as these comments effectively disappear post upgrade **** Custom "Your -> Foo" links in the web ui can be set to open in new tabs. This is configurable through your user preferences in Gerrit **** Some changes show up as conflicting with each other despite having a direct git tree relationship *** https://review.opendev.org/c/opendev/system-config/+/991945/ and children will drop Gerrit 3.12 images, add 3.14 images, and test a 3.13 to 3.14 upgrade just as soon as we're confident we won't rollback to 3.12. ** Upgrading Grafana (clarkb 20260609) *** https://review.opendev.org/c/opendev/system-config/+/991155 This change will upgrade grafana to the latest version *** https://23.253.20.165/ is a held node for testing purposes. Things look good to clarkb and we can probably proceed. ** 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

1 0

Team Meeting agenda for June 2, 2026
by Clark Boylan 01 Jun '26

01 Jun '26

We will meet with this agenda on June 2, 2026 at 1900 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 *** backup03.ca-ymq-1.vexxhost.opendev.org has been launched and is being backed up too **** Preliminary checks all looked good. Should double check that all expected hosts are backing up to this server and confirm that a backup is mountable and looks accurate. *** 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 ** 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) *** Upgrade is happening this Friday June 5, at 1600 UTC *** https://lists.opendev.org/archives/list/service-announce@lists.opendev.org/… *** 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 ** Etherpad 3.2.0 Upgrade (clarkb 20260519) *** 3.0.0, 3.1.0, and 3.2.0 have been released *** 2.7.3 introduced session cleanups in the database. But this created OOMs. We have disabled this feature. It should be fixed in 3.2.0. *** https://github.com/ether/etherpad/blob/v3.2.0/CHANGELOG.md Big change appears to be the ability for etherpad to self update. We will not opt into this functionality and already have it disabled *** https://review.opendev.org/c/opendev/system-config/+/990531 ** 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

1 0