Deployment Platform/1.1/Todo

sugar-server-blacklist

New SSK component.

• package blacklists for content filtering in SSK repo
• setup infra on jita.sugarlabs.org for regular updates for this package
• add blacklist provider to the Mace.

sugar-client

New SSK component.

• handle datastore backup/restore
• handle package upgrades from school server for deployment specific updates (from separate repositories)

Documentation

• in-code documentation for sugar-server and sugar-server-templates

Testing

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

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

Deployment

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

(?) 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...