openstack/placement
Code Issues Proposed changes
OpenStack resource provider inventory allocation service
10,977 Commits 10 Branches 49 Tags 22 MiB
Python 94.4%
PHP 4.3%
Shell 1.2%
c04a107e32
Go to file
Chris Dent c04a107e32 Make the PlacementFixture usable without intercept 
There are cases where it is necessary to use the PlacementFixture
without it running a wsgi-intercept, for example when you'd like
to run an indepdendent wsgi-intercept, as in the nova tests that
exercise the report client.

In the bug listed as partial below those report client tests were
using a nova conf global to initialize the wsgi intercept. They
just happened to be working because that CONF has the required
configuration settings. When placement's conf diverged [1] things
broke. A nova change which depends on this one will resolve the
bug.

Note that as a part of this change, the code which deletes
'sync_on_startup' (the new conf option) before configuring the
database, is adapted to be more flexible. There really is only
one conf setting that is required to start the placement database,
connection, and we'd like to make it possible for people to set
just that when doing tests or experiments and not have to worry
about extraneous optional things.

Some parameter descriptions are added to the PlacementFixture
__init__.

We should add more robust testing to all three of PlacementFixture,
fixtures.Database, and PlacementDirect, but at the moment we are
trying to fix a gate blocking bug.

Partial-Bug: #1818560

[1] Ie43a69be8b75250d9deca6a911eda7b722ef8648

Change-Id: I8c36f35dbe85b0c0db1a5b6b5389b160b68ca488
2019-03-04 20:55:22 +00:00
api-ref in_tree[N] alloc_cands with microversion 1.31 2019-02-25 13:00:30 -06:00
doc Add a vision-reflection 2019-02-21 13:26:20 +00: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 Make the PlacementFixture usable without intercept 2019-03-04 20:55:22 +00:00
playbooks Also time placeload when doing perfload 2019-02-05 11:20:54 +00:00
releasenotes Merge "Optionally migrate database at service startup" 2019-03-04 17:25:20 +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
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 Don't use OVO with ResourceProvider and ResourceProviderList 2019-02-25 23:48:33 +00:00
README.rst Update README to warn of status 2018-09-10 11:11:26 -06: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 Use tox 3.1.1 fixes 2019-02-14 09:59:07 -06: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: