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
This commit is contained in:
Artom Lifshitz 2024-04-21 13:39:34 -04:00
parent 3abea334d5
commit a8cfa5abc1

View File

@ -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),