Difference between revisions of "Deployment Platform/1.1/Todo"

Revision as of 17:12, 23 August 2011

more system tests of SSK infra using sugaroid to cover various deployment workflows
using sugaroid bots, stress test prosody to compare with ejabberd

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

Many things to think about at first before any implementation...

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

Revision as of 17:06, 23 August 2011 (view source) Alsroot (talk \| contribs) (Created page with "All 1.x minor releases will be based on deployment needs. Including taking decision what following features need to be implemented. == Documentation == * in-code documentation ...")		Revision as of 17:12, 23 August 2011 (view source) Alsroot (talk \| contribs) m Newer edit →
Line 1:		Line 1:
−	~~All 1.x minor releases will be based on deployment needs. Including taking decision what following features need to be implemented.~~
−
	== Documentation ==		== Documentation ==