Nepal:School Server Specification

XS Server Specification for Nepal Deployment

The School Server is still under development and it is unlikely that all of the planned features will be ready by Nepal's OLPC pilot, to start in early April 2008. This below specification represents what we hope to implement given the functionality currently stable in the school server.

School server specifications:

The School Server Hardware Specification currently is out-of-date

Here is what we intend to use in Nepal for the school server hardware

Server:

• Intel or AMD at least 2 g, at least 300gb hard rive, USB ports, DVD or CD ROM drive.
• OS: Fedora Core 7
• XS Server build: OLPC_XS_150.iso (This is the latest image so far.)

Network Modules:

1. Domain Name Service (DNS)
2. Dynamic Host Configuration Protocol (DHCP) (the ip range should not overlap if there is more than one XS.)
3. Mesh Network specification. (How many mesh ports? How many XO's are designated for each mesh?)
4. Active Antennas (One for each mesh)
5. Internet connection needs a router (wireless can add access for normal laptops), and is provided through Wifi or VSAT.
6. Network Cables (cat5, cat6 with RJ45 connectors, and 5m USB cable for active antenna (the antenna comes with the cable attached).
7. Power adapters. ( A detailed specification needs to written on power solution for the XS, especially in a school environment, and the classroom environment, (district level?)--get help from Joshua?)

Core Software:

OS and base image:XS server build OLPC_XS_150.iso on Fedora 7

1. Apache
2. DNS
3. DHCP
4. Moodle 1.8.4
5. PHP
6. MySQL
7. HTTP Cache – squid?
8. Content Filtering - http://dansguardian.org/

Requirements for core software

1 Apache Only hosts moodle or other web pages? What is the domain name?

2 DNS Local with forwarders set to resolve any unknown ip/domain name.

3 DHCP Used only to assign IPs to Xos and enable routing to XS, library server and internet. [the ip range should not overlap if there is more than one XS.]. See also single sign on work around below.

4 Moodle 1.8.4 Moodle main class page Includes learning objectives for next six months. Includes links to each activity and lesson plan main page.

Moodle home page for each activity. • Each lesson plan has its own home page in moodle.

• Teacher places days activity in easy to access location so that all students can launch “lesson plan” home page. Preferred, lesson home page in moodle visible, from main actvity panel at bottom of screen. Acceptable that Activity launch page shows up on browse activity but must be easy to launch (aka no typing in URLs).

• Teacher can publish link to lesson plan so it shows up on all XOs in the class. • Students open lesson plan with one click - Should we update the base OLPC home page to have a link to Moodle? • Students see one version of the lesson plan home page. Teachers see different version. Preferred to have single URL for both and identity knows which client (XO) is teacher and which is student and displays appropriate page without user name/pass or other prompt. Acceptable to have teacher URL and student URL. (* how does teacher learn special URL? Type in to browser, same as student but with standard additional text? *)

• All Moodle and activity content resides on XS • Launch of actvity must use local copy if unchange. If changed should get latest copy from XS. (* never go out over WAN for updates? *)

Teacher or admin can easily post updated activities to XS

Must have search page on school server which checks for content in library. (* school specific or Nepal wide? Checks library only or library and internet or library and OLPC wiki and internet? *)

Must have a browse content link to walk through the library content by subject.

No e-mail required.

Other Moodle requirements not related to a specific course - Moodle web site top level will have a page for the whole school - Each class will have a class page - Each class and the whole school will have a "group" concept. Relevant students will be assigned to each group by XS administrator. - Each group will have a blog and a forum. - Each group will have a place where files can be shared. - Any member of the group will be able to upload files to the shared space - Teacher will have a special place to put their files

Other ideas for Moodle server:

1. Understand the use of Moodle in a (Nepali) teaching-learning process. How to use it? Is going to add a sense of burden for teachers? If so how do we integrate it to the existing philosophy of pedagogy of the teacher?
2. How to make it simple enough for students so that they feel comfortable using it?
3. Implementation?

See also Moodle write up at: http://blog.olenepal.org/index.php/archives/124

GS - I think there is another Moodle write up by Martin L., need URL

5 PHP

6 MySQL

7 HTTP Cache – squid? - Custom values for library server URLs. That is, must flush library server content last when cache runs out of space. - Has to cache any XO activities - XO needs to be able to tell if .xo already installed when clicked from a hyperlink in Moodle. If activity already downloaded to the Journal, XO doesn't download it a new.

8 Content Filtering - http://dansguardian.org/ - Blocks inappropriate sites and updates block list automaticaly on a regular basis. - Allows manual addition of blocked URLs by domain name including sub-domains. - Allow admin intervention to apply white list (AKA only those sites on the list are allowed) on the fly at any time. - Blocks access to actvities as well. Including ways to block to certain activities, like Doom --- Must have a white list and black list for activities.

9 Activities - Kids should be able to change activity (e.g. eToys) and upload changed activity for access by others. Should have way to know which activities is different from original just by looking at it (e.g. icon on screen) for easy troubleshooting by teachers.

- Need way to automatically change version of an activity once kid, or anyone else modifies it. We want kids to be able to change their activities and break them, but it must be very easy to go back to the original version.

Other XS Requirements Not Specific to a Software Module or Covering Multiple Applications :

1 - XS Backup Requirements

Must have a process to reflash XO laptops remotely.

XS must backup all of students work. There should be a simple process to re-image a students XO from XS with all student created content preserved.

No content specific to a particular student (e.g. content they created, their place in the lesson, IP address, journal histroy, XO backup) should reside outside the schools own XS, unless specifically posted by student/teacher.

XS access allowed from internet or only Nepal WAN? Only SSH port open on school server. Run port scan/ linux security tool (which one?)

XS should have clean XO image which can be copied to a USB drive. Need instructions for re-imaging XO from XS image and/or from USB drive. All re-imaging can be done from USB intially. Nice to have process to re-image XO over mesh. After clean image is loaded user specific content can be easily loaded (no login, user name?)

XS must have copies of all XO activities. Updated activities get pushed to XS and automaticaly updated on Xos on next launch. Teacher and Nepal admin can easily add actvities or updated versions of existing activities to XS

2 – Localization - A set of learning activities will be developed in Nepali. - Its desired that GUI interfaces in Moodle Nepali but that can be targeted for a future phase. Hindi script may work for the characters (to be confirmed).

3 – Single Sign On and Authentication - Authentication: Use auto-login so that students dont have to remember their login info and/or how to get to the course page. - Integrate with Moodle (see Moodle requirements above) - Allow backup and restore of user generated data (see requirements above)

One suggestion for SSO solution:

Use auto-login so that students dont have to remember their login info and/or how to get to the course page.

I am using a simple HTML to do that:

<*html><head></head><body>

<form action= "http://www.sugaroffice.ole/moodle/login/index.php" method="post">

<input type="hidden" name="username" id="username" value="olenepal" />

<input type="hidden" name="password" id="password" value="olenepal" />

<input type="submit" value="Login" />

</form> </body>

</html>
This HTML page will be added to the sugar-interface of the XO. When clicked by user: olenepal, it will take him to the group course page that he belongs to. Security is not a concern here (I think) because student wont have a personal page. It will be use more like a community forum, and all students within a group will have the same login. Separate groups will have separate login. Drawback of doing so: This HTML file has to be manually added to all the XO's.

A second idea: Use DHCP manual configuration to staticaly map IP addresses to MAC addresses. That ensures that a laptop always comes back with the same IP address. Downside is that someone has to create MAC - IP map in DHCP server and may need to add a student name to that table too. Open questions on this: Does available DHCP server support manual mapping? Does Moodle/MySQL support user identity based on IP address?

Other SSO and SSO - Moodle comments - Simplify the UI. Take out modules that are not needed for a particular group.
- For authentication use a mysql database. Account will be manually created by Moodle administrator prior to student using this feature. Teachers have the “role” of a editing teacher in Moodle. Self registration to Moodle, and into courses (for those have login) is disabled.
- The teacher-training package being developed by OLE Nepal team will not include for the first phase of training. Will be deployed a month later.
- SSO and Id manager can greatly improve the overall auth feature. We can then use the id given by the Id manager to login to moodle as well as others.

4 – XS Network Access - XS sever should have static IP address routable from the Internet.

Things that needs to be solved:

1. Get Id manager to work (Contact Ivan Krstic) for the authentication (SSO) to manage all network logins.
2. Test the range of XO-XO, and XO-XS wireless range? (Some report up to 1 Km range, James Cameron <quozl@laptop.org>, in rural Nepali village setting this might go down to 500m.)
3. Understand the school setting. We need to know where to physically place the active antennas as this might affect the range. Outside the building (see how guys in Peru did it) inside the class room, the exact location etc.
4. How do we provide internet access to the XS (or school)?
5. Test squid with school server.

Test Results:

• XO-XS connectivity through a wireless (Belkin) router works.
• DNS works.
• Apache web services works.
• Moodle works (more work on moodle).
• DHCP through the server needs testing. Need active antennas to test mesh.
• XO-XO communication works, testing needs to be done for range.

Networking School Server Related Files

See Files: /home/sulo/xs_networking_local.doc
/home/sulo/xs_networking_regional.doc
/home/sulo/doe_wireless_plan.doc

Teachers Training for the Pilot: See Files: /root/Desktop/Teacher_Training_Course_Outline_improved_Jan_08.doc
note: will extract and add to new Wiki page soon **