Difference between revisions of "Platform Team/Server Kit/Architecture"
< Platform Team | Server Kit
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | == | + | == Common purposes == |
− | + | * Having common project(s) and friendly support customization on purpose in downstream products: | |
+ | ** Modularizing when components might be included on purpose to fulfill local needs, | ||
+ | ** Not patching in downstream but supplementing the upstream, e.g., install upstream packages and just add additional packages with local customization without patching upstream code/configuration, | ||
+ | ** Provide useful API for any new components; | ||
+ | * Be a GNU/Linux distribution agnostic. It doesn't make much sense in case of having only Server on a school server and, e.g., installing Server from the ISO but it makes sense if downstream organizations ship their products based on the Server and having particular GNU/Linux distribution is important; | ||
+ | * It is not only about supporting XO laptops but about any Sugar based infrastructures. | ||
− | == | + | == Components == |
− | The | + | {| class="wikitable" border="1" |
+ | |- | ||
+ | ! scope="col" | '''Component''' | ||
+ | ! scope="col" | '''Provides''' | ||
+ | ! scope="col" | '''Description''' | ||
+ | |- | ||
+ | | [[#sugar-server|sugar-server]] | ||
+ | | Required modules: | ||
+ | * Student identification | ||
+ | Optional services: | ||
+ | * XO anti-thief support | ||
+ | * Entirely Journal backup/restore | ||
+ | * [[Features/Smart_Objects|Shared objects]] | ||
+ | | The core component. | ||
+ | |- | ||
+ | | [[#sugar-server-base|sugar-server-base]] | ||
+ | | Optional services: | ||
+ | * Jabber | ||
+ | * Web cache | ||
+ | * Content filter | ||
+ | * SSH | ||
+ | * NTP | ||
+ | * DNS | ||
+ | * DHCP | ||
+ | | Handling configuration of basic external services that need to be installed and configured on bare servers at school. | ||
+ | |} | ||
− | + | == sugar-server == | |
− | The | + | The Server provides basic services to support [[The_Server/Overview#Sugar_related|sugar based]], and [[The_Server/Overview#XO_specific|XO laptops]] in particular, infrastructure at schools. There is only one CLI tool to manage Server related functionality, {{Code|sugar-server}} utility. |
− | + | == sugar-server-base == | |
− | + | Thats an important part of the Server, since it should configure [[The_Server/Overview#Core|core services]] that need to be provided by a server at school. The configuration happens in GNU/Linux agnostic manner, basing on [[The Server/Mace|mace]] utility. | |
− | |||
− | |||
− | + | == Distribution == | |
− | + | The ways how upstream project might be obtained: | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | * Sources | |
+ | * Third party repositories with binary packages for particular GNU/Linux distribution | ||
− | The | + | The downstream organizations can choose the most practical way, eg, by using upstream repositories and adding new binary packages to tune upstream configuration. |
== Public API == | == Public API == |
Revision as of 06:43, 2 June 2011
Common purposes
- Having common project(s) and friendly support customization on purpose in downstream products:
- Modularizing when components might be included on purpose to fulfill local needs,
- Not patching in downstream but supplementing the upstream, e.g., install upstream packages and just add additional packages with local customization without patching upstream code/configuration,
- Provide useful API for any new components;
- Be a GNU/Linux distribution agnostic. It doesn't make much sense in case of having only Server on a school server and, e.g., installing Server from the ISO but it makes sense if downstream organizations ship their products based on the Server and having particular GNU/Linux distribution is important;
- It is not only about supporting XO laptops but about any Sugar based infrastructures.
Components
Component | Provides | Description |
---|---|---|
sugar-server | Required modules:
Optional services:
|
The core component. |
sugar-server-base | Optional services:
|
Handling configuration of basic external services that need to be installed and configured on bare servers at school. |
sugar-server
The Server provides basic services to support sugar based, and XO laptops in particular, infrastructure at schools. There is only one CLI tool to manage Server related functionality, sugar-server
utility.
sugar-server-base
Thats an important part of the Server, since it should configure core services that need to be provided by a server at school. The configuration happens in GNU/Linux agnostic manner, basing on mace utility.
Distribution
The ways how upstream project might be obtained:
- Sources
- Third party repositories with binary packages for particular GNU/Linux distribution
The downstream organizations can choose the most practical way, eg, by using upstream repositories and adding new binary packages to tune upstream configuration.