Isolate scheduler db aggregates
Aggregate information is used by the scheduler to determine placement of instances on hosts. The aggregate information is held in the database, placed there by the aggregate api and used by the scheduler. In order to split out the scheduler this sharing of information needs to be broken such that the database deals with its own information in isolation from the rest of Nova.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Paul Murray
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Paul Murray
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Propose Isolate Scheduler DB Aggregates
Paul, can we mark this obselete since it is now completed via another blueprint in Kilo?
Yes, this is obsolete - it got lost when scheduler work was reorganized. It was in fact replaced by the other blueprint. Sorry - should have been marked obsolete when the spec was abandoned.
