14:00:35 #startmeeting networking 14:00:35 Meeting started Tue Jan 31 14:00:35 2023 UTC and is due to finish in 60 minutes. The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:35 The meeting name has been set to 'networking' 14:00:36 o/ 14:00:36 o/ 14:00:38 hi 14:00:40 Hi 14:00:42 hello all 14:00:42 o/ 14:01:27 o/ 14:01:41 o/ 14:01:49 let's start 14:01:55 o/ 14:01:57 #topic announcements 14:02:00 #link https://releases.openstack.org/antelope/schedule.html 14:02:14 This is R-7 week 14:02:30 and the election nomination process has began 14:02:36 #link https://releases.openstack.org/antelope/schedule.html#b-election-nominations 14:02:51 and this 14:02:53 #link https://governance.openstack.org/election/ 14:03:21 I still need to discuss in my company if I'm proposing myself again as PTL 14:03:23 in any case 14:03:40 anyone is welcome to propose his/her candidacy 14:04:10 and another reminder: in 2 weeks we have 14:04:15 1) the feature freeze 14:04:36 2) the final release for the client libraries. E.g.: n-lib, os-ken, ovsdbapp 14:04:40 so be aware please 14:04:52 3) this is the A-3 milestone 14:05:29 and again, please check the openinfra presentations 14:05:39 the last one, done 1 week ago: "Large Scale Ops Deep Dive: Ubisoft" 14:05:45 #link https://openinfra.dev/live/#all-episodes 14:06:01 thanks for the url ++ 14:06:09 ^^ thank you folks for those videos 14:06:13 really interesting topics for the first weeks of this year 14:06:21 yeap 14:06:30 yes, indeed 14:06:55 something else missing here? 14:07:04 ralonsoh++ for continuing being PTL :) thx a lot 14:07:21 ++ 14:07:25 ++ indeed 14:07:28 hehehe let's see what happens during the next weeks 14:07:35 :-) yeah, thanks for the cycle and we are backing you 14:07:51 thank you folks 14:08:14 ok, let's jump to the next topic 14:08:15 thanks ralonsoh, keep going please! 14:08:29 hehehe 14:08:34 #topic bugs 14:08:41 busy week from obondarev 14:08:53 many news bugs (most of them from slaweq) 14:08:59 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031953.html 14:09:03 ups :) 14:09:13 we'll talk about RBAC in the next topic 14:09:39 not busy as slaweq usually triages bugs himself, so thanks slaweq!:) 14:10:02 right 14:10:16 there are 3 bugs not assigned or that need to be discussed 14:10:22 :) 14:10:24 I didn't assign myself to all of them but I will take them one by one 14:10:25 so don't worry about those related to RBAC 14:10:43 #link https://bugs.launchpad.net/neutron/+bug/2004041 14:10:49 ok, this one is now assigned 14:10:56 (I did this list yesterday) 14:11:13 #link https://bugs.launchpad.net/neutron/+bug/2004004 14:11:18 slaweq: what is the one related to rbacs? 14:11:35 we'll talk about those bugs in the next topic 14:11:36 i can perhaps help as i'm working on this area this days 14:11:45 sorry 14:11:52 about https://bugs.launchpad.net/neutron/+bug/2004004 14:11:52 go ahead ralonsoh 14:12:05 according to the last comment, the problem is solved in Zed 14:12:24 because of https://review.opendev.org/c/openstack/neutron/+/771621 14:12:34 @sahid, it's not one but 6 which are marked as "High" in the email https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031953.html 14:12:36 I'll check if we need to backport this patch then 14:13:39 slaweq: ack thank you 14:13:46 never mind, I'm checking the comments 14:14:15 and seems that the submitter of the bug was using a version that is not in upstream 14:14:35 so, IMO, the bug is not valid 14:14:44 can anyone double check that? 14:14:47 yes it seems to be Rocky or similar 14:15:05 if we speak about https://bugs.launchpad.net/neutron/+bug/2004004 14:15:09 yes 14:15:18 but seems that he was not using the upstream version 14:15:25 Moreover, with respect to Florian's use case, there is already code upstream to handle such situations, as one can see in [4]. The that happened with Florian only exists because he is not using upstream Neutron version. 14:15:53 please, some else double check the bug 14:16:07 and close it if needed or propose a solution 14:17:15 the last one is 14:17:18 #link https://bugs.launchpad.net/neutron/+bug/2003842 14:17:48 I commented in c#1: with routed networks, OVN does not support routers 14:17:59 the router port won't have an IP assigned 14:18:32 and the routes won't be set on the LRP 14:18:47 again, some else please double check this one 14:19:52 This week isabek is the bug deputy, next week will be elvira. 14:19:57 ok? 14:20:05 ok ralonsoh ! 14:20:09 on it 14:20:15 thank you 14:20:26 ok, let's move to the next topic 14:20:35 #topic specs 14:20:41 one active review 14:20:51 #link https://review.opendev.org/c/openstack/neutron-specs/+/870030 14:21:00 approved last drivers meeting 14:21:12 so please (including myselft), check this spec 14:21:23 will do today 14:21:39 thank you 14:21:56 next topic 14:22:03 #topic community_goals 14:22:11 1) Consistent and Secure Default RBAC 14:22:23 I'll post here all the bugs related opened by slaweq 14:22:35 #link https://bugs.launchpad.net/neutron/+bug/2004017 14:22:41 #link https://bugs.launchpad.net/neutron/+bug/2004016 14:22:47 #link https://bugs.launchpad.net/neutron/+bug/2004015 14:22:52 #link https://bugs.launchpad.net/neutron/+bug/2004014 14:22:58 #link https://bugs.launchpad.net/neutron/+bug/2004013 14:23:03 #link https://bugs.launchpad.net/neutron/+bug/2004012 14:23:10 slaweq, something you want to add here? 14:23:18 no 14:23:27 stacktraces are in bug reports 14:24:05 it can be easily reproduced locally if someone wants to check and fix some 14:24:21 please, if you start working on one of these bugs, assign it first to yourself 14:24:23 if will be working on them and assigning myself to them one by one in next days/weeks 14:24:46 ralonsoh++ exactly - if LP will be assigned to someone, I will simply take another one 14:24:59 so please assign to Yourself to avoid work duplication 14:25:10 we should have them fixed ASAP, better before A-3 (2 weeks) 14:25:17 ack 14:25:21 slaweq, thanks for taking care 14:26:14 next one is 14:26:14 yw 14:26:21 2) Neutron client deprecation 14:26:38 the most urgent patch should be https://review.opendev.org/c/openstack/neutron-lib/+/870582 14:26:47 that is in n-lib 14:27:05 sorry, not related 14:27:06 you mean for review? 14:27:06 yeah it is not for me :-) 14:27:22 some news for the neutronclient things: 14:27:52 the SDK merged BGP and taas code, so in neutroncleint we can use that if it will be released 14:28:18 by the way SDK will be 1.0.0 with the new release (https://review.opendev.org/c/openstack/releases/+/872206 ) 14:28:28 nice! 14:28:35 and python-neutronclient merged trunk code 14:28:54 so some progress with it 14:29:28 I think that's it now, I have to go back and prepare the next wave :-) 14:29:49 thanks a lot lajoskatona 14:30:48 ok, let's jump now to the next topic 14:30:52 #topic on_demand 14:30:59 1st topic is from elvira 14:31:02 please, go on 14:31:07 Yes, thanks. 14:32:02 Basically, RDO team contacted me to see if we could make proactive bumps on the libraries that we need on the RDO neutron-distgit repository, so that we don't make the gates fail 14:32:51 do you have a manual for this? what should be done? 14:32:52 They had this problem with the last pyroute2 bump 14:32:58 how was that? 14:33:13 this pyroute2 version was in fact used by Neutron already 14:33:25 Yes, I asked them 14:33:34 Slawek Kaplonski proposed openstack/neutron master: [Secure RBAC] Allow network owner to delete ports plugged to the network https://review.opendev.org/c/openstack/neutron/+/872280 14:34:00 "One way to manage that is to send a patch to neturon distgit setting the minimal required version to what you will need. The review will fail because we don't have it in rdo. The review would fail but that would warn us aboutupdating it on Fedora and follow the workflow" 14:34:46 That's what they said. Which I assume is changing the minimum versions for the library in this file: https://github.com/rdo-packages/neutron-distgit/blob/rpm-master/openstack-neutron.spec 14:35:16 That way they can proactively ask Fedora for an update on their packages 14:36:06 elvira, I would ask you to collect the information, provide some examples (some gerrit patches) and send an email to the mailing list (or give me this info and I'll send it) 14:37:03 ok! I will do it and check with you before sending the email if that is ok o/ 14:37:14 perfect 14:38:01 Just in case anyone is curious, this is their workflow for requirements: https://www.rdoproject.org/documentation/requirements/ 14:39:23 the next topic is SQLAlchemy 2.0 14:39:27 (sorry for that!) 14:39:41 we are bumping the version in requirements 14:39:45 and everything is broken 14:39:53 I've opened some bugs 14:40:04 these are the patches 14:40:09 #link https://review.opendev.org/c/openstack/neutron/+/872271 14:40:14 #link https://review.opendev.org/c/openstack/neutron-lib/+/872272 14:40:20 #link https://review.opendev.org/c/openstack/neutron/+/744512 14:40:42 and the last one is a proposal for adding a sqlalchemy master branch job 14:40:45 well, jobs 14:40:49 #link https://review.opendev.org/q/topic:bug%252F2004265 14:41:16 I hope that with this ^^^ we won't have those surprises again 14:41:50 (please review these patches) 14:41:53 and that's all I have 14:42:00 do you have any other topic? 14:43:04 ok, folks, remember that we have the CI meeting in 17 mins 14:43:09 see you later 14:43:14 #endmeeting