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

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

diff --git a/cinder/volume/drivers/ibm/storwize_svc/storwize_svc_common.py b/cinder/volume/drivers/ibm/storwize_svc/storwize_svc_common.py
index 5bd6af51d3ae3114fd452ed6bb5fd3f4ba9479bc..8f50e5a3923fbdcc14410dc4f172afa8e8d5790a 100644 (file)
--- a/cinder/volume/drivers/ibm/storwize_svc/storwize_svc_common.py
+++ b/cinder/volume/drivers/ibm/storwize_svc/storwize_svc_common.py
@@ -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