openstack/placement
Code Issues Proposed changes
OpenStack resource provider inventory allocation service
10,897 Commits 10 Branches 29 Tags 21 MiB
Python 94.3%
PHP 4.4%
Shell 1.2%
c198326150
Go to file
Tetsuro Nakamura c198326150 Set root_provider_id in the database 
When nested resource provider feature was added in Rocky,
root_provider_id column, which should be non-None value, is created in
the resource provider DB.

However, online data migration is only done implicitly via listing or
showing resource providers. With this patch, executing the cli command

    `placement-manage db online_data_migrations`

makes sure all the resource providers are ready for nested provider
feature, that is, all the root_provider_ids in the DB have non-None
value.

Change-Id: I42a1afa69f379b095417f5eb106fe52ebff15017
Related-Bug:#1803925
2019-01-18 15:39:36 -05:00
api-ref Correct link rest api history 2018-12-19 11:13:02 +00:00
doc Set root_provider_id in the database 2019-01-18 15:39:36 -05: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 Set root_provider_id in the database 2019-01-18 15:39:36 -05:00
playbooks Don't create placement.conf in perfload.yaml 2018-12-04 15:56:03 +00:00
releasenotes Set root_provider_id in the database 2019-01-18 15:39:36 -05:00
tools Add stamp DB version to the migration script 2018-12-12 00:26:57 +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 Add release-notes-jobs-python3 job 2019-01-16 19:12:36 +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 Use os-resource-classes in placement 2018-12-19 10:43:18 +00:00
README.rst Update README to warn of status 2018-09-10 11:11:26 -06:00
requirements.txt Use os-resource-classes in placement 2018-12-19 10:43:18 +00:00
setup.cfg Update author-email in setup.cfg 2018-12-04 04:21:17 +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 Correct lower-constraints.txt and the related tox job 2018-11-27 17:41:02 +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: