yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Oh nevermind, 0 and 1, *respectively*.

** Also affects: nova/ocata
   Importance: Undecided
       Status: New

** Changed in: nova/ocata
       Status: New => Confirmed

** Changed in: nova/ocata
   Importance: Undecided => Medium

** Changed in: nova
     Assignee: (unassigned) => Ed Leafe (ed-leafe)

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

Title:
  placement apis for inventory and allocations use insufficiently robust
  jsonschema

Status in OpenStack Compute (nova):
  Triaged
Status in OpenStack Compute (nova) ocata series:
  Confirmed

Bug description:
  In placement API v 1.4 it is possible to make inventories and
  allocations that pass the constraints of the jsonschema but are not
  correct according to the design of the system. If no values are
  provided, the defaults are incorrect as well:

  inventories:

  * It is possible to make inventories with with a min_unit or max_unit <= 0. min_unit and max_unit minimum should be 1.
  * It is possible to create a step size that is <= 0. It's minimum should be 1.
  * default for min_unit should be 1 not 0
  * default for max_unit should be a big number not 0
  * reserved and total need a minimum, probably of 0 and 1 respectively

  allocations:

  * resource consumption value must have a minimum of 1

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