21:00:52 #startmeeting networking 21:00:53 Meeting started Mon Jun 24 21:00:52 2019 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:57 The meeting name has been set to 'networking' 21:01:00 o/ 21:01:05 hi 21:01:11 hello 21:01:14 hi 21:01:19 howdy 21:01:20 mlavalle: Sorry I missed the drivers meeting on Friday; I was on PTO. 21:02:11 hi 21:02:17 njohnston: no problem. we made progress on the additional ethertypes RFE 21:02:42 * mlavalle hopes njohnston enjoyed his time off 21:03:07 #topic Announcements 21:03:34 Next milestone is T-2 is week of July 22 - 26 21:04:30 Please also remember that the Shanghai Summit CFP deadline is fast approaching, July 2nd: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006262.html 21:04:54 if you are planning to propose talks, don't let that deadline catch you by surprise 21:05:16 Any other announcements 21:05:22 ? 21:05:34 just in case if anyone missed email 21:05:52 revert of patch in nova which caused failures in our gate is now merged 21:05:59 so You can recheck Your patches :) 21:06:14 thanks to mriedem 21:06:33 yes :) 21:07:10 ok, let's move on 21:07:23 #topic Blueprints 21:07:58 These are the blueprints that we are targeting for Train-2: https://launchpad.net/neutron/+milestone/train-2 21:08:34 Please note that I added 3 blueprints since last meeting: 21:08:37 1) Allow subnets from different subnet pools on the same network when using address scopes 21:08:50 https://blueprints.launchpad.net/neutron/+spec/subnets-different-pools-same-net 21:09:09 2) 2) https://blueprints.launchpad.net/neutron/+spec/neutron-classifier-neutron-qos 21:09:24 3) https://blueprints.launchpad.net/neutron/+spec/improve-extraroute-api 21:10:05 For this last one, I can see that the spec got a +2: https://review.opendev.org/#/c/655680/ 21:10:18 so if you have time please take a look 21:10:37 for 1 ^^^^, the RFE is approved and we are waiting for the code 21:11:22 I've got it in the works, should see something this week 21:11:54 Thanks :) 21:12:05 and for 2 we have a PoC patch: https://review.opendev.org/#/c/636333/ 21:12:40 anything else we should mention today in blueprints? 21:14:09 ok, let's move on 21:14:21 #topic Community goals 21:15:17 in regards to "Enabling PDF generation support for project documentation" I want to mention that the docs team is explicitely asking for a Neutron volunteer: http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007301.html 21:16:02 amotoki indicated last week that he will be working on this goal. Just want to make sure he is aware of that request from the docs team 21:17:20 and hopefully we have some folks with TeX skills (mine are a bit rusty) 21:17:47 in regards to https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html 21:18:04 523469 21:18:08 sorry 21:18:19 I was reading the last paragraph: https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html#current-state-anticipated-impact 21:18:39 does it mean that we need an ipv6 scenario test in neutron? 21:19:09 mlavalle: IIUC such job should be proposed by QA team, but I will ask gmann about details 21:19:30 so adding tempest-full-py3-ipv6 to our list? 21:19:34 (or a similar one) 21:19:43 bcafarel: probably 21:19:55 slaweq: yes, please. That is my assumption, but let's make it explicit. I don't want to drop the ball 21:20:09 mlavalle: sure, I will take care of it 21:20:23 anything else on community goals? 21:20:38 not from my side 21:21:16 just to point out there is also python 3.7 UT goal http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007284.html 21:22:14 it was not on initial list but has good progress (mostly watch on incoming reviews and fix broken things - if any) 21:22:50 Thanks for bringing it up 21:23:00 #topic Bugs 21:23:23 Last week, yamamoto was our deputy. He sent this report: http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007290.html 21:23:59 openstack help | grep log 21:25:12 I went over the list earlier today and almost everything has an owner. The thing that concerned me is that there are a couple of reports for FWaaS and one for VPNaaS 21:26:22 I am going to reach this week to Sridar and see what is his level of commitment to help with that project. njohnston_ do you want to paryicipate in that conversation? 21:26:46 mlavalle: absolutely 21:26:59 njohnston_: ok, I'll keep you in the loop 21:27:22 any other bugs we should discuss today? 21:29:47 This week the deputy is rubasov 21:30:14 Please note that after this meeting, I will rollover the calendar.... 21:30:43 That means bcafarel will be on duty next week 21:30:58 hi 21:31:06 ready to start the new rotation :) 21:31:23 FYI I'm not sure there's a report for this, but I believe https://review.opendev.org/#/c/666224/ fixes some failures in other net projects 21:31:31 and slaweq's turn will be the week after 21:31:47 mlavalle: ok 21:32:38 ok, moving on 21:32:49 #topic neutron-lib 21:33:28 boden: any updates? 21:34:07 before I give a quick update for lib, just wanted to make sure you saw my message above regarding the net projects failing and the respective fix 21:34:28 boden: I already +W this patch now 21:34:36 slaweq okay thanks 21:35:03 for neutron-lib I'll just mention there's a 1.28.0 release proposed https://review.opendev.org/#/c/666870 21:35:11 but still some testing going on it appears 21:35:30 I will keep an eye on it this week 21:35:40 other than that, just business as usual really 21:36:35 thanks for the update 21:36:44 #topic On demand agenda 21:36:52 haleyb: you have a topic 21:37:32 mlavalle: yes, i do (again) 21:37:47 you can have as many as you want 21:37:58 especially after th Bruins heartbreak 21:38:18 while investigating the ML2+OVS+DVR and OVN convergence, i wanted to propose that we setup a meeting to discuss things 21:38:31 don't get me started on the Bruins or Celtics :( 21:39:11 I assume you want a convenient time for the people in Europe, right? 21:39:26 since we don't always have time in this meeting, i figured another time would be better, and make it more Europe-friendly 21:39:41 but not weekly, maybe bi-weekly or monthly? 21:40:33 How aboout evry four weeks 21:40:42 I'm fine with either bi-weekly or monthly 21:40:51 sure, since noone really wants more meetings 21:40:54 and make it coincide with one of the Tuesday when we don't have neutron meeting 21:41:00 tomorrow for example 21:41:09 +1 for monthly (4 weeks) 21:41:27 sounds good 21:41:35 +1 21:41:38 right, that time might be good for Europe, 10am ET 21:42:01 +1 21:42:04 i'll set something up 21:42:17 +1 21:42:30 njohnst__: in 20 minutes you'll just be n______ 21:43:01 :) 21:43:18 mlavalle: that was it from me 21:43:26 haleyb: in preparation for that, are this scripts still good: https://github.com/openstack/networking-ovn/tree/master/vagrant 21:43:37 these^^^ 21:45:20 mlavalle: i don't know, can't say i use vagrant much. i did just have trouble with plain devstack today, pip versions took some figuring out, so my guess is they might need some updates 21:45:30 devstack w/ovn that is 21:45:45 haleyb: I'll give it a try then 21:45:48 thanks 21:46:05 anything else we should discuss today? 21:46:34 ok, thanks for attending 21:46:39 Have a great week 21:46:43 #endmeeting