Difference between revisions of "Deployment Platform/1.1/Notes"

From Sugar Labs
Jump to navigation Jump to search
Line 48: Line 48:
 
* ''sugaroid''<br>was renamed to [[Sugar_Server_Kit/sugar-unit|sugar-unit]] to expose more general purpose of this project;
 
* ''sugaroid''<br>was renamed to [[Sugar_Server_Kit/sugar-unit|sugar-unit]] to expose more general purpose of this project;
 
* ''sugar-server-demoxo''<br>was removed as an Sugar Server Kit component and will be back as a supported [[Sugar_Server_Kit/Solutions/Server_on_an_XO|final solution]] in [[Sugar_Server_Kit/1.2/Todo|1.2]].
 
* ''sugar-server-demoxo''<br>was removed as an Sugar Server Kit component and will be back as a supported [[Sugar_Server_Kit/Solutions/Server_on_an_XO|final solution]] in [[Sugar_Server_Kit/1.2/Todo|1.2]].
 +
 +
See also the [[Sugar_Server_Kit#Components|full list]] of Sugar Server Kit components.
  
 
== Getting the release ==
 
== Getting the release ==

Revision as of 07:53, 1 December 2011

Summary

This is the first Sugar Server Kit release that is being positioned as ready for using in the field, thanks to the Paraguayan pilot program. This release should fulfill needs similar to that were faced in Paraguay. The next step will be proving this system in restricted environments within the Server on an XO project for SSK-1.2.

This is also the first release that is following the Sugar Server Kit releasing plan.

Design changes

Changes made from initial, 1.0, Sugar Server Kit implementation.

Unified API for sugar-server

The major way to interact with sugar-server for now, is a RESTfull API. The API inherited from the OLPC XS is preserved when it is possible, e.g., except Journal backups that were implemented differently from the begining.

sugar-client

sugar-client project is intended to be the only one on a client side to cover all possible interactions with a school server.

Clients are identified by profile UIDs on a server

In comparing with 1.0 implementation, and OLPC XS as well, sugar-server-1.1 identifies clients by UID that is unique for particular user's profile, i.e., not by XO's UUIDs. That was done to cover usecases when the same hardware is being used for several users.

Final solution

This release is entirely based on experience gotten during the work on Paraguayan pilot program, i.e., the functionality of Sugar Server Kit was improved and proven by using it in a school. As a result, the paraguayeduca-server, the final Sugar Server Kit based solution, was created.

It covers the full life cycle of using school servers in environments similar to Paraguay, i.e.:

  • Install Kit on USB stick to:
    • install new server,
    • migrate from existing installation,
    • migrate from existing OLPC XS installation;
  • Post-install school server automated tests;
  • Initial setup for the Mothership to support new school servers;
  • New client side behaviour based on sugar-client.

Supported platforms

  • Current LTS version of Ubuntu/Trisquel GNU/Linux distributions.

Fedora-14 will be added to supported platforms in 1.2 to provide Server on an XO solution.

Components

In comparing with 1.0 release, there are the following changes:

  • sugar-client
    new component to interact with a school server on a client side;
  • sugaroid
    was renamed to sugar-unit to expose more general purpose of this project;
  • sugar-server-demoxo
    was removed as an Sugar Server Kit component and will be back as a supported final solution in 1.2.

See also the full list of Sugar Server Kit components.

Getting the release

Sources in tarballs can be found on package.sugarlabs.org and in master-1.1 branches in repositories on git.sugarlabs.org.

Binaries for supported distributions can be found on download.sugarlabs.org.

Looking forward

The next minor, 1.2, release should contain the following major features:

See the 1.2 TODO list for more details.

Credits

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Deployment_Platform/1.1/Notes&oldid=71988"