14:01:25 #startmeeting neutron_routed_networks 14:01:25 Meeting started Tue Apr 5 14:01:25 2016 UTC and is due to finish in 60 minutes. The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:30 The meeting name has been set to 'neutron_routed_networks' 14:01:30 #topic Announcements 14:01:38 #link https://wiki.openstack.org/wiki/Meetings/Neutron-Routed-Networks 14:02:07 Let's see. I think the basic segment API is ready to merge. 14:02:25 #link https://review.openstack.org/#/c/296603/ 14:02:52 I hope to get someone to merge it today. 14:02:57 Any other announcements? 14:03:14 Just to mention the summit 14:03:22 it's 3 weeks away 14:03:38 Yep! Coming fast. 14:03:52 We have some sessions relevant to this effort there 14:03:59 I see some feedback from armax on the API patch. I'll address it early this morning. 14:04:14 Specifically on Wednesday, discussion with the Nova team 14:04:29 mlavalle: Do you know the specific time / session? 14:05:05 carl_baldwin: no, but I intend to follow up with mreidem to make sure we have good coverage 14:05:19 I'll update this team next week during this meeting 14:05:46 The Nova sessions on the schedule still say "tbd" 14:06:03 mlavalle: Thanks for following up on that. Hopefully, next week we'll know. 14:06:19 Any other announcements? 14:06:25 yeah, I am passing along what was commented yesterday during the scheduler meeting :-) 14:06:52 #topic Progress 14:07:24 The basic CRUD patches are pretty much ready. So, nothing to report on that. 14:07:36 #topic Associate Subnets to Segments and IPAM 14:08:17 I'm wrapping up UTs on a patch to allow association of subnets to segments. It should be ready to go by early tomorrow. 14:09:21 The next part is IPAM related. My plan is to have a patch for pluggable IPAM up for review by the end of the week. 14:10:20 The idea will be to push some concept of grouping down in to the pluggable driver so that drivers can optionally optimize queries based on groups of subnets (by network, by segment, etc.) 14:10:32 It will still work with existing IPAM drivers. 14:10:53 That's about it. 14:11:02 i look forward to it 14:11:06 hey carl_baldwin: anything we can help on? 14:11:13 #action carl_baldwin will post review for pluggable IPAM this week. 14:12:09 ski2: At the moment, I just need to get the first patch up for the IPAM part. 14:12:47 From there, it would be nice to have someone actually running the patches on their own to see what testing I may have missed and getting familiar with it. 14:12:47 carl_baldwin: did you want us to take it and run with it after you post? 14:13:16 carl_baldwin: sure thing, once you post we'll take it on 14:13:45 ski2: Thanks, we'll communicate once I've got it up. 14:14:26 I'll push really hard to get it up by the end of the week. 14:15:00 #topic Nova Scheduler 14:15:06 mlavalle: you're up. 14:15:54 So I posted a new approach to handle the coordination between Nova and Neutron in the spec https://review.openstack.org/#/c/263898/ 14:16:43 It refers specifically on how to reduce the complexity of handling use case 3 (port created in neutron with ip address) 14:17:04 I brought it up yesterday during the Nova scheduler meeting 14:17:14 No specific feedback 14:17:46 so if carl_baldwin has some time, I would like to see his reaction to it 14:18:00 mlavalle: I'm hoping we can still get that high bandwidth discussion with jaypipes and hopefully others soon. 14:18:29 yeah, me too. I can follow up with him 14:18:40 mlavalle: I read it over yesterday but I need to read it over again. I'll point out some things on the review today. 14:18:56 mlavalle: I need to read it over one more time to be sure I understood. 14:19:14 ping me if at any time if you have questions 14:19:31 My initial reaction was that it could lead to more nova boot failures than they may want. 14:19:45 i need to read it over 50 more times :) 14:20:37 #action carl_baldwin will comment on mlavalle 's approach on the nova spec. 14:20:55 The other thing I've been looking at is in re-thinking where we need to make the calls to Neutron in the Nova code 14:21:00 I encourage all to read it too. 14:21:18 I think we need to move that from the compute manager to the scheduler manager 14:21:41 I mentioned this briefly last week to carl_baldwin 14:21:54 I will elaborate that this week 14:22:20 mlavalle: What is the motivation for that? Would Nova be making calls to Neutron during scheduling? 14:23:27 Nova now to make the decision of where to place a port based on IP availability in segments 14:23:34 has to make^^^ 14:24:57 this doesn't mean we need to touch the Neutron API inside Nova. It means we need to call it from a diferent place 14:25:08 mlavalle: One thing I do know is that it is *very* important to nova that it not have to make external calls during scheduling. I tend to agree with them. 14:25:54 ok, i'll take that into consideration 14:26:11 it's something I've been thinking of and just wanted to shre it here 14:26:21 mlavalle: understood. 14:26:39 that's all I have on this topic this week 14:26:46 mlavalle: Thanks. 14:27:13 #topic Create / delete segment in ML2 14:27:37 I see it is still no owner, right? 14:27:40 This one still has no owner. I think we're going to need someone pretty familiar with ML2. 14:27:45 xiaohhui: correct. 14:27:53 I will be full back to work this week, I think I can do that. 14:28:40 I talked to rkukura about this a bit last week. He said that it was always the intention to enable create and delete of segments on an existing network. It was just never implemented. It sounded feasible. 14:29:50 Anyway, we'll keep this one on the back burner and continue to search for an owner. We might be able to use the summit to find support. 14:30:11 #action carl_baldwin will add it to the summit etherpad 14:30:45 xiaohhui: your message came in late for me. 14:31:03 bad network~ 14:31:11 xiaohhui: :) 14:31:26 xiaohhui: will that be difficult with the OVN work you're also doing? 14:32:08 I think they might be related, so I would to look them both, together. 14:32:17 xiaohhui: It will be good to get a good start on this. 14:32:54 yeah, I do think so 14:33:46 It can follow https://review.openstack.org/#/c/296658/ which I intend to rebase and get in to shape as soon as the preceding one merges. 14:34:03 That one should merge pretty quickly too I should think. 14:34:07 xiaohhui: Thanks! 14:34:37 #topic Segment aware DHCP 14:34:53 blogan talked to me yesterday about this. 14:34:58 blogan: hi 14:35:02 hello! 14:35:35 but yeah i'll certianly take this on, its definitely a knowledge gap for me but it'll be a good learning exercise even if i fall flat on my face 14:37:27 blogan: You should be able to get a start on this once you can associate subnets with segments. I have that patch *almost* ready to update. 14:37:45 okay ill start on top of that patch then 14:38:15 blogan: I'll reach out as soon as I get that one posted. 14:38:26 carl_baldwin: excellent, thanks! 14:38:51 blogan: Thank you! 14:38:55 #topic Client 14:39:00 rtheis: reedip__ : hi 14:39:05 hi 14:39:29 hello .. 14:40:00 Anything to discuss? 14:40:09 I have some issues with the neutron tests, and have fallen back on the name/desc patch 14:40:41 I will spend tomorrow to see what the problem is... 14:41:10 #link https://review.openstack.org/#/c/293305/ 14:41:51 reedip__: That patch keeps falling off my radar. I think it is because the topic is not "bp/routed-networks" 14:42:10 cant figure out the error properly.. carl_baldwin: Yeah, rtheis suggested the same 14:42:10 Working devref update for newton (https://review.openstack.org/#/c/299399/)... CLI ready once APIs are 14:43:15 rtheis: Thanks. I'll have a look at that devref too. 14:43:17 carl_baldwin: but it sounds like we won't want entire CLI CRUD since things are coming in stages on API side 14:43:45 maybe I'll break up my patches to match API 14:44:26 nothing else to report fromme 14:44:31 rtheis: that might be good. It is always strange to have an API land before the capability lands. 14:44:39 :) 14:44:49 reedip__: I'll have a look at your patch too. 14:45:00 Thanks. Anything else to discuss? 14:45:37 nothing else 14:45:57 rtheis: reedip__ Thanks. 14:46:00 #topic L2 adjacency 14:46:01 carl_baldwin : Nothing else.. I think however, you have a patch for associating segments as well ? 14:46:11 #undo 14:46:12 Removing item from minutes: 14:46:29 reedip__: Yes, I've committed to getting that patch updated by early tomorrow. 14:46:36 ok 14:47:03 reedip__: It'll be an update to https://review.openstack.org/#/c/288774/ which is now very old but I have new stuff locally. 14:47:20 carl_baldwin: ok... 14:47:34 #topic L2 adjacency 14:48:12 This'll be a pretty straight-forward task, I think. 14:48:52 Basically, just add a read-only attribute to the extension to return true or false based on the network. 14:49:04 It has no owner so I wanted to throw it out there. 14:49:30 That's all. 14:49:35 #topic Open Agenda 14:49:51 xiaohhui: Actually did you have anything regarding OVN to discuss? 14:49:56 carl_baldwin: are we going to discuss segments host mapping? 14:50:15 yeah,, I talked with russellb a little earlier. The code for ovs ovn has been implemented. Now the bridge-mapping and hostname can be found in OVN db. I will add some code in networking-ovn to read them out and use them for routed network. I had some personal affairs in the last two weeks, so I have to say sorry that I still have these in mind, not a patch for them now. I will try my best to post a patch in this week. 14:50:17 mlavalle: Is that missing from the agenda? Oops. 14:50:24 carl_baldwin: we can take the l2 adjacency as well 14:50:27 \o/ 14:50:27 carl_baldwin: can take up L2 adjacency, should help me understand a bit more ... 14:50:45 reedip__: ping me about it. 14:50:46 xiaohhui: thanks again 14:50:55 xiaohhui: no worries on delays ... i needed some time to implement those pieces in OVN 14:51:13 reedip__: ski2: Actually ski2 was in there first. 14:51:33 xiaohhui: and please let me know if you hit anything else that's needed 14:51:47 xiaohhui: Sounds like good progress. 14:51:51 ski2: can I help ?? 14:52:04 sure, thanks russellb 14:52:19 russellb: Thanks for getting to that stuff so quickly. 14:52:24 no problem 14:53:01 ski2: Can we discuss in the neutron channel later? 14:53:09 reedip__: if you want to take it, be my guest :) 14:53:14 sure thing 14:54:23 ski2: thanks ... :) 14:54:31 Anything else? 14:54:33 And this patch might need some attention https://review.openstack.org/#/c/295173/ it is just a clean up patch, no functionality 14:55:03 xiaohhui: I'll review. Thanks! 14:55:16 thank you, nothing else from me 14:55:38 If that's it... 14:55:39 going once 14:55:49 twice... 14:55:55 #endmeeting