Add release note for force live migration allocations
When forcing a destination host during live migration, conductor
bypasses the scheduler, performs some pre-migration checks and then
casts to the specified destination compute host directly.
With change I40b5af5e85b1266402a7e4bdeb3705e1b0bd6f3b we are still
bypassing the scheduler but conductor will attempt to allocate
resources against the specified destination host, which could fail
and result in the live migration failing even though the force flag
was specified in the API.
This change simply adds a release note for the new behavior which
was missing from the original fix.
Change-Id: I1811dfa59865c0a878522007e0070f0fde8344f0
Related-Bug: #1712008
(cherry picked from commit 02a82c41f90a64f261d81cdc0bc57471d15a7c8e)
Reviewed: https:/ /review. openstack. org/501477 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=7d220b3dd7f 9a52773604eab81 60503b05f586b3
Committed: https:/
Submitter: Jenkins
Branch: stable/pike
commit 7d220b3dd7f9a52 773604eab816050 3b05f586b3
Author: Matt Riedemann <email address hidden>
Date: Wed Sep 6 11:13:04 2017 -0400
Add release note for force live migration allocations
When forcing a destination host during live migration, conductor
bypasses the scheduler, performs some pre-migration checks and then
casts to the specified destination compute host directly.
With change I40b5af5e85b126 6402a7e4bdeb370 5e1b0bd6f3b we are still
bypassing the scheduler but conductor will attempt to allocate
resources against the specified destination host, which could fail
and result in the live migration failing even though the force flag
was specified in the API.
This change simply adds a release note for the new behavior which
was missing from the original fix.
Change-Id: I1811dfa59865c0 a878522007e0070 f0fde8344f0 261d81cdc0bc574 71d15a7c8e)
Related-Bug: #1712008
(cherry picked from commit 02a82c41f90a64f