21:01:15 #startmeeting networking 21:01:16 Meeting started Mon Jan 25 21:01:15 2016 UTC and is due to finish in 60 minutes. The chair is HenryG. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:01:17 hi! 21:01:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:01:18 hi 21:01:20 The meeting name has been set to 'networking' 21:01:26 \o/ 21:01:28 Hello everyone 21:01:29 #chair mestery 21:01:30 Current chairs: HenryG mestery 21:01:46 * mestery straps into the shotgun seat of HenryG's meeting 21:01:55 armax is traveling, so I will run the meeting and mestery will help 21:01:59 did you bring a shotgun? 21:02:05 o/ 21:02:11 o/ 21:02:17 o/ 21:02:17 Some objections were voiced about the change to Mondays only for this meeting. 21:02:24 But there has been no response to this invitation: 21:02:31 #link http://lists.openstack.org/pipermail/openstack-dev/2016-January/084556.html 21:02:39 Please read that email (and thread) and respond on the ML or in gerrit. 21:03:01 #topic Announcements 21:03:08 HenryG: I hoped someone else will raise his hand. I can step forward if no one else is ready for that... 21:03:29 go for it ihrachys 21:03:39 ok, will send a patch tomorrow. 21:04:07 sounds good ihrachys 21:04:15 First announcement ... 21:04:17 #midcycle #midcycle #midcycle #midcycle! 21:04:26 Miktaka Milestone 2 has been released 21:04:32 #link https://launchpad.net/neutron/+milestone/mitaka-2 21:04:42 Second announcement ... 21:04:49 The Nova mid-cycle sprint is in progress 21:04:56 #link https://etherpad.openstack.org/p/mitaka-nova-midcycle 21:05:06 Third announcement ... 21:05:16 The Neutron mitaka mid-cycle sprint will be on Feb 23-26 in Rochester, MN, USA 21:05:19 * salv-orlando loves this new meeting chair ;) 21:05:24 #link https://etherpad.openstack.org/p/neutron-mitaka-midcycle 21:05:32 (brrrr) 21:05:53 HenryG: ice fishing all the way! :) 21:06:04 salv-orlando: armax wanted me to get to the backlog 21:06:29 Any other announcements? 21:06:45 one preliminary here 21:07:14 we will probably have a code sprint for "objectification" some time in mid-March somewhere in Europe 21:07:26 stay tuned for more updates on the ML 21:07:45 thanks ihrachys 21:07:55 ihrachys: what would objectification be? The stuff you did for QoS applied to everything? 21:08:16 salv-orlando: that's the end goal, but we'll be tactic and do only half of everything ;) 21:08:51 we are currently looking into some core resources in context of upgrades subteam (port, network) 21:08:53 ihrachys: that would still be a rich goal 21:08:57 we'll see what we will get to 21:09:28 Let's move on to bugs 21:09:37 #topic Bugs 21:09:52 ZZelle__: Anything to report from bugs last week? 21:10:14 HenryG, 1 critical bug 21:10:34 https://bugs.launchpad.net/neutron/+bug/1537746 about to be solved 21:10:35 Launchpad bug 1537746 in neutron "l3_db should not assume dns-integration" [Critical,In progress] - Assigned to Russell Bryant (russellb) 21:11:58 a potentially critical bug: https://bugs.launchpad.net/neutron/+bug/1536540 (i wait for ajo feedback before setting this importance to critical if it's confirmed) 21:11:59 Launchpad bug 1536540 in neutron "AttributeError: 'NoneType' object has no attribute 'port_name' when deleting an instance with QoS policy attached" [Undecided,New] - Assigned to Miguel Angel Ajo (mangelajo) 21:12:18 ZZelle__: even if QoS is broken entirely it is not a 'critical' bug 21:12:21 t's not a core feature 21:12:30 amuller, oups, ok 21:12:33 + to amuller 21:13:05 (even though it's the best feature anyone could possibly ever imagine and looking at its code is like being hugged by a thousand unicorns) 21:13:18 huhum 21:13:19 * njohnston spits out his soda 21:13:55 thanks ZZelle__ 21:13:57 also does not look like actual behavioral issue. more like a nasty traceback in lots. 21:14:11 *in logs 21:14:35 I noticed a rise in the jobs failure rates over the weekend, but I think that was a blip due to the pip 8.0.0 release. The failure rates seem to be dropping back to "normal". 21:15:01 This week mlavalle is the bug deputy. 21:15:08 HenryG: Yes I am 21:15:18 Any volunteers for next week? 21:16:34 OK, after the meeting I'll have to guilt someone into volunteering :) 21:16:38 I will volunteer, though I am a little green for it. 21:17:09 njohnston: great! and no problem, you have a ton of people to pester for help 21:17:26 yay to volunteer! 21:17:40 njohnston: see the meeting wiki for the table of past deputies: 21:17:44 #link https://wiki.openstack.org/wiki/Network/Meetings 21:17:45 * russellb wanders in late and pretends he was here the whole time 21:17:48 just mark them all as opinion and then change the project to nova. that should throw a week of confusion onto it so you wont have to deal with it :) 21:18:04 HenryG: Thanks! 21:18:06 kevinbenton: hahah 21:18:22 kevinbenton: That's a hanging offense in Texas 21:18:46 Let 21:18:50 oops 21:18:54 kevinbenton: if armax ever needs what you just wrote, you're dead. 21:19:01 You know that, don't you 21:19:17 he'll have to find me first. i'm hiding in the desert 21:19:26 Let's move on to the backlog for M 21:19:37 #topic Blueprints 21:20:04 #link https://launchpad.net/neutron/+milestone/mitaka-3 21:20:45 First, https://blueprints.launchpad.net/neutron/+spec/tenant-delete 21:21:43 related question, is it okay if an HTTP DELETE request returns a body? 21:21:56 i was thinking it would be nice if this thing returned a list of all of the things it deleted 21:21:57 kevinbenton, nope 21:22:00 ok 21:22:51 Looks like that BP is out of M? 21:23:07 Most likely, I mean. 21:23:42 HenryG: +1 21:24:07 looks like it. well, it's common for High prio BPs to fall thru cracks, ain't it? 21:24:55 Still more discussions needed to agree on how and where to orchestrate, I guess. 21:25:09 kevinbenton: you should check the api-wg guidelines and if no answer there RFC 7231. But if I'm not mistaken it's a no 21:25:45 kevinbenton, after checking HTTP RFC allows response bodies in DELETE 21:25:47 next 21:25:51 https://blueprints.launchpad.net/neutron/+spec/multi-l3-backends 21:25:57 kevinbenton ? 21:26:37 in progress. should have some PoC code and a spec pushed up at the end of this week 21:26:50 still figuring out the least invasive way to do it 21:26:53 sounds good 21:26:55 next 21:27:06 https://blueprints.launchpad.net/neutron/+spec/push-notifications 21:27:11 kevinbenton: also you 21:27:27 still in spec review 21:27:36 will need a volunteer core reviewer to be my approver also 21:28:19 kevinbenton: would be glad, though there is no agreement for what I see 21:28:35 ihrachys: yes :( 21:28:46 I assume it's not Mitaka deliverable 21:28:50 chances of making M = slim? 21:28:59 yeah, partial at best 21:29:05 i assume it will need a proof of concept 21:29:11 so we can at least fix the race condition in QoS with it 21:29:23 and then worry about more objects next cycle 21:29:43 and it gives us some time to proceed with objectification first ;) 21:29:55 thanks kevinbenton and ihrachys 21:29:59 next 21:30:13 https://blueprints.launchpad.net/neutron/+spec/get-me-a-network 21:30:33 That's me, and armax and jaypipes 21:30:49 chances?.. 21:30:59 Some good feedback has been given on the patch, which I updated 21:31:19 It is being discussed and sprinted at the nova mid-cycle this week 21:31:46 We hope nova will pick up the orchestration/policy bits on their side 21:32:13 I have no idea of the feasibility of nova getting that done for M 21:32:24 We'll hear a report next week 21:32:53 sounds promising nevertheless 21:33:12 The neutron work will proceed full steam for now 21:33:38 next 21:33:48 https://blueprints.launchpad.net/neutron/+spec/external-dns-resolution 21:33:52 hi 21:34:07 mlavalle: hi 21:34:29 code merged last week: https://review.openstack.org/#/c/212213/ 21:34:59 mlavalle: is anything left? (sorry, have not followed the BP) 21:35:22 armax indicated in the blueprint that operator docs are needed. So I have already coordinated with Sam-I-Am as to what needs to be done 21:35:48 I'll update the networking guide over the next few days 21:35:53 that's it 21:35:55 mlavalle: great! and thanks as always to superdoc Sam-I-Am 21:36:01 woot 21:36:14 if you document it, they will come 21:36:28 this is a thing a lot of people have been asking about 21:36:29 too true 21:36:46 next 21:36:59 https://blueprints.launchpad.net/neutron/+spec/l2-api-extensions 21:37:18 that one is mine. the spec in review: https://review.openstack.org/263819 (armax requested some clarifications, respinned, beleive it's ready) 21:37:33 and David pushed a patch for review: https://review.openstack.org/267591 21:37:47 that one may require some respins, I need to get back to it. 21:37:56 but overall, should easily land in M 21:38:11 nice, thanks ihrachys 21:38:33 next 21:38:35 https://blueprints.launchpad.net/neutron/+spec/modular-l2-agent 21:38:45 ok, I am approver there. 21:38:54 Andreas landed some preparation patches. 21:39:09 there is also the main patch up for review: https://review.openstack.org/246318 21:39:18 I think it should be almost ready for landing 21:39:33 then there will be another patch that just moves code in another file 21:39:33 and that should be it 21:39:37 so will also land in M 21:40:12 good stuff, thanks ihrachys and Andreas 21:40:30 next 21:40:34 https://blueprints.launchpad.net/neutron/+spec/neutron-lib 21:40:42 dougwig 21:40:51 i think he's afk 21:40:51 I can report 21:41:02 Patches are landing 21:41:34 But it is a long-term ongoing effort that can be adopted gradually 21:41:53 will we have first release in M? 21:42:01 I mean, consumed by neutron 21:42:19 You can start now, it is on PyPI 21:42:27 but is it in g-r? 21:42:59 I believe so 21:43:11 * HenryG scrambles to find the review 21:43:22 https://github.com/openstack/requirements/blob/master/global-requirements.txt#L88 21:43:35 thanks :) 21:44:11 So knock yourselves out :/ 21:44:35 It has some constants you can use :) 21:45:04 next 21:45:28 https://blueprints.launchpad.net/neutron/+spec/dhcp-options-per-subnet 21:46:14 Looks like this is being re-thought 21:46:33 I'll talk to the owners later, since they are not online 21:46:33 #link https://review.openstack.org/#/c/268232/ for neutron-lib 21:46:34 yeah I think so. 21:46:44 i will follow up. 21:46:57 sorry amotoki, I expected you to be asleep :) 21:47:13 thanks amotoki 21:47:53 next 21:47:54 https://blueprints.launchpad.net/neutron/+spec/keystone-v3 21:48:01 I am the approver 21:48:16 The spec is being reviewed 21:48:33 The spec has the projected deliverables with timelines 21:49:14 The spec: https://review.openstack.org/257362 21:49:28 next 21:49:30 doesn't migration to keystoneauth help us? I think most of the work has been done actaully. 21:50:51 it seems it is trying more than that. let's move to the next one. 21:51:43 amotoki: Let's follow up with Dariusz on that 21:51:51 next 21:51:55 HenryG: ok 21:51:58 https://blueprints.launchpad.net/neutron/+spec/performance-counters 21:52:12 * regXboi wakes up 21:52:16 Hi regXboi 21:52:50 this is not likely to make M - what PoC code is there is the low level agent side and transport - still need to work out the tables and storage 21:53:06 and then passing up to the northbound consumer 21:54:07 that's all I've got 21:54:22 regXboi: thanks, that's fine as long as no one is expecting otherwise 21:54:46 HenryG: if folks are expecting otherwise, they haven't dropped me the hint 21:55:27 we'll make sure it's noted in the BP 21:55:32 next 21:56:20 actually I'm gonna stop there for today 21:56:29 #topic Open Discussion 21:56:35 5 minutes 21:56:46 i had something... 21:56:54 or is it more important to hit the docs stuff? 21:57:24 HenryG: ? 21:57:26 Sam-I-Am: we skipped the docs today to churn through the BP backlog 21:57:32 ok 21:57:40 but you can bring it up now if you want 21:57:50 quick stuff - the networking guide is now versioned 21:58:01 nice! 21:58:08 so we don't need to worry about 'in version X, you can do... in version Y, you can do..." 21:58:09 "versioned" means it has stable branches. 21:58:12 yes 21:58:28 we tried making it CD, but it didnt work out well 21:58:44 i'm working on updates for liberty (yeah, i'm behind) 21:58:53 most of them apply to mitaka too, which is aoog 21:58:54 good 21:59:20 always looking for more contributions. i can help you figure out where stuff goes. 21:59:38 the other open discussion topic - please read the 'mtu' discussion on the -dev mailing list if you haven't 21:59:43 its pretty enlightening 21:59:48 i'll be posting my results with OVS soon 22:00:15 Sam-I-Am: thanks 22:00:19 #link http://lists.openstack.org/pipermail/openstack-dev/2016-January/084241.html 22:00:37 lets solve this once and for all 22:00:38 If there is nothing else, then ... 22:00:40 Sam-I-Am: hopefully the thread will get to some actionable items 22:00:48 hope so 22:01:02 #endmeeting