Deployment Platform/1.0/Todo: Difference between revisions

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.

=== Initial coding of core components ===

Line 26:

Line 28:

* <strike>improve mod_sugar_roaster plugin to share the same memory structure of sugar roaster among all buddies</strike>

* using sugaroid bots, stress test prosody to compare with ejabberd

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

=== ~~Content filter~~ ===

=== Initial configuration using Mace ===

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

It is a proof of concept.

~~Options are:~~

* configure sugar-server and prosody in form dextrose-server package

* Dans Guardian (MinD fork)

=== Documentation ===

* SquidCache

* OpenDNS

* ?

~~Thoughts:~~

Initial documentation efforts on the wiki.

* Nepal uses Dans Guardian and looks like pretty satisfied

== 1.x ==

* 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 ===~~

All 1.x minor releases will be based on deployment needs. Including taking decision what following features need to be implemented.

~~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.

=== More sugar-server-base templates ===

~~Thoughts~~:

Depending on will mace configuration be used in Sugar Server based deployments or not, implement configuration for all needed services:

* run http://collectd.org/ daemons on school servers and provide useful uploading method

* 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

~~=== Documentation ===~~

~~Initial documentation efforts on the wiki.~~

~~== 1.x ==~~

=== Initial Smart Objects support ===

@@ 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.
 === Initial coding of core components ===
@@ Line 26: / Line 28: @@
 * <strike>improve mod_sugar_roaster plugin to share the same memory structure of sugar roaster among all buddies</strike>
+* using sugaroid bots, stress test prosody to compare with ejabberd
 Sugar code is here, http://git.sugarlabs.org/server/prosody-sugar
-=== Content filter ===
+=== Initial configuration using Mace ===
-Need to decide what content filter software configuration will be included with sugar-server-base.
+It is a proof of concept.
-Options are:
+* configure sugar-server and prosody in form dextrose-server package
-* Dans Guardian (MinD fork)
+=== Documentation ===
-* SquidCache
-* OpenDNS
-* ?
-Thoughts:
+Initial documentation efforts on the wiki.
-* Nepal uses Dans Guardian and looks like pretty satisfied
+== 1.x ==
-* 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 ===
+All 1.x minor releases will be based on deployment needs. Including taking decision what following features need to be implemented.
-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.
+=== More sugar-server-base templates ===
-Thoughts:
+Depending on will mace configuration be used in Sugar Server based deployments or not, implement configuration for all needed services:
-* run http://collectd.org/ daemons on school servers and provide useful uploading method
+* 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
-=== Documentation ===
-Initial documentation efforts on the wiki.
-== 1.x ==
 === Initial Smart Objects support ===