yahoo-eng-team team mailing list archive

[Jay Pipes <1683377@xxxxxxxxxxxxxxxxxx>]

Turns out we don't actually need this... the set_allocations() call
ensures that inventory capacity is never exceeded.

** Changed in: nova
       Status: Triaged => Invalid

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

Title:
  [placement] PUT /allocations should include resource provider
  generations

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  The resource provider generation is used to provide consistency
  guarantees for concurrent changes to a provider's
  inventory/allocations. Because right now, the nova-compute worker
  holds a lock for the duration of any instance claim, we didn't have to
  pass a generation marker for resource providers involved in
  allocations on a compute node (because only one writer was allowed at
  a time).

  With the move to claiming in the conductor, no such lock will be used
  and we will want to pass the resource provider generation value that
  we receive from GET /resource_providers to the PUT /allocations call
  that the conductor makes.

  Therefore, we should add the generation field to the request payload
  of PUT /allocations

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