Routing table configuration support on L3

Registered by Nachi Ueno

Adding new attribute “routes” for Router which is configuring routing table in l3-agent.
https://docs.google.com/document/d/1wDQJ00PbLY-7O-BuVLDRatP0BD57PnBZzSWFQ9ljGCk/edit

Blueprint information

Status:
Complete
Approver:
Mark McClain
Priority:
Low
Drafter:
Nachi Ueno
Direction:
Needs approval
Assignee:
Nachi Ueno
Definition:
Discussion
Series goal:
Accepted for grizzly
Implementation:
Implemented
Milestone target:
milestone icon 2013.1
Started by
Nachi Ueno
Completed by
Thierry Carrez

Related branches

Sprints

Whiteboard

This still needs design discussion, but i am setting it to grizzly, as nothing should be in code review if its not assigned to the current milestone :)

Some comments/questions:

Will there be some differentiation in terms of who can set routes and networks/destinations (internal, external, VPN)?

> In this BP, we are using specify port id, so I think no need to differentiation between them (Nachi)
> Updated, I removed port_id. so current answer is no differentiation.

Why call the attribute host_routes? Traditionally in networking, a host route refers to a /32 route. Maybe you can pick some other name to reduce risk of confusion.

> I agree. I changed host_routes -> routers (Nachi)

Gerrit topic: https://review.openstack.org/#q,topic:bp/quantum-l3-routes,n,z

Extension Support
https://review.openstack.org/#/c/19882/

Client Support
https://review.openstack.org/21042

Addressed by: https://review.openstack.org/19882
    Routing table configuration support on L3

Addressed by: https://review.openstack.org/21265
    Add support for extended attributes for extension resources

Addressed by: https://review.openstack.org/21208
    Add routed-service-insertion

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.