openstack/placement
Code Issues Proposed changes
OpenStack resource provider inventory allocation service
10,860 Commits 10 Branches 49 Tags 21 MiB
Python 94.3%
PHP 4.4%
Shell 1.2%
3ae8653338
Go to file
Chris Dent 3ae8653338 Use a smaller base job for the perfload run 
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
2018-11-30 15:00:57 +00:00
api-ref Fix aggregate members in nested alloc candidates 2018-09-21 11:44:58 +09:00
doc Fix typo 2018-11-28 17:20:34 +08:00
etc/placement Remove [keystone] config options from placement 2018-11-28 03:07:57 +00:00
gate Add a perfload job. 2018-11-30 14:59:47 +00:00
placement Allow placement to start without a config file 2018-11-29 13:25:47 +00:00
playbooks Use a smaller base job for the perfload run 2018-11-30 15:00:57 +00:00
releasenotes Add placement-status upgrade check command 2018-11-20 13:53:07 -05:00
tools Added alembic environment 2018-11-14 15:26:13 +00:00
.coveragerc Use both unit and functional for coverage testing 2018-09-14 13:30:14 -06:00
.gitignore Clean up .gitignore file 2018-10-16 00:14:36 +09:00
.gitreview Set up initial .zuul.yaml 2018-08-31 14:24:59 +00:00
.stestr.conf Put stestr group_regex in .stestr.conf 2018-09-14 13:30:14 -06:00
.zuul.yaml Use a smaller base job for the perfload run 2018-11-30 15:00:57 +00:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Merge "Bindep does not catch missing libpcre3-dev on Ubuntu" 2018-02-14 07:31:09 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Update the HACKING.rst file 2018-09-13 16:45:23 -06:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
lower-constraints.txt Allow placement to start without a config file 2018-11-29 13:25:47 +00:00
README.rst Update README to warn of status 2018-09-10 11:11:26 -06:00
requirements.txt Allow placement to start without a config file 2018-11-29 13:25:47 +00:00
setup.cfg Add placement-status upgrade check command 2018-11-20 13:53:07 -05:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Update requirements and test-requirements 2018-09-05 21:30:42 +01:00
tox.ini Clean up and clarify tox.ini 2018-11-06 16:18:14 +00:00

README.rst

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

image

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: