Allow subnets from different subnet pools on the same network when using address scopes

Registered by Miguel Lavalle on 2019-06-24

When address scopes are used, we really only need to enforce that all subnets on a given network belong to the same address scope for each address family. This unlocks use cases for operators that allow them to build different subnet pools to be used with specific subnet service types and allocate them from different pools.

For example:

Suppose an operator has different blocks of addresses for floating IP's and FIP agent gateway ports. This change will allow the operator to manage the FIP range from one subnet pool and FIP gateway addresses from another pool, which is something they can't do today because neutron only allows subnets to be placed on the network if they are allocated from the same pool.

Blueprint information

Status:
Complete
Approver:
Miguel Lavalle
Priority:
Medium
Drafter:
Miguel Lavalle
Direction:
Approved
Assignee:
Ryan Tidwell
Definition:
Approved
Series goal:
Accepted for train
Implementation:
Implemented
Milestone target:
milestone icon train-3
Started by
Slawek Kaplonski on 2019-07-02
Completed by
Miguel Lavalle on 2019-08-05

Related branches

Sprints

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.