Merging ltsp-cluster-client in upstream code

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

With xinitrc.d having recently been added to LTSP I now have most of the
structure to merge ltsp-cluster-client in the upstream code.

Before I start moving our scripts to ldm rc.d and xinit rc.d directories
I want to make sure nobody has a problem with that.

All of these will only be used if the ltsp-cluster configuration file
exists in /etc/ltsp/, this one is currently called directory.conf but
will likely be renamed cluster.conf as that name makes more sense.

What will be included will basically be (extracted from our bzr branch):

- - ldm/rc.d/S99-ltsp-cluster
  Registers the session in the control center so we know when, from
where and on what server someone is connected.

- - ldm/rc.d/K99-ltsp-cluster
  Un-register the session on logout

- - ltsp/screen.d/tech-cluster
- - ltsp/screen.d/autologin-cluster
- - ltsp/screen.d/ldm-cluster
- - ltsp/screen.d/rdesktop-cluster
  These four won't be merged as is, they'll be updated so the only
changes they currently do (basically play with the environment) will
happen in xinit rc.d scripts instead of needing some extra screen.d
scripts. They basically just ask our control center for a lts.conf, then
source it, they also ask the loadbalancer and add the ssh key of the
application server when missing.

- - usr/bin/getltscfg-cluster
  Our main script, it's used to interrogate the control center, get the
environment and is used by our rc.d scripts to register/unregister the
sessions.

- - usr/sbin/inventory
  Used to get some basic information about the computer (ram, cpu and
pci devices), it's then used by getltscfg-cluster to be used in the
control center for hardware specific configuration.

- - man/getltscfg-cluster.1
  The manpage for getltscfg-cluster (will likely need to be updated)


You can have a look at the code there:
https://code.launchpad.net/~stgraber/ltsp/ltsp-cluster-client.devel

- From a packaging point of view, merging that upstream won't touch any
existing file, so if you don't want to include it in your distro, just
don't package the files. Though, the scripts shouldn't be distro
specific so even if your distro doesn't have the other components
packaged, your will still be able to have your chroot and application
server running your distro with the other components running on Ubuntu
(only supported distro so far).

Please ask any question you may have regarding that change.

Thanks

Stéphane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkkk6UIACgkQjxyfqkjBhuxg5QCdEXG4UXIjThJJjUB+bI6U4GAk
dyMAni8aDUL0q3O4QV468a4FoGNaoFW5
=7UOf
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net