Difference between revisions of "Deployment Platform"

From Sugar Labs
Jump to navigation Jump to search
(Obsolete)
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{Obsolete}}
 
<noinclude>[[Category:Supported systems|Harmonic]]</noinclude>
 
<noinclude>[[Category:Supported systems|Harmonic]]</noinclude>
 
{{Template:Deployment Platform Cycle Linkbar}}
 
{{Template:Deployment Platform Cycle Linkbar}}
Line 4: Line 5:
 
== Summary ==
 
== Summary ==
  
A customizable platform based on Sugar Learning Environment which is intended to be a basis for downstream distributions. The targeting audience for this platform is edu distributors and deployments who might be interested in:
+
A customizable platform based on the Sugar Learning Environment which is intended to be a basis for downstream distributions. The targeting audience for this platform are educational distributors and deployments who might be interested in these features:
  
* Solid content sharing system, [[Sugar Network]];
+
* A robust content sharing system, [[Sugar Network]];
 
* Getting feedback from the field;
 
* Getting feedback from the field;
* Provide remote educational and technical support using Sugar Network's capabilities; that are especially needed in offline scenario;
+
* Providing remote educational and technical support using Sugar Network's capabilities; which are especially needed in an offline scenario;
* Support offline scenario;
+
* Supporting the offline scenario;
 
* Centralized gathering of usage statistics;
 
* Centralized gathering of usage statistics;
* Support heterogeneous deployments, i.e., not only XO laptops.
+
* Supporting heterogeneous deployments, i.e., not only XO laptops.
  
