Tuesday, 2021-06-01

*** jentoio has quit IRC00:34
*** jentoio has joined #opendev-meeting00:59
*** jentoio has quit IRC01:25
*** jentoio has joined #opendev-meeting01:28
ianw#footest04:30
ianw#help04:30
ianw#listplugins04:30
ianw!help04:39
opendevmeetianw: (help [<plugin>] [<command>]) -- This command gives a useful description of what <command> does. <plugin> is only necessary if the command is in more than one plugin.04:39
ianw!listplugins04:39
opendevmeetianw: Error: "listplugins" is not a valid command.04:39
ianw!help echo04:39
opendevmeetianw: Error: There is no command "echo".04:39
ianw!listcommands04:40
opendevmeetianw: Error: "listcommands" is not a valid command.04:40
ianw!list04:40
opendevmeetianw: Admin, Bugtracker, Channel, ChannelLogger, Config, MeetBot, Misc, Owner, Services, and User04:40
*** gouthamr_ has joined #opendev-meeting14:34
*** gouthamr has joined #opendev-meeting14:47
*** gouthamr_ has quit IRC15:12
*** gouthamr has quit IRC15:13
*** gouthamr has joined #opendev-meeting15:14
*** gouthamr is now known as identify15:18
*** gouthamr has joined #opendev-meeting15:19
*** identify has quit IRC15:20
clarkbAnyone else here for the infra meeting? we will get started in a few minutes18:59
fungiahoy, mateys!19:00
ianwo/19:00
clarkb#startmeeting infra19:01
opendevmeetMeeting started Tue Jun  1 19:01:19 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-June/000252.html Our Agenda19:01
*** frickler has joined #opendev-meeting19:01
clarkb#topic Announcements19:01
clarkbI didn't have any announcements.19:02
fungiwelcome to oftc?19:02
clarkbIt is a later topic in the meeting but ya we are here on oftc now19:02
clarkbI know a few of us are still hanging around in a few freenode channels but I'll probably clean those up next week19:03
fungihope everyone found us okay19:03
fungiand yeah, we can discuss later in the meeting19:03
clarkb*clean those up in my client.19:03
clarkbBut ya welcome and let us know if you have qusetions/concerns/problems with the switch19:04
clarkb#topic Actions from last meeting19:04
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-05-25-19.01.txt minutes from last meeting19:04
clarkbThere were no actions and even if there were I think we ended up fairly swamped by irc and related tasks19:04
fungia swamp it was19:04
clarkb#topic Topics19:05
fungihow topical19:05
clarkbThe most generic of topics. I reorged the meeting agenda as discussed last week19:05
clarkb#topic Switch to OFTC now largely complete19:05
fungithere's some patches up to convert ptgbot19:05
clarkbfungi: want to give us an update on where we are with the switch and any outstanding issues we need to clean up?19:05
fungiand someone still needs to follow up on the #openstack-sahara registration19:06
fungii also have a patch out there to drop #edeploy from the statusbot config19:06
clarkb#link https://review.opendev.org/c/openstack/ptgbot/+/793792 ptgbot oftc conversion19:07
clarkb#link https://review.opendev.org/c/opendev/system-config/+/793813 drop edeploy channel from statusbot config19:07
fungion the topic of statusbot, we've seen an unexplained crash but the way it logs fails to capture exceptions/tracebacks, so it's running foreground currently in a root screen session on eavesdrop with an su to the ptgbot account19:07
clarkbfungi: and I guess we'll keep running it that way in the hopes of catching the crash?19:08
fungiyeah19:08
fungilikely some unforeseen problem in the hurried python3 conversion we did for it over the weekend19:08
fungiand ianw has been tackling the converged bot/limnoria spec, has a poc up i believe though i haven't had time to look19:09
clarkbfungi: for sahara we need them to give accessbot master perms via chanserv?19:09
clarkb#link https://review.opendev.org/q/topic:%22limnoria%22+status:open Limnoria bot rewrite19:09
fungicorrect on #openstack-sahara19:09
clarkbianw: based on the commits there you're porting the existing supybot config to limnoria?19:09
fungithe pending patch to add #openstack-sahara back to acessbot and gerritbot is...19:10
fungi#link https://review.opendev.org/792857 Revert "Accessbot OFTC channel list stopgap"19:10
ianwthat stack (completely uncommented) is intended to port meetbot to python3/limnoria19:10
clarkbianw: nice, I'll try to take a look today19:10
ianwhowever limnoria is so far exactly the same as supybot19:10
ianwi will clean up that stack iwth actual change comments19:10
clarkbianw: sounds good19:11
ianwit's probably more useful to have a poke at it in #opendev-sandbox atm and see what's right/wrong19:11
clarkbah ok interactive debugging more so than code review19:11
ianwyeah, the other part is19:11
fungioh, that reminds me, the supybot package on eavesdrop has one of its files edited to basically roll in a newer (but many years old) commit which never made it into ubuntu19:11
ianw#link https://review.opendev.org/c/opendev/system-config/+/79370419:12
ianwwhich builds a limnoria/meetbot container19:12
fungiwhich makes the limnoria work slightly more important19:12
clarkbfungi: ++19:12
ianw#link https://review.opendev.org/c/opendev/system-config/+/793719/819:12
ianwis then installing that19:12
ianwi've tried my best to port over the existing config, but there's *a lot* of options in there19:12
ianwsmall details all still WIP, but big picture comments definitely useful at this point.19:13
clarkbcool, I will attempt to interact with the bot and see if that produces any feedback19:13
fungialso more generally, we introduced some known security risks during the bot conversion by switching some of them to identify where previously they authed at connection time, and by no longer having an atomic means of verifying the nicks they get messages from are authentic19:13
clarkbfungi: we should set enforce on our nicks with nickserv ya?19:14
ianwi don't know if supybot had certificate support, but there are options in it for limnoria19:14
*** corvus has joined #opendev-meeting19:14
clarkbianw: its verification of the nicks interacting with the bots that is the struggle19:14
fungiclarkb: yes, it's already set for our the bot accounts but we should encourage people to set it on their own nicks19:14
fungiif we can set the new converged bot up to do certfp auth, that eliminates one of those risks19:15
clarkbother networks have extensions that include with every message the auth/ident status when each message is sent but oftc does not19:15
fungior if it does, i wasn't readily able to find it19:15
clarkbOverall I think the transition went well. We hit a few speedbumps but nothing major and we managed to work through almost all of them. Thank you to all who helped with this process.19:16
fungigranted, the cap freenode was relying on for that also didn't seem to be part of the irc3 standard caps19:16
clarkbfungi: it was but then got superceded by another cap that does similar19:16
fungiahh, yeah i'll admit i only skimmed them to see which ones were implemented in freenode and oftc19:17
clarkbalright anything else on this topic or should we move on?19:17
fungii think we can move on, but please anyone with questions or problems do reach out to us19:17
clarkb#topic Gerrit Account cleanup19:18
fungiand i have an oftc-related policy question to bring up during open discussion if there's time19:18
clarkbnoted19:18
clarkbFor gerrit account cleanups this is a reminder that I've got a list up of slightly more dangerous but probably safe account cleanups on review19:18
clarkbWe've all been busy and not able to review that list (and at this point I feel like I should rereview it myself), but if you get time to look over it that would be great19:18
clarkbI think doing that cleanup in a multistep process where we disable teh accounts first then sit and wait a while then cleanup the conflicting external ids has worked well and should be relatively safe here. When done I think we end up with about 80 accounts that we should reach out to users about19:19
clarkb#topic Refreshing SSL certs19:20
clarkbWe have made some good progress with these. A number of services are now using LE certs. We also cleaned up certcheck a bit.19:20
clarkbThe last remaining cert we need to renew is for wiki and I'll be doing that manually after this meeting because we don't have that service in config mgmt19:20
clarkbThen we should be good for another year.19:21
fungithanks!19:21
clarkbIf you notice old certs hanging around that may be due to apache not cleaning up all child processes when we tell it to reload. I think the risk is low but it does happen19:21
clarkbDefinitely say something if you see a cert expiring soon19:21
fungiand we do have workarounds we can apply for cases like that if they keep cropping up19:21
clarkb#topic Switch Vexxhost to provide only specialized labels in Nodepool19:22
clarkb#link https://review.opendev.org/c/openstack/project-config/+/78576919:22
clarkbThis has been rebased and looks mergeable19:22
clarkbfungi: did you want to discuss it further or just ask for reviews and possible +A at this point?19:23
fungii guess i was hoping for some consensus on either the ml or review that this was something we wanted before approving it19:23
clarkbok so more than just one or two +2s before approving it19:23
fungibut maybe the lack of general interest in the topic is a sign that there's no objection19:24
fungii can go ahead and approve it after the meeting, it's always easy enough to revert19:24
clarkbI added my thoughts to the change in review and ya basically said it should be safe and it is easy to revert if we discover it causes problems somehow19:24
clarkb#topic Server Upgrades19:25
clarkbOnce I've sorted out the wiki ssl cert I plan to set up a hold for change that runs system-config-run-lists and then do in plcae upgrades of the resulting test nodse as a first pass check of that upgrade.19:26
clarkbThen based on how the test nodes handle it we can decide if we need to do a snapshot of the prod list server(s) and test that upgrade with real prod like images19:26
fungithat sounds like a reasonable check19:26
clarkbI don't expect any trouble. iirc last time we did this we had to modify some mailman pipelines but otherwise it went well19:27
clarkb#topic Scheduling project renames19:28
fungiwe've still just got the one requested for now, i guess19:28
clarkbI still feel like it is a bit early to schedule these as we're still coming up for air from the last fire... Maybe next week we'll have some thoughts based on how playbook updates go?19:28
clarkbya I'd like to think we can do it this month sometime. I'ev got family visiting through the month but should have time for this at some point. But I need to catch up with everything else going on before I can commit to that19:29
fungii think the osf/* repos are probably wanting to move to something like openinfra/ but i don't know that i have time to push on the patches and coordination for that as it's not at all urgent19:29
clarkbfungi: do you think someone else at the foundation might be interested?19:29
clarkbmaybe jimmy?19:29
funginot really sure, tbh19:29
clarkbI guess we can ask around and see19:29
fungican ask around, yeah19:29
clarkbit would be good to do more than one if we can19:30
fungishould probably be all of those in one go19:30
clarkbok, I think that is all for the agenda. I ran through it fairly quickly.19:31
clarkb#topic Open Discussion19:31
clarkbfungi: plenty of time for your extra item19:31
fungiyeah, so there's this change...19:31
fungi#link https://review.opendev.org/793999 Rename IRC channel for Octavia19:31
fungiit raises the question of whether we should continue to squat abandoned channels when we move or otherwise clean our bots out of them19:32
clarkbhrm my initial though is that keeping things cleaner is a good thing particularly after all the audit work you had to do19:32
fungigiven there's no join forwarding on oftc, there's less of an incentive to keep those old channels registered19:32
fungiin a similar vein, i'd like to try to root out other abandoned channels (the ones we log are easy to audit, those we don't log are not so easy)19:33
clarkbI'm ++ on renaming and dropping the old for simplicity19:33
corvusyeah; and we're not actually revoking our access; we could conceivably still step in and set a topic if we needed to19:33
fungialso to be polite to the fine folks who run the servers, i feel like we should unregister channels when we stop using them19:33
corvus(no guarantee of course, but mostly just saying we're not likely to box ourselves into a corner and be sad)19:33
fungiif we unregister them, we would theoretically lose control of them19:34
corvusor, should we consider doing all of that 6 months after we stop using them?19:34
fungiyeah, i think a delay before cleaning up is warranted, for sure19:34
clarkbdoing it with a delay seems reasonable. We still eventually reduce network overhead, but give us an out if things change in the short term19:34
corvusbecause if we are going to unregister them, then losing privs immediately after the switch might make us sad19:34
fungiand we can always appeal to the network operators in the (very rare, i'm sure) case where we'd need to do something to regain control of a channel we unregistered19:35
corvusi wouldn't want someone to accidentally (or purposefully) hinder a move by squatting the channel right as the move happens19:35
fungiso maybe we should comment out those entries with a date or something, so we remember when to unregister them?19:36
fungii don't think a heavyweight process is warranted19:36
clarkbfungi: ++19:37
fungialso worth noting we haven't rewritten the channel renaming section of our system-config irc doc yet, so i can take a shot at drafting the new policy there19:37
fungipolicy/process19:37
clarkbthanks19:37
fungiand big thanks to frickler for rewriting a good chunk of that document19:38
fungii've already pointed folks to the updated channel registration instructions19:38
fungiso it's definitely come in handy19:38
corvuscomment process sgtm :)19:39
corvusif we have time for another unscheduled topic...19:40
clarkbwe do, go for it19:40
corvusi pushed up a zuul spec to see if the zuul project can achieve consensus to move to matrix; i consider that step 0 before talking to opendev about that19:41
corvuslike, my understanding of how we want these relationships to work is for projects to express desires/needs/etc and work with opendev to achieve them19:41
fungisounds right to me19:41
clarkbyup (also Ishould add repsonding to that spec to my todo list)19:42
corvuscool19:42
corvus#link zuul spec about using matrix https://review.opendev.org/79366919:42
corvusthere's some positive response already19:42
corvusi think it would be useful for people to weigh in both with their zuul hat and their opendev hat19:42
corvussince most of the folks who haven't weighed in yet are in the overlapping area on the venn diagram :)19:43
clarkb++19:43
corvusand if that proceeds, then i figure i'll be working on an infra-spec as a followup and talking about it more here19:44
fungiwhich is probably at least subconsciously intentional since i personally want to know what other folks think before i potentially go clouding the input with my overlapping opinion space19:44
fungibut more generally, i'm comfortable connecting to both irc and matrix from the same unified client for different communities, some of which aren't on irc networks which have matrix bridges19:45
clarkbAnything else? if not we can get to breakfast/lunch/dinner 15 minutes early :)19:46
fungiso weechat having a matrix plugin for matrix-only channels and native irc protocol support for non-matrix-accessible channels is going to be necessary for me anyway19:46
clarkbfungi: ++19:46
clarkbI'll go ahead and call it there. Thank you everyone. We'll see you here next week19:47
clarkb#endmeeting19:47
opendevmeetMeeting ended Tue Jun  1 19:47:51 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:47
opendevmeetMinutes:        http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-06-01-19.01.html19:47
opendevmeetMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-06-01-19.01.txt19:47
opendevmeetLog:            http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-06-01-19.01.log.html19:47
clarkbnow we should go check those logs :)19:48
fungithanks clarkb!19:48
corvusclarkb: thanks!19:48
clarkbthe logs lgtm. Happy to see meetbot has handled the network switch without much fuss19:48
fungiyeah, log links worked fine for me19:48
fungithe only complicated part was it embedding the network name into the logfile path19:49
fungibut an atomic mv of the old directory to the new one was trivial19:49

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