You are on page 1of 34

Medusa Project

Sameer Verma, Ph.D. Bo Kim

Implementing LTSP at SF State University

Thank you!

Bo Kim – taking up the challenge Jack Tse and Don Strickler – loaning us a switch Tony Chan and Karl Schackne (BUS computing) – for letting us use the lab. Edubuntu team – making an excellent LTSP distro!

     

Brief introduction to LTSP Requirements for running LTSP Advantages and disadvantages Medusa - LTSP at SF State Possible implementation scenarios Informative links

 LTSP allows for a single point of configuration and control  Great for lab environments .   All programs run on the server Clients run a thin Linux base with network and X session capabilities.What is LTSP?  Linux Terminal Server Project  Allows “thin” clients to connect to a Linux Terminal Server.

How it works  A “thin” client performs a Preboot Execution Environment (PXE) boot and retrieves an IP from the LTSP server via DHCP.  dhcp server runs on the private network interface on the LTSP server PXE DHCP request DHCP response .

The client loads the Linux image and starts the X window system via secure shell (ssh)  client images and server have ssh keys DHCP response + TFTP Linux image X session forwarded over ssh .How it works   A small footprint Linux kernel is sent to the thin client computer via TFTP.

but are forwarded via ssh and displayed on the thin client. X session forwarded over ssh mouse+keyboard . Feedback from the user (keyboard & mouse) are sent back to the server over ssh as well.How it works   All programs execute in a X session on the server.

0/24 eth0 SFSU 130.What Does it Look Like? firewall eth1 192.0/24 .

2 Network Interface Cards Private interface preferably gigabit  Clustering?  Not sure if it is possible .     Intel Xeon processor.Hardware Requirements  Server  CPU should be powerful enough to run multiple X sessions. 75-150MB of RAM per client.

Pentium II and above with 64MB RAM and 4MB display card.Hardware Requirements  Client  Minimum  Pentium II with 48 MB RAM and a 2MB display card. Identical hardware preferred  Recommended   .

Networking Requirements  Network  Avoid   Hubs 10-BaseT cards 100 Mbps switch 100-BaseT cards Gigabit switch. 100 Mbps switch with 1 Gbps uplink to the LTSP server.  Preferred:    Ideal:   .

   LTSP (if not installed natively) Most distros except Ubuntu and Debian do not have LTSP 5. LTSP 5 is significantly different  LTSP 5 builds thin-client environment off of the server environment.Software Requirements  A Linux distribution with or without LTSP included. .

It uses X forwarded over ssh instead .Software Requirements  Four services running on the LTSP server:     DHCP for IP address leases TFTP for initial netboot kernel NFS for forwarding filesystems SSH for all communication on the LAN  Note: Ubuntu does not use XDMCP.

Advantages  Disadvantages  Diskless clients Highly Centralized   Invest in powerful server Need a fast network Documentation is weak  patches firewalling no licensing fees LDAP auth     Cost effective   Many references to LTSP 4. especially multimedia  Change lab footprint as needs grow . Time sensitive apps will not work well.x  Customized profiles   Sabayon seems broken in Ubuntu Feisty.

but appears as two .Medusa Project  LTSP server  Note: Single processor.

Medusa Project   10/100 Mbps unmanaged switch 20 clients      Dell Optiplex Pentium 4 256MB RAM 15 inch flat panel Some have speakers .

Medusa Project   Edubuntu – Ubuntu for Education Additional software installed:  Webmin  Firewall/NAT Customized user profiles and lockdown (built-in. Seems to be broken in Ubuntu Feisty  Sabayon   . via pessulus) tool.

Swap and NET behavior  We looked at behavior with one and multiple users (1+8) on the LAN. Note: We did not use a built-in screen capture program because it muddies the parameters.Medusa Project  Captured CPU. We used a video camera instead.  . RAM.

Medusa Project All clients at login screen CPU RAM SWAP NET .

Medusa Project One client starts Firefox CPU RAM SWAP NET .

Medusa Project One client starts OOo CPU RAM SWAP NET .

Medusa Project Multiple clients start OOo CPU RAM SWAP NET .

Medusa Project First client starts video CPU RAM SWAP NET .

Medusa Project Multiple clients start video CPU RAM SWAP NET .

Medusa Project Multiple clients finish video CPU RAM SWAP NET .

Medusa Project All clients logout CPU RAM SWAP NET .

  Note: Lab machines will be on a private network  Administrator can maintain lab logs for accounting . Ubuntu Linux via LTSP.Services at the LTSP Lab  Dual boot  Windows XP localboot. Both environments get dhcp and firewalling via LTSP server.

Services at LTSP lab   Internet access Office Automation  OpenOffice GIMP Inkscape Scribus  Graphics     Printing via network .

Thin Client Manager .

Webmin .

 Traffic Shaping   Support Windows apps via Win4Lin or VMWare Possible to boot PPC thin clients  .Future use at SF State  Domain Authentication  Users will be able to use their SFSU accounts to logon via LDAP More efficient network load balancing that will be conducted on the LTSP server. .Informative Links • • • www.

..Demo time….

Questions? .