On Tue, Apr 7, 2015 at 3:56 PM, Rajesh Joseph <rjoseph@xxxxxxxxxx> wrote:
Hi all,
In gluster 3.7 multiple features (Snapshot scheduler, NFS Ganesha, Geo-rep) are planning to use
additional volume to store metadata related to these features. This volume needs to be manually
created and explicitly managed by an admin.
I think creating and managing these many metadata volume would be an overhead for an admin. Instead
of that I am proposing to have a single unified metata-volume which can be used by all these features.
For simplicity and easier management we are proposing to have a pre-defined volume name.
If needed this name can be configured using a global gluster option.
Please let me know if you have any suggestions or comments.
Thanks & Regards,
Rajesh
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
+1 for
a. automatic creation of metadata volume over manual
b. configuration through gluster cli
few suggestions
a. disable access through any mechanisms other than fuse/gfapi.(Samba and NFS should not export.)
b. Restrict access to peer nodes.
Question:
What would be the replica count of the said volume and would that be ok for every use case
mentioned above?
Thanks,
Raghavendra Talur
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
