---+ Instant Labs This topic is a WIP.
The idea of an Instant Lab is to provide the community with the ability to open a small computer lab in less than a day. This could be a small remote lab with no internet access or a large lab with broadband connectivity. Here is what an InstantLab should be:
- Be able to run with no internet connectivity.
- Be able to take advantage of any internet connectivity provided.
- Create its own private network for student computers.
- Student computers can boot from the network or have a minimal install on board.
- Be easy to install.
- Be easy to use.
---++ System Requirements The InstantLab should have the following systems requirements:
XXX: We need to verify the system requirements to make sure the minimal specs still result in a "usable" system.
*Central Server*
- 800MHz or above processor speed
- 512 MB memory
- 20GB harddrive
- Ethernet NIC (10/100 recommended)
- CD-ROM drive
*Firewall/Router* (if connecting to the internet)
- 300MHz or above processor speed
- 64MB or above
- 2GB harddrive
- (2) Ethernet NICs
- CD-ROM drive for initial installation
*Work Stations* (w/o harddrive)
- 200MHz processor speed (500MHz recommended)
- 128MB or above (256MB recommended)
- Ethernet NIC
- CD-ROM drive if NIC does not support network booting
*Work Stations* (w/ harddrive)
- 200MHz processor speed (500MHz recommended)
- 64MB or above (128MB recommended)
- Ethernet NIC
- CD-ROM drive if NIC does not support network booting
---++ Installation Installing an InstantLab should be very easy. Here is what the requirements for an installation system are:
- Bootable CD-ROM with an easy to use installer.
- CD should ask if you want to install the server, install terminal client, install workstation client, etc
- A seperate CD for workstations without network boot support (or where network boot is not available).
- Should broadcast on a pre-determined port asking for the class server to respond.
- Should get configuration form server response (mount NFS, etc)
- If terminal services are available, should give the user the choice to log in under
- XDMCP or work as a diskless workstation.
- (optional) Autodetect system capabilities to determine if it meets the minimal requirements
- to work as a workstation. If it fails, automatically selects terminal services.
- A network boot image (same as CD, maybe even same image).
- Server Install CD should also be able to install a firewall/router on another computer
---++ Xen Components Xen is to be used as a virtualization system for different network services, based on lab needs. Here are some examples of services that could be implemented as Xen Servers
- Base System (Domain 0)
- Contains software to perform basic configuration on setting up a lab (TODO: explain)
- ...
-- Main.SteveTindle - 09 Oct 2005