OpenStack Block Storage (Cinder)
6d7125bdbc
Currently, if we want to manage a volume in the K2 array, we rename the volume and associated VG in K2 according to cv-CinderVolumeId for volume and cvg-CinderVolumeId for VG. So, if K2 volume is managed by cinder, then for any future reference for the managed volume, cv-CinderVolumeId and cvg-CinderVolumeId must exist on K2 array. But if a VG in K2 have more than one volume and we try to manage another volume in the same VG, then it will rename the VG and any future reference for another managed volume will result in error. Change-Id: I0db48d11d812ea802d11165a959ff5b46a4d6af3 Closes-Bug: #1646766 Co-Authored-By: Nikesh Mahalka <Nikesh.Mahalka.ctr@kaminario.com> 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 | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
pylintrc | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
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: 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