[Gluster-users] Separate Replication Traffic from Production Traffic

[James]

On Thu, 2013-10-24 at 16:13 +0200, Jan Pages wrote:
> Hi Gluster-Users,
>  
> I read that with GlusterFS you can separate the replication traffic
> from the production LAN.
You can do it with separate "lan" and "gluster" interfaces, using
routing if you want. I'm not sure there's a huge win in doing this. I
think you'll need to elaborate your use case. Since gluster doesn't
currently support Kerberos [1], you should make sure you're mounting on
trusted clients in a trusted zone anyways. If you really want to go down
this path anyways, I recommend using shorewall. If you need more
information, I can elaborate.

HTH,
James

[1] I'm pretty sure this doesn't really exist yet.

>  
> So far, I didn't find examples or documentation how it can be
> implemented. Is it done during volume creation? There doesn't seem to
> be an option for
> that: http://gluster.org/community/documentation/index.php/Gluster_3.2:_Setting_Volume_Options
>  
> Or is it done by Network Interface configuration? How?
>  
> Any examples or documentation about implementing this separation?
>  
> Thanks you for your hints!
>  
> Regards,
> Jan
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131024/622c166d/attachment.sig>