Difference between revisions of "Deployment Platform/1.2/Todo"
< Deployment Platform | 1.2
Jump to navigation
Jump to search
(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...") |
|||
| 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 == | ||
Revision as of 19:42, 7 September 2011
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:
- 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
Feedback service for sugar-server
- Handle reports and statistic from XOs around school server to securely send to the mothership
Deployment
- as much as possible plug&play solution for SSK based school servers
(?) Initial Smart Objects support
Many things to think about at first before any implementation...
(?) Mothership
- Interaction with motherships
- Initial sugar-mothership implementation, only regarding to current sugar-server functionality
Need to collect more experience from XS deployments before any implementation...