Tests/Start up and Activation

From OLPC
< Tests
Revision as of 11:47, 25 June 2007 by Jfuhrer (talk | contribs)
Jump to: navigation, search

Activation Security scenario 1: Basic Activation

Uruguay has been planning for their delivery for months and has identified two country admins and a number of trusted deployment admins to activate laptops at the schools. These deployment admins are dispatched to the location where skids are being disassembled for shipment to individual schools, so they can collect serial numbers for the schools that they are responsible for.

Justification: Self

Actions:

  1. Deployment admin provides the list of valid serial numbers to the country admin.
  2. Setup school server at the local schools.
  3. The country admin uploads the deployment admin's list serial numbers to the olpc global server and receives a set of activation codes. He creates a usb stick with these activation codes and sends it to the deployment admin.
  4. At the school, the deployment admin connects the usb stick with the activation codes into the school server.
  5. Open an XO that was on the original list of serial numbers.
  6. Open an XO that was NOT on the original list of serial numbers;
  7. The trusted Admin inserts a memory stick with the activation codes into the first XO.

Verify:

  • That during boot the XO that was on the original list of serial numbers will find the server via the mesh (not via wireless) and activate. It should be usable right away. If a 'grace' period of time was allowed (1 week without activiation, for instance), then the laptop WILL continue to work after that week.
  • That the XO that was not on the original list of serial numbers should not come up working, or it will stop working after the activation grace period.
  • That, at the second school, there is no school server set up yet at this point.
  • That, once the memory stick is inserted into the first XO, the XO should come up working and continue to work past the activation grace period.
  • That an XO that was not on the original list should not activate even with the USB stick directly connected to it.


Activation Security scenario 2: Disable stolen XO

Maya's laptop was stolen from her home. It had been issued to her and the local school server had provided the initial activation when she got the laptop.

Justification: Self

Actions:

  1. Activate an XO with a valid activation key through the server
  2. The laptop is reported stolen to the school adminstrator. The admin uses the server UI to report the full name (or the serial number) of the stolen laptop.
  3. The OLPC global server adds this laptop to the 'Deactivate' list.
  4. Connect Maya's laptop to the internet.
  5. Power the laptop off/on.

Verify:

  • That if Maya's laptop is used without access to the internet, it should continue to work (until a lease expiration)
  • That, when Maya's laptop is connected to the internet, it becomes de-activated.
  • That Maya's laptop no longer boots up after being turned off.

Activation Security scenario 3: Child moves to new School

Pari has a laptop she has been using for months. She moves to a new town or new school which also has an OLPC school server.

Justification: Self

Actions:

  1. Get Pari's laptop is up and running; documents, browsing, books.
  2. Move Pari's laptop to a new school server.

Verify:

  • That Pari's laptop is seen by the new server.
  • That Pari's teacher can go into the school server interface and designate this new computer as having 'moved' to this school zone.
  • That Pari's laptop continues to work.
  • That, if the school server is not told to allow this new laptop, then Pari's original school lease would expire and the laptop would deactivate.

Activation Security scenario 4: Server is replaced

The activation and lease information that is held on the local school server may be lost if the server is replaced. Need to ensure that any information the server keeps locally can be overruled by OLPC's global server (?).


Activation Security scenario 5: Lease Mechanism

Tom is a student who received a laptop from a school in Sau Paulo. After a month, his family moves to a town without laptops or internet connectivity. When the lease runs out (the minimum amount of time without connecting with a school server, the laptop should fail to boot.

Justification: Self

Actions:

  1. Successfully activate Tom's XO with a school server.
  2. Set the lease period to a short time for this test (a few days or hours, if possible).
  3. After the lease period, access the internet.
  4. Then, reboot Tom's XO.

Verify:

  • That Tom's XO has no access to the internet or a school server for > lease period.
  • That the next time Tom's XO does access the internet, this machine should have been listed in the 'Deactivate' list, and get a deactivate message. (Does it have a local lease mechanism so it will stop working after some period of time, or only after the period of time + next connect to internet?)
  • That, when you reboot Tom's XO, it no longer boots.


Start up scenario 1: Server support

Jose is a 6 year-old student at a school in Brazil is being issued his XO laptop today. The school has spent weeks preparing for this day. The school server is set up and has internet connectivity. All the laptops have been activated by the school server, which contains books and software specific for Jose's grade level. The teacher has a specific activity she asks all the children to work on.

Justification: Self

Actions:

  1. Setup school server with a school text book for content and appropriate activation keys for 5 XOs.
  2. Activate all 5 XOs
  3. Designate one of the XOs as the teacher, boot it and select fullname(?), nickname and X) color.
  4. On teacher's XO, download a book from the school server (need details on how to do this).
  5. On teacher's XO, open the book and share it (need details)
  6. For the other 4 XOs, turn them on, wait for boot up, and select fullname(?), nickname, and XO color. Designate one of the XOs as Jose. [Should two student nicknames the same?]
  7. From Jose's XO, from the mesh view, click on the teacher's shared book. Then, click on the teacher's shared book from the other XOs.


Verify:

  • From Jose's XO ensure that the mesh shows all other XOs
  • That all XOs can access and read the teacher's shared book.
  • From the school server, ensure that all 5 XOs have been registered.
  • That, upon appropriate event (turning off and back on again, or waiting a period of time), the school server should force an archive or back up of the user data for all 5 machines. (is this initiated by the server or XO?)


Start up scenario 2: No server support

Maria is a 10 year-old student in a school being issued XOs. This school just received their server but not set up or has no internet connectivity. Activation will occur via USB stick. The teacher is not prepared with activities or curriculum, but will allow the children time to explore the laptops on their own.

Justification:

Actions:

  1. No school server, no Access Point (to start)
  2. Use a USB to activate 5 XOs (ensure that these are 'out of the box' XOs)
  3. For all 5 XOs, turn them on, wait for boot up, and select fullname(?), nickname, and XO color. Designate one of the XOs as Maria.
  4. From Maria's XO, go to the mesh and designate 2 other XOs as 'friends'
  5. From Maria's XO, start a chat session with one of the friends
  6. Add an off-the-shelf wireless router (such as Linksys) with an uplink to the internet. No WEP key.

Verify:

  • That the mesh shows all other XOs from each student XO.
  • That the friends show up in the group mesh view, and all XOs continue to show up in neighborhood mesh view.
  • Ensure that Maria's XO can connect to this AP, and can now browse the internet

Start up scenario 3: Server added later

This is a continuation of scenario 2, where the Server is introduced into the school after the students have activated their laptops and started creating documents.

Justification: Self

Setup:

  1. Activate five XOs and create shared documents, video and etoys programs.
  2. Power on the school server.

Tests:

  • That the server finds all the XOs and registers them.
  • That the XOs are able to access the internet through the school server.
  • That the school server provides a back up of the student's files.


Start up scenario 4: Server start up

The server hardware and cables have arrived early at a large school in Uruguay. The local administrator takes the hardware out of the box and would like to set up the server and download the curriculum books and software that have been created ahead of time. There will be 3 radios (all active antennas? or 2 AAs and one embedded radio?)

Justification:

Actions:

  1. Plug in the school server, keyboard, mouse, display, connect active antennas, connect uplink.
  2. Start Server UI for choosing content (?)
  3. Start an XO.

Verify:

  • That uplink connection is available.
  • That server boots up and provides diagnostic info: Connectivity to uplink, number of live radio channels (antennas), IP Address for uplink, number of wireless hosts... (what else do we want to show at start up?)
  • That the School server sees the XO and can provide content to it (automatically?)
  • That the school server provides the appropriate backup and reporting