glusterfs vol layout: start volume cloned from snapshot
When handling create_share_from_snapshot with glusterfs
volume layout, we do a snapshot clone gluster operation
that gives us a new volume (which will be used to back
the new share). 'snapshot clone' does not start the
resultant volume, we have explicitly start it from Manila.
So far the volume layout code did not bother about it,
rather the 'vol start' was called from glusterfs-native
driver. That however broke all other volume layout based
configs (ie. glusterfs driver with vol layout).
Fix this now by doing the 'vol start' call in the vol
layout code.
Reviewed: https:/ /review. openstack. org/228772 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=4e4c8759a25 fa18384b45f4150 000aacfaed035a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4e4c8759a25fa18 384b45f4150000a acfaed035a
Author: Csaba Henk <email address hidden>
Date: Tue Sep 29 09:49:19 2015 +0200
glusterfs vol layout: start volume cloned from snapshot
When handling create_ share_from_ snapshot with glusterfs
volume layout, we do a snapshot clone gluster operation
that gives us a new volume (which will be used to back
the new share). 'snapshot clone' does not start the
resultant volume, we have explicitly start it from Manila.
So far the volume layout code did not bother about it,
rather the 'vol start' was called from glusterfs-native
driver. That however broke all other volume layout based
configs (ie. glusterfs driver with vol layout).
Fix this now by doing the 'vol start' call in the vol
layout code.
Change-Id: I63c13ce468a322 7f09e381814f55e 8c914fbef95
Closes-Bug: #1499347