14:01:49 #startmeeting neutron_routed_networks 14:01:50 Meeting started Tue Sep 20 14:01:49 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:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:55 The meeting name has been set to 'neutron_routed_networks' 14:01:56 #topic Announcements 14:02:13 RC-1 is out and the branch is open for Ocata. 14:02:50 There are still a few bugs remaining for Newton so we shouldn't go nuts on refactoring or anything like that. 14:03:15 We should be able to hit the Newton release within a couple of weeks. 14:03:42 I'll be honest. Since our last routed networks meeting, I've taken two days off and spent the rest working on Newton. 14:04:02 I haven't done a thing to progress routed networks. :'( 14:04:14 But, I'm getting excited to get to it very soon. 14:04:23 #topic patches 14:04:28 #undo 14:04:29 Removing item from minutes: 14:04:30 did you have fun? 14:04:42 mlavalle: yes 14:04:50 Any other announcements? 14:04:53 that's what matters ;-) 14:05:33 Not from me 14:06:57 #topic patches 14:07:12 #topic https://review.openstack.org/#/q/status:open+(topic:bp/routed-networks+OR+topic:bp/neutron-routed-networks+OR+topic:bp/service-subnets) 14:07:29 * johnthetubaguy is lurking in two meeting at once, badly 14:08:07 We don't have a lot out there. I see tests, docs, and client mostly. 14:08:42 No progress on the docs since last week. But, I'm starting to feel the pressure. 14:08:50 johnthetubaguy: hi 14:09:06 mlavalle: How are the tests coming? 14:09:27 the tests are complete as far as the functionality 14:10:01 I put a -1 on both of them (scenario and api) because we need to solve the environment issue 14:10:13 mlavalle: Makes sense. 14:10:18 I had a conversation with Assaf earlier today 14:10:24 and it is not clear yet 14:10:55 I will pursue this with Jakub this week 14:11:32 that's the status in that front 14:11:51 mlavalle: Thanks. 14:14:38 #topic Open Agenda 14:14:48 So, I don't have anything new this week. 14:15:12 Just a quick update on https://review.openstack.org/#/c/358658/ 14:15:20 Basically, we could copy / paste last week's meeting here and it would still be relevant. 14:15:43 I have finished testing all the functionality, and it works fine now 14:16:14 mlavalle: very, very cool. 14:16:40 The only missing piece is the association of aggregates to resource pools 14:17:03 waiting for this patchset to merge on the Nova side: 14:17:10 #link https://review.openstack.org/#/c/357993/ 14:17:27 johnthetubaguy: do you see this patchset merging soon?^^^^ 14:18:02 mlavalle: Do you think we should do reviews over there? 14:18:34 honestly, not 100% sure where we are at with that bit of placement 14:18:48 there was a chase to get release critical stuff in, I know that wasn't one of those bits 14:18:51 I personally don't feel I have much to add, other than reporting my findings, which I do as soon as I find anything 14:19:00 I suspect it should get into it in the next month or so 14:19:16 mlavalle: I bet your feedback has been very valuable. 14:19:24 yeah, it should be useable in devstack now (we even have some basic functional testing I believe) 14:19:31 more folks trying this out the better really! 14:19:52 johnthetubaguy: I am not really in a hurry for that. I've been testing around it. I just wanted to get a feel for pacing my own work 14:20:02 Thanks! 14:20:25 ah, understood 14:20:38 not sure at this point I am afraid 14:20:48 carl_baldwin: one question for you: can a port on a routed network have ipv4 addresses ifrom 2 subnets? 14:21:36 johnthetubaguy: but as soon as that piece is ready, I want to get it back to it, to test it and provide you guys feedback 14:21:58 I understand you are pretty much still tryin to get Newton out the door :-) 14:22:32 mlavalle: It should be able to but I haven't tested it. 14:22:44 mlavalle: I'm not sure I see a compelling use case for it. Do you? 14:23:21 Unless you include a floating IP as one of them. 14:23:21 carl_baldwin: no, I just want to know if I have to consider that case when updating the inventory on the Nova side 14:23:39 But, we still need to have the discussion about how such a floating IP will work. 14:24:36 if we create a port on the Neutron side with an address (or several) I need to update the reserved count on the Nova inventory side 14:25:10 so here's what I propose: I will assume one ipv4 address per port and I will leave a comment in the code 14:25:23 indicating that might change. Fair enough? 14:28:17 mlavalle: I don't think there is anything that actively prevents a port from having more than one. 14:28:23 mlavalle: So, I'm a little concerned about that plan. 14:28:37 in that case, we just change it 14:28:40 mlavalle: Because if someone is free to do it, someone will eventually do it. 14:29:04 I'll assume the possibility of multiple ipv4 addresses 14:29:12 I just wanted guidance 14:29:21 mlavalle: sounds good 14:29:33 That's all I have for today 14:29:40 Does anyone have anything to add? 14:34:29 going once.. 14:34:39 going twice... 14:34:41 #endmeeting