13:00:18 <haleyb> #startmeeting networking
13:00:18 <opendevmeet> Meeting started Tue Jun 17 13:00:18 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:18 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:18 <opendevmeet> The meeting name has been set to 'networking'
13:00:20 <haleyb> Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, haleyb, ralonsoh
13:00:21 <mlavalle> \o
13:00:31 <rubasov> o/
13:00:35 <ykarel> o/
13:00:36 <ralonsoh> hello
13:00:37 <obondarev> o/
13:01:39 <haleyb> #announcements
13:01:51 <haleyb> We are currently in Week R-14 of Flamingo
13:01:59 <haleyb> Our next milestone in this development cycle will be Flamingo-2, on July 3rd
13:02:06 <haleyb> Final 2025.2 Flamingo release: October 3rd, 2025
13:02:13 <haleyb> #link https://releases.openstack.org/flamingo/schedule.html
13:02:56 <haleyb> there was also a ML thread on the next PTG kickoff
13:03:03 <lajoskatona> o/
13:03:05 <haleyb> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/FU26JK6VKZNLNK7ZV7SGJF2V4KA37IQW/
13:03:16 <haleyb> The next OpenInfra PTG[1] will take place October 27-31, 2025 and registration for the event is now open[2]!
13:03:27 <haleyb> i have signed-up neutron
13:03:50 <lajoskatona> +1
13:04: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:04:52 <haleyb> this week i will be out thursday and friday as there is a holiday in the US, so planned on not having the drivers meeting
13:05:39 <haleyb> and the last announcement
13:05:42 <lajoskatona> ack, thanks for reminder / warning
13:06:26 <haleyb> yesterday was the initial meeting for the OVN BGP meeting, thanks jlibosva for organizing that
13:06:48 <haleyb> there will be more, so if you would like to attend please ping someone to get added to the invite
13:08:30 <haleyb> any other announcements?
13:09:01 <haleyb> ok, we can move on
13:09:08 <haleyb> #topic bugs
13:09:24 <haleyb> rubasov was the deputy last week, his report is at
13:09:28 <haleyb> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/5FDNKLQF6VCCUFQOBI5ANZ7CPAIJXOXH/
13:10:11 <rubasov> other than the RFE, all of them are taken care of
13:10:56 <haleyb> rubasov: yes, that's great, and a slow week :)
13:11:17 <rubasov> yep, hardly any reports
13:11:29 <slaweq> it's summer time :)
13:11:41 <haleyb> the RFE one is
13:11:45 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2114451
13:11:53 <haleyb> i have not looked at it yet
13:12:18 <rubasov> I was not sure why the author opened a new one, after having the earlier
13:12:19 <haleyb> [RFE] ports should contain a reference to the segment_id they are bound to
13:12:54 <rubasov> maybe he considered it a bug, but to me it looked more like an RFE
13:13:32 <haleyb> rubasov: right, i remember him asking on irc about it and i think i just said it's not there
13:13:55 <haleyb> if anyone has an opinion on that, especially from a DB perspective, please comment in the bug
13:14:55 <haleyb> any other bugs to discuss?
13:15:30 <haleyb> this week the deputy is mlavalle, next week is jlibosva - is that ok for you kuba?
13:15:33 <mlavalle> on it
13:16:13 <haleyb> kuba might not be here, thanks mlavalle hopefully another slow week :)
13:16:42 <haleyb> ok, moving on
13:16:48 <haleyb> #topic community goals
13:16:49 <mlavalle> kuba will be off on PTO next week. I'll ping him internally and will let you know his response
13:17:50 <haleyb> mlavalle: ack, maybe someone can swap, assuming he can do it another week, thanks
13:18:07 <lajoskatona> I can swap with kuba for next week
13:18:54 <mlavalle> we might need to shuffle the calendar, because kuba is taking several weeks off
13:19:32 <haleyb> lajoskatona: thanks, that will probably be a good swap, i now remember he's taking 3+ weeks off from the OVN meeting yesterday
13:19:58 <haleyb> lajoskatona is the week of July 21st
13:20:24 <lajoskatona> yes that will be ok for him perhaps, but we cab shuffle more later :-)
13:20:45 <haleyb> i will swap it in the calendar, thanks lajoskatona!
13:21:30 <haleyb> ok, back to community
13:21:44 <haleyb> lajoskatona: i saw some forward progress on the neutronclient changes
13:22:13 <lajoskatona> yes for Horizon the sec-groups related change was merged, and I have to check the QoS one as that is failing in CI
13:22:52 <lajoskatona> I beleive the failure is not related, (some volume and compute tests) but have to double check if somehow I break that...
13:23:02 <lajoskatona> that's it for this topic now
13:24:23 <haleyb> ack, thanks lajoskatona
13:24:42 <haleyb> and for reference the horizon QoS patch mentioned is
13:24:46 <haleyb> #link https://review.opendev.org/c/openstack/horizon/+/949764
13:24:53 <lajoskatona> thanks
13:25:32 <haleyb> ralonsoh: i'll let you update eventlet, definitely has made progress
13:25:45 <ralonsoh> yes, for the OVS patches, I've pushed a new PS
13:25:46 <ralonsoh> https://review.opendev.org/c/openstack/neutron/+/937765
13:26:03 <ralonsoh> now the OVS agent is working fine but fullstack is completely broken
13:26:31 <ralonsoh> I think I'm going to suggest to mark fullstack as non voting and fix these test in further patches
13:26:36 <haleyb> ralonsoh: fullstack related to eventlet or something else?
13:26:39 <ralonsoh> yes
13:26:48 <ralonsoh> from the upper patch: https://0152cc80754598f7dd6e-579ffa891605f8b01745396aeb7b7fcc.ssl.cf2.rackcdn.com/openstack/b4031eeca68d46438edf24bcc9cd1d09/testr_results.html
13:26:56 <ralonsoh> all OVS related broken
13:27:05 <ralonsoh> but tempest is working fine, all of them
13:27:16 <ralonsoh> let me check that first
13:27:28 <ralonsoh> I would add a topic for the driver meeting
13:28:05 <ralonsoh> we had many other patches merged for the neutron API, moving the other workers to non-eventlet
13:28:28 <ralonsoh> we had an issue with oslo.service but 4.2.1 (already approved this release) will fix that
13:28:41 <ralonsoh> once we have requirements bumped, I'll recheck the patches
13:28:49 <ralonsoh> and the DHCP agetn patch, by lajoskatona
13:29:07 <ralonsoh> https://review.opendev.org/c/openstack/neutron/+/950499
13:29:11 <ralonsoh> that's all I have
13:29:30 <lajoskatona> yes for that I have to jump to functional and fullstakc
13:30:03 <ralonsoh> functional is avoidable, we can make almost all tests to work
13:30:13 <ralonsoh> but I have no idea with fullstack, I need to check
13:30:44 <lajoskatona> ack, I have to check it myself also to see what happens
13:30:49 <ralonsoh> the problem is that we run all services from a single process, some of them use eventlet, but not others
13:32:00 <haleyb> thanks for the update. there are links to the review topics on the wiki if anyone has cycles
13:32:05 <haleyb> #link https://review.opendev.org/q/topic:%22eventlet-removal%22+project:openstack/neutron+status:open
13:32:12 <haleyb> there is also one for ovs-agent
13:32:30 <haleyb> #link https://review.opendev.org/q/topic:%2522bug/2087939%2522+status:open
13:32:41 <haleyb> thanks everyone for all their work on this
13:33:22 <haleyb> and if anyone can review this cherry pick - it fixes the metadata agent in 2025.1
13:33:25 <haleyb> #link https://review.opendev.org/c/openstack/neutron/+/952561
13:33:30 <haleyb> related to eventlet
13:33:46 <ralonsoh> right, important backport
13:35:06 <haleyb> there is a link to the Neutron Priority dashboard on the wiki, cut/paste here will wrap
13:35:44 <haleyb> that was all i see for community
13:36:01 <haleyb> #topic on-demand
13:36:30 <haleyb> something i forgot during announcements - the change to DCO
13:36:32 <haleyb> CLA is getting replaced with DCO https://governance.openstack.org/tc/resolutions/20250520-replace-the-cla-with-dco-for-all-contributions.html
13:36:39 <haleyb> starting date will be 2025-07-01, but it doesn't hurt to start signing off your commits earlier. the TC is still working on updating the global contributor docs accordingly
13:36:52 <haleyb> using -s with git commit (or tweaking .gitconfig) should get this behavior
13:37:18 <mlavalle> is that all we need to do?
13:38:42 <lajoskatona> you need some gpg key to be ready for it i think, so perhaps you have to play with that to make git happy
13:38:46 <haleyb> mlavalle: that's all i did. i am not a lawyer but do not believe there is any other sign-off, etc or that it changes things
13:38:59 <mlavalle> cool
13:39:58 <haleyb> i am guessing that on a cherry-pick it will automatically add your signed-off-by if you were not the original submittor but have not looked at the doc in a week
13:40:43 <haleyb> it brings openstack in-line with things like the linux kernel as far as commits go
13:41:34 <haleyb> ralonsoh: oh i see you had added a topic
13:41:41 <ralonsoh> yes, one sec
13:42:08 <ralonsoh> https://bugs.launchpad.net/neutron/+bug/2114819
13:42:12 <ralonsoh> so another issue with tags
13:42:29 <ralonsoh> we found (a customer) that they are not case sensitive
13:42:41 <ralonsoh> well, at least the DB table charset and collation
13:42:56 <ralonsoh> (the collation is used to make, for example, text comparisons)
13:43:10 <ralonsoh> the default ones are not case sensitive
13:43:21 <ralonsoh> so, we can do one of these actions
13:43:50 <ralonsoh> 1) chage the collation and charset. But nobody else do it and could have interferences with other tables
13:44:08 <ralonsoh> 2) make this extension case insensitive: sanitize all tags to lower case and that's all
13:44:21 <ralonsoh> ^^ the second is easily backportable too
13:45:11 <haleyb> ralonsoh: is tag just a text string?
13:45:14 <ralonsoh> yes
13:45:18 <lajoskatona> is there some common paper for tags in openstack perhaps?
13:45:29 <ralonsoh> lajoskatona, I'll check that, for sure
13:46:23 <lajoskatona> this API doc tells that they are case sensitive : https://specs.openstack.org/openstack/api-wg/guidelines/tags.html
13:46:27 <slaweq> https://specs.openstack.org/openstack/api-wg/guidelines/tags.html
13:46:30 <slaweq> now I found it
13:46:37 <slaweq> and they said that "tags are case sensitive"
13:46:38 <lajoskatona> not sure if these API sig docs are widely adapted
13:46:45 <mlavalle> lajoskatona: do you mean role?
13:46:48 <slaweq> :/
13:47:26 <ralonsoh> I would like to know if other projects have this issue too
13:47:44 <lajoskatona> ralonsoh: +1
13:48:15 <ralonsoh> ok, so far I need to do more investigation
13:48:28 <ralonsoh> if I have this info for the next drivers meeting, I'll ping you
13:48:32 <ralonsoh> thanks!!
13:48:41 <haleyb> ack thanks ralonsoh
13:49:11 <haleyb> anything else to discuss?
13:49:18 <mlavalle> I do. kuba will be back at work the week of July 14th and he is fine being the deputy that week
13:49:31 <frickler> just to clarify: DCO is just a line in the commit message, not a gpg signature
13:50:02 <lajoskatona> frickler: thanks, that is for -S perhaps which some github projects ask for , sorry for confusion
13:50:06 <haleyb> mlavalle: ack, i will re-arrange the schedule
13:50:25 <ildikov> I also have a quick ad-hoc topic for today, if there's still time :)
13:50:39 <haleyb> ildikov: sure, go ahead
13:50:49 <ildikov> haleyb: thank you!
13:51:09 <ildikov> I dropped a quick text into the channel yesterday about the new OpenStack Ops Radio Hour meeting series
13:51:09 <opendevreview> phillip toohill proposed openstack/neutron stable/2024.1: Reduce metadata port lookup log message to warning  https://review.opendev.org/c/openstack/neutron/+/952767
13:51:23 <ildikov> the next one is scheduled for June 27, which is next Friday
13:51:52 <ildikov> and on the last call people brought up some networking topics, OVN-related and other ones
13:52:23 <ildikov> and it would be great to have some folks from the Neutron team around for those topics
13:52:38 <mlavalle> what time?
13:52:44 <ildikov> it's at 1300 UTC
13:53:07 <ildikov> meeting agenda and previous notes are here: https://etherpad.opendev.org/p/openstack_ops_radiohour
13:53:58 <mlavalle> is it a video meeting?
13:54:03 <ildikov> I'm happy to chat more about it outside of the team meeting. I just wanted to raise awareness, and see if people might have any questions I can answer.
13:54:32 <ildikov> we're using Meetpad, so it is a call, but most people were off camera last time
13:54:48 <haleyb> it is right before the drivers meeting time-wise
13:54:57 <mlavalle> yeap
13:55:42 <ildikov> I understand that might not be the most ideal timing, but at least the two are not colliding
13:56:29 <ildikov> the call series is set to monthly cadence currently
13:57:15 <haleyb> ildikov: thanks for the notice, maybe someone will be able to attend, not sure if i have a conflict right now but will check
13:57:17 <ildikov> we're trying to get ops people and devs together in a more casual setting to sync up and figure things out that might cause challenges in production environments
13:57:53 <ildikov> haleyb: it would be tremendously helpful to have one or two people from the team, thank you for considering
13:58:28 <ildikov> I'll check back on the channel as we get closer to the Ops Radio Hour with a reminder and to see who might be able to make it
13:58:40 <mlavalle> ildikov: I will also try to attend. I'll let you know by Wednesday of next week
13:58:53 <ildikov> mlavalle: great, thank you!
13:59:27 <ildikov> and thank you all for allow me a little time on the meeting to bring up and discuss the topic last minute! :)
13:59:37 <haleyb> ok we are at top of hour
13:59:41 <haleyb> have a good week everyone!
13:59:45 <haleyb> #endmeeting