His flow mostly likes this,
Clients <-> Web services <-> Storage
Even the web servers will be making the call with another http services for the mp3 resource. He still needs the storage to put the files. gluster looks a good one to him. It looks like having most features of commercial products.
------------ Banyan He Blog: http://www.rootong.com Email: banyan@rootong.com
On 2012-11-20 1:12 AM, Les Mikesell wrote:
On Mon, Nov 19, 2012 at 7:48 AM, Ted Miller tedlists@sbcglobal.net wrote:
If RHSS is not available or suitable, other suggestions welcome. I need a file system/server with:
- primary function is serving MP3 files for playback in a radio station
environment in Haiti * if the system goes down all your clients (listeners) know it * they know it NOW * they know how long it takes to get it back up
- High Availability as the primary concern
- ability to administrate via web interface or similar by non-Linux-savvy
IT staff.
- ability to grow file system from 2-3TB to 20-50TB by simply adding disks
and/or adding 'bricks'
- clients will all be Windows computers, so files accessible by CIFS
- critical application is read-only
- prefer a system that would continue serving files even if the network
goes down (but have not found such a system yet for Windows clients).
Is it possible to change the application so it uses http to get content or uses a distributed database natively? Distributed failure-tolerant systems are a lot easier if you don't even try to provide filesystem semantics that require a lot of atomic operations.