14:00:19 <liuyulong> #startmeeting neutron_l3
14:00:20 <openstack> Meeting started Wed Sep 25 14:00:19 2019 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:21 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:23 <openstack> The meeting name has been set to 'neutron_l3'
14:00:48 <ralonsoh> hi
14:01:25 <haleyb> hi
14:01:38 <liuyulong> #chair haleyb
14:01:39 <openstack> Current chairs: haleyb liuyulong
14:02:36 <liuyulong> OooooK, let's ssstart.
14:02:44 <liuyulong> #topic Announcements
14:03:59 <liuyulong> #link https://releases.openstack.org/train/index.html
14:04:07 <liuyulong__> #link https://releases.openstack.org/train/index.html
14:04:19 <liuyulong> We have a Projects Release Date: 16 October, 2019
14:05:01 <liuyulong> it will come soon
14:05:36 <liuyulong> And I received many RC release mail.
14:06:08 <slaweq> yes, we already released rc1 for many stadium projects
14:06:29 <liuyulong> #link https://launchpad.net/neutron/+milestone/train-rc1
14:08:26 <liuyulong> This is our train-rc1 related topics. IMO, they are in good shape now, we could catch up the scheduler.
14:10:04 <liuyulong> Next
14:10:18 <liuyulong> #link https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
14:11:21 <liuyulong> Call for topics, summit is also coming soon, we will have 5 days meeting?
14:11:49 <slaweq> ptg starts on Wednesday
14:12:02 <slaweq> Monday - Wednesday is summit and Forum
14:12:12 <slaweq> IIRC
14:13:55 <liuyulong> Good, so 3 days, another thing is that we will also hold the meeting online in parallel?
14:14:22 <slaweq> liuyulong: I sent You an email recently about that
14:14:39 <slaweq> I will probably need Your help to organize some streaming
14:14:53 <slaweq> but we can sync later with that
14:15:03 <liuyulong> And mlavalle send us the mail to query if there will have a nice tool for those who can not go to Shanghai.
14:16:37 <slaweq> liuyulong: yes, but I will now take care of it instead of mlavalle
14:18:02 <liuyulong> Wechat is widely used in China. So I may want to give a try for our L3 team members to test some tools before the PTG.
14:18:29 <slaweq> liuyulong: will You be available tomorrow morning my time? So afternoon Your time
14:18:35 <slaweq> we can sync about it then
14:18:43 <slaweq> or on Friday if You want
14:19:34 <liuyulong> And a Proxy Server can also be another choice, so I wonder if there are any free server for us to user from the community?
14:19:58 <liuyulong__> Backup is coming...
14:20:10 <liuyulong__> Seems that connection is broken...
14:22:06 <liuyulong__> slaweq, sure, I will ping you tomorrow. Friday can also be fine.
14:22:26 <slaweq> liuyulong__: great
14:22:28 <slaweq> thx
14:23:41 <liuyulong__> All right, I have no more announcement. If you have please go ahead.
14:25:05 <liuyulong__> My irc connection is unstable. Let's speedup.
14:25:18 <liuyulong__> #topic Bugs
14:27:07 <liuyulong> #topic Bugs
14:27:29 <liuyulong> #chair liuyulong__
14:27:30 <openstack> Current chairs: haleyb liuyulong liuyulong__
14:27:43 <liuyulong__> #link https://bugs.launchpad.net/neutron/+bug/1845150
14:27:43 <openstack> Launchpad bug 1845150 in neutron "[FT] "keepalived" needs network interfaces configured as in its own config" [High,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)
14:28:01 <ralonsoh> the patch is here
14:28:12 <ralonsoh> #link https://review.opendev.org/#/c/684249/
14:28:49 <ralonsoh> as commented in the patch, if keepalived starts and doesn't see the tracked interfaces with the needed ips
14:28:52 <liuyulong> ralonsoh, thanks, it looks good to me.
14:29:02 <ralonsoh> the process stops
14:29:07 <ralonsoh> ok, thanks! thats all
14:29:37 <liuyulong> haleyb have +wed it :)
14:30:12 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1844688
14:30:12 <openstack> Launchpad bug 1844688 in neutron ""radvd" daemon does not work by default in some containers" [Medium,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)
14:30:21 <ralonsoh> yes, thanks for the comment
14:30:22 <liuyulong> The fix: https://review.opendev.org/683207
14:30:26 <ralonsoh> I need to add a reno
14:30:49 <ralonsoh> and test cases
14:31:16 <liuyulong> A new config is added for this bug, so IMO, a release note is needed. Users should know such config option in many ways.
14:31:37 <ralonsoh> for sure, today I'll push a new patch
14:32:48 <liuyulong> ralonsoh, np
14:33:01 <liuyulong> Next
14:33:03 <liuyulong> #link https://review.opendev.org/683207
14:33:09 <liuyulong> #undo
14:33:10 <openstack> Removing item from minutes: #link https://review.opendev.org/683207
14:33:14 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1845227
14:33:15 <openstack> Launchpad bug 1845227 in neutron "new l3 agent router factory breaks neutron-fwaas functional tests" [Critical,Fix committed]
14:33:41 <ralonsoh> fixed here #link https://review.opendev.org/#/c/652812/
14:34:16 <liuyulong> A Critical bug, and it is fixed.
14:35:52 <liuyulong> Last one from me
14:35:55 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1845145
14:35:55 <openstack> Launchpad bug 1845145 in neutron "[L3] add abilitiy for iptables_manager to ensure rule was added only once" [High,In progress] - Assigned to LIU Yulong (dragon889)
14:38:21 <liuyulong> Basically I did not see that WARNING log from our local queens deployments. But when create new agent extension with parallel processing, I noticed many warning log.
14:39:16 <liuyulong> In order to ensure the reentrancy of rule addition, I raised such bug.
14:39:21 <slaweq> liuyulong: but doesn't it means that Your agent extension is doing something wrong?
14:42:21 <liuyulong> slaweq, we can add more code to prevent that, but it will need more cache and event more lock to achieve that. A simple reentrancy or idempotent can be a nice approach.
14:42:55 <liuyulong> IMO, iptables_manager should have that ability.
14:43:55 <slaweq> I wonder why it wasn't dont like that in the past
14:44:13 <liuyulong> I did not find any reason that we want the duplicated rules in that managers rule cache.
14:44:16 <slaweq> maybe haleyb or mlavalle will remember something
14:44:42 <liuyulong> #link https://review.opendev.org/#/c/684237/
14:44:47 * haleyb sticks his head up
14:45:14 <liuyulong> The fix is quite simple.
14:45:52 <haleyb> slaweq: we've never needed that before, i don't know why it's happening now
14:47:32 <haleyb> that's why i was wondering if something outside neutron was adding a rule, or if we were calling something twice
14:48:08 <slaweq> haleyb: IIUC Neutron U/S don't need it still but liuyulong is doing some d/s agent extension which needs it to make his life easier
14:48:17 <liuyulong> haleyb, yes, that upstream log search can approve that.
14:48:32 <liuyulong> LOG a warning does not make sense to me, we are neutron developers, so we can make it better.
14:49:26 <haleyb> right, i'm just wondering how that ironic devstack setup is causing issues, since that seems to be where that port rule is added, not via the neutron api
14:50:14 <liuyulong> This fix should still use list() instead of set(), because the rule needs the proper order.
14:50:15 <haleyb> basically i'm saying it would be good to better understand how it's happening before adding a duplicate check
14:50:46 <liuyulong> And that's why the patch set 2 has functional test failures.
14:51:13 <liuyulong> I will run test locally and update it soon.
14:51:43 <liuyulong> Sorry, I have to run now. Let's stop here.
14:52:01 <liuyulong> Thank you for your participation.
14:52:10 <ralonsoh> bye
14:52:25 <liuyulong> and sorry for my bad network connection...
14:52:30 <liuyulong> Bye
14:52:33 <slaweq> thanks
14:52:35 <slaweq> o/
14:52:41 <liuyulong> #endmeeting