Deployment Platform/1.2/Todo: Difference between revisions

Line 1:

== More sugar-server-templates templates ==

Depending on ~~will~~ mace configuration 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 configuration 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 bunch of ready-to-use solutions like Munin, Nagious, etc. The problematic ~~usecase~~ is having servers that are mostly or entirely offline. The way might be collecting data on school servers and ~~pass~~ them to the mothership somehow via sneakernet. Options: run http://collectd.org/ daemons on school servers and provide useful uploading method

* 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.

== Feedback service for sugar-server ==

* Handle reports and ~~statistic~~ from XOs around school server to securely send to the mothership

* Handle reports and statistics from XOs around a school server and securely send such to the mothership

== Deployment ==

* as much as possible plug&play solution for SSK based school servers

* as much as possible a plug&play solution for SSK based school servers

== (?) Initial Smart Objects support ==

Line 22:

== (?) Mothership ==

* Interaction with motherships

* Interaction with other motherships

* Initial sugar-mothership implementation, only ~~regarding to~~ current sugar-server functionality

* Initial sugar-mothership implementation, regarding only the current sugar-server functionality

Need to collect more experience from XS deployments before any implementation...

@@ Line 1: / Line 1: @@
 == More sugar-server-templates templates ==
-Depending on will mace configuration 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 configuration 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 bunch of ready-to-use solutions like Munin, Nagious, etc. The problematic usecase is having servers that are mostly or entirely offline. The way might be collecting data on school servers and pass them to the mothership somehow via sneakernet. Options: run http://collectd.org/ daemons on school servers and provide useful uploading method
+* 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.
 == Feedback service for sugar-server ==
-* Handle reports and statistic from XOs around school server to securely send to the mothership
+* Handle reports and statistics from XOs around a school server and securely send such to the mothership
 == Deployment ==
-* as much as possible plug&play solution for SSK based school servers
+* as much as possible a plug&play solution for SSK based school servers
 == (?) Initial Smart Objects support ==
@@ Line 22: / Line 22: @@
 == (?) Mothership ==
-* Interaction with motherships
+* Interaction with other motherships
-* Initial sugar-mothership implementation, only regarding to current sugar-server functionality
+* Initial sugar-mothership implementation, regarding only the current sugar-server functionality
 Need to collect more experience from XS deployments before any implementation...