
This changes gabbits/nested-perfload.yaml to create a tree of providers based on one of the compute nodes in the NUMANetworkFixture used in the functional tests. For the time being only one type of compute node is created (of which there will be 1000 instances). Room is left for future expansion as requirements expand. The resulting hierarchy has 7 resource providers. The allocation candidates query is: GET /allocation_candidates? resources=DISK_GB:10& required=COMPUTE_VOLUME_MULTI_ATTACH& resources_COMPUTE=VCPU:1,MEMORY_MB:256& required_COMPUTE=CUSTOM_FOO& resources_FPGA=FPGA:1& group_policy=none& same_subtree=_COMPUTE,_FPGA This is a step in the right direction but is not yet a complete exercising of all the nested functionality. It is, however, more complex than prior, notably testing 'same_subtree'. We should continue to iterate to get it doing more. Change-Id: I67d8091b464cd7b875b37766f52818a5a2faa780 Story: 2005443 Task: 35669
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: