Bug 1042641

Summary: [RFE][neutron]: allow multiple subnets to connect to vpn
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: Upstream M1Keywords: FutureFeature
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/vpn-multiple-subnet
Whiteboard: upstream_milestone_mitaka-1 upstream_status_implemented upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:21:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-13 00:35:48 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/vpn-multiple-subnet.

Description:

I think we should allow more than one subnet_id in one vpnservice object.

This bp will allow user to create vpn service with multiple subnets, insert subnet into vpn service or remove it from vpn service.

We will try to keep compatible with the existing one subnet API

Specification URL (additional information):

None