8b6f41715c
Up until now drivers have been able to define their own custom exception classes. In most cases these are inherited from either a native python exception class or at best the base cinder exception class. The problem with this is that it makes it very difficult for higher layers (such as volume manager) to do any intelligent exception handling and the base Cinder.exception class is too broad. This change takes the first step in cleaning this up. We create new exception classes for all drivers to inherit from: VolumeDriverException VolumeBackendAPIException BackupDriverException This still allows the freedom to create custom exceptions for a particular driver, however it also gives us a common exception class to catch and check in higher levels. Further refinement and standardization will be helpful going forward but this should give us a good start. Change-Id: I8c2ca4eecf7a64a82846d6d24fc0239db086237e |
||
---|---|---|
bin | ||
cinder | ||
doc | ||
etc/cinder | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
CONTRIBUTING.md | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
openstack-common.conf | ||
pylintrc | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
taskflow.conf | ||
test-requirements.txt | ||
tox.ini |
README.rst
The Choose Your Own Adventure README for 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.
To monitor it from a distance: follow @openstack on twitter.
To tame it for use in your own cloud: read http://docs.openstack.org
To study its anatomy: read http://cinder.openstack.org
To dissect it in detail: visit http://github.com/openstack/cinder
To taunt it with its weaknesses: use http://bugs.launchpad.net/cinder
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING.rst