Changes

no edit summary
Line 1: Line 1: −
== Distribution package ==
+
== Scenarios ==
 +
 
 +
The following list describes common deployment scenarios where [[Platform_Team/Harmonic_Distribution|Harmonic Distribution]] might be useful. The final model might be an intermediate variant of them.
 +
 
 +
=== Online peers ===
 +
 
 +
There is a [[#Dedicated_online_school_server|master server]] located in the Internet in highly accessible place for any maintaining work. The main task is supporting users that are connected to the server all time.
 +
 
 +
Possible options for deployment packages are:
 +
 
 +
* Attach proper [[#Repository|repository]] and install client sides packages. Client packages need to be preconfigured to connect to the Internet located server.
 +
 
 +
* The same but with special [[#XO image|XO image]] that is ready to work right after flashing a XO.
 +
 
 +
=== Dedicated online school server ===
 +
 
 +
A machine that has Internet connectivity and is intended to serve clients, e.g.,:
 +
 
 +
* [[Platform_Team/Harmonic_Distribution/Software#Software_Map|base software]] updates,
 +
* [[Sugar Network]] content,
 +
* collect usage statistics,
 +
* provide OLPC's XO anti-thief support,
 +
* backup functionality for client.
 +
 
 +
Server might be master (the main server) or node (replication of master). For nodes, the synchronization process with master will happen on regular basis using current Internet connection.
 +
 
 +
Possible options for deployment packages are:
 +
 
 +
* Attach proper [[#Repository|repository]] and install preconfigured server sides packages.
 +
 
 +
=== Dedicated offline school server ===
 +
 
 +
The same server as [[#Dedicated online school server|online]] one with a difference that it doesn't have Internet connection and needs to be synchronized using [[#Offline synchronization|sneakernet]].
 +
 
 +
Possible options for deployment packages are:
 +
 
 +
* Attach proper [[#Repository|repository]] and install preconfigured server sides packages.
 +
 
 +
=== Peer as a school server ===
 +
 
 +
The case when one of peers can play a role of either [[#Dedicated_online_school_server|online]] or [[#Dedicated_offline_school_server|offline]] school server.
 +
 
 +
Possible options for deployment packages are:
 +
 
 +
* Attach proper [[#Repository|repository]] and install client and server sides packages. Client packages need to be preconfigured to connect to the same peer as a server. Server packages need to be preconfigured for serve clients around using existing network interface, i.e., ethernet or wireless ad-hoc.
 +
 
 +
* The same but with special [[#XO image|XO image]] that is ready to work right after flashing a XO.
 +
 
 +
== Deployment packages ==
 +
 
 +
=== Repository ===
 +
 
 +
It might be either on of [[Sweets Distribution]] repositories or a repository derived from [[Sweets Distribution]] one and preconfigured.
 +
 
 +
=== XO image ===
 +
 
 +
Regular XO image created with including packages from proper [[#Repository|repository]].
 +
 
 +
== Synchronization ==
 +
 
 +
Only server need to be synchronized.
 +
 
 +
=== Online synchronization ===
 +
 
 +
=== Offline synchronization ===
 +
 
 +
The process is based on [[Wiki:Sneakernet|sneakernet]].
   −
* XO image (translation, stats);
  −
* Initial SN content;
  −
* Sugar Network SD card;
  −
* USB key;
  −
* Sugar Network Manuals for students, teachers, supporters;
  −
* Master server.
      
<!--
 
<!--