16:00:12 <gmann> #startmeeting tc 16:00:12 <opendevmeet> Meeting started Wed Dec 14 16:00:12 2022 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:12 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:12 <opendevmeet> The meeting name has been set to 'tc' 16:00:23 <rosmaita> o/ 16:00:24 <gmann> tc-members: meeting time 16:00:27 <noonedeadpunk> o/ 16:00:28 <gmann> #topic Roll call 16:00:30 * JayF notes that https://governance.openstack.org/tc/#meeting links to the ics-file-page, not the one that indicates video/irc 16:00:30 <gmann> o/ 16:00:31 <JayF> o/ 16:00:31 <slaweq> o/ 16:01:13 <gmann> #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions 16:01:31 <gmann> today agenda, let's wait for couple of min in case more member join 16:03:08 <gmann> let's start 16:03:09 <avanzagh> o/ 16:03:16 <gmann> #topic Follow up on past action items 16:03:26 <gmann> none from the last meeting 16:03:34 <gmann> #topic Gate health check 16:03:40 <jungleboyj> I am lurking. :-) 16:03:46 <gmann> we faced gate brake from tox 4 16:04:08 <gmann> which is pinned for stable branch testing in devstack (integration and devstack tox based job) 16:04:32 <gmann> and for master also it is pinned as workaround for now which need to be fixed and unpin 16:05:25 <gmann> also, I observed more frequent ssh timeout in tempest multinode job and bug is open for that in tempest 16:05:50 <gmann> any other news on gate? 16:06:08 <rosmaita> thanks for getting that done in the stable branches 16:06:18 <clarkb> the ensure-tox role will uncap tox next week. 16:06:34 <fungi> remember that jobs will need their tox versions pinned or compatibility issues fixed by a week from tomorrow 16:06:48 <gmann> and similarly other job if not capped with devstack cap can cap it same way for stable branches 16:07:01 <fungi> #link https://lists.zuul-ci.org/archives/list/zuul-announce@lists.zuul-ci.org/thread/3NNATSUTSIGP5FE2MDY5X2KJ5X4NB4PT/ ensure-tox and tox v4 16:07:31 <fungi> jobs relying on the ensure-tox role i mean (so that's generally things like unit testing and linting) 16:07:51 <gmann> yeah they need to do explicitly 16:08:12 <rosmaita> ok, thanks for the link, that announcement is clear about what to do 16:08:13 <gmann> let' 16:08:30 <gmann> let's see how many will fail 16:08:53 <clarkb> neutron seems to have discovered that skipsdist is problematic under tox v4 16:09:06 <clarkb> https://review.opendev.org/c/openstack/neutron/+/867048/ 16:09:24 <clarkb> just a heads up for anyone looking at updating their tox.ini for compatibility and running into problems with your project not getting installed into the venv 16:10:08 <gmann> skipsdist is used in many projects tox.ini 16:11:04 <gmann> but I think this is right time to get those fixed 16:11:13 <fungi> yes. but apparently it's mutually exclusive with usedevelop now 16:11:29 <clarkb> I think what it really means is skip installing the project into the venv 16:11:43 <clarkb> which is what breaks usedevelop as that implies an install to the venv 16:12:05 <clarkb> anyway its one of the weirder behavior changes we've seen so I wanted to call it out. The others are pretty mechanical updates to translate from old to new 16:12:36 <gmann> ok 16:12:50 <gmann> anything else on gate things? 16:13:26 <slaweq> nothing from me 16:13:33 <gmann> #topic 2023.1 TC tracker checks 16:13:34 <rosmaita> did they really change 'usedevelop' to 'use_develop' ? 16:14:16 <fungi> rosmaita: they're synonymous still (were in v3 as well looks like() 16:14:26 <fungi> that was a red herring 16:14:37 <JayF> I intend to focus on getting something written up for my item in the TC tracker over the rest of the month while things are a little slow. 16:14:39 <rosmaita> \o/ 16:14:56 <gmann> #link https://etherpad.opendev.org/p/tc-2023.1-tracker 16:15:05 <gmann> JayF: np!, thanks 16:15:27 <spotz_> o/ 16:15:55 <gmann> one update from tracker is election things. next election dates are selected #link https://governance.openstack.org/election/ 16:16:12 <gmann> and we have two election officials to run the show 16:16:22 <gmann> I will keep eyes on date just in case 16:16:48 <gmann> election start from Feb 1 to March 8 16:17:39 <gmann> any other updates from anyone on their item from tracker ? 16:18:12 <slaweq> I still didn't had time to get into mine 16:18:15 <slaweq> but I will :) 16:18:26 <gmann> sure, thanks 16:18:41 <gmann> #topic Mistral situation 16:19:01 <gmann> Release team proposing Mistral to mark as release deprecated 16:19:03 <gmann> #link https://review.opendev.org/c/openstack/governance/+/866562 16:19:23 <gmann> and there we got new volunteer from OVHCloud to help maintaining Mistral 16:19:39 <gmann> and they sent it over ML also #link https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031421.html 16:19:51 <gmann> mistral current maintainer are also aware of it 16:20:26 <gmann> but I did not see any response on email or review if new maintainers are onboarded now 16:20:59 <avanzaghi> Arnaud Morin and myself have been added as core reviewer today 16:21:15 <gmann> avanzaghi: perfect, you are here. 16:21:46 <spotz_> Thanks for stepping up 16:21:47 <gmann> avanzaghi: as mentioned in email, do you want to change Mistral from DPL model to PTL model in leadership? 16:22:00 <gmann> or it is ok to continue DPL for this cycle and in next cycle you can decide 16:22:51 <avanzaghi> I guess we might still use DPL for this cycle to give me time to get in the project 16:23:09 <gmann> avanzaghi: sure, make sense 16:23:56 <gmann> but thanks avanzaghi for helping there and as next step you can ping release team member in #openstack-release on what are the required things to get it release 16:24:14 <avanzaghi> Noted 16:24:20 <gmann> I think we are now good in Mistral side so no specific action needed for now 16:24:28 <JayF> I'd also generally say if you are confused about anything with keeping it up, or getting going upstream, even just putting a message in here I know I'll be willing to help and others likely will to. 16:24:31 <JayF> Thanks for stepping up 16:24:41 <gmann> ++ 16:25:13 <avanzaghi> Thank you it's noted 16:25:39 <gmann> ok, moving next 16:25:43 <gmann> #topic Recurring tasks check 16:25:49 <gmann> Bare 'recheck' state 16:25:59 <gmann> #link https://etherpad.opendev.org/p/recheck-weekly-summary 16:26:07 <gmann> slaweq: please go ahead 16:26:10 <slaweq> all good with rechecks 16:26:21 <slaweq> I updated etherpad today 16:26:29 <slaweq> so numbers are fresh 16:26:47 <gmann> cool, thanks 16:27:07 <gmann> #topic Open Reviews 16:27:12 <gmann> #link https://review.opendev.org/q/projects:openstack/governance+is:open 16:27:44 <gmann> one change I would like to get review, changing the timeline for Inactive projects #link https://review.opendev.org/c/openstack/governance/+/867062 16:28:20 <gmann> other than that we are doing good on open reviews. 16:28:32 <JayF> Is there anything wrong with governance gate? I saw a lot of V-1. 16:28:43 <JayF> Didn't know if one of us needs to take time to resolve some issue (tox?) there... 16:29:03 <JayF> If so I can; if it's already being dealt with please say so and I'll save my time :D 16:29:18 <gmann> is it ? I think it is green 16:29:29 <gmann> but let me recheck and check 16:29:39 <JayF> of the 3 open reviews in the governance queue from the link above; 2 are V-1 16:30:12 <JayF> looks like it's actual lint issues; so really we only have one outstanding; ready for review request 16:30:18 <gmann> ohk they are V-1 due to their change not gate issue, like project-config change is not merged for charm thigns 16:30:54 <gmann> yeah, gate is ok as 867062 ran yesterday and it is green 16:31:19 <noonedeadpunk> I actually wonder if we should try and define Roll-Call vote as requirement for merge. As since it's among "trigger votes" I think it's not set as requirement now 16:31:54 <noonedeadpunk> So change can be merged just with positive verified label 16:31:56 <JayF> That sounds a little bit like a potential social problem more than a technical one? If a change is merged to governance without proper vote; it's not really changing the governance, right? 16:32:18 <JayF> Or are you saying the opposite; it shouldn't need anything but RC+1s and V+1? 16:32:21 <noonedeadpunk> It's new gerrit renderring question :D 16:32:24 <fungi> seems like this is more of a workaround for it not appearing in the summary table 16:32:32 <fungi> in gerrit 3.6 16:32:34 <gmann> noonedeadpunk: we do not merge it automatically base don RC. it is manual merge +W by TC chair 16:32:47 <gmann> and we check those fro the check-review-status script 16:33:05 <gmann> but it is difficult to see those now 16:33:18 <noonedeadpunk> yes, exactly that point ^ 16:33:28 <JayF> ah, understand 16:33:35 <gmann> yeah, i am also finding it difficult 16:34:08 <gmann> and if I understand it correctly there is no way to make it always showing those like we use to have? 16:34:10 <fungi> clarkb was talking about possible approaches for that in #opendev yesterday 16:34:12 <noonedeadpunk> so making RC a requirement (eventually it still is) we will workaround new behaviour 16:34:43 <gmann> making requirement where? 16:34:44 <noonedeadpunk> but yeah, that discussion doesn't worth time that's been spent on it 16:35:02 <gmann> yeah 16:35:34 <gmann> anyways, that is all from today meeting. we can discuss that after meeting or in opendev chanel 16:35:39 <clarkb> gmann: making it a requirement to merge. Gerrit seems to treat those labels as special 16:35:40 <gmann> and we will have next week meeting also 16:35:59 <gmann> clarkb: ok that we do already 16:36:10 <gmann> anything else for today? 16:36:23 <noonedeadpunk> Have small update about sahara state 16:36:26 <gmann> sure 16:37:13 <noonedeadpunk> So there's a patch now that covers all found issues in the project and passing gates and all tempest tests that were before - had to squash several bugs together, but patch quite feasable 16:37:32 <gmann> ok, link please 16:37:58 <noonedeadpunk> And I've sent ML targeting sahara cores asking for review also forwarded to PTL email directly after couple of days without reply 16:38:02 <noonedeadpunk> #link https://review.opendev.org/c/openstack/sahara/+/864728 16:38:25 <noonedeadpunk> As of today there's no reaction to ML or any comment to the patch. 16:38:59 <gmann> I see 16:39:08 <noonedeadpunk> We still have couple of weeks before milestone-2, so I'm going to wait for another week and in case of no feedback I guess we can mark project as inactive 16:39:43 <gmann> sure, let's wait as it is holiday season also 16:40:01 <gmann> but if gate is not fixed then it is clear to call out for help and mark Inactive 16:40:37 <gmann> noonedeadpunk: do you want it to add in next weekly meeting agenda to track the progress? 16:41:06 <noonedeadpunk> yeah, I think it might be worth it 16:41:17 <noonedeadpunk> as gate is also was broken when releasing Zed 16:41:27 <gmann> sure, will do. 16:41:39 <gmann> thanks for keep eyes on it and fixing the gate 16:41:50 <noonedeadpunk> So making another release with broken gates (and code that is not supposed to work against py3) is likely not worth it 16:41:59 <gmann> true 16:42:39 <gmann> any other topic for today? 16:43:10 <gmann> if not then let's close it 16:43:14 <gmann> thanks everyone for joining 16:43:17 <gmann> #endmeeting