18:00:30 <gouthamr> #startmeeting tc 18:00:30 <opendevmeet> Meeting started Tue Jul 23 18:00:30 2024 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:30 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:30 <opendevmeet> The meeting name has been set to 'tc' 18:00:57 <gouthamr> Welcome to the weekly meeting of the OpenStack Technical Committee. A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduc 18:01:12 <gouthamr> https://openinfra.dev/legal/code-of-conduct 18:01:24 <gouthamr> Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee 18:01:35 <gouthamr> #topic Roll Call 18:01:36 <noonedeadpunk> o/ 18:01:40 <dansmith> o/ 18:01:41 <gmann> o/ 18:01:41 <gtema> o/ 18:01:47 <frickler> \o 18:01:50 <JayF> o/ 18:02:22 <gouthamr> #chair frickler 18:02:22 <opendevmeet> Current chairs: frickler gouthamr 18:03:20 <gouthamr> noted absence: spotz[m] slaweq 18:03:38 <gouthamr> so everyone's accounted for :) 18:03:45 <gouthamr> lets get started 18:03:58 <gouthamr> #topic AIs from last week 18:04:04 <noonedeadpunk> ccccccvcvrvvejkecigfbeeuteglerlvnjfrujgiekhf 18:04:12 <gouthamr> oops 18:04:12 <noonedeadpunk> doh 18:04:21 <gouthamr> :D 18:04:31 <noonedeadpunk> thankfully it\s not a password :D 18:04:41 <gmann> :) 18:04:53 <gouthamr> anyway, we had a few action items :) 18:05:07 <gouthamr> 1. Review the eventlet removal proposal and other pending patches 18:05:20 <gouthamr> this proposal has now merged; thank you everyone that provided feedback 18:05:33 <gouthamr> hberaud et al have some AIs here to follow up 18:06:14 <gouthamr> there were a number of other changes that merged in the past week as well... we're ready to retire some items from our tracking! 18:06:26 <gouthamr> we'll get around to that in a little bit 18:06:34 <gouthamr> 2. Investigate and address the concerns regarding the skyline project 18:07:15 <gouthamr> thank you for posting the concern you shared last week on the skyline graduation patch, frickler 18:08:02 <gouthamr> the patch merged; and am hoping wu_wenixang will respond to your concerns 18:08:24 <gouthamr> 3. Monitor and merge the submitted fix for Masakari 18:08:38 <noonedeadpunk> that merged 18:08:41 <gouthamr> i looked at the project's open changes, and things looked better 18:09:18 <noonedeadpunk> gates look quite healthy now 18:09:22 <frickler> yes, the reqs cross job also went green again I think 18:09:33 <gouthamr> ah, yes.. so sqlalchemy2.0 concerns are addressed there, and that was the last project we were concerned with? 18:11:03 * gouthamr thinks so.. requirements gate looks super green 18:11:21 <gouthamr> great; that's all the AIs i noted.. did anyone else have any? 18:11:45 <noonedeadpunk> ┌(° ͜ʖ͡°)┘ 18:12:11 <gouthamr> is that a "yes, i have one?" :) 18:12:38 <noonedeadpunk> nah, that's amazing that requirements gates are green now and project health is fine 18:12:45 <gouthamr> ++ 18:12:52 <gouthamr> an ascii jig 18:13:00 <gouthamr> #topic A reminder on "house rules" 18:13:37 <gouthamr> just a topic to bring our attention back to teh way reviews work on the "governance" repository 18:14:04 <gouthamr> the biggest one where we need buy-in from most of the TC are "charter-change" proposals 18:14:08 <gouthamr> #link https://governance.openstack.org/tc/reference/charter.html#charter-motions-section 18:14:39 <gouthamr> these changes need 2/3rds of the TC to approve; and in this 9-member TC, it means 6 people approving 18:15:25 <gouthamr> an approval means a +1 roll call vote 18:15:47 <gouthamr> the change prposer must also exercise this vote :) - i know that sounds redundant 18:16:05 <gouthamr> but, it helps keeping records for important changes like these 18:16:42 <gouthamr> next up are things we use "formal-vote" for 18:16:46 <gouthamr> #link https://governance.openstack.org/tc/reference/charter.html#amendment 18:16:52 <gouthamr> ugh 18:17:01 <gouthamr> i messed up the links 18:17:04 <gouthamr> apologies 18:17:33 <gouthamr> #link https://governance.openstack.org/tc/reference/charter.html#amendment ("charter-change") 18:17:42 <gouthamr> #link https://governance.openstack.org/tc/reference/charter.html#charter-motions-section ("formal-vote") 18:18:29 <gouthamr> these are resolutions, project retirements, project activity annotations 18:18:41 <gouthamr> (any more examples?) 18:19:20 <gouthamr> any formal-vote change needs 1/3rd of the TC approving - at least, which means, 3 out of 9 TC members must +1 this change 18:20:05 <gouthamr> the proposer needn't +1, i've been waiting for more of a consensus around "formal-vote" if possible 18:21:38 <gouthamr> since these numbers that I'm sharing are the _minimum_ number of positive approvals, i have yet-another rule to follow prior to merging anything that has the minimum number of positive votes 18:21:56 <gouthamr> the latest patch is atleast a week old before it is workflowed 18:22:09 <gmann> motions actually does not have proposer concept and all tc members votes are important/counted irrespective of who's idea it was or who is proposer 18:23:12 <gouthamr> true 18:24:07 <gouthamr> thank you, gmann JayF - do keep me honest if you were using any other written/un-written rules in addition 18:24:33 <gouthamr> we do have a number of changes that don't fit either category 18:24:37 <JayF> Honestly, the only guideline I provided was continuing to whip votes, even if not required, until we got a majority. 18:24:46 <gouthamr> ^^ +1 18:24:54 <JayF> Just because I think it makes the TC look unengaged to be unable to gather a majority of votes on perfunctory things. 18:25:26 <gmann> yeah, these are minimum things to merge and depends on the change we can keep it open for more votes and for community also not just TC 18:25:28 <gouthamr> #link https://governance.openstack.org/tc/reference/house-rules.html 18:25:28 <gouthamr> all the other kinds of changes are described in this doc ^ 18:26:22 <gouthamr> JayF: gmann: ty.. 18:27:04 <gouthamr> i wanted to reprise this $topic because we tend to forget the minutia 18:27:49 <gouthamr> no specific reason :) and never a bad time to refresh this 18:28:20 <gouthamr> anything else to add? 18:31:05 * gouthamr takes silence as no.. 18:31:25 <gouthamr> #topic A check on gate health 18:32:24 <gouthamr> does any one have any issues that've noticed, or fixes they're pursuing across the gate jobs? 18:33:03 <dansmith> seems have been pretty reasonable in the last week AFAICT 18:33:09 <JayF> I think Ironic has been doing OK too. 18:33:25 <gouthamr> +1 seen a stable-ish gate 18:33:28 <gmann> yeah, did not notice any blocking or frequent failure 18:34:00 <gtema> there were some tempest failures wrt glance recently (noticed in Keystone) 18:34:06 * gouthamr doesn't want to anger dana 18:34:15 <clarkb> stable/2023.1 has the setuptools and packaging packages incompatibility problem 18:34:15 <gtema> not very often, but not a 1 time occurence 18:35:19 <dansmith> gtema: got a linik? 18:35:30 <gtema> looking 18:36:26 <JayF> clarkb: do we have a workaround for that yet? 18:36:39 <gouthamr> #link https://review.opendev.org/c/openstack/requirements/+/924764 (Update packaging constraint to match 2023.2) 18:37:00 <JayF> thanks for that o/ 18:37:05 <fungi> notably, it's blocking the ossa-2024-002 patch on that branch 18:37:16 <clarkb> there is also a workaround in devstack to stop installing the problematic project (dbcounter) 18:37:20 <fungi> so getting it addressed quickly would be appreciated, yes 18:37:23 <clarkb> I think the devstack change was approved but failed for some reason 18:37:42 <gouthamr> #link https://review.opendev.org/c/openstack/devstack/+/924740 ([stable only] Unset the default value of MYSQL_GATHER_PERFORMANCE) 18:37:59 <gouthamr> devstack-platform-debian-bullseye failed 18:38:43 <gouthamr> while installing ovs 18:38:54 <gouthamr> https://zuul.opendev.org/t/openstack/build/4e5d78e6489c45e2b10e549a6ad41d9d/log/job-output.txt#9323 18:40:28 <gouthamr> no need to debug here, but zuul didn't run that job for ~a month on that branch 18:40:41 <frickler> so that's the same error caused by the new setuptools 18:41:10 <gouthamr> oh 18:42:02 <gouthamr> #link https://review.opendev.org/c/openstack/requirements/+/924494 (Cap the maximum setuptools version) 18:43:07 <gouthamr> could the jobs turn off dbcounter temporarily and get the CVE fix in? 18:43:45 <frickler> that failure in neutron/ovs install is with dbcounter turned off 18:43:57 <frickler> so likely 924764 is the fix that will be needed 18:45:30 <frickler> but I'd really like to see feedback from tonyb or prometheanfire on that one 18:45:57 <gouthamr> frickler: i meant selectively disable_service dbcounter if they're inheriting other jobs.. 18:46:26 <gouthamr> not helpful perhaps if the packaging version can be safely bumped 18:47:33 <gouthamr> thanks for raising the awareness about this here 18:47:48 <gouthamr> we can chat about this on the various patches mentioned.. 18:48:09 <gouthamr> i'd like to move to the last topic of the day for a quick few minutes 18:48:13 <gouthamr> any concerns? 18:48:43 <gouthamr> #topic 2024.2 TC Tracker 18:48:47 <gouthamr> #link https://etherpad.opendev.org/p/tc-2024.2-tracker (Technical Committee activity tracker) 18:48:57 <gouthamr> ^ we've updates added to each item here 18:49:32 <gouthamr> is there any thing that needs a discussion here to help move along? 18:51:03 <gouthamr> *crickets* :) 18:51:29 <gouthamr> there're a couple of "openstack-manuals" changes 18:51:35 <gouthamr> #link https://review.opendev.org/q/project:openstack/openstack-manuals+status:open 18:51:52 <gouthamr> nothing urgent, but, could some folks with nova/glance expertise, help out with the reviews here? 18:52:29 <gouthamr> spotz[m] ty for the reviews there so far 18:52:42 <prometheanfire> frickler: seems right 18:53:15 <gouthamr> specifically these changes; 18:53:19 <gouthamr> #link https://review.opendev.org/q/project:openstack/openstack-manuals+status:open+owner:d1nuc0m@protonmail.com 18:53:33 <gouthamr> ty in advance.. 18:54:28 <gouthamr> #topic Open Discussion and Reviews 18:55:41 <gouthamr> i was looking at a bunch of changes in "repositories maintained by the TC" and many of those are quite old 18:55:48 <gouthamr> #link https://review.opendev.org/q/project:openstack/api-site+status:open 18:55:48 <gouthamr> #link https://review.opendev.org/q/project:openstack/constellations+status:open 18:55:48 <gouthamr> #link https://review.opendev.org/q/project:openstack/goal-tools+status:open 18:55:48 <gouthamr> #link https://review.opendev.org/q/project:openstack/ideas+status:open 18:55:48 <gouthamr> #link https://review.opendev.org/q/project:openstack/openstack+status:open 18:56:33 <fungi> openstack/openstack is a superrepo so i think if there are any reviews it's just for adding/removing subrepos 18:56:55 <clarkb> yes, and I think it regularly gets ignored and things get out of sync 18:56:56 <fungi> some of those other repositories may be past their sell-by date 18:57:14 <JayF> given how old the unreviewed PRs are, I'd remove the "may" from that statement 18:57:18 <frickler> there's a change by mordred to restructure it according to governance 18:57:33 <clarkb> we may even consider not having the superrepo if it isn't properly maintained. I don't know if it has utility if the history is either polluted with extra stuff or missing important bits 18:57:46 <fungi> the constellations effort was abandoned years ago, i don't think the ideas effort was formally abandoned but i don't know if it's still publishing anywhere 18:58:13 <gouthamr> https://governance.openstack.org/ideas/ 18:58:21 <gouthamr> ^ #til 18:58:30 <fungi> similarly i don't know if the tools in goal-tools are still useful with the current goals workflow, but it merits double-checking 18:58:47 <gouthamr> ++ 18:58:59 <JayF> There is some sad but funny irony in the website dedicated to crazy openstack ideas being a ghost town. 18:59:22 <fungi> i find it hard to believe we somehow stopped being crazy 18:59:28 <fungi> probably just got better at hiding it 19:00:00 <gouthamr> no we just moved to a different facility 19:01:03 <gouthamr> :D thanks for engaging here.. i can try to round up some of these and discuss specific changes next few weeks 19:01:05 * frickler hops to the next meeting three room to the right 19:01:11 <gouthamr> its past the hour here 19:01:15 <gouthamr> thank you all for attending 19:01:19 <gouthamr> #endmeeting