openstack
/
placement
Code Issues Proposed changes
OpenStack resource provider inventory allocation service
11,202 Commits 9 Branches 46 Tags 21 MiB
Python 93%
PHP 4.3%
Shell 2.6%
Go to file
Chris Dent c00d043376 Spec for nested magic 1 
This is a spec for several nested features which has been split
off from the original spec for nested magic [1] in an effort to
not delay progress on these features while 'can_split' is being
discussed.

This spec describes a cluster of Placement API work to support several
interrelated use cases for Train around:

* Modeling complex trees such as NUMA layouts, multiple devices,
  networks.
* Requesting affinity (in the NUMA sense) between/among the various
  providers/allocations in allocation candidates against such layouts.
* Describing granular groups more richly to facilitate the above.
* Requesting candidates based on traits/aggregates that are not
  necessarily associated with resources.

In particular, it describes the new GET /allocation_candidates
features:

* arbitrary group suffixes
* same_subtree query parameter
* resourceless request groups
* root_required, root_member_of

[1] I7c00b06e85879ab1bf877ce32979e8cc898bfd9e

Co-Authored-By: Eric Fried <openstack@fried.cc>
Change-Id: I55973aa7de4a85b63dff4a7d1afb6c36796af71a
Story: #2005575
Task: #30949
 		2019-06-20 10:18:06 -05:00
api-ref Allow [a-zA-Z0-9_-]{1,64} for request group suffix 2019-05-21 11:07:38 +01:00
doc Spec for nested magic 1 2019-06-20 10:18:06 -05:00
etc/placement Add oslo.log to genconfig 2019-03-19 09:47:14 -05:00
gate Add a perfload job. 2018-11-30 14:59:47 +00:00
placement Reuse cache result for sharing providers capacity 2019-05-29 15:22:38 -05:00
placement_db_tools Package db migration scripts in placement pypi dist 2019-05-07 00:08:39 +00:00
playbooks OpenDev Migration Patch 2019-04-19 19:41:22 +00:00
releasenotes Merge "Allow [a-zA-Z0-9_-]{1,64} for request group suffix" 2019-05-29 02:53:34 +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 Don't run functional.db tests in nova functional run 2019-05-24 14:00:58 +00: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-resource-classes requirements 2019-05-23 17:52:43 -05:00
requirements.txt Bump os-resource-classes requirements 2019-05-23 17:52:43 -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: