14:06:14 <lajoskatona> #startmeeting networking 14:06:14 <opendevmeet> Meeting started Tue Mar 22 14:06:14 2022 UTC and is due to finish in 60 minutes. The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:06:14 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:06:14 <opendevmeet> The meeting name has been set to 'networking' 14:06:17 <lajoskatona> Hi 14:06:17 <mlavalle> o/ 14:06:32 <isabek_> Hi 14:06:32 <obondarev> hi 14:06:53 <rubasov> o/ 14:07:07 <slaweq> o/ 14:07:40 <bcafarel> \o 14:07:55 <amotoki> hi 14:08:00 <ralonsoh> hi 14:08:14 <lajoskatona> ok, let's start 14:08:20 <lajoskatona> #topic Announcements 14:08:34 <lajoskatona> The usual Yoga cycle calendar https://releases.openstack.org/yoga/schedule.html 14:08:43 <lajoskatona> Release countdown, R-1: http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027761.html 14:08:55 <lajoskatona> so we are close to really finish Yoga 14:09:17 <lajoskatona> Zed schedule: https://releases.openstack.org/zed/schedule.html to remember it :-) 14:09:28 <lajoskatona> And Zed PTG etherpad: https://etherpad.opendev.org/p/neutron-zed-ptg 14:09:40 <lajoskatona> please propose topics 14:09:44 <slaweq> do we have any last minute patches/bugs planned for RC? 14:09:53 <slaweq> I didn't saw any but maybe I missed something 14:10:05 <lajoskatona> I checked yesterday but nothing that I noticed 14:10:13 <slaweq> great :) 14:10:32 <lajoskatona> if there's any please increase reviuew priority and advertise on the channel 14:11:30 <lajoskatona> On thing (thanks bcafarel and elod for warning for it): 14:11:42 <lajoskatona> We have no devstack yoga branch, so please hold backports 14:11:49 <lajoskatona> #link https://meetings.opendev.org/irclogs/%23openstack-neutron/%23openstack-neutron.2022-03-22.log.html#t2022-03-22T09:37:29 14:12:36 <lajoskatona> I haven't checked it in details, but perhaps QA team waits for ironic RC before cutting devstack yoga branch 14:13:12 <frickler> devstack waits for requirements, the latter waits for ironic, horizon and others 14:13:36 <lajoskatona> frickler: ohh, thanks so its more a chain of waits :-) 14:13:47 <frickler> #link https://review.opendev.org/c/openstack/releases/+/833610 14:14:16 <frickler> the "same topic" changes linked there seem to be all blockers 14:15:04 <bcafarel> it seems to match the list indeed, thanks for the link frickler 14:16:25 <lajoskatona> yeah thanks, good list (#link https://review.opendev.org/q/topic:yoga-missing-stable-branches ) 14:17:10 <lajoskatona> if there is no comments / questions for announcements we can move on 14:18:26 <lajoskatona> #topic Bugs 14:18:36 <lajoskatona> Report from mlavalle: http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027771.html 14:19:00 <lajoskatona> I saw one bug without owner: 14:19:01 <lajoskatona> python-ovs package 2.17 introduce table.condition attribute which is overwriten by neutron ovsdb code (#link https://bugs.launchpad.net/neutron/+bug/1965599 ) 14:19:14 <ralonsoh> Terry is working on this one 14:19:26 <lajoskatona> but I think there's another bug for it: list object has no attribute 'acked' (#link https://bugs.launchpad.net/ovsdbapp/+bug/1965819 ) 14:19:26 <ralonsoh> there are two patches, one for ovsdbapp and other for neutron 14:19:31 <ralonsoh> yes 14:19:42 <lajoskatona> ralonsoh: ok,thanks 14:20:20 <lajoskatona> not sure if we have to make duplicate one of the other 14:20:33 <mlavalle> Great, I was going to ask Terry to look at this bug 14:20:48 <ralonsoh> I've marked 1965599 as duplicated, because Terry is working in the other one 14:20:51 <lajoskatona> but anyway it is not lost and otherwiseguy is working on it 14:21:01 <lajoskatona> ok, cool 14:21:05 <mlavalle> ralonsoh: yeah, thanks 14:21:41 <mlavalle> I don't have any other comment 14:21:53 <lajoskatona> mlavalle: thanks :-) 14:22:01 <lajoskatona> This week rubasov is the deputy, and next week ralonsoh will be. 14:22:09 <rubasov> on it 14:22:15 <ralonsoh> ok 14:22:24 <lajoskatona> rubasov, ralonsoh: thanks 14:23:51 <lajoskatona> if there's no more questions/ comments we can move on 14:24:17 <lajoskatona> #topic On Demand Agenda 14:24:50 <lajoskatona> (lajoskatona): I added question for neutron-vpnaas: 14:25:02 <lajoskatona> Specific issue: VPNaaS reconfiguration creates duplicate IPtables rules causes the VPN connection to remain DOWN (#link https://bugs.launchpad.net/neutron/+bug/1943449 ) 14:25:51 <lajoskatona> it's a quite old bug, and the reporter sent few mails with reproduction: 14:26:21 <lajoskatona> but generally neutron-vpnaas is not in a good shape today 14:26:32 <lajoskatona> https://review.opendev.org/c/openstack/neutron-vpnaas/+/833056 => neutron-vpnaas-functional-sswan failing. 14:26:52 <lajoskatona> I checked lieutenants list: https://docs.openstack.org/neutron/latest/contributor/policies/neutron-teams.html#sub-project-lieutenants 14:27:08 <lajoskatona> and for vpnaas nobody is active recently 14:27:11 <ralonsoh> does vpnaas use IPTablesTable class? 14:27:18 <ralonsoh> I'm saying this because we can revive https://review.opendev.org/c/openstack/neutron/+/684237/13/neutron/agent/linux/iptables_manager.py 14:27:23 <slaweq> maybe we should once again call for maintainers of that project and if there will be nobody, deprecate it? 14:28:12 <lajoskatona> slaweq: yes, thats a good question 14:28:19 <lajoskatona> ralonsoh: probably 14:28:25 <ralonsoh> ok 14:29:14 <lajoskatona> I added this topic to the PTG etherpad also (some more details I have to add later) 14:29:57 <slaweq> ++ 14:30:14 <lajoskatona> perhaps it's more a community question, can we say that we are responsible for a project (release it, maintain it, expects bug for it) if we lost the smart people from behind it? 14:31:08 <lajoskatona> on the other hand I pushed patches to have weekly periodic jobs for our stadium: 14:31:11 <lajoskatona> https://review.opendev.org/q/topic:weekly-jobs 14:31:36 <lajoskatona> because we have few and irregular patches for most of them this can help to have feedback regularly 14:31:40 <slaweq> we were discussing that I think in Shanghai, and we agree then that we should deprecate/remove from stadium such projects which aren't really maintained 14:32:07 <lajoskatona> slaweq: yes, true 14:32:25 <lajoskatona> slaweq: for vpnaas was there mail about deprecation? 14:32:27 <slaweq> very good idea with weekly jobs - lets collect data with those jobs and then we can discuss health of each of such projects during the PTG 14:32:29 <bcafarel> nice idea the weekly jobs 14:33:04 <slaweq> lajoskatona: no, for vpnaas probably there wasn't emails as we had yamamoto who volunteered to maintain it then 14:33:47 <lajoskatona> slaweq: ok, thanks, I set a note for myself to send out mail after PTG discussion 14:33:59 <bcafarel> fwaas I think it had a nice gradual process on that (call for maintainers a few times, out of stadium, deprecation) 14:34:25 <slaweq> bcafarel: yes, and even revive recently :) 14:34:27 <lajoskatona> and now we have it back :-) 14:34:33 <slaweq> so full "circle of life" :P 14:34:52 <lajoskatona> ok, that's it from me 14:35:12 <ralonsoh> (full "circe of life" does not imply zombies revived from the tomb) 14:35:31 <slaweq> :D 14:35:37 <lajoskatona> :D 14:35:57 <slaweq> ralonsoh: so it was even more than full "circle of life" :D 14:36:02 <ralonsoh> hehehe 14:36:10 <slaweq> one and half of circle ;P 14:37:17 <lajoskatona> Is there any topics we should discuss? 14:37:44 <mlavalle> not from me 14:38:03 <slaweq> me neighter 14:38:57 <lajoskatona> huhh, perhaps one personal from me: next week will be troubled for me, Monday-Wednesday with rubasov we try to help refugees so I will be offline most probably 14:39:24 <ralonsoh> good luck! please to hear that 14:39:33 <mlavalle> lajoskatona, rubasov: thank you for doing that. Good luck! 14:39:47 <slaweq> lajoskatona++ 14:39:53 <mlavalle> lajoskatona: Ukranian refugees? 14:39:53 <slaweq> thx for doing tha 14:39:55 <slaweq> *that 14:39:58 <obondarev> thank you lajoskatona 14:40:03 <lajoskatona> thanks 14:40:10 <obondarev> and rubasov 14:40:19 <lajoskatona> #endmeeting