Enable adoption of an existing subnet into a subnetpool
It is currently not possible to take an existing subnet and move it into a subnetpool or address scope. The subnetpool_id attribute on subnets is not updateable, meaning that once a subnet is created it cannot be moved between subnetpools or address scopes. If a subnet was created without a subnetpool_id, it still cannot be moved into a subnetpool or address scope. This is a barrier to the adoption features like subnetpools, address scopes, and BGP. Many users likely have existing subnets that they would prefer to not destroy and re-create just for the purpose of being able to use these features.
Blueprint information
- Status:
- Complete
- Approver:
- Miguel Lavalle
- Priority:
- High
- Drafter:
- Ryan Tidwell
- Direction:
- Approved
- Assignee:
- Ryan Tidwell
- Definition:
- Approved
- Series goal:
- Accepted for rocky
- Implementation:
-
Implemented
- Milestone target:
-
stein-3
- Started by
- Armando Migliaccio
- Completed by
- Slawek Kaplonski
Related branches
Related bugs
| Bug #1558812: [RFE] Enable adoption of an existing subnet into a subnetpool | Fix Released |
Sprints
Whiteboard
May-18-2017(armax): giving this another shot.
Oct-31-2016(armax): deferred due to lack of resources.
Sep-12-2016(armax): deferred to Ocata
Jul 25, 2016 (carl_baldwin): Ryan has been playing with this and it was stuck on discussing the API. We've just had that discussion and code should show up soon. This won't be a large effort.
Gerrit topic: https:/
Addressed by: https:/
[WIP] Enable adoption of subnets into a subnet pool
Addressed by: https:/
[WIP] Enable adoption of subnets into a subnet pool
Addressed by: https:/
Add API Definition for Subnet Onboard
Addressed by: https:/
Add support to Create/Update subnets in subnet_onboard
Gerrit topic: https:/
Addressed by: https:/
Fix default value of subnet attribute for subnet onboard
Addressed by: https:/
Remove unnecessary attributes and specs from subnet_onboard API
Addressed by: https:/
Add documentation for subnet onboard
