Routing table configuration support on L3
Adding new attribute “routes” for Router which is configuring routing table in l3-agent.
https:/
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:
- 2013.1
- Started by
- Nachi Ueno
- Completed by
- Thierry Carrez
Related branches
Related bugs
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/
> 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:/
Extension Support
https:/
Client Support
https:/
Addressed by: https:/
Routing table configuration support on L3
Addressed by: https:/
Add support for extended attributes for extension resources
Addressed by: https:/
Add routed-
Work Items
Dependency tree
* Blueprints in grey have been implemented.