yahoo-eng-team team mailing list archive

[OpenStack Infra <1638681@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/395971
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=00bc0cb53d6113fae9a7714386953d1d75db71c1
Submitter: Jenkins
Branch:    master

commit 00bc0cb53d6113fae9a7714386953d1d75db71c1
Author: Prateek Arora <parora@xxxxxxxxxx>
Date:   Thu Nov 10 04:09:32 2016 -0500

    Correct wrong max_unit in placement inventory
    
    When the resource tracker creates Inventory in the placement
    API for its VCPU, MEMORY_MB and DISK_GB, max_unit is set to 1.
    
    Until commit I18596a3c0f2b0049aaccd0f3e73aef90b684c4a8 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.
    
    This patch tries to fix the above stated problem by changing
    the value of max_unit to reflect the real limits on the machine
    when creating the inventory.
    
    Change-Id: I23fa868fec7f71c01e78e1a3bba5b08407c1e3ef
    Closes-bug: #1638681
    Co-Authored-By: Chris Dent <cdent@xxxxxxxxxxxxx>


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

Title:
  resource tracker sets wrong max_unit in placement Inventory

Status in OpenStack Compute (nova):
  Fix Released

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