21:00:08 <slaweq> #startmeeting networking 21:00:09 <openstack> Meeting started Mon Jan 20 21:00:08 2020 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:12 <openstack> The meeting name has been set to 'networking' 21:00:13 <slaweq> o/ 21:00:32 <mlavalle> o/ 21:00:44 <bcafarel> hi 21:00:50 <mlavalle> Today is a Holiday in the US, so we might have very low attendance 21:00:56 <haleyb> o/ 21:01:27 <slaweq> mlavalle: right, but I see that we have at least 2 great team members from US already :) 21:02:25 <slaweq> ok, so lets start and do it fast to not keep You here for too long :) 21:02:30 <slaweq> #topic Announcements 21:02:58 <slaweq> first one 21:03:18 <slaweq> we are still looking for neutron-fwaas maintainer, I just sent LAST CALL reminder to the ML 21:03:32 <slaweq> lets see if there will be any responses 21:03:47 <slaweq> next one: 21:03:49 <slaweq> We are getting close to Ussuri-2, it will be in the week of February 10: https://releases.openstack.org/ussuri/schedule.html 21:04:18 <slaweq> and one which I should announce last week but I forgot, next release will be Victoria: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011947.html :) 21:04:33 <slaweq> that's all announcements from my side today 21:04:42 <slaweq> anything else You want to announce to the team? 21:05:52 <slaweq> ok, if not than lets move on 21:06:00 <slaweq> #topic Blueprints 21:06:14 <slaweq> #link https://launchpad.net/neutron/+milestone/ussuri-2 21:06:53 <slaweq> Some of those BPs are getting close to be merged IMO, like e.g. port tagging during bulk create (thx mlavalle) 21:07:01 <slaweq> and ovn merge 21:07:12 <mlavalle> yeah, it is getting close but.... 21:07:22 <mlavalle> I will have to re-work it a bit 21:07:30 <slaweq> I know - internal server error which rubasov found, right? 21:08:13 <mlavalle> testing for tagging a single port creation brought to light the fact that the create ports in bulk is not passing correctly the created port to the extensions 21:08:42 <mlavalle> it is actually the create single port that is correct 21:08:50 <mlavalle> so that changes some of my assumptions 21:08:57 <mlavalle> not a major thing 21:09:07 <mlavalle> I think it will still be ready by U-2 21:09:15 <mlavalle> but it needs a bit of re-work 21:09:26 <slaweq> that's good 21:09:33 <slaweq> thx mlavalle for an update about it 21:09:43 <mlavalle> expect one patch changing the behavior of ML2 plugin 21:09:51 <slaweq> sure :) 21:09:52 <mlavalle> in rgt to create ports in bulk 21:10:07 <mlavalle> and then the patch for tagging will go on topo of it 21:10:29 <mlavalle> that's all 21:10:36 <slaweq> thx mlavalle 21:11:08 <slaweq> I have to ask tomorrow amorin about future of https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant as I know that original owner of this RFE will for sure not work on that anymore 21:15:08 <slaweq_> sorry I have some network issues 21:15:10 <slaweq_> but I'm back now 21:15:30 <slaweq_> so do You have maybe any other updates about blueprints or can we move on to the next topic? 21:16:12 <mlavalle> just regarding metadata 21:16:28 <mlavalle> I agreed with rubasov to handle the consensus part of it 21:16:39 <mlavalle> and then he will continue with the technical work 21:17:37 <slaweq> thx, I think that this is reasonable as You have a lot of "political" experience in making such stuff :) 21:19:41 <slaweq> ok, I think we can move on with next topics now, right? 21:20:15 <bcafarel> the silent attendance seems to agree :) 21:20:19 <slaweq> #topic Community goals 21:20:29 <slaweq> any updates about community goals? 21:20:52 <slaweq> njohnston_ is probably not here, so we will not have update about dropping py2 this week 21:21:24 <slaweq> and I don't have any updates about PTL docs guide yet as I totally didn't had time to look into our docs and start writing it 21:21:24 <bcafarel> related to dropping py2, oslo has started to drop py2 support too (as agreed in original planning) 21:22:14 <bcafarel> it should not affect us as we have good progress on our side, so mostly just heads-up 21:22:24 <slaweq> bcafarel: ok, but I don't think this will impact us anyhow 21:22:41 <slaweq> and thx for info about that :) 21:24:45 <slaweq> I think we can move on to the next topic then 21:24:47 <slaweq> #topic Bugs 21:24:58 <slaweq> haleyb was on bug deputy last week 21:25:13 <slaweq> haleyb: any bugs You want to share with the team now? 21:25:37 <haleyb> the critical one is related to tempest and py2/3 21:25:45 <haleyb> https://bugs.launchpad.net/neutron/+bug/1860033 21:25:45 <openstack> Launchpad bug 1860033 in tempest "Tempest jobs broken on stable branches due to requirements neutron-lib upgrade (the EOLing python2 drama)" [Critical,In progress] - Assigned to Ghanshyam Mann (ghanshyammann) 21:26:00 <haleyb> it is being actively worked 21:26:09 <bcafarel> yes, gmann++ 21:26:58 <bcafarel> this is mostly rocky (for supported branches) we got a few backports merged recently on stein and train 21:27:15 <haleyb> i think most others were picked-up or have ongoing questions 21:27:40 <haleyb> https://bugs.launchpad.net/neutron/+bug/1859887 is maybe the only one, as we won't have an l3 meeting this week 21:27:40 <openstack> Launchpad bug 1859887 in neutron "External connectivity broken because of stale FIP rule" [Undecided,New] 21:28:04 <haleyb> slaweq: does ^^^ look familiar? it did to me just couldn't place the fix 21:29:10 <slaweq> haleyb: nope, but looking at bug report I have a question 21:29:31 <slaweq> reporter of this bug included qrouter namespace and how it looks like in broken case 21:29:47 <slaweq> but it's dvr router IIUC and issue is when port don't have fip 21:30:03 <slaweq> so shouldn't traffic be sent through snat- namespace on networker node? 21:30:43 <haleyb> slaweq: yes, to me it looked like a race condition where FIP was added, then removed, but rule got left behind 21:31:28 <slaweq> haleyb: but he also said that rule which is causing problem is "54173: from 172.20.7.16 lookup 16" 21:31:54 <slaweq> and this seems for me like some rule related to fixed IP, not FIP 21:32:13 <slaweq> because 172.20.7.1/24 is subnet configured on qr- port 21:32:15 <haleyb> yes, that is the fixed IP of the port from what i can tell, it shouldn't have a rule if there is no floating 21:32:16 <slaweq> not on qg- 21:32:26 <slaweq> ahh, ok 21:33:02 <haleyb> i'll ask some more questions, would just need to reproduce it 21:33:09 <haleyb> it is stable/rocky 21:33:18 <slaweq> and maybe L3 agent logs could be useful too 21:35:33 <haleyb> that was all i had for bugs 21:35:38 <slaweq> ok, thx a lot 21:35:54 <slaweq> anyone else has got any bug which wants to discuss today? 21:37:29 <slaweq> ok, I guess this means "no" 21:37:32 <slaweq> so lets move on 21:37:34 <slaweq> next topic 21:37:38 <slaweq> #topic Neutron performance subteam 21:37:42 <slaweq> mlavalle: any updates? 21:38:04 <mlavalle> NO, unfortunatlly didn't have to work on this. I'll do my best for next time 21:38:16 <slaweq> mlavalle: sure :) 21:38:19 <slaweq> it's fine 21:38:32 <slaweq> I know that njohnston_ was recently trying to use Your profiler decorator 21:38:49 <slaweq> and he had some problems with that, did he reached to You about that? 21:38:50 <mlavalle> yes, I'm aware 21:38:55 <slaweq> great :) 21:39:43 <slaweq> ok, so lets move on to the last topic for today 21:39:50 <slaweq> #topic On demand agenda 21:40:14 <slaweq> there is nothing on the agenda page for today but maybe someone has something to talk now? 21:40:29 <slaweq> if not, we can finish this meeting earlier today 21:40:57 <bcafarel> second option looks nice :) (aka nothing from me) 21:41:07 <slaweq> bcafarel: LOL 21:41:55 <slaweq> ok, so I will listen bcafarel as I agree with him about second option :) 21:42:03 <slaweq> thx for attending today 21:42:08 <bcafarel> :) 21:42:15 <mlavalle> o/ 21:42:17 <bcafarel> o/ 21:42:23 <slaweq> have a great afternoon/night and see You online tomorrow 21:42:25 <slaweq> o/ 21:42:29 <slaweq> #endmeeting