81bf953701
When runnign tests under tox the virtualenv is created in a number of phases (in brush strokes) 0. virtualenv -p $python .tox/$dir 1. pip install $deps 2. pip install . Step 2 is run without any deps as they're all supposed to be installed in phase 2 We have constraints in 'deps' we need to install all of cinders requirements during phase 2. If we don't then we get unconstrained versions being installed during phase 2. This shows up in a py27 run[1] as the absence of taskflow, and then in [2] with new dependancies being installed [1] http://logs.openstack.org/34/647934/3/check/openstack-tox-py27/93180f1/tox/py27-1.log [2] http://logs.openstack.org/34/647934/3/check/openstack-tox-py27/93180f1/tox/py27-2.log Change-Id: I5b1c285680f7c3256a707ea5973573f1176d4a26 (cherry picked from commit |
||
---|---|---|
api-ref/source | ||
cinder | ||
contrib/block-box | ||
doc | ||
etc/cinder | ||
playbooks/legacy/cinder-tempest-dsvm-lvm-lio-barbican | ||
rally-jobs | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
driver-requirements.txt | ||
lower-constraints.txt | ||
pylintrc | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
CINDER
You have come across a storage service for an open cloud computing service. It has identified itself as Cinder. It was abstracted from the Nova project.
- Wiki: https://wiki.openstack.org/Cinder
- Developer docs: https://docs.openstack.org/cinder/latest/
- Blueprints: https://blueprints.launchpad.net/cinder
- Release notes: https://docs.openstack.org/releasenotes/cinder/
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
For developer information please see HACKING.rst
You can raise bugs here https://bugs.launchpad.net/cinder
Python client
https://git.openstack.org/cgit/openstack/python-cinderclient