Public bug reported:
We could use either
a) A choice of which server you wish your ldm session to login to (if different
from the plain dhcp server) [Fairly trivial change. We can see how the python
would work, just don't have a python + gtk/glade guy here]
b) Load-balancing client sessions that detects when a server is offline, and
will failover to the other(s), as well as ensuring that one LTSP server is not
over-loaded by too many sessions. (Also, a way to put a server offline, easily,
for maintenance.)
Reason being, we're running a full hardware failure redundant system at
our customers site (~50 users, DRDB backends with heartbeat failover).
We've been forced to use GDM, instead of LDM (that was a *really* _fun_
game of hacks...), because there's currently no documented way to cope
with a server being offline or down for maintenance with LDM.
Theoretically, you could enter client specific information into
lts.conf, and have an automatic re-write on server failure, but thats
just too much work.
Our customers site is a mainly Ubuntu shop. Ubuntu servers, Ubuntu
Desktops. We're only now working on upgrades to feisty, because of the
sheer amount trouble caused getting Dapper LTSP (GDM) working with some
semblance of failover.
This is a wish-list request, although its the main reason we're not
using LDM in our sites, so if you could fix it, it'd be helpful.
** Affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
--
[Feature Request] Need some kind of server chooser / failover system in ldm
login.
https://bugs.launchpad.net/bugs/132984
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
