Improve DVR router sheduling mechanism for better performance/scalability
Neutron code does not properly handle scheduling for DVR and often confuses why a router has been scheduled to an L3 agent, especially in cases where an agent could host both the centralized and a distributed piece of the router.
Blueprint information
- Status:
- Complete
- Approver:
- Carl Baldwin
- Priority:
- Low
- Drafter:
- Carl Baldwin
- Direction:
- Approved
- Assignee:
- Oleg Bondarev
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
mitaka-3
- Started by
- Oleg Bondarev
- Completed by
- Oleg Bondarev
Related branches
Related bugs
Sprints
Whiteboard
Feb 2, 2016 (carl_baldwin): This is finished and I believe that it had the desired effect. A lot of scheduling stuff was simplified and I believe the end-user experience is improve too. Thanks, Oleg!
Jan-24-2016(armax): looks on track. It's unclear if the backlog includes all there is to it.
Dec-07-2015(armax): this is a blank canvas, more details must be provided.
Gerrit topic: https:/
Addressed by: https:/
Improve bindings of DVR routers to L3 agents
Addressed by: https:/
Introduce new query to return all hosts for DVR router
Addressed by: https:/
Introduce new queries to return DVR routers for a host
Addressed by: https:/
Remove duplicate for check_ports_
Addressed by: https:/
Bring more consistency in getting l3 agents hosting router
Addressed by: https:/
Refactor remove_
Addressed by: https:/
HA for DVR - Neutron Server side code changes
Gerrit topic: https:/
Addressed by: https:/
Bing back dvr routers autoscheduling
Addressed by: https:/
Remove useless unit tests in test_l3_
