LTSPManager

Differences between revisions 1 and 3 (spanning 2 versions)
⇤ ← Revision 1 as of 2006-06-07 13:30:27 →
Size: 522
Editor: p5089EFDD
Comment:
← Revision 3 as of 2006-11-08 20:49:28 → ⇥
Size: 1490
Editor: 207
Comment: + design for whether LTSP is running
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
We will create a nice, gui management tool for LTSP, and Edubuntu administrators to manage their thin client network.
Line 17: Line 19:

...

`• LTSP is not running. ( Start )`
`@ LTSP is running. ( Stop )`

...
Line 28: Line 37:
 * We decided in Detroit that a requirement for LTSP should be some kind of gui management.
 * Should allow for different target architechtures.
 * We need to add the management of the lts.conf file.
 * ltsp-manager is already in universe, simply needs some more work.
 * Doesn't have a .desktop yet, should install under the Administration.
 * Move over some of Jim's code for testing the status of some services.
 * We are missing handling of screen scripts. Need to add that.
 * Per client as well as default settings.
 * Either grab the syslog for dhcpd, or do an arp -a to automatically grab all the mac addresses on the network.
 * Promote a dynamic ip address to a static ip address.
 * Update the chroot via apt.

Summary

We will create a nice, gui management tool for LTSP, and Edubuntu administrators to manage their thin client network.

Rationale

Use cases

Scope

Design

...

• LTSP is not running.           ( Start ) @ LTSP is running.               ( Stop  )

...

Implementation

Code

Data preservation and migration

Outstanding issues

BoF agenda and discussion

  • We decided in Detroit that a requirement for LTSP should be some kind of gui management.
  • Should allow for different target architechtures.
  • We need to add the management of the lts.conf file.
  • ltsp-manager is already in universe, simply needs some more work.
  • Doesn't have a .desktop yet, should install under the Administration.
  • Move over some of Jim's code for testing the status of some services.
  • We are missing handling of screen scripts. Need to add that.
  • Per client as well as default settings.
  • Either grab the syslog for dhcpd, or do an arp -a to automatically grab all the mac addresses on the network.
  • Promote a dynamic ip address to a static ip address.
  • Update the chroot via apt.

CategorySpec

LTSPManager (last edited 2008-08-06 16:18:23 by localhost)