Chris Dent
3ae8653338
In this job we install placement by hand, based on the instructions in https://docs.openstack.org/placement/latest/contributor/quick-dev.html and run the placeload command against it. This avoids a lot of node set up time. * mysql is installed, placement is installed, uwsgi is installed * the database is synced * the service started, via uwsgi, which run with 5 processs each with 25 threads, otherwise writing the resource providers is very slow and causes errors in placeload. It's an 8 core vm. * placeload is called A post.yaml is added to get the generated logs back to zuul. Change-Id: I93875e3ce1f77fdb237e339b7b3e38abe3dad8f7
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: