allow multiple subnets to connect to vpn
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
Blueprint information
- Status:
- Complete
- Approver:
- Akihiro Motoki
- Priority:
- Low
- Drafter:
- Paul Michali
- Direction:
- Approved
- Assignee:
- Paul Michali
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
mitaka-1
- Started by
- Armando Migliaccio
- Completed by
- Akihiro Motoki
Related branches
Related bugs
| Bug #1459423: VPNaaS: Allow multiple local subnets for IPSec | Fix Released |
| Bug #1515670: VPNaaS: Modify neutron API users to detect multiple local subnet feature | Fix Released |
Sprints
Whiteboard
Nov-23-2015(armax): the feature is indeed implemented, but there's a problem with discoverability of the API extension, and bug #1515670 is about that.
Nov-23-2015(armax): some bugs look still open. Are we sure we can claim this implemented?
armax(Oct-19-2015): If I am not mistaken, this has been taken care of in these patches:
https:/
- server side review https:/
- client change https:/
- functional test enhancements commit https:/
- API documentation for both endpoint groups (the foundation code) and multiple local subnets, https:/
(pc_m)There are some related tasks that will need to be addressed, once the main feature is upstreamed. Provided here for reference:
- API test for new endpoint group and multiple local subnet APIs (once API tests available in neutron-vpnaas repo).
- Horizon support for multiple local subnet feature.
- Check when changing subnet in use by endpoint group (https:/
- Akihiro would like to see endpoint group API placed in an extension shim to make the API discoverable. (https:/
