Reviewed: https://review.openstack.org/392933 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b000989635be95a1548a983d290d16492b436571 Submitter: Jenkins Branch: master
commit b000989635be95a1548a983d290d16492b436571 Author: Chris Dent <[email protected]> Date: Wed Nov 2 18:42:21 2016 +0000 [placement] Enforce min_unit, max_unit and step_size Add support for checking min_unit, max_unit and step_size when making allocations to the placement API. When the constraints are violated a new exception InvalidAllocationConstraintsViolated is raised. Change-Id: I18596a3c0f2b0049aaccd0f3e73aef90b684c4a8 Closes-Bug: #1623545 ** Changed in: nova Status: In Progress => Fix Released -- 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): Fix Released 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
