Deployment Platform/1.2/Todo: Difference between revisions
Created page with "== More sugar-server-templates templates == Depending on will mace configuration be used in Sugar Server based deployments or not, implement configuration for all needed service..." |
No edit summary |
||
| Line 5: | Line 5: | ||
* Content filter. Options are: Dans Guardian (MinD fork?), SquidCache, OpenDNS | * 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 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 | ||
== Feedback service for sugar-server == | |||
* Handle reports and statistic from XOs around school server to securely send to the mothership | |||
== Deployment == | == Deployment == | ||