Cerebro talk

From OLPC
Revision as of 16:21, 16 June 2008 by Kimquirk (talk | contribs) (New page: Cerebro: Can provide presence and file transfer Unlike TCP/IP, laptops dont' discard packets it sees even if it doesn't think they are targeted to Teacher can send a file to all the lapto...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Cerebro: Can provide presence and file transfer Unlike TCP/IP, laptops dont' discard packets it sees even if it doesn't think they are targeted to Teacher can send a file to all the laptops Or, the individual laptops can ask for the same file, they may already have heard most of the file and won't need to load it all. RAM is the cache; not using the flash

Presence info that can include some vague info on distance Wireless network to synchronize the time

First tests Poly has done included a 27 laptop file transfer; the next test was a 65 node chat. Poly created a collaboration layer over Cerebro; be able to share an activity;

Next choice is to implement connection manager into telepathy; and/or rewrite activities to make the new cerebro work

Right now we are thinking that we will have two collaboration stacks for the short term. Would like an abstraction layer that makes it unimportant to the activity developer which stack is being used.

Main goal for MIT campus goal Purpose: neighborhood scenario, fewer total laptops, but they hop the network.

User interface to communicate between XO and regular PC (linux based)

Bunch of XOs as the regular network.

Total number of laptops: Need USB-Eth cable Build 708 How to report bugs? Both Joe and Poly will be copied on all bugs to determine if they are cerebro

What are the tests? They will have both AP connectivity and cerebro connectivity Sharing a large file Requesting a large file

Scalability testing - # of hops First problem is going to be getting all the laptops to see each other through building materials and across buildings.

First need to prove that laptops can see each other laptops at the wireless firmware level: iwlist

  • Establish non-mobile Laptop
  • Second level of testing involves statistics collection
** # of retransmissions
** # of files/bytes
  • Third level of testing will be adding extra mobile laptops

Utility to track laptops if they change IP Webpage utility to track laptops