Wednesday, 2023-10-25

pcheliHello, I'm setting up ThirdParty CI with jenkins and gerrit-trigger plugin. Generally, it works. However, results posting fails with Too many concurrent connections (96) - max. allowed: 96.09:01
pcheliCan anyone help with this?09:01
*** d34dh0r5- is now known as d34dh0r5312:20
stephenfinclarkb: fungi: We were discussing getting OSC/SDK back on Launchpad just now. Stop me if you've heard this all before, but it seems we have existing projects and dtroyer is sole admin for many of them. I've no idea how to get in touch with Dean nowadays so am considering reaching out to the Launchpad admins and asking them to move it to gtema or I14:25
stephenfinBefore I do, does that sound reasonable and have have you folks any experience interacting with the launchpad admins?14:25
fungistephenfin: if ~openstack-admins is the owner of any groups i can add myself to them as a temporary admin and then add/change the member lists14:26
fungibut reaching out to the people who do still have control over them is the best first step14:27
fungiwhich specific projects on lp are these?14:27
stephenfinFor OSC, it's this one https://launchpad.net/~python-openstackclient/+members#active14:27
stephenfinFor SDK, I think it's this one: https://launchpad.net/~python-osdk-team14:28
clarkbyes I would reach out to dean first. I'm sure we can find an email address14:28
clarkbcorvus is admin on that first one14:29
clarkbso could help with that one as well14:29
fungiboth those teams are owned by ~openstack-admins too, if necessary14:29
stephenfinthey are? how can you tell that?14:29
clarkbfungi: the second one isn't? its owned by 'jnoller'14:30
clarkbstephenfin: on the main page for the group it shows the owner14:30
stephenfinahh, so it does14:30
fungier, yeah ~python-openstackclient is the only one owned by ~openstack-admins14:30
* stephenfin was looking at /+members14:30
fungii must have pulled it up twice14:30
fungii agree the one with jnoller as the owner and only admin is going to be the tougher nut to crack14:31
fungisomeone will need to try to reach out14:31
stephenfinI can do that14:31
stephenfinfungi: For ~python-openstackclient, if we can skip reaching out to Dean would you be able to add gtema and I as admins and we can clean up the list?14:33
stephenfinassuming I understood you correctly14:33
fungistephenfin: yeah, in this case i can be pretty sure it's not in use for anything since the project was on storyboard for a while14:34
fungistephenfin: what are your lp usernames?14:35
stephenfingtema is gtema14:35
stephenfinmine is stephenfinucane14:35
fungistephenfin: done14:36
stephenfinthanks14:45
stephenfindone on my end also14:45
clarkbstephenfin: https://review.opendev.org/c/openstack/python-openstackclient/+/898129 is a low ish priority item on my plate. Thats driven by opendev trying to stop building older docker base images. I'm not sure when osc will switch python3.11 testing to voting but when it does it would be good to land this as well14:46
stephenfinfine by me14:47
stephenfinWe use openstack-python3-jobs, so I had assumed we'd have switched Python 3.11 to voting already tbh14:48
clarkboh you're waiting on the global switch14:48
stephenfinyup14:48
stephenfinDo we need the Bugs, Core and Drivers teams on Launchpad or can we remove them as sub teams? Ideally they should be deleted if so but I don't know if that's possible 14:53
stephenfinOh, you can do that from the homepage of the group also14:53
clarkbstephenfin: the different groups are used for different privileges iirc. Drivers have historically had all the permissions. Core less and bugs fewer14:54
clarkbYou can probably get away with drivers and core. Or maybe just a single group that does everything14:54
stephenfinAre those permissions configured via the web UI also? We probably also need to be added to the three projects if we are to keep them since it appears admin permissions/membership do not cascade down14:57
clarkbyes everything should be doable via the web ui14:57
clarkbsomeone like ttx may remmeber how all of this was structured14:58
clarkbstephenfin: https://bugs.launchpad.net/nova here you can see the nova bug team is listed as bug supervisor14:58
clarkbhere you see the driver and maintainers of nova are the noav drivers team https://launchpad.net/nova14:58
clarkbeach of those give certain permissions iirc. I don't know if nova has a core and if it does where that is set or what it does14:59
stephenfinPresumably not. https://launchpad.net/~nova-core is a 40414:59
fungiit used to be that "drivers" had the ability to set milestone targets, add series, approve blueprints, and similar release-related activity as well as configuring the project in lp. "bugs" was for when projects didn't want random users to be able to assign things or set priorities15:18
fungiand then the "coresec" teams are for vulnerability management per project15:19
opendevreviewCorey Bryant proposed openstack/openstack-zuul-jobs master: Update openstack-python3-charm-jobs py3 branches  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/89907815:30
fricklerconfig-core: ^^ and 720544 would be nice if you have a minute15:38
fungisure, looking15:38
fungifrickler: do you know if there's a change proposed to address that syntax error in osj?15:43
fricklerclarkb: what was your plan for the test in https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/866054 ? just merge it and watch things for a bit?15:43
fricklerfungi: did you get confused by the storpool result like I did a couple of times?15:44
fungid'oh, yep!15:44
fungisorry ;?15:44
fungi:/15:44
fungiyeah, our zuul just came back with a +115:45
fungistorpool seems to be running an old version of zuul15:45
fungiso doesn't support the newer branches syntax15:45
clarkbfrickler: I probably had a devstack rp tempest chagne depending on that let me look15:46
clarkbfrickler: https://review.opendev.org/c/openstack/devstack/+/858996 this one. But I'm not sure where that ended up sorry15:47
clarkbfrickler: Basedo n the ocmments it looks like we need to recheck until we hit a rax node and then compare the performance delta?15:47
fricklerfungi: they also should not report on patches in that repo, neither for devstack, they are a cinder CI. iirc clarkb sent them a mail but got no response15:48
clarkboh ya I haven't seen a response. We can probably disable that account now if we want. iirc I cc'd yall but I'll check to see if I got a direct response that didn't include you15:48
clarkbya no response to me15:49
fricklerclarkb: even then we might need multiple iterations on the devstack patch since io performance is variable15:49
clarkbfrickler: for the rsync thing I feel like I remember that the performance wasn't better. But I don't have hard evidence of that15:49
opendevreviewMerged openstack/openstack-zuul-jobs master: Remove pypy template  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/72054415:50
opendevreviewMerged openstack/openstack-zuul-jobs master: Update openstack-python3-charm-jobs py3 branches  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/89907815:50
fricklero.k., let's do some more rechecks and then either do a larger test by merging or else abandon15:50
clarkbwfm15:50
*** gce108__ is now known as gce10822:31

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