Changes

<noinclude>{{TeamHeader|Infrastructure Team}}</noinclude>

<noinclude>{{TeamHeader|Infrastructure Team}}{{TOCright}}

{{TOCright}}

==Introduction==

==Introduction==

A content delivery network or content distribution network (CDN) is a system of computers containing copies of data, placed at various points in a network so as to maximize bandwidth for access to the data from clients throughout the network. A client accesses a copy of the data near to the client, as opposed to all clients accessing the same central server, thereby causing a bottleneck near that server.

A content delivery network or content distribution network (CDN) is a system of computers containing copies of data, placed at various points in a network so as to maximize bandwidth for access to the data from clients throughout the network. A client accesses a copy of the data near to the client, as opposed to all clients accessing the same central server, thereby causing a bottleneck near that server.

Mirrorbrain, Bouncer, Fedora Mirror Manager, and Cacheboy are four possible choices for scaling up the Sugar Labs content delivery net work.  Long term, Cacheboy looks like it might be the best fit for Sugar Labs, but the project must become more stable before becoming Sugar Labs primary CDN.  Bouncer is currently being used as successfully by Mozilla.  But development ended at the end of 2008.  Mozilla is currently investigating Mirrorbrain.  Mirrorbrain looks promising.

Mirrorbrain, Bouncer, Fedora Mirror Manager, and Cacheboy are four possible choices for scaling up the Sugar Labs content delivery network.  Long term, Cacheboy looks like it might be the best fit for Sugar Labs, but the project must become more stable before becoming Sugar Labs primary CDN.  Bouncer is currently being used as successfully by Mozilla.  But development ended at the end of 2008.  Mozilla is currently investigating Mirrorbrain.  Mirrorbrain looks promising.

==Goals==

==Goals==

*Reduce bandwith at primary download server.

* Reduce bandwith at primary download server.

*Improve quality of service for users.

* Improve quality of service for users.

*Move content closer to users.

* Move content closer to users.

==Mirrors==

==Mirrors==

<noinclude>[[Category:Resource]]</noinclude>

</noinclude>

<includeonly>==[[Mirrors]]==</includeonly>

<includeonly>==[[Infrastructure Team/Content Delivery Network|Content Delivery Network]]==</includeonly>

=== Global Mirror ===

=== Global Mirror ===

|}

|}

==Becoming a Mirror==

===Becoming a Mirror===

rsync -avz --exclude=soas/snapshots  --exclude=soas/xoimages  rsync://sunjammer.sugarlabs.org/pub ~/d3.sl.o

rsync -avz --exclude=soas/snapshots  --exclude=soas/xoimages  rsync://sunjammer.sugarlabs.org/pub ~/d3.sl.o

=== Monitoring ===

==== Monitoring ====

There is some basic information on the status of our mirrors.

There is some basic information on the status of our mirrors.

Your can find it here, http://martenvijn.nl/sugar_mirror.html

Your can find it here, http://martenvijn.nl/sugar_mirror.html

 

===[http://mirrorbrain.org/ Mirrorbrain]===

==[http://mirrorbrain.org/ Mirrorbrain]==

Mirrrorbrain is used by several major project including opensuse and openoffice.  It is quite stable, under activate development, and well documented,  

Mirrrorbrain is used by several major project including opensuse and openoffice.  It is quite stable, under activate development, and well documented,  

===Installation===

====Installation====

Please see http://mirrorbrain.org/docs/installation/debian/ .  Our Sugar Labs installation instructions have become the official mirrorbrain on ubuntu instructions.

Please see http://mirrorbrain.org/docs/installation/debian/ .  Our Sugar Labs installation instructions have become the official mirrorbrain on ubuntu instructions.