13:00:16 #startmeeting networking 13:00:16 Meeting started Tue May 13 13:00:16 2025 UTC and is due to finish in 60 minutes. The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:16 The meeting name has been set to 'networking' 13:00:24 Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, haleyb, ralonsoh, sahid 13:00:30 hello all 13:00:36 o/ 13:00:39 \o 13:00:39 o/ 13:00:40 o/ 13:00:53 o/ 13:01:12 \o 13:01:27 let's start 13:01:40 #topic announcements 13:01:46 #link https://releases.openstack.org/flamingo/schedule.html 13:01:47 o/ 13:01:52 we are in R20 13:02:01 that means flamingo-1 milestone 13:02:37 a heads-up about the Neutron drivers meeting 13:02:42 o/ 13:02:42 the agenda is here: https://wiki.openstack.org/wiki/Meetings/NeutronDrivers 13:02:55 if you want to add any topic, please do it before this Friday 13:03:07 o/ 13:03:12 o/ 13:03:23 Bobcat is now unmaintained: https://review.opendev.org/q/topic:%22bobcat-stable%22 13:03:35 ralonsoh: nope, eoled 13:03:36 sorry, EOL 13:03:49 yes, I was writing that 13:04:23 and that's all I have, any other announcement? 13:05:07 ok, let's move on 13:05:09 #topic bugs 13:05:25 last report was done by mtomaska 13:05:29 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/MHNCBYOVZPJJS7IETORBQRTLDLJMBGKP/ 13:05:47 there are some unassigned bugs 13:05:56 #link https://bugs.launchpad.net/neutron/+bug/2110094 13:06:01 OVN AgentCache get_agents method filters agents incorrectly if hostname overlaps 13:06:16 well, not this one, I've proposed a patch today 13:06:17 sorry 13:06:29 #link https://bugs.launchpad.net/neutron/+bug/2110225 13:06:33 Floating IPs attached to Octavia LB VIPs are not reachable across routers using different external subnets (OVN + Octavia) 13:06:44 This one has been moved from Octavia to Neutron 13:07:00 yep. I am not sure if that is a bug to be honest 13:07:14 I didn't have time to reproduce the scenario 13:07:36 and maybe it could be done without deploying octavia 13:07:58 if I'm not wrong, it is adding an extra subnet to a GW network, right? 13:08:51 yes. the GW network (aka public) has two subnets and each subnet is connected to a router which is then connected to its own private network 13:10:08 ok, I need to spend sometime on this one 13:10:34 I know for sure there are some patches related to the presence of two subnets in the GW network in an OVN router 13:10:38 but I need to find them 13:10:57 in any case, has anyone time to check this bug? 13:11:05 Ill do it 13:11:11 mtomaska, thanks! 13:11:19 I'll ping you later with the related patches 13:11:22 ill setup the network they described 13:11:26 ack 13:11:44 next bug 13:11:50 #link https://bugs.launchpad.net/neutron/+bug/2110087 13:11:57 OVN log plugin merges log records from different log objects across projects 13:12:31 so basically, as written at the end: 13:12:32 I was not 100% sure what the reporter claims as the bug. But I think it is what I posted in my comment 13:12:37 "all log entries are being attributed to only one of the Neutron log objects, despite being from different security groups and different projects/domains" 13:12:56 I.e. we group all logs under the same "neutron object" in the ovn-controller log. 13:13:53 so you tried pinging from vm-a to to vm-b 13:14:00 both with different SGs, right? 13:14:03 yes 13:14:11 and the logs are always associated to one SG 13:14:28 they got associated to object "neutron-fd9caf20-08b6-40e1-bde8-c33aee1f675a" 13:14:40 that is SGa 13:14:40 which is wrong... and I think that is the core of this bug 13:15:09 right, I think that deserves a question in the ovn mailing group 13:15:25 yes in this case. What I saw is that it will always be the first uuid of the first neutron object name 13:16:08 ^ that seems wrong 13:16:14 qq: when should we see logs from the other SG? 13:16:51 IDK :) . I dont know too much about this feature to tell what is wrong and what is right :) 13:16:53 because I see no logs related to the ping in the other direction 13:17:07 elvira, maybe you can check this one first? 13:17:08 I'll talk to elvira 13:17:11 right 13:17:13 right 13:17:13 could this be an information leak? i.e. is this a security issue? 13:17:25 it doesn' 13:17:35 doesn't look like a security issue 13:17:38 but a lack of logging 13:17:40 sure, I can take a look 13:17:44 frickler I dont think so. After all, only admins should have access to ovn-controller.log, right? 13:18:11 elvira: let discuss offline. Maybe a quick video call or something 13:18:20 mtomaska: ah, right 13:18:33 cool, thanks, let's talk about this one offline 13:18:51 the last one is 13:18:55 #link https://bugs.launchpad.net/neutron/+bug/2110306 13:18:56 Note that dropped traffic will be logged for all sec groups since we have that traffic being monitored by the general drop acl 13:19:01 will continue offline :) 13:19:14 [RFE][OVN] subnet onboarding is not supported 13:19:26 so this is a RFE 13:19:31 seems like a decision for RFE to me. 13:19:49 hmmm 13:20:00 maybe is just a matter of adding the extension to OVN 13:20:19 becauseI think this is only API related 13:20:21 (I think) 13:20:40 what is really subnet onboarding? :) 13:20:52 "The subnet onboard feature allows you to take existing subnets that have been created outside of a subnet pool and move them into an existing subnet pool. " 13:21:15 it changes the address scope, so maybe OVN will have to do something? 13:21:16 https://docs.openstack.org/neutron/latest/admin/config-subnet-onboard.html 13:22:33 frickler, yeah, that maybe would need some driver interaction, not just API actions 13:22:44 ok, I'll check it after the meeting 13:23:06 if this bug requires any kind of driver interaction, that will be a RFE for sure 13:23:25 otherwise, it will be just a oneliner patch 13:23:33 ack 13:23:51 and that's all I have 13:23:57 any other bug you want to discuss? 13:24:37 and the "winner" this week is bcafarel, next week will be elvira 13:24:40 ack? 13:24:43 ack 13:24:58 what is the winning prize? :) 13:25:06 (and also ack for this week) 13:25:15 spend wonderful time reviewing launchpad... 13:25:33 bcafarel: 10+ bugs assigned 13:25:53 ok, let's move to the next topic 13:26:04 #topic community-goals 13:26:15 the first one is the Neutronclient deprecation 13:26:18 lajoskatona, any update? 13:26:36 nothing this week 13:26:47 I pinged hoeirzon team, thats all 13:26:53 link to any patch? 13:26:55 horizon 13:27:10 https://review.opendev.org/c/openstack/horizon/+/946269 13:27:18 cool thanks! 13:27:24 to go back to fullstack I had no time 13:27:41 FYI: https://review.opendev.org/c/openstack/neutron/+/947851 13:28:03 ah yes, complex one 13:28:47 the next one goal is the eventlet removal 13:29:07 I've pushed a new patch this week, related to the L3 agent LP 13:29:10 #link https://review.opendev.org/c/openstack/neutron/+/949135 13:29:11 the bigest proble is tha I have no idea how to do no-auth connection with SDK, and seems it is not easy and known by somebody 13:29:53 lajoskatona, this? 13:29:53 https://review.opendev.org/c/openstack/neutron/+/947851/1/neutron/tests/fullstack/resources/process.py 13:30:08 yes, exactly 13:30:22 but sorry go ahaead with eventlet, that's i t from me for SDK 13:30:49 lajoskatona, qq: did you bring this topic to any team meeting? 13:30:57 slaweq, ^ could be in TC? 13:31:21 ralonsoh: you mean the SDK vs no-auth question? 13:31:37 sorry, not TC, SDK 13:31:43 ralonsoh I am not in TC anymore and didn't attend meetings recently 13:31:51 sorry, not TC, my bad 13:31:57 I asked on SDK channel, but plan to ask more to see if it is possible at all 13:32:00 frickler should know better maybe 13:32:19 I also only know that it seems to be difficult 13:32:41 but that was possible with neutronclient 13:33:03 we call that progress usually (sorry just sarcasm....) 13:33:12 hahahaha 13:33:49 maybe, just for testing, I would be needed to implement this in SDK 13:34:02 I'll ping stephenfin after this meeting 13:34:07 I run another round with SDK people, how should we progress with it 13:34:28 thanks, I had a chat with gtema last week, or before about this 13:34:52 ok, about the L3 patch (https://review.opendev.org/c/openstack/neutron/+/949135). Just a bit of context: 13:35:40 it is described in the commit message. With the oslo.service threading backend (patch under review), the service (l3 agent) is forked in the start method 13:35:59 any object created in the init method will be forked too 13:36:06 but RPC clients doesn't like this 13:36:25 I've moved all the RPC client initialization to the init_host method, that is called from Service.start() 13:36:47 that patch MUST work with both backends (in the CI is working now with eventlet) 13:37:03 in the upper patch is working with theading backends 13:37:06 that's all 13:37:30 any other comment? 13:37:41 thanks ralonsoh, I check this one, I played also with dhcp-agent and the oslo.service patch 13:37:52 yeah, that will need exactly the same 13:37:56 but just locally at the moment 13:38:05 to move all RPC clients to the init_host methods 13:38:25 I was able to start the agent with it, with some exceptions, but will check yours of course 13:38:35 did you use the oslo.service patch? 13:38:41 yes, I did 13:38:47 cool! 13:39:03 it seems that we'll have it soon in a new oslo.service release 13:39:10 that will be easier for testing 13:39:29 +1 13:39:37 ok, let's move to the last topic 13:39:42 #topic on-demand 13:39:51 anything you want to add? 13:40:47 Ok, I'm closing the meeting for today. Thank you all for attending! 13:40:53 #endmeeting