openstack/cinder
Code Issues Proposed changes

Add the key 'replication' and set the correct 'replication_status'

Browse Source 
This patch fixes the minor issues following the implementation
of replication v2.1 for storwize driver. It adds the key
'replication' to make sure of that the cinder-volume service
can have a successful restart and sets the 'replication_status
'back to enabled for failback.

Change-Id: I1ddb715e72336378434b7ee5ffe617cbb94cd16b
Closes-Bug: #1556285
This commit is contained in:
Vincent Hou 2016-03-11 16:25:18 -05:00
parent 9504f51882
commit 1ed4d2d2fb
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
cinder/volume/drivers/ibm/storwize_svc/storwize_svc_common.py
View File

@ -2535,7 +2535,7 @@ class StorwizeSVCCommonDriver(san.SanDriver,
replication.replication_failback(volume)
volume_update_list.append(
{'volume_id': volume['id'],
'updates': {'replication_status': 'available'}})
'updates': {'replication_status': 'enabled'}})
else:
volume_update_list.append(
{'volume_id': volume['id'],
@ -3103,6 +3103,7 @@ class StorwizeSVCCommonDriver(san.SanDriver,
data['pools'] = [self._build_pool_stats(pool)
for pool in
self.configuration.storwize_svc_volpool_name]
data['replication'] = self._replication_enabled
data['replication_enabled'] = self._replication_enabled
data['replication_targets'] = self._get_replication_targets(),
self._stats = data