5,705
edits
Changes
Jump to navigation
Jump to search
Line 13:
Line 13: − == Components ==+ Line 21:
Line 21: − + + + + + + + + + + + + + + + + + + + + +
no edit summary
* Supporting heterogeneous deployments, i.e., not only XO laptops.
* Supporting heterogeneous deployments, i.e., not only XO laptops.
Deployment Platform consists of the following major components:
* [[Deployment_Platform/Software#Software_Map|Base software]]
* [[Deployment_Platform/Software#Software_Map|Base software]]
: 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 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".
: 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".
== 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]].
== Reference distributions ==
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 distributions ==
== Downstream distributions ==