18:00:23 <JayF> #startmeeting tc 18:00:23 <opendevmeet> Meeting started Tue May 16 18:00:23 2023 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:23 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:23 <opendevmeet> The meeting name has been set to 'tc' 18:00:36 <JayF> Welcome to the weekly meeting of the technical committee. 18:00:40 <JayF> A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct 18:00:46 <JayF> #topic Roll Call 18:00:46 <dansmith> o/ 18:00:47 <JayF> o/ 18:00:48 <gmann> o/ 18:01:11 <slaweq> o/ 18:01:40 <JayF> knikolla is off this week; so I'm chairing the meeting 18:01:48 <rosmaita> o/ 18:02:05 <jamespage> o/ 18:02:40 <JayF> Alright, that looks like quorum. Getting starting. 18:02:50 <JayF> No action items from last meeting; so I'm skipping this agenda item. 18:02:55 <JayF> #topic Gate Health Check 18:02:57 <JayF> how is the gate looking? 18:03:20 <spotz_> o/ 18:03:34 <JayF> I'll note for Ironic; our boot-from-volume job was broken by the Cinder bugfix. We're pretty sure Ironic<>Cinder is broken in any branch that had the fix backported into. We're working on a fix of our own to backport, but progress is slow. 18:03:52 <dansmith> could be better (always) but seems pretty good lately 18:03:56 <dansmith> JayF: the cinder cve change you mean? 18:03:58 <JayF> YEs. 18:04:02 <slaweq> I think that (at least in neutron) we finally get it better than last few weeks 18:04:07 <gmann> I have not observed much failure on master 18:04:09 <dansmith> ack, I did not know you guys consume cinder directly 18:04:19 <dansmith> unfortunately I expect we'll see knock-on effects from that change for a while to come yet 18:04:30 <JayF> Yes, we do. We had a conversation with fungi about how, once this is all over, we'd like to have some kind of follow up meeting/conversation/etc 18:04:34 <gmann> wallaby ceph job is broken and requried os-brick fix is backported but as wallaby is EM we cannot release this lib 18:05:14 <noonedeadpunk> o/ 18:05:18 <JayF> gmann: so does that mean wallaby ceph support has to go away? No way around it? 18:05:38 <dansmith> no there are ways around it, 18:05:41 <spotz_> Could someone just apply the patch themselves? 18:05:54 <dansmith> but it's EM and usually not fixing jobs when they break is how we handle those things 18:05:58 <gmann> I will try if that work with fix released version or master os-brick in job 18:06:27 <gmann> spotz_: its job take the version from upper constraints 18:06:41 <fungi> alternatively, stable/wallaby of os-brick could be installed instead of installing the release from pypi 18:06:52 <gmann> but I will try if any way we can mention the fix release version in job and if that is being picked 18:06:54 <dansmith> fungi: you mean the git tree 18:07:04 <fungi> just make it a required-project in the job and it should end up getting installed from source of the corresponding branch 18:07:06 <gmann> yeah 18:07:16 <gmann> required-project and override branch with stable/wallaby 18:07:17 <JayF> That's how we test changes in EM branches of libraries like sushy in Ironic 18:07:55 <JayF> As unfortunate as it is that we have specific items we're complaining about with gate this week; it's better than the "everything is flakey due to X" reports that are sometimes common. These all sound fixable :) 18:08:01 <JayF> Is there anything further about the gate or should we move on? 18:08:51 <JayF> Moving on. 18:08:56 <JayF> #topic Broken docs due to inconsistent naming 18:09:07 <JayF> It's unclear if there's anything left to discuss on this topic. Does anyone have something to share? 18:10:12 <fungi> dod the proposed fixes correct it? 18:10:17 <fungi> s/dod/did/ 18:10:43 <gmann> it is not merged yet, there are few review comments on that 18:10:43 <fungi> #link https://docs.openstack.org/2023.1.antelope/user/ 18:10:48 <fungi> that still looks pretty empty 18:11:00 <JayF> #link https://review.opendev.org/c/openstack/openstack-manuals/+/881290 18:11:08 <JayF> is the proposed fix, it has negative feedback to be addressed 18:11:17 <gmann> yeah 18:11:22 <JayF> Given it's Kristi's patch; I'd assume his time off has put this on pause. 18:11:24 <fungi> got it. so still under review 18:11:41 <JayF> I'm going to move on then 18:12:00 <JayF> #topic Schedule of removing support for Python versions by libraries - how it should align with coordinated releases (tooz case) 18:12:45 <JayF> #link https://review.opendev.org/c/openstack/governance/+/882165 18:12:49 <gmann> we have some comment on proposed PTI, noonedeadpunk not sure if you got time to check those? 18:12:55 <JayF> #link https://review.opendev.org/c/openstack/governance/+/882154 18:13:04 <JayF> are both still under review, I encourage TC members to review them 18:13:21 <gmann> I think we can discuss it here if noonedeadpunk is ok ? 18:13:44 <gmann> I feel we should make py3.8 r any future runtime same for everyone not just for lib 18:14:19 <gmann> otherwise it will be difficult to coordinate and keep it working in the way we want 18:14:19 <JayF> I think there's value in having some of those discussions async in Gerrit, but if we think we can make a quick breakthrough here that's likely good 18:14:39 <noonedeadpunk> well, we can do that, but there was a valid point that we should have a way to deprecate old python versions overall 18:15:31 <noonedeadpunk> and coordinate this somehow. Having that as community goal might not be enough, as some will still need to drop support first 18:15:32 <gmann> deprecated ? 18:15:44 <noonedeadpunk> *remove 18:15:48 <gmann> k 18:16:18 <gmann> goal can give us benefit of planning right like one or two people planning what should drop first and what at end 18:16:29 <JayF> It seems to me we have two separate, related problems: 1) unwinding the breakages that hurt bobcat development (this is done?) and 2) figuring out how to remove python versions moving forward 18:16:38 <opendevreview> Jeremy Stanley proposed openstack/openstack-manuals master: Attempt at fixing broken docs https://review.opendev.org/c/openstack/openstack-manuals/+/881290 18:16:42 <JayF> #1 is urgent, #2 needs to be solved by end-of-cycle... yeah? 18:17:08 <gmann> 1 is done as we have py38 voting job now 18:17:33 <noonedeadpunk> it's done, but not documented 18:17:36 <JayF> Ok, so the problems remaining need addressing this cycle, but we don't have to treat it urgently. That's nice. 18:17:37 <gmann> I think 2nd also urgent as not all project are up to dated on our discussion so having our pti updated is important 18:17:48 <noonedeadpunk> yeah 18:18:01 <JayF> Well, we can update the state of the art for Bobcat 18:18:13 <JayF> without solving future project management problems (which is essentially what the python retirement is) 18:18:15 <JayF> yeah? 18:18:23 <noonedeadpunk> I will check comments on the patch shortly and will have another round of thinking what we can do there 18:18:49 <gmann> we do not have py38 in bobcat testing runtime so any project can argue to drop it that is why updating PTI is also important 18:18:57 <gmann> noonedeadpunk: +1 thanks 18:19:01 <noonedeadpunk> as again, I'm not sure we should oblige everyone to have 3.8 support when we don't support any platform that has it natively 18:19:36 <JayF> I look forward to seeing the updates in the patch. 18:19:47 <JayF> It seems like that's where things are going, so I'm going to move the meeting along if so? 18:19:59 <gmann> I am ok with that if we are able to clearly list what all projects to keep and who all can drop. lib is not defined term here 18:20:37 <JayF> Moving on. 18:20:40 <JayF> #topic Bare recheck state 18:20:44 <JayF> How are rechecks looking like? 18:20:51 <noonedeadpunk> gmann: ++ 18:20:56 <JayF> #link https://etherpad.opendev.org/p/recheck-weekly-summary 18:21:19 <slaweq> all good with rechecks 18:21:32 <slaweq> numbers are pretty ok 18:21:41 <JayF> Thanks for aggregating that data! 18:21:50 <JayF> Anything else before we move on? 18:21:59 <slaweq> nothing from me 18:22:05 <JayF> #topic Open Reviews 18:22:16 <JayF> #link https://review.opendev.org/q/projects:openstack/governance+is:open 18:22:33 <JayF> We have a lot of governance patches up for review right now; please find time to review and vote and/or comment. 18:23:08 <slaweq> I will try to go through them tomorrow morning 18:23:17 <JayF> That's the last item on the agenda. Is there any comments about open reviews, or anything else that needs to be addressed in the TC meeting before we close it for today? 18:23:19 <gmann> I think many of them are depends-on on project config changes 18:25:02 <JayF> I'm going to close up the meeting. 18:25:07 <JayF> thank you everyone for your participation 18:25:09 <JayF> #endmeeting