Tuesday, 2023-01-10

clarkbmeeting time19:00
clarkbhaven't had one of these in a while19:00
clarkb#startmeeting infra19:01
opendevmeetMeeting started Tue Jan 10 19:01:09 2023 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 https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/thread/5WW6CBUKQUWVNW7C5RRLXW7PWUXDPY75/ Our Agenda19:01
clarkb#topic Announcements19:01
clarkbThe Open Infra Foundation individual board member election is happening right now19:02
clarkbif you are a member of the foundation you should've received a ballot via email.19:02
clarkbPlease vote if you are able to.19:03
clarkb#topic Bastion Host Updates19:03
clarkbianw: I know prior to holidays you were querying people to see if anything else needed migrating from the old bastion before it was shutdown.19:03
clarkbLooks like the old bastion is still up, but maybe we can shut it down soon? I didn't see anyone indicate anything needed to be moved at last poll19:04
ianwyeah i think i got a response from everyone active19:04
ianwi can shut it down, and we can consider removal after a little19:04
clarkbsounds good19:05
ianwmore time19:05
clarkbAnything else bastion related?19:05
ianwi don't think so ... the backup bits i think might need a rebase now19:05
clarkb#topic Mailman 319:06
clarkbI think we may still need to restart services to pick up the site owner update. ALso frickler discovered that local root alias is not working anyway.19:06
clarkbdo we want to use a different site owner value or fix the root@lists01 alias in exim? I assume we prefer fixing the alias?19:06
fungiand i have some more related changes up for review19:07
fungiincluding an upgrade to the latest mm3 versions from last week19:07
clarkbthese changes are related to fixing the vhosting of lists themselves?19:07
fungiyes19:07
clarkbhttps://review.opendev.org/c/opendev/system-config/+/867986/ and children? Looks like they are all workinprogress right now19:08
clarkbhttps://review.opendev.org/q/topic:mailman3+status:open is a better link. Finds a couple extra changes19:08
clarkbfungi: what do you think the plan there should be?19:09
fungijust a sec, need to page a lot of this back into my head ;)19:09
fungii think i still need to review the failures on 86798719:09
fungii have a feeling it's probably just going to need test adjustments, but don't think i've confirmed that yet19:10
fungithe upgrade is up for discussion. the change passes at least19:11
clarkbfungi: was that generated to be in sync with how the upstream docker images are handling the version upgrade too?19:11
fungiand the upgrade notes for the new versions don't indicate any extra steps needed19:11
clarkbmy main concern is with the dep pinning as that seems to be a major headache for everyone doing mm319:11
clarkbbut once you have a good install it sounds like they handle upgrades pretty transparently19:11
fungiyes, much of that was ported from the docker image repo19:11
clarkbawesome. In that case I think we can land that either before or after fixing the other issues, Probably your preference really19:12
fungii think i'd like to dig into fixing the domain separation first19:12
fungiafter we get that ironed out though, and upgrade mailman to the latest releases, i should be ready to start planning for the next site migrations19:13
clarkbworks for me. Maybe ping us when you're in a state where extra eyeballs could be helpful? Whether just code review or helping with debugging on held nodes19:13
fungiyep19:13
fungimigrating lists.katacontainers.io should probably be prioritized since it frees up an entire server19:13
clarkbmakes sense19:14
fungibut also i've been fighting oom kills of random processes on the old lists.openstack.org server so the more we move off of it the better19:14
fungi(i just moments ago killed and restarted all relevant processes on that server yet again)19:14
clarkbAnything else on this topic?19:15
corvusfungi: i'm assuming you shut down/disabled the migrated processes already?19:15
fungiyes19:15
corvusfigured :)19:15
fungiyeah, if i hadn't, that would be an easy way to relieve some pressure on it19:15
fungitoo bad19:15
clarkb#topic Quo vadis Storyboard19:17
clarkbI swear I sent that followup email I said I would send but I'm not finding it now...19:17
clarkbIn any case there hasn't been much movement on this topic. As mentioned before I think we need to make a proposal (probably towards turning it off in a gracefaul manner if possible) based on the feedback we've gotten19:19
clarkbI feel like I've got enough distractions this week that I won't get to that this week whcih means we can let it simmer for a bit longer :/19:20
clarkbStill happy to receive any and all additional feedback others may have though19:20
clarkb#topic Gerrit 3.619:21
clarkbThe upgrade happened and we haven't reverted19:21
clarkbianw sent email to the repo discuss list to bring up the label listing behavior that is new in 3.6 (I have't seent an responses yet)19:21
clarkbI think we are at a point where we should remove 3.5 image builds, add 3.7 image builds, and update our upgrade testing to perform a 3.6 to 3.7 upgrade19:22
ianw++ i don't see us going back to 3.519:22
fungisgtm19:22
clarkbianw: I'm happy to help with the wrangling of those changes if you'd like.19:22
ianwsure :)19:23
ianwi also started on19:23
ianw#link https://review.opendev.org/c/openstack/project-config/+/86793119:23
ianwto update copyConditions in our configs19:24
clarkbthis is one of potentially several similar types of changes we'll need to make prior to upgrading to 3.719:24
ianwwe have some in our All-Projects which I think will need manual intervention, but i'd like to put some of it into the gate testing first19:24
clarkb++ there is less blast radius outside of all-projects19:25
ianwsome work started on that @19:25
ianw#link https://review.opendev.org/c/opendev/system-config/+/86805419:25
clarkbanything else gerrit upgrade related before we jump to the next thing?19:26
ianwnope, more to discuss in the future as we work on submit requirements etc :)19:26
clarkb#topic Nox19:27
clarkbThis is the evolution of the Tox v4 topic we had previously19:27
clarkbThe way the tox v4 situation has panned out has led to us needing to deal with new issues with every tox v4 release19:27
clarkbEventually some of us got tired of that and started looking at alternatives: in particular nox.19:27
clarkbNox is a tox alternative that uses a simple python file to specify its targets (it calls them sessions) and relies on standard tools and processes for installing things19:28
clarkbThis to me is the main feature with nox that has me wanting to switch. Tox has reimplemented libraries for certain peps and it led to weird behavior19:28
clarkbSticking to standard tools ensures we don't need todebug oddness like that19:29
clarkbLong story short Zuul is already largely moved to nox and I think OpenDev should do the same19:29
clarkb#link https://review.opendev.org/c/opendev/bindep/+/868004 An example conversion19:29
clarkbI've got this change up for bindep that serves as an example too19:29
clarkbAll of the zuul-jobs tooling for artifact retrieval and siblings support should be there now too19:29
fungithe only counterargument against nox i've heard so far is that some folks prefer the declarative nature of tox.ini files over turing-complete python scripts for configuration, but tox.ini is pretty far down the road to being a programming language of its own at this point too19:30
clarkbAnd as a user I've been relly happy using nox. I don't think I would suggest the move if I wasn't. The syntax for command is a little different but its not so different and it is quick to pick up19:30
clarkbfungi: ya and I would argue that this is tox's greatest flw right now because they keep changing the semantic meaning of that declarativeconfig19:30
clarkbmaking it effectively useless19:31
fungii'm good with switching bindep over to see how it goes (and zuul/nodepool are already basically there)19:32
clarkbAnyway, I intend on pushing changes to move active opendev repos to nox. But I don't want to get too far down that path until we've got general consensus this isn't a problem19:32
clarkbSo please do take a look at the bindep change, fetch that change locally and run nox yourselves and see what you think. THen let me know :)19:33
fungiconvincing large and complex projects like openstack to switch away from tox is probably not a windmill i feel like tilting at (especially since they're stuck using tox on older branches for years to come), but i think for opendev's projects it makes sense and shouldn't be too big of a lift19:33
corvusif it were me, i'd pin those older branches to tox v3 then nox on master19:34
fungiyeah, they're pinning the older branches anyway, as it turns out19:34
fungibut stuff like release tooling will have to support both19:34
clarkbdepending on where I get with zuul and opedev I might take a look at the release tooling, but I agree its a much stronger preexisting force you run up against there19:35
corvusi'm very happy with nox and i like the idea of us using it for opendev projects19:35
clarkbwoot my first couple of bits of feedback :)19:36
clarkbI think we can move on to the next thing19:36
clarkb#topic Service Coordinator Election19:36
clarkbIt has been about 5 months since we last elected our service coordinator19:36
clarkb6 months after our previous nomination period is January 31, 2023 - February 14, 202319:37
clarkbI'd like to propose we open that two week period for nominations for the next service coordinator and take it from there19:37
clarkbIf there are no objections to this timeframe I'll send email to service-discuss making it official soon19:38
clarkbas I've said before I'm happy for someone else to do the work too :)19:38
clarkb#topic Linaro Cloud Move and Cleanup19:39
clarkbianw: want to fill us in on the recent updates for the linaro cloud move19:39
ianwyep sure, we have credentials19:40
ianwthere are changes to enable the cloud for CI @ 19:41
ianw#link https://review.opendev.org/q/topic:linaro-202219:41
ianwone issue is that it doesn't have much disk.  so much so that our 800gb volume for the builder /opt would leave nothing else19:42
ianwso i asked osuosl if they could give us compute quota to run a nodepool builder there, which they kindly provided19:42
ianwi have the host up, storage attached, etc, and some changes out there to add it to system-config & dns19:43
ianwso i think i'd like to add that, and get it working and building things19:43
ianwthen disable nb0319:43
ianwthen cut testing over to new cloud19:44
fungisounds great19:44
ianwthen disable old cloud19:44
clarkboh I just approved the first two chagnes that shift over to the new cloud19:44
clarkbshould I WIP them?19:44
clarkbI guess its only the second that is a problem. I'll WIP it19:44
ianwit's ok, just we will want to monitor to make sure it is actually working19:44
clarkbheh ok switched back to +A19:45
ianwit can all really happen in any order, depending on our attention span to monitor the different bits :)19:45
clarkbthank you for picking this up. I think it will make ed happy and in theory these newer test nodes should be very quick19:45
clarkbAnything else related to the cloud moves?19:46
ianwyep, good to try and work with the providers to keep everyone happy :)19:46
ianwno more on that, will keep working at it19:47
clarkb#topic Upgrading Bionic Servers19:47
clarkb#link https://etherpad.opendev.org/p/opendev-bionic-server-upgrades19:47
clarkbThis is going to take on a bit more urgency due to bionic EOL in april19:48
clarkbI'm personally hoping to be able to really start picking things off of that list starting next week.19:48
clarkbIf anyone else ends up helping out please stick a note in the etherpad so that we don't step on each other. Also, help is appreciated :)19:48
clarkb#topic Open Discussion19:50
clarkb#link https://review.opendev.org/c/opendev/system-config/+/866781 Retire Mordred as infra root19:50
ianwone thing frickler pointed out was the increasing storage numbers19:50
clarkbCan other infra-root review this change? mordred pushed it himself so no concerns there. Unfortunately I think the time has come for this little bit of cleanup19:50
ianw#link https://grafana.opendev.org/d/9871b26303/afs?orgId=1&from=now-6M&to=now19:50
frickleryes, not critical yet, but worth watching19:51
clarkblooks like ubuntu and ubuntu.ports have grown a bit19:51
clarkbI wonder why19:51
clarkbsince they should be pretty fixed after the jammy release last april19:51
ianwwhich, apropos the prior topic, one win we could have there is purging everything xenial related19:51
clarkbthe open euler mirror also doubled in size19:52
clarkbso ya we probably needto make another pruning pass19:52
corvusi'd like to land the nodepool openstack statemachine change soon.  there is a non-zero chance of real-world performance problems.19:52
corvusonce we get all the nodepool tox/nox/k8s changes merged, how about i tag a 8.0.1 release, then if there is a problem we can revert opendev to it quickly?19:52
clarkbcorvus: ++ to tagging first19:52
ianwclarkb: yeah, i thought we got a new openeuler release but purged the old one19:53
clarkbdebian security almost doubled too19:53
clarkbdefinitely a good idea to dig into that. Thank you for calling it out ianw and frickler19:54
corvuscool, i'll make sure the tag happens and will keep folks updated.  let me know if there's any other concerns, preparation, or safeguards we'd like for opendev.  i figured i would manually upgrade launchers slowly to keep an eye on things.19:54
clarkbcorvus: you'll need to put them in the emergency file to do them manually as our hourly jobs are really good at updating them otherwise19:55
clarkb(remember this is on bridge01.opendev.org now)19:55
corvusclarkb: ack.  and i've already retrained to use bridge.opendev.org  :)19:55
corvusand thanks, i forgot that could happen hourly and not nightly19:56
corvusso: tag, emergency file, manual upgrade.19:56
ianw#link https://review.opendev.org/c/opendev/system-config/+/848796/319:56
ianw^ is the openeuler mirror drop -- i knew i'd seen something about it.  we should probably do that at least19:56
clarkb++ I'll review it now19:57
corvus(incidentally, tagging 8.0.1 will be a nice double check of any release job nox updates)19:58
corvusif we have to do an 8.0.2 it's no big deal19:58
funginumbers are free19:58
fungiwe won't run out19:58
clarkbAnd we are just about at time19:59
clarkbthank you everyone. Apologies for not communicating better last week. I ened up sick and wasn't in a place to computer. I'm still sort of on the tail end of that too but much more with it now :)19:59
clarkbWe'll be back next week. Happy new year!19:59
fungiwe didn't have anything worth covering last week anyway19:59
fungithanks clarkb!20:00
clarkb#endmeeting20:00
opendevmeetMeeting ended Tue Jan 10 20:00:01 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/infra/2023/infra.2023-01-10-19.01.html20:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/infra/2023/infra.2023-01-10-19.01.txt20:00
opendevmeetLog:            https://meetings.opendev.org/meetings/infra/2023/infra.2023-01-10-19.01.log.html20:00
-opendevstatus- NOTICE: One of our CI job log storage providers appears to be having trouble with log uploads and retrievals. We are in the process of removing that provider from the pool.22:43

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