This is the first in a series of changes to the content in doc/source to make it more accurately reflect the current state of placement, now that it is in its own repo. There are small changes throughout the front page, mostly to make it more clear and make useful stuff a bit more discoverable. The two major changes are: * Older (pre-stein) upgrade notes are found by linking back to nova's rocky documentation. * The REST API history is moved to its own sub-page, otherwise it the page is overwhelming and noisy. Close review is probably required. cdent typed this. That has implications. Change-Id: I66e0c7d18b253b0a5a8fdac65e30b5b3cef37db2
|4 years ago|
|api-ref||4 years ago|
|doc||4 years ago|
|etc/placement||4 years ago|
|gate||4 years ago|
|placement||4 years ago|
|releasenotes||4 years ago|
|tools||4 years ago|
|.coveragerc||4 years ago|
|.gitignore||4 years ago|
|.gitreview||4 years ago|
|.stestr.conf||4 years ago|
|.zuul.yaml||4 years ago|
|CONTRIBUTING.rst||5 years ago|
|HACKING.rst||4 years ago|
|LICENSE||13 years ago|
|README.rst||4 years ago|
|babel.cfg||11 years ago|
|bindep.txt||5 years ago|
|lower-constraints.txt||4 years ago|
|requirements.txt||4 years ago|
|setup.cfg||4 years ago|
|setup.py||6 years ago|
|test-requirements.txt||4 years ago|
|tox.ini||4 years ago|
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.
Team and repository tags
OpenStack Placement provides an HTTP service for managing, selecting, and claiming providers of classes of inventory representing available resources in a cloud.
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:
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``.
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: