Re: [Server-devel] CCCS XS deployment
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.langh...@gmail.com] Sent: Monday, October 12, 2009 3:47 AM To: jvo...@shaw.ca Cc: Josh Totoro; server-devel@lists.laptop.org Subject: Re: [Server-devel] CCCS XS deployment On Mon, Oct 12, 2009 at 2:50 AM, Jerry Vonau jvo...@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 server. 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 pleasure. * Not concurrently connected, but requesting a page within the same 5s window. cheers, m -- martin.langh...@gmail.com mar...@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 postmas...@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. ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] CCCS XS deployment
On Tue, Oct 13, 2009 at 3:37 PM, Josh Totoro jtot...@chartersmi.com wrote: This limited the number of users per XS to 350 total and more like 100 concurrent. Why? The kids only see other kids from their own building Unless you've configured that explicitly from Moodle, that is a hint of trouble. It very likely means you are having XMPP problems. See the ejabberd troubleshooting /diagnosis in http://wiki.laptop.org/go/XS_Techniques_and_Configuration -- are the XOs using gabble? Have they connected to ejabberd correctly? our Procurve Wireless Edge Service You have a slightly different setup from what I'd call a normal XS install ;-) Thanks for the help No problem! m -- martin.langh...@gmail.com mar...@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 ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] CCCS XS deployment
On Thu, 2009-10-08 at 15:23 -0400, Josh Totoro wrote: Hey all, We currently have 350 xo’s on our network and 1 xs server running. How well does the XS fair when fully loaded? What specs? We just purchased 300 more xo’s and will purchase 300 more in a month or so. Yea, more fun for you. ;) 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? As network_config is used for the setup for the server's role, only role 1 provides internet access, and a large netblock on eth1, while role 1 assumes that you have only one nic and are using AA to contact the XO's. So we are really in uncharted waters here.. Think the easiest way would to have the wired lan on role 1 handle less of the netblock and allocate the addresses across the XS server farm in the form of a new lanbond0 file that would take into account the fact that the role other that 1 should create the needed network configuration. I'm thinking a /23 for each XS's wired nic here. Anybody running more that 500 clients off a single XS? Of course you would have to change the bind/dhcp config to match... Martin, what do you think? Should we set up all XS servers the same way and let them run individually from each other? I am worried about conflicts with using the same name schoolserver.cccs.org, should the next one be schoolserver2.cccs.org or will that prevent things like ejabberd from working. Until the above issue is addressed, that might get a bit out of hand with 2 lans sharing the same address space. Just tossing around ideas... Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] CCCS XS deployment
On Sun, 2009-10-11 at 19:50 -0500, Jerry Vonau wrote: On Thu, 2009-10-08 at 15:23 -0400, Josh Totoro wrote: snip 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? As network_config is used for the setup for the server's role, only role 1 provides internet access, and a large netblock on eth1, while role 1 assumes that you have only one nic and are using AA to contact the XO's. So we are really in uncharted waters here.. Think the easiest way would to have the wired lan on role 1 handle less of the netblock and allocate the addresses across the XS server farm in the form of a new lanbond0 file that would take into account the fact that the role other that 1 should create the needed network configuration. I'm thinking a /23 for each XS's wired nic here. Anybody running more that 500 clients off a single XS? Of course you would have to change the bind/dhcp config to match... Better plan, just make eth1,2,3 be slaves of mshbond0,1,2. on the additional XSes, No need to change the network layout, ~500 clients per nic. We just have to edit the ifcfg-ethX file and add MASTER=mshbondX SLAVE=yes. Martin, what do you think? Cleaner? Should we set up all XS servers the same way and let them run individually from each other? I am worried about conflicts with using the same name schoolserver.cccs.org, should the next one be schoolserver2.cccs.org or will that prevent things like ejabberd from working. Until the above issue is addressed, that might get a bit out of hand with 2 lans sharing the same address space. The issue now is that hostname is set to HOSTNAME=schoolserver.@@BASEDNSNAME@@ in /etc/sysconfig/network which would apply to both XS servers. The quick workaround would be to use a subdomain for each XS when you run domain_config, eg: lan1.cccs.org for the first XS, then change lan1 for the second XS. Just tossing around ideas... Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
