yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

The min_unit, max_unit and step_size values of resource provider
inventory are not checked when submitting allocations. Only available
capacity.

This is a known issue, a deliberate decision was made to put it off
until later, but we need to record the presence of the issue. What's
suppose to happen is that in addition to checking capacity, we also want
to make sure that the allocation is between min_unit and max_unit and
cleanly divisible by step_size. These checks should happen in the OVO
code, not the API level.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: placement

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

Title:
  placement API allocation handling does not check min_unit, max_unit,
  step_size

Status in OpenStack Compute (nova):
  New

Bug description:
  The min_unit, max_unit and step_size values of resource provider
  inventory are not checked when submitting allocations. Only available
  capacity.

  This is a known issue, a deliberate decision was made to put it off
  until later, but we need to record the presence of the issue. What's
  suppose to happen is that in addition to checking capacity, we also
  want to make sure that the allocation is between min_unit and max_unit
  and cleanly divisible by step_size. These checks should happen in the
  OVO code, not the API level.

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