Tuesday, 2021-03-16

*** SotK has quit IRC01:12
*** SotK has joined #opendev-meeting01:13
*** hamalq has quit IRC01:23
*** zbr has quit IRC06:13
*** zbr has joined #opendev-meeting06:16
*** sboyron has joined #opendev-meeting06:47
*** hashar has joined #opendev-meeting08:05
*** yoctozepto has quit IRC13:53
*** kopecmartin has joined #opendev-meeting16:44
*** hamalq has joined #opendev-meeting16:48
*** hashar has quit IRC16:53
clarkbanyone else here for the meeting?19:00
clarkbwe will get started momentarily19:00
fungias the kool-aid man always says, "oh yeah"19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue Mar 16 19:01:04 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
clarkbfungi: just be careful around brick walls19:01
fungioww19:01
clarkb#link http://lists.opendev.org/pipermail/service-discuss/2021-March/000196.html Our Agenda19:01
ianwo/19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbI will be out next week. ianw has offered to chair the meeting on the 23rd. Thank you ianw!19:01
clarkbAlso the DST change has happend in North America but the EU, Australia, and I'm sure others are still few weeks away so timezones are weird right now. Double chcek your meeting calendar :)19:02
clarkb#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-03-09-19.01.txt minutes from last meeting19:02
clarkbI didn't readd corvus' unfork jitsi action, but I did push a new patchset that is passing testing now. Maybe someone other than corvus or myself can review taht change and we can get it in?19:03
clarkb#link https://review.opendev.org/c/opendev/system-config/+/778308 unfork jitsi meet19:03
clarkbfungi: ^ looks like ianw already reviewed it, maybe you have time for that today?19:03
fungioh, yup19:04
fungiafter dinnert19:04
clarkbthanks19:04
clarkb#topic Priority Efforts19:04
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:04
fungiwhich is like dinner and tea?19:04
clarkb#topic OpenDev19:04
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:04
clarkbmmm tea19:04
clarkbI have account inconsistency updates19:05
clarkbsince we last had our meetings I managed to correct all of the preferred email address don't have external id consistency issues.19:05
clarkbThat means the only issues we have now are with conflicts in external ids19:05
clarkbI also corrected about 100 of those or so and the total number of conflicts is down to 54519:05
clarkbI've since started looking at categorizing the next sets of accounts so that we can decide if we can safely clean more up and I think I have identified a number of accounts where this appears safe.19:06
clarkbthose notes can be found at review:~clarkb/gerrit_user_cleanups/notes.20210315 and if other infra-root can take a look athat would be great19:06
clarkbThey are tiered from what I expect are super safe cleanups to less safe cleanups but all seems fairly safe. But feedback on where the line seems to be for contacting people first would be appreciated19:07
clarkbalso fungi and I found mroe correlation of manage-projects to gitea sadness which prompted https://review.opendev.org/c/opendev/system-config/+/78090419:08
clarkbessentially it undoes our always update descriptions change and offers some further improvement suggestions in the commit message19:09
clarkbit does pass testing now so I think we can start reviewing that19:09
clarkbanything else opendev related or should we move on?19:09
clarkb#topic Update Config Management19:11
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:11
clarkbianw has change(s) up to ansible krb5 servers19:11
clarkbI've reviewed the main change and it lgtm19:11
clarkbianw: do you need more reviews and/or are there newer changes to look at?19:11
ianwwell it *should* be a no-op for production19:12
ianwbut clearly one i'll want to babysit closely19:12
ianwso if noboy has particular interest your review probably suffices19:13
fungiwhat's the review topic? i think i reviewed some of those but not sure if it was the most recent revisions19:13
fungialso possible i forgot to vote on them19:13
ianw#link https://review.opendev.org/q/topic:%22kerberos-server%22+(status:open%20OR%20status:merged)19:14
clarkblooks like there are a couple I need to review, I'll look at those after lunch19:15
clarkbare there any other config management updates to call out?19:15
ianwi have a little cleanup of sslcert checks in19:16
ianw#link https://review.opendev.org/c/opendev/system-config/+/78014019:16
clarkb#topic General Topics19:17
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:17
clarkb#topic Picking up steam on server upgrades19:17
*** openstack changes topic to "Picking up steam on server upgrades (Meeting topic: infra)"19:17
clarkbI hit a little issue with nodepool launcher replacements that required an update to nodepool itself to address (basically its unique launcher name registration awsn't unique enough)19:18
clarkbThe current opendev hourly deploy is expected to configure nl01.opendev.org. Hoping that transition will be completed real soon now19:19
clarkbit is a bit more of a dance as we need to coordinate config changes between the servers as we do it. Though I expect we can do 02-04 in one go if 01 looks happy19:19
clarkb#topic Deploy new Refstack server19:20
*** openstack changes topic to "Deploy new Refstack server (Meeting topic: infra)"19:20
clarkbI suspect that this may be the last time I need to bring this topic up? DNS has been updated to point at the new server and we corrected a couple of issues19:20
clarkbianw: kopecmartin: can we call this done? or do we want to keep it up for things like db backups etc19:20
ianwdb backups are done, i fixed that yesterday19:21
ianwif we are happy, we can remove the puppet19:21
clarkbexcellent19:21
ianw#link https://review.opendev.org/c/opendev/system-config/+/78013819:21
clarkbseems like we may have reached that point19:21
fungihave we ripped out the old puppetry and retired the module repo?19:21
clarkbthank you to ianw and kopecmartin for pushing this over the finish line19:21
ianwi can leave a todo to cleanpu the old server/db in a month or so just for saftely19:22
clarkbfungi: thats the cahgne above19:22
ianwsafety even19:22
fungiyup, got it19:22
ianwi haven't retired the puppet module19:22
clarkbianw: sounds good19:22
ianwthere's probably several we could do that to now19:22
kopecmartini think it's done, thanks for the help with that19:22
clarkb#topic review server upgrade19:24
*** openstack changes topic to "review server upgrade (Meeting topic: infra)"19:24
clarkb#link https://review.opendev.org/c/opendev/infra-specs/+/78047819:24
clarkbafter our discussion last week ianw put together a spec document to help outline the considerations to make when replacing this server19:24
ianwi don't want to tie us up in paperwork over this :)19:24
fungiyeah, i think the spec is pretty complete out of the gate, though seemed like you wanted mnaser to add some info19:25
clarkbI think the idea was to use it as a way for mnaser to double check he was comfortable as a hosting option19:25
clarkbsince it outlines the considerations we should make19:25
ianwyeah, i feel like we are tending towards vexxhost (if they'll have us :)19:26
mnasery'all are welcome to use it19:27
mnaserhappy to coordinate all this19:27
clarkbmnaser: do you think you could look over https://review.opendev.org/c/opendev/infra-specs/+/780478 and double check there aren't any major gotchas or concerns that jump out to you in that?19:28
clarkband if not we'll go ahead and start doing some testing of ah ost in vexxhost?19:29
mnaserid suggest backups to be in another region19:29
clarkbmnaser: you mean we should move our current backups or that the gerrit host be bakced up to a different region?19:29
mnaseri think you'll find better hardware in the montreal region19:30
mnaserand im not sure wher ethe backups are rifght now19:30
ianwwe have a backup server in sjc-119:30
clarkbI think ianw said they are in sjc1 so we should be good if we use montreal for the review host19:30
ianwwe don't currently have anything in mtl19:30
mnaserah ok perfect, the rest seems fine to me, obviously suggest using v3 flavors and boot from volume19:31
clarkbgreat, thank you for checking. I guess we can go ahead and spin something up and do comparison of performance?19:31
mnaseryep, go for it, and if you see anything odd, let me know19:32
fungimnaser: will we still need to coordinate ipv6 reverse dns, or you have an interface to set that now?19:32
mnaserfungi: no we'll have to coordinate for that19:32
clarkbipv4 too iirc19:32
mnaseryeah19:32
mnaserbut can easily be done19:32
ianwi haven't checked but do we have some quota there for the /home/gerrit2 volume on something fast?19:32
ianwor maybe the question is more, how should i best create that volume19:33
fungione other thing we probably should have added to the spec, the server *does* directly send e-mail via smtp19:33
clarkbfungi: ++19:33
mnaseryou should be able to create a volume with volume_type=ssd19:33
fungi(all those gerrit watched change/projects notifications to users)19:33
mnaserwe don't block port 25, so that shouldn't stop you from having any problems out of the bat other than rdns19:33
fungigreat, thanks mnaser!19:33
ianwok, i can take an action item to start up a server and see how we go19:34
ianwi have a few related changes out19:34
ianw#link https://review.opendev.org/q/topic:%22review-update-2021%22+(status:open%20OR%20status:merged)19:34
ianwremoving review-dev from testing is the big one19:34
mnaserbtw, you can ping me or guilhermesp in #vexxhost19:34
mnasershould you need anything19:35
clarkbgood to know, thanks19:35
ianwthanks, joined :)19:35
clarkbanything else on this topic?19:35
ianwso i'll look at at ~96gb instance right?19:35
ianwi.e. we want to go a bit bigger19:36
clarkb++ particularly since we want to move the db19:36
clarkbbut that should also give the kernel space for caches again19:36
clarkbI expect that will make for a much more responsive experience19:37
mnaseri think we have v3-standard-16 which is 16C/64G memory or v3-standard-32 which is 32C/128G memory19:37
clarkbmnaser: is it better to just use the bigger flavor or figure out a 24C/96GB flavor?19:37
fungi16C/64G is very close to what we have now19:37
mnaseri think it's much easier for you to leap to 32C/128G than me getting 24C/96G up and going19:37
clarkbok that works for me :)19:37
mnaserdidn't think it would be an issue =)19:38
ianwhrm, it doesn't seem we have an openstackci tenant in mtl?19:38
fungialso with the provisioned port trick, we can always move to a smaller flavor later without an ip address change if desired19:38
clarkbianw: we should unless somethign changed19:38
clarkbianw: the actual region name is ca-ymq-1 or similar19:39
fungiyeah, mtl is the new name but same region19:39
mnaseryes, sorry for the gross name :)19:39
fungiwell, ymq is also a local airport ;)19:39
ianwoh!  ok, that makes sense19:39
ianwi thought we were talking about another region all together :)19:40
clarkbca == canada ymq == montreal airport19:40
mnaseri would kindly suggest looking at moving zuul over too not far after19:40
mnaserjust to drop the amount of ingress/egress traffic overall19:40
ianwso i see v3-standard-9619:41
clarkbmnaser: though that will shift the ingress/egress to zuul and may not necessarily be the dent you think it is19:41
clarkb(definitely something to consider though)19:41
ianwbut only v1-standard-12819:41
mnaserah yeah, cause zuul caches stuff mostly19:41
mnaseryeah you want to go for v3-standard-32 which is 32C/128G memory :)19:41
mnaser# = cpu count and not memory19:41
ianwok ... :)  i'm getting there it's early19:42
ianwalthough it's nice when the number of cores can be easily confused with the number of gigabytes of ram :)19:42
clarkbOk lets move on19:43
ianwi think i am going to call it review02.opendev.org (even though we never really had an 01)19:43
clarkbianw: wfm19:43
ianwyeah, move on, getting into the weeds :)19:43
clarkb#topic PTG Planning19:43
*** openstack changes topic to "PTG Planning (Meeting topic: infra)"19:43
fungithat'll make some of our dns gymnastics easier, yeah19:43
clarkbI've tried to spend a little time brainstorming what a PTG would look like for us19:43
clarkbI expect it would be really low key and not all that different than when we chat on IRC19:43
fungiwe could chat on irc like usual, and put up a commemorative "ptg" themed /topic?19:44
clarkbI'm leaning towards not trying to PTG time for us as a result, but am considering having a few office hours in case there are others who have testing/service/etc questions they want to bring up19:44
clarkbbut I'm not sure if others agree with me on that assessment19:44
clarkbIf you'd like to have voice/video time during the week of PTG I'll sign us up and work on a small agenda19:45
fungiabout the only thing which comes to mind is we could take it as an opportunity to try to arrange a sprint around something19:45
clarkbthat isn't a bad idea, and I hadn't considered that actually19:45
clarkbdo actual coding and reviews rather than primarily be discussion focused19:46
fungiwe do also have some new config-core reviewers. maybe it could be a good opportunity to help answer questions they have (that's more in-line with your office hours idea i guess)19:47
clarkbfungi: ++ that is the sort of thing I had in mind for office hours19:47
fungier, not actually new config-core reviewers yet, but volunteers who are helping config-core19:47
clarkbI think I'll go ahead and sign us up but note in the survey we intend the time to be office hours type and maybe we'll try sprinting if we can come up with a good topic19:48
clarkb#topic Open Discussion19:49
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:49
clarkbnl01.opendev.org got ansibled. It didn't auto start the launcher so I'm going to do that momentarily. I don't expect it to cause problems but we'll have two different launchers operating on the rax nodepool providers19:49
clarkbthe openstack.org launcher has non zero max server values, the opendev.org launcher has 0 max-server values so it should largely be idle19:50
clarkbthen we can land the change to flip the configs around, then we can retire nl01.openstack.org and clean things up19:50
fungiactually, i guess that last topic was a good reminder, gmann and amotoki have been taking a closer look at config changes, and they've been a big help19:50
clarkbplease let me know if you see nodepool weirdness today :)19:50
clarkbfungi: oh tahnks for the heads up. I guess they were part of the volunteer group too?19:51
fungiyep19:51
corvuszuul is running a crazy amount of new code; so keep an eye out for behavior changes19:52
corvusan area of particular interest (since it changed recently but rarely does) is git repo prep19:52
corvusgit repo state is frozen and consistent for all repos in a buildset now19:52
corvusor at least should be19:53
fungioh, neat, i didn't realize it wasn't before19:53
corvus(previously, the repo of the change under test (and any dependent changes) would be consistent for all builds in a buildset, but repos in required-projects could theoretically be different)19:53
fungisomething i need to brainstorm a bit, with the new gerrit api and acls having the ability for us to dole out branch deletion permissions now, it would be nice if we could scale the openstack release managers permissions down from global to just over the openstack namespace. gerrit does have the ability to do acl inheritance, but the inherited acl needs a "project" to contain it... would creating an19:53
fungiempty project for that be ugly, are there alternative ways to do that?19:53
corvusfungi: yeah, i mean, it *pretty much* was -- this is definitely an edge case19:54
corvusfungi: my understanding is "empty project" is the gerrit way19:54
clarkbfungi: ya I think creating the empty repo is the way to go19:54
fungiokay, i'll get to work proposing that19:54
fungithere are a few hundred pending branch deletions for eol openstack project branches, and i'd rather not wind up being the one to do them19:55
clarkb++19:55
fungibut this is a good opportunity to test out the new permissions model19:55
clarkbalright sounds like that may be it. Thank you everyone!19:57
clarkb#endmeeting19:57
fungithanks clarkb!19:57
*** openstack changes topic to "Incident management and meetings for the OpenDev sysadmins; normal discussions are in #opendev"19:57
openstackMeeting ended Tue Mar 16 19:57:51 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-03-16-19.01.html19:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-03-16-19.01.txt19:57
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-03-16-19.01.log.html19:57
*** yoctozepto has joined #opendev-meeting20:14
*** sboyron has quit IRC21:00
*** zbr has quit IRC22:37

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