openstack/placement
Code Issues Proposed changes
OpenStack resource provider inventory allocation service
10,743 Commits 10 Branches 27 Tags 21 MiB
Python 93%
PHP 4.3%
Shell 2.6%
c85ae69ee9
Go to file
Tetsuro Nakamura c85ae69ee9 Fix aggregate members in nested alloc candidates 
When placement picks up allocation candidates, the aggregates of
nested providers were assumed as the same as root providers. This
means that the `GET /allocation_candidates API` ignored the
aggregates on the nested providers. This could result in the lack
of allocation candidates when an aggregate is on a nested provider
but the aggregate is not on its root provider and the aggregate is
specified in the API by the `member_of` query parameter.

This patch fixes the bug changing it to consider the aggregates
not only on root rps but also on the nested rp itself and adds
a release note for this.

The document which explains the whole constraint of `member_of`
and other query parameters with nested providers, will be submitted
in a follow up patch.

Change-Id: I9a11a577174f85a1b47a9e895bb25cadd90bd2ea
Closes-Bug: #1792503
2018-09-21 11:44:58 +09:00
api-ref Fix aggregate members in nested alloc candidates 2018-09-21 11:44:58 +09: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 Fix aggregate members in nested alloc candidates 2018-09-21 11:44:58 +09:00
releasenotes/notes Fix aggregate members in nested alloc candidates 2018-09-21 11:44:58 +09: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: