yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1988011@xxxxxxxxxxxxxxxxxx>]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

-- 
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/1988011

Title:
  The allocation ratio of ram change by placement does not work

Status in OpenStack Compute (nova):
  Expired

Bug description:
  I found that Nova will check ram_ratio in the table of compute_nodes
  in order to check whether the destination node has enough memory, when
  executing live migration instance to a target host.

  In same cases, the ram ratio in Nova is different from Placement, when
  I change the allocation_ratio by Placement API. And live migration is
  still failed when I increasing the ram ratio by Placement if it is
  deficient.

  I think the ratio in Nova should keep up with the value in Placement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1988011/+subscriptions