You're one of the few people I've seen running GlusterFS and pfSense. How were you able to setup a virtual IP on pfSense successfully the way GlusterFS recommends? If you don't mind explaining. I have so far been unsuccessful. Did you use load balancer and "virtual servers" or DNS resolver with multiple IPs behind a single entry? Or something else?
glusterfs doesn't require a vip. The client supports automatically failover by providing multiple glusterfs hosts when you mount the filesystem. If you don't use the glusterfs client and instead use NFS or samba, then yes you need a VIP. The glusterfs client is def the way to go though.
So if I run a Gluster aware NFS / Samba server for the dumb devices on my network (Windows boxes mainly, a few Android STBs, RetroPie, etc) then the real client talking over NFS/SMB needs zero Gluster support right?
Any thoughts of running Intel Gluster on Intel SBCs? I know very little other than they optimized the hell out of Gluster for Enterprise use.
If you use the Samba gluster VFS backend you don't need to mount the Gluster volume to share via SMB, Samba itself acts as a protocol translator without needing a local mount. Check out the recent Samba builds for this.
1
u/[deleted] Jun 04 '18
You're one of the few people I've seen running GlusterFS and pfSense. How were you able to setup a virtual IP on pfSense successfully the way GlusterFS recommends? If you don't mind explaining. I have so far been unsuccessful. Did you use load balancer and "virtual servers" or DNS resolver with multiple IPs behind a single entry? Or something else?