Allow specification of a SolidFire volume-prefix

[John Griffith]

The SolidFire creates names for Volumes on the backend using the format UUID-<cinder-id>

This works well, but it turns out that there is a possibility of a UUID collision for customers running multiple clouds against the same cluster. To eliminate that possibility we should allow a config option to set the prefix to be whatever an admin chooses.

So the format would be <sf_volume_prefix><cinder-id>

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/231250
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=2d990c8c56985b6a678b9cdaede525ab0b2a7c59
Submitter: Jenkins
Branch: master

commit 2d990c8c56985b6a678b9cdaede525ab0b2a7c59
Author: John Griffith <email address hidden>
Date: Mon Oct 5 17:22:30 2015 -0600

    Add ability to set prefix in SolidFire Volume name

    The SolidFire creates names for Volumes on the backend using
    the format UUID-<cinder-id>

    This works well, but it turns out that there is a possibility
    of a UUID collision for customers running multiple clouds against
    the same cluster. To eliminate that possibility we should allow
    a config option to set the prefix to be whatever an admin chooses.

    This patch introduces the sf_volume_prefix config option to
    address this bug. The default still uses the 'UUID-' prefix.

    DocImpact
    Changing this setting on an existing deployment will
    result in the existing volumes being inaccessible. To introduce
    this change to an existing deployment it's recommende to
    add the Cluster as if it were a second backend and disable
    new deployments to the current backend.

    Change-Id: I21a87e6431099e51355044f2dfea35b61ca8125f
    Closes-Bug: #1503069

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/cinder 8.0.0.0b1 development milestone.