5,705
edits
Changes
Platform Team/Server Kit/Architecture (view source)
Revision as of 11:37, 6 November 2011
, 11:37, 6 November 2011→Server functionality models
* 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.
* sugar-server doesn't break the system configuration (it touches nothing).
* sugar-server doesn't break the system configuration (it touches nothing).
The maintaining process is the same as for any other service launched on a server.
=== Dumb school servers ===
=== Dumb school servers ===
After installing the main package, it will provide possibility to fetch Mace environment file and pure data from the Mothersip, and finally running Mace to complete school server setup.
After installing the main package, it will provide possibility to fetch Mace environment file and pure data from the Mothersip, and finally running Mace to complete school server setup.
The maintaining process will be:
* sugar-server-templates provides unattended packages update on school servers, packages to update come from:
** GNU/Linux official repositories with security updates,
** Sugar Server Kit upstream repository that follows the [[Sugar_Server_Kit/Release_plan|Statement of purpose for releases]], i.e., declares that newly appeared updates should not break already deployed systems;
* taking care that pure data on the Mothership is up-to-date, e.g., leases are properly created, content filtering blacklists are fresh, etc.;
* do occasional changes in the main school server package to add new services or tune downstream Mace configuration and upload it to the repository that will be used for unattended updates on school servers;
* do occasional changes in the Mace environment file to reflect on global changes in deployment infrastructure.
=== Highly maintained school servers ===
=== Highly maintained school servers ===
Servers at schools might be not only simple like in the previous model. They might contain complex services like content management systems. This usecase might require more regular maintaining scenarios, e.g., using configuration tools like Puppet or CFEngine, having more detailed monitoring, etc.
It seems that the only useful Sugar Server Kit component here is the sugar-server.
== Client functionality models ==
== Client functionality models ==