openstack
/
placement
Code Issues Proposed changes
OpenStack resource provider inventory allocation service
11,231 Commits 9 Branches 46 Tags 21 MiB
Python 93%
PHP 4.3%
Shell 2.6%
Go to file
Chris Dent 8723bd7772 Nested provider performance testing 
This change duplicates the ideas started in with the placement-perfload
job and builds on it to create a set of nested trees that can be
exercised.

In placement-perfload, placeload is used to create the providers. This
proves to be cumbersome for nested topologies so this change starts
a new model: Using parallel [1] plus instrumented gabbi to create
nested topologies in a declarative fashion.

gate/perfload-server.sh sets up placement db and starts a uwsgi server.

gate/perfload-nested-loader.sh is called in the playbook to cause gabbi
to create the nested topology described in
gate/gabbits/nested-perfload.yaml. That topology is intentionally very
naive right now but should be made more realisitc as we continue to
develop nested features.

There's some duplication between perfload.yaml and
nested-perfload.yaml that will be cleared up in a followup.

[1] https://www.gnu.org/software/parallel/ (although the version on
ubuntu is a non-GPL clone)

Story: 2005443
Task: 30487
Change-Id: I617161fde5b844d7f52dc766f85c1b9f1b139e4a
 		2019-06-20 12:37:28 +01:00
api-ref Implement allocation candidate mappings 2019-06-12 21:19:14 +00:00
doc Optionally run a wsgi profiler when asked 2019-06-05 19:41:18 +00:00
etc/placement Add olso.middleware.cors to conf generator 2019-05-28 15:29:55 +01:00
gate Nested provider performance testing 2019-06-20 12:37:28 +01:00
placement Uniquify allocation mappings 2019-06-17 11:16:34 +01:00
placement_db_tools Package db migration scripts in placement pypi dist 2019-05-07 00:08:39 +00:00
playbooks Nested provider performance testing 2019-06-20 12:37:28 +01:00
releasenotes Implement allocation candidate mappings 2019-06-12 21:19:14 +00:00
tools Package db migration scripts in placement pypi dist 2019-05-07 00:08:39 +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 OpenDev Migration Patch 2019-04-19 19:41:22 +00:00
.stestr.conf Put stestr group_regex in .stestr.conf 2018-09-14 13:30:14 -06:00
.zuul.yaml Nested provider performance testing 2019-06-20 12:37:28 +01:00
CONTRIBUTING.rst Update CONTRIBUTING and HACKING 2019-03-11 18:28:36 +00:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
README.rst Replace git.openstack.org URLs with opendev.org URLs 2019-04-29 13:06:10 +08: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
lower-constraints.txt Bump os-traits to latest release (0.14.0) 2019-06-06 12:58:57 -05:00
requirements.txt Bump os-traits to latest release (0.14.0) 2019-06-06 12:58:57 -05:00
setup.cfg Package db migration scripts in placement pypi dist 2019-05-07 00:08:39 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Correct lower-constraints.txt and the related tox job 2018-11-27 17:41:02 +00:00
tox.ini Cache provider ids in requested aggregates 2019-05-29 15:22:38 -05:00

README.rst

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:

Developers

For information on how to contribute to Placement, please see the contents of CONTRIBUTING.rst.

Further developer focused documentation is available at: