Jeff, Depending on how many of these lowend VPSs you have, my suggestion would change, but with two it's fairly simple. Make them clones of each other and cron sync what you need from node-1 to node-2 then use heartbeat or something else fairly small to setup IP fail over. Within your master you can pool resources for PHP and mysql from the slave even though the slave isn't actually being used in a balanced situation.
-- If you can spare some resources to get 2 more even smaller VPSs say 256 in size, then we are talking a different story... With this setup, I would install cherokee on all 4 machines. On the two 256 machines, they would be complete clones of eachother, with one as a master and a slave. Cherokee and a shared IP would be the only necessary High Availability services between them, this would also using IP fail over. Then on your two 512 machines, they are now your application servers. Install PHP and MySQL on both and setup a file sync with another master and slave rsync setup. In cherokee, for each of these machines, setup fast-cgi for PHP use resources from both application servers. Also setup db replication in mysql. Then in the two 256 use a reverse proxy in cherokee to load balance each of the 512 application servers how ever you want for how ever domains you want to be balanced. Make sure cherokee's caching is working, or completely replace cherokee with Varnish on the load balancers, it's your preference. On Oct 27, 2010, at 2:49 PM, Jeff Johnson wrote: > Good day all! > > I want to present a scenario and see what the list members have to offer for > suggestions. Let's say you have three separate VPS servers (fairly low end, > 512MB RAM/ea) in geographically separate locations. You're hosting a handful > (three or four) domains that are dynamic PHP based sites using apps like > Wordpress or MODx. You want to set up a high availability solution for > hosting these sites across the three VPS servers. Cherokee, of course, is the > web server of choice in this scenario. > > There are likely different approaches one could take to achieve this. What > approach would you suggest? > > I'm going to try to set something similar up (if possible) and document the > process for others. Right now I'm seeking implementation suggestions. At this > point I'm just concerned with the web server and MySQL components of this > scenario. Mail and DNS are simple enough to figure out. > > Jeff > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
