9c7f869b84
Placement synchronizes the content of the os-traits and os-resource-classes lib to its internal DB at service startup. We had gabbi tests to test that by asserting a hard coded number of traits and RCs. These test were always blocking the global version bump of such os- libs as the placement test needed to be updated. This created a deadlock between the version bump in the requirements repo and the test update in the placement repo. To avoid the need to always do three steps for a lib version bump (turn of test, bump global req, update an re-enable the test) the test logic is changed. Now these tests compares the content of the lib with the DB automatically instead of hard coding a number of expected traits and RCs. To be able to this these tests are move from gabbi to python. Change-Id: I31431a6eb4f144135da0dc9c6d5e4c6b75d1af5d
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: