Gluster users - Apr 2017 - What is the CLI NUFA option "local-volume-name" good for?

Hi,

I've been struggling with NUFA for a while now and I know very well what 
the "option local-volume-name brick" in the volfile does. In fact,
I've
been using a filter to force gluster to use the local subvolume I want 
instead of the first local subvolume it finds, but filters are very 
unreliable. Recently I've found this bug [1] and thought that I'll 
finally be able to set the NUFA's "local-volume-name" option 
*per-server* through the CLI without the use of the filter, but no. This 
options sets the value globally, so I'm asking what is the use of LOCAL 
volume name set GLOBALLY with the same value on every server?

With thanks,
Jan Wrona

[1] https://bugzilla.redhat.com/show_bug.cgi?id=987240


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3706 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170428/f126e14f/attachment.p7s>

On Fri, Apr 28, 2017, at 10:57 AM, Jan Wrona wrote:
> I've been struggling with NUFA for a while now and I know very well
what
> the "option local-volume-name brick" in the volfile does. In
fact, I've
> been using a filter to force gluster to use the local subvolume I want 
> instead of the first local subvolume it finds, but filters are very 
> unreliable. Recently I've found this bug [1] and thought that I'll 
> finally be able to set the NUFA's "local-volume-name" option 
> *per-server* through the CLI without the use of the filter, but no. This 
> options sets the value globally, so I'm asking what is the use of LOCAL
> volume name set GLOBALLY with the same value on every server?
You're right that it would be a bit silly to set this using "gluster
volume set" but it makes much more sense as a command-line override
using "--xlator-option" instead.  Then it could in fact be different
on
every client, even though it's not even set in the volfile.