Horizontally Scalable (O(1)) scheduler
Add a massively scalable scheduler to Nova. By massively scalable, we mean "Schedulding a new instance on a hundred thousand node deployment with millions of current and past instances should not take more than a second."
Blueprint information
- Status:
- Complete
- Approver:
- Russell Bryant
- Priority:
- Undefined
- Drafter:
- Soren Hansen
- Direction:
- Needs approval
- Assignee:
- Rohit Karajgi
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Rohit Karajgi
- Completed by
- Rohit Karajgi
Related branches
Related bugs
Sprints
Whiteboard
I like the goal here. Note that there is also a plan emerging to split the scheduler out into its own repository. We need to reconcile this with that plan. This plan assumes scheduling that is deeply integrated with Nova. (Reference: http://
I like the goal as well, but this seems like an umbrella blueprint to me. What steps are going to be taken to reach this goal? --alaski
Deferred to icehouse-3 as the blueprint was not approved by the icehouse-2 blueprint approval deadline. --russellb
With the Gantt work in progress, and since there's no code for this yet, I'm curious if this still makes sense to be targeted to Icehouse. Does it seem reasonable to get this in? --alaski
deferred from icehouse-3 to "next": http://
Gerrit topic: https:/
Addressed by: https:/
Scalable scheduler
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyI like the goal here. Note that there is also a plan emerging to split the scheduler out into its own repository. We need to reconcile this with that plan. This plan assumes scheduling that is deeply integrated with Nova. (Reference: http://
I like the goal as well, but this seems like an umbrella blueprint to me. What steps are going to be taken to reach this goal? --alaski
Deferred to icehouse-3 as the blueprint was not approved by the icehouse-2 blueprint approval deadline. --russellb
With the Gantt work in progress, and since there's no code for this yet, I'm curious if this still makes sense to be targeted to Icehouse. Does it seem reasonable to get this in? --alaski
deferred from icehouse-3 to "next": http://
Gerrit topic: https:/
Addressed by: https:/
Scalable scheduler
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
Addressed by: https:/
Make instance scheduling horizontally scalable
