14:01:04 #startmeeting networking 14:01:04 Meeting started Tue Apr 18 14:01:04 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:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:04 The meeting name has been set to 'networking' 14:01:05 Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, sahid, slawek, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki 14:01:05 o/ 14:01:09 o/ 14:01:09 o/ 14:01:15 o/ 14:01:16 o/ 14:01:17 hello all 14:01:20 o/ 14:01:38 o/ 14:01:40 o/ 14:02:09 ok, I think we can start now 14:02:10 o/ 14:02:14 #topic announcements 14:02:19 #link https://releases.openstack.org/bobcat/schedule.html 14:02:35 in 3 weeks, we'll have the bobcat-1 milestone 14:02:49 and in 2 months the Vancouver summit! 14:03:29 I would like to refresh the link for the summit 14:03:32 #link https://etherpad.opendev.org/p/neutron-vancouver-2023 14:03:53 of course, as usual, please check the openinfra videos 14:03:56 #link https://openinfra.dev/live/#all-episodes 14:04:20 and finally, the oslo.db 13.0.0 release 14:04:22 #link https://review.opendev.org/c/openstack/releases/+/880659 14:04:28 yatin proposed openstack/neutron master: [DNM] check 880586 https://review.opendev.org/c/openstack/neutron/+/880704 14:04:34 that should have full support for sqlalchemy 2.0 14:04:41 so just a heads-up 14:04:52 is that already bumped in requirements? 14:04:56 not yet 14:05:00 ok, thanks 14:05:17 but here is the link 14:05:18 #link https://review.opendev.org/c/openstack/requirements/+/880729 14:05:34 (and Neutron is not failing) 14:05:43 but remember this is not bumping sqlalchemy 14:05:51 only oslo.db with support for 2.0 14:06:11 ack, thanks for the headsup 14:06:16 something else I'm missing here? 14:06:54 ok, let's move on 14:06:57 #topic bugs 14:07:10 last week I was the bug deputy 14:07:14 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033393.html 14:07:24 and there are some bugs to be discussed/assigned 14:07:40 #link https://bugs.launchpad.net/neutron/+bug/2016413 14:07:53 I think this is a low hanging fruit one 14:07:56 I'll add the tag 14:08:24 so please check it if you want to collaborate with documentation 14:08:49 next one is 14:08:54 #link https://bugs.launchpad.net/neutron/+bug/2016198 14:09:03 that is related to https://bugs.launchpad.net/neutron/+bug/2016197 14:09:22 should we bring this topic to the drivers meeting? 14:09:53 it's a bug, isn't it? 14:09:59 the first one yes 14:10:15 but the suggestion is to limit the port creation in a network without subnets 14:10:23 ahh, 14:10:25 that I don't think should be done because of a race condition 14:10:27 I get it 14:10:57 so LP#2016198 should be addressed, but LP#2016197 should not be the solution 14:11:05 IMO 14:11:07 let's discuss it during the drivers meeting 14:11:15 I'll move this topic then 14:11:20 ok, thanks 14:11:24 last one is 14:11:26 yes, that's probably a good idea 14:11:28 #link https://bugs.launchpad.net/neutron/+bug/2015844 14:11:44 in a nutshell, OpenStack is removing windows support 14:12:07 this code is not tested in the CI 14:12:08 regarding recent discussion about winstackers project that it will be gone I think we should remove completely this windows bits from neutron 14:12:36 first deprecate and then remove? 14:12:38 but we should probably follow deprecations policy so deprecate it in this cycle 14:12:42 perfect 14:12:48 if windows is not supported anmore no need to maintain all that code 14:12:49 and remove in 2024.2 at least 14:13:03 yes, that should be in 2 cycles 14:13:10 in D 14:13:13 ++ 14:13:16 +1 14:13:17 +1 14:13:22 we need to keep it deprecated for at least one SLURP release 14:13:28 which will be C in this case 14:13:28 +1 14:13:31 +1 14:13:36 I can deprecate it 14:13:38 +1 14:13:41 ok, decided, I'll comment that in the LP 14:13:50 slaweq, thanks, please propose the patches 14:13:57 I will propose patch, sure 14:13:57 and assign that to you 14:14:07 we can consider this LP closed with the deprecation 14:14:17 and in 1 year, we'll create a new one to remove the code 14:14:36 ++ 14:14:36 LOL, close a LP by removing the related code 14:14:52 yes, just to track it 14:14:56 mlavalle we should follow that practice more often :P 14:15:01 but I would prefer not to have this LP open 1 year 14:15:11 ok, that was fast 14:15:23 this week lucasgomes is the deputy, next week will be jlibosva 14:15:33 I know lucasagomes is aware 14:15:44 I'll ping Jakub next week 14:15:56 something else you want to discuss here? 14:16:08 yes, one more 14:16:38 https://ubuntu.com/security/CVE-2023-1668 14:16:44 this is a problem in OVS 14:16:52 I know there is a list of patches to fix that 14:17:09 and the mail from ovs-discuss 14:17:10 https://www.openwall.com/lists/oss-security/2023/04/06/1 14:17:18 that is affecting ML2/OVS and ML2/OVN 14:17:52 well, I don't know if that is possible in OVN 14:18:00 but we can create this rule in OVS FW 14:18:16 in any case, this is a heads-up 14:18:44 ok, something else? 14:19:13 ok, I'll skip the spec reviewal as we don't have any active one 14:19:21 #topic community_goals 14:19:28 1) Consistent and Secure Default RBAC 14:19:39 #link https://review.opendev.org/c/openstack/neutron/+/879827 14:19:51 I think we don't have active bugs, slaweq ? 14:20:09 nothing new this week 14:20:20 btw, https://review.opendev.org/c/openstack/neutron/+/880461/ 14:20:24 I'm still working on patch https://review.opendev.org/c/openstack/neutron/+/879827/ 14:20:28 is failing in neutron-tempest-plugin-openvswitch-enforce-scope-new-defaults 14:20:42 yes, this is the 4th patch of the series 14:20:47 but is failing the 1st 14:20:54 ohh, I will need to check it 14:21:15 ok, I think this is just a red herring 14:21:22 it failed because of issue with installation of packages 14:21:24 something with the mirrors, nothing else 14:21:26 yes 14:21:31 nothing relevant to patch itself 14:21:33 (much better) 14:21:46 fingers crossed 14:21:54 so we are almost ready to merge the sRBAC by default in Neutron 14:22:02 and main patch to enable new policies by default is almost there, just about 300 UT to fix still 14:22:09 and 200 FT 14:22:26 nahhh almost nothing... 14:22:31 (ping for help if needed) 14:22:54 but once all that will be done, we will also have a bit better coverage of policy testing in UT as all such tests will make API requests with proper context 14:23:01 not without context at all 14:23:32 so we need to review all UTs to use the proper context? 14:23:39 I will definitely bother You all with review requests once it will be green 14:23:46 perfect 14:24:01 ralonsoh not all but many which are using api to e.g. create resources 14:24:08 like many tests for extensions 14:24:13 or ml2 plugin 14:24:16 or db modules 14:24:34 I'm on it and it's high priority for me to finish it ASAP 14:25:00 thank you 14:25:21 thanks slaweq 14:25:42 ok, the second topic is 14:25:45 2) Neutron client deprecation 14:25:51 I 've identified 3 active patches 14:25:59 #link https://review.opendev.org/c/openstack/python-neutronclient/+/880629 14:26:04 #link https://review.opendev.org/c/openstack/python-neutronclient/+/875728 14:26:09 yes, I started to work on fwaas CLI 14:26:10 #link https://review.opendev.org/c/openstack/python-neutronclient/+/868321 14:26:31 880629 is wip (this is for fwaas) 14:27:03 so we have the OSC/SDK code merged for fwaas? 14:27:04 the patch for octavia is also in good shape: https://review.opendev.org/c/openstack/octavia/+/866327 (thanks octavia team) 14:27:28 ralonsoh: yes it is already done (https://review.opendev.org/c/openstack/openstacksdk/+/592303  ) 14:27:35 perfect 14:28:00 so if yo have time you can even check the octavia patch 14:28:14 ^^ fantastic the patch in octavia, good to see traction outside Neutron team 14:28:35 agree, we had the same good example from designate 14:29:06 that's it from me for the neutronclient topic 14:29:12 thanks! 14:29:23 and that's all! 14:29:27 #topic on_demand 14:29:40 I have one topic but was discussed in the bug section 14:29:54 so please, if you have something, this is the moment 14:30:24 I wanted to ask people about ideas for forum sessions in vancouver 14:30:36 do You have any ideas what we can propose there? 14:31:25 the forum proposals ends this Friday 14:31:34 not sure but the RBAC as default would be interesting even for operators 14:31:46 actually it is 14:31:53 that was a request from operators 14:31:58 lajoskatona but what You want exactly discussing regarding RBAC? 14:32:33 yeah, maybe this is a topic for a presentation, not a forum 14:32:37 what kind of new personas they have to use and what can be expected? things like that 14:33:05 but presentation proposal is closed :-) so we have the forum only now >/( 14:33:06 a general operators feedback session? 14:33:20 lajoskatona but this actually is something broader than Neutron only thing 14:33:30 so maybe S-RBAC team will propose some session 14:33:37 ok 14:33:53 mlavalle: that can be interesting anytime I suppose 14:33:59 I don't think we should have any neutron specific discussion about it with operators, at least not something for separate session 14:34:00 yeap 14:34:22 and this would be the first time face to face in a long time 14:34:25 mlavalle yes, I was also thinking about "general feedback session" 14:35:01 another one might be discussion on scalability issues 14:35:03 and ask operators about what features/plugins/drivers they are using, what are their pain points, etc. 14:35:23 +1 14:35:55 and my idea was to ask operators question like "If You could choose one thing which will be fixed in Neutron, what it would be" to see if there would be any pattern there, maybe all of them needs the same thing to be there :) 14:36:13 ^^ right 14:36:31 yes, we can start with a menu of teaser questions and then see where the discussion goes 14:37:23 to uncover pattersn, as you say slaweq 14:38:04 ok, tomorrow we'll present, in this channel, some proposals 14:38:11 and then you'll approve then or not 14:38:17 and then we'll register them 14:38:25 ok? 14:38:32 sounds good 14:38:35 ++ 14:38:40 we are running out of time and we need to ground something 14:38:43 perfect then 14:38:51 what time? don't forget us, the ones on this side of the pond 14:39:03 of course, at this time more or less 14:39:16 say around 1400 utc? 14:39:25 ok 14:39:28 cool 14:39:32 good time for me 14:40:09 lajoskatona, rubasov o/ 14:40:20 ok, I think that's all for today 14:40:29 quick question regarding https://review.opendev.org/c/openstack/neutron/+/872905/15 14:40:42 oh sorry i think the meeting was finished :-) 14:40:47 not yet 14:40:49 one sec 14:41:04 please remember the CI meeting is in 20 mins in this channel 14:41:10 #endmeeting