From 55c86166326069f9fdf156b60d63f9f20b80f957 Mon Sep 17 00:00:00 2001 From: tianhui Date: Thu, 31 May 2018 11:53:04 +0800 Subject: [PATCH] Fix bug to api-ref The API reference for the server 'migrate' (cold migrate) action doesn't mention any asynchronous post conditions. We should have something similar to what's in the 'resize' action API reference. Change-Id: I596b95cbd276e8d16a1cc8ce20d77f0ff6985317 Closes-bug: #1774234 --- api-ref/source/servers-admin-action.inc | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/api-ref/source/servers-admin-action.inc b/api-ref/source/servers-admin-action.inc index f266b557e5f5..e86e3e63f16f 100644 --- a/api-ref/source/servers-admin-action.inc +++ b/api-ref/source/servers-admin-action.inc @@ -65,6 +65,15 @@ Starting from microversion 2.56, the ``host`` parameter is available to specify the destination host. If you specify ``null`` or don't specify 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. + Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the ``policy.json`` file.