Nova should support drive_type and drive_version priority scheduling on live_migration
Registered by
warewang
In the process of live_migration, if the user does not specify the destination, the scheduler will choose a suitable host, but the scheduler can not choose hosts according to the driver_type and driver_version in the existing scheduling method, especially in a heterogeneous environment, it will lead to the migration failure probability increased, so I think the OpenStack as an excellent choice should be able to deal with this situation.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- warewang
- Direction:
- Needs approval
- Assignee:
- zhangtralon
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add drivertype priority scheduling on migration
Addressed by: https:/
Add drivertype priority scheduling on migration
(?)
