LtspConvergence

Revision 2 as of 2006-06-20 14:42:54

Clear message

Summary

Rationale

The upstream LTSP project is currently maintaining a large number of source packages and a complete build environment that are needed to build the "official" LTSP binary packages. This list of packages includes glibc, kernel, init, X.org, bash, etc. The MueKow specification outlines a new method of creating the LTSP binaries that are executed by the thin client. Ubuntu's implementation of LTSP is based on the MueKow specification.

The existence of 2 different versions of LTSP has created some confusion within the LTSP community and without a clear statement of the direction of LTSP, it is perceived as a lack of leadership within the project.

Use cases

Scope

Design

Implementation

There are a number of issues that need to be addressed, before we can abandon the current upstream LTSP method and Before Ubuntu's LTSP can be a 1:1 replacement, a few problems remain to be solved. Both LTSP and Ubuntu should be able to work towards solving these in the next few months, with a target of edgy of being a "beta" for a replacement of the current LBE (LTSP Build Environment).

Code

Data preservation and migration

Outstanding issues

  • While running X over SSH is a simple method of encrypting the X traffic, doing so puts a heavy strain on the server. This causes a scaling problem when deploying LTSP in schools and businesses, where the workstation-to-server ratio is on the order of 50:1 or more. It has even been reported that there are huge performance issues when running only a single thin client trying to view a website with flash animation.
    • Should be Trivial, just some docs and perhaps a minor touch up to the code for avoiding gettys.
  • Local device support
    • Coming for Edgy
  • Local printing.
    • No plan yet, but probably pretty simple to implement.
  • Etherboot support,
    • Coming for Edgy
  • Scanner support
    • ???
  • rdesktop for client.
    • ???
  • network swap
    • Coming for Edgy.
  • Needs to run 64 meg clients (32mb w/swap)
    • Some more whittling required? Probably very close.

BoF agenda and discussion

CategorySpec