yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

If a compute node has been reconfigured such that its allocations are
above its available capacity, the resource tracker still needs to be
able to report existing allocations without failure so that it doesn't
get in a stuck state.

To that end, we will make it so that when sending allocations via a PUT,
if those allocations are already present in the data store, will respond
with success but neither write the database, nor update the resource
provider generation. This allows the resource tracker to know "yeah,
you've got my data" and feel at peace with the state of the world.

** Affects: nova
     Importance: Undecided
     Assignee: Chris Dent (cdent)
         Status: New


** Tags: scheduler

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

Title:
  in placement api an allocation reporter sometimes needs to be able to
  report an allocation even if it violates capacity constraints

Status in OpenStack Compute (nova):
  New

Bug description:
  If a compute node has been reconfigured such that its allocations are
  above its available capacity, the resource tracker still needs to be
  able to report existing allocations without failure so that it doesn't
  get in a stuck state.

  To that end, we will make it so that when sending allocations via a
  PUT, if those allocations are already present in the data store, will
  respond with success but neither write the database, nor update the
  resource provider generation. This allows the resource tracker to know
  "yeah, you've got my data" and feel at peace with the state of the
  world.

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