15:01:25 #startmeeting neutron_routed_networks 15:01:25 Meeting started Tue Aug 2 15: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. 15:01:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:29 The meeting name has been set to 'neutron_routed_networks' 15:01:45 #topic Announcements 15:01:52 #link https://etherpad.openstack.org/p/routed-provider-networks-notes 15:02:01 Standard announcements 15:02:19 Mid-cycle is just about two weeks away in Cork, Ireland. 15:02:42 #link https://etherpad.openstack.org/p/newton-neutron-midcycle 15:03:05 I'm going. 15:03:24 me too and john-davidge too 15:03:32 We have just four weeks left until Newton-3 15:03:48 mlavalle: john-davidge: it will be great to see you there. 15:03:54 #link http://releases.openstack.org/newton/schedule.html 15:04:29 Any other announcements? 15:05:48 #topic Reviews 15:05:57 #link https://review.openstack.org/#/q/status:open+topic:bp/routed-networks 15:06:25 #link https://review.openstack.org/#/q/status:open+topic:bp/neutron-routed-networks 15:06:32 ^ these are the Nova ones. 15:06:55 I think we've done a pretty good job of whittling these down. 15:07:41 It is great to see that the deferred IP port one in Nova has just been approved. 15:07:47 ++ 15:07:51 * blogan sneaks in late 15:08:00 bad blogan 15:08:04 Many thanks to the Nova team, especially johnthetubaguy and mriedem for all their help getting this through. 15:08:41 We will continue to refine this Nova / Neutron interaction but this is a big step just to be sure that we can used deferred IP ports. 15:09:20 \o/ 15:09:24 We should include this too. 15:09:25 #link https://review.openstack.org/#/q/status:open+topic:bp/service-subnets 15:09:46 yeap 15:10:14 carl_baldwin: Thanks, the main CRUD patch is in good shape. I'll be ready to push the follow-up for review very soon 15:10:52 john-davidge: great. I look forward to reviewing that. Make sure to ping me when it is up for review. 15:11:11 carl_baldwin: Will do. Expect it by the end of today or early tomorow 15:12:23 carl_baldwin: Great news on the update from armax! Thanks 15:13:12 xiaohhui: you around? I see you're making some progress on your patches. I hope you're settling in to your new position comfortably. 15:13:14 * haleyb wakes up and looks around meeting 15:13:18 yeah 15:13:37 I did a rebase to the patch 15:13:56 Thanks 15:14:43 I'd like to get https://review.openstack.org/#/c/317358/ wrapped up. What do you think we need there/ 15:14:50 s,/,?, 15:15:55 I think we need some review to it 15:16:06 xiaohhui: I guess seeing if kevinbenton could take another quick look would be a good first step. 15:16:23 kevin will be good person for the review 15:16:24 xiaohhui: Would you mind sending him a quick note? 15:17:19 he had given some good feedback 15:17:19 I will send him a mail today 15:17:50 xiaohhui: Great. 15:18:36 I just noticed https://review.openstack.org/#/c/333716/ has made some good progress while I was away. I'll have a look at it today to see if it can be merged. 15:19:48 yeah, I think that one is ready to merge 15:20:11 +1 15:20:30 Any other work in progress that should be discussed? 15:21:22 I think our pace has continue to be pretty impressive. 15:21:52 #topic Docs 15:22:14 I dropped the ball here for a few weeks. I did start something locally but didn't get very far. 15:22:35 I'm at a point where I think I can knock out at least a rough beginning. 15:22:52 So, I'll take that action item. 15:23:43 #action carl_baldwin will knock out initial docs 15:23:50 #topic Testing 15:23:51 mlavalle: 15:24:06 we are making progress with the tempest tests 15:24:26 Bin has posted two revisions to the scenario test 15:24:40 experiencing some problems that he is working on 15:24:51 janzian is working on the api tests 15:25:20 We should have a scenario test by the end of this week 15:25:29 with the two happy paths 15:25:50 and to that we will add a connectivity test of vm's on different segments 15:26:59 #link https://review.openstack.org/#/c/347188 15:27:47 Sounds like good progress. 15:28:55 that's it this week 15:29:23 #topic Integration with Nova Scheduler 15:29:28 mlavalle: back to you. :) 15:29:52 I have started coding the interaction of Neutron with the generic resource pools api 15:30:19 I am using the client I wrote for generic resource pools 15:30:53 it's been slower that I expected. But I should have a first prototype soon 15:31:34 Sounds cool. 15:31:53 Anything to discuss? 15:32:11 Not now. I'll yell if I need help 15:32:44 Thanks. 15:32:54 #topic Service Subnets 15:33:06 john-davidge: haleyb: I guess we already talked about this a bit. 15:33:37 There was something I wanted to bring up but I'm having just a little trouble finding it. 15:33:52 carl_baldwin: Yeah I think i covered eveything from me on this 15:34:01 yes. I just pushed a new OSC patch, think it's close as well, https://review.openstack.org/#/c/342976/ 15:34:43 I remember now. 15:34:54 #link https://review.openstack.org/#/c/304647/15/neutron/services/segments/plugin.py 15:34:59 ^ I wanted to point this out. 15:35:21 #link https://review.openstack.org/#/c/304647/16/neutron/services/segments/plugin.py 15:35:25 ^ I put a TODO here. 15:35:30 I hope it makes sense. 15:36:03 * john-davidge looking 15:36:20 Basically, with service subnets and routed networks, we'll eventually have subnets that aren't attached to segments. The main one is floating IP service subnets. 15:36:26 That was my thinking anyway. 15:38:46 Yes, that sounds right to me I think 15:38:50 yes, think that makes sense 15:38:56 Either way that simplification seems sensible for now 15:39:13 It could be tricky given that a few places in code make the assumption that all of the subnets are attached to segments. 15:39:48 A fun hurdle to deal with when we come to it :) 15:40:06 But, I think we can finish the initial service subnet functionality without regard to routed networks. Then, we can look at reconciling the two. 15:40:23 One step at a time. 15:41:11 yes. i'm sure there will be some implementation details wrt the service subnet being different from the FIP subnet for example, whether we need to tweak routes/rules, etc 15:41:18 haleyb: I'll take a look at your OSC patch. 15:41:45 carl_baldwin: thanks, i might need to add more tests now that i seem to have it working 15:41:58 Anything else? 15:42:07 not from me 15:42:29 Thanks. 15:42:36 #topic Client 15:42:44 rtheis: Are you around? 15:42:55 Anything in the client being neglected? 15:42:55 carl_baldwin: yes 15:43:13 right now I'm waiting on create and delete segment in neutron to merge 15:43:32 then I can remove WIP from "network segment create" and "network segment delete" 15:43:47 rtheis: Yeah, that is one that we're focusing attention to now. 15:43:56 cool 15:44:17 carl_baldwin: are there any other client changes that are needed 15:44:43 I will review https://review.openstack.org/#/c/342976/ 15:44:45 rtheis: Off the top of my head, I can't think of any. 15:44:53 ok 15:44:59 rtheis: thanks. 15:45:14 carl_baldwin: do you think name and description will be added to segment 15:45:19 rtheis: I'll let you know if I discover any others as I'm writing the documentation. 15:45:25 ok 15:45:37 If so, then I'll have a few minor updates for that 15:45:49 rtheis: We have a patch for that. It has been somewhat neglected due to priority but I think we can start taking another look. 15:46:01 sounds good 15:46:39 nothing else 15:46:45 rtheis: Thanks. 15:46:49 #topic Open Discussion 15:47:06 Anything that we 're neglecting? 15:47:26 I am working on a patchset to return the segment id in the port dictionary 15:47:46 I only need to add unit tests. I will push it later today 15:48:22 mlavalle: Great, is that one already listed on the etherpad? It keeps slipping my mind. :( 15:48:30 it is 15:48:40 mlavalle: But, that is an important piece. I'm glad it's not slipping yours. 15:49:11 lol 15:49:36 I return the segment id in the port dictionary if the network is routed 15:50:10 Thanks, let us know when it is up. 15:50:16 and it is built on top of the work you did for the deferral attribuet 15:50:26 attribute^^^^ 15:51:16 I also want to introduce yb to the team 15:51:30 He is the one working on the tempest scenario test 15:51:54 and he will be attending this meeting from nw on to report his progress on that subject 15:51:57 yb: hi 15:52:02 hi :) 15:52:31 His name is Bin Yu and he is based out of Shanghai 15:52:41 cal_baldwin: hi:) 15:53:05 That's all fom me and yb 15:53:18 mlavalle: yb: thanks 15:53:45 Anyone else have anything? 16:01:13 carl_baldwin: endmeeting? 16:01:38 #endmeeting