14:00:28 #startmeeting neutron_drivers 14:00:28 Meeting started Fri Sep 19 14:00:28 2025 UTC and is due to finish in 60 minutes. The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:28 The meeting name has been set to 'neutron_drivers' 14:00:30 Ping list: ykarel, mlavalle, mtomaska, slaweq, tobias-urdin, lajoskatona, haleyb, ralonsoh 14:00:38 hello 14:00:49 mlavalle is on PTO, slaweq is ill 14:01:07 o/ 14:01:19 ah, we probably won't have quorum then 14:01:38 what topics do we have? 14:02:06 dsan had added a topic, i had not triaged yet - https://bugs.launchpad.net/neutron/+bug/2123836 14:02:14 it was related to a patch that was proposed 14:02:47 ahh yes 14:02:57 https://review.opendev.org/c/openstack/neutron/+/950486 14:03:01 sounds good, to be honest 14:03:35 I don't know if that would require a spec but at least a discussion here 14:04:12 +1, the idea looks ok, and a good extension of current dhcp 14:04:30 let's wait for the next meeting then 14:04:33 I don't know if it is possible with OVN as well 14:04:41 yeah ,lets postpone it 14:04:42 I think that will be fast to discuss 14:04:55 hmmm I don't know if that is needed in OVN 14:05:02 we don't have namespaces there to monitor 14:05:09 the dhcp is internal to OVN 14:05:18 yes, that's true 14:05:30 ok, we can wait on that one 14:06:05 there was another one i triaged the other day that seemed interesting, and almost a bug 14:06:16 it's quite a long description 14:06:20 #link https://bugs.launchpad.net/neutron/+bug/2124215 14:07:32 hmmm that's interesting 14:07:36 i had a quick writeup in my comment, seems we can be more graceful when writing the leases file to help with windows vms 14:07:47 so you change the config with a live lease 14:07:51 I read it also, interesting indeed but as you wrote not sure if we have to change current behaviour 14:08:22 yes, they are reducing the lease time with running instances 14:08:53 I think that could be a documentation issue 14:09:17 ralonsoh: it's related to a patch that was sent last week by the same person, which you -1 14:09:23 correctly i believ 14:09:29 what patch? 14:09:44 I don't remember anything related (but I have very short memory) 14:10:05 * haleyb is looking 14:10:30 I see nothing in the open patches 14:10:50 https://review.opendev.org/c/openstack/neutron/+/960323 14:10:58 it was abandoned 14:11:21 ahhhh yes, but my -1 was for the quesiton only 14:11:31 I really wanted to understand this change 14:12:11 I usually write "-1 for visibility" 14:12:15 not this time 14:12:37 understood, maybe the rfe is just a better explanation of what caused the issue 14:12:58 right 14:13:42 i was wondering if as a compromise, we still advertise the config value for lease time, but write "forever" in the leases file, since technically it's there until we remove the port 14:14:04 then the comparison is a noop and we don't see this 14:14:14 does that make sense? 14:14:48 I would need to recheck the code and the problem, to be honest 14:14:50 i mean, as long as we have the port we'll have the dnsmasq entries and respond to a request 14:15:06 yes, that's correct 14:16:12 with a little change we'd avoid the DHCP NAK. it was just a thought and wouldn't change what the DHCP response is 14:18:22 anyways, i can ping the submittor and put on next weeks agenda to discuss further 14:19:52 alright, since we don't have quorum i'll end the meeting, hopefully next week everyone is back 14:20:03 have a nice weekend! 14:20:12 you too o/ 14:20:14 #endmeeting