placement apis for inventory and allocations use insufficiently robust jsonschema
Bug #1673227 reported by
Chris Dent
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Smith | ||
Ocata |
Fix Committed
|
Medium
|
Elod Illes |
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
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Triaged → In Progress |
Changed in nova: | |
assignee: | Ed Leafe (ed-leafe) → Dan Smith (danms) |
To post a comment you must log in.
"* reserved and total need a minimum, probably of 0 and 1 respectively"
reserved should not be a min of 1.