14:00:47 #startmeeting networking 14:00:47 Meeting started Tue Nov 14 14:00:47 2023 UTC and is due to finish in 60 minutes. The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:47 The meeting name has been set to 'networking' 14:00:48 o/ 14:01:03 o/ 14:01:15 o/ 14:01:18 o/ 14:01:32 hi everybody 14:01:32 o/ 14:01:39 \o 14:01:45 #topic announcements 14:02:16 This week is the C-1 milestone, and library releases have started to happen 14:02:36 os-ken was released and python-neutronclient is ready to do 14:03:01 ovsdbapp had a few things ready to merge and neutron-lib has some more 14:03:20 #link https://review.opendev.org/q/project:openstack/neutron-lib 14:04:26 if there is anything you want merged for C-1 there please update it and ping for reviews, i'll be updating the release patch either tonight or tomorrow to move it along 14:05:16 i think the only thing i had was fixing some unit tests to support sqlalchemy 2 - https://review.opendev.org/c/openstack/neutron-lib/+/900557 14:05:30 it's at least passed the debian amd64 testing 14:06:20 next announcement 14:06:51 o/ 14:06:54 sorry for being late 14:06:56 i was going to cancel the drivers meeting this friday as i'm on pto, and next friday since it's a US holiday, unless someone wants to run them 14:07:05 slaweq: o/ 14:08:02 do we have any proposals that my warrant a meeting? 14:08:12 or can we wait until december? 14:08:34 there is nothing at https://wiki.openstack.org/wiki/Meetings/NeutronCI at the moment 14:08:44 If needed I can run the meeting this coming Friday 14:08:44 and no new bugs up to today 14:09:07 next week's I have the same holiday as you \o/ 14:09:30 mlavalle: sure, we can decide thursday based on need, thanks! 14:09:35 yeap 14:09:54 +1 for deciding on thursday 14:12:08 the other announcement is just with this being C-1 release week, I'm guessing there will be a neutron release proposed as well, so if there is anything you need there work on getting reviews 14:12:36 also, regarding releases - yoga is going to be unmaintained soon 14:12:58 we have many not released patches there - maybe it's worth to make one more release before this "final" step 14:13:34 elodilles sent out a mail with useful links: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/SYPTRTPUNWZFJNSL2PEYK4NX67RQ5LLW/ 14:13:40 slaweq: ack, thanks 14:14:17 the neutron etherpad from the mail: https://etherpad.opendev.org/p/neutron-stable-yoga-eom 14:14:32 i know we had gone through the stable branches last week trying to merge things, lets take a look again 14:15:44 fwiw i know someone here at canonical was going to propose releases for all the neutron stable branches, i will ping him to get that started 14:18:26 so since i'm dense, yoga will be deleted but u/v/w/x will still be around? 14:19:52 or maybe the *deleted* doesn't mean what i think 14:20:33 Perhaps ask on the release channel as I know things are fluid 14:20:46 but I just hve rumors from elodilles :-) 14:20:49 just yoga-em ? 14:21:10 sure i'll ask 14:21:18 any other announcements? 14:21:53 #action (haleyb) ask what *deleted* means in yoga release email 14:22:00 #topic bugs 14:22:27 lucasagomes was the deputy last week, his report is at 14:22:30 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/PXVY4XBS32G5RDDU5MZJTQ5PL5LIID7H/ 14:23:32 not too busy, and as of this morning only one was unassigned 14:23:35 #link https://bugs.launchpad.net/neutron/+bug/2042941 14:24:14 i think yatin is off today, but that might be related to the oslo.utils issue we saw last week 14:24:59 oh, i misread the bug 14:25:27 they are not installing later versions? 14:27:36 is anyone more familiar with the job syntax on that to confirm? 14:28:05 I can check it 14:28:35 lajoskatona: thanks 14:29:36 my weekly bug query shows we're down 2 bugs to 765 so moving in the right direction 14:29:54 hopefully more will get auto-closed as patches merge 14:30:45 this week's deputy is jlibosva - are you ok doing it? 14:30:52 yes :) 14:31:21 and next week is obondarev 14:31:49 o/ 14:31:52 jlibosva: ack, and i see zero bugs so far :) 14:32:36 any other bugs anyone wants to discuss? 14:33:35 #topic specs 14:33:43 #link https://review.opendev.org/q/project:openstack%252Fneutron-specs+status:open 14:34:13 currently 3 open, the two BGP ones are close to merging, i just had some nits :-o 14:36:08 otherwiseguy had raised a question on the OVN interconnect one but hasn't had any follow-up yet 14:36:24 #link https://review.opendev.org/c/openstack/neutron-specs/+/891204 14:37:25 so i'll just ask if you have an opinion to comment there 14:39:48 #topic community_goals 14:40:30 lajoskatona: any updates? 14:41:13 nothing, sorry 14:41:36 ack 14:41:47 moving on 14:41:51 #topic on_demand 14:42:15 i had some items, but will let others talk first if they have something 14:43:16 ok, in no particular order 14:43:20 OVN support for VPNaas. Does anyone have cycles to take a look? 14:43:29 #link https://review.opendev.org/c/openstack/neutron-vpnaas/+/765353 14:44:18 it has one +2 from slaweq and a +1 from lajoskatona, it's just an XXL patch 14:44:57 someone on the ML asked about this and it came up at our PTG 14:44:59 wow 4k+ lines 14:45:02 I checked and stated it in devstack, so I am fine with it basically, but not deep testing as I am not vpn master 14:46:42 Luis Tomas Bolivar proposed openstack/ovn-bgp-agent master: Add initial support for local OVN cluster instead of kernel-networking https://review.opendev.org/c/openstack/ovn-bgp-agent/+/881779 14:46:45 right, who are the contributors working on vpnaas? besides bodo and dmitriy i guess 14:47:07 would be good to have another +1 from someone familiar with vpn 14:47:16 yeap 14:47:52 mnaser perhaps came earlier with questions or bugs 14:48:21 "This looks quite fair to me and it's confirmed to work by multiple operators. This also passes tempest test, so might worth having a shot and do a follow-up work whenever needed." - last comment from dmitriy 14:49:32 ok, I'll take a stab at it over the next 2 weeks. I'll go slowly and deploy in devstack 14:49:46 if i have time i'll look through it, i guess as long as the db migration is sane, etc we can always fix the bugs later 14:49:50 I might ping lajoskatona for some guidance 14:49:58 mlavalle: ack, thanks 14:50:00 +1 14:50:32 ok, my second topic is... 14:50:32 if by next Tuesday I feel I'm not making progress, I'll let you know during this meeting 14:50:57 Is anyone familiar with the neutron-lib API reporting tool? It has not been maintained and does not currently run 14:51:02 #link https://review.opendev.org/c/openstack/neutron-lib/+/899009 14:51:56 has anyone run 'tox -e api-report' in neutron-lib in the past 7 years? 14:52:09 I checked first when saw a patch around it, and now it is not working 14:52:25 haleyb what is this "api-report"? 14:52:30 it's first time I see that :) 14:52:49 slaweq: you answered my question, i had no idea it was there either 14:53:04 and it doesn't run 14:54:08 #link https://review.opendev.org/c/openstack/neutron-lib/+/338571 14:54:12 introduced there ^^ 14:55:32 we can either remove it, or fix the issue with the shebang and let someone try and get it working 14:55:47 but it seems we have enough on our plates right now 14:56:25 just a note: it was removed from pep8 job with https://review.opendev.org/c/openstack/neutron-lib/+/355563 14:58:08 I say remove it 14:58:28 mlavalle: ack, just wanted a second opinion, someone can always revert and fix it 14:58:33 + 14:58:35 yeap 14:58:35 +1 14:58:54 ok, that patch just needs an update to remove the rest of it, will ping submittor 14:58:56 ++ 14:59:08 last topic with one minute left 14:59:46 i had mentioned review days at the PTG, is everyone good at trying it for a day or two? 15:00:01 yes 15:00:05 yes 15:00:06 well, I am 15:00:17 I'll let others speak for themselves 15:00:23 ++ 15:01:14 ok, i guess that makes four of us at least :) 15:01:57 just please let me know when it will be so I will organize other stuff in the way to prioritize this :) 15:02:32 i was going to propose next week, but begin a short week maybe the week after? does november 30th/dec 1st work? or can do later 15:02:45 how about sending a doodle. Let's target second week of december 15:03:08 the week after Thanksgiving is also good 15:03:13 mlavalle: that's a good idea, will send one 15:03:26 #action (haleyb) send a doodle about review days 15:03:26 +1 15:03:53 ok, we are over time 15:04:07 there is no CI meeting today, will be next week i believe 15:04:17 ok, thx for the info :) 15:04:25 nope, Yatin if off today 15:04:27 thanks, just wanted to ask 15:05:31 lajoskatona: sorry, did you have a question? 15:05:48 no, he was asking about the CI meeting 15:05:50 no, just thanks for the info that no CI meeting today 15:05:51 answered 15:05:55 ah, ok 15:05:56 exactly 15:06:04 #endmeeting