21:01:25 #startmeeting networking 21:01:26 Meeting started Mon Mar 4 21:01:25 2019 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:01:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:01:30 The meeting name has been set to 'networking' 21:01:39 hi 21:01:47 hi 21:01:49 hi 21:01:58 o/ 21:02:00 howdy 21:02:19 o/ 21:02:20 hi 21:02:39 #topic Announcements 21:03:12 So Team, this is it, we reached the week of Stein-3 21:04:14 We are almost at the nd of the cycle 21:04:24 That's the big one for today 21:04:35 Any other annouuncements from the team? 21:05:35 ok, let's move on then 21:05:47 #topic Blueprints 21:06:17 These are the blueprints that we are targeting for this cycle: https://launchpad.net/neutron/+milestone/stein-3 21:06:44 tidwellr: we merged the adoption of subnects, didn't we? 21:07:12 mlavalle: we did, the only missing bit now is updating the networking guide 21:07:44 are you planning to do any time soon? 21:08:00 nice, I did not see that one pass (was away last week) 21:08:13 The bulk port creation work is waiting on fixing a few tests but then I think will be ready to go. 21:09:07 njohnston: yeah I was looking at the patch earlier today. Is it fixing OVN tests? 21:10:26 mlavalle: Yes sir. I pinged the OVN folks today, will be getting help from them. 21:10:43 mlavalle: I was going to get the documentation for subnet onboard started, hopefully I can get some help to clean it up and make it presentable :) 21:11:13 njohnston: ok so I understand that on our side the action item is wait for them 21:11:27 tidwellr: yes, please push it and wewill help fixing it 21:11:49 we will be happy to wash and scrub it 21:11:58 mlavalle: I'll work closely with them to fix the issue, since it manifests in OVN but that's not to say that it couldn't be some minor issue in the ML2 changes I am making. 21:12:20 njohnston: do you need any help? 21:13:21 mlavalle: I would be happy to accept some help, yes 21:13:49 njohnston: ok, I'll ping you after the meeting to see how to help 21:13:59 mlavalle: Thanks very much! 21:14:09 in regards to https://blueprints.launchpad.net/neutron/+spec/strict-minimum-bandwidth-support 21:14:50 I was looking at the gerrit search that lajoskatona gave us last week: https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)+status:open++owner:%22Bence+Romsics+%253Cbence.romsics%2540ericsson.com%253E%22 21:15:08 it seems that there are only a couple of patches left 21:15:59 do tohers agree with my asssesment 21:16:01 ? 21:16:13 or am i missing something? 21:16:37 mlavalle: https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)+status:open 21:16:44 I think that this is better list 21:17:05 but maybe not all are necessary now 21:17:42 slaweq: so let's assume this is the list we need to work with this week 21:17:48 ok 21:18:10 unless rubasov or lajoskatona indicate otherwise 21:18:33 slaweq: since they are closer to your time zone, would you confirm with them tomorrow morning? 21:19:10 sure 21:19:23 slaweq: and I'll ping you tomorrow morning 21:19:39 You mean Your morning, right? :) 21:20:15 slaweq: yeah, that's my hope 21:20:21 :) 21:20:23 ok 21:21:12 however, there are some patches that seem obvious we need to keep an eye on. For example : https://review.openstack.org/#/c/574783/ 21:21:47 I intend to go over it at the end of this meeting 21:22:24 if we don't bind ports, we don't have feature ;-) 21:23:31 as for https://blueprints.launchpad.net/neutron/+spec/network-segment-range-management 21:23:47 I went over the three patches before this meeting 21:24:23 the CRUD / service plugin one is waiting to respond to a comment made by liuyulong 21:25:26 The with the segment type drivers I +1ed it because we are waiting for results from zuul 21:26:11 I'll +2 it when zuul finishes 21:26:26 and there is a patch with a chapter for the networking guide 21:26:48 I found minor details that need to be fixed, but seems very close 21:27:45 These are the patches: 21:27:55 https://review.openstack.org/#/c/624708/ CRUD, service plugin 21:28:17 https://review.openstack.org/#/c/624709/ segment type drivers 21:28:36 https://review.openstack.org/#/c/639110/ networking guide chapter 21:29:45 anything else we should discuss in regards to blueprints? 21:30:56 #topic Community goals 21:31:17 Any updates in regards to Python3? 21:32:21 not much 21:32:33 I am doing a sweep of the stadium to identify all the jobs still running on python2. Some of them need to, like ones keyed specifically to centos 7 (i.e. networking-midonet-tempest-aio-ml2-centos-7) but there are still many that need to be converted. 21:32:47 one thing I would like to mention is fact that now all our job in neutron are finally switched to py3 21:32:52 I plan to have the list complete and send email out by the Neutron CI meeting tomorrow. 21:33:08 we still need to do stadium projects and njohnston is doing that 21:33:24 slaweq, njohnston: good job 21:33:38 thx :) 21:33:41 thanks! 21:33:46 yeah, let's see that etherpad in the CI meeting tomorrow 21:34:12 #topic Bugs 21:34:39 Our deputy last week was manjeets 21:34:56 and this is his report: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003461.html 21:35:36 most of bugs look okay and assigned however I'd like attention on two of them 21:35:39 1. https://bugs.launchpad.net/neutron/+bug/1818015 21:35:40 Launchpad bug 1818015 in neutron "VLAN manager removed external port mapping when it was still in use" [Critical,New] 21:36:03 vlan binding getting removed for external network looks very strange 21:36:10 and its happening on queens deployment 21:36:25 and second https://bugs.launchpad.net/neutron/+bug/1817548 21:36:27 Launchpad bug 1817548 in neutron "macvtap: possible race of interfaces scan/deletion at migration" [High,New] 21:37:11 other than these most looked normal and I think are already taken care of by reporters ! 21:39:25 manjeets: I chenged the one about Vlan manager to l3-dvr-backlog 21:39:33 I mean the tag 21:40:17 could be type driver issue too but not reproduced it yet so that tag should be good for now 21:41:21 thanks 21:41:51 manjeets: good job. Thanks for the report 21:42:09 any other bugs we should discuss today? 21:42:23 hi, I have one to mention.. I think it can be quick 21:43:01 last week I think we mentioned https://bugs.launchpad.net/tricircle/+bug/1816644 21:43:02 Launchpad bug 1816644 in Tricircle "tempest-dsvm jobs don't pull required projects from source" [Undecided,New] 21:43:40 while we have a short term solution, I think we need to discuss more about if functional jobs should be testing from master or from latest release of dependencies 21:43:51 is that something we should discuss at the PTG? or should I bring it to the ML? 21:44:10 I would say let's start the discussion in the ML 21:44:23 mlavalle ok I will get something out this week 21:44:24 and we con close it in the PTG if needed 21:44:24 thx 21:44:27 ack 21:45:21 the deputy for this week is Lujin Luo 21:45:50 I'll make sure at the end of the meeting she is aware 21:45:59 #topic neutron-lib 21:46:29 boden: the stage is yours 21:47:11 so we released neutron-lib 1.25.0 last week in prep for stein... are there any plans to re-release it or is 1.25.0 still our candidate? 21:47:56 as far as I an tell, that is our candidate 21:48:05 I ask because there has been some discussion on reviews about including some of the bp/network-segment-range-management work... like https://review.openstack.org/#/c/640777/ 21:48:06 unless the team thinks otherwise 21:48:37 mlavalle ^ is the only thing I'm aware of 21:49:13 I jut went over the neutron patches of that feature and the neutron-lib patch doesn't seem to be essential 21:49:53 mlavalle ok if we don't plan to re-release lib then IMO we should not be landing any PY code in lib until we solidify neutron for stein... API ref is OK 21:50:26 I'm ok with that 21:50:28 if error raised by API will be wrong now, we can temportary handle it on neutron side also, so I think that this can wait 21:50:50 slaweq ack.. maybe you guys can comment on the patch 21:51:05 boden: I can but tomorrow :) 21:51:19 no rush slaweq . thanks 21:51:25 last; I still have a handful (or more) of consumption patches out there... do we want to try and target some for Stein or just go with the flow in terms of what we land? 21:52:05 it seems we are in good shape, based on the blueprints review 21:52:15 so let's target some 21:52:44 mlavalle... ok; let me look through and make a list of some that are realistic 21:52:51 I'll ping you 21:52:57 boden: ack 21:53:13 thanks... and that's all on the neutron-lib side of the house today 21:53:22 thanks 21:53:37 #topic On demand agenda 21:53:47 anything else we want to discuss today? 21:53:58 I would like to ask all of You for review of patch https://review.openstack.org/#/c/567369/ 21:54:05 In think it is now ready 21:54:18 ironic AFAIK don't need this old option anymore 21:54:48 thx hongbin for help with Ironic :) 21:54:49 slaweq: ack 21:55:04 slaweq ack... we have a hit in vmware-nsx... have been held up by other things breacking the UTs tho 21:55:19 I don't know if we can merge it still in Stein or should wait for Train but please take a look if You will have some time 21:55:57 anything else? 21:56:02 boden: is this option still needed for vmware-nsx? 21:56:33 slaweq no I have a patch out there to remove it... it just needs to be rebased... but vmware-nsx has been broken by other things the past week so I can't get to it 21:56:41 I will get to it soon if I can fix the gate 21:56:45 ok, thx :) 21:57:01 if You would have any issues with it, please ping me :) 21:57:12 slaweq ack and thank you 21:57:26 thanks, that's all from my side 21:57:34 ok, Thanks for attending 21:57:44 have a great week! 21:57:49 #endmeeting