3057989714
Per the discussion at the Train Forum [1] this deprecates the problematic --live option on the server migrate command which, depending on the compute API version used, forcefully bypasses the scheduler and also does not allow you to live migrate a server and let the scheduler pick a host. The --live option is replaced here with two new options: * --live-migration: this simply tells the command you want to perform a live rather than cold migration; if specified with --live the --live-migration option takes priority. * --host: when specified, this will request a target host for the live migration and will be validated by the scheduler; if not specified, the scheduler will pick a host. This option is mutually exclusive with --live. We can build on the --host option by supporting cold migrations with a specified host when using compute API version 2.56 or greater but that will come in a separate change. If the --live option is ever used we log a warning. Note there are several related changes for this issue: - https://review.openstack.org/#/c/628334/ - https://review.openstack.org/#/c/626949/ - https://review.openstack.org/#/c/627801/ - https://review.openstack.org/#/c/589012/ - https://review.openstack.org/#/c/460059/ This change allows us to deprecate the --live option and provide a replacement which is backward compatible without having to use something potentially error-prone like nargs='?'. Closes-Bug: #1411190 [1] https://etherpad.openstack.org/p/DEN-osc-compute-api-gaps Change-Id: I95d3d588e4abeb6848bdccf6915f7b5da40b5d4f
28 lines
1.2 KiB
YAML
28 lines
1.2 KiB
YAML
---
|
|
deprecations:
|
|
- |
|
|
The ``--live`` option on the ``openstack server migrate`` command has
|
|
been deprecated and is being replaced with two new options:
|
|
|
|
* ``--live-migration``: This will signal that the migration is a live
|
|
migration.
|
|
* ``--host``: This can be used to request a target host for the live
|
|
migration but requires ``--os-compute-api-version`` 2.30 or greater
|
|
so the requested host can be validated by the scheduler.
|
|
|
|
The ``--live`` option is problematic in that it requires a host and
|
|
prior to compute API version 2.30, specifying a host during live migration
|
|
will bypass validation by the scheduler which could result in failures to
|
|
actually migrate the server to the specified host or over-subscribe the
|
|
host.
|
|
|
|
The ``--live`` and ``--host`` options are mutually exclusive. Furthermore,
|
|
if both the ``--live`` and ``--live-migration`` options are used the
|
|
``--live-migration`` option takes priority.
|
|
fixes:
|
|
- |
|
|
`Bug 1411190`_ has been fixed by providing a ``--live-migration`` and
|
|
``--host`` option to the ``openstack server migrate`` command.
|
|
|
|
.. _Bug 1411190: https://bugs.launchpad.net/python-openstackclient/+bug/1411190
|