5,705
edits
Changes
Jump to navigation
Jump to search
Line 22:
Line 22: + − + − Depending on will mace configuration be used in Sugar Server based deployments or not, implement configuration for all needed services:+ − + − − * 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 − + − − == (?) Initial Smart Objects support == − − [[Features/Smart_Objects]] − − 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...
Deployment Platform/1.1/Todo (view source)
Revision as of 20:29, 7 September 2011
, 20:29, 7 September 2011no edit summary
* more system tests of SSK infra using sugaroid to cover various deployment workflows
* more system tests of SSK infra using sugaroid to cover various deployment workflows
* using sugaroid bots, stress test prosody to compare with ejabberd
* using sugaroid bots, stress test prosody to compare with ejabberd
* the basis for regression tests to keep 1.x branch w/o regressions
== More sugar-server-templates templates ==
== New templates ==
* <strike>squidGuard</strike>
* Monitoring (?) Munin
* Content filter. Options are: Dans Guardian (MinD fork?), SquidCache, OpenDNS
== Deployment ==
== Deployment ==
* as much as possible plug&play solution for SSK based school servers
* SSK based .py final solution