19:05:23 #startmeeting quantum-vpn 19:05:24 Meeting started Fri Apr 5 19:05:23 2013 UTC. The chair is salv-orlando. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:05:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:05:27 The meeting name has been set to 'quantum_vpn' 19:05:35 salv-orlando: thanks 19:05:43 I don't know if this starts the log too however 19:05:55 it should… but… don't trust me! 19:05:56 may be :) 19:06:13 I'll also copy and paste logs 19:06:22 #topic [Agenda0] Share definitions 19:06:44 I wrote some terms of definitions. Is this OK for you guys? 19:06:53 #link https://etherpad.openstack.org/HavanaVPNaaS 19:07:09 well, it was logging even before that: http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2013-04-05.log 19:07:17 but this should give us also the minutes 19:07:24 salv-orlando: nice! 19:07:49 nanti_ueno: Thanks for writing that etherpad up, reading through parts of it now. 19:07:58 mestery: :) 19:08:15 Is Swaminathan here? 19:08:40 ah he looks trying to connect IRC 19:10:11 test from webchat 19:10:21 hm webchat looks working 19:10:29 nati_ueno: have you summarised the agenda somewhere? It might be me but it seems a bit cluttered now on the etherpad 19:10:45 salv-orlando: yes https://etherpad.openstack.org/HavanaVPNaaS L40 19:12:46 ok looks good. 19:13:26 OK I'll proxy etherpad and IRC for Swaminathan 19:14:27 can you start with an overview of the use cases? 19:14:36 just the 30,000 high ft view 19:14:47 salv-orlando: so you wanna discuss about usecase before sharing definitions? 19:15:31 if you want to start with terminology I'm fine either 19:15:43 actually as long as we start,I'm ok with it :) 19:15:57 OK the usecase also using the terminology, so let's discuss terminology first 19:16:14 Quantum Router - Quantum Router defined by Quantum V2.0 API 19:16:14 Quantum Network - Quantum Network defined by Quantum V2.0 API 19:16:14 Quantum Subnet - Quantum Subnet defined by Quantum V2.0 API 19:16:21 This three is OK? 19:16:27 Those look good, yes. 19:16:36 VPN Site - One exsting network which is connected via Network 19:17:02 Do you mean "connected via Quantum Network" here? 19:17:25 no any network 19:17:44 OK 19:17:50 may be it should be via any VPN method 19:18:08 I updated the def 19:18:16 OK, I think that is a bit clearer 19:18:38 Note: Swan added Remote Users in the definition 19:18:41 kk 19:18:47 VPN Site Group - a set of VPN Site 19:19:06 L3 Connection - Network is reachable via L3 layer 19:19:06 L2 Connection - Network is reachable via L2 layer 19:19:19 Hub - Spoke Model - Spoke site can connect to the Hub site. but spoke to spoke connection is prohibited 19:19:19 Remote Clients - Remote Users who uses the VPN Network 19:19:26 OK no problem for defs? 19:19:33 Please feel free to add new terms 19:19:40 Can we go usecase ? 19:20:00 Those all look good to me. 19:20:08 seems ok 19:20:12 ok 19:20:21 #topic [Agenda1] Identify unique use cases from various proposals (SSL/IPSEC/MPLS or other) 19:20:30 sure i think narrowing those down will be important in priorizing 19:20:44 so I summarize use case for three 19:20:50 Use case [ Router to VPN Site ] 19:20:55 Use case2 [ Network to VPN Site ] 19:21:04 Use case3 [Deffrent teant] 19:21:12 On 1. Use case [ Router to VPN Site ] 19:21:22 We will connect quantum router to VPN site 19:21:44 Assumption; All site is owned by single tenant 19:21:44 Router and VPN Site is connected by L3 connection 19:22:00 There is some variation 19:22:04 1-1. Connect Quantum Router to One VPN site 19:22:04 1-2 . Connect Quantum Router to the multiple VPN Site 19:22:04 1-2-1 both direction 19:22:05 1-2-2 hub and spoke model 19:22:12 and routing 19:22:15 1-3. Static route between connected Site (may be combination of 1-1,1-2,) 19:22:15 1.4. Dynamic routing between connected Site (may be combination of 1-1,1-2 19:22:30 Usecase 1 is clear for you guys? 19:22:45 is that in priority. i think the use case is fine 19:22:58 Looks good to me too. 19:23:02 OK let's discuss priority after we share the usecases 19:23:10 ok 2. Use case2 [ Network to VPN Site ] 19:23:19 fair enough 19:23:24 Connect Quantum Network to VPN Site directry by L2 connection 19:23:42 Use case2 is OK? 19:24:18 Swaminathan Vasudevan(HP):12:23 Looks good for me as well 19:24:25 use case 2 is an extension of a broadcast domain? 19:24:45 salv-orlando: Effectively it would have to be I think. 19:24:55 Since it's L2, it implies the same broadcast domain I think. 19:25:03 salv-orlando: is there any any variation? 19:25:18 nope, just want to make sure it was not a different kind of site-2-site 19:25:25 case 1 is L3 VPN, case 2 is L2 VPN, am I understand correctly? 19:25:34 ywu: yes 19:25:49 so if we wanna connect quantum network to vpn directory. I should be L2 19:26:05 but if there are the other way, I'll add usecase under the usecase2 19:26:35 s/I should be L2/it should be L2/ 19:26:50 Swaminathan Vasudevan(HP):12:24 Is Use case 2 similar to a Cloud Bridge 19:27:06 Swaminathan: what's a Cloud Bridge ? 19:27:18 like the company verizon bought 19:27:29 salv-orlando: thanks 19:27:41 OK usecase2 is OK for you guys? 19:27:42 a layer-2 bridge between on premise network and a network in the cloud 19:27:46 it's ok for me 19:27:56 salv-orlando: aha kind of EVPN service 19:28:13 3. Use case3 [Deffrent teant] 19:28:24 sorry typo 19:28:30 . Use case3 [Deffrent tenant] 19:28:47 so usecase 3 may be combined by usecase1 and 2 19:28:50 difference is 19:29:00 the resources are owned by different tenant 19:29:16 We should discuss permission model on usecase3 19:29:47 OK usecase3 is oK? 19:30:06 So use case 3 is letting networks from different tenants connect? 19:30:21 mestery: yes 19:30:27 i think rbac will be a separate discussion from the base object model thought, right? 19:30:31 *though 19:30:49 rbac is always orthogonal 19:30:57 sthakkar: yeah, but we should identify rbac is needed or not via Usecase discussion 19:31:10 at least for quantum API - the API police will enforce this through havana release cycle 19:31:40 nati_ueno: sure that seems fair. i think maybe we nail down the obj model and then attach rbac to each obj in the model as appropriate 19:32:04 sounds good 19:32:08 good 19:32:13 OK let's prioritize usecases 19:32:31 I think all bp is on Use case1 19:32:32 yep, simpler if we separate the two for now 19:32:34 ok sounds good 19:33:04 so IMO priority is Use case1 -> Use case2 -> Usecase 3 19:33:08 is this fair? 19:33:27 I agree with that prioritization. 19:33:40 Ok let's sort sub usecases 19:33:58 IMO, simple usecase get more high priorities 19:34:21 ah I didn't describe sub usecases yet 19:34:27 let's me explain 19:34:35 1-1. Connect Quantum Router to One VPN site 19:34:43 #info attendees agree with following priority: use case 1, use case 2, use case 3 19:34:45 this is one to one connection between router and one vpn site 19:34:57 quite simple 19:35:02 1-2 . Connect Quantum Router to the VPN Site Group 19:35:08 one to many connection 19:35:21 1-3. Static route between connected Site (may be combination of 1-1,1-2,) 19:35:29 static routing version 19:35:35 1.4. Dynamic routing between connected Site (may be combination of 1-1,1-2 19:35:56 IMO priority is 1-1,1-2,1-3,1-4 19:36:24 simple to complex 19:36:41 Is this fair? 19:36:59 Swaminathan Vasudevan(HP):12:36 My priority will be 1-1,1-3,1-2,1-4 19:37:02 makes sense from an implementation perspective 19:37:12 kk 19:37:20 OK how about 1-1,1-3,1-2,1-4 ? 19:37:33 if this is ok, I'll sort usecases 19:37:42 I think as long as 1-1 is first we're good. 19:37:51 isnt 1-2 a prereq for 3? 19:38:14 sthakkar: one site may have muliple subnet 19:38:18 sthakkar: I'll update defs 19:38:50 done 19:38:52 kk 19:38:58 Swaminathan Vasudevan(HP):12:38 I don't think there is a dependency of 1-2 for 1-3 19:39:07 OK I'll sort usecase 19:39:37 nati_ueno: I have a trivial question here. Is the quantum router itself an endpoint for the VPN in your view? 19:40:21 salv-orlando: Impl could be different, but we will connect router resource and some vpn on the resource model 19:40:56 thanks. I am not talking about implementation, but about the resource model exposed to the user. 19:41:09 through the quantum API. So there would be a VPN resource, wouldn't it? 19:41:25 salv-orlando: IMO, we should discuss the modeling after we agreed usecase 19:41:35 I do apologise for asking trivial question, my only purpose is to avoid ambiguity at all costs. 19:41:44 let's move ahead then 19:41:48 salv-orlando: kk 19:41:57 so usecases are all ok for you guys? 19:42:08 Swaminathan added Remote Clients 19:42:10 on the defs 19:42:22 How this related with usecases? 19:42:23 sounds good to me. 19:42:34 I feel we should add usecase for the term 19:43:14 IMO, any user can connect to the VPN Site, can connect the quantum router if the vpn site and quantum router is connected 19:43:45 but there could be more advanced usecase 19:43:57 It's probably best to ask Swaminathan as he's probably be envisioning a different situation. 19:44:00 Swaminathan Vasudevan(HP):12:43 We have not discussed use cases were remote warriors connect to the cloud using the vpn client 19:44:01 Alan K:12:43 I think we should take that at the end 19:44:01 Alan K:12:43 For now i think we figure out how to fullfill the use cases we have outlined 19:44:34 Swaminathan: Ah so it is not site-site connection 19:44:45 I agree with Alan K 19:44:59 Swaminathan Vasudevan(HP):12:44 ok, I am fine with that, we will discuss that at the end 19:45:10 but how we prioriteze the new usecase? 19:46:12 Swaminathan Vasudevan(HP):12:45 Priority for remote users would be 1-4 19:46:20 OK I added 19:46:22 4. Use case4 Client to the Router 19:46:23 remote warriors connect to the cloud using the vpn client 19:46:32 OK usecase is all set? 19:46:57 It sounds Ok 19:47:14 #topic [Agenda2] Possible generization of VPN related api 19:47:21 OK let's model the usecase we agreed 19:47:39 salv-orlando: It looks you have some idea, and you are lead of quantum api 19:48:00 I don't have any strong opinion yet 19:48:01 salv-orlando: could you add your modeing on the etherpad? 19:48:04 salv-orlando: ah ok 19:48:40 Swaminathan Vasudevan(HP):12:48 I have modeled API based off of the Loadbalancer approach. 19:48:40 Alan K:12:48 reason for this is HA support. I would in the use cases just go with VPN 19:48:48 I think we are at a very early stage to discuss API proposal - we can just provide general directions for the model 19:48:58 salv-orlando: I agree 19:49:04 yea salv and i have discussed one of the models 19:49:09 Alan K:12:48 so i will put it another way, VPN does not need to be terminated on an L-3 service 19:49:14 perhaps we follow the same as lb for the mount points? 19:49:50 unnamed:12:49 Alan, in user case 2, it is a L2VPN, it may address your concern 19:50:09 OK at least we should model VPN site 19:50:15 and the connection between router and vpn site 19:50:18 (usecase1-1) 19:50:41 #info the VPN use case does not need to be terminated on L3 service 19:50:43 Swaminathan Vasudevan(HP):12:50 Please take a look at my blueprint and I have captured the API 19:50:43 Alan K:12:50 not really. I think we should be careful here. VPN is a service. whether that requires L-2 or L-3 is another matter. both will be used imho 19:51:21 Swaminathan :could you add your idea about modeling on the etherpad? 19:51:22 Alan K: this would a difference between router-level or network-level plugging. Both should be allowed. 19:51:31 Alan K:12:50 ok i will look at your API this evening 19:51:31 Alan K:12:51 but if you look at the API i submitted its a good started for a "Core API" for VPN services 19:52:09 Alan K:12:51 but for sure we can add to that 19:52:14 ywu:12:51 where could I find your API, Alan? thx 19:52:31 Swaminathan Vasudevan(HP):12:52 Before we discuss the API, can we discuss the data model and then come to the API to configure the data model 19:52:38 nati_ueno: if you have more people on the hangout then IRC, just invite us there 19:52:47 this is starting to get a bit awkward 19:52:53 Yes, agree with salv-orlando. 19:53:01 salv-orlando: yeah, let's move to the etherpad 19:53:06 A meeting on the etherpad seems odd, unsure why folks can't get on IRC. 19:53:18 OK, odd though it may be, headed over there ... 19:53:29 me too for unsure the reason.. 19:53:48 ok, I'll switch to ether pad fwiw 19:53:50 #info discussion is continued on https://etherpad.openstack.org/HavanaVPNaaS 19:53:57 #endmeeting quantum-vpn 19:54:02 lol fine 19:56:51 #endmeeting quantum-vpn