Changes

== Summary ==

== Summary ==

This is [[Harmonic_Distribution/Deployment|one of possible]] reference implementations of [[Harmonic Distribution]] based solutions. The goal is creating Sugar based downstream distribution to run on OLPC XO laptops by end-users. Created reference implementation is intended to be a template for final deployment distribution.

This is [[Harmonic_Distribution/Deployment|one of the possible]] reference implementations of [[Harmonic Distribution]] based solutions. The goal is creating a Sugar based downstream distribution to run on OLPC XO laptops by end-users. The created reference implementation is intended to be a template for final deployment distributions.

== Overview ==

== Overview ==

The task is creating XO image capable for further support.

The task is to create an XO image capable of further support.

Image will be composed using [http://wiki.laptop.org/go/OSBuilder olpc-os-builder] utility and will be populated with the following content:

The image will be composed using the [http://wiki.laptop.org/go/OSBuilder olpc-os-builder] utility and will be populated with the following content:

'''System packages'''

'''System packages'''

:Package will be installed from the following sources:

:Packages will be installed from the following sources:

:* stock Fedora repositories,

:* stock Fedora repositories,

:* [http://mock.laptop.org/cgit/ stable OLPC repositories],

:* [http://mock.laptop.org/cgit/ stable OLPC repositories],

:* one of [[Template:Sweets_Distribution_Linkbar|Sweets Distribution]] repositories (for now, available only [[Platform_Team/Sweets_Distribution/Factory|Factory]]),

:* one of the [[Template:Sweets_Distribution_Linkbar|Sweets Distribution]] repositories (for now, only the [[Platform_Team/Sweets_Distribution/Factory|Factory]] repository is available),

:* [[#Deployment_repository|deployment repository]] to keep packages specific only to particular deployment.

:* the [[#Deployment_repository|deployment repository]] to keep packages specific to a particular deployment.

'''Initial Sugar Activities'''

'''Initial Sugar Activities'''

:[[Harmonic Distribution]] based solution are based on [[Sugar Network]] when all Sugar Activities are accessible from local school server or Internet located one. But, it is useful to have some first-time activities already included to the image.

:[[Harmonic Distribution]] based solutions are based on [[Sugar Network]], which makes all Sugar Activities accessible from a local school server or an Internet located one. Nonetheless, it is useful to have some first-time activities already included with the image.

: Activities will be downloaded from the Sugar Network and placed to {{Code|~/Activities}} directory in the image.

: Activities will be downloaded from the Sugar Network and placed in the {{Code|~/Activities}} directory in the image.

'''Deployment configuration'''

'''Deployment configuration'''

:This is how final systems will be initially configured and supported afterwards. All deployment configuration is placed to [[#Deployment_package|meta package]] in [[#Deployment_repository|deployment repository]]. This meta package contains dependencies and configuration files for all other packages needed to be installed on final systems. Further, if there is a need to change configuration on already installed systems, meta package will be updated and spread among users.

:This is how final systems will be initially configured and supported afterwards. All deployment configuration is placed in a [[#Deployment_package|meta package]] in the [[#Deployment_repository|deployment repository]]. This meta package contains dependencies and configuration files for all other packages needing to be installed on final systems. Further, if there is a need to change configuration on already installed systems, the meta package will be updated and spread among users.

== Start new implementation ==

== Start new implementation ==

These are step-by-step instruction how to create new deployment distribution basing on this reference implementation.

These are step-by-step instruction on how to create a new deployment distribution based on this reference implementation.

=== Deployment repository ===

=== Deployment repository ===

Make sure you have Fedora repository accessible from building host and end-users. If you are looking for building and hosting environment, try [[Platform_Team/Open_Build_System|packages.sugarlabs.org]] which is an instance of [http://www.open-build-service.org/ Open Build Service].

Make sure you have the Fedora repository accessible from building host and end-users. If you are looking for a building and hosting environment, try [[Platform_Team/Open_Build_System|packages.sugarlabs.org]], which is an instance of [http://www.open-build-service.org/ Open Build Service].

If you are using [[Platform_Team/Open_Build_System|packages.sugarlabs.org]], create new project and add Fedora-14 repository from [[Sweets Distribution]] project your implementation is based on. For example, there is [https://packages.sugarlabs.org/project/show?project=SweetsDistribution%3AFactory%3AReferenceXO reference project] based on [https://packages.sugarlabs.org/project/show?project=SweetsDistribution%3AFactory SweetsDistribution:Factory] repositories.

If you are using [[Platform_Team/Open_Build_System|packages.sugarlabs.org]], create a new project and add the Fedora 14 repository from the [[Sweets Distribution]] project your implementation is based on. For example, there is [https://packages.sugarlabs.org/project/show?project=SweetsDistribution%3AFactory%3AReferenceXO reference project] based on [https://packages.sugarlabs.org/project/show?project=SweetsDistribution%3AFactory SweetsDistribution:Factory] repositories.

=== Deployment package ===

=== Deployment package ===