<p dir="ltr">Hi, thanks For answering</p>
<p dir="ltr">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 <a href="http://192.168.100.0/24">192.168.100.0/24</a> and for a complete different purpose that Cinder's gluster.</p>
<p dir="ltr">So is like this:</p>
<p dir="ltr">Gluster for cinder using disks 2 and 3 from each of the 5 nodes in a vol called CinderGluster usable to <a href="http://10.10.10.0/24">10.10.10.0/24</a> network only</p>
<p dir="ltr">On the same servers another gluster vol for company storage called LanData with disks 4 and 5 only usable to <a href="http://192.168.100.0/24">192.168.100.0/24</a> network.</p>
<p dir="ltr">So two vols, different bricks, different networks but the same 5 servers handling both</p>
<div class="gmail_quote">On Feb 10, 2014 12:30 PM, "James" <<a href="mailto:purpleidea@gmail.com">purpleidea@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Feb 10, 2014 at 11:56 AM, Elías David<br>
<<a href="mailto:elias.moreno.tec@gmail.com">elias.moreno.tec@gmail.com</a>> wrote:<br>
> Hello all, I would like to do something but I'm not sure if it's possible, I<br>
> have 5 servers each with 6 ethernet ports, 4 ports working on say<br>
> <a href="http://192.168.100.0/24" target="_blank">192.168.100.0/24</a> and 2 ports working on subnet <a href="http://10.10.10.0/24" target="_blank">10.10.10.0/24</a>.<br>
><br>
> Each server has 6 disks and what I would like to do is to have a gluster<br>
> vol, say GVol0 using to disks from each server and available to<br>
> <a href="http://192.168.100.0/24" target="_blank">192.168.100.0/24</a> and another vol, say GVol1 with another 2 disks from each<br>
> servers but available to subnet <a href="http://10.10.10.0/24" target="_blank">10.10.10.0/24</a> only.<br>
><br>
> I tried but I was unable to do this, is like gluster said "you already have<br>
> a vol on the 192.168... network and the 10.10... network points to the same<br>
> servers already peered in 192.168... network"<br>
><br>
> Is my setup possible? Please if I'm not being clear let me know.<br>
<br>
If I understand correctly, all you need is the:<br>
<br>
auth.allow<br>
<br>
volume property.<br>
<br>
You should use that to control access, and as for the servers, build<br>
it all on the same network.<br>
<br>
Alternatively, set up two separate Gluster pools that don't peer with<br>
each other.<br>
<br>
Here's an auth.reject example (similar syntax to auth.allow) with<br>
Puppet-Gluster, for example:<br>
<a href="https://github.com/purpleidea/puppet-gluster/blob/master/examples/distributed-replicate-example.pp#L140" target="_blank">https://github.com/purpleidea/puppet-gluster/blob/master/examples/distributed-replicate-example.pp#L140</a><br>
<br>
HTH,<br>
James<br>
<br>
<br>
><br>
><br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> <a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div>