1164497964
Based on the spec[1], the user doc[2] and the implementation[3][4] the original intention of trait filtering during allocation candidate query is that the required traits in the unnamed group needs to be provided by the resource providers contributing resources to the candidate. So traits on RPs which are in the tree of the candidate but not providing resource to the candidate should be ignored. The current API doc is not clear on this and can be misunderstood. So this patch clarifies that doc. [1] https://docs.openstack.org/placement/latest/specs/train/implemented/2005575-nested-magic-1.html [2] https://docs.openstack.org/placement/latest/user/provider-tree.html#filtering-by-traits [3]d48d22ff24/placement/objects/research_context.py (L745)[4]d48d22ff24/placement/tests/functional/db/test_allocation_candidates.py (L817-L827)Story: #2009795 Task: #44334 Change-Id: Idc367df609dc8d4874fc329f2317c582b9e06a4d
If you are viewing this README on GitHub, please be aware that placement development happens on OpenStack git and OpenStack gerrit.
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: