tripleo-image-elements/elements/cinder-volume
Jan Provaznik 3f1408e8cc Run cinder-volume in active/passive mode for NFS backend
Running multiple cinder-volume instances which access the same storage
is currently not supported and may cause data inconsistency.
This issue is discussed here:
https://bugs.launchpad.net/cinder/+bug/1322190

Running cinder-volume service in active/passive mode seems to be
the only safe way when shared backend storage is used. Also
workaround with setting shared host is needed.

Of course in default no-HA setup each cinder-volume manages its
local volumes and none of the above is needed.

Change-Id: Id8f5c33f63538a9be85a1434f36b0a840e0b8db9
2014-08-29 10:13:48 +02:00
..
install.d/cinder-source-install cinder-volume: install qemu-img for conversions 2014-07-10 21:51:18 -04:00
os-refresh-config Run cinder-volume in active/passive mode for NFS backend 2014-08-29 10:13:48 +02:00
README.md Move Cinder NFS backend driver config in cinder-volume-nfs element 2014-08-21 19:47:56 +02:00
element-deps cinder-volume: install qemu-img for conversions 2014-07-10 21:51:18 -04:00
pkg-map cinder-volume: install qemu-img for conversions 2014-07-10 21:51:18 -04:00

README.md

Installs cinder volume service.