40781fbae5
Since we now have a RequestSpec object, we can directly provide it thru the RPC API select_destinations(). Since the conductor also uses the RequestSpec object, we just need to have a RPC compatibility check to see whether we can directly send the object or backport it to dicts if the scheduler is old. Note: As mox was in use for the RPC API tests, I replaced it by mock for cleaning up the test helper method. Implements blueprint request-spec-object-mitaka Change-Id: Ifd3289bf9eccab7e47cd00055b716abb8e6eb965 |
||
---|---|---|
.. | ||
__init__.py | ||
query.py | ||
report.py |