15:01:28 #startmeeting neutron_routed_networks 15:01:28 Meeting started Tue Jul 5 15:01:28 2016 UTC and is due to finish in 60 minutes. The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:31 The meeting name has been set to 'neutron_routed_networks' 15:01:35 Anyone around today? 15:01:40 hello 15:01:43 hi 15:01:47 yo 15:01:57 o/ 15:02:21 Hi all. 15:02:45 #topic Announcements 15:02:55 Etherpad is here: 15:02:58 #link https://etherpad.openstack.org/p/routed-provider-networks-notes 15:03:53 Newton-2 is coming right up. It'd be very good to get a couple of things merged by then. Namely DHCP, deferred IP ports in Nova, and service subnets. 15:04:15 But, there are lots of smaller improvements that could go too. 15:04:22 Any other announcements? 15:04:43 * carl_baldwin feels like we were just here. He had a 4 day week-end away from work. 15:04:48 Remind people of the Neutron mid-cycle, August 17 - 19, Cork Ireland 15:05:13 mlavalle: Thanks. I've booked my travel. I'll be there the. 15:06:00 s/ the// 15:06:05 Anything else? 15:06:29 Talks submission deadline July 13th 15:06:33 for the Summit 15:07:07 Thanks again. 15:08:03 Moving on... 15:08:24 We've got lots of miscellaneous patches on the etherpad. Be sure to check there when you can. 15:08:48 I've been trying to make sure that all of the patches are listed on there with their status. 15:09:04 If you have a patch that isn't listed, please list it in the appropriate section. 15:10:23 We're still merging at a decent rate. So, just double check the status of your patches. 15:11:21 #topic DHCP 15:11:33 blogan said he won't be able to make it today. 15:11:46 * neiljerram slips in late 15:12:00 I'm going to try to pick up where I left off last week and get DHCP working in mlavalle 's fantastic vagrant environment. 15:12:19 * mlavalle blushes 15:13:14 I will also keep an eye on blogan'a next patchset. Janzian and I will also be testing it 15:13:26 I think we're close. I think blogan has some work to fix the problem of the agent requesting subnets on other segments and then we've got an RPC thing to fix. 15:13:31 mlavalle: great. 15:14:07 I'm going to try hard to get this fixed by Newton-2 15:14:13 Anything else on DHCP? 15:15:15 #topic Deferred IP allocation 15:15:56 I've got to close on this one 15:15:58 #link https://review.openstack.org/#/c/299591 15:16:34 I took a look yesterday and made a comment 15:17:10 mlavalle: Thanks for your comment. I was just replying. 15:17:24 I don't think it should matter if the extension is enabled the way I wrote it. 15:17:38 It will return None which will be interpreted as not deferred. 15:17:47 Just wanted to make sure it was considered 15:17:55 mlavalle: Thanks. 15:18:19 I still need to digest the rest of the conversation. I might need to ping Matt today. 15:18:57 I will also try to comment on the broader conversation, now that I have a dded a patchset to that seires 15:19:07 series^^^ 15:19:56 mlavalle: What do you mean by "added a patchset ..."? 15:20:50 I added a new patchset for the interaction with routed networks from nova. We can comment in the NOva update 15:20:57 doesn't interfere with yours 15:21:08 mlavalle: ok 15:22:13 #topic Service Subnets 15:22:30 john-davidge: haleyb: Hi, anything on this? 15:23:22 carl_baldwin: i am trying to get the WIP out so john can iterate on it, too much FTO for me last week :( 15:23:36 it's my priority today 15:23:57 haleyb: Thanks, please do everything you can to get it uploaded today, I'm ready to work on it fulltime 15:24:29 I'll be happy to take a look at it too. 15:24:35 ... when it is posted. 15:25:55 Anything else? 15:26:15 not from me 15:26:52 It is probably a stretch at this point to get this merged by Newton-2. That is fine but it'd be nice to close on it soon after. I'm willing to help anytime you need another perspective. 15:27:25 #topic Integration with Nova Scheduler 15:27:35 First of all, many thanks to johnthetubaguy and the Nova core team for merging the patchsets in the prep for network aware scheduling series up to here: 15:27:54 #link https://review.openstack.org/#/c/329851/ 15:28:41 Following johnthetubaguy advise from last week's meeting, I added this patchset on top of it: 15:28:59 #link https://review.openstack.org/#/c/337387/ 15:29:34 This patchset adds the ineraction from allocate_for_instance in Nova with the Routed Networks API 15:30:28 I made some assumptions as to the precise features in the Neutron side, because some of that is not ready yet 15:31:05 mlavalle: Do you think there is any chance to get this reviewed? 15:31:43 I have to admit I don't understand this patch's purpose yet. I need to look at it. 15:32:05 carl_baldwin: Well, it was John's advise. So I am assuming they will review it. I will certainly give it visibility on Monday's during the scheduler meeting 15:33:15 I'll take a look at it. 15:33:45 mlavalle: Do you know what the time table for the scheduler changes is? 15:33:54 mlavalle: Still targeted for Newton? 15:34:10 carl_baldwin: it is still targeted for Newton 15:34:38 Last night I started working in the Vagrant environment adding 2 aggregates 15:35:12 On top of that I want to deploy this week the g-r-p series of patchsets 15:35:20 Sounds like good progress. Keep up the good work and let me know if / when we need to help. 15:35:36 the purpose is two fold 15:35:55 1) Get a sense of how ready g-r-p is ready 15:36:16 2) Start prototyping in Neutron the interaction with that API 15:37:10 That's all for today 15:37:26 mlavalle: Good plan. 15:37:36 hi 15:37:43 #topic Open Discussion 15:37:49 What have we left out? 15:38:17 carl_baldwin, john_davige : wanted to know if l2_adjacency would be false if we have a single segment 15:39:02 tah is when l2_adjacency is true, as far as I understand it 15:39:11 reedip: I wouldn't count segments. I think if subnets are associated with segments then it should be false. 15:39:34 hmm ... okay 15:39:50 A multi-segmented network might start out as a single segment but with the intention that it become multi-segmented soon. 15:40:06 That makes sense 15:40:16 john-davidge had this comment, so wanted to know for sure 15:40:46 The intention being signaled be associating subnets to the segment 15:40:51 I don't want the value of l2adjacency to suddenly change when a new segment is added. 15:41:12 carl_baldwin: Perhaps I misunderstood the spec, but that's how I read it 15:41:41 mlavalle: ++ 15:42:01 https://specs.openstack.org/openstack/neutron-specs/specs/newton/routed-networks.html#l2-adjacency 15:42:04 john-davidge : thanks for the comment though, made things clear :) 15:42:25 according to the above ^^^ l2 adjacency should be true only if there is a single segment 15:42:41 john-davidge: Unfortunately, we didn't get some updates in to the spec. 15:42:42 :( 15:43:16 That is my mistake. I meant to get that updated but did not. 15:43:21 carl_baldwin: Ok, so the new expectation is that l2_adjeacency will be true only if the netowkr has zero segments? 15:43:26 john-davidge: yeah, that is how I read it a few months ago. But I think that we should expect this evolution in thinking happen, as we develop the functionality 15:43:56 mlavalle, john-davidge, carl_baldwin : can you review and let me know how to move forward with https://review.openstack.org/#/c/304647/ , whenever you have time? 15:44:00 carl_baldwin, john-davidge: wrestling with the code always enhance our understanding 15:44:00 john-davidge: Not really. It will be true only if there are no subnets associated with segments. 15:44:42 carl_baldwin: Ah, ok 15:45:25 john-davidge: Sorry about that confusion and thanks for your diligence. This one really is on me. I forgot that was not properly changed in the spec. 15:45:48 Yeah, in both cases the question is what subnets are associated to 15:45:54 carl_baldwin: No worries, thanks for the clarification. I guess I missed the discussion where that chnaged 15:45:55 I'll post an update to the spec but those aren't always given much priority. But, at least we'll have an update to reference. 15:46:58 #action carl_baldwin will post update to clarify l2adjacency in the spec. 15:48:08 reedip: I will review the update. 15:48:27 reedip: Thanks for your work there. 15:50:22 Anything else? 15:50:51 Late last week janzian, yb and I had a conversation about adding tempest tests for routed networks 15:51:25 janzian is going to follow up soon adding segment api support to the neutron driver in tempest 15:51:36 and the api tests 15:51:49 yb will be working on a scenario test 15:52:40 mlavalle: It will be great to have well tested code in Newton. I hope we can set a good example. 15:52:59 Yes, please tear my code apart when I get it up for review :) 15:53:07 Speaking of good examples, we also need good documentation. I started writing some but haven't completed it. 15:53:32 janzian: :) I hope that's not what I'm doing when I review. But, I like to be thorough. 15:54:12 I will recommit to creating some documentation -- at least a complete draft -- by the end of Newton-3. 15:55:47 Anything else? 15:56:00 Going once... 15:56:31 ... twice ... 15:57:02 #endmeeting