#1507 HIGH Trial-2: Manufacturing Tracking Server: tracking of the laptops by SN, their UUID algorithm

[Zarro Boogs per Child]

#1507: Manufacturing Tracking Server: tracking of the laptops by SN, their UUID
algorithm
-----------------------+----------------------------------------------------
  Reporter:  jg        |       Owner:  krstic  
      Type:  task      |      Status:  assigned
  Priority:  high      |   Milestone:  Trial-2 
 Component:  security  |     Version:          
Resolution:            |    Keywords:  security
  Verified:  0         |  
-----------------------+----------------------------------------------------
Changes (by elvis):

 * cc: Luna.Huang at quantatw.com, Vance.Ke at quantatw.com,
 Victor.Chao at quantatw.com (added)

Comment:

 I have discussed with Richard at QSMC and summarized as following,

 1.       SN comes from manufacturing labels and we use barcode scanner to
 input in into test system.

 UUID is generated by command “uuidgen” and upload to SF.

 2.       Production engineer create the job bills and some manufacturing
 data in into SF to cerate the primary data like the hardware argument,
 software argument, region, etc.

 Operators input SN into test system and response manufacturing data about
 this machine to SF. We have DBA to do maintenance database whatever
 routine or emergency.

 Only DBA/programmer who creates SF can have privilege to break database or
 clean those data. We have routine backup on daily and weekly by using
 database schedule system.

 3.       Operators just input SN into system and UUID is generated
 automatically for them. They don’t know UUID and can’t access it.

 4.       We have a separate server you have installed Ubuntu. It’s done.
 Tony prepared a program that submits requests to the OLPC tracking server
 as each laptop is manufactured and it works.

 SF submits requests to that server in QSMC, and then it forwards the
 requests to Cambridge. We can use the browser to track the manufacturing
 data of each laptop via connection to Cambridge.

 5.       When copying image to NAND, we use block copy with CRC (Cyclic
 Redundancy Check) error detection algorithm. Each block to write in NAND
 have a checksum by CRC algorithm and we check it correctly.

 Remark: SF means Shop floor system of Quanta

-- 
Ticket URL: <http://dev.laptop.org/ticket/1507#comment:2>
One Laptop Per Child <http://laptop.org/>