Tuesday, 2025-08-05

clarkb~5 minutes to our meeting18:55
corvusread you loud and clear18:56
clarkb#startmeeting infra19:00
opendevmeetMeeting started Tue Aug  5 19:00:06 2025 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
opendevmeetThe meeting name has been set to 'infra'19:00
clarkb#link https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/thread/GPTGNBBSJONHY3AZX64L5HECQ2YZYXB7/ Our Agenda19:00
clarkb#topic Announcements19:00
clarkbI didn't have anything to announce. Did anyone else?19:00
clarkbI guess I can note the service coordinator nomination period is open now19:00
clarkbwe'll discuss that in more depth later in the meeting19:00
fungii didn't, no19:02
clarkb#topic Gerrit 3.11 Upgrade Planning19:03
clarkbNothing really new here. I had hoped to start testing upgrade things with our latest image builds last week but then got distracted by other things19:03
clarkbit is still relatively high on my todo list though so I'm hoping to have updates soon19:03
clarkb#link https://www.gerritcodereview.com/3.11.html Gerrit 3.11 Changelog19:03
clarkb#link https://zuul.opendev.org/t/openstack/build/f1ca0d1f2e054829a4506ececb58bed3 Held Nodes A19:03
clarkb#link https://zuul.opendev.org/t/openstack/build/588723b923e94901af3065143d9df818 Held Nodes B19:04
clarkband these are useful links if anyone else wants to look into it a bit more too19:04
clarkbany questions/concerns/comments around Gerrit 3.11 upgrades before we move on?19:04
clarkb#topic Upgrading old servers19:06
clarkbThere are updates here19:06
clarkbfungi replaced eavesdrop01 with eavesdrop02 updating it to Noble19:06
clarkbthere were some minor hiccups during the replacement but overall things went smoothly19:06
clarkbfungi: is the old server still running? And if so when do you think we should consider cleaning it up?19:07
fungistill up at the moment19:07
fungibut yes needs cleaning up along with dns19:07
fungii was going to do it this week19:08
clarkbsounds good. Any thing else to note on the eavesdrop server replacement?19:08
fungiother than me forgetting to add the acme cname initially, it went fine19:08
clarkbyup the actual data recording outage ended up being pretty minimal as planned19:09
fungithe cinder volume name still references eavesdrop01 of course19:09
clarkbthe ssl cert problem only affected reading the logs back out again19:09
clarkbI wonder if you can rename a volume19:09
fungiwe can do a seamless replacement later if we want, using pvmove19:09
clarkbgood point19:10
fungibut it's mainly cosmetic19:10
clarkbfungi also announced the plan to shutdown refstack and retire its git repos19:10
clarkb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/WNI4PE2TZ3G52C3U5FT2YNVRUAJB3CMO/19:10
corvusgoogle suggests "openstack volume set --name" can rename but that should be verified19:10
clarkbI don't think any of those changes have actually happend yet but announcing that they will happen is a good start19:10
fungiyeah, side note, turns out refstack crashed weeks ago and nobody noticed19:11
corvus(maybe worth a try before doing pvmove)19:11
fungiso it's already down19:11
clarkbha confirming that shutting it down is the right course of action19:11
clarkbfungi: is there anything you need to continue to make progress on the refstack cleanup?19:12
funginah19:12
clarkbthank you for pushing these along. It helps a lot when we're all chipping away at the big list of server upgrades19:12
fungii just wanted to give the announcement thread a few days before i stop/snapshot/delete the server19:12
clarkbanything else on the larger server upgrades topic?19:13
clarkb#topic Matrix for OpenDev comms19:14
clarkb#link https://review.opendev.org/c/opendev/infra-specs/+/954826 Spec outlining the motivation and plan for Matrix trialing19:14
clarkbI've gotten a couple more reviews now. I'll plan to make some updates and push a new patchset this week in response to those19:14
clarkbthank you for that. I haven't really seen any feedback that diverges from what we've already talked about. But some good ideas on tightening up the plan19:15
clarkbwe can keep the discussion largely in Gerrit so that we don't have diverging threads. I just want to keep calling attention to the spec here while it is getting iterated on19:15
clarkb#topic Working through our TODO list19:16
clarkb#link https://etherpad.opendev.org/p/opendev-running-todo-list19:16
clarkbwe have a new dedicated etherpad that is also linked to from the front page of our specs site19:16
clarkbhttps://docs.opendev.org/opendev/infra-specs/latest/#todo-list19:16
corvusoh matrix19:16
corvusianw suggested looking into mjonlr19:17
clarkbIdea is to capture things on our radar that we either haven't been able to get to yet or are slowly making progress on and don't want to forget19:17
clarkbcorvus: ya I was going to look at the options there then update the spec19:17
clarkbI thought we were already subscribed to some sort of global moderation system but maybe this is an extra layer on top of that?19:17
corvusok... cool... yeah, that might change the work item stream.19:17
corvusi think maybe they just provide access to it and we have to start using it19:17
clarkbgot it. I'll dig in and see what I find19:18
corvussounds good19:18
corvusthanks!19:18
clarkbon the todo list front feel free to update that document with other things you're aware of that aren't already captured19:18
clarkbor mark things done if I've missed things getting completed19:18
clarkbthe idea is to have an easy system to acpture stuff at a very high level so that we don't completely forget but also give people a thread to pull on if/when they are ready to start the next thing (which may lead to writing a spec etc)19:19
clarkband related to that is pre PTG planning19:19
clarkb#topic Pre PTG Planning19:19
clarkb#link https://etherpad.opendev.org/p/opendev-preptg-october-2025 Planning happening in this document19:19
clarkbI've added some real content ideas there and everyone should feel free to add more19:19
clarkbOne thing I wanted feedback on as we get closer is how much time do we think we can dedicate to this in october and what time of day are we thinking?19:20
clarkbI was thinking may be 2 hours a day tuesday through thursday and if we run out of discussion topics we can cancel the later blocks of time19:20
clarkbtonyb: will you be in an au timezone or somewhere else? Wondering if we should try to have an early and late session or maybe something around 1900 UTC which may "work" (for some value of work) for everyone?19:21
clarkbwe are about 2 months away now so plenty of time to figure that out, but I don't want to forget that we need a more concrete set of times so am starting that discussion now19:22
fungishould be doable for me19:22
clarkbif I don't hear and specific feedback I'll probably just pick some times in a couple of weeks then see if anyone complains :)19:23
clarkbso ya get back to me on what times you expect to work for you and I'll see what I can do schedule wise19:23
clarkb#topic Service Coordinator Election Planning19:23
clarkb#link https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/thread/YXRD23ZWJGDPZ3WESBNZNEYO7NBCXFT4/19:23
clarkbNomination Period open from August 5, 2025 to August 19, 2025. If necessary we will hold an election from August 20, 2025 to August 27, 2025. All date ranges and times will be in UTC. Is the summary19:23
clarkbthis has all been made official on the mailing list now19:24
clarkbI am more than happy for someone else to step into the role and can act as backup and contineu to support whoever it may be19:25
clarkblet me know if you have any questions about what is involved19:25
clarkb#topic Loss of upstream Debian bullseye-backports mirror19:26
clarkb#link https://review.opendev.org/956497 temporarily ignore undefinedtarget19:26
clarkbfungi: want to catch us up on this one?19:26
fungiyeah...19:27
fungiso, the backports suite in debian for bullseye was eol for a while, finally removed from the upstream mirrors a couple weeks ago19:27
fungithis broke our reprepro mirroring of course, so there was a change to remove it from the config19:28
fungiunfortunately, because it still persists in the reprepro database, it's treated as an error causing the script to abort19:28
fungiin the short term we can work around it by telling reprepro to ignore that error and get the mirror back up to date19:29
clarkbfungi: so we've already removed it from the config?19:29
fungiyes, in git19:29
fungithe script change you linked above refers to the earlier config change19:29
clarkbso I guess we need to run the steps we have documented for cleaning up targets like that? Similar to what we would do after the changes to cleanup xenial land?19:29
clarkbin the case of xenial we probably won't get an error because ubuntu isn't removing that content from the mirrors I guess. But I suspect the cleanup fixup steps are similar/the same?19:30
fungiwe could instead just purge the bullseye-backports suite, but that's going to cause jobs which are using bullseye with the configure-mirror role to start breaking unless they override its default19:30
clarkbgot it. Do we know if any actually depend on that?19:31
clarkbjust thinking that bullseye is old enough and backports are uncommon enough that maybe it is a non issue?19:31
fungii highly doubt they're installing packages from it19:31
clarkband if it is an issue maybe that is an indication the jobs should be updated19:31
fungior the default19:32
fungi#link https://opendev.org/zuul/zuul-jobs/src/commit/06098ab/roles/configure-mirrors/defaults/main.yaml#L1419:32
clarkbI'm ok with that workaround change and I've +2'd it. But I suspect we can probably just proceed with clearing out backports as the longer term solution19:32
fungias we've discussed before, that role enables the backports repo in all jobs that use it, unless they explicitly set `configure_mirrors_extra_repos: False` as an override19:33
clarkbfungi: I think we can set a site vars override for that19:33
clarkbthen you don't have to do it on a per job basis19:33
fungione possibility that could be less intrusive is to make the default version-dependent19:33
clarkbor we could set it in the base jobs that configure mirrors I guess which is only a small number of locations19:33
clarkbfungi: well I'm thinking that we should set it to false because debian doesn't keep the packages up for long enough19:34
clarkbrather than make it version dependent just force things to opt in and then deal with the fallout when the packlages go away in those locations19:34
fungiyeah, i just wonder if (and this is more a topic for zuul discussion venues) that role's default should be rethought19:34
corvusthere's a completely different way of configuring mirrors already specced out19:35
corvusbut no one is working on it19:35
corvushttps://zuul-ci.org/docs/zuul-jobs/latest/mirror.html19:35
clarkbya that appraoch is far more specific and less convention based. Definitely a good thing to pick up if someone has time19:36
clarkbso for next steps I think we can land the workaround to start syncing packages again, then concurrently flip the var value in opendev one way or another, then finally cleanup the old packages db and revert the workaround19:37
clarkbif that seems reaosnable i think fungi can go ahead and +A the workaround19:37
fungiyeah, can do19:38
fungithis had enough moving parts i didn't want to go making too many changes before we had a chance to talk through the options19:39
clarkb#topic Adding Ansible 11 to Zuul19:39
clarkbZuul is growing support for Ansible 11 (this may already be deployed in opendev as of our friday restarts?) and losing support for ansible 819:40
corvusyep is deployed19:40
corvus#link ansible 11 test https://review.opendev.org/95649019:40
corvusthat initial sanity check came back green19:40
corvusso do we want to go ahead and set the tenant defaults for opendev and zuul to 11?19:41
clarkbI'm open to try that and see what if anything breaks19:41
clarkbhave we run into any problems at all yet?19:41
clarkb(just wondering if there are known gotchas)19:41
corvusnothing yet; i don't expect the changes to impact us (or probably almost anyone)19:42
corvusbut nobody expects, etc...19:42
clarkbthen ya I think the next step is to toggle over a tenant or two and exercise it19:42
corvuscool, i'll propose a change19:43
clarkb#topic Gitea 1.24.4 Upgrade19:43
clarkb#link https://github.com/go-gitea/gitea/blob/v1.24.4/CHANGELOG.md19:43
clarkb#link https://review.opendev.org/c/opendev/system-config/+/95659119:43
clarkbthis appears to be a fairly straight update for us. I suggested earlier today that we land fungi's opendev.org main page update first then land this to upgrade the service itself19:44
fungiyeah, i'll take a look after the meeting19:44
clarkbthe main page update has enough reviews now but my upgrade change could use some reviews19:44
clarkbthanks!19:44
clarkbso ya not a major item but wanted to bring it up as I think we can get it done and rolled out fairly quickly19:45
clarkb#topic Etherpad 2.4.2 Upgrade19:45
clarkbThis change however is probably a bit more involved19:45
clarkb#link https://github.com/ether/etherpad-lite/blob/v2.4.2/CHANGELOG.md19:45
clarkb#link https://review.opendev.org/c/opendev/system-config/+/95659319:45
fungii love the bug fix "fix various bugs"19:45
clarkbin particular they've added dark mode support that I guess toggles based on your browser settings19:45
fungi(that was about the gitea upgrade)19:46
clarkband they added a home button to the toolbar list which I'm not entirely sure what it does19:46
clarkbso anyway I've held a node looks like it is 158.69.64.11719:46
clarkbwe'll want to edit local /etc/hosts to point etherpad.opendev.org to that IP and test out these new UI updates19:46
clarkbreviews welcome as well as any feedback on the ui updates19:47
clarkb#topic Open Discussion19:48
clarkbI did want to call out I've got a couple changes up to clear out xenial mirror content and bionic arm64 content19:48
clarkbbut I'm thinking now the priority is probably in fixing the bullseye situation so that we've got a stable and happy reprepro before we start trying to modify the ubuntu content?19:48
clarkbAnything else?19:50
clarkbsounds like no. Thank you for your time and help everyone! Let me know about timing for pre ptg schedule blocks and consider running for service coordinator19:52
clarkbwe'll be back here next week at the asme time and location19:52
clarkb#endmeeting19:52
opendevmeetMeeting ended Tue Aug  5 19:52:23 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:52
opendevmeetMinutes:        https://meetings.opendev.org/meetings/infra/2025/infra.2025-08-05-19.00.html19:52
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/infra/2025/infra.2025-08-05-19.00.txt19:52
opendevmeetLog:            https://meetings.opendev.org/meetings/infra/2025/infra.2025-08-05-19.00.log.html19:52

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!