Address scope and Subnet-pool mapping
Starting in the Mitaka release Neutron defines and supports the use of Address Scopes. Subnet-pools were defined in the earlier Kilo release and can now be used within Address Scopes. The notion of an address scope has existed in GBP in the form of L3-Policy. The GBP L3-Policy manages the address-scope and subnet-pools with its own home-grown implementation. It would be preferable to leverage the Neutron address-scopes and subnet-pools instead.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Sumit Naiksatam
- Direction:
- Needs approval
- Assignee:
- Sumit Naiksatam
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
AIM Policy Driver - Part 5 - L3 Policies
Addressed by: https:/
AIM Policy Driver - Part 5 - L3 Policies (implicit)
Addressed by: https:/
[WIP] AIM Policy Driver - Part 7 - L3 Policies (explicit)
Addressed by: https:/
AIM Policy Driver - Part 7 - L3 Policies (explicit)
Addressed by: https:/
[WIP]AIM Policy Driver - Part 9 - Multiple explicit subnetpools
Addressed by: https:/
AIM Policy Driver - Part 9 - Multiple explicit subnetpools
Addressed by: https:/
Allow v6 subnets on routers
Addressed by: https:/
WIP: Dual-stack support for L3 Policy
Addressed by: https:/
Allow v6 subnets on routers
Addressed by: https:/
Allow v6 subnets on routers
Addressed by: https:/
Dual-stack support for L3 Policy
Addressed by: https:/
Dual-stack support for L3 Policy
