Tuesday, 2021-07-20

clarkbanyone else here for the meeting? we will begin shortly18:59
clarkb#startmeeting infra19:01
opendevmeetMeeting started Tue Jul 20 19:01:09 2021 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
opendevmeetThe meeting name has been set to 'infra'19:01
clarkb#link http://lists.opendev.org/pipermail/service-discuss/2021-July/000269.html Our Agenda19:01
clarkb#topic Announcements19:01
clarkbI didn't have any announcements19:01
clarkb#topic Actions from last meeting19:01
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-07-13-19.01.txt minutes from last meeting19:02
clarkb#action someone write spec to replace Cacti with Prometheus19:02
diablo_rojo_phoneO/19:02
ianwo/19:02
clarkbAs far as I know that action hasn't been done. But good news is I think we're getting throug some of the stuff that had been distracting us and so that might get done soon :)19:02
clarkb#topic Specs Approval19:02
clarkb#link https://review.opendev.org/796156 Supporting communications on our very own Matrix homeserver19:02
clarkbLast week we said we'd put this up for approval this week. Big part of that was people weren't around last week that might want to review the change19:03
* mordred does dance19:03
clarkbfungi: ianw ^ if you can give that a read before Thursday EOD clarkb time that would be great19:03
fungiyeah19:03
mordredclarkb: you're your own timezone now19:03
clarkbtristanC has a change up to run a matrix gerritbot too which might be interesting to others19:04
clarkb#topic Topics19:04
clarkb#topic Gerrit Server Upgrade19:04
clarkbThis happened. Thank you ianw for doing the bulk of the work on this one.19:05
clarkbWe've had a few minor hiccups with things like java sql conncetor libraries and getting ssh host keys sorted last minute and making the change to reflect this in config management pass actually pass19:05
clarkball told those are small issues and this went really well.19:06
clarkbI wanted to call out for followups we now have the ability to do some gerrit cache and memory usage tuning that we didn't really have room for before19:06
fungithe end result is we now have a bigger gerrit with a local db for the reviewed file checkmarks?19:06
clarkbMaybe we let the server run for a week or two then look at data?19:06
clarkbfungi: yup19:06
clarkbThe othe rthing that ianw has mentioned is we should all check our homedirs and the gerrit2 homedir for files we want to live on the new server too19:07
clarkbI've already moved the ones I know I wanted to move, but still need to go look at the rest to see if any of it is worth carrying over19:07
clarkb#link https://etherpad.opendev.org/p/gerrit-upgrade-2021 Look here for changes to review in followup to the server move19:08
clarkbthe etherpad also has a few changes that ianw has pushed in followup. I think I've reviewed them all, and other reviews would be nice too19:08
clarkbianw: anything else to say about this?19:08
clarkbDo we want to keep it on the agenda for next week or can we consider this done?19:09
ianwnope, it seems like everything is going well.  i'll wait for frickler_pto to become frickler and then i think we can retire the old server19:09
ianwoh and i think i have some log archives i can move across too19:09
fungihow is the mariadb connector fix applied to the image build? sed -i?19:09
ianwfungi: currently we reverted to the mysql connector, which is still compatible19:10
clarkbfungi: we landed it via normal gerrit changes after manually editing the config file19:10
clarkbwe have both libs present in the image to support the old and new server db setups so we just had to change the connection line to specify the other lib19:10
fungioh, got it, so all in configuration19:10
clarkbyup, once mariadb connector works properly we can update the config as well as update our image to remove the old mysql lib19:10
fungiwe're not actually running with the mariadb connector patched19:10
clarkbcorrect19:11
fungithat makes sense, thanks19:11
ianwyep; no rush to get back.  i was just using the mariadb connector because, well, we were connecting to mariadb :)19:11
fungii wonder why they added a special one for that19:11
ianwjust the way the subclasses work i think19:12
ianwbasically string matching the db uri and then choosing classes19:12
ianwi do wonder why they added it with at least two bugs that made it not work at all, and nobody noticed, however19:12
fungijust seems odd that with as little as gerrit uses an rdbms for now, they'd incur the maintenance overhead of slight variations of a generic sql connector19:13
fungihistorical baggage i suppose19:13
fungianyway, not necessary to dig into now19:13
clarkbit may have been added back in 2.16 or prior for the actual db when that existed19:13
clarkbya19:13
clarkb#topic Gerrit Account Cleanup19:14
clarkbI've been thinking about scheduling for this and the project renaming that we said we'd all do "week after the upgrade"19:14
clarkbIn my head it makes sense to do the external id pruning Say on Monday. That is 3 weeks after I disabled the related accounts. Then do the project renames later in the week, say Friday.19:15
fungithat sounds reasonable to me19:15
clarkbThe reason for this is if we need to do account surgery after the external id cleanup happens due to the cleanups we can take advantage of the outage to do it19:15
clarkbwe did surgery on two accounts during the move for unrelated reasons and it went well but does require a downtime19:15
clarkbI don't expect we'll end up doing that as part of the project rename downtime, but it is nice to have the option19:16
clarkbOk I'll plan to run the external id cleanup script on Monday then.19:16
fungiyep19:16
clarkb#topic Gerrit Project Renames19:17
clarkbAs just mentioned I'm suggesting Friday July 30 for this and probably early that day. Say 15:00UTC ?19:17
clarkbthat gives us time to do more testing if we can find time to do that testing but also the buffer to account cleanups which we can use to fix accounts if necessary19:17
fungii'm around and happy to do it then19:18
clarkbok lets do it19:18
clarkbI can send out email about that as well19:18
clarkb#topic Gitea01 backup issues19:19
clarkbI don't expect anything new has come up about this but wanted to double check19:19
ianwno i haven't looked into it sorry19:19
clarkbno worries you were busy :)19:20
ianwi haven't heard any more on the ipv6 issues19:20
ianwi could take it out of the lb and reboot it i guess19:20
fungiand does look like it's still going on19:20
ianwthe switch it off and on again method probably has a high likelyhood of fixing things19:20
clarkbhah ok19:21
fungiyeah, neutron likes to get a kick in the interface every now and then19:21
ianwwe can sync back after that happens one way or the other19:22
clarkbsounds good19:22
clarkb#topic Gitea 1.14.4 upgrade19:22
clarkbI started working on this when all the other gerrit and zuul work was happening and didn't want to impact those as they seemed more important19:22
clarkbbut now that is largely behind us so I'd like to go ahead and land this upgrade when I have time to monitor it. Currently I think I have time tomorrow morning any objections to landing the change to upgrade gitea then?19:23
clarkb#link https://review.opendev.org/c/opendev/system-config/+/800274 gitea upgrade19:23
clarkbIts a fairly large gitea upgrade as far as the change delta goes, but I did hold a node and it looked good19:23
clarkband our testing caught one issue with a changing api so that seems to be working well for us19:23
fungii'm good with it, finally reviewed and checked it out today19:24
clarkbSounds like no objections. If things are quiet when I start my day tomorrow I'll approve it19:24
ianw++19:25
clarkb#topic High AFS utilization19:25
fungii'll be more around tomorrow anyway, more than today19:25
clarkbfungi: cool19:25
clarkbYesterday it was pointed out that the opensuse mirror was sad. It had a stale lock which I removed and then manually did updates for after and is happy now19:25
clarkbIn the process of looking into that I noticed htat our afs vicepa utilization is high19:26
clarkbwe have less than 10% remaining disk space19:26
clarkbThe debian volume looks like it may need to grow as well as we are right up against quota there19:26
fungiwere we able to reclaim much with the centos cleanup?19:26
clarkbfungi: yup, but then we backfilled with openeuler mirroring :)19:26
fungiwe can push to try and drop debian-stretch images19:26
ianwyeah, although bullseye is fully frozen now, so we can probably drop some debian soon19:27
clarkbya I was going to ask about that particularly since debian is near its quota19:27
ianwor yeah, just push to drop it now19:27
clarkbI think that would be a good next step if we think it isn't too disruptive to users for some reason19:27
clarkbThe other one that is large and I'm not sure still used is mirror.yum-puppetlabs19:27
fungibut yes, stretch is already "oldstable" (the release before the current stable) and is about to become "oldoldstable"19:28
clarkbI think tripleo and/or puppet-openstack may be the users of the yum puppetlabs mirror. I'm wondering if they continue to use it at all and if so if they only use a small subset19:28
fungiwe should probably ask the puppet-openstack team if they're still using that, and if so whether they're using all or just a small part19:28
clarkbcurrently that mirror seems to have packages for old fedora and sles and so on19:29
clarkbfungi: ++ exactly19:29
clarkbI suspect we can trim that done one way or another.19:29
clarkbI can send email to openstack-discuss asking puppet-openstack and tripleo to weigh in on it19:29
clarkbfungi: ianw: any idea what the first step for debian trimming would be?19:29
fungiprobably check for zuul configs referencing debian-stretch, though searching stable branches will be hard19:30
fungiprobably better would be to start a discussion proposing we drop it, and then see if we get pushback19:30
clarkbfungi: that seems reasonable. Is that something you might want to send to service-discuss?19:31
ianwyeah, i can have a look at it19:31
clarkbianw: that would be great thanks19:31
ianwi think both discussion, but also directly proposing changes might help19:31
fungistretch has been obsolete for ~2 years since buster came out, and most projects aren't supporting their branches past that anyway19:31
ianwanything we can do to get dib's testing more under control is good too :)19:31
clarkbThe last note I put related to this on the agenda is I've noticed discussion about adding Alma linux to our node list.19:32
fungii can bring up dropping stretch on the openstack-discuss ml19:32
clarkbI think starting with clenaup is the right option but we should probably be prepared to add a third 1TB device to our vicepa setups if the linux distros keep multiplying19:32
clarkbThere is probably another disucssion there about whether we can delete centos entirely if we do alma or similar but I think it is a bit early for that19:33
ianwi mean we can build images before putting the mirror in19:33
fungiaha, alma linux is in the same vein as rocky linux and (non-stream) centos. i knew the name sounded familiaer19:33
clarkbianw: yup that is true, though I suspect ne wdistros like that may want us to offloda for them as much as possible19:34
clarkbfungi: yes, alma seems to be the one iwth all the momentum right now19:34
fungiyes, mirrors are more of a general speedup, and matter more for our more heavily-used distros19:34
fungiso we might just consider mirrors to be out of scope for less-used images we offer19:34
fungiif a particular label only sees use in a handful of builds a week, the overhead in maintaining a mirror for the software is clearly overkill19:35
fungitaking that into account, we could always just consider dropping some of our mirrors of significantly under-utilized stuff even if we don't drop the images19:36
clarkbfungi: yup, that is why I also mentioned the possibility of mv centos alma && sed -i -e s/centos/alma/ *zuul.yaml :)19:36
ianw(this was a bit of my concern with openeuler as it seems like that has a long path to being used)19:37
clarkbBut all of that currnetly depends on imgaes and people being interested in the work and so19:37
clarkbianw: thats a good point. I guess we can take a high level view once the afs pruning happens and we know where we stand19:38
clarkbthen start thinking a bit more critically about the various distros and whether we need full mirrors for all of them19:38
clarkbNot something we need to solve today, I just saw the demand seems to be creeping up and wanted to call it out19:38
clarkb#topic PTG Participation19:39
clarkbI discovered yesterday that the deadline to sign up for PTG participation is tomorrow19:39
clarkbThe PTG is running October 18-22, 2021. If you are curious yes this sign up deadline is earlier than in the past19:40
fungiit feels sudden, but i guess that's because i've been on vacation19:40
clarkbThe office hours we did last time around seemed to work well for 2 hours in the EU friendly timezone.19:40
clarkbs/timezone/time block/19:40
clarkbI'm happy to sign up for similar this time around as a result.19:40
clarkbDoes anyone think we should have more time than that?19:41
clarkbOr perhaps think we should skip entirely?19:41
fungiwhat we did last time worked for me19:42
clarkbfungi: ok, I'm proposing we trim that back to a single 2 hour block during the EU afternoon NA morning since that is where we got participation last time19:43
clarkbianw: ^ will you feel excluded if we do that ?19:43
ianwno19:43
clarkbalright I'll sign us up for that. If anyone wants mor etime let me know and I'll adjust to try and include that19:44
clarkb#topic Open Discussion19:44
clarkbThat was all I had. Except I remember thinking of something I should bring up during the meeting earlier today and I've completely forgotten what it was19:45
clarkbAnything else?19:45
fungii got nuthin'19:45
ianwnothing more from me19:46
clarkbAlright then, thank you everyone for your time and now you can go find $meal :)19:47
fungithanks clarkb!19:47
clarkbAs always feel free to find us in #opendev or at service-discuss@lists.opendev.org and we can discuss anything there that was missed here19:47
clarkb#endmeeting19:47
opendevmeetMeeting ended Tue Jul 20 19:47:57 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:47
opendevmeetMinutes:        https://meetings.opendev.org/meetings/infra/2021/infra.2021-07-20-19.01.html19:47
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/infra/2021/infra.2021-07-20-19.01.txt19:47
opendevmeetLog:            https://meetings.opendev.org/meetings/infra/2021/infra.2021-07-20-19.01.log.html19:47

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