Essentially, gluster is a cluster distributed filesystem. It uses local storage on each 'server' node, and that can then be mounted on clients. It's intended for high performance compute resources, but works quite nicely for freeswitch backend. In my case, I have 4 servers accessing the cluster - 2 freeswitch nodes that are setup as an HA pair using keepalived (article already in wiki for that), 2 web server front end nodes for a local custom UI. On the backend, I have the three gluster nodes for file service (odd number to insure quorum) and 3 Percona XTraDB mysql nodes also operating as a cluster. Everything except the two freeswitch instances is running as a VM. The FS nodes are running on real hardware. The key difference with NFS is that the filesystem itself is redundant - so you can take any one of those backend nodes out of service and it isn't visible (except as a momentary hang) to the servers that have the filesystem mounted. -- Nathan On 08/01/2016 05:31 PM, jungle Boogie wrote:
Hi Nathan, On 1 August 2016 at 15:24, Nathan Neulinger <nneul@mst.edu> wrote:
I'm using gluster filesystem as backend storage...
Can you take a couple paragraphs to write what you can about it? I'll add it to the voicemail confluence page: https://freeswitch.org/confluence/display/FREESWITCH/mod_voicemail
Being totally ignorant about glusterFS, is this any different than NFS-like options?
From what I understand the voicemail code does not support non-filesystem style access at the moment.
Thanks for the confirmation!
-- Nathan
-- ------------------------------------------------------------ Nathan Neulinger nneul@mst.edu Missouri S&T Information Technology (573) 612-1412 System Administrator - Architect