RPC support for l3 agent
At the end of Folsom, we did not have time to make the L3-agent use RPC, as a result, it uses polling, which is expensive if there are a lot of routers and router interfaces in a deployment. We should fix this to use RPC, similar to how an L2-plugin-agent uses RPC.
Blueprint information
- Status:
- Complete
- Approver:
- dan wendlandt
- Priority:
- High
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- yong sheng gong
- Definition:
- Review
- Series goal:
- Accepted for grizzly
- Implementation:
-
Implemented
- Milestone target:
-
2013.1
- Started by
- yong sheng gong
- Completed by
- yong sheng gong
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add created_at and updated_at datetime column into quantum resources.
Addressed by: https:/
l3 agent rpc blueprint rpc-for-l3-agent
----
Draft Spec for this BP: https:/
Gerrit topic: https:/
Work Items
Work items:
add updated_at and created_at to quantum resource objects: TODO
import service.py from openstack common: TODO
tranfer l3 agent to RPC: TODO
finish this BP: TODO
