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

From Sugar Labs
Jump to navigation Jump to search
Line 31: Line 31:
 
=== Content filter ===
 
=== Content filter ===
  
Need to decide what content filter software configuration will be included to sugar-server-base.
+
Need to decide what content filter software configuration will be included with sugar-server-base.
  
 
Options are:
 
Options are:
Line 43: Line 43:
  
 
* Nepal uses Dans Guardian and looks like pretty satisfied  
 
* Nepal uses Dans Guardian and looks like pretty satisfied  
* Dans Guardian's site declares that it is faster then SquidCache but publication date is too old
+
* Dans Guardian's site declares that it is faster then SquidCache, but publication date is too old
 
* Dans Guardian's MinD for is promising option, it support proxy-less mode and has recent activity (in comparing with Dans Guardian)
 
* Dans Guardian's MinD for is promising option, it support proxy-less mode and has recent activity (in comparing with Dans Guardian)
* OpenDNS way might be useful, i.e., having such server on the mothership and point all school servers' dns there. but can't find (?) FOSS project with such functionality and opendns.com is pure commercial organisation with ugly stuff like forwarding failed request to is site with ads and it can change the rules at any time.
+
* OpenDNS way might be useful, i.e., having such server on the mothership and point all school servers' dns there. but can't find (?) FOSS project with such functionality and opendns.com is a pure commercial organisation with ugly stuff like forwarding failed requests to its site with ads, and it can change the rules at any time.
  
 
=== Monitoring support ===
 
=== 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.
+
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.
  
 
Thoughts:
 
Thoughts:
Line 59: Line 59:
 
[[Features/Smart_Objects]]
 
[[Features/Smart_Objects]]
  
Many things to think at first before any implementation...
+
Many things to think about first before any implementation...
  
 
=== Mothership ===
 
=== Mothership ===
Line 66: Line 66:
 
* (?) Initial sugar-mothership implementation, only regarding to current sugar-server functionality
 
* (?) Initial sugar-mothership implementation, only regarding to current sugar-server functionality
  
Need to collect more existed experience from XS deployments before any implementation...
+
Need to collect more experience from XS deployments before any implementation...

Revision as of 11:24, 11 June 2011

1.0

Initial coding of core components

  • sugar-server
  • sugar-server-base
  • mace

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

Testing

  • sugar-server unit tests, initial work done the rest is in permanent process
  • mace unit tests, initial work done the rest is in permanent process
  • sugaroid, library and application that represent regular sugar client behaviour
  • sugar-server integration tests using sugaroid library
  • system tests of sugar-server + sugar-server-base infra with reproducing usual and stress behaviour of sugar client using sugaroids instances (up to 1K)

Patch OBS

  • produce binary packages with sugar-server, mace and sugar-server-base for Fedora-11
    alsroot 19:46, 9 June 2011 (EDT)
  • (?) Create images on OBS for Fedora

Prosody

  • improve mod_sugar_roaster plugin to share the same memory structure of sugar roaster among all buddies
  • stress test it, up to 1K users

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

Content filter

Need to decide what content filter software configuration will be included with sugar-server-base.

Options are:

  • Dans Guardian (MinD fork)
  • SquidCache
  • OpenDNS
  • ?

Thoughts:

  • Nepal uses Dans Guardian and looks like pretty satisfied
  • Dans Guardian's site declares that it is faster then SquidCache, but publication date is too old
  • Dans Guardian's MinD for is promising option, it support proxy-less mode and has recent activity (in comparing with Dans Guardian)
  • OpenDNS way might be useful, i.e., having such server on the mothership and point all school servers' dns there. but can't find (?) FOSS project with such functionality and opendns.com is a pure commercial organisation with ugly stuff like forwarding failed requests to its site with ads, and it can change the rules at any time.

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.

Thoughts:

Initial Smart Objects support

Features/Smart_Objects

Many things to think about 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...