e1783b0087
When making a GET /allocation_candidates request with the 'limit' parameter, include all the providers in the same tree as the providers mentioned in the allocation requests. That is, in a nested situation, if we limit the allocation requests to 10, we would usually expect considerably more than 10 providers in provider summaries, to include any non-contributing providers in the same tree. Accomplish this by filtering provider summaries on root_provider_uuid instead of individual provider uuid. A gabbi test is added which exercises this in a nested situation. An existing test is updated to reflect the new filtering style. It does not exercise the nested scenario. A reno is added indicating the fix. Change-Id: I136bd7cd89f1bd54f0d1691268545850af234f18 Story: 2005859 Task: 33654
If you are viewing this README on GitHub, please be aware that placement development happens on OpenStack git and OpenStack gerrit.
Team and repository tags
OpenStack Placement
OpenStack Placement provides an HTTP service for managing, selecting, and claiming providers of classes of inventory representing available resources in a cloud.
API
To learn how to use Placement's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Placement, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Placement, please see the contents of CONTRIBUTING.rst.
Further developer focused documentation is available at: