Sugar Labs

Deployment Platform/1.0/Todo: Difference between revisions

← Older edit
No edit summary
 
(31 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== 1.0 ==
Initial Sugar Server release that is not intended to be used as-is in deployments. It is about having stable code base and infra to fulfil deployment needs in further 1.x releases.


=== <strike>Initial coding of core components</strike> ===
== Initial coding of core components ==


* sugar-server
* <strike>sugar-server</strike>
* sugar-server-base
* <strike>sugar-server-base</strike>
* mace
* <strike>mace</strike>


Need to be polished though (see the rest of TODO).
Need to be polished though (see the rest of TODO).


=== Patch OBS ===
== Testing ==


* produce binary packages with sugar-server, mace and sugar-server-base for Fedora-11
* <strike>sugar-server unit tests</strike>, initial work done the rest is in permanent process
* (?) Create images on OBS for Fedora
* <strike>mace unit tests</strike>, initial work done the rest is in permanent process
* <strike>sugaroid, library and application that represent regular sugar client behaviour</strike>
* <strike>sugar-server integration tests using sugaroid library</strike>, initial work done the rest is in permanent process
* <strike>system tests of sugar-server + sugar-server-base infra with reproducing usual and stress behaviour of sugar client using sugaroids instances (up to 1K)</strike> sounds like more deployment related task, thus moved to 1.x releases


=== Prosody ===
== Patch OBS ==


* improve mod_sugar_roaster plugin to share the same memory structure of sugar roaster among all buddies
* <strike>produce binary packages with sugar-server, mace and sugar-server-base for Fedora-14</strike>
* stress test it, up to 1K users
* <strike>while most of packages come from initial distro release, monitor for updates for some of package, e.g., xulrunner when hulahop needs to be rebuilt on any new xulrunner update</strike> all packages on obs are based on initial distro releases, hulahop/sugar were patched to not fail on every minor update
* <strike>announce packages.sl.o, not only for Sugar Server usage but also for sweets/sdk</strike> will be announced with sweets


Sugar code is here, http://git.sugarlabs.org/server/prosody
== Prosody ==


=== Content filter ===
* <strike>improve mod_sugar_roaster plugin to share the same memory structure of sugar roaster among all buddies</strike>
* <strike>using sugaroid bots, stress test prosody to compare with ejabberd</strike> not ready, moved to 1.x


Configuration in sugar-server-base
Sugar code is here, http://git.sugarlabs.org/server/prosody-sugar


=== Monitoring support ===
== Documentation ==


If connectivity is good then no questions, there are bunch of ready to use solutions like Munin, Nagious, etc.
<strike>Initial documentation efforts on the wiki.</strike>


=== Initial Smart Objects support ===
== Tech demo ==


[[Features/Smart_Objects]]
<strike>Test case:


=== Mothership ===
* on unlocked XO, plug usb stick with demo server image, flash and booth
* on locked XO, inject lease demo keys from a usb stick and boot
* locked XO should be fine with:
** activate on boot on unlocked XO
** register user
** do journal backup
** restore journal
** connect to jabber


* Interaction with motherships
Demo server XO image will be composed by adding {{Code|downstream-server-demo}} package (and all its deps) during the regular XO image building process.</strike>
* (?) Initial sugar-mothership implementation, only regarding to current sugar-server functionality
Retrieved from "https://wiki.sugarlabs.org/go/Deployment_Platform/1.0/Todo"