Open Stack

Hi Swaminathan

Yes that is what I am saying also, the VPN selection is part of the “VPN Plugin”.

Not sure I get your point on the second line, if you are saying that the Infra would have to support both h/w and s/w then sure it’s a deployment condition, nothing more than that. But let me go a little bit on the ledge and say, some cases make sense for h/w and some are s/w, and this is dependent on the deployment scenario, VPN service requested, what the Dc provider has choosen etc, lots of variables, but nothing prevents both from being deployed.

Yes looked at that API, I guess more discussion in Portland will take place around that.

BR
Alan
From: Vasudevan, Swaminathan (PNB Roseville) [mailto:swaminathan.vasudevan at hp.com]
Sent: April-11-13 4:29 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Quantum] 2nd Quantum VPN discussion

Hi Alan,
Regarding hardware or software vpn should be part of the driver that we use for the vpn plugin.
But including a hardware or a virtual appliance vpn in the tenant network would require quantum infrastructure to support it.
Device registration blueprint  for LBaaS discusses about the physical and virtual devices that could be registered with the quantum for a particular advanced service plugin.
But this work is not complete yet. So we have a dependency in there.

Hope this helps.

Thanks.

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasudevan at hp.com<mailto:swaminathan.vasudevan at hp.com>

From: Alan Kavanagh [mailto:alan.kavanagh at ericsson.com]
Sent: Thursday, April 11, 2013 1:23 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Quantum] 2nd Quantum VPN discussion

This is my thinking too. I do not see a case where you will have a tenant request a physical VPN device. I see the configuration and deployment scenarios dictating when the appropriate VPN device (hardware or software) would be used. Yes it will be done in the plugin.

If folks see a reason to add an attribute to support hard or soft VPN config from the tenant it would be good to hear and discuss.

BR
Alan

From: Sachin Thakkar [mailto:sthakkar at vmware.com]
Sent: April-11-13 3:37 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Quantum] 2nd Quantum VPN discussion

The physical device will be all abstraction in the plugin layer.

As a whole, the consensus on the call was to follow the model introduced by LBaaS

Sachin
________________________________
From: "Yapeng Wu" <Yapeng.Wu at huawei.com<mailto:Yapeng.Wu at huawei.com>>
To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Sent: Thursday, April 11, 2013 10:45:33 AM
Subject: Re: [openstack-dev] [Qunatum] 2nd Quantum VPN discussion

Nachi,

I have one question regarding of the page 3 in the slide.

The "VPNGW (Physical)" here implies the physical box terminates VPN connection. Does it have to be physical device? Or physical is one of the implementation?

Thanks,
yapeng

-----Original Message-----
From: Nachi Ueno [mailto:nachi at ntti3.com]
Sent: Wednesday, April 10, 2013 9:59 PM
To: OpenStack Development Mailing List
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<mailto: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<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130411/e1e1f92f/attachment.html>