Separate public and floating networks

Registered by Aleksandr Shaposhnikov on 2014-02-07

Public and floating networks should be separated. Fuel should allow the following combinations:
a) Run floating & public in same L3 subnet
b) Run separated floating & public (can be L2 separated)
c) Use multiple separated floating networks.

For >20 nodes envs, it is required to have ~2000 IPs. It is large range and not everyone has such a large subnets available, so it is required to be able to use multiple subnets.

Blueprint information

Status:
Not started
Approver:
Mike Scherbakov
Priority:
High
Drafter:
Aleksandr Shaposhnikov
Direction:
Approved
Assignee:
Fuel Python (Deprecated)
Definition:
Discussion
Series goal:
Accepted for future
Implementation:
Not started
Milestone target:
milestone icon next

Related branches

Sprints

Whiteboard

The dependent BP (advanced networking) is targeted for 6.0, so we should re-target this one as well

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.