[Server-devel] CCCS XS deployment

Josh Totoro jtotoro at chartersmi.com
Tue Oct 13 09:37:32 EDT 2009

Thanks for the Info, but we ended up going a different direction.

We segregated the wireless networks for each building into different VLAN's and created a unique SSID for each building, we then made the XS the gateway to our main network for each VLAN.  This limited the number of users per XS to 350 total and more like 100 concurrent.  So far it seems to be working.  The kids only see other kids from their own building but that was fine by us since there are different grades in each building.

FYI we are running this XO network on our Procurve Wireless Edge Service module and it has been working like a charm.  I didn't know if you knew anyone else who has tested this system so I thought I would let you know.

Thanks for the help

-----Original Message-----
From: Martin Langhoff [mailto:martin.langhoff at gmail.com]
Sent: Monday, October 12, 2009 3:47 AM
To: jvonau at shaw.ca
Cc: Josh Totoro; server-devel at lists.laptop.org
Subject: Re: [Server-devel] CCCS XS deployment

On Mon, Oct 12, 2009 at 2:50 AM, Jerry Vonau <jvonau at shaw.ca> wrote:
>> When I set up the first XS server back in march (0.5.1) there was a
>> lot more info on the Wiki about setting up multiple XS servers in one
>> network.  Does anyone have any of this info available still or does it
>> no longer apply?

I removed the info because we don't really support multiple XS servers
in one network. That model is old, from the days when we thought we
would strongly recommend active antennas.

If you have a really large school, the model is:

 - Build a network with many APs, all connected to a "network
backbone" (one or more switches). The network backbone must connect to
eth1 on the XS.

 - Only one XS. If you have many users, just aim for a high-spec
machine for the XS role.

 - If the traffic is too much even for the high-spec machine you have
as XS , you can setup machines for specific roles -- this will need
minor changes in the config of the main XS. For example:
   - If postgresql load is significant (mainly in disk IO, memory),
the pgsql-xs process can be moved to a different machine -- just a
vanilla Fedora server running postgresql.
   - If the http proxy load is significant (disk IO, memory), the
squid process can be moved to a separate machine.
   - If the Moodle (apache/php, affecting memory and cpu) load is
significant, move it to a separate machine.

Now... the heaviest load on the XS will be Moodle (Apache / PHP /
PostgreSQL); and I have a lot of experience with large scale moodle
installs for up to 120K users, with "concurrent" use peaking at a
couple of thousand. There the answer was a small cluster of x86
mid-range servers.

The very largest schools we are targetting for OLPC deployments have
have around 3K users. At most you'll see 500~800 concurrent users(*)
and that will probably melt the network before it even gets to the

And any mid-range server of the current generation (multi-core, maybe
8GB RAM using PAE, some reasonably fast SATA disks) will handle that
and laugh in your face while it cooks some pasta for your dining

* Not concurrently connected, but requesting a page within the same 5s window.


 martin.langhoff at gmail.com
 martin at laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information of Chester Community Charter School (CCCS). If you have received this message in error, please e-mail administrator at postmaster at chestercommunitycharter.org, then delete the e-mail and destroy any printed copy. CCCS reserves the right to retain, archive, use and disclose any emails that are sent from or to this email address. Thank you.

More information about the Server-devel mailing list