John Griffith bb59afc5ab Add device identifier to replication device
One thing that may be needed by some back ends
that are implementing replication is some sort
of back end device identifier.

For managed back ends this shouldn't be an issue
but for unmanaged, it's handy to have some sort
of identifier string.

This patch just adds that to the response examples
in the volume.manager code as well as adds an update
to the dev docs to point it out.

Change-Id: Ic113d905e65c756439425b03035179e65ce0b39e
2015-10-07 16:49:36 -06:00
2015-09-22 15:43:51 -04:00
2015-09-01 03:20:30 +00:00
2012-05-03 10:48:26 -07:00
2013-06-14 14:02:17 +00:00
2012-05-03 10:48:26 -07:00
2012-05-03 10:48:26 -07:00
2012-08-10 11:56:00 -04:00
2015-06-11 17:19:19 +02:00
2015-01-12 14:02:24 +01:00
2015-09-18 16:37:17 +00:00

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.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://github.com/openstack/cinder.git

For developer information please see HACKING.rst

You can raise bugs here http://bugs.launchpad.net/cinder

Python client

https://github.com/openstack/python-cinderclient.git

Description
OpenStack Block Storage (Cinder)
Readme 913 MiB
Languages
Python 99.7%
Smarty 0.3%