[Gluster-devel] metdata-volume for gluster

[Rajesh Joseph]

----- Original Message -----
> From: "Raghavendra Talur" <raghavendra.talur at gmail.com>
> To: "Rajesh Joseph" <rjoseph at redhat.com>
> Cc: "Gluster Devel" <gluster-devel at gluster.org>
> Sent: Wednesday, April 8, 2015 12:16:54 AM
> Subject: Re: [Gluster-devel] metdata-volume for gluster
> 
> On Tue, Apr 7, 2015 at 3:56 PM, Rajesh Joseph <rjoseph at redhat.com> 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 at gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> >
> 
> 
> +1 for
> a. automatic creation of metadata volume over manual

Right now it would be manual because automatic means we not only
need to create the volume but manage them. Which would need an
entire management frame. I think the next phase should be to 
achieve this.

> b. configuration through gluster cli
> 

What do you mean by configuration?

> few suggestions
> a. disable access through any mechanisms other than fuse/gfapi.(Samba and
> NFS should not export.)

Right now there is no restriction on export. I think it might be good to disable
NFS and Samba access.

> b. Restrict access to peer nodes.

I think we should consider this when we have the meta-volume management implementation.

> 
> Question:
> What would be the replica count of the said volume and would that be ok for
> every use case
> mentioned above?

Since we support only 3-way replication we are recommending the same.

> 
> Thanks,
> Raghavendra Talur
>