Hi, If I understand correctly, it shouldn't work. You need all your peers and all of your clients to be able to talk to each other. The only way I've found around that is to use NFS, that way the client only needs to see one of the bricks, but you lose HA so it's not that interesting. On Wed, May 31, 2017 at 01:46:23PM +0100, lejeczek wrote: > dear fellas > > I've a pool, it's same one subnet. Now I'd like to add a > peer which is on a subnet which will not be > available/accessible to all the peers. > a VolV > peer X 10.0.0.1 <-> 10.0.0.2 peer Y 192.168.0.2 <-> peer Z > 192.168.0.3 # so here 192.168.0.3 and 10.0.0.1 do not see > each other. > > Above is not the best practice I understand, or, it does not > matter to gluster and it will just work? > Does anybody have experience with such a setups? > > many thanks. > L. > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://lists.gluster.org/mailman/listinfo/gluster-users
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
