As generic and nested resource providers begin to crystallize and be
exercised, it becomes necessary to be able to express:
- Requesting an allocation of a particular resource class with a
particular set of traits, and requesting a *different* allocation of
the *same* resource class with a *different* set of traits.
- Ensuring that requests of certain resources are allocated from the
same resource provider.
- The ability to spread allocations of effectively-identical resources
across multiple resource providers in situations of high saturation.
This specification attempts to address these requirements by way of a
numbered syntax on resource and trait keys in flavor extra_specs and the
GET /allocation_candidates Placement API.
APIImpact
blueprint: granular-resource-requests
Change-Id: I49fb16c0e080361e6754edc64754abde3a975e14
5bdab45dd3