History

John Griffith e7498ca5bd Enable fail back in SolidFire driver

This change fixes up a few things in the SolidFire driver to enable the
ability to "fail back" to the original cluster in a replication scenario.

We're still assuming a cluster-wide fail over, but now an admin has the
ability to specify subsequent `cinder failover-host` calls to switch
back and forth between their SF clusters.

This change promotes the target on a fail over and also now attempts to
set up replication back to the original src  as well (assuming the
original is available and not a puddle of melted goo).  This means that
writes to the new back end will be replicated back to the src, so if a
user so chooses they can fail back to the original and have their new
data.

Change-Id: I678986e557755c2fe4183927c17342e430f5df0d

2017-12-21 17:27:21 -07:00

notes

Enable fail back in SolidFire driver

2017-12-21 17:27:21 -07:00

source

Remove setting of version/release from releasenotes

2017-11-16 22:34:49 +00:00

README.rst

Fix release notes link

2017-07-25 14:24:18 -07:00

README.rst

Release notes

The release notes for a patch should be included in the patch. The intended audience for release notes include deployers, administrators and end-users.

A release note is required if the patch has upgrade or API impact. It is also required if the patch adds a feature or fixes a long-standing or security bug.

Please see https://docs.openstack.org/cinder/latest/contributor/releasenotes.html for more details.