== Components ==
+
Deployment Platform consists of the following major components:
  
 
* [[Deployment_Platform/Software#Software_Map|Base software]]
 
* [[Deployment_Platform/Software#Software_Map|Base software]]
: Base software is the foundation to start exploring the rest of the system. It will be accessible from [[Deployment_Platform/Software#Sweets_Distribution|Sweets Distribution]] native packages. Repositories of packaged software will be provided for all [[Deployment_Platform/Supported_platforms|supported platforms]] and can be used as-is on top of existing operating system, e.g., [[wikipedia:GNU/Linux distribution|GNU/Linux distribution]] for regular desktops, or [http://one.laptop.org/ OLPC OS] for XO laptops.
+
: Base software is the foundation to start exploring the rest of the system. It will be accessible from [[Deployment_Platform/Software#Sweets_Distribution|Sweets Distribution]] native packages. Repositories of packaged software will be provided for all [[Sweets_Distribution/Supported_platforms|supported platforms]] and can be used as-is on top of existing operating system, e.g., [[wikipedia:GNU/Linux distribution|GNU/Linux distribution]] for regular desktops, or [http://one.laptop.org/ OLPC OS] for XO laptops.
  
 
* [[Sugar_Network|Content]]
 
* [[Sugar_Network|Content]]
 
: This class of software is based on [[Sugar Network]], with master services hosted on Sugar Labs resources.  It provides a broad variety of content, such as Sugar activities, artifacts derived from Sugar activities, books, etc., and the community social activity centered around this content. It is the common information forum to embrace all participants. Software provided on this level, in comparison to ''Base software'', will be [[Deployment_Platform/Software#Sugar_Network|supported]] out of native packages.
 
: This class of software is based on [[Sugar Network]], with master services hosted on Sugar Labs resources.  It provides a broad variety of content, such as Sugar activities, artifacts derived from Sugar activities, books, etc., and the community social activity centered around this content. It is the common information forum to embrace all participants. Software provided on this level, in comparison to ''Base software'', will be [[Deployment_Platform/Software#Sugar_Network|supported]] out of native packages.
  
* [[Deployment_Platform/Deployment|Deployment scenarios]]
+
* [[#Reference_distributions|Reference distributions]] to cover most common [[#Deployment scenarios|Deployment scenarios]]
: Deployment scenarios is a set of solutions adapting all the previous components in order to support differing Sugar deployment scenarios. For example, "Keep the [[wikipedia:Long_Term_Support|LTS]] releases for an ''Operating System'' and its ''Base software''", or "Provide tools to sort out ''Content'' to make it useful for specific deployment needs".
+
: Deployment scenarios are a set of solutions adapting all the previous components in order to support differing Sugar deployment scenarios. For example, "Keep the [[wikipedia:Long_Term_Support|LTS]] releases for an ''Operating System'' and its ''Base software''", or "Provide tools to sort out ''Content'' to make it useful for specific deployment needs".
  
== Downstream distributions ==
+
== Deployment scenarios ==
 +
 
 +
The following list describes common deployment scenarios where Deployment Platform might be useful. The final model might be an intermediate variant of them tuned by third-party distributor for local needs.
 +
 
 +
* [[Deployment_Platform/Internet|Internet server]]<br>There is a master server located on the Internet in a highly accessible place for any maintenance work. Users are always connected to the Internet and the master server.
 +
 
 +
* [[Deployment_Platform/Gateway|Gateway server]]<br>The school server has Internet connectivity and serves it into the local network where it can be used by clients. Users are always connected to their school server via the Intranet.
 +
 
 +
* [[Deployment_Platform/Sneakernet|Offline server]]<br>When the school server itself and clients it serves are in an Internet-less environment with only one way to be synchronized with the outer world, [[wikipedia:Sneakernet|sneakernet]].
 +
 
 +
== Deployment specific functionality ==
 +
 
 +
The following features were designed especially for deployment workflow.
 +
 
 +
* Common client side [[Deployment_Platform/Client_Configuration|configuration]] for all Deployment Platform components;
 +
* Deployment specific improvements of the Sugar Shell:
 +
** Shell [[Deployment_Platform/Shell_Plugins|plugins]],
 +
** [[Deployment_Platform/Blacklist_Shell_Components|blacklist]] Shell components;
 +
* Collecting [[Deployment_Platform/Usage_Statistics|usage statistics]] of Sugar users;
 +
* Lightweight [[Deployment_Platform/Package_Management_on_XO|package management]] to process system updates and extra dependencies installation on XO laptops.
 +
 
 +
== Reference implementations ==
 +
 
 +
These are reference implementations of distributions based on Deployment Platform. These implementations might be used as a template for downstream solutions.
 +
 
 +
* [[Deployment_Platform/XO_reference_distribution|XO distribution]]<br>Reference desktop distribution for OLPC XO laptops.
 +
 
 +
* [[Deployment_Platform/Ubuntu_desktop_reference_distribution|Ubuntu desktop distribution]]<br>Reference desktop distribution for workstations on Ubuntu or its derivates.
 +
 
 +
* [[Deployment_Platform/Debian_server_reference_distribution|Debian server distribution]]<br>Reference school server distribution for servers on Debian, Ubuntu or its derivates.
 +
 
 +
== Downstream solutions ==
  
 
* The [http://pe.sugarlabs.org/go/Proyecto_Piloto_Hexoquinasa Hexoquinasa] project created by Peruvian community to support Sugar Learning Platform deployments.
 
* The [http://pe.sugarlabs.org/go/Proyecto_Piloto_Hexoquinasa Hexoquinasa] project created by Peruvian community to support Sugar Learning Platform deployments.
Line 31: Line 63:
  
 
* Announcement [http://thread.gmane.org/gmane.linux.laptop.olpc.sugar/34422 email thread].
 
* Announcement [http://thread.gmane.org/gmane.linux.laptop.olpc.sugar/34422 email thread].
* '''[[Sugar Network/Tutorial|Sugar Network Tutorial]]''' - A series of screen-shots of ''Sugar Network Factory 0.94''
 
  
 
== Getting involved ==
 
== Getting involved ==
  
 
{{:Deployment_Platform/Feedback}}
 
{{:Deployment_Platform/Feedback}}
 
=== Activity Testing ===
 
 
:[[Sugar Network Activities]] only half completed --[[User:Satellit|Satellit]] 10:16, 19 May 2012 (EDT)
 
:[[Sugar Network Activities Alphabetic]]-not updated for latest SN--[[User:Satellit|Satellit]] 09:44, 19 May 2012 (EDT)
 
  
 
== Subpages ==
 
== Subpages ==
  
 
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
 
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Latest revision as of 17:59, 14 May 2016

Stop hand.png NOTE:
The content of this page is considered
DEPRECATED and OBSOLETE
It is preserved for historical research, along with its talk page.

Deployment Platform version cycle: | 1.0 | 1.1 | 2.0 |

Summary

A customizable platform based on the Sugar Learning Environment which is intended to be a basis for downstream distributions. The targeting audience for this platform are educational distributors and deployments who might be interested in these features:

  • A robust content sharing system, Sugar Network;
  • Getting feedback from the field;
  • Providing remote educational and technical support using Sugar Network's capabilities; which are especially needed in an offline scenario;
  • Supporting the offline scenario;
  • Centralized gathering of usage statistics;
  • Supporting heterogeneous deployments, i.e., not only XO laptops.

Deployment Platform consists of the following major components:

Base software is the foundation to start exploring the rest of the system. It will be accessible from Sweets Distribution native packages. Repositories of packaged software will be provided for all supported platforms and can be used as-is on top of existing operating system, e.g., GNU/Linux distribution for regular desktops, or OLPC OS for XO laptops.
This class of software is based on Sugar Network, with master services hosted on Sugar Labs resources. It provides a broad variety of content, such as Sugar activities, artifacts derived from Sugar activities, books, etc., and the community social activity centered around this content. It is the common information forum to embrace all participants. Software provided on this level, in comparison to Base software, will be supported out of native packages.
Deployment scenarios are a set of solutions adapting all the previous components in order to support differing Sugar deployment scenarios. For example, "Keep the LTS releases for an Operating System and its Base software", or "Provide tools to sort out Content to make it useful for specific deployment needs".

Deployment scenarios

The following list describes common deployment scenarios where Deployment Platform might be useful. The final model might be an intermediate variant of them tuned by third-party distributor for local needs.

  • Internet server
    There is a master server located on the Internet in a highly accessible place for any maintenance work. Users are always connected to the Internet and the master server.
  • Gateway server
    The school server has Internet connectivity and serves it into the local network where it can be used by clients. Users are always connected to their school server via the Intranet.
  • Offline server
    When the school server itself and clients it serves are in an Internet-less environment with only one way to be synchronized with the outer world, sneakernet.

Deployment specific functionality

The following features were designed especially for deployment workflow.

  • Common client side configuration for all Deployment Platform components;
  • Deployment specific improvements of the Sugar Shell:
  • Collecting usage statistics of Sugar users;
  • Lightweight package management to process system updates and extra dependencies installation on XO laptops.

Reference implementations

These are reference implementations of distributions based on Deployment Platform. These implementations might be used as a template for downstream solutions.

Downstream solutions

  • The Hexoquinasa project created by Peruvian community to support Sugar Learning Platform deployments.

See also

Getting involved

  • Subscribe to the sugar-devel mailing list and email with the subject prefixed with [PLATFORM].
  • Ask your question on IRC channels, #sugar (not logged) or #sugar-newbies (logged).

Subpages