Sugar Labs

School Server/RIT

< School Server
Revision as of 11:49, 22 October 2009 by Rnolette (talk | contribs) (→‎Project Ideas)

For RIT Honors Seminar project.

School Server Fall 2009 Seminar Project

Purpose

  1. Provide a school server test and development environment for the Honors Seminar participants
  2. Develop School Server systems administration skills
    1. Create an ebook reader server/client system
      • Status: currently under way
    2. Backup registered XOs or Sugar Sticks
      • Status: not started
    3. Host Moodle content developed in class
      • Status: Moodle is installed but not fully configured
  3. Test and Debug OLPC - Sugar Labs School Server software
    1. currently running (insert image name)
      • Status: upgraded to latest Server image
  4. Develop a School Server SysAdmin training curriculum for volunteers who want to support an OLPC or Sugar deployment
    1. Basic documentation and support is being compiled
      • Status: not complete

Resources

schoolserver.rit.edu

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

Project Ideas

  • Fix Ejabber
    • Status: Ejabber is running and working. XO's can communicate
      • To use Ejabber point XO server to schoolserver.rit.edu
  • Configure Moodle to our needs
    • Status: We currently do not have a project that needs moodle
  • Create an Activity(Application) for RIT XOs so students can easily access Moodle
    • Status: not started
  • Moodle xo python api
    • Status: not started
  • XO Backup/Restore
    • Status: not started
  • XO Security [1]
    • Status: not started
  • Deployment "whitebook"
    • Status: not started
  • Provide a service that allows teachers/volunteers (who don't speak English) in actual deployments to communicate via email with technical support volunteers by using the translating service Pootle. Incoming and outgoing "tagged" emails would be translated in and out of the server on arrival / departure of the XS.
    • Status: not started
  • Library /Book Reader. Thousands of books stored on the XS which children are able to pull over the network either as whole book or bit by bit as they read them on their XO's.
    • Status: currently under development
    • Additionally, they can "check out" books and bring them home on their laptops to read at home, or while not connected to the XS.
      • Status: currently under development
    • This may prove to be more economical than the proposal of distributing text via SDcards as it would allow for a wider range of content per available Gigabyte. One 40 gig hard disk library would hold 10 times as much content as ten, 4-GB SDcards replicated with identical content.
      • Status: currently under development
    • Run said books through Pootle, so children have access to books not in their native tongue.
      • Status: currently under development
    • Essentially, a backend to the read activity.
      • Status: currently under development
  • In class quizzing. Teachers ask questions, students respond using their XO, quiz results stored on XS. (Think the I>clicker) I believe similar concepts were proposed by Alex Jones
      • Status: not started
    • Possibility of parsing of information, possible graphical heuristics.
      • Status: not started

Reading Library

Some resources:

Proposed Design Goals

  1. Hold copies of ebooks for learners with no Internet access
  2. Compatible with existing Sugar ebook readers
  3. Teacher/administrator interface for loading books from a variety of Internet book archives and portable USB or CD/DVD storage media.

In the end, we want to have instructions and some supporting scripts to modify the standard OLPC School Server to support a reading library and our campus environment as independent features.

File Distribution System

An alternative to extending e-book readers - a file distribution system for the server and a client for the XO.

See the Project Page.

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.

System Configuration

Collaboration Server

  • This bug report, http://dev.laptop.org/ticket/9242, covers the missing collaborator icons in the Neighborhood view (after first connection and before reboot or reconnection to the access point)
  • /etc/idmgr.conf edited line BIND_DOMAIN=172.18.0.1 to BIND_DOMAIN=129.21.47.159 in order to try to enable the registration service. Ran service idmgr restart.
    But, on trying to register my XO, it stalls for a minute or two and then reports that it failed to connect to the schoolserver (it was connected to the ejabberd service). --FGrose 00:35, 17 October 2009 (UTC)

Schedule/Milestones

Necessary Tasks

Completed Tasks (Weeks 1-6):

  • Week 1:
  • Week 2:
  • Week 3:
  • Week 4:
  • Week 5:
  • Week 6:

Upcoming Tasks (Weeks 7-11)

  • Week 8:
  • Week 9:
  • Week 10:
  • Week 11:

For Future Development

Subpages

Retrieved from "https://wiki.sugarlabs.org/index.php?title=School_Server/RIT&oldid=39451"