| 2017-05-23 07:17:25 |
Hidekazu Nakamura |
description |
Currently, destination_node is mandatory for migrate action.
But live migration in Nova can rely on nova-scheduler for it's destination node.
It is useful to destination node can be chosen by nova-scheduler to reduce migration error, cost of choosing destination node.
refererence: https://developer.openstack.org/api-ref/compute/?expanded=migrate-server-migrate-action-detail |
Currently, destination_node is mandatory for migrate action.
But live migration in Nova can rely on nova-scheduler for it's destination node.
It is useful destination node is optional when migration type is live:
If destination node is not given, destination node can be chosen by nova-scheduler.
If destination node is given, migrate action will do as the same as current behavior.
refererence: https://developer.openstack.org/api-ref/compute/?expanded=migrate-server-migrate-action-detail |
|
