School server: Difference between revisions
No edit summary |
|||
Line 6: | Line 6: | ||
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 [[XS_Server_Discussion|open to debate]], but [[XS_Server_Services|at a minimum they include]] internet communication and storage resources to the school's wireless mesh. |
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 [[XS_Server_Discussion|open to debate]], but [[XS_Server_Services|at a minimum they include]] internet communication and storage resources to the school's wireless mesh. |
||
== |
== Roadmap == |
||
⚫ | |||
The school server is in heavy development at the moment (March/April 2008) - following the [[XS Roadmap]]. |
|||
== Design Documents == |
|||
⚫ | |||
*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 |
Revision as of 14:50, 21 March 2008
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 and storage resources to the school's wireless mesh.
Roadmap
The school server is in heavy development at the moment (March/April 2008) - following the XS Roadmap.
Design Documents
The School server is described by these documents:
- The Server Specification introduces the School Server and its functions
- Server Services described the services supported by the School Server
- Server Discussion describes services and enhancements possibly supported by the School Server
- XS Server Software describes the software system being built for release, and has instructions for downloading and installing the software
- The XS Server Specification describes the School Server hardware platform in much more detail.
- 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
- School Service Names
- School Identity Manager
- XS Installing Software has instructions for installing the latest School Server images
- XS Configuration Management has aids to configuring the software for your school
- XS Building Software
- XS Software Repositories
- XS LiveCD
- XS Server P2P Cache
- XS Software Testing
- XS Backup and Disaster Recovery
See also
- IRC - #schoolserver on irc.oftc.net
- Using SSH Keys
- Active Antenna
- Ejabberd Configuration
- School server network debugging is helpful. Troubleshooting School Servers is so incomplete as to be useless.
- How to debug networking in a crowded environment
- Collaboration Network Testbed
- School server/School district networks
- Bitfrost Security and Identity model
- Thin client
- http://lists.laptop.org/pipermail/server-devel/