Difference between revisions of "Deployment Platform/Sneakernet"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
* '''Master server'''<br>Main Sugar Network server accessible via the Internet. | * '''Master server'''<br>Main Sugar Network server accessible via the Internet. | ||
| + | |||
* '''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 a [[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 a [[wikipedia:Sneakernet|Sneakernet]]. | ||
| − | * '''Synchronization Media'''<br>Arbitrary media device, e.g., USB stick or SD card that will be used to transfer Packets between servers. | + | |
| − | * '''Synchronization Packets'''<br>Regular files that contain synchronization data placed to Media. | + | * '''Database'''<br>Storage space where servers keep Sugar Network data. It might be removable device, e.g., SD card on a XO, or regular directory in the files system on a standalone school server. In all cases, the final directory name should be {{Code|sugar-network}}. |
| + | |||
| + | * '''Synchronization Media'''<br>Arbitrary removable media device, e.g., USB stick or SD card that will be used to transfer Packets between servers. In particular cases, Media might be a directory in the files system. In all cases, the final directory name should be {{Code|sugar-network-sync}}. | ||
| + | |||
| + | * '''Synchronization Packets'''<br>Regular files that contain synchronization data placed to Media. If synchronization happens using regular tools, Packet files will be named as {{Code|<server's-guid>-<server's-seqno>.packet}}. These files are [[wikipedia:Tar_(file_format)|tarballs]]. | ||
== Workflows == | == Workflows == | ||
Revision as of 11:17, 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.
- 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 a Sneakernet.
- Database
Storage space where servers keep Sugar Network data. It might be removable device, e.g., SD card on a XO, or regular directory in the files system on a standalone school server. In all cases, the final directory name should besugar-network.
- Synchronization Media
Arbitrary removable media device, e.g., USB stick or SD card that will be used to transfer Packets between servers. In particular cases, Media might be a directory in the files system. In all cases, the final directory name should besugar-network-sync.
- Synchronization Packets
Regular files that contain synchronization data placed to Media. If synchronization happens using regular tools, Packet files will be named as<server's-guid>-<server's-seqno>.packet. These files are tarballs.
Workflows
A list of scenarios to follow in the field.