yahoo-eng-team team mailing list archive

[OpenStack Infra <1619722@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/365068
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=09627f2a0bd0c4ad05671d4646557066e606f2ad
Submitter: Jenkins
Branch:    master

commit 09627f2a0bd0c4ad05671d4646557066e606f2ad
Author: Chris Dent <cdent@xxxxxxxxxxxxx>
Date:   Fri Sep 2 15:58:38 2016 +0000

    [placement] Allow inventory to violate allocations
    
    When a compute node is reconfigured to have different inventory it
    needs to be able to tell the placement service of these changes,
    even if they violate existing allocations. Thus, when updating
    inventory we no longer check the new capacity against existing
    allocations, we just let it happen (but log a warning).
    
    This is safe because allocations in excess of capacity will still
    prevent resources from being used.
    
    Change-Id: I48ae1d7cd6bc309243493ddac99ce990c0146534
    Closes-Bug: #1619722
    Co-Authored-By: Dan Smith <dansmith@xxxxxxxxxx>


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

Title:
  in placement api we must be able to update inventory to violate
  allocations

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  If a compute node is reconfigured in a way that makes its inventory
  change, those changes must be reflected in the placement service, even
  if they violate the existing allocations, otherwise the node is left
  in a difficult state.

  This is safe because with this new inventory the node won't be
  scheduled to: it doesn't have available capacity.

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