Changes

Deployment Platform/Sneakernet (view source)

Revision as of 02:07, 25 July 2012

1,560 bytes removed , 02:07, 25 July 2012

Line 2: Line 2:

This page is intended to describe the process of offline synchronization between Sugar Network servers. The synchronization process means making data changes, happened on servers, common for all of them.

−

~~== Objects ==~~

−

~~What kind of objects involved to the process:~~

−

* '''Master server''' Main Sugar Network server accessible via the Internet. Each Master server has public API url. This tutorial is using http://api-testing.network.sugarlabs.org to refer to testing Sugar Network Master launched on Sugar Labs server.

−

* '''Node servers''' Local Sugar Network servers that are intended to be distributed versions of the Master. This tutorial assumes that Nodes don't have direct connection to the Master, and the only one way to synchronize data is the [[wikipedia:Sneakernet|Sneakernet]].

−

* '''Database media''' Node servers might store database on removable devices (makes sense if Nodes are XO laptops), in that case, such devices should have a magic file, named {{Code|.sugar-network}}, in the root directory on removable device. Having this magic file will let Node's software auto detect recently plugged removable device as a Database media to start behaving correspondingly.

−

* '''Synchronization media''' Removable media device, e.g., USB stick or SD card that will be used to transfer Packets between servers. Synchronization media should have a magic file, named {{Code|.sugar-network-sync}}, in the root directory. Having this file will let Node's software start synchronization process automatically after plugging media.

−

* '''Synchronization packets''' Regular files that contain synchronization data placed to Synchronization media. Packet files are [[wikipedia:Tar_(file_format)|tarballs]] with {{Code|.packet}} file name suffix.

== Recipes ==

Alsroot

Bots, Bureaucrats, Check users, Administrators, Widget editors

5,705

edits