14:01:06 #startmeeting networking 14:01:07 Meeting started Tue Apr 11 14:01:06 2023 UTC and is due to finish in 60 minutes. The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:07 The meeting name has been set to 'networking' 14:01:08 o/ 14:01:10 hi all 14:01:11 o/ 14:02:10 ok, let's start 14:02:14 #topic announcements 14:02:40 we have a new schedule 14:02:45 #link https://releases.openstack.org/bobcat/schedule.html 14:02:50 o/ 14:03:09 \o 14:03:25 so please check the dates and get used to this new cycle 14:03:28 and welcome, of course 14:03:42 also please remember the Vancouver etherpad 14:03:45 #link https://etherpad.opendev.org/p/neutron-vancouver-2023 14:04:28 let me be honest: we need more topics and attendands 14:04:47 I know during the vPTG we had a packed agenda 14:04:51 and we discussed many topics 14:05:27 but if the agenda of vancouver doesn't grow, I don't think I'll attend (I'll be able to) 14:05:57 and if you missed that last wee 14:05:59 week 14:06:02 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033115.html 14:06:29 something else? 14:06:54 ok, let's jump to the funny topic 14:06:58 #topic bugs 14:07:02 we have two reports 14:07:07 one from mlavalle2 14:07:11 https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033184.html 14:07:20 and the next one from rubasov 14:07:24 https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033279.html 14:07:37 there are some pending/not assigned bugs 14:07:46 #link https://bugs.launchpad.net/neutron/+bug/2013326 14:07:56 slaweq, ^^ is this one related to policies? 14:08:01 srbac? 14:08:31 yes 14:08:41 ok perfect, will you assign it yo you? 14:09:15 I'll do it, yes 14:09:20 yes, thx 14:09:23 thanks! 14:09:24 next one 14:09:40 #link https://bugs.launchpad.net/neutron/+bug/2012332 14:09:44 this is a RFE 14:09:59 I've added it to the drivers agenda next friday 14:10:11 but I hope Liu takes it, I'll ping him 14:10:21 ok, next one 14:10:34 #link https://bugs.launchpad.net/neutron/+bug/2015065 14:10:51 this one is not 100% happening but very very often 14:12:07 and if I'm not wrong, is always failing in the same point 14:12:15 only in grenade? 14:12:17 during the SG creation 14:12:18 yes 14:12:22 only in this job 14:12:31 interesting 14:12:49 yes, I believe it's always failing the same way 14:13:16 I can check it 14:13:32 cool, thanks a lot (my agenda is full this week, sorry) 14:13:49 next one 14:13:51 #link https://bugs.launchpad.net/neutron/+bug/2015364 14:13:55 related to grenade too 14:14:07 this time the -skip-tests, only in OVN 14:14:33 these 4 jobs (actually 3 plus a class) are always failing 14:15:39 are we installing a different version of OVN? I think so 14:16:39 ok, I'll check them with ykarel if he has time 14:16:54 sure i can check this issue 14:16:57 or I'll ping infra folks to stop an env once failed 14:17:05 I appreciate that, thanks! 14:17:07 but yes looks like something wrong with ovn version 14:17:28 that's what I think (but I can't support with facts what I'm saying) 14:17:36 ack i will dig 14:17:46 these are passing in OVS (and we are executing the same test set) 14:18:16 ok, next one is 14:18:19 #link https://bugs.launchpad.net/neutron/+bug/2015449 14:18:31 frickler, can you provide some update on this one? 14:19:08 well it sounds like intra-subnet traffic may be natted by ovn to the FIP attached to an instance 14:19:22 I had no reproduction yet, but I was unsure about whether we consider the described behavior a bug or an unfortunate undocumented behavior 14:19:30 but somebody will need to try to reproduce that I guess 14:19:35 that was my first question: ovs or ovn 14:19:49 so OVN, I'll make a comment in the bug 14:19:54 by the way I will follow up on the bugs in the "triage in progress" section in my report 14:20:04 no need to take over from the next deputy 14:20:11 thanks 14:20:20 oh, I was assuming ovn, but maybe not 14:20:31 I'll ask that in the BZ 14:20:44 and in case of OVS, what FW driver 14:21:17 ok, once replied, I'll try to reproduce it 14:21:25 for me, as noted in the last comment, fw behavior seems correct, just natting shouldn't happen 14:21:41 yeah, looks like 14:22:10 ok, once we have the answer, I'll deploy an env and reproduce it 14:22:35 also ask for ovn/ovs versions 14:22:53 sure 14:23:08 ok, and the last one I have is 14:23:10 #link https://bugs.launchpad.net/neutron/+bug/2015275 14:23:21 I added a comment today 14:23:35 related to why the RPC is attended in just one worker 14:23:55 this is a problem of how it was designed 14:24:15 so it will require a proper refactor 14:24:36 does anyone have time/energy/will to do it? 14:25:08 ok, I'll assign it to myself 14:25:34 ok, and that's all for today 14:25:36 ralonsoh: you can assign it to myself 14:26:05 sahid, perfect, this is not a trivial refactor 14:26:22 thanks for that 14:26:40 sure i think it will be interesting to look in that part of the code 14:26:58 ok, this week I'm the bug deputy 14:27:05 next week is lucasagomes 14:27:27 btw, do we have new volunteers to be added to the deputy list? 14:27:39 as commented during the PTG 14:27:52 you can take your time and ping me in IRC at any time 14:28:01 check https://wiki.openstack.org/wiki/Network/Meetings 14:28:24 let's move on 14:28:29 ralonsoh: please add me on it 14:28:35 I'll do it 14:28:38 ok 14:28:42 we don't have new specs 14:28:47 nor os-ken issues 14:29:03 so we can jump to the next topic 14:29:11 #topic community_goals 14:29:30 about sRBAC, I don't think slaweq has any new 14:29:38 actually I have 14:29:42 sorry! 14:29:52 last week I started working on switch to new policies by default 14:30:23 I sent patch: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/879828 14:30:29 and WIP https://review.opendev.org/c/openstack/neutron/+/879827 14:30:50 that last one is going to be a lot of work as there is still almost 2k of UT failing there :/ 14:30:54 but I'm working on it 14:31:15 during debugging of those failed UT I found out small issue in new policy for get_ports 14:31:24 and I sent fix https://review.opendev.org/c/openstack/neutron/+/879891 14:32:10 "test_port_list_queries_constant" still failing 14:32:11 and this is now puzzling me as 2 UT are failing there 14:32:12 this failure is somehow related to that patch 14:32:13 but I have no idea how 14:32:13 and if I run only that one test locally, it is passing 14:32:24 ralonsoh maybe we can talk about this failing test later offline? 14:32:39 yeah, I'll check them today (or tomorrow morning) 14:32:52 thx 14:33:01 and that's my update about S-RBAC for this week 14:33:25 thanks, I'll add these patches to the meeting agenda 14:33:29 to track them 14:33:57 next one is 14:34:04 2) Neutron client deprecation 14:34:22 lajoskatona, any new topic? 14:34:22 The usual etherpad: https://etherpad.opendev.org/p/python-neutronclient_deprecation 14:34:30 not much 14:34:56 designate seems to be finished, and octavia is slowly progressing (not me who works on it 14:35:27 do you have any pending patch in SDK or OSC? 14:35:29 and sahid started to check how nova can be changed to use sdk 14:35:49 https://review.opendev.org/q/topic:bug/1999774+status:open 14:36:15 these are for neutronclient, but to change the current cli code to use sdk only 14:36:20 ok 14:36:26 I have small update related to this one too. I spent today some time checking ralonsoh's patch https://review.opendev.org/c/openstack/python-neutronclient/+/871711 and I finally made it to be green in CI. So maybe we will be able to finally get rid of "neutron" CLI tool in this cycle 14:37:20 slaweq: you mean to remove all code that is realted to core Neutron CLI? 14:37:22 but ps7 is not removing the CLI code? 14:37:32 lajoskatona not all code really 14:37:52 but at least remove some of bits related to CLI tool and "neutron" command 14:38:06 and to not provide this CLI tool, bash completion and other related things at all 14:38:14 yeah, at least the shell class 14:38:16 so users will not have "neutron" command available anymore 14:38:44 we can't remove some nclient modules (still used by many other projects) 14:38:47 parts from neutronclient/neutron/v2_0 needs to be still there as e.g. nova is using it 14:38:52 but I'm ok removing the shell class 14:38:53 I will check it, as I see it also removes some unit tests related to bgp for example but that code remains in neutronclient 14:39:04 but shell.py and everything what depends on it can be removed probably 14:39:23 yeah that can be removed (theoretically :P) 14:39:32 and all FT/UT related 14:39:37 lajoskatona yes, it removes most of the UT as those tests were importing shell.py module 14:39:48 and those are "CLI" tests really 14:40:03 ok, I will check it 14:40:07 thx 14:40:53 I need to check again if I sent the mail to make this public 14:41:10 It was years ago but again as a heads-up 14:41:18 ok, please check this patch 14:41:20 and thanks slaweq 14:41:44 and that's all in this topic 14:41:48 ++ thx a lot 14:42:02 next one 14:42:06 #topic on_demand 14:42:11 lajoskatona, you have a topic there 14:42:13 2 actually 14:42:47 yes, I added here as reminder as we discussed the PTG to list some forum topic ideas 14:43:02 that is the first one 14:43:42 so if you have forum ideas which can be discussed during the Vancouver summit/PTG please .... 14:44:34 I have one but perhaps that is not worth a whole forum: to discuss the deprecation of Neutronclient 14:44:59 this whould not be interesting for users, but for deveopers of other projects it can be interesting 14:45:07 I need to check with slaweq (I didn't have time) some suggestions he has 14:45:55 in any case we still have time to add more topics 14:46:13 the second one is related to Xena release 14:46:14 https://review.opendev.org/c/openstack/releases/+/878874 14:46:23 I've updated (wrongly) the patch 14:46:35 note: for a EM branch, it is needed a new release 14:46:44 there is one missing patch for Neutron 14:46:55 yeah just a headsup that Xena is planned to EMed soon 14:46:59 that was +W by slaweq 14:46:59 https://review.opendev.org/c/openstack/neutron/+/879330 14:47:18 so I think we'll be able to push a final releases patch tomorrow morning 14:47:40 last day is 20th of April 14:48:03 but as commented, tomorrow I'll push the patch that should be the one accepted 14:48:09 and that's all for today 14:48:11 cool, thanks 14:48:16 remember the CI meeting is in 10 mins 14:48:27 video or irc? 14:48:28 do you have any other topic? 14:48:31 thx ralonsoh 14:48:35 it's irc this week 14:48:38 cool 14:48:39 ack 14:48:43 ack 14:49:04 so thank all 14:49:07 #endmeeting