Tuesday, 2024-07-30

fricklerI'm going to skip the meeting and call it a day, will read backlog tomorrow18:56
fungihave a good evening frickler!18:56
clarkbgood night!18:58
clarkbit may be a small group then18:58
clarkbtonyb also mentioend not being able to make it today18:59
clarkb#startmeeting infra19:00
opendevmeetMeeting started Tue Jul 30 19:00:15 2024 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/GBQUFAFSFBGZGLEYVTCCSUABJXCS6ZUJ/ Our Agenda19:00
clarkb#topic Upgrading old servers19:00
clarkb#undo19:00
opendevmeetRemoving item from minutes: #topic Upgrading old servers19:00
clarkbI'm getting ahead of myself here19:00
clarkb#topic Announcements19:00
clarkbAs mentioned above frickler and tonyb won't make the meeting today. But we'll take notes here so that they and others can review them later19:01
clarkbI've realized that I made a bit of a mistake in planning family obligations and will likely miss the next two Tuesdays... My brother has midweek "weekends" and so late summer family stuff all got planned midweek19:01
clarkbAnyway I probably won't be around on August 6 or 13 to run this meeting.19:02
fungii expect to be around and can chair either/both if we want to meet19:02
clarkbthanks!19:02
fungiwe can probably defer that decision until closer to the end of the week since we have some people not around today19:03
clarkbI'm also waffling on whether or not to attend Fossy whcih starts Thursday afternoon. I probably should go and use it is an opportunity to thank the folks that work on the osuosl stuff19:03
clarkbfungi: yup no rush on that19:03
clarkbI do have a working laptop again though so if I do go to fossy I won't be completely disconnected from the world. Just highly distracted :)19:03
clarkb#topic Upgrading Old Servers19:04
clarkbtonyb can't make it but did mention that noble images have been uploaded to all cloud regions but one. I'm not sure which that one is, but this implies that at least two rax regions were uploaded to which is good news as I expected those to be most difficult19:05
fungithat's exciting progress. thanks tonyb!19:06
clarkb++19:06
clarkblooking forward to more info when tonyb is able to share19:06
clarkbanything else to mention about upgrading servers? I've been distracted by services and clouds and stuff not servers lately19:07
fungii don't think so19:07
clarkb#topic AFS Mirror Cleanups19:08
clarkbwe just landed the change to cleanup centos 8 stream nodesets and similar stuff from opendev/base-jobs19:08
clarkbThe next step there is to clean the centos 8 stream images out of nodepool entirely.19:09
clarkb#link https://review.opendev.org/c/openstack/project-config/+/924790 Next step in CentOS 8 Stream Cleanup19:09
clarkbalso topic:drop-centos-8-stream19:09
clarkbbefore we merge 924790 we should check if there are any stuck nodes that need deleting, but  Ithink the solution to that is likely not going to chagne regardless of how we merge that change19:10
clarkbjust somethign to check on and clean up19:10
clarkbapologies that progress has been so slow on this, but we are slowly making progress which I'll take as a small win19:11
clarkb#topic Testing Rackspaces New Cloud Offering19:11
clarkbI'm going to send a followup email today/tomorrowish after double checking that this is more likely to be a better time for them19:12
clarkbI was told to wait a week and its been a week. Just want to check first before things get lost in the ether again. But otehrwise nothing new here19:12
clarkb#topic Reconsider queue depth for integrated gate19:13
clarkbThe alternative proposal for this to implement early failure detection has been implemented for tempest jobs19:13
clarkbThe reason for doing this in tempest is that those jobs are long running so have a larger impact if we can detect failures early and reset ASAP, but also beacuse these tempest base jobs are used everywhere and we can make a small change in one spot and have a large impact across many jobs19:13
clarkbSo far haven't seen any complaints or even questions about why things are failing before they are done. This would imply that it is working in a manner that isn't too intrusive which is great19:14
fungiyeah, a tempest job can fail on a test 25 minutes in and then keep running more tests for a further hour or more19:14
clarkba good next step may be to update openstack-tox-pyXY jobs to do similar though their impact will be smaller19:15
clarkbother than that I guess try to observe gate behavior the next time you notice a large queue and we can see if this has helped at all19:16
clarkb#topic Removing the Works on ARM Linaro Cloud from Nodepool19:16
clarkbLast week I received an email from the Works on ARM folks letting us know that the hardware hosting the linaro cloud will be removed/no longer accessible on August 10. I committed to shutting down our usage of that cloud this week which is now done as of this morning local time for me19:17
clarkbI have since sent a followup email to Kevin at linaro letting him know the cleanup on our side is done and that we can clean up the cloud stuff if necessary. I also offered to help19:18
clarkbI suspect that might end up being a die on the vine situation and the cloud will go away when the hardware goes away19:18
clarkbThis does mean we are down to operating arm jobs in one cloud region (the osuosl arm cloud)19:19
clarkbfungi: you've been helping out with this process anything else to add?19:19
funginope, i think we're basically done other than whatever kevin comes back with19:21
clarkb#topic Service Coordinator Election19:22
clarkbIt is that time of year again. I looked at when we had the last election and added 6 months and ended up with this proposal: Open candidate nominations from August 6 to August 20. Then if necessary we can have an election August 21 to 28. This timing also works out nicely to avoid the summit19:23
clarkbconsidering that attendance is light today, maybe we can see if others can ack this proposal as reasonable and then I'll send out email to the list making it official later this week?19:23
fungisounds good, thanks for keeping up with that!19:24
clarkband if there are any concerns or questions feel free to raise those too19:24
clarkbthanks!19:25
clarkb#topic Open Discussion19:25
clarkbI have more thinsg too that never made it to the agenda proper (you might have noticed the last item was missed too, I was very distracted by laptop reinstall things)19:25
clarkbFirst up dansmith is trying to clarify some confusion he ran into creating a new project here: https://review.opendev.org/c/opendev/infra-manual/+/92527519:25
clarkbI think landing that now if we can is a good idea just because it is strightforward and I don't want to forget later19:26
clarkbfungi maybe you have time to review that? it should be a quick one19:26
fungion it19:26
clarkbNext I've been looking ahead to mid term goals I've got for OpenDev: I would like to see us bump the default nodeset to ubuntu noble and change the default ansible version in our zuultenants to ansible 9 for example. A late october early november ish upgrade of Gerrit to 3.10 would also be great. I've also been thinking about trying to have more "OpenDev Zuul for our users"19:29
clarkbcontent this is still very early brainstorming but I've noticed a lot of people struggling with zuul concepts recently...19:29
clarkbof these the most straightforward might be the ansible bump. Noble presents challenges due to it having python3.12 which is a fairly big leap in the python workd19:30
fungicontent in the infra-manual?19:30
clarkbfungi: maybe? another thought was some sort of video19:30
clarkbaddressing things like people not understanding depends on and speculative git states, rarely providing direct links to debug failures, understanding when jobs run and why, and so on are what I want to address19:32
fungimakes sense19:32
clarkbZuul is this really great powerful tool and I want people to be able to take advantage of it19:33
clarkbanyway all of that gets mixed in with things like the summit and the ptg and the next openstack release. A lot of stuff is happening over the next few months and I wanted to bring these ideas up early so that we can try and fit them in19:34
corvus++19:34
clarkbfeedback and ideas welcome.19:35
clarkbAnything else to go over in the meeting today?19:36
fungii didn't have anything else19:37
clarkbsounds like that is everything. Thank you for your time today. And we can figure out what we are doing next week as we get closer to that point in time.19:39
clarkb#endmeeting19:39
opendevmeetMeeting ended Tue Jul 30 19:39:39 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:39
opendevmeetMinutes:        https://meetings.opendev.org/meetings/infra/2024/infra.2024-07-30-19.00.html19:39
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/infra/2024/infra.2024-07-30-19.00.txt19:39
opendevmeetLog:            https://meetings.opendev.org/meetings/infra/2024/infra.2024-07-30-19.00.log.html19:39
corvusthanks clarkb !19:39
fungithanks clarkb!119:39
fungi!!1!eleven19:39
opendevmeetfungi: Error: "!1!eleven" is not a valid command.19:39
fungieven opendevmeet doesn't get my jokes19:40

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