![]() If some K2 arrays are configured with same 'volume_backend_name' in cinder.conf, then 'self.k2_lock_name' will be same for attaching and detaching volumes for these arrays and it will block simultaneous attach and detach volumes for these K2 arrays. Use of K2 management IP in place of 'volume_backend_name' will keep 'self.k2_lock_name' different for attaching and detaching volumes and allow simultaneous attach and detach volumes for these K2 arrays. Also, Adding/Deleting loggers according to below thumb rules: 1. startup/shutdown functions should use the logging decorator 2. each function that creates objects should use the logging decorator 3. helper functions that do not create objects should NOT use the logging decorator 4. API functions should use the logging decorator Change-Id: I1b70bee41f6c42585d0df40a4ae59c33f038b58c Closes-Bug: #1623328 Co-Authored-By: Ido Benda<Ido.Benda@kaminario.com> |
||
---|---|---|
api-ref/source | ||
cinder | ||
doc | ||
etc/cinder | ||
rally-jobs | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
babel.cfg | ||
pylintrc | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
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: http://wiki.openstack.org/Cinder
- Developer docs: http://docs.openstack.org/developer/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 http://bugs.launchpad.net/cinder
Python client
https://git.openstack.org/cgit/openstack/python-cinderclient