Inside the OLPC School Server: Difference between revisions
m (add Template:Documentation stub) |
|||
(5 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
==Hardware== |
==Hardware== |
||
See also [[ |
See also [[School Server Specification#Hardware]] |
||
*Case |
*Case |
||
*Power |
*Power Supply |
||
**UPS (Un-interruptible Power Supply) |
|||
*Main board |
*Main board |
||
**[[ |
**[[School Server Specification#Processor_.26_Memory|Processor and Memory]] |
||
**Firmware |
**Firmware |
||
**Expansion slots |
**Expansion slots |
||
Line 16: | Line 17: | ||
==Software== |
==Software== |
||
See also [[ |
See also [[School Server Specification#Software]]. |
||
; LAMPS + Moodle |
|||
* Linux |
|||
* '''L'''inux ''Fedora distro'' |
|||
* Server apps |
* Server apps |
||
** [http://en.wikipedia.org/wiki/'''A'''pache_HTTP_Server Apache ''HTTP Server''] |
|||
** [http://en.wikipedia.org/wiki/'''M'''ySQL MySQL ''SQL database management system (DBMS)''] |
|||
** [http://en.wikipedia.org/wiki/'''P'''HP PHP5 ''PHP: Hypertext Preprocessor''] |
|||
** [http://en.wikipedia.org/wiki/'''S'''quid_cache Squid cache ''proxy server and web cache daemon''] |
|||
* Development |
* Development |
||
** [http://en.wikipedia.org/wiki/Moodle Moodle (CMS) ''Course Management System''] |
|||
* Web ''Content Filtering'' |
|||
** [http://en.wikipedia.org/wiki/DansGuardian DansGuardian] |
|||
==Backup== |
|||
[[School Server Specification#Backup]] |
|||
==Content== |
==Content== |
||
See also [[ |
See also [[School Server Specification#Library]] |
||
* Wikipedia subset |
* Wikipedia subset |
||
Line 60: | Line 72: | ||
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. |
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 [[XS_Server_Discussion|open to debate]], but [[ |
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. |
||
Currently, the School server is described by these documents: |
Currently, the School server is described by these documents: |
||
Line 74: | Line 86: | ||
*[[School Identity Manager]] |
*[[School Identity Manager]] |
||
*[[XS Installing Software]] has instructions for installing the latest School Server images |
*[[XS Installing Software]] has instructions for installing the latest School Server images |
||
*[[XS Building Software]] |
|||
*[[XS_Building_Software]] |
|||
*[[XS Software Repositories]] |
|||
*[[XS_Software_Repositories]] |
|||
*[[ |
*[[XS LiveCD]] |
||
*[[ |
*[[XS Server Software]] |
||
*[[XS Installing Software]] |
|||
*[[XS_Installing_Software]] |
|||
*[[ |
*[[XS Server P2P Cache]] |
||
==== See also ==== |
==== See also ==== |
||
Line 90: | Line 102: | ||
* [[Thin client]] |
* [[Thin client]] |
||
* [http://lists.laptop.org/pipermail/server-devel/ Server development mailing list] |
* [http://lists.laptop.org/pipermail/server-devel/ Server development mailing list] |
||
{{Documentation stub}} |
|||
[[Category:SchoolServer]] |
Latest revision as of 10:26, 13 November 2008
Hardware
See also School Server Specification#Hardware
- Case
- Power Supply
- UPS (Un-interruptible Power Supply)
- Main board
- Processor and Memory
- Firmware
- Expansion slots
- I/O
- USB
- CD/DVD
- Video
- Networking
- Storage
- Internet Connectivity
Software
See also School Server Specification#Software.
- LAMPS + Moodle
- Linux Fedora distro
- Server apps
- Development
- Web Content Filtering
Backup
School Server Specification#Backup
Content
See also School Server Specification#Library
- Wikipedia subset
Administration
- Updates
- Updating XOs
- Student and Teacher accounts
- Data exchange on non-Internet-connected servers
Troubleshooting and Repair
Troubleshooting School Servers
Other pages
Hardware specification
School Server Hardware
While the laptop is rightfully at the center of OLPC, a valuable peripheral is the school server. OLPC will be building and distributing school servers along with the laptops, to extend the storage and computation provided by each laptop, as well as providing a local library and a mesh portal to the Internet.
Unlike the laptop, the school server is more of a collection of services than a hardware platform. In a manner identical to the laptop, OLPC will collaborate with manufacturing partners to provide a cost-efficient hardware platform for running the recommended software. Unlike the laptop, the manufacturing collaboration will not be exclusive. Individual countries will be free (even encouraged) to design and manufacture their own school servers running derivatives of the OLPC school server software.
XS
This will be the school server designed by OLPC. It is mostly designed, but currently on hold as we reconsider manufacturers, and should reach early production volumes in spring 2008. See the specification.
XSX
This is a prototype school server, built for early school trials in country. It will be integrated from off-the-shelf components, and will be overpowered compared to a production school server in order to simplify early demands for system software. See the specification and the implementation.
School server
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.
Currently, 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 Building Software
- XS Software Repositories
- XS LiveCD
- XS Server Software
- XS Installing Software
- XS Server P2P Cache
See also
- IRC - #schoolserver on irc.oftc.net
- Troubleshooting School Servers
- How to debug in a crowded environment
- School server/School district networks
- Bitfrost Security and Identity model
- Thin client
- Server development mailing list