[Bugs] [Bug 1330081] [RFE] gluster vfs plugin should be able to make use of multiple volfile server feature of gfapi

bugzilla at redhat.com bugzilla at redhat.com
Wed Sep 7 10:16:15 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1330081

Raghavendra Talur <rtalur at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |POST



--- Comment #3 from Raghavendra Talur <rtalur at redhat.com> ---
How to test
=================================================================
glusterfs:volfile_server key can be list of white space seperated
elements where each element could be
unix+/path/to/socket/file or [tcp+]IP|hostname|\[IPv6\][:port].

Note the restriction on naming a IPv6 host, it follows the same
restriction that is based on IPv6 naming in URL as per RFC 2732[1].

Some tests:

1. Setup, Gluster cluster of 192.168.122.13, 192.168.122.14, 192.168.122.15 .
In smb.conf on Server 192.168.122.13, you can have

    a. glusterfs:volfile_server = google.com 192.168.122.13 192.168.122.14
192.168.122.15
    Expected result: connection should succeed with 192.168.122.13 .

    b. glusterfs:volfile_server = google.com 192.168.122.31 192.168.122.14
192.168.122.15
    Expected result: connection should succeed with 192.168.122.14 .

    c. glusterfs:volfile_server = tcp+192.168.122.14:24007 192.168.122.15
    Expected result: connection should succeed with 192.168.122.14 .

    d. glusterfs:volfile_server = unix+/var/run/glusterd.socket
tcp+192.168.122.14:24007 192.168.122.15
    Expected result: connection should succeed with local glusterd using unix
socket.

    e. glusterfs:volfile_server = 192.168.122.31 192.168.122.44 192.168.122.45
    Expected result: connection should fail with log saying could not fetch
volfile.


For all the above cases, please use netstat to verify connections and perform
IO from the smb clients to ensure that connection is fully operational. Logging
at default level 0 will only happen for total failure case where all volfiles
are exhausted. All other logs would be at level 3 onwards.

I will add more cases later.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=O8NsuQt1DG&a=cc_unsubscribe


More information about the Bugs mailing list