School server: Difference between revisions

From OLPC
Jump to navigation Jump to search
(FIELD_OTHER)
m (Reverted edits by 67.223.234.160 (Talk) to last version by RafaelOrtiz)
Line 53: Line 53:
* [[XS_Blueprints:Datastore_Simple_Backup_and_Restore|Datastore Simple Backup and Restore]]
* [[XS_Blueprints:Datastore_Simple_Backup_and_Restore|Datastore Simple Backup and Restore]]


== Key tools ==
FIELD_MESSAGE_lic4tchi

* [[Ds-backup]] - backup infrastructure
* [[XS-rsync]] - the rsync publishing, used for XO OS updates.
* [[XS-tools]] - grabbag of useful utilities. The NOC team will also want this :-)
* [[XS Automount triggers]] - used by [[Xs-activation]], [[Xs-activity-server]], [[Xs-rsync]] and probably others.
* [[XS-activation]] - activation lease server.
* [[XS-activity-server]] - serves packages over http.


== Meetings ==
== Meetings ==

Revision as of 07:06, 17 December 2008

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



The XO School server, or XS, is one of the products of the OLPC project, designed to complement the XO laptop. It is a Linux-based OS (a Fedora-based distribution) engineered to be installed on generic low-end servers. We outline hardware recommendations and in the future, we may offer a hardware platform specially designed for the role.

When we deploy one laptop per child, we must also provide additional infrastructure extending the capabilities of the laptops. While the laptops are self-sufficient for many learning activities, other activities and services depend on the School Server providing connectivity, shared resources and services. Services, tools and activities running on the School Server allow asynchronous interaction, can use larger storage capacity, and take advantage of the processing power of the XS.

Mailing List

Join the server-devel mailing list, search the list archives at archives or find us on the IRC channel: #schoolserver on irc.oftc.net.

XS Documentation

Roadmap

Technical notes

Design Documents

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

Blueprints

In development

Implemented

Key tools

Meetings

Slightly Outdated

See also