Eric Fried 388db7e6e2 placement: Return new provider from POST /rps ... To facilitate opaqueness of resource provider generation internals, we need to return the (initial) generation when a provider is created. For consistency with other APIs, we will do this by returning the entire resource provider record (which includes the generation) from POST /resource_providers. Change-Id: I8624e194fe0173531c5aa2119c903e3c68b8c6cd blueprint: generation-from-create-provider		2018-03-14 17:08:55 -05:00
..
aggregates	placement: generation in provider aggregate APIs	2018-03-14 17:08:52 -05:00
allocation_candidates	[placement] Move body examples to an isolated directory	2018-02-08 21:59:19 +00:00
allocations	[placement] Move body examples to an isolated directory	2018-02-08 21:59:19 +00:00
inventories	[placement] Move body examples to an isolated directory	2018-02-08 21:59:19 +00:00
resource_classes	[placement] Move body examples to an isolated directory	2018-02-08 21:59:19 +00:00
resource_provider_allocations	[placement] Move body examples to an isolated directory	2018-02-08 21:59:19 +00:00
resource_provider_traits	[placement] Move body examples to an isolated directory	2018-02-08 21:59:19 +00:00
resource_provider_usages	[placement] Move body examples to an isolated directory	2018-02-08 21:59:19 +00:00
resource_providers	placement: Return new provider from POST /rps	2018-03-14 17:08:55 -05:00
root	[placement] Move body examples to an isolated directory	2018-02-08 21:59:19 +00:00
traits	[placement] Move body examples to an isolated directory	2018-02-08 21:59:19 +00:00
usages	[placement] Move body examples to an isolated directory	2018-02-08 21:59:19 +00:00