From a8cfa5abc141089878acd6077c9d57e980b69781 Mon Sep 17 00:00:00 2001 From: Artom Lifshitz Date: Sun, 21 Apr 2024 13:39:34 -0400 Subject: [PATCH] Update api-ref for 2.95: evacuate to STOPPED When we added evacuate to STOPPED in microversion 2.95 in d732ee38a1c596ab2720de51e91f83d6dbc727cf, we never updated our api-ref. This patch just adds a sentence explaining how evacuate behaves starting in 2.95. Related: bp/allowing-target-state-for-evacuate Change-Id: I1ed7211bcdd85547d3c7d8d396b6efab36b835c6 --- api-ref/source/servers-action-evacuate.inc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/api-ref/source/servers-action-evacuate.inc b/api-ref/source/servers-action-evacuate.inc index 8ae3d22093cf..a776aacae10b 100644 --- a/api-ref/source/servers-action-evacuate.inc +++ b/api-ref/source/servers-action-evacuate.inc @@ -21,6 +21,11 @@ Starting from API version 2.68, the ``force`` parameter is no longer accepted as this could not be meaningfully supported by servers with complex resource allocations. +Starting from API version 2.95, the server will remain stopped on the +destination until it is manually started. If the server should end in the same +power state on the destination as it had on the source before the evacuation, +older microversions can be used. + Normal response codes: 200 Error response codes: badRequest(400), unauthorized(401), forbidden(403),