This change set bases the extra_specs processing in
resources_from_flavor and resources_from_request_spec on the new
ResourceRequest class and its from_extra_specs factory method.
resources_from_flavor is used by consumers who assume the compute node
is the one and only resource provider, so here we fold all the resources
together, even if they're coming from multiple groupings in the
extra_specs. This will have to be fixed as soon as we have anything
using nested or shared RPs.
resources_from_request_spec now produces a ResourceRequest object which
is passed directly into the scheduler's get_allocation_candidates
method. However, get_allocation_candidates currently just extracts the
(unnumbered) 'resources' dict out, resulting in precisely the
pre-existing behavior. Later in the series, when GET
/allocation_candidates is prepped to accept it, this will be changed to
process the whole dict into the query string for GET
/allocation_candidates.
_process_extra_specs is no longer used, and is removed.
blueprint: granular-resource-requests
Change-Id: Ic940faabd32c2c7e6673fccab6694c5eedab272f
78167bfae3