14:05:06 #startmeeting networking 14:05:06 Meeting started Tue Mar 14 14:05: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:05:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:05:06 The meeting name has been set to 'networking' 14:05:07 o/ 14:05:22 o/ 14:05:22 ping bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, sahid, slawek, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki 14:05:46 ok, I think we start 14:05:54 #topic announcements 14:05:58 o/ again 14:06:20 #link https://releases.openstack.org/antelope/schedule.html 14:06:44 during this week we'll propose the final RCs for the projects 14:06:46 late o/ 14:06:59 maybe today or tomorrow we'll have the releases patches in gerrit 14:07:17 please check anything needed for 2023.1 and propose a backport if necessary 14:07:36 +1, and happy new release :-) 14:08:11 as usual, a reminder that the PTG is in 10 days 14:08:20 the etherpad is https://etherpad.opendev.org/p/neutron-bobcat-ptg 14:08:34 please add any relevant topic 14:08:58 tomorrow I'll add those related to the TC resolutions, CI topics and SQLAlchemy 14:09:05 and other new features to be proposed 14:09:15 next week we'll schedule the room calendar 14:09:17 ralonsoh: can we merge code again? 14:09:26 mlavalle, we never stopped 14:09:31 ok 14:09:48 #link https://ptg.opendev.org/ptg.html 14:10:15 today I'll send a voting poll to decide what are the most suitable hours for us 14:10:44 same as other projects, the goal is to plan everything from tuesday to friday 14:10:57 leaving monday for TC 14:11:05 +1 14:11:40 and June PTG ("PTG, the revenge") 14:11:43 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032523.html 14:12:18 I need to know what sessions are we going to schedule during the Vancouver PTG 14:12:35 in order to register Neutron project and schedule the rooms 14:12:58 we can also discuss this during the virtual PTG, but please be aware 14:13:27 We are still waiting for the travel approval, so not sure if we can travel (I mean rubasov and myself) 14:13:39 I know this is a big stopper 14:13:43 I'm aware of this 14:14:24 ok, something else I'm missing? 14:14:47 last reminder: today we don't have CI meeting 14:15:03 ok, let's move to the next topic 14:15:07 #topic bugs 14:15:23 we don't have a summary this week 14:15:44 but I have the links of the bugs currently not assigned and opened during the last week 14:15:55 #link https://bugs.launchpad.net/neutron/+bug/2009705 14:16:32 to be honest, I don't have the knowledge to debug this 14:16:55 but I'll ping zhouhenglc if he can assign and investigate this issue 14:17:23 ok, next one 14:17:27 #link https://bugs.launchpad.net/neutron/+bug/2009807 14:17:27 zhouhenglc already commented on the bug so sounds good idea 14:17:39 yeah 14:17:55 but he couldn't reproduce it 14:18:09 so maybe this is not a bug or the reproducer steps are not correct 14:18:38 I have summary of bug reports almost ready. But as I was off yesterday and today I forgot to send ot 14:18:41 I will send it later today, sorry for that 14:18:53 slaweq, no problem, we are discussing the bugs not assigned 14:19:00 opened during the last week 14:19:26 ok, let's move to the next one 14:19:31 #link https://bugs.launchpad.net/neutron/+bug/2009807 14:20:06 IMO, the user is don't something wrong or is not describing one step 14:21:05 please, check if that rings you a bell, but I think the user is already using this provider network 14:21:11 sorry 14:21:13 physical network 14:22:01 anyway, we should wait for more information from the reporter 14:22:21 the next two bugs are low hanging fruits ones 14:22:26 #link https://bugs.launchpad.net/neutron/+bug/2009832 14:22:32 #link https://bugs.launchpad.net/neutron/+bug/2009831 14:22:45 to correctly document the installation process 14:23:03 feel free to take them 14:23:28 and that's all I have 14:23:38 any other pending bug you want to discuss today? 14:24:18 btw, I think you read the mail related to the L3 agent fullsync problem 14:24:30 and how to detect that the agent is in this state 14:24:37 I created https://bugs.launchpad.net/neutron/+bug/2011422 14:24:43 but as a RFE 14:24:52 ralonsoh: i have a change up for this bug, https://bugs.launchpad.net/neutron/+bug/1988069 14:24:54 https://review.opendev.org/c/openstack/neutron/+/875809 14:25:02 Change API to validate network MTU minimums 14:25:23 any reviews are welcome, i don't think we need the other change(s) if we do that one 14:25:57 yeah, I think we discussed this before 14:26:11 but what happens if we are using other than IP traffic? 14:26:53 ralonsoh: if there are no subnets then we don't care about the mtu 14:27:19 but we set the MTU in the TAP device 14:27:53 well, this is only for L3 (so IP) 14:29:05 ok, any other bug? 14:29:07 do you have an example of non-IP usage i can look at? this patch didn't change any of the mtu code in the drivers 14:29:17 or just comment in the bug :) 14:29:21 s/bug/patch 14:29:40 nova used the MTU to define the TAP 14:30:08 in any case, this is a corner case and I think we can tunnel this kind of traffic 14:30:44 This week haleyb is the deputy, next week will be amotoki. 14:31:03 ralonsoh: ack 14:31:26 MTU here is max payload size for ethernet on a virtual network, so MTU is needed even for non-IP network in theory (though I don't know a real use case example) 14:31:40 * to define a tap device 14:33:01 I need to refresh that, MTU is related to IP, not the frame size 14:33:08 but anyway, we can review that in the patch 14:33:38 yeah 14:33:42 ok, let's move to the next topic 14:33:49 #topic community_goals 14:33:54 1) Consistent and Secure Default RBAC 14:34:18 #link https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/874709 14:34:24 is still failing 14:34:34 but slaweq commented this is because of the n-lib version 14:34:51 once we have the latest one, that should pass 14:34:59 the release patch for Zed (one sec) 14:35:33 #link https://review.opendev.org/c/openstack/releases/+/876835 14:35:34 cool 14:35:38 merged 2 hours ago 14:35:47 so I'll recheck that patch again 14:36:12 that's that last bit needed for sRBAC in Zed (I hope so) 14:36:27 fingers crossed 14:36:51 hehehe I think there is just one little problem with one n-lib call 14:37:02 you'll need the u-c bump first I think https://review.opendev.org/c/openstack/requirements/+/877367 14:37:05 this is why we have so many tests failing 14:37:16 yeah, I was checking that 14:37:32 and seems that CI is not happy with this patch 14:37:59 anyway, I'll check what is happening with n-lib 3.1.1 14:38:08 that seems more like a general zed issue for reqs 14:38:24 pkg_resources.extern.packaging.requirements.InvalidRequirement: Expected end or semicolon (after version specifier) 14:38:24 lesscpy>=0.9h 14:38:24 ~~~~~^ 14:38:30 weird 14:38:56 ok, maybe the problem is not in n-lib, after the meeting I'll check the status of this 14:39:41 that sounds familiar, I'll have a look, too 14:39:51 the issue is in "requirements/openstack_requirements/tests/files/gr-base.txt" 14:40:04 so that seems to be a testing problem 14:40:17 lesscpy is a dependency but not set in this patch: https://codesearch.openstack.org/?q=lesscpy&i=nope&literal=nope&files=&excludeFiles=&repos= 14:40:27 so really wird 14:40:32 weird ----^ 14:41:08 https://review.opendev.org/c/openstack/requirements/+/873620 14:41:17 seems need to backport that fix 14:41:29 perfect, that looks better 14:41:57 +1, thanks 14:42:27 https://review.opendev.org/c/openstack/requirements/+/877269 will see how that goes 14:42:44 but we'll need 2023.1 too 14:42:54 no 14:43:04 the patch was merged in 2023.1 14:43:18 cool, thanks! 14:43:43 ok, the next goal is 14:43:46 2) Neutron client deprecation 14:44:04 #link https://etherpad.opendev.org/p/python-neutronclient_deprecation 14:44:11 open patches: https://review.opendev.org/q/topic:bug/1999774+status:open 14:44:30 BGPVPN sdk and neutronclient patch is ready for review 14:44:35 ^^^ I swear I'll review all of them this weej 14:44:36 week* 14:44:54 thanks 14:45:06 please folks, add this link ^^^^ to your review piles 14:45:34 this is important: the less projects we have using nclient, the better for us in terms of code maintenance 14:45:41 I also asked gtema if he can join to our PTG to help in the discussion of this topic and have one eye from SDK/OSC point of view, and was happy 14:46:02 perfect, ask him for a day/hour 14:46:07 and we'll schedule it 14:46:10 so if we are closer to have a schedule I will ask ralonsoh to help in this 14:46:17 ralonsoh: ok, thanks 14:46:21 perfect 14:46:45 and that's all for today 14:46:50 #topic on_demand 14:46:53 I have one 14:46:57 related to the releases 14:47:04 Terry Wilson proposed openstack/neutron master: Only create a frozen Row on matching events https://review.opendev.org/c/openstack/neutron/+/877383 14:47:04 I you saw in the mail last week 14:47:20 I proposed new releases for Neutron projects for X, Y and Z 14:47:31 but my mistake was not to care of this more often 14:47:49 so every month, the first meeting we have 14:47:57 I'll raise this topic to your consideration 14:48:16 just to decide or not if there is a project/release that need to be proposed 14:48:29 that will take us some mins, no more 14:48:39 that's all from my side 14:48:40 good idea 14:49:03 do you have any topic you want to discuss today? 14:49:54 again, sorry for the delay and have a nice week! 14:50:00 #endmeeting