Looking through the documentation I only ever find vague explanations of how high availability would work with LTSP. The scenario I have in mind is that the main ltsp-server crashes, but the clients can simply connect to one (or more) other servers where at least the file systems are replicated.
Since we are planning to use fat clients, session management should be no problem here (afaik that information would live in the ram of the clients then anyway). Also it wouldn't be that much of a deal if the boot-server would smoke down too. The only real issue are the file systems, where we plan to have two or three main read-only roms and diff-images for each node using unionfs/aufs. I understand that LTSP-cluster may be what I am looking for, but as I see it, ltsp-cluster is not meant for provisioning a cluster, but to scale the ltsp-server across a cluster. In our scenario most of our nodes in our cluster are fat clients that should connect to the ltsp infrastructure. How should I go about to avoid a single point of failure using ltsp to host multiple fat clients? thanks, alex. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
