glusterfs_driver: Glusterfs NFS-Ganesha share's export location should be uniform for both nfsv3 & nfsv4 protocols

[karthick]

In Liberty, export location for gluster nfs-ganesha is different for nfsv3 & nfsv4 protocols.

NFSv3 share location is of the format - <ganesha server ip>:/<share-id> and NFSv4 share location is of the format - <ganesha server ip>:/<share-id>--<access-id>.

Export location listed in 'manila list' works only with NFSv3 protocol. Using same path to export share using NFSv4 protocol fails.

cropped output of 'manila list' command:

|ID| Name| export location|
| 7303bc3d-bb1f-4d7b-9171-0c168edcc78c | nfs-ganesha-vol10 10.70.37.91:/share-d34d3ab4-197d-4ae3-9623-14e96b4e5398 |

Export location for both nfsv3 and nfsv4 should use pseudo path i.e., <ganesha server ip>:/<share-id>--<access-id>

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/286346
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=e4d9f56f140abf60ab9400cb80699a6e3a4ebe64
Submitter: Jenkins
Branch: master

commit e4d9f56f140abf60ab9400cb80699a6e3a4ebe64
Author: Csaba Henk <email address hidden>
Date: Tue Mar 1 01:46:51 2016 +0100

    glusterfs/ganesha: add symbolic access-id to export location

    With Ganesha the actual location where the storage backend entities
    are exported include the id of the access rule on behalf of which
    the export is made; see

    http://docs.openstack.org/developer/manila/devref/ganesha.html#known-issues
    https://review.openstack.org/#/c/249998/2/doc/source/devref/ganesha.rst

    Thus the export location reported through the Manila API/UI
    is inaccurate and current Manila interface is not capable of
    a faithful representation of the actual export mechanism
    (as the exposed export location values depend only on the share but
    noot on the acces rules).

    We can at least try to find partial representations that give
    more clue than a straightaway false export location value.
    With this patch we make such attempt, using export locations
    of the format

      example.com:/share-6c0262e8-f989-4df1-9f01-c758b0d72428--<access-id>

    Change-Id: I029a28341225087101920c3792e9b2fb4beed081
    Closes-Bug: #1501178

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/manila 2.0.0.0b3 development milestone.