Difference between revisions of "Deployment Team/Peru"

From Sugar Labs
Jump to navigation Jump to search
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Draft}}
 
 
 
== Summary ==
 
== Summary ==
  
This page is an overview of a pilot program that will happen in 2012 in Puno region of Peru. This effort is being led by Peru Local Lab. The detailed information (in Spanish) will be shared on the Peru Local Lab [http://pe.sugarlabs.org/ home page]. This page also contains technical details of implementation that might be helpful for other deployments.
+
This page is an overview of a pilot program that will happen in 2012 in Peru. This effort is being led by Peru Local Lab. The detailed information (in Spanish) is [http://pe.sugarlabs.org/go/Proyecto_Piloto_Hexoquinasa located] on the Peru Local Lab [http://pe.sugarlabs.org/ home page]. This page also contains technical details of implementation that might be helpful for other deployments.
  
 
== Layers ==
 
== Layers ==
Line 21: Line 19:
 
** no connectivity;
 
** no connectivity;
 
** only XO laptops, no wireless access points, no dedicated hardware for school servers.
 
** only XO laptops, no wireless access points, no dedicated hardware for school servers.
* town schools:
+
* town schools (CRT):
 
** computer labs, not laptop per child, model;
 
** computer labs, not laptop per child, model;
 
** skilled technical personnel;
 
** skilled technical personnel;
Line 32: Line 30:
 
*Bernie Innocenti
 
*Bernie Innocenti
 
*Chris Leonard
 
*Chris Leonard
*David Cruz
+
*Juan Camilo Lema
 +
*Koke Contreras
 
*Laura Vargas
 
*Laura Vargas
*Neyder Achahuanco
 
*Ruben Monrroy
 
 
*Sebastian Silva
 
*Sebastian Silva
  
Line 51: Line 48:
 
* Lack of technical support, only teachers;
 
* Lack of technical support, only teachers;
 
* No connectivity;
 
* No connectivity;
* Only XO laptops, no wireless access points, no dedicated hardware for school servers to server additional content;
+
* Only XO laptops, no wireless access points, no dedicated hardware for school servers to provide additional content;
 
* No translation to local languages.
 
* No translation to local languages.
  
Line 64: Line 61:
  
 
''XO students''
 
''XO students''
: Students from one-teacher village schools. They have XOs in personal usage.
+
: Students from one-teacher multi-grade schools. They have XOs in personal usage.
  
 
''XO teachers''
 
''XO teachers''
: Teachers from one-teacher village schools. They have XOs in personal usage as well. They are the only who maintain XO related workflows at schools on daily basis.
+
: Teachers from one-teacher multi-grade schools. They have XOs in personal usage as well. They are the only who maintain XO related workflows at schools on daily basis.
  
 
''Chaski''
 
''Chaski''
: A person who travels around to visit village schools.
+
: Any person who can travel from one-teacher multi-grade schools to an internet access point and back.  
  
 
''Teachers Trainer''
 
''Teachers Trainer''
Line 81: Line 78:
 
:
 
:
  
''Network coordinators''
+
''Network coordinators / Community Managers''
 +
* Activate Network
 
* Merge data
 
* Merge data
* Moderate date
+
* Moderate data
 +
* Monitor metrics
 
* Connect downstream needs and upstream implementation
 
* Connect downstream needs and upstream implementation
 
: TODO more specific
 
: TODO more specific
Line 95: Line 94:
 
Major components are:
 
Major components are:
  
* [[Deployment_Team/Peru/Puno/Sugar_Distribution|SomosAzúcar Sugar Distribution]],
+
* [[Deployment_Team/Peru/Puno/Sugar_Distribution|SomosAzúcar Sugar Distribution: Hexoquinasa]],
 
* [[Platform_Team/Sugar_Network|Sugar Network]],
 
* [[Platform_Team/Sugar_Network|Sugar Network]],
 
* [[Deployment_Team/Peru/Puno/Teachers_Server|SomosAzúcar Teacher's Server]].
 
* [[Deployment_Team/Peru/Puno/Teachers_Server|SomosAzúcar Teacher's Server]].
Line 102: Line 101:
  
 
''XO students'' have:
 
''XO students'' have:
* XO image of SomosAzúcar Sugar Distribution;
+
* XO image Hexoquinasa;
 
* [[Platform_Team/Sugar_Network|Sugar Network]] frontend;
 
* [[Platform_Team/Sugar_Network|Sugar Network]] frontend;
 
* ''Statistics'' monitor.
 
* ''Statistics'' monitor.
Line 120: Line 119:
  
 
''Lab students''
 
''Lab students''
* Trisquel image of SomosAzúcar Sugar Distribution;
+
* Trisquel image of Hexoquinasa;
  
 
''Mothership''
 
''Mothership''

Latest revision as of 00:41, 12 May 2012

Summary

This page is an overview of a pilot program that will happen in 2012 in Peru. This effort is being led by Peru Local Lab. The detailed information (in Spanish) is located on the Peru Local Lab home page. This page also contains technical details of implementation that might be helpful for other deployments.

Layers

Puno-map.png

The whole picture is split into three layers: Schools, Deployment team, Upstream. The current section briefly characterize all of them.

Schools

The are two types of schools:

  • schools, one-teacher schools in villages:
    • laptop per child model;
    • about 10-20 students of different ages;
    • lack of technical support, only teachers;
    • no connectivity;
    • only XO laptops, no wireless access points, no dedicated hardware for school servers.
  • town schools (CRT):
    • computer labs, not laptop per child, model;
    • skilled technical personnel;
    • good connectivity;
    • good hardware equipment.

Deployment team

  • Aleksey Lim
  • Bernie Innocenti
  • Chris Leonard
  • Juan Camilo Lema
  • Koke Contreras
  • Laura Vargas
  • Sebastian Silva


TODO

Upstream

The rest of Sugar community.
TODO

The problem

The problems with one-teacher schools are:

  • Lack of technical support, only teachers;
  • No connectivity;
  • Only XO laptops, no wireless access points, no dedicated hardware for school servers to provide additional content;
  • No translation to local languages.

References:

Roles

All involved people might be categorized by the following roles.

XO students

Students from one-teacher multi-grade schools. They have XOs in personal usage.

XO teachers

Teachers from one-teacher multi-grade schools. They have XOs in personal usage as well. They are the only who maintain XO related workflows at schools on daily basis.

Chaski

Any person who can travel from one-teacher multi-grade schools to an internet access point and back.

Teachers Trainer

Lab students

Lab teachers

Network coordinators / Community Managers

  • Activate Network
  • Merge data
  • Moderate data
  • Monitor metrics
  • Connect downstream needs and upstream implementation
TODO more specific

Upstream

The rest of Sugar community.
TODO concretize.

Infrastructure

Major components are:

They are spread within the Roles as:

XO students have:

  • XO image Hexoquinasa;
  • Sugar Network frontend;
  • Statistics monitor.

XO teachers's XOs operate as school servers and contain:

  • Additional storage on SD card;
  • School Sugar Network server;
  • A copy of XO updates repository;
  • (?) Jabber server;
  • (?) Journal backups;
  • (?) Anti-thief support.

Synchronization USB key

  • Sync data as a singular file that might be uploaded in any way,
  • the script to upload data,
  • Live image to boot to the hw and upload data.

Lab students

  • Trisquel image of Hexoquinasa;

Mothership

Workflows

These are kinds of workflows that Roles can take part in. The particular activity might involve several Players and several Roles.

Synchronization

A Chaski travels between a school that needs to be synchronized and a place with the connectivity.
The process is only about carrying the USB key, the rest should be done automatically.
TODO describe the process.

Training teachers

A process of teaching XO Teachers to use the system.
TODO describe the process.

Maintaining the Sugar Network

Network Coordinators
TODO describe the process.
  • Maintain XO system updates repository;

Sugar Network's workflows

The workflows that relate to Sugar Network.

References

Subpages