I dont believe this is required. That would place too much complexity on
the unify xlator. Defining different servers and client mount points should
be the best way to go here :)
Matt.
Why would the user want to mount a bunch of different mount points. Wouldn't
it be more convenient for the end user to mount just one point? The fix
seems trivial for the unify translator --when deciding which brick to write
the file to, use the list specified by the user as the available list of
bricks.
From: Matt Paine <matt@xxxxxxxxxxxxxxxx>
To: gluster-devel@xxxxxxxxxx
Subject: Re: Specify which files should be saved to which
brick
Date: Mon, 30 Jul 2007 14:47:46 +1000
I want to store all applications on one brick, and all logs and cached
data into another brick, all user data and home directories in another
brick, and backups on another brick, etc.
Is there a way to do this, similiar to how replication is specified,
eg option datalocation /var/*:brick1,/home/*:brick2-afr
No, not by specifying an option, but you can simply have a number of server
bricks which will achieve that. Have a server for /var, a server for /home
- and have the client mount each server in the place thats required.
This way, I can put more replication on user data, and less so on less
important data, similiar to how afr can specify which types of files get x
number of backups.
Having different servers, you could specify different afr across each
server doing exactly that.
If not, please add to feature request maybe to the unify translator.
I dont believe this is required. That would place too much complexity on
the unify xlator. Defining different servers and client mount points should
be the best way to go here :)
Matt.
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
_________________________________________________________________
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507
