Public bug reported: disable a compute node
run migration on a vm not running, it will still have to start on that compute node to do resize... next imagine that the compute node has gone down, why can't it just do a new scheduling and start running on a existing/not-disabled node? this is with shared storage btw... ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1995714 Title: cold migration shouldn't spin up the vm ins a resize step Status in OpenStack Compute (nova): New Bug description: disable a compute node run migration on a vm not running, it will still have to start on that compute node to do resize... next imagine that the compute node has gone down, why can't it just do a new scheduling and start running on a existing/not-disabled node? this is with shared storage btw... To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1995714/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp