Changes

== Functionality model ==

== Functionality model ==

This is all about how improved functionality of servers at schools might look, at least, Sugar Server is being designed and implemented in this direction. Sugar Server is not intended to cover all the components described here. It is just the global picture from a Sugar Server point of view.

This is all about how improved functionality of servers at schools might look, at least, Sugar Server Kit is being designed and implemented in this direction. Sugar Server Kit is not intended to cover all the components described here. It is just the global picture from a Sugar Server Kit point of view.

Two pure models might describe Sugar Server design, the final model might be an intermediate variant of them.

Two pure models might describe Sugar Server Kit design, the final model might be an intermediate variant of them.

=== Black box model ===

=== Black box model ===

The model where the server at school is entirely dependent on Sugar Server design decisions. There are two types of machines:

The model where the server at school is entirely dependent on Sugar Server Kit design decisions. There are two types of machines:

* servers at schools under Sugar Server control

* servers at schools under Sugar Server Kit control

* optional mothership(s) to control school servers

* optional mothership(s) to control school servers

=== One package model ===

=== One package model ===

The model with minimal Sugar Server design influence:

The model with minimal Sugar Server Kit design influence:

* existing and configured out of Sugar Server servers at schools

* existing and configured out of Sugar Server Kit servers at schools

* the remaining environment that Sugar Server is not aware of

* the remaining environment that Sugar Server Kit is not aware of

The key points:

The key points:

* Servers at schools are supported out of Sugar Server.

* Servers at schools are supported out of Sugar Server Kit.

* Admins install the sugar-server package from upstream binary repositories, and just launch it.

* Admins install the sugar-server package from upstream binary repositories, and just launch it.

* sugar-server starts to serve all sugar boxes around, providing only [[#sugar-server|basic sugar specific]] functionality.

* sugar-server starts to serve all sugar boxes around, providing only [[#sugar-server|basic sugar specific]] functionality.

== Distribution model ==

== Distribution model ==

How Sugar Server might be reused from downstream, excluding the most obvious way, download its sources.

How Sugar Server Kit might be reused from downstream, excluding the most obvious way, download its sources.

=== Core packages ===

=== Core packages ===

Sugar Server is designed to avoid patching its sources in downstream. Reusing upstream binary packages as-is from repositories on http://download.sugarlabs.org is how Sugar Server is being designed. Downstream might create new packages, that don't have file collisions with upstream packages, to have tweaks for local environment. It is being accomplished by:

Sugar Server Kit is designed to avoid patching its sources in downstream. Reusing upstream binary packages as-is from repositories on http://download.sugarlabs.org is how Sugar Server Kit is being designed. Downstream might create new packages, that don't have file collisions with upstream packages, to have tweaks for local environment. It is being accomplished by:

* sugar-server project has services formed as plugins, from downstream packages. Such services might be:

* sugar-server project has services formed as plugins, from downstream packages. Such services might be:

== Deployment model ==

== Deployment model ==

It is an entirely downstream decision as to how to deploy Sugar Server based solutions.

It is an entirely downstream decision as to how to deploy Sugar Server Kit based solutions.

== Components ==

== Components ==

There are several Sugar Server project components:

There are several Sugar Server Kit project components:

* [[The_Server/sugar-server|sugar-server]] provides basic sugar specific services,

* [[Sugar_Server_Kit/sugar-server|sugar-server]] provides basic sugar specific services,

* [[The_Server/sugar-server-templates|sugar-server-templates]] provides configuration templates that might be reused in downstream solution,

* [[Sugar_Server_Kit/sugar-server-templates|sugar-server-templates]] provides configuration templates that might be reused in downstream solution,

* [[The_Server/Mace|mace]] process configuration sources, e.g., from sugar-server-templates,

* [[Sugar_Server_Kit/Mace|mace]] process configuration sources, e.g., from sugar-server-templates,

The only relationship between them are:

The only relationship between them are: