14:04:09 #startmeeting networking 14:04:09 Meeting started Tue Jan 4 14:04:09 2022 UTC and is due to finish in 60 minutes. The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:04:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:04:09 The meeting name has been set to 'networking' 14:04:12 o/ 14:04:15 o/ 14:04:20 o/ 14:04:28 Welcome back everybody, and happy 2022 :-) 14:04:38 Likewise :-) 14:04:59 o/ 14:05:17 o/, happy new year! 14:06:12 #topic Announcements 14:06:28 The usual Yoga cycle calendar https://releases.openstack.org/yoga/schedule.html 14:06:45 and the release countdown mail: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026479.html 14:07:21 hi (sorry for the delay) 14:07:34 as this is Yoga-2 milestone, we have to cut new release of our libraries 14:08:01 so be aware (I have to check them too) 14:08:02 ahh, ok 14:08:09 sorry, wrong window :) 14:08:14 :-) 14:08:54 lol 14:09:28 if no questions/comments for the milestone, we can go on 14:10:01 #topic Bugs 14:10:21 The last deputyies were: 14:10:31 mlavalle: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026396.html 14:10:41 rubasov: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026456.html 14:11:07 and ralonsoh for last week 14:11:30 this week you mean? 14:12:34 ralonsoh: In the table (https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy) last week 14:12:57 from 27. December 14:13:11 ok I was on PTO 14:13:17 and I wasn't aware 14:13:22 I'll make a mail today 14:13:46 sorry, I missed my duty to send out mail, as I was also on PTO :-) 14:14:35 LOL, raise TooManyPtoException() 14:15:10 :-) 14:15:16 that's why I always demand a personalized bugs deputy email the week befor 14:15:27 my duty 14:15:48 and it has to be from the PTL 14:16:16 I checked and I see these unassigned bugs: 14:16:40 #link https://bugs.launchpad.net/neutron/+bug/1954942 14:17:35 #link https://bugs.launchpad.net/neutron/+bug/1955008 14:17:54 these are fullstack and functional failures 14:18:00 #link https://bugs.launchpad.net/neutron/+bug/1955478 14:18:24 this one I saw in CI meeting log as well (metadata connection issue) 14:18:43 #link https://bugs.launchpad.net/neutron/+bug/1955639 14:19:02 #link https://bugs.launchpad.net/neutron/+bug/1955765 14:19:04 That last one I was investigating a bit 14:19:12 but I don't really know what the problem can be there 14:20:17 thanks for checking it (notes in the CI meeting etherpad: https://etherpad.opendev.org/p/neutron-ci-meetings#L18 ) 14:20:44 and a last unassigned: #link https://bugs.launchpad.net/neutron/+bug/1955765 14:21:07 about 1955765 we may also ask if we are supporting the newer devstack plugin or not (not that the legacy one is un-deprecated) 14:21:17 This one is related to the devstack changes which moved code from neutron devstack plugin to core devstack 14:22:03 s/not that/now that/ 14:22:07 rubasov: thanks, that can be really straightforward to be decided 14:22:51 as the legacy is the used and a lot of things are not working in the new one (like OVN) 14:23:32 I think we discussed that back in Shanghai and we decided to "undeprecate" neutron-legacy 14:23:41 as new one wasn't never really finished 14:23:58 but since then still nobody wanted/had time to do it 14:24:02 slaweq: yes, but do we want to now support both the legacy and the new? 14:24:17 rubasov: I don't think we should keep both 14:24:24 +1 14:24:33 if the "legacy" one is ok and works for us, I would personally stay with that one 14:24:33 afaiu this report is about some breakage in the new 14:24:47 right, we should keep one option 14:25:15 I recommended the reporter that he switches back to the legacy 14:25:24 right 14:25:47 but that was kind of unofficial, just my opinion, not the neutron team's :-) 14:26:56 the "new" plugin code is in devstack, am I right? 14:27:37 I think, yes 14:27:57 devstack/lib/neutron 14:28:36 I don't know if there's any deprecation process for devstack, or how to handle if we get rid of the devstack/lib/neutron totally 14:29:06 but I can ask to be sure 14:29:09 deprecation is probably user-friendlier 14:29:20 sure 14:30:10 Ok, I will check it with QA team, how to deprecate it, or what should be the best way forward 14:31:32 If there's no more thoughts for the bugs we can move forward 14:32:03 One more sentence for the bugs: 14:32:08 This week lucasgomes is the deputy, and next week jlibosva will be. 14:32:40 I sent a mail to lucasgomes to be sure :-) 14:32:56 they are aware 14:33:02 ralonsoh: thanks 14:34:05 I checked the meeting agenda, and no more topics from as I see, as liuyulong didn't add topics for L3, and there is no change in ryu 14:34:42 If you have anything to discuss, please do it now 14:34:50 #topic On Demand Agenda 14:35:59 I just want to mention that I scheduled a topic for the drivers meeting on friday, about bringinh back FWaaS. You probably saw the email exchange 14:36:14 ++ 14:36:35 a team in China is interested in maintaining it and devlop the it for ovn 14:37:32 mlavalle: thanks, good that you mention it 14:37:57 they plan to attend the meeting this coming Friday 14:38:54 It's a little risky if I can participate, as I bring my sons for vaccination, and not sure if the gods of timing and queues are on my side.... 14:39:19 should we re-schedule for next week's Friday? 14:39:29 I think you should attend 14:40:32 this friday I will be off generally but I was going to attend the meeting 14:40:37 yeah perhaps that would be better 14:40:42 if it would be moved to next week, better for me :) 14:40:49 ok, I'll send them an email in abit 14:40:56 mlavalle: thanks 14:41:04 :-) 14:42:27 if no more topics we can close the meeting 14:43:07 thx, and see You in 18 minutes in the CI meeting :) 14:43:44 :) 14:43:45 bye 14:43:48 see you in a bit 14:43:49 #endmeeting