API: Remove evacuate/live-migrate 'force' parameter
Add a new microversion that removes support for the aforementioned argument, which cannot be adequately guaranteed in the new placement world. Change-Id: I2a395aa6eccad75a97fa49e993b0300bdcfc7258 Signed-off-by: Stephen Finucane <sfinucan@redhat.com> Implements: blueprint remove-force-flag-from-live-migrate-and-evacuate APIImpact
This commit is contained in:
committed by
Matt Riedemann
parent
c1fb445b8d
commit
36a91936a8
@@ -137,6 +137,10 @@ Nova responds immediately, and no pre-live-migration checks are returned.
|
||||
The instance will not immediately change state to ``ERROR``, if a failure of
|
||||
the live-migration checks occurs.
|
||||
|
||||
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.
|
||||
|
||||
Normal response codes: 202
|
||||
|
||||
Error response codes: badRequest(400), unauthorized(401), forbidden(403)
|
||||
|
||||
Reference in New Issue
Block a user