XS Blueprints:Lease and update server

From OLPC
Revision as of 12:54, 14 November 2008 by Gregorio (talk | contribs) (Scenarios)
Jump to: navigation, search


Lease and activation services are a key role of the XS. They are key enablers at the school and in the warehouse where the XOs are prepared for deployment.

Scenarios

  • Tama is a field technician, he's visiting a rural school without internet. He has a new OS build to install on the existing laptops and 20 new laptops to hand out with serial numbers that the existing XS doesn't have leases for.
  • Lee is a field technician. He is deploying an XS to a school that did not have one earlier - so the XOs had very long leases, which now need to be shortened.
  • Teacher Catalina travelled to town and got leases and an OS image on a USB stick. The XS at his school is slow -- she wonders whether anything is happening with the USB stick.
  • Jocinta is a NOC sysadmin and wants to get all the XSs out there with the new leases for a XO shipment that is being handed out, new blacklist (a few machines have been misplaced) and updated XO OS images. She has to prepare an update for the internet-connected XSs, and a usb img for the non-connected ones.
  • Ludmilla and Jim are technicians at the warehouse in Wellingtonia-- they have 5K XOs to activate and update. They want to use a temporary machine - perhaps one of the XOs even - as lease and update server.
  • In Zoolandia it is the first day of school after summer holidays -- kids are returning to school and those who haven't visited school in the holidays have their XOs locked. The wireless signal in the Zoolandia schools is unencrypted.
  • First day at school in Oz is a bit more complicated -- wireless network signal is WPA encrypted or perhaps the wireless antenna is broken, flaky, saturated. Teacher wants to prepare an "unlocker" usb stick to pass around.
  • See also the requirements definition [Feature_roadmap#Activation_lease_security]

Implementation Notes

After talking with Wad, we broke the activation/lease server scenario down to

Warehouse scenario

  • Initial activation
    • FW client - by Mitch - probably looks for a pre-set ESSID and dns name
    • Known to work in Mitch's lab
  • Wireless-based reflash
    • For perf reasons you really want to do it via multicast with a bumped multicast rate. We can
      • document how to bump the MC rate on APs
      • document how to bump the MC rate on AAs (script it if we have a "turn into reflash server" script)
    • Needs XOs to be booted off a USB stick with a forth script to trigger the "reflash from network"
    • Worked -- at least once -- via multicast

In school

  • Lease renewal, blacklists
  • olpc-update (done!)


XO side

...

XS side

...

Test plans and user walkthrough

...

TODOs and future work

...