cinder/kaminario-concurrency-bug-e0b899a42383660c.yaml at c3d1dd1048bff4976bc771539d1f44cc423b7adf - cinder - OpenDev: Free Software Needs Free Tools

openstack/cinder

VenkataKrishna Reddy 4e92c272eb Add replication failback in Kaminario K2 drivers

Replication failback support is added based on active_backend_id
in Kaminario K2 iSCSI and FC Cinder drivers.
Use "cinder failover-host" command to switch between failover and
failback based on active_backend_id.
If active_backend_id is secondary array, "cinder failover-host"
will trigger failback code.
Below are the steps as part of failback:
1)Search "failed-over" sessions on secondary array.
2)Change state of "failed-over" sessions to "in-sync".
  This will reverse the replication direction from secondary
  to primary.
3)Create external snapshots and synced to primary array volumes
4)Change state of "in-sync" sessions on primary to "failed-over".
5)Change state of "failed-over" sessions to "in-sync".
  This will reverse the replication direction from primary to
  secondary.

Also, updated releasenotes of bug #1608913
DocImpact
Closes-Bug: #1615178
Co-Authored-By: Nikesh Mahalka<Nikesh.Mahalka.ctr@kaminario.com>
Co-Authored-By: Sreedhar Varma<Sreedhar.Varma.ctr@kaminario.com>
Co-Authored-By: Lakshman<Lakshmi.Narayana.ctr@kaminario.com>
Co-Authored-By: Ido Benda<Ido.Benda@kaminario.com>
Change-Id: I664516ab31f9d33e4d14cd8615a1e0da4dba15b6

2016-08-23 00:50:25 -04:00

7 lines

237 B

YAML

Raw Blame History

 ---
 fixes:
   - Fixed concurrency issue in K2 iSCSI and FC Cinder drivers
     due to possible race conditions between attach and detach
     volumes and due to limitation from Kaminario K2 iSCSI and
     FC arrays on concurrent operations.