Open Stack

On 07/28/2016 11:19 AM, Dan Smith wrote:
>>> There was some discussion that conflicted with reality a bit and I
>>> think we need to resolve before too long, but shouldn't impact the
>>> newton-based changes:
>>>
>>> We bounced around two different HTTP resources for returning one or
>>> several resource providers in response to a launch request:
>>>
>>> * POST /allocations
>>>
>>>   returns a representation of the one target for this launch
>>>   request, already claimed
>>
>> This will be in Ocata.
>
> We _do_ need the resource tracker to be reporting allocations to the
> placement service in Newton in order to allow the following call (GET
> /resource_providers) to work. Is this POST that thing or a different thing?

No. POST /allocations/{consumer_uuid} is the thing that the resource 
tracker calls for the claim on the compute node.

The POST /allocations is something we've been throwing around ideas on 
for an eventual call that the placement engine would expose for "claims 
in the scheduler".

Best,
-jay