Changes

* Functionality of school servers is simple, only basic services.

* Functionality of school servers is simple, only basic services.

* Complex, thus non-trivial for maintenance, services are on the mothership and singular, i.e., to minimize maintenance costs and let the minimal number of skilled personal support them effectively.

* Complex—thus, non-trivial for maintenance—services are on the mothership and singular, so to minimize maintenance costs and allow effective support with the minimum number of skilled personal.

* A set of school server's services tends to be constant, at least it doesn't require regular intervention to add/remove services.

* A set of school server's services tends to be constant, at least it doesn't require regular intervention to add/remove services.

* All school servers have exactly the same set of services.

* All school servers have exactly the same set of services.

=== Highly maintained school servers ===

=== Highly maintained school servers ===

Servers at schools might not be so simple as in the previous model. They might contain complex services like content management systems. This usecase might require more regular maintenance scenarios, e.g., using configuration tools like Puppet or CFEngine, or having more detailed monitoring, etc.

Servers at schools might not be so simple as in the previous model. They might contain complex services like content management systems. This use case might require more regular maintenance scenarios, e.g., using configuration tools like Puppet or CFEngine, or having more detailed monitoring, etc.

It seems that the only useful Sugar Server Kit component here is the sugar-server.

It seems that the only useful Sugar Server Kit component here is the sugar-server.