Deployment Platform/1.0/Todo
< Deployment Platform | 1.0
Jump to navigation
Jump to search
1.0
Initial coding of core components
- sugar-server
- sugar-server-base
- mace
Need to be polished though (see the rest of TODO).
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 to sugar-server-base.
Options are:
- Dans Guardian (MinD fork, since it provide proxy-less mode that might be useful if some deployment don't need proxy)
- SquidCache
- OpenDNS
- ?
Thoughts:
- 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 pure commercial organisation with ugly stuff like forwarding failed request to is 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:
- run http://collectd.org/ daemons on school servers and provide useful uploading method
Initial Smart Objects support
Mothership
- Interaction with motherships
- (?) Initial sugar-mothership implementation, only regarding to current sugar-server functionality