VM migration ordering
Currently the list of VM migrations generated by a strategy engine is not ordered. It needs to be ordered to respect compute node resource constraints such as available RAM and CPUs. There is an existing project which implements an algorithm to determine this ordering. It is only a proof of concept but as it is Python it could possibly be integrated into Watcher to solve this problem:
https:/
We need to integrate it into a new strategy (copy an existing one) :
- we need to remove existing cluster constraints (a VM should be allowed to move to an overloaded node at least temporary)
- we need to ckeck that this strategy do not generate a large amount of useless migrations as we won't take into account the current cluster state
Blueprint information
- Status:
- Not started
- Approver:
- Jean-Emile DARTOIS
- Priority:
- Undefined
- Drafter:
- Adam Spiers
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Work Items
Dependency tree
* Blueprints in grey have been implemented.