Neutron Routed Networks (partial)

Registered by Matt Riedemann on 2016-06-03

In Neutron, there is a effort to support routed provider networks. A routed network in this context, is a physical network infrastructure that implements scaled networks by routing instead of large L2 broadcast domains. For example, deployers may have routers at each top-of-rack. Instead of a single VLAN covering the deployment, each rack would have its own VLAN and the routers will provide reachability to the rest of the racks over L3. Operators want Neutron to model this like a single network. This has implications for Nova scheduling.

Blueprint information

Status:
Complete
Approver:
Dan Smith
Priority:
Low
Drafter:
Carl Baldwin
Direction:
Approved
Assignee:
Carl Baldwin
Definition:
Approved
Series goal:
Accepted for newton
Implementation:
Implemented
Milestone target:
milestone icon newton-3
Started by
Matt Riedemann on 2016-06-23
Completed by
Matt Riedemann on 2016-08-02

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/neutron-routed-networks,n,z

Addressed by: https://review.openstack.org/299591
    Enable deferred IP on Neutron ports

Addressed by: https://review.openstack.org/337387
    Add Routed Networks support to Neutron API

FYI, we agreed to extend this to 7/28 (after the midcycle) to sort out anything that can get done for deferred IP allocation, but after that this is going to be frozen. -- mriedem 20160706

Addressed by: https://review.openstack.org/346278
    Abort on HostNotCompatibleWithFixedIpsClient

With https://review.openstack.org/#/c/299591/ being merged I'm considering this partially complete for the Newton release, any remaining work for neutron routed networks should happen in Ocata. -- mriedem 20160802

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.