Difference between revisions of "Deployment Platform/Sneakernet"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
* '''Master server'''<br>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. | * '''Master server'''<br>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'''<br>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]]. | + | * '''Node servers'''<br>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]]. If regular Sugar box will be a Node, enable ''Behave as a Sugar Network server..'' check-box (will require restarting Sugar Shell) in ''Sweets Distribution'' Control Panel section. |
* '''Database media'''<br>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. | * '''Database media'''<br>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. | ||
| Line 16: | Line 16: | ||
* '''Synchronization packets'''<br>Regular files that contain synchronization data placed to Synchronization media. Packet files are [[wikipedia:Tar_(file_format)|tarballs]] with {{Code|.packet}} file name suffix. | * '''Synchronization packets'''<br>Regular files that contain synchronization data placed to Synchronization media. Packet files are [[wikipedia:Tar_(file_format)|tarballs]] with {{Code|.packet}} file name suffix. | ||
| + | |||
| + | * '''Clients'''<br>Sugar boxes in Internet-less environment when only Node server is available from the local network, e.g., Ad-Hoc wireless. All Clients should enable ''Auto discover server in local network'' radio-box in ''Sweets Distribution'' Control Panel section. | ||
== Workflows == | == Workflows == | ||
Revision as of 16:04, 15 July 2012
Summary
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 Sneakernet. If regular Sugar box will be a Node, enable Behave as a Sugar Network server.. check-box (will require restarting Sugar Shell) in Sweets Distribution Control Panel section.
- 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.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.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 tarballs with.packetfile name suffix.
- Clients
Sugar boxes in Internet-less environment when only Node server is available from the local network, e.g., Ad-Hoc wireless. All Clients should enable Auto discover server in local network radio-box in Sweets Distribution Control Panel section.
Workflows
A list of scenarios to follow in the field.