Deployment Platform/1.2/Todo: Difference between revisions

Line 1:

== More sugar-server-templates templates ==

Depending on whether mace configuration will be used in Sugar Server based deployments or not, implement ~~configuration~~ for all needed services:

Depending on whether mace configuration will be used in Sugar Server based deployments or not, implement configurations for all needed services:

* Content filter. Options are: Dans Guardian (MinD fork?), SquidCache, OpenDNS

* Monitoring support. If connectivity is good, then no ~~questions~~, there are a bunch of ready-to-use solutions like Munin, Nagious, etc. The problematic use case is having servers that are mostly or entirely offline. ~~The way~~ might be collecting data on school servers and passing them to the mothership somehow via sneakernet. Options: run http://collectd.org/ daemons on school servers and provide a useful uploading method.

* Monitoring support. If connectivity is good, then, no question, there are a bunch of ready-to-use solutions like Munin, Nagious, etc. The problematic use case is having servers that are mostly or entirely offline. A solution might be collecting data on school servers and passing them to the mothership somehow via sneakernet. Options: run http://collectd.org/ daemons on school servers and provide a useful uploading method.

== Glucose patches ==

Line 12:

== [[Sugar_Server_Kit/Usage_Statistics|Usage statistics]] ==

Handle reports and statistics from XOs around a school server and securely send such to the mothership. This feature might be useful from pedagogical point of view, e.g., what activity is being used most of all.

Handle reports and statistics from XOs around a school server, and securely send such to the mothership. This feature might be useful from a pedagogical point of view, e.g., what activity is being used most of all.

== Avoid compromised school servers ==

@@ Line 1: / Line 1: @@
 == More sugar-server-templates templates ==
-Depending on whether mace configuration will be used in Sugar Server based deployments or not, implement configuration for all needed services:
+Depending on whether mace configuration will be used in Sugar Server based deployments or not, implement configurations for all needed services:
 * Content filter. Options are: Dans Guardian (MinD fork?), SquidCache, OpenDNS
-* Monitoring support. If connectivity is good, then no questions, there are a bunch of ready-to-use solutions like Munin, Nagious, etc. The problematic use case is having servers that are mostly or entirely offline. The way might be collecting data on school servers and passing them to the mothership somehow via sneakernet. Options: run http://collectd.org/ daemons on school servers and provide a useful uploading method.
+* Monitoring support. If connectivity is good, then, no question, there are a bunch of ready-to-use solutions like Munin, Nagious, etc. The problematic use case is having servers that are mostly or entirely offline. A solution might be collecting data on school servers and passing them to the mothership somehow via sneakernet. Options: run http://collectd.org/ daemons on school servers and provide a useful uploading method.
 == Glucose patches ==
@@ Line 12: / Line 12: @@
 == [[Sugar_Server_Kit/Usage_Statistics|Usage statistics]] ==
-Handle reports and statistics from XOs around a school server and securely send such to the mothership. This feature might be useful from pedagogical point of view, e.g., what activity is being used most of all.
+Handle reports and statistics from XOs around a school server, and securely send such to the mothership. This feature might be useful from a pedagogical point of view, e.g., what activity is being used most of all.
 == Avoid compromised school servers ==