Tuesday, 2021-11-16

clarkbMeeting time19:00
fungiahoy!19:01
clarkb#startmeeting infra19:01
opendevmeetMeeting started Tue Nov 16 19:01:28 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
ianwo/19:01
clarkb#link http://lists.opendev.org/pipermail/service-discuss/2021-November/000296.html Our Agenda19:02
fricklero/19:02
clarkb#topic Announcements19:03
clarkbGerrit User Summit is happening virtually December 2&319:03
fungialso openinfra live keynotes tomorrow and thursday19:04
clarkbalso virtual19:04
fungi15:00-17:00 utc both days, though may run longer19:04
fungibasically this year's replacement for the openinfra summit19:05
clarkbAnyway thought I would throw that out there as I've always missed previous gerrit user summits as they don't seem toget as much advertisement19:05
clarkband others may be interested in attending19:05
clarkbAlso next week is a US holiday week. I wasn't planning to take the whole week off just the end of the week but then school last minute cancelled for the whole week19:06
fungii expect to be around most of the week, in case anything comes up19:06
clarkbThis means I'm going to try and avoid being around during the whole week to spend time with family. I'm inclined to cancel our team meeting next week as a result but happy for others to run a meeting if they like19:06
fungithough will likely be busy thursday, maybe friday19:06
ianwi'd do it but given low attendence doesn't seem worth it19:08
ianwseems better to force some time  away :)19:08
clarkbwfm, we'll cancel next week then. See you all here in 2 weeks19:08
clarkb#topic Actions from last meeting19:08
fungiyeah, i'm fine cancelling19:08
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2021/infra.2021-11-09-19.01.txt minutes from last meeting19:08
clarkbWe don't seem to have recorded any specific actions19:09
clarkb#topic Topics19:09
clarkb#topic Improving OpenDev's CD Throughput19:09
clarkbI've got new motivation to pick this up again and realyl do hope to do so this week (I was sick last week otherwise I'd like to think I would've looekd at these)19:09
clarkbYesterday we landed a change to our base inventory stuff which caused all the jobs to run and it took a couple of hours19:10
clarkbRight now we are in good shape when we run jobs in a targetted manner but when we do those base updates it is painful waiting for everything to complete.19:10
clarkbAnyway thats the motivation. I really do hope to look at the changes and figure out why CI isn't super happy with the later changes19:11
clarkb#topic Gerrit Account Cleanups19:11
clarkbI still haven't heard from the most recent user I updated so assume that was fine. I haven't done the mass emails yet but need to explicitly block off time for that. Maybe week after next and just work through those19:12
clarkbIt is too easy to deprioritize this effort, but it is very close to being done so I should just get it done19:12
clarkb#topic Zuul Multi Scheduler19:14
clarkbZuul is still running with two schedulers and seems significantly more stable19:14
clarkbzuul01 and zuul02 are the two hosts and zuul02 is the primary and runs zuul-web19:14
fungibeen running that way since the weekend, and we even had a zero-downtime rolling restart of the schedulers19:15
clarkbzuul-web has been updated to talk to zk directly which means you should always get a consistent view from the status pages now19:15
clarkbThis is feeling like it is stabilising now, and maybe we'll get another zuul release in the near future (though there are a few inflight fixes that we will ideally restart opendev on to sanity check first, good news is those can hopefully be done without downtime now)19:16
clarkbAnyway just an update on that as its been a thing lately. Hopefully less and less a thing as we stabilize it further19:17
clarkb#topic User management on our systems19:18
clarkbThank you fungi and ianw and frickler and others for the reviews on this. We've landed the first changes in starting to clean this up19:18
clarkbunnecessary users should now be removed and we've adjusted the uid and gid range on our systems (though any uids/gids outside of that range haven't been moved)19:19
clarkb#link https://review.opendev.org/c/opendev/system-config/+/816769/ Give gerritbot and matrix-gerritbot a shared user19:19
clarkbis the next step in that process I think19:19
clarkbplease review that one carefully as I suspect this will act as a sort of template as we go through and update other services to do similar19:19
clarkbseparately I think that if we want to work on shifting mariadb uids over to match the services the db is running for I think we can probably start that work in parallel though I expect it to be fiddly19:21
ianwthanks, sorry reviewing of these got a bit distracted, but will do19:22
clarkbthanks.19:22
clarkbre mariadb I suspect that etherpad would be a good first candidate19:22
clarkbsince it is fairly self contained and doesn't ahve a lot of moving parts like gitea or gerrit19:22
clarkb#topic Caching of openstack/openstack on our DIB image builds19:23
fungiwith mariadb, the idea would be to have a specific mariadb user, or use the same user as the etherpad service runs under?19:23
clarkb#undo19:23
opendevmeetRemoving item from minutes: #topic Caching of openstack/openstack on our DIB image builds19:23
fungisorry, i'm typing slowly today19:23
clarkbfungi: I think use the same user as the etherpad service. Since all of the services running etherpad have rw access to the db there isn't much to gain from separateing them19:23
clarkbif we ran a central db and shared it with many services I would say they should be separate but in this case we run a mariadb separately for each service19:24
clarkband this helps simplify things. THough we could split users if there was a good reason to19:24
fungiyeah, makes sense as long as multiple services don't share a common db server19:24
fungithanks, that answers my question19:25
ianwmariadb already runs as 999 though right?19:25
clarkbianw: yes19:26
fungiwhich unfortunately conflicts with the range of accounts that might get taken by distro packages of things19:26
clarkbright the concern is we don't want the overlap with system usage19:26
clarkbwe should shift it to our uses and having it run as the same user as the service seems fine since the db is rw and separate for each service19:26
fungihence our desire to carve up separate ranges19:26
ianw++19:27
clarkb#topic Caching of openstack/openstack on our DIB image builds19:29
clarkbI wasn't sure if this would be fixed or not by the time of the meeting so I had this on the agenda to discuss simply removing openstack/openstack from caching19:29
clarkbBut ianw was able to track this down to a weird git interaction (I kinda think it might be a bug?) between using the git dir option and how submodules are checked19:30
clarkbthankfully there is the -C option as an alternative to the git dir option and that should fix things. The dib change to switch to -C has landed but I think we need a release and new nodepool iamges to take advantage of it19:30
ianwit might be a bug that git made it so confusing as to what was going on, but it does appear to be mostly our fault19:30
ianwat least git is written in C and builds with make, so it wasn't a multi-day setup to instrument it and figure out what it thought it was doing :)19:32
clarkbya I mean it seems liek git should be resilient to people passing flags like that19:32
clarkbeither by saying "I can't function in this situation" explicitly or by figuring out a way to function19:33
ianwi'll probably do a dib point release and update nodepool, because it's very racy getting images built atm19:33
clarkbsounds good, and thank you for looking into that. An upside to using containers this way I guess19:34
ianwi think openstack/openstack project is fine, but it's still not clear to me how it's actually setup19:34
clarkbianw: gerrit has a magic flag where it will auto update submodules in a repo if it hosts the submodule repos too19:35
clarkbianw: so basically if you add a submodule to that repo and it is on our gerrit gerrit will make commits to it automatically as we merge chagnes to hose repos19:35
clarkb(its an explicit config option on the repo that has to be set) The idea when it was set up was that it could be used to track a log of the order things land in19:35
clarkbbut it never really got used and has become very bit rotten (it lacks repos iirc)19:35
ianwahh, yeah that's what i was wondering, what maintains it19:36
ianwit looks like there's a "generate-gitmodules.py"19:38
ianwbut, it doesn't look like this auto-runs or auto-proposes?19:38
clarkbI think it is in gerrit itself19:39
clarkbianw: https://gerrit-review.googlesource.com/Documentation/user-submodules.html19:40
fungiin theory the openstack tc is supposed to be maintaining the list of included submodules in it19:41
ianw$ git review19:42
ianwssh://iwienand@review.opendev.org:29418/openstack/openstack.git did not work. Description: fatal: Upload denied for project 'openstack/openstack'19:42
fungithere might be some automation in openstack/governance, like the script they run which creates github projects for mirroring into19:42
ianwinteresting.  it looks like AJaeger used to mostly run the script and update .gitmodules in there19:42
fungianyway, worth checking with the opemstack tc to see if anyone's maintaining it19:43
ianw"2. configure the submodule to allow having a superproject subscribed" was the step i was unclear on19:43
ianwsubmodule.enableSuperProjectSubscriptions seems like it defaults to true, so that explains that bit19:44
ianwi guess we have done something in All-Projects for this repo?19:45
clarkbthat could be19:45
clarkbI wasn't invovled in the setup so don't recall how it was done19:46
clarkb#topic Open Discussion19:47
ianwfungi: i think the answer empirically is "no" https://opendev.org/openstack/openstack/commits/branch/master/.gitmodules19:47
clarkbFigured I'd open it up to any other discussion19:47
ianwclarkb: https://review.opendev.org/c/opendev/system-config/+/817301 was a quick one from your comment on doing a mark/unmark/mark cycle on the gerrit testing19:49
clarkbah yup +219:50
ianwi had been under the impression this repo was automatically keeping itself up to date19:50
ianwgiven that it isn't, i guess i'll post to the list and propose retiring it19:50
fungione of the main reasons they've wanted it kept around is the "cncf landscape"19:51
fungifor a project to be included on the landscape, it must be represented by one (and only one) repo on github19:51
fungiso the github mirror of the openstack/openstack superrepo is how the lf/cncf measures the level of "activity" for the openstack project19:52
ianwinteresting19:52
ianwsince i couldn't push an update to the .gitmodules, i'm guessing it's locked down to some group19:53
ianwthe first thing i'm thinking is that the proposal bot should run the project update19:53
fungipush = group Release Managers19:54
fungiexclusiveGroupPermissions = Push19:54
fungithat's in the [access "refs/for/refs/*"] section of gerrit/acls/openstack/openstack.config19:54
ianwor, could we do something more like have zuul run it in a periodic job?19:55
ianwbut where would the zuul job get permissions to propose/push the change?19:55
fungicould use the same account which pushes tags for openstack19:56
fungiit's a member of release managers19:56
ianwseems reasonable19:57
clarkbyou'd still need someone to review them? or are you saying just push directly?19:58
ianwif it ran and just +2 +W'd it's change it would seem to keep it in sync19:58
ianwyeah, i'm thinking that reality of people reviewing is low19:59
fungiwe could adjust the acl to give create = group Release Managers in [access "refs/heads/*"] and bypass reviewing, i suppose19:59
ianwsince it's based on the YAML file that is reviewed it seems low risk19:59
ianwis it running any testing from project-config?20:01
fungii don't think so20:01
ianwhttps://review.opendev.org/c/openstack/openstack/+/741207 ... just noops20:01
fungiwhich is another reason direct pushing to the branch might be more sensible20:01
ianwok, well i'll put it on the todo.  could be an interesting exercise in zuul jobbing20:02
fungiseems like we've probably finished meeting. thanks clarkb20:10
fungi#endmeeting20:10
opendevmeetMeeting ended Tue Nov 16 20:10:36 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:10
opendevmeetMinutes:        https://meetings.opendev.org/meetings/infra/2021/infra.2021-11-16-19.01.html20:10
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/infra/2021/infra.2021-11-16-19.01.txt20:10
opendevmeetLog:            https://meetings.opendev.org/meetings/infra/2021/infra.2021-11-16-19.01.log.html20:10
clarkboh sorry I spaced out on the logging thing20:17
clarkbFor some reason I thought I had ended the meeting but nope. Thank you for doing that20:17
fungino worries, i figured you had already switched context20:17

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