[Gluster-users] Same server different networks and different bricks

[Elías David]

Hi, thanks For answering

I'm not really talking about control ing client access, see I have 5
OpenStack nodes that communicate through 10.10... Network and in the same
servers I'm planing to use a few disks for a gluster vol for cinder to use,
now in the same servers I have another set of disk that are going to be
used for a gluster vol to replace a storage in our internal network which
is 192.168.100.0/24 and for a complete different purpose that Cinder's
gluster.

So is like this:

Gluster for cinder using disks 2 and 3 from each of the 5 nodes in a vol
called CinderGluster usable to 10.10.10.0/24 network only

On the same servers another gluster vol for company storage called LanData
with disks 4 and 5 only usable to 192.168.100.0/24 network.

So two vols, different bricks, different networks but the same 5 servers
handling both
On Feb 10, 2014 12:30 PM, "James" <purpleidea at gmail.com> wrote:

> On Mon, Feb 10, 2014 at 11:56 AM, Elías David
> <elias.moreno.tec at gmail.com> wrote:
> > Hello all, I would like to do something but I'm not sure if it's
> possible, I
> > have 5 servers each with 6 ethernet ports, 4 ports working on say
> > 192.168.100.0/24 and 2 ports working on subnet 10.10.10.0/24.
> >
> > Each server has 6 disks and what I would like to do is to have a gluster
> > vol, say GVol0 using to disks from each server and available to
> > 192.168.100.0/24 and another vol, say GVol1 with another 2 disks from
> each
> > servers but available to subnet 10.10.10.0/24 only.
> >
> > I tried but I was unable to do this, is like gluster said "you already
> have
> > a vol on the 192.168... network and the 10.10... network points to the
> same
> > servers already peered in 192.168... network"
> >
> > Is my setup possible? Please if I'm not being clear let me know.
>
> If I understand correctly, all you need is the:
>
> auth.allow
>
> volume property.
>
> You should use that to control access, and as for the servers, build
> it all on the same network.
>
> Alternatively, set up two separate Gluster pools that don't peer with
> each other.
>
> Here's an auth.reject example (similar syntax to auth.allow) with
> Puppet-Gluster, for example:
>
> https://github.com/purpleidea/puppet-gluster/blob/master/examples/distributed-replicate-example.pp#L140
>
> HTH,
> James
>
>
> >
> >
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://supercolony.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140210/6ca2806b/attachment.html>