Public bug reported: When doing a nova live migration with a destination node specified, there is a different code path to check that there is enough memory on the destination than the case where no destination is specified.
The code path for the case when a destination is specified does not check whether we are allowing overcommit through the ram_allocation_ratio setting just because it bypasses the scheduler where the allocation logic is. Since we're accepting that if the operator provides a target, all the scheduler policies are not checked then we should accept that this validation check should be removed. ** Affects: nova Importance: Medium Assignee: Sylvain Bauza (sylvain-bauza) Status: New ** Tags: conductor -- 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/1451831 Title: Specifying a destination node with nova live_migration does not take into account overcommit setting (ram_allocation_ratio) Status in OpenStack Compute (Nova): New Bug description: When doing a nova live migration with a destination node specified, there is a different code path to check that there is enough memory on the destination than the case where no destination is specified. The code path for the case when a destination is specified does not check whether we are allowing overcommit through the ram_allocation_ratio setting just because it bypasses the scheduler where the allocation logic is. Since we're accepting that if the operator provides a target, all the scheduler policies are not checked then we should accept that this validation check should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1451831/+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