7c1e92278c
When volume backends were defined in the [DEFAULT] cinder.conf config section, it did not make sense to have more than one AZ config setting. Now that we have multibackend and we have deprecated the ability to configure backends in DEFAULT, we can set AZs per backend section. This previously required setting up a separate service using a different cinder.conf to have more than one AZ. But since the vast majority of backends are separate physical devices, there is no reason to restrict the control plane service to be on separate nodes to support separate AZ configurations. Change-Id: I0d7669718a1d1e03e3dd42d1a19b70ff03342bd7 Implements: bp multibackend-az-support
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