XS Server Hardware
This is a description of the first implementation of the School server. It describes the hardware and software implementation details, including the management of services. The actual services provided by the School server are described in the Server Services document, with an accompanying discussion of desired services.
Contents
Hardware Specifications
The School server hardware platform has not been selected at this time.
The current plan is to provide two hardware platforms. One, XSX, available by mid-March, will allow for School server software testing and early deployments in areas where power mains are at least periodic if not continuous. The second platform, XS, would be reduced in cost and power, and should be available for deployment beginning in October.
XSX Specifications
This is a version with a target date of mid-March. The primary goal is to support development of the School server/laptop software, including early trials.
The initial spec is similar to an OLPC laptop with attached USB hard drive and USB CD reader. The only defined aspect is an x86 family processor.
As this is a very limited production model (10s - 100 ?), flexibility wins out over cost. Consumer PC hardware is a possibility.
There are no power consumption targets for this device. A UPS may be suggested for trial deployments in areas of uncertain power.
XS Specifications
This is the hardware for deployment.
The school server must meet all of the environmental constraints of the XO laptop with the exception of daily rough handling!
It may or may not be based on an x86 platform. The pros and cons are: ... (feel free to editorialize)
Software Specifications
The School server should run roughly the same Linux OS as that in the XO laptop. The release process will probably be different, but the kernel and most libraries should be identical.
Development Toolchain
What is the cost of this toolchain being different from that used for the XO laptop?
Upgrades
How is the School server upgraded ?
Service Management
How are services on the School server installed, configured, managed, and updated ?
A web based interface is a natural candidate for performing these actions on the School server.
Scalability
A School server should serve up to sixty students. In schools with more students, how are the servers interconnected to minimize the management overhead ?
