13:00:13 <haleyb> #startmeeting networking 13:00:13 <opendevmeet> Meeting started Tue Jun 3 13:00:13 2025 UTC and is due to finish in 60 minutes. The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:13 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:13 <opendevmeet> The meeting name has been set to 'networking' 13:00:14 <haleyb> Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, haleyb, ralonsoh 13:00:15 <mlavalle> \o 13:00:24 <obondarev> o/ 13:00:27 <ralonsoh> hello 13:00:29 <mtomaska> o/ 13:00:34 <bcafarel> o/ 13:00:38 <slaweq> o/ 13:00:50 <lajoskatona> o/ 13:01:12 <daidv> o/ 13:01:14 <haleyb> hi everyone let's get started 13:01:17 <haleyb> #announcements 13:01:28 <frickler> \o 13:01:30 <haleyb> We are currently in Week R-16 of Flamingo 13:01:37 <haleyb> Our next milestone in this development cycle will be Flamingo-2, on July 3rd 13:01:45 <haleyb> Final 2025.2 Flamingo release: October 3rd, 2025 13:01:51 <haleyb> #link https://releases.openstack.org/flamingo/schedule.html 13:02:02 <haleyb> Reminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers 13:02:10 <rubasov> o/ 13:02:52 <haleyb> That said, I am out this Friday and next Monday (high school graduation) so I was going to cancel drivers meeting for this week 13:02:52 <cbuggy> o/ 13:03:05 <ralonsoh> ok 13:03:39 <lajoskatona> ack 13:04:03 <opendevreview> Rodolfo Alonso proposed openstack/neutron stable/2025.1: Add provider network resources filter for "network" https://review.opendev.org/c/openstack/neutron/+/950324 13:04:17 <elvira> o/ 13:04:26 <haleyb> for those that were interested in OVN and BGP after the last drivers meeting, Frode did sent something to the ML regarding an in-person meeting for that. if interested please respond there 13:05:18 <haleyb> that was all i had for announcments, any others? 13:05:46 <haleyb> #topic bugs 13:05:56 <haleyb> slaweq was the deputy last week, his report is at 13:06:00 <haleyb> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/4GTKQGHIEZRHM4DFUHKUMBBJR6YL3HFO/ 13:06:11 <slaweq> It was pretty quiet week 13:06:39 <slaweq> But with relatively many new RFEs proposed 13:07:30 <haleyb> ack. The first two we discussed at last weeks drivers meeting i think 13:07:37 <slaweq> The only one which I would like someone to ask to check is https://bugs.launchpad.net/neutron/+bug/2111660 as I don't have env now to check it 13:07:45 * haleyb wonders if LP is down as he can't see the bugz 13:07:54 <ralonsoh> I did 13:08:03 <ralonsoh> the latest patch is working fine 13:08:08 <ralonsoh> https://review.opendev.org/c/openstack/neutron/+/950828 13:08:18 <slaweq> haleyb: LP seems to be down for me too now 13:08:37 <slaweq> ralonsoh: thx 13:08:39 <haleyb> it's slowly responding now 13:08:55 <slaweq> Other than that I think all is good from last week 13:09:21 <ralonsoh> the issue with Helm, maybe 13:09:27 <ralonsoh> https://bugs.launchpad.net/openstack-helm/+bug/2112130 13:09:40 <slaweq> Yeah. This one I think is on Helm team now 13:09:48 <ralonsoh> as haleyb pointed first, the code is incorrect in helm 13:09:57 <slaweq> I don't think this is an issue in neutron really 13:10:03 <ralonsoh> cool 13:10:07 <haleyb> ralonsoh: the only thing that might be useful from the neutron side is to make those LOG.info perhaps? 13:10:20 <haleyb> is it an error if we can't find the port? 13:10:56 <haleyb> but yes, helm needs to update their health check code 13:10:59 <ralonsoh> what logs? 13:11:04 <ralonsoh> neutron or helm? 13:11:28 <haleyb> ralonsoh: neutron. when we can't find the port we use LOG.error 13:12:03 <ralonsoh> but that's correct, I think 13:12:18 <slaweq> IMHO error is ok as this service is intended to be used by OpenStack VMs so we should expect that we will find the port 13:12:29 <ralonsoh> agree 13:13:36 <haleyb> ok. i would have voted for info or warning since there is nothing the cloud admin can do, or needs to do 13:14:16 <slaweq> maybe warning would be ok too 13:15:54 <haleyb> i will propose a quick patch for that, can vote on it there 13:17:00 <lajoskatona> +1 13:17:12 <haleyb> any other bugs to discuss? 13:18:21 <haleyb> i am the bug deputy this week, next week is rubasov - is that good for you? 13:18:29 <rubasov> yes, it is 13:18:40 <haleyb> perfect, thanks! 13:18:49 <haleyb> moving on 13:19:01 <haleyb> #topic community goals 13:19:16 <haleyb> lajoskatona: any update on neutronclient? 13:19:25 <lajoskatona> yes some small 13:19:49 <lajoskatona> an sdk release is on its way for sec-groups fix: https://review.opendev.org/c/openstack/releases/+/951388 13:20:12 <lajoskatona> and an OSC patch for the same topic: https://review.opendev.org/c/openstack/python-openstackclient/+/950494 13:20:39 <lajoskatona> after this one (the sdk one) the horizon patches can move forward I beleive 13:21:00 <lajoskatona> that's it for this topic in the last week 13:21:15 <haleyb> lajoskatona: excellent. that last OSC one just needs a requirements bump once that release tag lands? 13:21:47 <lajoskatona> yes but I think the req bump is automatic after the release patch, but have to double check 13:22:19 <lajoskatona> but hs to be merged and voted by release team of course 13:23:02 <haleyb> perfect, thanks, and great to see progress :) 13:23:34 <haleyb> that leaves eventlet 13:23:49 <ralonsoh> yes, 3 subtopics 13:23:54 <ralonsoh> OVS agent: https://review.opendev.org/q/topic:%22bug/2087939%22+status:open 13:24:05 <ralonsoh> 3 first patches work fine, I think 13:24:11 <ralonsoh> apart from a pep8 error 13:24:33 <ralonsoh> but the 4th one, removing eventlet no, this one needs deeper investigation 13:24:45 <ralonsoh> L3 agent: https://review.opendev.org/c/openstack/neutron/+/938404 13:24:50 <ralonsoh> finally passing the CI 13:25:10 <ralonsoh> Neutron API - OVN maintenance worker: https://review.opendev.org/c/openstack/neutron/+/950854 13:25:18 <ralonsoh> I need to rebase on top of the other one 13:25:20 <ralonsoh> that's all 13:27:14 <haleyb> ralonsoh: what about the os-ken part? did you have an opinion on that? 13:27:16 <haleyb> https://review.opendev.org/c/openstack/neutron/+/941340 13:27:22 <haleyb> and there might have been an os-ken change 13:27:41 <ralonsoh> let me check that one, I didn't review it yet 13:27:46 <haleyb> https://review.opendev.org/c/openstack/os-ken/+/938337 13:28:19 <ralonsoh> yeah but this is the last step 13:28:29 <ralonsoh> changing the default value of the os-ken hub 13:28:50 <ralonsoh> let's check that everything works fine and then we'll change the default hub type 13:28:58 <haleyb> +1 13:29:18 <lajoskatona> +1 13:29:46 <haleyb> thanks for the update, will try and review this week 13:30:10 <haleyb> anything else for community? 13:30:29 <haleyb> #topic on-demand 13:30:36 <haleyb> i had one thing here 13:31:17 <haleyb> johnsom had asked about updating the base grenade job settings, i forgot to mention in CI meeting yesterday 13:31:19 <haleyb> Hi neutron neighbors, I see that the grenade parent job is still using q-svc: https://opendev.org/openstack/grenade/src/branch/master/.zuul.yaml#L242 13:31:27 <haleyb> I think that can go away now right? 13:31:38 <haleyb> ykarel: can you take a look at that? 13:31:49 <ykarel> haleyb, ack will check 13:32:00 <haleyb> thanks! 13:32:11 <johnsom> Thank you 13:32:22 <haleyb> anything else for on-demand? 13:32:36 <daidv> o/ 13:32:42 <daidv> I have an idea about a dns proxy l2 extension 13:32:50 <daidv> #link https://review.opendev.org/c/openstack/neutron/+/951390 13:33:16 <daidv> it's similar with dhcp extension to make a internal dns resolution like aws, gcp or ovn without dhcp agent 13:34:07 <haleyb> daidv: thanks for the ping 13:34:38 <haleyb> can you create a bug for this with [RFE] in the title so we can discuss it in our friday drivers meeting? 13:34:53 <lajoskatona> +1 for RFE 13:34:56 <haleyb> #link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers 13:36:14 <daidv> yeah, I will, did not create it before 13:36:53 <daidv> but this friday drivers meeting will be skip, right? 13:37:02 <haleyb> daidv: great thanks, that way we can understand what the change is, etc 13:37:34 <haleyb> daidv: right, no meeting this week, next would be June 13th 13:38:03 <daidv> oki, thank haleyb 13:38:47 <haleyb> np, thanks for the proposal 13:38:54 <haleyb> any other topics? 13:39:26 <haleyb> ok, thanks for attending and have a great week 13:39:28 <haleyb> #endmeeting