School Server/RIT

From Sugar Labs
Jump to navigation Jump to search

For RIT Honors Seminar project.

School Server Fall 2009 Seminar Project

(Draft, please contribute)


  1. Provide a school server test and development environment for the Honors Seminar participants,
  2. Develop School Server systems administration skills,
    1. Backup registered XOs or Sugar Sticks
    2. Host Moodle content developed in class
  3. Test and Debug OLPC - Sugar Labs School Server software
  4. Develop a School Server SysAdmin training curriculum for volunteers who want to support an OLPC or Sugar deployment


  1. RIT LTL or other hardware
  2. OLPC XS development builds,
  3. and the list archives, archive with search
  4. OLPC projects/xs repository,
  5. Martin Langhoff's git repository,

Note: Admin log is located on the server at /var/log/adminlog.log

Possible task

  • Fix Ejabber
  • Configure Moodle to our needs
    • Create a Activity(Application) for RIT XOs so students can easily access Moodle
  • Moodle xo python api
  • XO Backup/Restore
  • XO Security [1]

Completed Tasks

  • Install Moodle
    • Apache (httpd)
    • PHP
    • MySql
    • Install Moodle
    These experiments are fine to understand the above services. In the end, we want to add instructions and some supporting scripts to modify the standard OLPC School Server to support our campus environment. For example php, and PostgreSql are installed with the School Server,, and Moodle is included in the latest of these builds,, from what I understand. --FGrose 23:27, 30 September 2009 (UTC)

Network configuration

The School Server, XS, as received is designed and configured for 2 Ethernet adapters,

  • eth0 - connected to the wide area network (WAN) or the campus Internet connection,
  • eth1 - connected to an access point (AP) which the XOs connect to.

For robustness in unreliable power supply environments, there are scripts that reconfigure features on a frequent basis. This design has frustrated anyone wanting to deviate from the default configuration.

We will have to understand the design, carefully document our adjustments for our environment, and make preparations to restore one or more configurations once we upgrade to a new version of the server that may likely restore some of the default configurations.