Tuesday, 2025-11-18

clarkbjust about meeting time18:59
clarkbI suspect this one might be quicker than usual as our agenda is fairly light (and that is ok)18:59
clarkb#startmeeting infra19:00
opendevmeetMeeting started Tue Nov 18 19:00:12 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/R36BWJAGRO7EBAJ6NH7SB2646MP555D3/ Our Agenda19:00
clarkb#topic Gerrit 3.11 Upgrade Planning19:00
clarkbLast week we managed to fix the bind mount issue with gerrit's docker compose file and updates our images to the latest bugfix releases for 3.10 and 3.1119:00
clarkbsince then I have held new nodes using those new images19:00
clarkbIf you want to look at them yourselves you can do so via 3.10: https://217.182.142.186 and 3.11: https://174.143.59.5819:01
clarkbmy hope/goal is that starting tomorrow I'll be able to pick up the gerrit upgrade effort as my primary focus for the next little bit and we'll get it done19:01
clarkb3.10 went eol like last week. So its a good idea for us to upgrade as soon as is reasonable19:01
clarkb#link https://www.gerritcodereview.com/3.11.html19:02
clarkbPlease do take a look over the release notes if you have time and flag any issues you see19:02
clarkb#link https://etherpad.opendev.org/p/gerrit-upgrade-3.11 Planning Document for the eventual Upgrade19:02
clarkbnotes will be captured in this etherpad19:02
clarkbalso I skipped announcements today because I didn't have any and figured if its going to be a shorter meeting anyway we may as well make the most of it. We can call anything out that is important to note that I miss at the end of our time19:03
clarkbAny concerns or questions around the Gerrit upgrade process? I know we were able to walk tonyb through the bugfix update process and I think that was helpful19:03
tonybvery19:04
tonybthank you all for making the time to do that19:04
clarkbhappy to. And I think we can try and organize the actual upgrade to 3.11 in a similar way so that more people can gain that familiarity if there is interest19:05
clarkbthat might mean doing the upgrade on a sunday afternoon (for me) if tonyb is interested19:05
clarkbianw did at least one upgrade that way too19:05
clarkbanyway as noted my plan is to page this all back in starting tomorrow and start (re)building the confidence we need in the upgrade and downgrade then we can set a time to do the actual upgrade19:06
clarkbthinking out load here maybe first ish week of december? I think that may be enough time for me to figure things out with the upcoming holiday19:06
clarkb#topic Upgrading old servers19:08
tonybthat sounds good to me.   if you're willing to give up some of your Sunday19:08
clarkbtonyb: ya that should work I'll keep it in mind with the planning19:08
clarkbfor server upgrades are there any updates? I know tonyb had some changes going but not sure if they got new patchsets yet19:09
tonybthey have not.19:09
tonybsorry19:10
tonybtoday for sure!19:10
clarkback thanks. I think we've all been busy with many other things so understandable19:10
clarkbThe other thign I wanted to call out on this topic is that there is even some value to upgrading servers like etherpad or giteas to noble despite them being on jammy. And that is due to docker hub rate limits19:10
clarkbthe recent etherpad ugprades got hit by rate limits and I had to do /etc/hosts surgery to force ipv4 as a temporary workaround19:11
clarkbNot terrible and the focus is definitely still on the older nodes, but once those are done doing more updates has value too19:11
clarkb#topic Matrix for OpenDev comms19:12
clarkb#link https://docs.opendev.org/opendev/infra-specs/latest/specs/matrix_for_opendev.html19:12
clarkbThe room exists now (thank you tonyb) and corvus has a change up to add statusbot support for matrix19:12
clarkb#link https://review.opendev.org/q/hashtag:%22opendev-matrix%22+status:open19:12
clarkbper the spec the next steps will be adding gerritbot and eavesdrop bots to the room. I can write chagnes for that soon19:13
corvusit's a wee bit of a larger change than i hoped19:13
clarkbthen we can also update statusbot and get it joined to the opendev room and the zuul room19:13
corvusmostly due to the way statusbot assumed there would only every be one bot, plus also, the matrix lib is async.19:13
clarkbcorvus: I think the change ends up being readable enough despite the mix of async and threads19:13
corvusi disabled the feature which changes the room topics.  we haven't used that in ages, and it's always been a bit fragile19:14
corvusi'm hoping that gives us a bit more confidence in the system as a whole19:14
clarkbthe link above is for a hashtag in gerrit that we'll use to track the work so keep an eye out for the changes and please review them19:14
clarkbcorvus: ++19:14
clarkbthen once we have all the bots staged I think we can start the planned cut over and begin using the new room as the primary synchronous comms location19:15
fungialso i *think* tonyb said he fixed up the opendev admin account to be present and admin in all the channels on our homeserver now? or at least most of the ones i might have screwed up in the past19:15
corvusi've tested it, but not completely, but i think it's ready to merge and for us to update it19:15
clarkbcorvus: ya I was ahppy with it as is19:15
clarkb(though that was just code review on my part)19:15
corvusi think we should go ahead and do the statusbot upgrade and test it out.  then add the others.  we know that eavesdrop and gerrit work, but statusbot needs exercising19:16
tonybyup I definitely tried to make  join all the rooms as admin:opendev.org.   and make it thr admin 19:16
fungithanks tonyb! and sorry for all the makework19:16
clarkbcorvus: makes snse19:16
tonybfungi: no problem at all19:17
clarkbone thing I haven't considered is that matrix eavesdrop and limnoria eavesdrop may try to log to the same directory on disk for logs19:17
clarkbthat just occurred to me and is worth looking into /me makes a note19:17
fungiwe could maybe just have a test to make sure there's no overlap in channel/room names being logged?19:17
corvusthe matrix eavesdrop does intentonally do that, mostly because that was our cutover strategy for zuul19:18
tonybon the matrix stuff.   did we decide we're okay to include the ops and new opendev rooms as publicly listed?19:18
clarkbfungi: ya that might be one solution19:18
clarkbtonyb: I think we decided that zuul is publicly listed so publicly listing those two should also be fine19:18
tonybokay.   I'll double check I did that19:18
fungii mean, as long as we're not logging the zuul irc channel when we start logging the zuul room in matrix (i know this already happened, simply an example) then it should be fine19:18
clarkbfungi: yup if only one channel is logged at a time we'll be ok19:19
clarkbI may take a quick look to see if there is a way to dedup somehow in limnoria and/or matrix eavesdrop in case we want that feature19:19
fungistrip the two lists to bare names, concatenate and sort, then count duplicates and error19:20
clarkbanyway real progress is being made on this spec now. I'll work on a gerritbot chagne since that is easy. Everyone else should review the statusbot change. And I'll see about the logging collision problem19:20
clarkband then once we're happy with the bots we can start moving over potentially as early as this week or next?19:21
corvusfwiw, i like the flag-day cutover and continuing the same logfile19:21
clarkbcorvus: ack19:21
fungiyeah, sounds like an ideal approach19:21
clarkbany other questions, concerns, comments on this effort?19:22
fungisimple and straightforward19:22
clarkb#topic Gitea Performance19:23
clarkbI left this on the agenda beacuse i wanted to see if anyone had noticed problems since the load balancer and memcached updates19:23
clarkbFor me personally things appear to be much more consistent in terms of performance since those changes19:24
clarkbwe did also upgrade to 1.25.1 and add the canonical link headers to apache but I don't think either were expected to improve performance19:24
tonybI haven't noticed any problems, performance or otherwise 19:25
clarkbgreat. If you do notice anything feel free to note it. Improvements like this are often driven by users noticing issues19:25
tonyband accessing specific gitea backends is pretty easy with a SOCKS proxy to the LB.19:26
clarkbyes I've done that in my browser but then have relied on direct port forwards for git operations19:26
clarkbyou probably can get git to talk socks (since it uses curl which almost certainly understands socks somehow) but I haven't figured that out yet19:26
fungithe deployment window between one and all backends getting updated is also brief enough that i'm fine just checking through the lb unless we're troubleshooting a problem with a specific backend19:27
fungithis isn't a five-nines operation19:27
clarkbneither is cloudflare so I think we're doing ok19:27
fungitouch'e19:27
fungihmm, my compose key is busted19:28
clarkb#topic Open Discussion19:28
clarkbthat was everything on the agenda.19:28
clarkbhttps://review.opendev.org/c/opendev/zuul-providers/+/966200 will add trixie arm64 images19:28
clarkbhttps://review.opendev.org/c/opendev/zuul-providers/+/967599 adds trixie x86 nodests (since we don't quite have arm64 images yet)19:29
fungireran xmodmap and can now touché correctly. i wonder why the call through .xinirc didn't take19:29
clarkbcorvus: fungi  ^ should I go ahead and approve 599 at this point? It shouldn't affect anything that is running yet so I think its fine19:29
corvussgtm19:29
fungiyeah, i'm cool with it19:30
tonybI haven't checked my scroll back.   any objection to me using the cli admin interface to remove the unwanted gitea user?19:30
fungifingers crossed we can add the missing ones later today or tomorrow19:30
clarkbtonyb: no objections from me. I think you can do it through the web ui as admin too though?19:30
fungitonyb: i didn't see anyone comment on it, but please feel free19:30
clarkbtonyb: we've only used the cli admin interface once to fix the db records iirc19:30
clarkbso its a bit more of an unknown but no objections to getting that sorted out19:31
fungithat one user account slipping through was due to a brief window that we hadn't disabled the feature, but hasn't posed enough of a risk that any of us has prioritized cleaning it up until now19:31
clarkbI mentioned this yesterday when prepping the agenda. I think we got a fair bit done in the last couple of weeks between gerrit updates and zuul launcher bugfixes and etherpad and gitea and zookeeper upgrades. Thank you everyone for helping keep the ball rolling forward and keeping the lights on19:31
tonybclarkb: yeah I thought the cli admin interface was "easier" than web clicky clicky19:31
fungiprobably so now that we don't have trivial webui access to each backend19:32
corvusyou're welcome and thank you (all) :)19:32
fungii'll likely prefer the cli in future now too19:32
clarkbnext week is a major US holiday but I expect to be around monday and tuesday as well as most of wednesday (at some point I need to start food prep though)19:33
clarkbI don't expect to be around thursday or friday19:33
fungii'll be around if people want to meet19:33
tonybI'll be here, and trying to watch a little closer19:34
fungii'll be around most of thursday and friday too and can keep an eye on things, i don't have plans to go anywhere or cater to a crowd this year19:34
clarkbfungi: hopefully you enjoy the quiet. I'm hosting so a bit of the opposite for me this year19:34
fungiyeah, you have my sympathies19:34
fungithe most i'll end up doing is making homemade pizza or grilling a couple of burgers19:35
clarkbok sounds like that may be everything?19:35
tonybnothing more from me 19:35
clarkbfeel free to continue discussion (or start new ones) in #opendev or on the mailing list. We'll probably meet next week per usual19:36
clarkband until then thanks again for all the help19:36
clarkb#endmeeting19:36
opendevmeetMeeting ended Tue Nov 18 19:36:24 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:36
opendevmeetMinutes:        https://meetings.opendev.org/meetings/infra/2025/infra.2025-11-18-19.00.html19:36
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/infra/2025/infra.2025-11-18-19.00.txt19:36
opendevmeetLog:            https://meetings.opendev.org/meetings/infra/2025/infra.2025-11-18-19.00.log.html19:36

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