openstack/placement
Code Issues Proposed changes
OpenStack resource provider inventory allocation service
10,742 Commits 10 Branches 47 Tags 21 MiB
Python 93%
PHP 4.3%
Shell 2.6%
dc472e144a
Go to file
Tetsuro Nakamura dc472e144a Add alloc cands test with nested and aggregates 
When placement picks up allocation candidates, the aggregates of
nested providers are assumed as the same as root providers. This
means it ignores the aggregates of the nested provider itself.
This could result in the lack of allocation candidates when an
aggregate on a nested provider but not on the root has been
specified in the `member_of` query parameter.

This patch adds test cases for the bug. The fix is done in a
follow up.

Related-Bug: #1792503

Change-Id: Ic532bc231e89eaec4cb5ad01d27bbe840b01a5f7
2018-09-21 10:25:51 +09:00
api-ref Make docs build 2018-09-06 11:45:11 -05:00
doc Sort openstack_projects in doc conf 2018-09-15 11:38:34 -06:00
etc/placement s/placement-config-generator/config-generator/ 2018-09-14 16:10:58 +00:00
gate Add trait query to placement perf check 2018-08-16 18:32:12 +01:00
placement Add alloc cands test with nested and aggregates 2018-09-21 10:25:51 +09:00
releasenotes/notes Remove the Nova aggregate files. 2018-09-04 10:31:22 -05:00
tools tox: make it possible to run pep8 on current patch only 2015-07-24 16:15:38 +01:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore config: Add oslo-config-generator config 2018-09-11 16:50:51 -06:00
.gitreview Set up initial .zuul.yaml 2018-08-31 14:24:59 +00:00
.stestr.conf Inspect and correct tox.ini, .stestr.conf and setup.cfg 2018-09-04 10:31:25 -05:00
.zuul.yaml Make docs build 2018-09-06 11:45:11 -05: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 Use uuidsentinel from oslo.utils 2018-09-05 22:32:56 +00:00
README.rst Update README to warn of status 2018-09-10 11:11:26 -06:00
requirements.txt Use uuidsentinel from oslo.utils 2018-09-05 22:32:56 +00:00
setup.cfg Set the name of the package to openstack-placement 2018-09-12 16:26:39 -06: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 Merge "s/placement-config-generator/config-generator/" 2018-09-14 16:34:23 +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: