Image of the setup is at: http://share.robotics.net/gluster.png The setup is as follows; eight servers each in NYC and LAX datacenters. I have not decided on RIAD 5 or 6, but each server has 8 750 gig disks connected to a 3ware controller, with each box connected to a switch over 3 bonded Gig E interfaces. The boxes boot off a SAN over a fiber channel interface and each box is used as a storage server, client and XEN host. The requirement is for three share exports, two that are unify shares for NYC and LAX and a 3rd that is a AFR between NYC and LAX. The idea is that we will store things that stay local in say /share-nyc or /share-lax and store files that need to be replicated between sites in /share that is afr of the two sites. High availably is important, the plan is to always use servers in pairs, server 0 for the brick and server 1 for the mirror of that data using AFR. Each server pair forms a block, with 4 blocks (8 servers) forming each city share unify. Data that needs to be in both NYC and LAX would actually be stored 4 times, twice in each city. To keep reads local, I was planing on using nfu forcing each city to prefer local reads. Would this work? Is gluster ready for someting like this? One thing I have not figured out is how to deal with name space, any ideas on that? Also, what issues will I run into with AFR between two cities 3000 miles apart? That latency is obviously going to be 60 ms more then between local servers, does this cause a problems? ><> Nathan Stratton CTO, Voila IP Communications nathan at robotics.net nathan at voilaip.com http://www.robotics.net http://www.voilaip.com
