OLE Nepal:Schoolserver: Difference between revisions
No edit summary |
|||
Line 22: | Line 22: | ||
#The [http://hg.olenepal.org/NEXS_scripts install.sh] and [http://hg.olenepal.org/NEXS_scripts postinstall.sh] scripts are copied to the usb drive for use in the '''Second Boot''' and '''Postinstall''' procedures. |
#The [http://hg.olenepal.org/NEXS_scripts install.sh] and [http://hg.olenepal.org/NEXS_scripts postinstall.sh] scripts are copied to the usb drive for use in the '''Second Boot''' and '''Postinstall''' procedures. |
||
==NEXS installation== |
==NEXS installation== |
||
NEXS is installed on the schoolserver from one or two USB sticks. There is also a [http://hg.olenepal.org/NEXS_scripts Boot CD] which is used when the server is not able to boot from USB or USB is not in the boot sequence before the hard drive. The Boot CD provides a 'boot' loader |
NEXS is installed on the schoolserver from one or two USB sticks. There is also a [http://hg.olenepal.org/NEXS_scripts Boot CD] (don't see an iso here, only scripts) which is used when the server is not able to boot from USB or USB is not in the boot sequence before the hard drive. The Boot CD provides a 'boot' loader |
||
for the usb drive. |
for the usb drive. |
||
Revision as of 19:53, 7 January 2009
Schoolserver
The schoolserver provides many services in support of the XO laptops.
Schoolserver Hardware
The schoolserver is a desktop with a minimum 1gb of memory and a minimum of 160gb hard drive capacity. Specifically, the server should provide 2gb of disk space for each supported XO plus 50gb for content. It must have one or more USB 2.0 ports and the ability to boot from USB. If the server cannot boot from USB or the boot sequence does not have USB ahead of the hard drive, it must have a CD reader. It must have two NIC interfaces. Normally, one of these is provided on the motherboard. The second is normally an added PCI card. Server installation and administration does not require a monitor, keyboard, or mouse. In addition to the server, the second NIC is connected to an Access Point (e.g Lontech WL54G-BR). The Access Point (AP) must be configurable via an http address.
NEXS
NEXS is the software installed on the server. It is derived from an OLPC XS release.
- NEXS 1.0 derived from OLPC XS-163 is installed currently at the pilot schools.
- NEXS 2.0 derived from OLPC_XS-0.4 is currently in test and is planned for installation in December 2008.
- NEXS 3.0 to be derived from OLPC_XS-0.5 or OLCP_XS-0.6 is planned for installation in schools in academic year 2009-10.
NEXS build
- NEXS 2.0 is built by a bash script build-final.sh. This script produces the NEXS iso image.
- The iso image and other necessary files are copied to a usb drive using livecd-iso-to-disk HowTo
- Additional content files are placed on the usb drive to be copied to /library on the schoolserver. HowTo
- The install.sh and postinstall.sh scripts are copied to the usb drive for use in the Second Boot and Postinstall procedures.
NEXS installation
NEXS is installed on the schoolserver from one or two USB sticks. There is also a Boot CD (don't see an iso here, only scripts) which is used when the server is not able to boot from USB or USB is not in the boot sequence before the hard drive. The Boot CD provides a 'boot' loader for the usb drive.
The NEXS installation procedure is capable of installing NEXS on a 'headless' schoolserver (one which does not have a monitor or keyboard). It also includes a series of tests to verify the network configuration, connectivity of the server with the XOs, and basic functionality of the schoolserver.
Services
The schoolserver provides the following services:
- protected access to the internet for the associated laptops via DansGuardian
- backup storage for the XO's datastore
- access to Pustakalaya, a library of educational materials maintained on the server
- access to educational activities via Moodle
- access to additional activities which the user of an XO can install or update via the XO control panel
- provides a higher capacity mesh network through the attached AP using ejabberd, a jabber server
- provides automatic authentication for XO users so that the conventional username and password login is unnecessary.