14:01:15 <haleyb> #startmeeting networking
14:01:15 <opendevmeet> Meeting started Tue Nov  5 14:01:15 2024 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:15 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:15 <opendevmeet> The meeting name has been set to 'networking'
14:01:30 <ralonsoh> hello
14:01:32 <elvira> o/
14:01:32 <haleyb> mlavalle: thanks for confirming :)
14:01:36 <ykarel> o/
14:01:44 <haleyb> Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki, haleyb, ralonsoh
14:01:45 <obondarev> o/
14:01:47 <mlavalle> \o
14:01:52 <lajoskatona> o/
14:01:55 <frickler> \o
14:02:14 <bcafarel> o/
14:02:22 <slaweq> o/
14:02:31 <haleyb> #announcements
14:02:33 <rubasov> o/
14:02:44 <cbuggy> o/
14:02:48 <haleyb> #link https://releases.openstack.org/epoxy/schedule.html
14:03:20 <haleyb> hope everyone had a good week last week, and thanks ralonsoh for running the meeting
14:03:26 <ralonsoh> yw
14:04:02 <haleyb> i am working on my write-up from PTG, travel and meetings kept me from it
14:04:58 <haleyb> 2023.1 is transitioning to unmaintained, think we are all set just waiting for release patches
14:05:39 <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
14:06:17 <haleyb> although saying that i might be out on friday, will see what topics we have beforehand
14:07:14 <haleyb> Let's continue to use the priorities dashboard for patches in the "ready to merge" state, it has worked well so far - see wiki for link (wiki does not allow url shorteners)
14:07:41 <lajoskatona> +1
14:07:43 <haleyb> any other announcements?
14:08:18 <haleyb> #topic bugs
14:08:36 <haleyb> bcafarel was deputy last week, his report is at
14:08:40 <haleyb> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/ONVMDOUQ4RDL7GVE2YRJ4AWCPUZCNFKO/
14:08:49 <haleyb> thanks bcafarel!
14:08:57 <bcafarel> np, it was a quiet week overall!
14:09:36 <haleyb> and it looks like most everything has a patch proposed
14:10:40 <haleyb> the only one that doesn't was for vpnaas
14:10:45 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2086189
14:11:31 <haleyb> not sure if anyone from vpnaas is present and can take a look?
14:12:00 <bcafarel> it would need some vpnaas eyes, the idea is nice but probably not a one-liner fix
14:12:23 <lajoskatona> I can send a mail out to the ones added OVN driver for vpnaas end of week if nobody checks it
14:12:39 <lajoskatona> agree with bcafarel
14:13:04 <haleyb> bcafarel: right, and nothing is propbably seamless with a reboot, but should know limitations
14:13:21 <haleyb> lajoskatona: thanks, that would work
14:14:10 <haleyb> i did not have any other bugs to discuss, does anyone else?
14:14:53 <haleyb> this week elvira is the bug deputy, next week is slaweq - ok with both?
14:15:46 <ralonsoh> (both are OK)
14:16:07 <slaweq> yeap
14:16:11 <haleyb> ok, moving on
14:16:24 <haleyb> #topic community goals
14:16:37 <elvira> yes, it's ok :)
14:16:58 <haleyb> looks like i need to update the wiki a little for this cycle, anyways...
14:17:14 <haleyb> lajoskatona: any progress on client deprecation?
14:17:23 <lajoskatona> no
14:18:00 <haleyb> lajoskatona: ack, thanks
14:18:51 <haleyb> ralonsoh: and i noticed in last week's notes you were still creating LP bugs for eventlet deprecation?
14:19:11 <ralonsoh> yes, the main one is the WSGI migration
14:19:24 <ralonsoh> not what we have done but the ASGI migration
14:19:39 <ralonsoh> I'm still reading the documentation and checking what is agreed in the community
14:20:03 <ralonsoh> but there is no opinion on this and I'm afraid of implementing a solution in Neutron that won't be supported by the community
14:20:16 <ralonsoh> in any case, I'll add this info in the related LP bug
14:20:16 <haleyb> i will have to catch-up with that thread
14:20:26 <ralonsoh> that's crazy, IMO
14:20:37 <ralonsoh> we should agree on a server and a FW
14:20:45 <lajoskatona> ok, so it inost just my lack of knowledge that I can't see the agreed solution and way forward :-)
14:21:05 <ralonsoh> in any case, at least for Neutron, WSGI works fine
14:21:22 <ralonsoh> we don't have the problems that, for example, Nova has with multiple threads during the API call
14:21:30 <ralonsoh> anyway, I'll document that in a LP bug
14:21:53 <ralonsoh> the rest of the bugs will be created too, to make work the rest of the agents
14:21:55 <haleyb> has there been any direction from the TC on the way forward in their meetings?
14:22:01 <ralonsoh> no
14:22:36 <slaweq> nothing I would be aware of
14:22:42 <ralonsoh> but so far, as commented, we work fine with WSGI
14:22:59 <ralonsoh> we need to "clean" the agents code and make them work without eventlet
14:23:00 <haleyb> ack, and yes we are fine with WSGI for now
14:23:10 <ralonsoh> that's all I have
14:23:45 <haleyb> thanks ralonsoh
14:24:05 <haleyb> #topic on-demand
14:24:19 <ralonsoh> one item
14:24:21 <ralonsoh> please check https://review.opendev.org/c/openstack/neutron/+/933836
14:24:31 <ralonsoh> this is fixing a recurrent issue in the CI
14:24:34 <ralonsoh> thanks!
14:25:16 <haleyb> ralonsoh: ack, thanks. and is your comment in the wiki old? regarding postgresql jobs, etc? i think it is
14:25:22 <ralonsoh> ah yes
14:25:31 <ralonsoh> so should we start deleting the jobs?
14:25:44 <haleyb> i usually clean before meeting but this is one hour earlier than normal
14:25:46 <ralonsoh> or removing the code in Neutron (tests, for example)
14:26:05 <ralonsoh> no no, the comment is for this meeting
14:26:11 <haleyb> ah
14:26:25 <slaweq> I think we can remove periodic jobs
14:26:37 <slaweq> and maybe keep tests in the functional tests for now
14:26:47 <ihrachys> why would we keep them?
14:26:47 <ralonsoh> ok to both suggestions
14:27:02 <slaweq> and add documentation warning that this backend is not tested by us
14:27:16 <ralonsoh> ihrachys, because FTs don't have such CI impact
14:27:19 <slaweq> ihrachys I think it would be similar to what e.g. nova is doing
14:28:39 <ihrachys> I don't know why nova is doing it, but I think in general, if we decide that something is not supported, then it's fair game to clean up code relevant to it (psql, linuxbridge or whatever else)
14:30:01 <ralonsoh> that's a fair suggestion, we tend to leave leftovers in the code...
14:30:10 <ihrachys> and if it's a capacity issue, I am happy to help with some of the cleanups (or take them over if you are busy)
14:31:09 <slaweq> I'm fine either way, we can also remove everything related to postgresql if that's the way team wants to go :)
14:31:28 <haleyb> i was going to ask if someone was interested in doing this cleanup? and if we should do in a single change if possible
14:32:12 <haleyb> i would +1 removing it all, instead of leaving some cruft behind we will all forget about until it fails CI
14:32:28 <ihrachys> imho whatever is most expedient; one piece is preferrable but if splitting simplifies life, also fine
14:32:40 <ralonsoh> +1 to this then
14:32:56 <lajoskatona> +1 to clean postgres things
14:32:57 <ihrachys> ralonsoh: I read you are going to clean up but if not, let us know
14:33:11 <ihrachys> and thank you
14:33:13 <ralonsoh> no no, +1 to the idea of removing all
14:33:21 <ralonsoh> this week I have no time
14:33:28 <ihrachys> ah ok I will look into it then
14:33:34 <ralonsoh> thanks!
14:33:55 <haleyb> ihrachys: thanks! ping for reviews
14:34:28 <haleyb> any other topics?
14:35:12 <haleyb> if not it's coffee time
14:35:21 <mlavalle> e\o/
14:35:26 <slaweq> o/
14:35:27 <haleyb> thanks for attending everyone and have a good week
14:35:29 <obondarev> \o
14:35:30 <haleyb> #endmeeting