Gluster users - Sep 2011 - Where to learn about "translators" and the config files?

I've looked at the docs, and this list of so-called "translators"
here:

    http://www.gluster.com/community/documentation/index.php/Gluster_Translators

...as well as the various files in /etc/gluster* and am having trouble
making sense of how these config files are organized and how/when to
make use of translators.

In particular I have been testing gluster by creating volumes using
the 'gluster' CLI utility, and I am trying to turn on POSIX compliance
or locking in order to support operations on sqlite dbs. It seems this
is done through "translators" like "features/locks", but
I'm having
difficulty understanding where to go from here.

Thanks,
Brandon

On Mon, Sep 19, 2011 at 10:07 AM, Brandon Simmons
<bsimmons at labarchives.com> wrote:
> I've looked at the docs, and this list of so-called
"translators" here:
>
> ?
?http://www.gluster.com/community/documentation/index.php/Gluster_Translators
>
> ...as well as the various files in /etc/gluster* and am having trouble
> making sense of how these config files are organized and how/when to
> make use of translators.
>
> In particular I have been testing gluster by creating volumes using
> the 'gluster' CLI utility, and I am trying to turn on POSIX
compliance
> or locking in order to support operations on sqlite dbs. It seems this
> is done through "translators" like "features/locks",
but I'm having
> difficulty understanding where to go from here.
Thanks for the post Brandon, I'm doing something very similar. We have
an issue with openvz gluster clients where, due to a vm environment
bug the supplemental groups cannot be properly verified on the servers
(openvz is answering host pid mapping in /proc vs the expected
container pid mapping, so when that broken UID/GID info is sent to the
server for access control, fail).

http://bugs.gluster.com/show_bug.cgi?id=3563
http://bugzilla.openvz.org/show_bug.cgi?id=1992

We are about to attempt a workaround where we manually modify the vol
file on each of the servers to exclude the volume stanza which
contains "type features/access-control", and modify the "type
features/access-control" block to shortcut to the "type
storage/posix"
subvolume stanza.

Two major questions are:
a) What is the cksum file and will it cause havoc with our change
b) Is there some way possible to modify one volume file and use a
builtin facility to propagate it to the servers?

Anybody have experience to share?

-George


-- 
George Georgalis, (415) 894-2710, http://www.galis.org/

On 09/19/2011 10:37 PM, Brandon Simmons wrote:
> I've looked at the docs, and this list of so-called
"translators" here:
>
>     
http://www.gluster.com/community/documentation/index.php/Gluster_Translators
>
> ...as well as the various files in /etc/gluster* and am having trouble
> making sense of how these config files are organized and how/when to
> make use of translators.
>
> In particular I have been testing gluster by creating volumes using
> the 'gluster' CLI utility, and I am trying to turn on POSIX
compliance
> or locking in order to support operations on sqlite dbs. It seems this
> is done through "translators" like "features/locks",
but I'm having
> difficulty understanding where to go from here.
>
> Thanks,
> Brandon
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Brandon,
         Before the 3.1 releases, the users needed to manually write the 
volfile using the translators, for the releases >= 3.1 you dont need to 
edit anything. You just use the cli and you are done. features/locks is 
added by default on all bricks when a volume is created. You dont need 
to turn anything on for POSIX compliance or locks. They should work by 
default. Let us know if you face any problems with your setup.

Pranith.