Sugar Labs

Deployment Platform/1.1/Todo: Difference between revisions

← Older edit
 
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
== New distro support ==
* <strike>Support Ubuntu [Server] in Mace.</strike>
== sugar-server-blacklist ==
== sugar-server-blacklist ==


Line 11: Line 15:
[[Sugar_Server_Kit/sugar-client|New]] SSK component.
[[Sugar_Server_Kit/sugar-client|New]] SSK component.


* handle datastore backup/restore
* <strike>handle datastore backup/restore</strike>
* handle package upgrades from school server for deployment specific updates (from separate repositories)
* <strike>handle package upgrades from school server for deployment specific updates (from separate repositories)</strike>


== Documentation ==
== Documentation ==


* in-code documentation for sugar-server and sugar-server-templates
* <strike>in-code documentation for sugar-server and sugar-server-templates</strike>, not completed, will be continued while working on 1.2


== Testing ==
== Testing ==


* more system tests of SSK infra using sugaroid to cover various deployment workflows
* <strike>more system tests of SSK infra using sugaroid to cover various deployment workflows</strike>, not fully completed, moved to 1.2 TODO and looking for SSK usage in the field;
* using sugaroid bots, stress test prosody to compare with ejabberd
* <strike>using sugaroid bots, stress test prosody to compare with ejabberd</strike>, not completed, moved to 1.2 TODO;
* <strike>the basis for regression tests to keep 1.x branch w/o regressions</strike> all SSK components have an initial set (the process is ongoing) of unit tests that will let keep the system out of regressions.


== More sugar-server-templates templates ==
== New templates ==


Depending on will mace configuration be used in Sugar Server based deployments or not, implement configuration for all needed services:
* <strike>squidGuard</strike>
* <strike>munin-node</strike>
* 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 ==
== Deployment ==


* as much as possible plug&play solution for SSK based school servers
* <strike>SSK based .py final solution</strike>, [[Sugar_Server_Kit/Solutions/Paraguay_Educa_Server|.py pilot program]].
 
== (?) 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...
Retrieved from "https://wiki.sugarlabs.org/go/Deployment_Platform/1.1/Todo"