14:02:24 <liuyulong> #startmeeting neutron_l3
14:02:25 <openstack> Meeting started Wed Nov 13 14:02:24 2019 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:02:28 <openstack> The meeting name has been set to 'neutron_l3'
14:02:37 <liuyulong> #chair slaweq
14:02:38 <openstack> Current chairs: liuyulong slaweq
14:02:41 <liuyulong> #chair haleyb
14:02:42 <openstack> Current chairs: haleyb liuyulong slaweq
14:02:47 <liuyulong> #chair liuyulong_
14:02:48 <openstack> Current chairs: haleyb liuyulong liuyulong_ slaweq
14:03:47 <liuyulong> Good to see you guys online here.
14:04:46 <slaweq> you too :)
14:04:57 <liuyulong> We have a memorable summit in Shanghai last week.
14:05:17 <liuyulong> And thanks to slaweq for the summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010702.html
14:05:20 <njohnston> It was great seeing you liuyulong_, wish I could have been there!
14:06:00 <liuyulong> njohnston, we had online conference with you, : )
14:06:19 <liuyulong> #topic Announcements
14:07:20 <liuyulong> I have no announcement, since we have no team meeting after the summit.
14:08:00 <liuyulong> So, maybe the blueprint should be mentioned here:
14:08:30 <liuyulong> #link https://blueprints.launchpad.net/neutron
14:09:07 <liuyulong> They did not move to U milestone。
14:10:06 <liuyulong> #link https://launchpad.net/neutron/ussuri
14:10:17 <liuyulong> No bugs and blueprints here.
14:11:39 <liuyulong> Any updates?
14:12:37 <liuyulong> #link https://releases.openstack.org/
14:13:06 <liuyulong> Ussuri 2020-05-13 estimated (schedule)
14:13:17 <liuyulong> OK, let's move on
14:13:37 <liuyulong> #topic Bugs
14:13:59 <liuyulong> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010676.html
14:14:26 <liuyulong> Ryan was our bug deputy last week, thanks.
14:14:47 <liuyulong> First one:
14:14:49 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1851659
14:14:49 <openstack> Launchpad bug 1851659 in neutron "removing a network from a DHCP agent removes L3 rules even if it shouldn't" [High,New]
14:16:25 <liuyulong> This looks a bit confusing to me, the 'rules' is policy route rule, dvr related flow?
14:17:59 <liuyulong> Due to the service port, for this bug it is DHCP port (instance)
14:19:03 <liuyulong> the dvr local router will be hosted to this scheduled host, if the compute node is running with DHCP agent, the compute port and DHCP port can both make the local router installation happen.
14:20:44 <liuyulong> So, if remove DHCP related port can cause the problem, that may point out that two compute port are hosted under same DVR router in one same host,
14:21:17 <liuyulong> Remove one VM will cause another VM traffic down? I don't think so.
14:21:36 <liuyulong> So let's test and investigate in details.
14:22:38 <liuyulong> Next
14:22:41 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1851194
14:22:42 <openstack> Launchpad bug 1851194 in neutron "FWaaSv2 configures iptables with invalid port name" [Medium,New]
14:23:12 <liuyulong> Yes, this is known issue, same to https://bugs.launchpad.net/neutron/+bug/1798577
14:23:13 <openstack> Launchpad bug 1798577 in neutron "[FWaas-DVR]wrong port name in iptables rules" [Medium,In progress] - Assigned to Wang Weijia (wangweij)
14:23:45 <liuyulong> This is the fix: https://review.opendev.org/#/c/606007/
14:25:06 <liuyulong> Surely it's worthy to fix, so let's start the review.
14:25:44 <liuyulong> Next one:
14:25:47 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1851609
14:25:48 <openstack> Launchpad bug 1851609 in neutron "Add an option for graceful l3 agent shutdown" [Medium,In progress] - Assigned to Oleg Bondarev (obondarev)
14:26:30 <slaweq> this one I would like You (L3 team) to triage first and than we can discuss that on drivers meeting
14:26:32 <liuyulong> Actually I'm fine with a new config option for varied deployments.
14:27:19 <liuyulong> Of course with default value False to not break the existing cloud.
14:30:05 <liuyulong> But according to the bug description, it the pod goes down, then everything is gone. (Maybe not, I'm not familiar with kubernetes...)
14:31:51 <liuyulong> Or the real story is the the l3-agent is running in container but the child processes are all in the host. Then everything remains after pod down.
14:33:05 <liuyulong> In this point of view, the proposal makes sense to me.
14:34:03 <liuyulong> But for sure, we need the bug reporter to give us more details.
14:35:02 <liuyulong> Oleg Bondarev is not here, I will add some concern to the bug.
14:37:16 <liuyulong> slaweq, so let's continue the discussion in LP first.
14:38:10 <slaweq> liuyulong: thx a lot
14:38:16 <slaweq> sounds like a good plan :)
14:38:29 <liuyulong> Looks like I'm now in a single person meeting, because I receive your message delay a lot...
14:38:58 <slaweq> sorry
14:39:09 <slaweq> I have also some urgent d/s stuff to do
14:39:17 <slaweq> so I'm doing two things in same time
14:39:37 <liuyulong> No, I mean my network connection to freenode...
14:39:52 <slaweq> ahh, ok
14:39:54 <slaweq> :)
14:40:28 <liuyulong> OK, let's scan the bug list.
14:41:13 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1850864
14:41:13 <openstack> Launchpad bug 1850864 in neutron "DHCP agent takes very long time to report when port is provisioned" [Medium,In progress] - Assigned to Slawek Kaplonski (slaweq)
14:41:39 <liuyulong> Looks like another bad background of DHCP agent...
14:42:52 <slaweq> yes
14:42:53 <liuyulong> I will raise the distributed DHCP based on openflow for ovs-agent sometime... I hope I have enough time to...
14:43:09 <slaweq> I sent patch for that already
14:43:28 <slaweq> https://review.opendev.org/#/c/692459/
14:43:38 <slaweq> please review it if You have some time
14:45:05 <liuyulong> Sure, my colleague may want to reproduce and test it, I will add the updates.
14:45:21 <liuyulong> Next
14:45:25 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1850818
14:45:25 <openstack> Launchpad bug 1850818 in neutron "[RFE][floatingip port_forwarding] Add description field" [Undecided,In progress] - Assigned to Pedro Henrique Pereira Martins (pedrohpmartins)
14:45:42 <liuyulong> IMO, this makes sense to me
14:45:58 <liuyulong> And I've reviewed some of the patch sets.
14:46:14 <liuyulong> And I may also want the author to add the name for the port forwarding.
14:46:36 <slaweq> yes, that makes sense for me too
14:46:51 <liuyulong> Sometimes, the name can be used for sorting, searching and classifying
14:47:06 <slaweq> but as this is api change, we need to discuss that on drivers meeting also
14:47:16 <liuyulong> description maybe to long for us.
14:47:31 <liuyulong> slaweq, sure, please add to the drivers list. : )
14:48:08 <liuyulong> OK, last one
14:48:14 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1850779
14:48:14 <openstack> Launchpad bug 1850779 in neutron "[L3] snat-ns will be initialized twice for DVR+HA routers during agent restart" [Medium,In progress] - Assigned to LIU Yulong (dragon889)
14:48:33 <liuyulong> We met this issue recently during a l3-agent upgrading
14:48:59 <liuyulong> There are too many routers in one agent, the restart time is really long.
14:49:52 <liuyulong> So we investigate the time spreading, this is one point.
14:50:44 <liuyulong> Many external commands will be executed in the namespace create function.
14:52:34 <liuyulong> If you run the agent with rootwrap, it spawns child processes, this is a bit expensive if there are tons of resources to process.
14:53:20 <liuyulong> The fix is here: https://review.opendev.org/#/c/692352/
14:53:52 <liuyulong> OK, we are running out of time.
14:53:57 <liuyulong> Next topic
14:53:59 <liuyulong> #topic On demand agenda
14:54:09 <liuyulong> #link https://review.opendev.org/#/q/project:openstack/neutron-specs+owner:+liuyulong+status:open
14:54:44 <liuyulong> I have updated some of spec for the topic raised during the PTG Shanghai.
14:55:30 <liuyulong> So comments are always welcomed.
14:57:08 <liuyulong_> Alright, let's end here.
14:57:21 <liuyulong_> Thanks for attending...
14:57:30 <liuyulong> #endmeeting