User:Holt/XS Community Edition/0.2/Test Plan: Difference between revisions

From OLPC
Jump to navigation Jump to search
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==XSCE Services Testing Checklist==
=Test plan=
Using only the instructions in the [[User:Holt/XS_Community_Edition/0.2/Hacking | Hacking page]] and a fresh Fedora 17 install.


Using only the instructions in the [[User:Holt/XS_Community_Edition/0.2/Hacking#Installing | Hacking page]] and a fresh Fedora 17 install.
==XSCE Testing Checklist==


Then repeat all below on XO-1.75 and "big iron" generic/commodity x86.
===Registration===

===Registration (idmgr)===
Register the XSCE (yes, you're actually registering it to itself). You should get a message informing you that registration was successful. Registration also creates a directory named the XO's serial number in /library/users.
Register the XSCE (yes, you're actually registering it to itself). You should get a message informing you that registration was successful. Registration also creates a directory named the XO's serial number in /library/users.


===Dynamic Host Configuration Protocol (dhcpd)===
===DHCP===
Connect an XO to the XSCE's AP. The XO will get an IP in the 172.18.x.x range.
Connect an XO to the XSCE's AP. The XO will get an IP in the 172.18.x.x range.


===Ejabberd===
===XMPP Server (ejabberd)===
Now that a client XO is connected to the XSCE, register it. If you get a message that registration failed, go to the Sugar Control Panel and in Network, clear out the collaboration server field. Upon successful registration, both XOs will appear in Network Neighborhood. To verify that ejabberd is managing collaboration and not the LAN, issue this in a root terminal: ejabberdctl connected-users.
Now that a client XO is connected to the XSCE, register it. If you get a message that registration failed, go to the Sugar Control Panel and in Network, clear out the collaboration server field. Upon successful registration, both XOs will appear in Network Neighborhood. To verify that ejabberd is managing collaboration and not the LAN, issue this in a root terminal:
ejabberdctl connected-users.


===Squid Caching and Internet Access===
===Proxy Caching and Internet Access (squid)===
Check the initial size of the squid cache directory: du -sh /library/cache. From the client XO's Browse Activity, surf the internet. Check the cache directory size again and it should be larger.
Check the initial size of the squid cache directory: du -sh /library/cache. From the client XO's Browse Activity, surf the internet. Check the cache directory size again and it should be larger.


===Apache===
===Apache Web Server (httpd)===
Go to http://schoolserver and http://schoolserver.local. Both should resolve to the Apache test page.
Go to http://schoolserver and http://schoolserver.local. Both should resolve to the Apache test page.


===Activity Server===
===Activity Server (uses httpd)===
If http://schoolserver/upload_activity.php resolves, the Activity Server is working.
If http://schoolserver/upload_activity.php resolves, the Activity Server is working.

To upload an Activity to the school server, use a browser to navigate to http://schoolserver.local/upload_activity.php.
Click on "Choose File", and use the file chooser to indicate which Activity you would like to upload.


===External SD Card for /library===
===External SD Card for /library===
Mount should report /dev/mmcblk0p1 on /library
Mount should report /dev/mmcblk0p1 on /library

This isn't necessary for testing, but is fun to poke around in:


===Ejabberd Web Interface===
===Ejabberd Web Interface===
Register the admin user: register admin schoolserver.local <password>
In a browser, go to http://schoolserver.local:5280/admin. The username is admin@schoolserver.local and the password is whatever you set it in the above command.


This isn't necessary for testing, but is fun to poke around in:
Repeat for both XO-1.75 and commodity x86.


Register the admin user: <code>ejabberdctl register admin schoolserver.local <password></code>
==Hacker side==
<li>Install XS from testing repo


In a browser, go to http://schoolserver.local:5280/admin
==Admin side==
<li>Install XS from stable repo


The username is admin@schoolserver.local and the password is whatever you set above.
==Services Checks==
===Dynamic Host Configuration Protocol (dhcpd)===


===Internet Domain Name Server (named)===
===Internet Domain Name Server (named)===

===Network Address Translation/NAT (iptables)===
===Network Address Translation/NAT (iptables)===
===Virtual Private Network (openvpn) [FOR EXPERIMENTATION]===

===OLPC-update (rsync) [NOT YET SUPPORTED]===
===XMPP server (ejabberd)===

===IDMGR===

===Web server (apache)===

===Proxy server and web cache (squid)===

===OLPC-update (rsync) [NOT YET]===

===Activity update (activity updater)===
To upload an Activity to the school server, use a browser to navigate to http://schoolserver.local/upload_activity.php.
<br>
Click on "Choose File", and use the file chooser to indicate which Activity you would like to upload.

===Virtual Private Network (open vpn)===

Latest revision as of 00:27, 22 February 2013

XSCE Services Testing Checklist

Using only the instructions in the Hacking page and a fresh Fedora 17 install.

Then repeat all below on XO-1.75 and "big iron" generic/commodity x86.

Registration (idmgr)

Register the XSCE (yes, you're actually registering it to itself). You should get a message informing you that registration was successful. Registration also creates a directory named the XO's serial number in /library/users.

Dynamic Host Configuration Protocol (dhcpd)

Connect an XO to the XSCE's AP. The XO will get an IP in the 172.18.x.x range.

XMPP Server (ejabberd)

Now that a client XO is connected to the XSCE, register it. If you get a message that registration failed, go to the Sugar Control Panel and in Network, clear out the collaboration server field. Upon successful registration, both XOs will appear in Network Neighborhood. To verify that ejabberd is managing collaboration and not the LAN, issue this in a root terminal:

ejabberdctl connected-users.

Proxy Caching and Internet Access (squid)

Check the initial size of the squid cache directory: du -sh /library/cache. From the client XO's Browse Activity, surf the internet. Check the cache directory size again and it should be larger.

Apache Web Server (httpd)

Go to http://schoolserver and http://schoolserver.local. Both should resolve to the Apache test page.

Activity Server (uses httpd)

If http://schoolserver/upload_activity.php resolves, the Activity Server is working.

To upload an Activity to the school server, use a browser to navigate to http://schoolserver.local/upload_activity.php. Click on "Choose File", and use the file chooser to indicate which Activity you would like to upload.

External SD Card for /library

Mount should report /dev/mmcblk0p1 on /library

Ejabberd Web Interface

This isn't necessary for testing, but is fun to poke around in:

Register the admin user: ejabberdctl register admin schoolserver.local <password>

In a browser, go to http://schoolserver.local:5280/admin

The username is admin@schoolserver.local and the password is whatever you set above.

Internet Domain Name Server (named)

Network Address Translation/NAT (iptables)

Virtual Private Network (openvpn) [FOR EXPERIMENTATION]

OLPC-update (rsync) [NOT YET SUPPORTED]