Open Stack

Hi Sachin , Alan

> Sachin
Thank you for adding it.
Let's find the time to discuss
( How about launch time? )

> Alan

VPN Model-1: I am assuming the model is not restrictive to just those
3 noted VPN Service Types, we should make that explicit in this model
and others.
-> Yes exactly. We can add any types of VPNServices.

VPN Model-1 slide-2: I assume the difference in this one that model-1
is that the VPN service (VPN Tunnel End Point) is done in conjunction
by the Router.

Yes.

VPN Model-2 slide-3: Model-2 is having a dedicated physical box for
VPN only termination. I think that is fine, but in reality for at
least connecting medium-to-large tenant networks you will run the VPN
on the Site Router which will handle the Routing function for
exporting the “selected tenant networks/routes” for reachability at
the VPN end points etc.

We didn't discussed about implementation or deployment stuff like you
said. IMO, it depends on the implementation.
VPN Model2 shows some VPNService may extend network, then use the
network to connect Quantum Router (CE) to VPN Endpoint (PE).  ( One
example is BGP/MPLS vpn case)

I'm looking forward to discuss this on the Summit with you guys :)

Nachi   NTT











2013/4/11 Alan Kavanagh <alan.kavanagh at ericsson.com>:
> Thanks Sachin sorry I missed the meeting.
>
>
>
> Just some comments and questions on the VPN models, which are very good by
> the way and I might be shooting from the hip as I missed the call yesterday,
> so please shoot if that’s the case J
>
>  VPN Model-1: I am assuming the model is not restrictive to just those 3
> noted VPN Service Types, we should make that explicit in this model and
> others.
>
> VPN Model-1 slide-2: I assume the difference in this one that model-1 is
> that the VPN service (VPN Tunnel End Point) is done in conjunction by the
> Router.
>
> VPN Model-2 slide-3: Model-2 is having a dedicated physical box for VPN only
> termination. I think that is fine, but in reality for at least connecting
> medium-to-large tenant networks you will run the VPN on the Site Router
> which will handle the Routing function for exporting the “selected tenant
> networks/routes” for reachability at the VPN end points etc.
>
>
>
> Is there a reason why we talk about Physical VPN Gateway here in slide-3 ?
>
>
>
> BR
>
> Alan
>
>
>
> From: Sachin Thakkar [mailto:sthakkar at vmware.com]
> Sent: April-10-13 10:45 PM
>
>
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] [Qunatum] 2nd Quantum VPN discussion
>
>
>
> Thanks Nachi. Just to add, we'll gather folks for the next round of
> discussion on Monday during the summit which should give us ample time
> before the first VPN session on Tuesday.
>
> Thanks,
> Sachin
>
> ________________________________
>
> From: "Nachi Ueno" <nachi at ntti3.com>
> To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
> Sent: Wednesday, April 10, 2013 6:58:30 PM
> Subject: [openstack-dev] [Qunatum] 2nd Quantum VPN discussion
>
> Hi folks
>
> I would like to share the result of 2nd Quantum VPN discussion which
> held today on conf call.
>
> We discussed general model of VPN based on usecase we agreed on the 1st
> meeting.
> Current consensus is here, but we will continue model discussion on the
> Summit.
>
> In the model, each VPN extension will create each own ServiceType,
> and inject it to the Router using Service insertion.
>
> https://docs.google.com/presentation/d/1LdL0Fy9PpEQXB9q_c47iJ6gyA1oZn7B6MKbzFyk73tI/edit#slide=id.p
>
> https://etherpad.openstack.org/HavanaVPNaaS
>
> Thanks
> Nachi  NTT
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>