Storwize SVC multiple management IPs

[OpenStack Infra]

https://review.openstack.org/284267
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/cinder" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit ca06025a4ab7fbe817e6d29f12bdfcf378c85cde
Author: Jacob Gregor <email address hidden>
Date: Wed Feb 24 11:06:32 2016 -0600

    Storwize SVC multiple management IPs

    Right now Storwize SVC does not support multiple management IPs.
    This patch adds this feature so that if the primary IP fails, it
    will switch to the secondary IP that the user sets.

    DocImpact
    Adds config option 'storwize_san_secondary_ip'

    Implements: blueprint storwize-add-support-for-multiple-management-ips
    Change-Id: Ib82ba5b43e92027bfe39873a556baec796bb457e

[Sean McGinnis (sean-mcginnis)]

Hey Jacob, please add comments as to the documentation impact and reassign to openstack-manuals.

[Jacob Gregor (jgregor)]

Thanks for reminding me to add comments here Sean,

The patch linked in the description adds a new config option 'storwize_san_secondary_ip'. Here is some more information about this new config option:

cfg.StrOpt('storwize_san_secondary_ip',
               default=None,
               help='Specifies secondary management IP or hostname to be '
                    'used if san_ip is invalid or becomes inaccessible.')

Let me know if you need any more information.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/286952
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=d7af3c41c196b759902b25575f740f7d07a501b7
Submitter: Jenkins
Branch: master

commit d7af3c41c196b759902b25575f740f7d07a501b7
Author: zhang.lei <[e-mail]>
Date: Wed Apr 27 19:18:32 2016 +0800

    IBM Storwize with pool-aware-cinder-scheduler

    According to [1], the configuration flag storwize_svc_volpool_name
    should be updated to a ListOpt.
    According to [2], Adds config option 'storwize_san_secondary_ip'

    generate cinder.conf.sample in cinder project and update here

    [1]: https://review.openstack.org/284614
    [2]: https://review.openstack.org/284267

    Change-Id: I7eb865cefaab26407bfb606d5c92ed24bc445771
    Partial-Bug: #1551844
    Partial-Bug: #1551709

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/324355

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/324355
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=d34b83de48c013dfe798f4ef8b5b40aba4dbc42a
Submitter: Jenkins
Branch: master

commit d34b83de48c013dfe798f4ef8b5b40aba4dbc42a
Author: KATO Tomoyuki <email address hidden>
Date: Thu Jun 2 19:27:45 2016 +0900

    [config-ref] add secondary management IP for Storwize SVC

    backport: mitaka

    Change-Id: Iafa8e364fcecd3b216f9263463f16c2ba30d64e3
    Closes-Bug: #1551709

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.