Hunt Xu 058469e1b9 VPNaaS integration with services flavor framework ... * adds new attribute 'flavor_id' for vpnservice * adds support for multiple drivers for VPNaaS This solution uses a flavor of service type VPN associated with a flavor profile containing a driver. During vpnservice creation, if a flavor_id is passed, it is used to find the provider for the driver which would handle the newly created vpnservice. The flavor_id and the provider-vpnservice association are pesisted in the DB. ApiImpact and DocImpact tags are added as the new optional flavor_id parameter should be described, as well as the support of multiple VPNaaS drivers. The original work and discussion about integrating VPNaaS and service type framework can be found in the following change: I9e195dfaee21b1cf204cb9b9fc773bc9e5af5936 ApiImpact DocImpact Closes-Bug: #1672920 Signed-off-by: Hunt Xu <mhuntxu@gmail.com> Change-Id: I0095e160481f1d4572e38ad1d3bbc8e183039b84		2017-07-13 18:57:25 +08:00
..
.placeholder	Add reno for release notes management	2015-12-04 10:21:33 -06:00
config-file-generation-0dcf19f5d8baaf5d.yaml	Automatically generate neutron VPNaaS configuration files	2015-12-11 11:03:33 +00:00
flavor-framework-integration-f68d28bd35ce2643.yaml	VPNaaS integration with services flavor framework	2017-07-13 18:57:25 +08:00
oslo-reports-3059c2e10e1b35b5.yaml	Add support for Guru Meditation Reports for VPNaaS agents	2016-08-29 02:25:42 +00:00