School server: Difference between revisions
Line 75: | Line 75: | ||
* [[Using SSH Keys]] |
* [[Using SSH Keys]] |
||
* [[Ejabberd Configuration]] |
* [[Ejabberd Configuration]] |
||
* [[School server network debugging]] |
* [[School server network debugging]] |
||
* [[Mesh Debug|How to debug networking in a crowded environment]] |
* [[Mesh Debug|How to debug networking in a crowded environment]] |
||
* [[Collaboration Network Testbed]] |
* [[Collaboration Network Testbed]] |
Revision as of 20:38, 30 December 2008
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
- XS Release Notes
- Overview of main XS Features
- XS Recommended Hardware describes the minimum hardware requirements for the School Server
- XS Installing Software has instructions for installing the latest School Server images
- XS Building Software
- XS Software Repositories
- School Identity Manager
- XS LiveCD
- XS Software Testing
Roadmap
- XS Roadmap (see also XS Changelog)
- Get Involved - join the mailing list and get started with one of these easy tasks. We also have some advanced tasks around Fedora packaging or configuration.
Technical notes
- XS-XO Interactions: how does the laptop talk to the server?
- XS Automount triggers
- XS Packaging
- XS Directory Layout for packagers
- Moodle implementation plan
- Ejabberd resource tests
Design Documents
The high-level design of the School server is described here - note that some may be slightly outdated:
- Scenario taxonomy School Server and XO laptop scenario taxonomy
- The Server Specification introduces the School Server and its functions
- School Service Names
Blueprints
In development
Implemented
Key tools
- 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.
Outdated
- Short Term Server Questions is a discussion of issues surrounding the immediate deployment of school servers
- Server Discussion describes services and enhancements possibly supported by the School Server
- XS Server P2P Cache
- Server Services
- XS Core and Contrib
- XS DevKit
See also
- IRC - #schoolserver on irc.oftc.net
- server-devel mailing list archives at http://lists.laptop.org/pipermail/server-devel/
- Using SSH Keys
- Ejabberd Configuration
- School server network debugging
- How to debug networking in a crowded environment
- Collaboration Network Testbed
- Bitfrost Security and Identity model
- Thin client