openstack/nova
Code Issues Proposed changes

api-ref: re-work migrate action post-conditions

Browse Source 
This is a follow up to [1] and borrows the same wording
from the resize action post-conditions except uses
"migrate(d)" instead of "resize(d)" where appropriate.

[1] I77830dfb738cd78c830dc3ce7ea88216c1eac7ef

Change-Id: Id24cb48b1b70848d2ce7020d114a843c509ab81c
This commit is contained in:
Matt Riedemann 2019-11-13 10:52:03 -05:00
parent e3b3ebed2b
commit aa0239f44d
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
api-ref/source/servers-admin-action.inc
View File

@ -68,12 +68,12 @@ this parameter, the scheduler chooses a host.
**Asynchronous Postconditions**
The server goes to a ``VERIFY_RESIZE`` status, ``RESIZED`` VM status,
and ``finished`` migration status after a successful cold migration
and then must be confirmed or reverted. If you set the
``resize_confirm_window`` option of the Compute service to a positive integer
value, the Compute service automatically confirms the migrate operation
after the set interval in seconds.
A successfully migrated server shows a ``VERIFY_RESIZE`` status and ``finished``
migration status. If the cloud has configured the `resize_confirm_window`_
option of the Compute service to a positive value, the Compute service
automatically confirms the migrate operation after the configured interval.
.. _resize_confirm_window: https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.resize_confirm_window
Policy defaults enable only users with the administrative role to
perform this operation. Cloud providers can change these permissions