Sugar Labs

Platform Team/Server Kit/Architecture: Difference between revisions

← Older editNewer edit →
No edit summary
Line 2: Line 2:


{{:Sugar_Server_Kit/Architecture/The_purpose}}
{{:Sugar_Server_Kit/Architecture/The_purpose}}
== Components ==
There are several major Sugar Server Kit project components that will be mentioned on this page:
* [[Sugar_Server_Kit/sugar-server|sugar-server]] provides basic sugar specific services,
* [[Sugar_Server_Kit/sugar-server-templates|sugar-server-templates]] provides configuration templates that might be reused in downstream solution,
* [[Sugar_Server_Kit/Mace|mace]] process configuration sources, e.g., from sugar-server-templates,
The only relationship between them are:
* sugar-server-templates contain basic configuration for sugar-servers.
* sugar-server-templates makes sense only after processing its content by mace.
These are building blocks for the final solutions in downstream deployments.


== Server functionality models ==
== Server functionality models ==
Line 66: Line 81:


== Distribution model ==
== Distribution model ==
How Sugar Server Kit might be reused from downstream, excluding the most obvious way, download its sources.
=== Core packages ===


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 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:
Line 79: Line 90:


Core packages are per-[[#Components|component]] and might be reused as-is in downstream, in a way that is most practical for them.
Core packages are per-[[#Components|component]] and might be reused as-is in downstream, in a way that is most practical for them.
=== Full cycle solution ===
Besides just having binary packages, it should be possible to build downstream packages and the final OS images on http://packages.sugarlabs.org by using only its web UI. The resulting files will be accessible for download from http://download.sugarlabs.org. It is an [https://build.opensuse.org/ Open Build Service] based service to build packages and images for rpm and deb based GNU/Linux distributions.


== Deployment model ==
== Deployment model ==
Line 95: Line 102:


The reliable testing environment should help with avoiding regressions while following [[Sugar Server Kit]] [[Sugar_Server_Kit/Release plan|statement of purpose]] for releases.
The reliable testing environment should help with avoiding regressions while following [[Sugar Server Kit]] [[Sugar_Server_Kit/Release plan|statement of purpose]] for releases.
== Components ==
There are several Sugar Server Kit project components:
* [[Sugar_Server_Kit/sugar-server|sugar-server]] provides basic sugar specific services,
* [[Sugar_Server_Kit/sugar-server-templates|sugar-server-templates]] provides configuration templates that might be reused in downstream solution,
* [[Sugar_Server_Kit/Mace|mace]] process configuration sources, e.g., from sugar-server-templates,
The only relationship between them are:
* sugar-server-templates contain basic configuration for sugar-servers.
* sugar-server-templates makes sense only after processing its content by mace.
These are building blocks for the final solutions in downstream deployments. Components are optional, meaning that
* sugar-server might be used in the singular manner; it doesn't need any special (outside of sugar-server) configuration, and can be started even from its sources directory;
* sugar-server-templates might be used in the singular manner (but obviously with the mace) to configure only non Sugar services;
* mace might be used in the singular manner to configure any services.
Retrieved from "https://wiki.sugarlabs.org/go/Platform_Team/Server_Kit/Architecture"