On Thu, 13 Nov 2014 06:06:28 PM Alex Crow wrote: > AFAIK multiple network scenario only works if you are not using Gluster via > FUSE mounts or gfapi from remote hosts. It will work for NFS access or when > you set up something like Samba with CTDB. Just not with native Gluster as > the server always tells the clients which addresses to connect to: ie your > storage hosts will always supply the connection details of the hosts that > are configured in gluster to your storage clients. > > I wonder if this could be gaffer-taped with some bridging/vlan/arp spoofing > trickery but I'm not sure I'd trust such a hack. > > It would be *really* nice if there was a way to set up gluster so you could > specify different IPs for backend and frontend operations. Yes, but I don't think that was what the OP was asking. I believe what he wanted to know was how to ensure the gluster servers talked to each other over his 10G interfaces. In that regard I thought he was correct - just setup the servers via the IP for the interfaces. I have a multiple interface setup: eth0: 192.168.5.0/24 : 1G bond0: 10.10.10.0/24 : 1x1G (Bonded) To route everything through bond0: from 10.10.10.240 gluster peer probe 10.10.10.241 gluster peer probe 10.10.10.242 gluster volume create datastore1 replica 2 transport tcp \ 10.10.10.240:/mnt/gluster-brick1/datastore \ 10.10.10.241:/mnt/gluster-brick1/datastore \ 10.10.10.242:/mnt/gluster-brick1/datastore Net monitoring shows all gluster traffic going through bond0 as desired. I realise this is old hat for most on the list, but I just wanted to confirm it for the op. -- Lindsay
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
