75555e7e2c
There are some more substantial changes here, including a few things what may need to move earlier in the statck. The standard stuff: Inventory and InventoryList are now classical Python objects. * Neither make use of a self._context, so that is removed, cascading changes through some tests. * From early on Inventory used obj_set_defaults to, uh, set defaults. Now keyword args in __init__ are handling that. * However a test which was checking for out of bounds values when creating Inventory objects has been removed because it can no longer work. I feel this is safe because we have jsonschema on the HTTP API and HTTP is the interface. * Timestamp handling (in placement.util) needs some tweaks to do with objects that were never loaded from the database. The comments there should indicate what's going on. There is quite a bit of duplication shared with other *List classes. That cleanup will come. Change-Id: I1a58810e73010ccefb80967d12f283e0f7007205
Warning: This repository is currently in a state of flux as the placement service is extracted from nova. While that is happening this repository is not yet fully working.
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:
For the time being bugs in placement should be created in the Nova bug tracker with a tag of ``placement``.
Developers
For information on how to contribute to Placement, please see the contents of CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all tests.
Further developer focused documentation is available at: