14:00:26 <lajoskatona> #startmeeting networking 14:00:26 <opendevmeet> Meeting started Tue Jan 11 14:00:26 2022 UTC and is due to finish in 60 minutes. The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:26 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:26 <opendevmeet> The meeting name has been set to 'networking' 14:00:28 <mlavalle> o/ 14:00:29 <lajoskatona> Hi 14:00:30 <ralonsoh> hi 14:00:32 <obondarev> hi 14:01:38 <rubasov> hi 14:02:11 <lajoskatona> I think we can start 14:02:17 <lajoskatona> #topic Announcements 14:02:30 <lajoskatona> The usual Yoga cycle calendar https://releases.openstack.org/yoga/schedule.html 14:02:31 <isabek> Hi 14:02:32 <slaweq> hi 14:02:39 <lajoskatona> Release countdown, R-11: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026580.html 14:02:46 <lajoskatona> Some highlights from elod: 14:03:04 <lajoskatona> closest date: non-client library freeze (February 17th, 2022) 14:03:18 <lajoskatona> its ~1 month from now to freeze n-lib 14:03:30 <lajoskatona> for example and ovsdbapp, and os-ken 14:03:40 <lajoskatona> Client library freeze / Yoga-3 milestone: (February 24th, 2022) 14:03:46 <lajoskatona> Yoga final release: March 30th, 2022 14:03:58 <lajoskatona> Aaaaand: next PTG: April 4 - 8, 2022 (virtual) 14:04:13 <mlavalle> was it going to be in Berlin? 14:04:25 <lajoskatona> in virtual Berlin? 14:04:37 <lajoskatona> by the mail it still be virtual 14:04:47 <mlavalle> no, I meant I thought we were meeting in person in Berlin 14:05:08 <slaweq> I think that in Berlin there will be Summit in June 14:05:10 <mlavalle> that's ok, I probably got confused 14:05:19 <mlavalle> ahh, that explains it 14:05:19 <lajoskatona> that will be july (or at least some mid summer date) and summit like event 14:05:53 <obondarev> https://openinfra.dev/summit/ - June 14:06:02 <lajoskatona> sorry, true that we will most probably have a personal summit in Berlin 14:06:11 <lajoskatona> so it is June 14:06:32 <opendevreview> Merged openstack/neutron stable/ussuri: [OVN] Prevent deleting the only IP of a router port https://review.opendev.org/c/openstack/neutron/+/823407 14:08:37 <lajoskatona> If there is no more questions for announcements and cycle events we can move to next topic 14:09:24 <lajoskatona> #topic Bugs 14:09:40 <lajoskatona> Last week lucasgomes was bug deputy: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026616.html 14:10:04 <lajoskatona> Unassigned bugs from the report: 14:10:08 <lajoskatona> https://bugs.launchpad.net/neutron/+bug/1956034 (ovn load balancer health monitor cause mac address conflic ) 14:10:28 <slaweq> I plan to take a look into that one 14:11:51 <lajoskatona> slaweq: thanks 14:12:12 <lajoskatona> actually there's another OVN ladbalancer issue: https://bugs.launchpad.net/neutron/+bug/1956035 (ovn load balancer member failover not working when accessed from floating ip) 14:12:37 <slaweq> lajoskatona: yes, I saw both of them and I will check them when I will have time 14:12:48 <lajoskatona> slaweq: ok, cool 14:12:55 <slaweq> I didn't assign them to myself yet because maybe someone else wants to take a look :) 14:13:00 <Ammad> Hi 14:13:23 <lajoskatona> slaweq: be careful try not to frighten others from bugs :P 14:13:33 <slaweq> LOL 14:13:34 <slaweq> sure 14:14:19 <lajoskatona> Ammad: Hi, we have now the team meeting, but if you have question we can discuss it at the end of the meeting 14:14:41 <lajoskatona> and the last unassigned: https://bugs.launchpad.net/neutron/+bug/1956846 (ha router duplicated routes) 14:14:49 <ralonsoh> I don; 14:14:55 <ralonsoh> I don't think this is a bug 14:16:18 <Ammad> Just a quick question. What is the best practice to create a provider network ? I have vlan provider network but dhcp disabled in ovn backend. Instance boot up failed. Is it the best practice to enable dhcp on provider network ? 14:16:45 <lajoskatona> ralonsoh: cool, as I see from last comment the reporter has some workaround for the issue 14:16:57 <ralonsoh> yeah but this is already solved in next versions 14:17:12 <ralonsoh> it is useless to create workarounds for something that is already solved 14:17:19 <ralonsoh> in any case, we should close it 14:17:26 <lajoskatona> ralonsoh: oh, I see they use stein, ok, thanks 14:18:18 <lajoskatona> There's another one which hit my sensor: https://bugs.launchpad.net/neutron/+bug/1956435 : OVS: support multiple segments per host 14:18:44 <lajoskatona> ralonsoh wisely said that this is not OVs specific and more an RFE 14:18:45 <ralonsoh> that should be discussed in drivers meeting, I think 14:19:20 <lajoskatona> that would be my next question do we need? 14:19:45 <lajoskatona> It was discussed on one of the PTGs (last Denver one perhaps) with a spec and wip patch proposed: https://review.opendev.org/c/openstack/neutron-specs/+/657170 14:19:55 <lajoskatona> https://review.opendev.org/c/openstack/neutron/+/623115 14:20:09 <lajoskatona> we can discuss of course 14:20:19 <ralonsoh> we can review the spec 14:20:43 <bcafarel> late o/ 14:20:57 <lajoskatona> I added as comment to the new spec the old one, and I would like to compare them :-) 14:23:35 <lajoskatona> I would vote on to review the spec, and assume that the idea to allow multiple segments per host is still supported by the community 14:24:53 <opendevreview> Merged openstack/os-ken stable/wallaby: Add requirements.txt to tox environment https://review.opendev.org/c/openstack/os-ken/+/824090 14:24:55 <lajoskatona> Ok, that's it for the bugs from me 14:25:05 <opendevreview> Oleg Bondarev proposed openstack/neutron master: Add devstack plugin support for Local IP https://review.opendev.org/c/openstack/neutron/+/818228 14:25:14 <lajoskatona> This week jlibosva is the deputy, and next week obondarev will be, is that ok? 14:25:23 <obondarev> yep 14:25:29 <lajoskatona> obondarev: thanks 14:26:07 <bcafarel> one extra bug recently reported (not sure os-ken storyboard is closely monitored) https://storyboard.openstack.org/#!/story/2009779 14:26:47 <bcafarel> os-ken logging some passwords when used with neutron-dynamic-routing, probably good to filter them out :) 14:26:50 <lajoskatona> bcafarel: thanks 14:27:22 <mlavalle> yeah, let's not log passwords. generally a good idea 14:28:56 <lajoskatona> mlavalle: +1 14:29:16 <lajoskatona> bcafarel: don't we need to treat it as security vulnerabilty? 14:29:32 <mlavalle> it has been disclosed here already 14:29:38 <mlavalle> so no need 14:29:52 <lajoskatona> mlavalle: ok 14:31:07 <lajoskatona> I can check it, 14:31:50 <lajoskatona> thanks bcafarel for mentioning it, I will add some notification to monitor storyboard 14:32:23 <lajoskatona> ok, next topic: 14:32:26 <lajoskatona> #topic L3 subteam 14:32:41 <lajoskatona> No news from liuyulong, so we can skip it 14:32:55 <lajoskatona> if nothing from you to discuss 14:33:26 <lajoskatona> #topic ryu and os-ken 14:33:59 <lajoskatona> no new patches in ryu 14:34:21 <lajoskatona> #topic On Demand Agenda 14:34:24 <ralonsoh> sorry 14:34:24 <ralonsoh> https://review.opendev.org/q/project:openstack%252Fos-ken+status:open 14:34:47 <ralonsoh> some active patches to fix stable branches in os-ken 14:35:22 <lajoskatona> ralonsoh: thanks 14:36:04 <lajoskatona> ralonsoh: when all merged do we need new stable release of os-ken? 14:36:21 <ralonsoh> at least for U and T 14:36:32 <ralonsoh> because of https://review.opendev.org/q/If616980b2c6d7303cdc5d4f5e7247d63e4c34939 14:36:36 <lajoskatona> ok, I keep in mind 14:37:29 <lajoskatona> so back to On Demand Agenda 14:37:36 <lajoskatona> (lajoskatona): Document Edge deployment scenarios 14:37:54 <lajoskatona> discussion logs from PTG: https://etherpad.opendev.org/p/octavia-designate-neutron-ptg#L16 14:38:12 <lajoskatona> I sent out a mail to collect ideas for documentation place: http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025811.html 14:38:45 <lajoskatona> and as there was no answer and suggestion where and how to document such thing the agreement (with ildikov and johnsom) was to use neutron/doc now. 14:39:30 <lajoskatona> but to tell the truth my brain power stopped here as I have no idea what specially we need to document which is only edge relate :-( 14:41:06 <lajoskatona> so I would like to ask some help to collect at least topics like difference from general AZ scenario.... 14:41:39 <lajoskatona> and I suppose there should be more specification compared to current general deployment docs 14:42:23 <opendevreview> Bence Romsics proposed openstack/neutron master: Make the dead vlan actually dead https://review.opendev.org/c/openstack/neutron/+/820897 14:45:43 <damiandabrowski[m]> hey guys, can I ask someone from the L3 team to look here and at least decide which direction should we go?https://bugs.launchpad.net/neutron/+bug/1952907 14:46:10 <damiandabrowski[m]> 3 different ways of fixing this issue are mentioned there 14:48:15 <slaweq> damiandabrowski: but shouldn't keepalived send garps immediately and also after some time? 14:48:35 <ralonsoh> (btw, let's close the meeting) 14:48:38 <lajoskatona> damiandabrowski[m]: I see 2 wip patches for the bug 14:48:41 <slaweq> ahh, ok I see the bug description 14:48:52 <ralonsoh> if no other topic is in the agenda 14:48:56 <lajoskatona> ralonsoh: ok 14:49:02 <mlavalle> +1 14:49:08 <lajoskatona> we can close if no more comments 14:49:13 <slaweq> +1 14:49:16 <lajoskatona> #endmeeting