openstack
/
placement
Code Issues Proposed changes
OpenStack resource provider inventory allocation service
11,106 Commits 9 Branches 46 Tags 21 MiB
Python 93%
PHP 4.3%
Shell 2.6%
Go to file
Chris Dent f7f5231677 Add register_opts param to PlacementFixture 
There are scenarios where it is useful to create a ConfigOpts
and register_opts on it before ever calling the PlacementFixture.
If that is done we don't want to re-register the opts within
the fixture as this can lead to errors (especially when CLI
opts are involved).

The scenario that discovered this problem is in nova in a regression
test [1] where a ConfigOpts is created and registered, the placement
DatabaseFixture is started and then that same config is used in
multiple instances of the PlacementFixture, each of which again
register_opts(). Until commit b647919666
this wasn't a problem because the default opts in placement did
not include any CLI options. Adding logging opts brought some in.

This change adds a flag to the constructor for PlacementFixture,
register_opts, defaulting to True, which lets the caller say
no, I don't want do register.

It also reverts the revert of b647919666
to perform oslo_log.log.register_opts() from a central location.

[1] test_bug_1679750.TestLocalDeleteAllocations.test_local_delete_removes_allocations_after_compute_restart

Change-Id: I360a306b5d05ada75274733038b73ec2f2bdc4d4
Needed-By: I042e41ac8c41c0e5f0389904eb548e0e97d54c60
Related-Bug: #1821092
 		2019-03-20 22:34:21 +00:00
api-ref Update docs bug links to storyboard 2019-03-11 20:54:24 +00:00
doc Merge "Flesh out the post-install verify doc" 2019-03-20 16:13:33 +00: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 Add register_opts param to PlacementFixture 2019-03-20 22:34:21 +00:00
playbooks Use sync_on_startup in placement-perfload job 2019-03-09 12:24:22 +00:00
releasenotes Add prelude to release notes 2019-03-19 19:40:10 +00: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 Merge "Add irrelevant files list to perfload job" 2019-01-22 04:41:13 +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 Update CONTRIBUTING and HACKING 2019-03-11 18:28: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
lower-constraints.txt Don't use OVO with ResourceProvider and ResourceProviderList 2019-02-25 23:48:33 +00:00
requirements.txt Don't use OVO with ResourceProvider and ResourceProviderList 2019-02-25 23:48:33 +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 Remove pep8 whitespace ignores 2019-03-05 18:18:30 -06: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: