Storwize_svc V2 replication needs to be updated to V2.1

Bug #1544611 reported by Jay Bryant on 2016-02-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Vincent Hou

Bug Description

The patch to implement V2 of replication for the Storwize_svc driver has now merged:

We need to now submit a patch to get V2 updated to the new V2.1 (Cheesecake) version of replication.

Jay Bryant (jsbryant) on 2016-02-11
Changed in cinder:
importance: Undecided → High
assignee: nobody → vincent_hou (houshengbo-u)
milestone: none → mitaka-3

Fix proposed to branch: master

Changed in cinder:
assignee: vincent_hou (houshengbo-u) → Vincent Hou (houshengbo)
status: New → In Progress

Submitter: Jenkins
Branch: master

commit c8cf5504cc6c49b3060b8c8c0f1304b19d00bfb1
Author: Vincent Hou <email address hidden>
Date: Tue Mar 1 14:26:52 2016 -0500

    Storwize: Update replication to v2.1

    This patch updates replication to match the v2.1 spec. This makes
    it possible to replicate an entire backend, and upon failover, all
    replicated volumes will be failed over together.

    cinder.conf should have the replication config group:

    The replication can be configured via either multi-backend on one
    cinder volume node, or on separate cinder volume nodes.

    Options to be put in cinder.conf, where the primary back-end is

    enabled_backends = sv1, sv2 (if enabling multi-backends)

    san_login = admin
    san_password = admin
    san_ip =
    volume_driver =\
    volume_backend_name = sv1
    replication_device = managed_backend_name:second_host@sv2#sv2,

    Options to be put in cinder.conf, where the secondary back-end is

    san_login = admin
    san_password = admin
    san_ip =
    volume_driver =\
    volume_backend_name = sv2

    Closes-Bug: #1544611

    Change-Id: I8a4963fa4b30f2df1903697909deece762228257

Changed in cinder:
status: In Progress → Fix Released

This issue was fixed in the openstack/cinder release candidate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers