opendevreview | Merged openstack/election master: Add dates for the 2023.2/B-release[1] https://review.opendev.org/c/openstack/election/+/862387 | 02:25 |
---|---|---|
opendevreview | Yoshi Kadokawa proposed openstack/governance master: Add Cinder Huawei charm https://review.opendev.org/c/openstack/governance/+/867588 | 03:02 |
*** blarnath is now known as d34dh0r53 | 06:54 | |
*** dasm|off is now known as dasm | 12:18 | |
rosmaita | gmann: dyk what channel i'd be likely to find ian choi in? | 15:16 |
fungi | rosmaita: #openstack-election and #openstack-i18n at least | 15:21 |
gmann | rosmaita: and he is responsive on email also in case he is away from IRC <ianyrchoi@gmail.com> | 15:36 |
JayF | Is our meeting in 10 minutes IRC or Video? | 15:50 |
fungi | last week was video, so presumably irc this week? | 15:54 |
JayF | ty; I easily forget | 15:54 |
JayF | and am sorta between setups now; so I don't have VC hooked up to this laptop unless I know I need it :) | 15:54 |
gmann | JayF: IRC in an 2 min | 15:58 |
gmann | I keep it updated as 'Location' in wiki https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions | 15:59 |
gmann | #startmeeting tc | 16:00 |
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 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
opendevmeet | The meeting name has been set to 'tc' | 16:00 |
rosmaita | o/ | 16:00 |
gmann | tc-members: meeting time | 16:00 |
noonedeadpunk | o/ | 16:00 |
gmann | #topic Roll call | 16:00 |
* JayF notes that https://governance.openstack.org/tc/#meeting links to the ics-file-page, not the one that indicates video/irc | 16:00 | |
gmann | o/ | 16:00 |
JayF | o/ | 16:00 |
slaweq | o/ | 16:00 |
gmann | #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions | 16:01 |
gmann | today agenda, let's wait for couple of min in case more member join | 16:01 |
gmann | let's start | 16:03 |
avanzagh | o/ | 16:03 |
gmann | #topic Follow up on past action items | 16:03 |
gmann | none from the last meeting | 16:03 |
gmann | #topic Gate health check | 16:03 |
jungleboyj | I am lurking. :-) | 16:03 |
gmann | we faced gate brake from tox 4 | 16:03 |
gmann | which is pinned for stable branch testing in devstack (integration and devstack tox based job) | 16:04 |
gmann | and for master also it is pinned as workaround for now which need to be fixed and unpin | 16:04 |
gmann | also, I observed more frequent ssh timeout in tempest multinode job and bug is open for that in tempest | 16:05 |
gmann | any other news on gate? | 16:05 |
rosmaita | thanks for getting that done in the stable branches | 16:06 |
clarkb | the ensure-tox role will uncap tox next week. | 16:06 |
fungi | remember that jobs will need their tox versions pinned or compatibility issues fixed by a week from tomorrow | 16:06 |
gmann | and similarly other job if not capped with devstack cap can cap it same way for stable branches | 16:06 |
fungi | #link https://lists.zuul-ci.org/archives/list/zuul-announce@lists.zuul-ci.org/thread/3NNATSUTSIGP5FE2MDY5X2KJ5X4NB4PT/ ensure-tox and tox v4 | 16:07 |
fungi | jobs relying on the ensure-tox role i mean (so that's generally things like unit testing and linting) | 16:07 |
gmann | yeah they need to do explicitly | 16:07 |
rosmaita | ok, thanks for the link, that announcement is clear about what to do | 16:08 |
gmann | let' | 16:08 |
gmann | let's see how many will fail | 16:08 |
clarkb | neutron seems to have discovered that skipsdist is problematic under tox v4 | 16:08 |
clarkb | https://review.opendev.org/c/openstack/neutron/+/867048/ | 16:09 |
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:09 |
gmann | skipsdist is used in many projects tox.ini | 16:10 |
gmann | but I think this is right time to get those fixed | 16:11 |
fungi | yes. but apparently it's mutually exclusive with usedevelop now | 16:11 |
clarkb | I think what it really means is skip installing the project into the venv | 16:11 |
clarkb | which is what breaks usedevelop as that implies an install to the venv | 16:11 |
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 |
gmann | ok | 16:12 |
gmann | anything else on gate things? | 16:12 |
slaweq | nothing from me | 16:13 |
gmann | #topic 2023.1 TC tracker checks | 16:13 |
rosmaita | did they really change 'usedevelop' to 'use_develop' ? | 16:13 |
fungi | rosmaita: they're synonymous still (were in v3 as well looks like() | 16:14 |
fungi | that was a red herring | 16:14 |
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 |
rosmaita | \o/ | 16:14 |
gmann | #link https://etherpad.opendev.org/p/tc-2023.1-tracker | 16:14 |
gmann | JayF: np!, thanks | 16:15 |
spotz_ | o/ | 16:15 |
gmann | one update from tracker is election things. next election dates are selected #link https://governance.openstack.org/election/ | 16:15 |
gmann | and we have two election officials to run the show | 16:16 |
gmann | I will keep eyes on date just in case | 16:16 |
gmann | election start from Feb 1 to March 8 | 16:16 |
gmann | any other updates from anyone on their item from tracker ? | 16:17 |
slaweq | I still didn't had time to get into mine | 16:18 |
slaweq | but I will :) | 16:18 |
gmann | sure, thanks | 16:18 |
gmann | #topic Mistral situation | 16:18 |
gmann | Release team proposing Mistral to mark as release deprecated | 16:19 |
gmann | #link https://review.opendev.org/c/openstack/governance/+/866562 | 16:19 |
gmann | and there we got new volunteer from OVHCloud to help maintaining Mistral | 16:19 |
gmann | and they sent it over ML also #link https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031421.html | 16:19 |
gmann | mistral current maintainer are also aware of it | 16:19 |
gmann | but I did not see any response on email or review if new maintainers are onboarded now | 16:20 |
avanzaghi | Arnaud Morin and myself have been added as core reviewer today | 16:20 |
gmann | avanzaghi: perfect, you are here. | 16:21 |
spotz_ | Thanks for stepping up | 16:21 |
gmann | avanzaghi: as mentioned in email, do you want to change Mistral from DPL model to PTL model in leadership? | 16:21 |
gmann | or it is ok to continue DPL for this cycle and in next cycle you can decide | 16:22 |
avanzaghi | I guess we might still use DPL for this cycle to give me time to get in the project | 16:22 |
gmann | avanzaghi: sure, make sense | 16:23 |
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:23 |
avanzaghi | Noted | 16:24 |
gmann | I think we are now good in Mistral side so no specific action needed for now | 16:24 |
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 |
JayF | Thanks for stepping up | 16:24 |
gmann | ++ | 16:24 |
avanzaghi | Thank you it's noted | 16:25 |
gmann | ok, moving next | 16:25 |
gmann | #topic Recurring tasks check | 16:25 |
gmann | Bare 'recheck' state | 16:25 |
gmann | #link https://etherpad.opendev.org/p/recheck-weekly-summary | 16:25 |
gmann | slaweq: please go ahead | 16:26 |
slaweq | all good with rechecks | 16:26 |
slaweq | I updated etherpad today | 16:26 |
slaweq | so numbers are fresh | 16:26 |
gmann | cool, thanks | 16:26 |
gmann | #topic Open Reviews | 16:27 |
gmann | #link https://review.opendev.org/q/projects:openstack/governance+is:open | 16:27 |
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:27 |
gmann | other than that we are doing good on open reviews. | 16:28 |
JayF | Is there anything wrong with governance gate? I saw a lot of V-1. | 16:28 |
JayF | Didn't know if one of us needs to take time to resolve some issue (tox?) there... | 16:28 |
JayF | If so I can; if it's already being dealt with please say so and I'll save my time :D | 16:29 |
gmann | is it ? I think it is green | 16:29 |
gmann | but let me recheck and check | 16:29 |
JayF | of the 3 open reviews in the governance queue from the link above; 2 are V-1 | 16:29 |
JayF | looks like it's actual lint issues; so really we only have one outstanding; ready for review request | 16:30 |
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 |
gmann | yeah, gate is ok as 867062 ran yesterday and it is green | 16:30 |
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 |
noonedeadpunk | So change can be merged just with positive verified label | 16:31 |
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:31 |
JayF | Or are you saying the opposite; it shouldn't need anything but RC+1s and V+1? | 16:32 |
noonedeadpunk | It's new gerrit renderring question :D | 16:32 |
fungi | seems like this is more of a workaround for it not appearing in the summary table | 16:32 |
fungi | in gerrit 3.6 | 16:32 |
gmann | noonedeadpunk: we do not merge it automatically base don RC. it is manual merge +W by TC chair | 16:32 |
gmann | and we check those fro the check-review-status script | 16:32 |
gmann | but it is difficult to see those now | 16:33 |
noonedeadpunk | yes, exactly that point ^ | 16:33 |
JayF | ah, understand | 16:33 |
gmann | yeah, i am also finding it difficult | 16:33 |
gmann | and if I understand it correctly there is no way to make it always showing those like we use to have? | 16:34 |
fungi | clarkb was talking about possible approaches for that in #opendev yesterday | 16:34 |
noonedeadpunk | so making RC a requirement (eventually it still is) we will workaround new behaviour | 16:34 |
gmann | making requirement where? | 16:34 |
noonedeadpunk | but yeah, that discussion doesn't worth time that's been spent on it | 16:34 |
gmann | yeah | 16:35 |
gmann | anyways, that is all from today meeting. we can discuss that after meeting or in opendev chanel | 16:35 |
clarkb | gmann: making it a requirement to merge. Gerrit seems to treat those labels as special | 16:35 |
gmann | and we will have next week meeting also | 16:35 |
gmann | clarkb: ok that we do already | 16:35 |
gmann | anything else for today? | 16:36 |
noonedeadpunk | Have small update about sahara state | 16:36 |
gmann | sure | 16:36 |
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 |
gmann | ok, link please | 16:37 |
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:37 |
noonedeadpunk | #link https://review.opendev.org/c/openstack/sahara/+/864728 | 16:38 |
noonedeadpunk | As of today there's no reaction to ML or any comment to the patch. | 16:38 |
gmann | I see | 16:38 |
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 |
gmann | sure, let's wait as it is holiday season also | 16:39 |
gmann | but if gate is not fixed then it is clear to call out for help and mark Inactive | 16:40 |
gmann | noonedeadpunk: do you want it to add in next weekly meeting agenda to track the progress? | 16:40 |
noonedeadpunk | yeah, I think it might be worth it | 16:41 |
noonedeadpunk | as gate is also was broken when releasing Zed | 16:41 |
gmann | sure, will do. | 16:41 |
gmann | thanks for keep eyes on it and fixing the gate | 16:41 |
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 |
gmann | true | 16:41 |
gmann | any other topic for today? | 16:42 |
gmann | if not then let's close it | 16:43 |
gmann | thanks everyone for joining | 16:43 |
gmann | #endmeeting | 16:43 |
opendevmeet | Meeting ended Wed Dec 14 16:43:17 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:43 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-14-16.00.html | 16:43 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-14-16.00.txt | 16:43 |
opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-14-16.00.log.html | 16:43 |
slaweq | o/ | 16:43 |
clarkb | gmann: it is not a merge requirement as far as I can tell: https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/governance.config#L31 | 16:44 |
clarkb | gmann: the function noop there means this is an informational label and gerrit 3.6 is prioritizing the rendering of labels required for merging over those that are not | 16:44 |
clarkb | at least that is what I think is going on. I have not tried converting any of these lables to a merge requirement yet | 16:44 |
noonedeadpunk | This is quite good candidate to try tbh... And looking that CR label is also in same category as RollCall vote | 16:45 |
noonedeadpunk | (in UI) I'm pretty sure it's the case | 16:45 |
gmann | clarkb: ohk, it is not in gerrit there but we do have that in our script | 16:45 |
gmann | and it is hard to add that as requirement in gerrit as TC merging requirement is based on the type of change | 16:46 |
gmann | noonedeadpunk: as per the type of change need different requirement of RC votes it is difficult to automate it | 16:46 |
gmann | for example, any patch with RC-1 can also merge based on other vote criteria as per motion or governance house rules | 16:47 |
clarkb | gmann: ok gerrit cannot know anything about your script though | 16:47 |
gmann | yeah it is many things in criteria not just number of vote, number of days it open etc | 16:48 |
clarkb | yes I understand that. I'm just trying to express what I think gerrit's behavior is here | 16:49 |
clarkb | "submit requirements" aka any label necessary for merging is given priority in the UI | 16:49 |
noonedeadpunk | I wasn't thinking about automating. I was thinking about showing votes better in UI | 16:57 |
gmann | yeah, understand that. i cannot find any value we can add there which does block on -/+ value but just make it in Submit Requirement | 16:58 |
gmann | https://gerrit-review.googlesource.com/Documentation/config-labels.html | 16:58 |
gmann | AnyWithBlock with 0 ? | 16:58 |
gmann | does not seems so, all need some positive or negative value | 16:59 |
clarkb | anywithblock requires a negative value | 17:00 |
noonedeadpunk | also I think if it would be "submit requirements" - votes will be shown for reviewers, so will be a bit easier to see who voted without hovering over label | 17:00 |
clarkb | I don't know your workflow well enough to make a suggestion here. Again I'm just trying to capture the gerrit behavior so that potential work arounds can be found | 17:00 |
gmann | but anything in 'submit requirements' also does not show votes you have to go over label to see it right? | 17:02 |
clarkb | gmann: they are shown in the reviewers list and in the comments below or in the label hover | 17:03 |
clarkb | though maybe the reviewers list only shows code-review votes? | 17:03 |
gmann | yes in Reviewers list but for label we need to hover it over | 17:05 |
clarkb | or look at the comments list | 17:05 |
gmann | previous way was so easy not sure why to change that :) | 17:06 |
clarkb | I'm sure google had a good reason. But didn't consider other users when the change was made | 17:06 |
gmann | let me try if we can make TC RC in 'submit requirements' clarkb any way I can try it without merging it in project-config ? | 17:07 |
clarkb | gmann: no | 17:07 |
gmann | hmm | 17:08 |
clarkb | but you can always revert it | 17:08 |
gmann | yeah, let me try something late this week or next week. | 17:08 |
clarkb | gmann: just reading the existing votes for roll call why wouldn't anywithblock work? | 17:13 |
clarkb | -1 "no" would prevent merging. Everything else can merge | 17:13 |
clarkb | the default is 0 so default is mergeable | 17:14 |
clarkb | your script can still double check that appropriate +1 is set when necessary | 17:14 |
clarkb | the only thing it would change is if you want to be able to override the -1 | 17:15 |
clarkb | which I guess maybe you do if a majority vote +1? | 17:15 |
fungi | i think the tc expects rc -1 to not be blocking, while rc -2 represents a blocking veto | 17:15 |
fungi | or at least that's how we used to do it, but maybe that's changed in recent years | 17:16 |
gmann | yeah, RC with -1 can still be mergable | 17:16 |
clarkb | fungi: there is no -2 rc currently. But maybe that is a workaround. Add a -2 to satisfy the check | 17:16 |
clarkb | -1 is still mergeable in that case. and tell people to no -2 unless they would also -W? | 17:17 |
fungi | that's an interesting idea. you can make -2 effectively unreachable by not granting anyone access to set it | 17:17 |
gmann | but we need to allow -2 as alowed value for RC label right? | 17:17 |
gmann | ohk | 17:17 |
gmann | or we can make -2 as blocking for any procedure change, in case chair want to hold it for some reason | 17:18 |
gmann | or yes no giving access to it | 17:19 |
gmann | let me try | 17:19 |
*** tosky_ is now known as tosky | 21:12 | |
*** dasm is now known as dasm|off | 21:26 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!