Tuesday, 2022-12-13

clarkbmeeting time19:00
ianwo/19:01
clarkb#startmeeting infra19:01
opendevmeetMeeting started Tue Dec 13 19:01:22 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
clarkb#link https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/thread/6DVJVHEPMASFL4PQWIQZFUT3H6T5BXP5/ Our Agenda19:01
clarkb#topic Announcements19:01
clarkbI didn't have anything to announce other than what ended up in our agenda19:02
clarkbanything else to make note of?19:02
clarkbthis meeting does conflict with a world cup semifinal game19:03
fungiwill you be able to announce the winner at the end of the meeting?19:03
clarkbno the game is at least 90 minutes long and we only have 60 minutes here19:03
clarkbok lets dive right in then19:04
clarkb#topic Bastion Host Updates19:04
clarkb#link https://review.opendev.org/q/topic:prod-bastion-group this is the lower priority stack for parallel runs. Ideally landed whe nwe can observe carefully19:04
clarkb#link https://review.opendev.org/q/topic:bridge-backups tooling to backup content in encrypted tarball19:04
clarkb#link https://review.opendev.org/c/opendev/zone-opendev.org/+/867540 bridge CNAME19:05
clarkband this last change came out of a reminder to corvus today not to run the zuul restart playbook from old bridge19:05
clarkbI think we are really close to being able to shutdown old bridge but suspected that the backup tooling might want to be used on old bridge as a final wrapup?19:05
clarkbI'll try to find time to revie wthose but anytime gpg and encryption is involved I like to take my time and do my best to actually understand it19:06
clarkbianw any other thoughts on what our next steps here should be?19:06
ianwsure -- yes i can probably shutdown the old bridge at this point, it's just been waiting on finalising the other changes19:07
ianwif infra-roots would like to confirm that they have everything they want from their ~ we can shut it down19:07
clarkbI think I did look at that and then left notes on the etherpad about things like the dns stuff and as far as I know all of that has been addressed. But I'll double check19:07
clarkband I guess we can shutdown before deleting too19:08
corvusi don't need anything from ~corvus; "delete at will" from me19:08
ianwyep no need to delete straight away, but also probably good to not have it lying around once we've moved on19:08
clarkb++19:08
* clarkb makes a note to take a look (probably after the afternoon school run)19:09
clarkbanything else?19:09
fungii've cleaned out my homedir on old bridge19:09
ianwno that's it, thanks19:10
clarkb#topic Mailman 319:10
clarkbI think all of the oustanding change srelated to the mm3 migration have landed at this point?19:11
fungiyes19:11
clarkbI was curious if we know if the site_owner update has been applied. I believe that would require a container restart and I'm not sure if that happened19:11
fungiwe haven't restarted the container yet, i don't thinkl19:11
clarkbfungi: ^ you might know or be able to check? I think you look in /etc/mailman/mailman.conf in the core container19:11
fungialso i noticed that the top-left corner of https://lists.zuul-ci.org/archives/ says lists.opendev.org, not sure yet where to configure that19:12
clarkbok I think that is worth following up on and restarting if it hasn't happened yet just to ensure we don't get bitten by that later if something is wrong19:12
clarkbfungi: the thing I noticed about that is the link itself has the correct target19:12
fungiright, it's just the name apparently19:12
clarkbfungi: for this reason I suspect this is a bug in mailman itself where they apply the value to the target but not the rendered name19:12
clarkbmight just need to stick the same string in both locations of the template or something19:12
fungiapparently also the page <title> says "Available lists - lists.opendev.org"19:13
fungibut as far as that hyperlink goes, it's relative which i guess is why it doesn't go to the wrong site19:14
fungilooks like this:19:14
fungi<a class="navbar-brand" href="/archives/">lists.opendev.org</a>19:14
clarkbah19:14
clarkbprobably need to dig up the source for that and take it from there. It might be missing config or it may be buggy vhost handling19:15
fungiso i expect there's a site-specific name we have to give hyperkitty somewhere19:15
fungii didn't notice postorius doing it19:15
clarkbI will say as a user I find this much easier to use19:15
clarkbon the whole I think it is a big improvement even with the small issues like that19:15
corvushttps://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/UAHC7L2M3KCKQXRQY3QCZZEQFGK4L4PK/19:16
fungioh, though i see that the page <title> for e.g. https://lists.zuul-ci.org/mailman3/lists/ says "List Index - lists.opendev.org"19:16
fungiso i guess postorius needs it somehow too19:17
clarkbsound slik ewe need to look at the django site admin19:17
fungiseems likely19:17
clarkb(that should work, we interacted with it on the test node)19:17
corvuspostorius also uses site_name for the title  https://gitlab.com/mailman/postorius/blob/master/src/postorius/templates/postorius/base.html#L1019:17
corvusso at least, that's a thread to pull on :)19:17
clarkb++ good find19:17
clarkbfungi: there should be a django admin user set as part of the ansible vars and you can use that to login via the admin url iirc19:18
fungiyeah, wondering if this is something we should be setting via an api on creation or just accept that we'll have to manually edit it for each site19:19
clarkbunfortunately the docs aren't so great for details like this19:19
clarkbbut we can usually work backward fro mthe expected process and figure it out19:19
clarkbanything else?19:20
corvus(or is it something we can set with proxy headers?)19:20
clarkbWe can dig into this more after the meeting. There are a few other topics I want to cover so we'll continue and can swing back to this later if necessary19:22
clarkb#topic Quo vadis Storyboard19:22
clarkb#link https://lists.opendev.org/pipermail/service-discuss/2022-October/000370.html19:22
clarkbno new movement on this19:22
corvusstatus quo vadis19:22
clarkbI've got a number of writing exercises on my todo list and am thinking maybe I/we should just start drafting a plan in etherpad since feedback on the list isn't happening?19:23
clarkb(that might actually mean drafting a couple of possible proposals and then choosing one)19:23
clarkbthere are no good options so we should maybe write them down in enough dtdail to make the least painful decision19:24
clarkbno one is screaming, I'll take that as the next step here and pin th etodo to my list19:25
clarkb#topic Gerrit 3.619:26
clarkbianw upgraded Gerrit from 3.5.4 to 3.6.3 yesterday19:27
ianwwell i pushed the buttons but everyone, mostly zuul, helped get it there :)19:27
clarkbseems to have gone well. The only issues I've seen so far are mostly around the UI changing19:27
clarkbThe main thing tripping people up seems to be how Gerrit renders votes19:28
clarkbin particular it summarizes votes and doesn't put names next to them in the requirements section (it does put them in the reviewers section so you have to look elsewhere)19:28
clarkbit also seems to only show required labels for merging in the change listing pages19:28
clarkbthis means review-priority and similar type sof labels that openstack use don't show up in the list summaries19:29
corvusbecause they're not submit-requirements, yeah?19:29
clarkbcorvus: yes they are purely informational/trigger requirements19:29
clarkbthat seems to be the criteria for including them in the UI listings19:29
clarkbit also looks like change owners might be able to delete positive votes on their changes. This doesn't seem harmful but may create confusion at some point19:30
corvusis something like a submit requirement that accepts any or no value a possible workaround?19:30
ianwthe summaries is maybe worth raising?  although the answer might be "make a dashboard, it works better anyway"?19:30
clarkbcorvus: yes that was one suggestion from fungi. I think we have options19:31
clarkbianw: the problem with dashborad is they don't show up thre either so it can be confusing19:31
clarkbso you need a dashboard with lists for each possible vote value19:31
clarkbI don't know how to make a submit requirement that accepts any value but if we can express that that may be the best option19:31
ianwyeah, i meant a separate section like "changes with backport-candidate" or whatever.  but yeah, it's not mixed in19:31
corvuslooks like a non-submit-requirement label is called a "trigger vote"?19:32
clarkbcorvus: yes these are trigger votes currently19:32
ianwi wonder with that approach though, will we ever see anything on the overview page that isn't a grey, crossed circle?19:32
ianwbecause our submit requirements are really not the same as the idea of "things that need to be done before you can push the merge button", if that makes sense19:33
ianwbecause we never push the merge button, zuul does.  so we're "ready to submit" when we have a +2 vote and +1 verified19:33
ianwthe +w is our "merge button"19:34
clarkbya  ithink a followup thing might be to have a conversation upstrema about making this directly configurable somehow? like an annotation in the label definition?19:34
clarkbthen we can more directly express how our labels are used without assumptions based on upstrea mgerrit workflows19:34
ianwdoes anyone happen to have a screenshot of the old layout, perchance?  19:35
corvusif the suggestion is that we would like to avoid having Verified+2 be a submit requirement, i don't agree with that19:35
clarkbI don't, but our CI will take them iirc19:35
clarkbcorvus: no i think it is about how we render the requirements19:36
clarkbyou would still need a +2 but we can treat a +1 as "ready for zuul"19:36
corvusokay.  i may not be understanding where ianw was going with the merge button thing then.19:36
fungibut we might like being able to avoid having "review-priority" as a submit requirement19:36
clarkbcorvus: the way they render submit requirements today is built around trying to show you what oyu need to click the submit button. But in our system we would ideally render it to show what is necessary for zuul to gate it19:37
ianwcoruvs: i'm just saying that i think the idea of the new column is to show you "things that are ready to merge".  but it will never really show anything but a grey circle for us19:37
clarkbianw: and that specifically workflow19:37
corvusfungi: yes.  my only suggestion there was maybe a submit requirement can have a "satisfied by no vote" to work around the fact that it's not displayed there.  that's all.  no idea if that's possible, just thought it worth looking into.19:37
clarkbbecause its usually set to 0 until set to +1 to trigger gating19:37
corvusianw: ah you're talking about the status column19:37
corvusianw: that is interesting and unfortunate19:38
ianwperhaps to move it on, i can come up with a draft email, or maybe two really -- one about the status column -- one about the other flags -- and we can revise it between us and send to gerrit for feedback?19:39
clarkb++19:39
fungisounds great19:40
ianwok, will do something up in an etherpad and let people know19:40
corvus(we could, conceivably, lift the verified+2 requirement and rely entirely on zuul, but i think it's better to express the requirements in gerrit itself)19:40
corvus++19:40
clarkbthanks. And thank you to everyon ewho made the upgrade happen and happen so smoothly. Now we need to look at 3.7 which might be more complicated :?19:41
clarkband ya lets move on we have 19 minutes left and a couple more things I'd like to cover19:41
clarkb#topic Tox v419:41
clarkbLast week tox released 4.0.0 and that very quickly broke all the things. This version is a rewrite and isn't backward compatible19:42
clarkbto stop the bleeding we pinned the tox install to <4 in zuul-job' ensure-tox19:42
clarkbbut the plan is to remove that cap next week19:42
clarkbWhat this means is we should be prepared to update our tox.ini files to be compatible with v4 and v3.19:42
clarkb#link https://review.opendev.org/c/opendev/system-config/+/867269 system-config tox v4 compat19:42
clarkbA change for openstack/project-config has already landed19:43
clarkbMost of the issues seem to be related to whitelist_externals becoming allowlist_externals and unlisted commands becoming errors instead of warnings19:43
clarkbneutron is running into a new issue where the project isn't installed to the venv for some reason that will need to be sorted out19:43
clarkbso far though with zuul-jobs, project-config, and system-config it hasn't been too bad19:44
fungiseems to be ignoring the usedevelop option19:44
clarkbso ya reviews and changes welcome to help get ahead of that. But I'm sure we'll find problems once we uncap too19:46
clarkb#topic Winding down iweb19:46
clarkbEarlier this year we were told the iweb cloud would be going away. We thought it might initially go away mid year but they kept it running until the end of the year19:46
clarkbwe are at the end of the year now and need to shut it down. Ideally in a graceful way for nodepool to avoid manual cleanup19:47
clarkblink https://review.opendev.org/q/topic:wind-down-iweb19:47
clarkbI've got a stack of changes that should do the bulk of this work. We will need to manually delete the mirror node too19:47
clarkbI'm happy for those to land anytime between now and about this time next week. After that my ability to pay attention will be decreased19:47
clarkbOnce we've done the cleanup I'll send them an email saying we've moved out19:48
ianw++19:48
ianwhopefully avoid end of lease cleaning fees :)19:48
clarkbso ya reviews welcome and I'll do my best to get that cleared out gracefully19:48
clarkbDue to time constraints I'm going to skip the vexxhost rescue instance and bionic upgrades topics. There isn't much new for them as far as I know19:49
clarkb#topic End of year Holiday party19:49
clarkbcorvus: suggested last week that our December 20 meeting coul dbe treated more like a holiday party. I like this idea. We've spent a ton of time this year running opendev we can take an hour to have some fun :)19:50
clarkbOne idea I've got is we can play games on board game arena if people are interested. You do need to create a free account but a paid account can host games that include free tier players19:50
clarkbI'm happy to upgrade to a paid subscription for this and do the hosting19:50
corvus☃️19:50
clarkbBut I'm also open to other ideas19:50
clarkbhttps://en.boardgamearena.com/ sorry board game erna19:51
corvusi'm in19:51
clarkbwe can use meetpad for voice and play ticket to ride or carcassone etc19:51
ianwok, wow i'd never heard of that site!  i'm surprised they have licensed so many games19:51
fungiit's quite an amazing collection of games they've implemented, yes19:52
fungiexcellent for when you want to remotely play board or card games with friends19:52
clarkbthe ui can be clunky at times but a lot of the games are actually really well done19:52
ianwit looks like my games cupboard online, haha19:52
fungii was thinking of upgrading my account to paid as well19:52
clarkbI haven't started on the annual report content  Ineed to write for 2022 yet, but it was a busy year just off the top of my head. So ya thank you everyone and lets have som efun next week :)19:54
ianw++19:54
corvusclarkb: thanks!19:54
clarkbI'll send out an agenda email but give details on where to sign up and what meetpad room we'll use19:54
clarkb#topic Open Discussion19:55
clarkbAnything else before our hour is up?19:55
clarkbI'll probably be floating around after the 25th but attempting to focus on writing those annual report things19:56
clarkbI expect things will be quiet as they usually are19:56
clarkbI hope everyone else is able to enjoy some down time too19:57
clarkbIt might snow here next week too. I'll have to get the sleds down19:57
clarkbsounds like that is it. Thank you everyone!20:00
clarkb#endmeeting20:00
opendevmeetMeeting ended Tue Dec 13 20:00:06 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/infra/2022/infra.2022-12-13-19.01.html20:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/infra/2022/infra.2022-12-13-19.01.txt20:00
opendevmeetLog:            https://meetings.opendev.org/meetings/infra/2022/infra.2022-12-13-19.01.log.html20:00
fungithanks clarkb!20:00

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