glusterfs_native: Unable to create shares using newly available GlusterFS volumes without restarting manila share service

[Ramana Raja]

'glusterfs_native' driver creates shares by using GlusterFS volumes whose addresses are fed in as a Manila config option 'glusterfs_targets'. So the driver cannot create more number of shares than the number of volumes listed as 'glusterfs_targets'. Even if the additional volumes are created in the GlusterFS backend to serve as Manila shares, the volumes cannot be made available to Manila without manually adding their addresses to the 'glusterfs_target' list option and restarting manila share service. This is cumbersome for the OpenStack admin.

[Ben Swartzlander (bswartz)]

https://review.openstack.org/#/c/162542/

[OpenStack Infra (hudson-openstack)]

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

commit 482d304e385b93b34ee7dd087b4a435987a7a232
Author: Csaba Henk <email address hidden>
Date: Fri Jan 23 00:32:33 2015 +0100

    glusterfs_native: negotiate volumes with glusterd

    So far glusterfs_native was able to create shares
    from volumes listed in 'glusterfs_targets' config
    option.

    New behavior: a regexp pattern is to be provided
    through the glusterfs_volume_pattern config option.
    Upon share creation, grep gluster server's volumes
    with this pattern and create the new share from
    one among those.

    Change-Id: I12ba0dbad0b1174c57e94acd5e7f6653f5bfaae8
    Closes-Bug: #1437176