School server: Difference between revisions

From OLPC
Jump to navigation Jump to search
(typo)
Line 28: Line 28:
*The [[School_Server_Specification|Server Specification]] introduces the School Server and its functions
*The [[School_Server_Specification|Server Specification]] introduces the School Server and its functions
*[[School Service Names]]
*[[School Service Names]]

== Blueprints ==

* [[XS_Blueprints:OTP_root_passwords|OTP Root Passwords]]
* [[XS_Blueprints:Remote_management|Remote management]]


== XS Documentation ==
== XS Documentation ==

Revision as of 00:05, 5 June 2008

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


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:

Blueprints

XS Documentation

Slightly Outdated

See also