Tuesday, 2021-05-18

*** hamalq has quit IRC04:27
*** sboyron has joined #opendev-meeting06:06
*** hashar has joined #opendev-meeting07:07
*** hashar is now known as hasharAway07:07
*** hasharAway is now known as hashar07:43
*** hashar has quit IRC13:07
*** hashar has joined #opendev-meeting13:08
*** openstack has joined #opendev-meeting14:08
*** ChanServ sets mode: +o openstack14:08
*** openstackstatus has joined #opendev-meeting14:11
*** ChanServ sets mode: +v openstackstatus14:11
*** hashar is now known as hasharAway14:48
*** hasharAway is now known as hashar15:45
*** hashar has quit IRC18:02
*** hamalq has joined #opendev-meeting18:05
*** rosmaita has joined #opendev-meeting18:55
clarkbAnyone else here for the meeting? We will get started in a couple of minutes18:59
rosmaitao/18:59
ianwo/19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue May 18 19:01:03 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
clarkb#link http://lists.opendev.org/pipermail/service-discuss/2021-May/000234.html Our Agenda19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbThis didn't make it onto the agenda, but I'm planning to take a day off on the 20th (Thursday)19:01
clarkbshouldn't really impact anything, jsut a ehads up19:01
clarkb#topic Actions from last meeting19:01
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-05-04-19.01.txt minutes from last meeting19:02
clarkbianw: you had an action for pbx cleanup. I believe this has happened. Anything else to say about that one?19:02
ianwnope, all gone19:02
clarkbthank you for working on that. I think meetpad/jitsi meet is the thing peopel seem to want anyway19:02
clarkb#topic Priority Efforts19:03
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:03
clarkb#topic OpenDev19:03
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:03
clarkb#link https://review.opendev.org/789098 Update base job nodest to focal19:03
clarkbThis change was merged a bit early today bceause devstack went ahead and made the swap on their side and things started to fail19:03
clarkbwe have noticed at least one bit of fallout where our gerrit image builds were failing due to a lack of a `python` executable19:04
clarkbkeep your eyes open for failures that could be related to those changes where nodeset isn't fixed by a job19:04
clarkbfungi: ^ anything else to say about that?19:04
clarkbfungi may not have made it to this meeting yet after all the previous meetings (so many meetings today)19:05
funginah, minimal disruption so far19:05
ianwi just self-approved https://review.opendev.org/c/zuul/nodepool/+/790004 which is a trivial ffi bindep update after it was mentioned this was now borken19:05
ianwbroken even19:05
fungii ended up doing the nodeset change earlier in the day than expected, because devstack merged a change to stop working on bionic19:06
clarkbya I expect that is the sort of thing we'll be looking at addressing over the next little bit19:06
clarkbOn the gerrit account side of things I haven't made any new progress since we last spoke. Been distracted by other things. I'm hoping that maybe next week I can do another pass of cleanups though if others are able to also double check the list I stashed on review19:07
clarkb#topic General Topics19:07
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:07
clarkb#topic Server Upgrades19:07
*** openstack changes topic to "Server Upgrades (Meeting topic: infra)"19:07
clarkbThe entire Zuul + nodepool + zk cluster has now been upgraded19:08
clarkbthank you to everyone that helped with that.19:08
clarkbThe next thing on my todo list for this is mailman19:08
clarkb#link https://review.opendev.org/c/opendev/system-config/+/789622 Mailman ansiblification19:08
clarkbIf others are ok with landing that tomorrow I think I would like to give that a go19:08
fungiwfm19:09
ianw++19:09
fungii'll be around most of the day19:09
clarkbprobably put both list servers in the emergency file, land the change, remove lists.kata from emergency, manually run there, then if that looks happy do the same for lists.o.o19:09
clarkbcool sounds like a plan then19:09
clarkbianw: for review02 what do we need to do next to keep things moving on that system?19:09
ianwi need to get back to the database setup which you've commented on19:10
ianwi've been a little bit worried about frickler's ongoing issues with ipv6 to opendev.org19:11
clarkbianw: if that is related to the issues that rdo saw I think mnaser indicated there were fixups for that?19:11
clarkbbut maybe there are multiple issues?19:11
clarkbI agree though that it would be good to not have to remove aaaa records19:11
fungiit has to do with how his routes are being announced into ebgp19:11
clarkb(which is probably what we would be left with if problems persist or get worse)19:12
fungis/his/vexxhost's/19:12
ianwyeah, i haven't heard a clear "that is fixed" but i also might not have been listening in the right place :)19:12
clarkbianw: maybe we can have frickler double check and then bring it up again in #vexxhost if necessary19:12
clarkbanything else on the subject of upgrades?19:13
fungithe v6 allocation for vexxhost is subnetted so those subnets can be announced out of different locations, but the allocation is from a range which the rir indicates should not be globally subnetted, so some providers are filtering those prefixes19:13
fungii don't see that gettnig fixed unless providers relax the routes they're willing to receive or vexxhost starts announcing aggregates19:14
clarkbfungi: I see, vexxhost would need additional allocations for additional locatiosn or to route internally ?19:15
clarkbso that a single location can advertise the entire allocation then route behind that19:15
fungiclarkb: not even to route internally, but they'd need to rely on the backbone to still carry the longer prefixes and reroute packets accordingly19:16
clarkbgotcha19:16
fungiit's really the smaller isps who seem to be filtering the tables in that way, so it would in theory "just work"19:17
clarkbmaybe when frickler is around (so early morning my time) we can have a discussion including frickler and the impact of that problem and whether or not we want to proceed with a new review server in vexxhost using ipv6? our other options are no ipv6 or deployed elsewhere19:17
clarkbI'll see if I can facilitate that19:17
clarkbits already an issue for opendev.org I guess19:17
ianwyeah, this is rather hard to explain to someone who turns up saying "i can't talk to review.opendev.org" :)19:17
clarkb#topic Refreshing non LE certs19:18
ianwthat's true, i don't think we have too many people reporting issues on opendev.org19:18
*** openstack changes topic to "Refreshing non LE certs (Meeting topic: infra)"19:18
clarkboh sorry I was thinking we could move on, should I undo?19:18
ianwno19:18
clarkbAlright we have a smallish number of non LE certs that are about to expire in ~3 weeks.19:19
clarkbthey are for ask, ethercalc, wiki, translate, storyboard, openstackid and openstackid-dev19:19
clarkbwe've already deprecated ask and made it read only. I think we can probably just let that one die on the vine.19:20
fungimore like rot on the ground ;)19:20
clarkbI want to say there was some discussion about people using wayback machine to access old Q&A there. Are we happy with that plan and if so do we need to write it down somewhere?19:20
ianwwe could redirect it to a static page19:20
clarkbianw: and that page could point to wayback machine?19:20
fungiredirect it to the lists.openstack.org page for the openstack-discuss ml19:21
ianwyeah, basically the banner at the top19:21
fungiahh, or that19:21
clarkbthat seems like a reasonable idea. We would host that on static and use typical LE setup for that then?19:21
ianwi think so; i can take that on, it should be a quick one19:21
clarkbianw: thank you19:21
clarkbfor openstackid and openstackid-dev I'm meeting with the foundation web admins after this meeting to discuss how we want to do hosting for those services going forweard19:22
clarkbwe're in a weird spot where we can't actually redeploy it as is without their involvement today. Want to figure out if having it hosted on opendev/openstack infra is still valuable or if it makes sense to have them take it on more fully19:22
clarkbThat leaves us with ethercalc, wiki, translate,  and storyboard19:23
clarkbThat number is small enough that I can go buy 4 new annual certs to keep us limping along while we continue to improve the config management for them19:23
fungiwiki will be a manual process on the server for now, the others can be distributed via puppet i guess19:23
fungifrom hiera19:23
clarkbyup19:23
clarkbdoes anyone feel strongly against that? its like $32 which isn't a major concern on my end19:24
ianwi think we could get everything but wiki on LE if we want19:24
clarkbianw: within the ~25 days we've got?19:24
clarkbif so then I'd be hapyp to help do that instead19:25
fungioh, like have ansible install the certs but leave puppet pointing apache at the same path?19:25
ianwyeah, basically install the certs and then comment out the puppet bits looking to install certs19:25
clarkbya we have done it for a few services before, its not terrible, just takes time to get everything set up issuing the certs then update the vhost templates19:25
clarkbya I guess we should give that a go first. I can probably give that a go next week19:26
clarkbfeel free to look at doing it sooner if you want :)19:26
ianwyeah i can have a look.  if we hit issues, i guess buying new certs isn't a problem19:26
clarkbcool sounds like a plan, thanks19:26
fungiawesome19:27
clarkb#topic Too small swap devices19:27
*** openstack changes topic to "Too small swap devices (Meeting topic: infra)"19:27
clarkbAt this point this is mostly a heads up that we had some problems with make_swap.sh that resulted in a small number of servers having 7MB swap devices19:27
clarkbWe have since corrected all of the servers that had this problem19:27
clarkbWhen I did my audit to check for them I discovered that a non zero set of servers have no swap at all (different problem than the one we fixed)19:28
clarkbConsidering all of those servers have been running without interruption since without swap I don't think it is a high priority to change them. But if we did want to we could easily add swapfiles to them19:28
ianwhrm, what was that problem19:29
ianwi'm guessing something to do with mounted /opt19:29
clarkbya I'm not sure19:29
clarkb#topic Remove registration requirement for IRC channels19:30
*** openstack changes topic to "Remove registration requirement for IRC channels (Meeting topic: infra)"19:30
clarkbI pushed up a change to do this19:30
clarkb#link https://review.opendev.org/c/openstack/project-config/+/791818 Remove channel forwarding and +r requirement19:30
clarkbbut then as if on cue we starte getting spam in the unregistered channle again19:30
clarkb"Non Terrestrial Or Terrestrial Beings which can help me with Trans Universal Transportation (Please PM Me)099"19:31
clarkbI think I'll WIP the change for now and see if that persists19:31
clarkbif that ends up stopping maybe try it next week otherwise probably best to keep it as is19:32
ianwi haven't really noticed spam in too many of the other channels i'm in19:32
fungii'm surprised that stranded alien intelligence can't work out how to register an account on freenode19:33
clarkbthat is a good sign. I'll pick this up again next week when we have a bit more data on the latest spam19:33
fungithen again, i guess they ended up stranded for a reason19:33
clarkbindeed19:33
clarkb#topic Toggle CI button is no longer on Gerrit19:34
*** openstack changes topic to "Toggle CI button is no longer on Gerrit (Meeting topic: infra)"19:34
clarkbrosmaita this is your topic19:34
rosmaitathanks, i saw your response in the agenda19:34
rosmaitalooks like we have the Full Name correct19:34
rosmaitabut what is the tag that the CIs need to set on their comments?19:34
clarkbfor those who haven't read the agenda: rosmaita and the cinder prject are wondering how users can better manager CI comments on gerrit changes and what third party ci systems can do to be filterable19:35
rosmaitayeah, thanks for summarizing19:35
clarkbNewer gerrit has a "Only Comments" toggle which becomes "Show All comments" in even newer gerrit19:35
rosmaitahere's an example: https://review.opendev.org/c/openstack/cinder/+/790796/19:35
ianwwe had a bit of discussion on this @ http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2021-05-17.log.html#t2021-05-17T19:34:3119:35
clarkbrosmaita: autogenerated:yourcisystemhere is the tag convention that seems to be used19:36
clarkbrosmaita: zuul does this for you automatically if you set it up to talk to gerrit via http(s)19:36
rosmaitaoh, i seen the tag is 'autogenerated'19:37
ianwyeah, i would say that those CI's that still show up with "only comments" flicked on are not setting tags19:37
rosmaitai thought you meant zuul autogenerated a tag19:37
ianwthat makes them look like a human comment to the gerrit display logic19:37
clarkbright19:37
ianwthe summary plugin has stuff in it to regex match comments that don't have a tag19:38
ianwone option *might* be to disable that -- only show in the summary results from comments with a tag19:38
ianwcarrot and stick -- if you want to be in the summary, your comment must have a tag19:38
clarkbianw: not a bad idea19:39
fungihowever it would break looking at old results19:39
clarkbmay also reduce confusion over why some bits work and others dont19:39
clarkbfungi: they would still be in the comments though, but ya19:39
fungilike, comments from zuul 2 years ago don't have any tagging19:39
fungi(even ours)19:39
rosmaitabut our 3rd party CIs *are* showing up in in the Zuul Summary, so looks like you dont' need a tag for that19:39
clarkbrosmaita: yes that is what ianw is saying19:39
ianw#link https://gerrit.googlesource.com/plugins/zuul-results-summary/+/refs/heads/main/zuul-results-summary/zuul-results-summary.js#28419:40
clarkbrosmaita: we could update the summary to enforce the tag which may reduce confusion and also provide a carrot for people to set the tag19:40
ianwbasically get rid of "_match_message_via_regex" there19:40
clarkbhttps://gerrit.googlesource.com/plugins/zuul-results-summary/+/refs/heads/main/zuul-results-summary/zuul-results-summary.js#210 only matches zuul or zuul like taggers19:40
clarkbmaybe that is good enoguh. the format of the comment that is parsed is assumed to be zuul's format too iirc19:41
ianwfungi: it's horrible, but we could conceivably have a config option which is a change number <= to look for comments via regex19:42
clarkbrosmaita: are you using zuul or some other ci system?19:44
rosmaitamostly other19:44
rosmaitawe are trying to get people to move to zuul v319:45
fungiv4 now. soon v5. maybe better to just say "modern"19:45
rosmaitaok19:45
clarkbya probably the biggest hurdle is that it relies on others to do the right thing. but we're really trying to avoid adding in unnecessary tech debt like we had with the old tools19:45
clarkbinstead we're relying on existing features and writing plugins where necessary19:46
fungiv2->v3 was a big jump because the job runner changed, but now zuul increments the major version component any time there's a non-backward-compatible change to deployment19:46
clarkbin this particular case I think we should give relying on the built in feature an honest effort19:46
ianwyeah, i think after we pulled it apart, tagged comments as implemented by gerrit are what we want19:46
ianwso if there's things we can do to help encourage CI systems to leave such comments, i think we're all ears19:47
fungisad that the checks api hit a wall19:47
clarkbrosmaita: https://review.opendev.org/Documentation/cmd-review.html has a --tag flag, that is effectively what zuul does though it doesnt' do it via ssh reviews only http19:47
clarkbrosmaita: you should be able to instruct your third party CI systems to set autogenerated:zuul if they are reporting zuul format comments of autogenerated:somethingelse if not using the zuul format19:47
rosmaitathanks for that link, i can get the news out19:48
rosmaitahow would you do this for http reviews?19:49
rosmaitai dont' know how most of the CIs connect to gerrit, tbh, but i think a lot of them use ssh19:49
clarkbI was trying to find similar docs for the rest api but not finding them19:49
clarkbthe rest api definitely supports it though as that is what zuul uses19:50
rosmaitaok, we can do some digging19:50
clarkbhttps://review.opendev.org/Documentation/rest-api-changes.html#set-review maybe and then https://review.opendev.org/Documentation/rest-api-changes.html#review-input that objects tag flag19:50
clarkblets move on we have one more subject to cover before we run out of time19:51
clarkb#topic Scheduling project renames19:51
*** openstack changes topic to "Scheduling project renames (Meeting topic: infra)"19:51
ianwhttps://gerrit-review.googlesource.com/Documentation/rest-api-changes.html#set-review is the api call19:51
ianwanyway, it's just a "tag" in the json19:51
clarkbianw: cool that confirms what I linked19:51
clarkbwe have at least one project rename request19:51
rosmaitaianw: clarkb: thanks19:51
clarkbWhen fungi and I were testing project renames it seemed to be as simple as stop gerrit, move repo to new name location, start gerrit, trigger online reindex19:52
clarkbThis didn't update individual user account project watches but that is a lot more work and potentailly runs into the same problems we have with user email conflict cleanup19:52
fungiyeah, i think we assume we lose watches and such19:52
clarkbI think I'm ok without updating project watches. Users can be instructed to update them themselves19:52
clarkbThe other thing we need to do is update our project rename playbook(s)19:53
clarkbI'm fairly certain they still try to modify sql things19:53
clarkbI'm thinking that a good next step here is to update our playbook(s) and exercise them in our gerrit functional testing. Then when we are happy with those results we can schedule a day for the gerrit downtime19:53
fungii can work on trimming that out19:53
clarkbfungi: that would be great and you should be able to do the testing ^ I describe too since the gerrit functional testing is fairly robust as this point19:54
fungibut yeah, adding testing for renames is a bigger task19:54
fungii'll see if i can also find time for that19:54
clarkbya its a bigger task but I don't think its much bigger. I could be wrong though19:54
clarkbalright, we can regroup and try to nail down an actual time for the rename once we've at least gotten an updated playbook19:54
clarkb#topic Open Discussion19:55
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:55
clarkbWe have 5 minutes for any other discussions that may have been skipped or need to be brought up again19:55
clarkbbut then I have another meeting to run to19:55
fungiit would probably be good to talk about https://review.opendev.org/785769 but that's likely to be a longer discussion and not urgent, i can add it to next week's agenda19:56
clarkbfungi: ++19:57
fungisimilarly https://review.opendev.org/77430019:57
clarkbya those would both be good discussions to have but probably also should just land them once we have ensured we're all aware of the delta19:58
fungior at least have reached consensus19:59
clarkb++19:59
clarkband we are at time. Thank you everyone19:59
clarkbwe'll see you here next week20:00
clarkb#endmeeting20:00
*** openstack changes topic to "Incident management and meetings for the OpenDev sysadmins; normal discussions are in #opendev"20:00
openstackMeeting ended Tue May 18 20:00:05 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-05-18-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-05-18-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-05-18-19.01.log.html20:00
fungithanks!20:01
*** rosmaita has left #opendev-meeting20:18
*** rosmaita has joined #opendev-meeting20:30
*** rosmaita has left #opendev-meeting20:30
*** sboyron has quit IRC21:07
*** hamalq has quit IRC23:37

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