![]() Active-Active configurations are not trivial, and therefore vendors need to check that their drivers support these configurations and have no issues. Since users will most likely assume that once Active-Active is available as a core functionality all drivers will be supporting it this could lead to data loss, data corruption, or just bad user experience. In order to prevent this, without a full Active-Active test suite, we will rely on vendor "auto certification". What this means is that Cinder won't allow any driver to start in an Active-Active configuration by default until the vendor has tested their driver's readiness and explicitly set in the code. Vendors will set SUPPORTS_ACTIVE_ACTIVE class attribute to True in their drivers to reflect the driver's readiness, or if the readiness depends on some configuration options they can leave the class attribute with the default False value and just set it as an instance attribute in their __init__ method. Implements: blueprint cinder-volume-active-active-support Change-Id: I6034be3e96f85e8995e34b6420fbdb5570538f1c |
||
---|---|---|
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