4469a813cb
While exploring removing unused packages from lower-constraints.txt it became clear that the lower-constraints job was not working as expected: Because our tox config has usedevelop=True 'setup.py develop' is called to install the placement package after the install command is called. This means that the lower-constraints are clobbered. I had mistakenly assumed that turning off 'usedevelop', which causes 'setup.py install' would not make any difference, because it usually installs dependencies too. It turns out however, that when using pbr and within a git working dir, it does not. That took some time to figure out. Oh well. This change makes it so that we create the tox environment using usedevelop=False and with our own install_command, to avoid upper constraints conflicting with lower constraints. This flagged up a few changes, the main one being that we did not have a new enough version of keystonemiddleware in order to require use of www_authenticate_uri. requirements.txt is updated for this as well. And PasteDeploy needed to be updated to work with Python 3's notion of namespace packages. psycopg2 need a newer version to work with Postgresql 10. oslotest needs to be raised to 3.4.0 because the tests in cmd.test_manage use features to control what is capture by the Output fixture from oslotest. Note that the lower-constraints job found this problem and also demonstrates why we must run the lower-constraints job without upper-constraints being involved. upper-constraints will "win" and we don't want that. The point of the job is find packages where lower-constraints are wrong, so it must "win". The end result here is a lower-constraints.txt file that starts from the lower-constraints.txt defined by nova, and then is adapted to update the versions of packages that were not up to date, remove those packages which are no longer present, and add some that are now required. Change-Id: Id66a28f7ace6fc2adf0e1201d9de5f901234d870 |
||
|---|---|---|
| api-ref | ||
| doc | ||
| etc/placement | ||
| gate | ||
| placement | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| babel.cfg | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| lower-constraints.txt | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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
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: