Thanks for the ideas.
We are a statistics research department, so folks are very keen on where
they run their apps since any given simulation may have different RAM
and processing requirements. So really, the only thing I want to
virtualize is the X session itself. All they do in the X session
One approach worth considering would be to dedicate specific
applications to their own isolated server on the backend. This wouldn't
reduce the number of server machines you have, but it would allow you to
devote hardware resources to those apps that need it, and not waste
hardware on those th
Statistical load spreading should be trivial -- just a matter of sharing
home directories and then spreading your clients around your various
servers.
True load balancing? I have no idea if/how that would work. Hopefully
someone else can answer that.
Jeff
---
There's such a huge amount of products (commercial) and so many options
open-source that I would just like a little feedback as to what others
would do in this situation.
I have 80 thin-clients that boot off of an LTSP server that is pretty
bare bones. The user is presented with a login script
