Tuesday, 2022-05-03

*** Guest1122 is now known as diablo_rojo_phone15:37
clarkbIt is almost meeting time. We'll get started in a couple minutes18:59
fungiahoy!19:00
clarkb#startmeeting infra19:01
opendevmeetMeeting started Tue May  3 19:01:33 2022 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
fricklero/19:01
clarkb#link https://lists.opendev.org/pipermail/service-discuss/2022-May/000334.html Our Agenda19:01
ianwo/19:01
clarkb#topic Announcements19:02
clarkbThere were no announcements on the agenda.19:02
clarkb#topic Actions from last meeting19:02
fungithough we are now running zuul/nodepool 6.0.019:02
clarkbyup19:03
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2022/infra.2022-04-26-19.01.txt minutes from last meeting19:03
clarkbThere were no actions recorded last meeting19:03
clarkb#topic Topics19:03
clarkb#topic Improving OpenDev's CD Throughput19:03
clarkbAs mentioned Zuulv6 and nodepool v6 have happend and we are running the released shas. Our versions won't show v6 until the next restarts we do as we restarted prior to tagging19:03
clarkbI'd still like to have a less formal more brainstorm like discussion wtih infra root on how this might affects us and so on. Is that something that might work for next week?19:04
clarkbmaybe we could do Monday UTC at the same time block as our Tuesday meeting?19:04
funginext week works for me19:04
fricklerI'd prefer something earlier, but that depends on what ianw thinks I guess19:06
clarkbya or maybe we do two chats. I can go as early as ~1530 UTC Monday19:06
fricklerthat'd be much better for me19:06
ianwyeah feel free to do it then, and i can catch up later19:06
clarkbok fungi  ^ does 15:30 UTC work for you?19:07
fungisure thing19:07
clarkbgreat we can just use meetpad probably? and I can share a link then19:07
clarkbAnything else on this topic or should we move on?19:08
clarkb#topic Container Maintenance19:09
clarkbI'm not aware of any movement on this since the base job cleanups and addition of python3.10 base images19:09
clarkbjentoio isn't here today, but I haven't seen any new changes either we can probably continue on19:10
clarkb#topic Spring Cleaning Old Reviews19:10
clarkb#link https://review.opendev.org/q/project:opendev/system-config+status:open+topic:system-config-cleanup could use second reviews19:10
clarkbfungi: frickler ^ If you have time to review those changes that would be much apprciated. I'm acting like an adopted change owner so didn't want to be the second reviewer on them. I also think that due to their age having some eyeballs on them is useful to catch things like what ianw found with the gerrit config updates19:11
jmorganhey19:11
clarkbjmorgan: oh hey I was looking for the wrong nick :)19:11
jmorgansorry for slacking but have been onboarding new role19:11
clarkbno problem. We've always got plenty going on too. I know how it goes19:11
jmorganI found my old password recently19:11
jmorganand I have a meeting conflict now sometimes19:12
jmorgananyway, I hope to be back at it sometime soon19:12
clarkbjmorgan: sounds good thanks19:12
clarkbLast week we also cleaned up ELK services and their puppetry and that came with additional change abandonments. I've been meaning to take a pass at system-config proper to abandon anything ELK/health/status/subunit2sql related that just doesn't apply anymore19:13
clarkbAny other change cleanup related ideas/options/etc ?19:13
ianwsounds good to me.  i'm sure i have some sub19:14
ianwsubunit2sql changes around that i'll clear out19:14
fungiwe took down status.o.o and associated broken things like reviewday19:16
fungialso i'm in the process of retiring about half the mailing lists for the openstack mailman site (any unused for 3 years or more)19:16
clarkbgood points any related changes for old lists or reviewday can be abandoned too19:17
clarkbso ya I'll try to make another bulk pass at that soon since there are things that can simply be abandoned due to not existing19:18
clarkb#topic Support for Jammy Jellyfish19:18
fungii hope you like jammin' too19:18
clarkbWe've got ubuntu mirroring in place for x86 and arm64 now19:18
clarkbThere are images for x86 at least, not sure about arm64 yet19:19
clarkband in some of my limited testing with zuul x86 appears to work. There are some small things I noticed like needing to specify python_version in jobs as a string not a float because 3.10 as a float is 3.1 and pythone 3.1 != 3.1019:19
fricklerthe reprepro issue still exists, but seems to clear up after repeated iterations19:19
clarkb#link https://review.opendev.org/c/opendev/base-jobs/+/840355 Add jammy nodesets to base-jobs19:20
fricklerthe devstack job on jammy also works fine except for distro OVN, yatin is working on that19:20
clarkbOnce we're happy enough with the bootstrapped state we should probably land that change or something like it to add nodesets19:20
clarkbfrickler: devstack has pretty broad coverage of all things linux too so that is a good indicator it largely works19:20
fungii expect the libzstd errors will trigger any time an affected package is pulled, which won't be all the time since reprepro will only pull changed packages on rerunning19:20
clarkbAs far as things that are missing goes we should add arm64 images and labels, and then we also need a wheel mirror19:21
fricklerfungi: that's what it looked like to me, too19:21
clarkbianw: after thinking about the openafs packaging it probably makes sense to add jammy builds to our ppa for consistency then we don't have to special case jammy19:21
fricklerfor wheel the builds in general were broken, but maybe got fixed today19:21
clarkbianw: I realized that all the jobs and tools that install openafs would have to have conditions and that just seems like extra work19:21
ianwyeah i think given the history it's worth it to keep the ppa around19:22
clarkbfrickler: is that related to the centos 7 issue? if so I think we are really close to getting that addressed in dib19:22
ianwwe've had to emergency push changes into it before, and although https://launchpad.net/~openafs is currently looking up-to-date, we've been caught with it not being before19:23
fricklerclarkb: not sure, it was related to afs for c9 missing iiuc19:23
ianwyeah, the bit i missed was the publishing steps on c9 wheels was failing19:24
ianwi've updated the rpms and https://review.opendev.org/c/opendev/system-config/+/839841, which has merged now, should fix todays run19:24
ianwi'm thinking of adding installing openafs to the base wheel jobs 19:24
ianwthe problem is that takes quite a while to compile, and isn't useful other than for testing we didn't forget to add things like with a new distro.  it's probably overkill for the amount of times we actually do that19:25
ianws/base/test/ -- you get the idea; do it in the gate19:25
clarkbah ok so nothing that would stop jammy19:26
clarkbthe big jammy thing would be the ppa for openafs19:26
clarkbianw: does that require uploading a new source package entirely? Or can we just tell lp to build for jammy too?19:26
ianwyeah i can do that today, should be straight forward19:26
clarkbthanks19:26
clarkbI can probably write up some changes to get arm64 jammy stuff moving along too19:27
ianwi *think* you have to add the distro then re-trigger with an upload19:27
ianwi don't think we added jammy to the arm64 dib functional tests; that's probably a good start19:27
clarkb++19:27
clarkbAny other Jammy related items? We're running jobs successfully on jammy now which is great progress. Thank you frickler for getting this started19:28
clarkb#topic Shutting Down Ethercalc19:30
clarkbOur list of services that are not bionic or newer is very small now. One service that stands out is ethercalc19:30
clarkbThe ethercalc service itself doesn't seem super well maintained (last I looked they haven't been modernizing the build tooling) and the software lacks historical records for the sheets which people expect due to etherpad19:31
clarkbon top of that it is mostly used for the PTG and other tools can be used there instead (PTGBot for example)19:31
clarkball of these has me leaning strongly towards shutting down this service entirely rather than updating it to focal/jammy19:31
clarkb*all of these things19:31
fungimy opinions on the matter mirror yours19:32
ianwyeah it's a shame, i've used it from time to time when we have data that has benefited from some simple analysis.  but practically it seems to be an abandonded project19:32
clarkbAre there any concerns from other infra-root for doing this? In my head we'd send an announcement for this to service-announce@lists.opendev.org planning to shut it down at the end of May. Then we can shutdown the instance, snapshot the instance, and delete the instance. Then do all the related config mgmt clean up19:32
fungiit was a neat idea in order to try to persuade community members not to rely on google spreadsheets, but it's unfortunately a liability19:33
clarkbok I'm not hearing any "please no!!!" :) I'll work to send out an announcement that this is our plan to communicate it with our user base19:35
clarkbfwiw I did bring it up with people who do a lot of the PTG planning like diablo_rojo_phone and there wasn't any major concern from them either19:35
diablo_rojo_phoneWe can totally just use the bot for teams to sign up with. 19:36
diablo_rojo_phoneSo as to avoid google sheets19:36
clarkbsounds like that may be it for ethercalc.19:37
clarkbboth in this meeting and long term :)19:37
clarkb#topic Open Discussion19:37
clarkbAnything else?19:37
corvusi have a quick thing19:38
corvushttps://zuul-ci.org/docs/zuul/6.0.0/releasenotes.html#relnotes-4-1-0-deprecation-notes19:38
corvusi don't believe that the opendev tenants have universally completed that migration19:38
clarkbcorvus: probably not. In fact just a month ago it was the OSA project saying that queues are pipeline specific and being confused about it19:39
corvusi plan on sending out a reminder to zuul-discuss about that, along with a script ppl can use to find places where updates are necessary19:39
clarkb(I tried to clarify)19:39
corvuswe should have removed that already, but the v6 release needed to happen before the next ansible release and i didn't want to hold it up19:39
corvusbut i think it's fairly likely that we'll complete that before the next major rev19:40
corvusso would be good for opendev tenants to update19:40
fungiagreed, thanks! that script will help us double-check19:41
clarkbjust skimming codesearch there are a few places I see. The script would be great19:41
clarkbfreezer, zaqar, tripleo-ci, os-net-config, ironic and so on19:42
clarkbthat list wasn't exhaustive19:42
clarkbAnything else?19:43
corvus(nak from me)19:43
funginope19:43
clarkbIn that case thanks everyone. We'll be back here next week same time and location. As always feel free to reach out on the mailing list (service-discuss@lists.opendev.org) or IRC (#opendev) if something comes up. We don't need to wait for the meeting to talk to each other :)19:44
fungithanks clarkb!19:45
clarkbAnd we can all have 15 minutes of breakfast/lunch/dinner/etc back19:45
clarkb#endmeeting19:45
opendevmeetMeeting ended Tue May  3 19:45:11 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:45
opendevmeetMinutes:        https://meetings.opendev.org/meetings/infra/2022/infra.2022-05-03-19.01.html19:45
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/infra/2022/infra.2022-05-03-19.01.txt19:45
opendevmeetLog:            https://meetings.opendev.org/meetings/infra/2022/infra.2022-05-03-19.01.log.html19:45

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