3d696b2207
Now we have `placement-manage db sync` CLI, which upgrades the placement DB to the current version using alembic. However, if you have already created tables in placement, the command fails on having the initial upgrade: (initial) -> (b4ed3a175331). This is because it assumes the initial DB has no contents and tries to create the tables. Since this can be a problem for nova-api -> placement migration case, where we expect placement DB has tables before starting alembic version mangement via the migration script in `tools/*-migrate-db.sh`, this patch provides a way to stamp the current version via the CLI: `placement-manage db stamp <version>`. Change-Id: I65fa8fd6e2479224f1b25cd62ca15a90d5948424
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: