School server: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Tried to separate out the outdate, the design docs, and the XS implementation docs)
(typo)
Line 42: Line 42:
*[[XS Backup and Disaster Recovery]]
*[[XS Backup and Disaster Recovery]]


== Sligthly Outdated ==
== Slightly Outdated ==
*[[Trial1 Server Software]] describes the proposed first revision of the server software
*[[Trial1 Server Software]] describes the proposed first revision of the server software
*[[Short Term Server Questions]] is a discussion of issues surrounding the immediate deployment of school servers
*[[Short Term Server Questions]] is a discussion of issues surrounding the immediate deployment of school servers

Revision as of 14:32, 2 May 2008

  This page is monitored by the OLPC team.
  english | 한글 | español HowTo [ID# 128989]  +/-  


When we deploy one laptop per child, we must also provide additional infrastructure extending the capabilities of the laptops. While the laptops are largely self-sufficient, a mesh portal providing connectivity and shared resources greatly extends their utility.

These persistent services required by OLPC laptops could conceivably be implemented in a fully distributed manner. They are , however, currently provided more economically by a centralized local resource, the school server. The functions provided by this server are open to debate, but at a minimum they include internet communication, a centralized presence service and storage resources to the school's wireless mesh.

Roadmap

The school server is in heavy development at the moment (March/April 2008) - following

Technical notes

Meetings

Design Documents

The high-level design of the School server is described here - note that some may be slightly outdated:

XS Documentation

Slightly Outdated

See also