On Wed, Aug 30, 2017 at 5:09 PM, Matt Riedemann wrote:
> Given the recent bugs [1][2] due to the force flag in the live migrate and
> evacuate APIs related to Placement, and some other long standing bugs about
> bypassing the scheduler [3], I don't think we should add the force option
> to the co
On 08/30/2017 10:56 AM, Matt Riedemann wrote:
On 8/30/2017 11:35 AM, Chris Friesen wrote:
(We might even want to fail a live migration/evacuation with a forced
destination that could cause a conflict in these non-shareable resources, but
that'd be a behaviour change and therefore a new microvers
On 8/30/2017 11:35 AM, Chris Friesen wrote:
(We might even want to fail a live migration/evacuation with a forced
destination that could cause a conflict in these non-shareable
resources, but that'd be a behaviour change and therefore a new
microversion.)
That's https://bugs.launchpad.net/nov
On 08/30/2017 09:09 AM, Matt Riedemann wrote:
Given the recent bugs [1][2] due to the force flag in the live migrate and
evacuate APIs related to Placement, and some other long standing bugs about
bypassing the scheduler [3], I don't think we should add the force option to the
cold migrate API, a
Given the recent bugs [1][2] due to the force flag in the live migrate
and evacuate APIs related to Placement, and some other long standing
bugs about bypassing the scheduler [3], I don't think we should add the
force option to the cold migrate API, as (re-)proposed in Takashi's cold
migrate sp
