yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

When the resource tracker creates Inventory in the placement (v1.0) API
for its VCPU, MEMORY_MB, and DISK_GB, max_unit is being set to 1.

Until https://review.openstack.org/#/c/392933/ the min_unit, max_unit
and step_size constraints on Inventory were not being checked when
making Allocations. When that enforcement merges, the resource tracker
will no longer be able to make allocations of anything other than unit
1.

The immediate fix for this is for the value of max_unit to reflect the
real limits on the machine (how many cores, how much RAM, how much disk)
when creating Inventory. In the future fancier things will be possible.

** Affects: nova
     Importance: Undecided
         Status: Triaged


** Tags: placement scheduler

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

Title:
  resource tracker sets wrong max_unit in placement Inventory

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  When the resource tracker creates Inventory in the placement (v1.0)
  API for its VCPU, MEMORY_MB, and DISK_GB, max_unit is being set to 1.

  Until https://review.openstack.org/#/c/392933/ the min_unit, max_unit
  and step_size constraints on Inventory were not being checked when
  making Allocations. When that enforcement merges, the resource tracker
  will no longer be able to make allocations of anything other than unit
  1.

  The immediate fix for this is for the value of max_unit to reflect the
  real limits on the machine (how many cores, how much RAM, how much
  disk) when creating Inventory. In the future fancier things will be
  possible.

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