<br><font size=2 face="sans-serif">Team,</font>
<br><font size=2 face="sans-serif">Here are my thoughts on networking.</font>
<br>
<br><font size=2 face="sans-serif">In the current School configuration:
http://wiki.laptop.org/go/XS_Configuration_Management#School_Specific_Configuration</font>
<br><font size=2 face="sans-serif">it has the XS being connected directly
to the ISP modem. All access is through the primary school server.
If it fails, all is lost.</font>
<br>
<br><font size=2 face="sans-serif">1--I suggest instead (modem)--(WiFi)--(XS)--(Mesh)</font>
<br><font size=2 face="sans-serif">A simple four-port hub could support
4 direct-connect items (an XS server, a Library server, a printer, etc.)
and over 200 Wireless.</font>
<br>
<br><font size=2 face="sans-serif">2--For normal operations, a WEP key
can prevent any XO laptop from using the Wireless directly. Instead,
they use the XS server,</font>
<br><font size=2 face="sans-serif">which has all the squid cache, library
server cache, etc. The WEP key can be provided to teachers to access
the system directly</font>
<br><font size=2 face="sans-serif">via WiFi from their laptops.</font>
<br>
<br><font size=2 face="sans-serif">3--In the even the XS is down, or the
Mesh Active Antenna is down, a teacher can turn off WEP (by accessing the
Wifi hub from their laptop), and open the WiFi up to all XO laptops. This
would also mean no content filtering, squid caching, etc.</font>
<br>
<br><font size=2 face="sans-serif">4--Alternatively, leave the WEP key
in place, and if a student needs to update an activity during the time
the XS server is down, the</font>
<br><font size=2 face="sans-serif">teacher can either download the XO file
on their behalf and send it to them via mesh, or enter the WEP key on the
student's XO for</font>
<br><font size=2 face="sans-serif">that exception. In this mode,
everyone just uses their XO and meshes with each other, but has no access
to the outside internet,</font>
<br><font size=2 face="sans-serif">moodle or the library cache.</font>
<br>
<br><font size=2 face="sans-serif">A step up from this would be:</font>
<br><font size=2 face="sans-serif">(modem)--(Wifi 1)--(XS)--(Wifi 2 + Mesh)</font>
<br>
<br><font size=2 face="sans-serif">In this environment, WiFi 1 would be
WEP-protected, teachers only. WiFi 2 would be open, and complement
the Mesh of the XS.</font>
<br><font size=2 face="sans-serif">In the event that the Mesh Active Antenna
failed, students could use WiFi2 without any significant changes. In
the event XS fails,</font>
<br><font size=2 face="sans-serif">Wifi2 could be cabled to Wifi 1, allowing
all students to access the internet, unfiltered, uncached.</font>
<br>
<br><font size=2 face="sans-serif">This approach has the advantage that
if we don't know how many XO laptops each antenna can handle, the WiFi
2 can certainly</font>
<br><font size=2 face="sans-serif">handle 200 or more IP addresses. Kind
of like an insurance policy to ensure success.</font>
<br>
<br><font size=2 face="sans-serif">Just a thought.</font>
<br><font size=2 face="sans-serif">--- Tony<br>
</font>
<table>
<tr>
<td><img src=cid:_1_081ADF14081ADB58001D9C12072573EA>
<tr>
<td><font size=1><br>
</font>
<table>
<tr>
<td><img src=cid:_2_0821873C08218380001D9C12072573EA>
<td><font size=1 color=#0060a0 face="Microsoft Sans Serif"><b>Tony Pearson</b></font><font size=1 face="Microsoft Sans Serif"><br>
Senior Storage Consultant, IBM System Storage™<br>
Telephone: +1 520-799-4309 | tie 321-4309 | Cell: +1 520 990-8669<br>
email: tpearson@us.ibm.com | GSA: http://tucgsa.ibm.com/~tpearson<br>
Blog: http://www.ibm.com/developerworks/blogs/page/InsideSystemStorage
AKA: 990tony Paravane, eightbar specialist </font></table>
<br>
<tr>
<td><img src=cid:_1_082191A808218DEC001D9C12072573EA></table>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>server-devel-request@lists.laptop.org</b>
</font>
<br><font size=1 face="sans-serif">Sent by: server-devel-bounces@lists.laptop.org</font>
<p><font size=1 face="sans-serif">02/08/2008 11:34 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
server-devel@lists.laptop.org</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">server-devel@lists.laptop.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Server-devel Digest, Vol 10, Issue 14</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Send Server-devel mailing list submissions to<br>
server-devel@lists.laptop.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
http://lists.laptop.org/listinfo/server-devel<br>
or, via email, send a message with subject or body 'help' to<br>
server-devel-request@lists.laptop.org<br>
<br>
You can reach the person managing the list at<br>
server-devel-owner@lists.laptop.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Server-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Nepal project plan and requirements (Bryan Berry)<br>
2. Re: Server-devel Digest, Vol 10, Issue 12 (Tony Pearson)<br>
3. Re: ejabberd crash (Dafydd Harries)<br>
4. Re: ejabberd crash (Robert McQueen)<br>
5. Re: ejabberd crash ( J?r?me Sautret )<br>
6. Re: ejabberd crash (Robert McQueen)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 08 Feb 2008 12:50:57 -0500<br>
From: Bryan Berry <bryan.berry@gmail.com><br>
Subject: Re: [Server-devel] Nepal project plan and requirements<br>
To: server-devel@lists.laptop.org<br>
Cc: "Greg Smith \(gregmsmi\)" <gregmsmi@cisco.com>,
sulochan
acharya<br>
<sulochan@olenepal.org><br>
Message-ID: <1202493057.6442.43.camel@dell.linuxdev.us.dell.com><br>
Content-Type: text/plain<br>
<br>
Greg and Wad, <br>
> The network is the biggest headache right now. Are you planning
to<br>
> deploy in any schools larger than 150 students ?<br>
<br>
We will have about 150-170 total laptops, which included students+teachers<br>
<br>
<br>
> After we lock down SSO strategy, what do you want to focus on next?
I<br>
> > think we should switch from design to implementation in less
than two<br>
> > weeks. Hot topics we could try to flush out include:<br>
> > - Moodle design and usage<br>
> > - Backup and reliability, including storage and network aspects<br>
<br>
The # 1 thing is backup and reliability<br>
- <br>
<br>
#2 Students need to be able to be able to "archive" their files
to the server<br>
once they run out of local space, or at least able to browse the regular<br>
backup of their files to the server. This could conceivably be done using
Moodle.<br>
<br>
#3 Moodle<br>
<br>
<br>
Localization -- We are taking care of this. Don't worry about it.<br>
<br>
Sulochan, any other thoughts?<br>
<br>
> Message: 2<br>
> Date: Fri, 8 Feb 2008 01:02:17 -0500<br>
> From: John Watlington <wad@laptop.org><br>
> Subject: Re: [Server-devel] Nepal project plan and requirements<br>
> updated<br>
> To: "Greg Smith (gregmsmi)" <gregmsmi@cisco.com><br>
> Cc: server-devel <server-devel@lists.laptop.org><br>
> Message-ID: <3D76415A-971C-46B6-86E4-406A217E4B3F@laptop.org><br>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed<br>
> <br>
> <br>
> On Feb 7, 2008, at 5:04 PM, Greg Smith (gregmsmi) wrote:<br>
> <br>
> > Hi All,<br>
> ><br>
> > The Nepal project plan and school server specification Wiki pages
have<br>
> > been updated.<br>
> > See:<br>
> > http://wiki.laptop.org/go/Nepal#Planning<br>
> ><br>
> > We need to pick the XS server image we will deploy ASAP. Teacher<br>
> > training starts April 1!<br>
> ><br>
> > Will there be another XS server image blessed by OLPC beyond<br>
> > OLPC_XS_150.iso in the next few weeks?<br>
> ><br>
> Yes. We are hoping to get one including some critical new<br>
> services (activation and update) out in the next week.<br>
> <br>
> > One open question is the status of single sign on.<br>
> ><br>
> > I see three options:<br>
> > 1 - Don't use it in phase 1<br>
> > 2 - Use one of the proposed work arounds. See Single Sign On
<br>
> > section at:<br>
> > http://wiki.laptop.org/go/ <br>
> > Nepal:School_Server_Specification#Requirements<br>
> > _Not_Specific_to_a_Core_Software_Module_<br>
> > 3 - Use some other OLPC developed solution. (Bitfrost?)<br>
> ><br>
> > Let me know if option 3 has a chance to make a new build or if
we <br>
> > should<br>
> > focus on the first two for now.<br>
> <br>
> Focus on one of the first two. I'm curious what you mean by
<br>
> "BitFrost", cause<br>
> the BitFrost document didn't really extend past the laptop.
The <br>
> current ID scheme<br>
> (described in earlier mail to Martin) IS the BitFrost ID scheme.
A <br>
> private/public<br>
> key pair is used to identify the student. As this is kind of
<br>
> awkward for a username,<br>
> two derivatives are in use: the laptop serial number and a hash
of <br>
> the public key.<br>
> This is probably changing somewhat in the future.<br>
> <br>
> > Any other comments on the which of the listed requirements are
<br>
> > addressed<br>
> > in which XS server build are appreciated.<br>
> ><br>
> > Also, clarifications, additions and suggestions are welcome.
I will <br>
> > try<br>
> > to improve the formatting and add detail regularly.<br>
> ><br>
> > For the Nepal team,<br>
> ><br>
> > After we lock down SSO strategy, what do you want to focus on
next? I<br>
> > think we should switch from design to implementation in less
than two<br>
> > weeks. Hot topics we could try to flush out include:<br>
> > - Moodle design and usage<br>
> > - Backup and reliability, including storage and network aspects<br>
> <br>
> The network is the biggest headache right now. Are you planning
to<br>
> deploy in any schools larger than 150 students ?<br>
> <br>
> > - Caching and filtering<br>
> <br>
> Squid is working fine, although I'm not sure the logs get deleted
as<br>
> well as rotated... Update to the testing repository (edit
/etc/ <br>
> yum.repos.olpc.d/testing<br>
> and /etc/yum.repos.olpc.d/stable) --- make sure you get xs-config
2.5-8.<br>
> Restart the httpd server, and now you should be able to start and
<br>
> stop web caching with<br>
> /etc/sysconfig/olpc-scripts/TURN_SQUID_ON and TURN_SQUID_OFF.<br>
> These persist across reboots.<br>
> <br>
> I'm working on getting Dansguardian packaged and configured.<br>
> <br>
> > - Localization<br>
> > Something else?<br>
> ><br>
> > Pick an area and we'll try to suggest and help implement a design
<br>
> > ASAP.<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Greg Smith<br>
> ><br>
> > _______________________________________________<br>
> > Server-devel mailing list<br>
> > Server-devel@lists.laptop.org<br>
> > http://lists.laptop.org/listinfo/server-devel<br>
> <br>
> <br>
> <br>
> ------------------------------<br>
> <br>
> Message: 3<br>
> Date: Fri, 8 Feb 2008 11:18:50 -0500<br>
> From: John Watlington <wad@laptop.org><br>
> Subject: Re: [Server-devel] ejabberd crash<br>
> To: "J?r?me Sautret" <jerome.sautret@process-one.net><br>
> Cc: olpc@collabora.co.uk, server-devel@lists.laptop.org,
Robert<br>
> McQueen
<robert.mcqueen@collabora.co.uk><br>
> Message-ID: <FADC65D5-F6EA-44DE-BBFD-BFCF041754E5@laptop.org><br>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
> <br>
> <br>
> We shouldn't have a ejabberd node named schoolserver1.<br>
> It might have happened as part of a recent upgrade.<br>
> <br>
> I'll look into it.<br>
> wad<br>
> <br>
> On Feb 8, 2008, at 11:01 AM, J?r?me Sautret wrote:<br>
> <br>
> > I can see that you have 2 nodes in your ejabberd cluster :<br>
> > ejabberd@schoolserver1 and ejabberd@schoolserver (the former
is<br>
> > stopped). What is this ejabberd@schoolserver node, why it is
stopped<br>
> > and where it is supposed to run ?<br>
> <br>
> <br>
> <br>
> ------------------------------<br>
> <br>
> Message: 4<br>
> Date: Fri, 8 Feb 2008 11:29:17 -0500<br>
> From: John Watlington <wad@laptop.org><br>
> Subject: Re: [Server-devel] ejabberd crash<br>
> To: "J?r?me Sautret" <jerome.sautret@process-one.net><br>
> Cc: olpc@collabora.co.uk, server-devel@lists.laptop.org,
Robert<br>
> McQueen
<robert.mcqueen@collabora.co.uk><br>
> Message-ID: <90277CD9-371A-4BD8-8EFE-4FA89E231853@laptop.org><br>
> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed<br>
> <br>
> <br>
> The init.d script grabs the node name from the hostname.<br>
> My problem is that a server many have serveral names....<br>
> <br>
> schoolserver, school always resolves to the principal server in a
<br>
> school.<br>
> schoolserver1, schoolserver2, etc... resolve to particular servers<br>
> (any of which may become the principal server).<br>
> I want the ejabberd node to be school.domainname, not<br>
> schoolserver1.domainname.<br>
> <br>
> Is there going to be a problem if I just change /etc/init.d/ejabberd
to<br>
> hardwire a node name ?<br>
> <br>
> On Feb 8, 2008, at 11:01 AM, J?r?me Sautret wrote:<br>
> <br>
> > I can see that you have 2 nodes in your ejabberd cluster :<br>
> > ejabberd@schoolserver1 and ejabberd@schoolserver (the former
is<br>
> > stopped). What is this ejabberd@schoolserver node, why it is
stopped<br>
> > and where it is supposed to run ?<br>
> <br>
> <br>
> <br>
> ------------------------------<br>
> <br>
> _______________________________________________<br>
> Server-devel mailing list<br>
> Server-devel@lists.laptop.org<br>
> http://lists.laptop.org/listinfo/server-devel<br>
> <br>
> <br>
> End of Server-devel Digest, Vol 10, Issue 13<br>
> ********************************************<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 8 Feb 2008 11:33:40 -0700<br>
From: Tony Pearson <tpearson@us.ibm.com><br>
Subject: Re: [Server-devel] Server-devel Digest, Vol 10, Issue 12<br>
To: server-devel@lists.laptop.org<br>
Message-ID:<br>
<OFE928B81B.891581FE-ON872573E9.0065E57E-072573E9.0065FA87@us.ibm.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Greg,<br>
I am glad we are making progress. Here is what I posted yesterday
to <br>
summarize my side so far.<br>
<br>
http://www.ibm.com/developerworks/blogs/page/InsideSystemStorage?entry=understanding_lamp_platform_for_web<br>
<br>
<br>
<br>
<br>
<br>
Tony Pearson<br>
Senior Storage Consultant, IBM System Storage?<br>
Telephone: +1 520-799-4309 | tie 321-4309 | Cell: +1 520 990-8669<br>
email: tpearson@us.ibm.com | GSA: http://tucgsa.ibm.com/~tpearson<br>
Blog: http://www.ibm.com/developerworks/blogs/page/InsideSystemStorage
<br>
AKA: 990tony Paravane, eightbar specialist <br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: http://lists.laptop.org/pipermail/server-devel/attachments/20080208/ce8c5729/attachment-0001.htm
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: not available<br>
Type: image/gif<br>
Size: 166 bytes<br>
Desc: not available<br>
Url : http://lists.laptop.org/pipermail/server-devel/attachments/20080208/ce8c5729/attachment-0002.gif
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: not available<br>
Type: image/jpeg<br>
Size: 3808 bytes<br>
Desc: not available<br>
Url : http://lists.laptop.org/pipermail/server-devel/attachments/20080208/ce8c5729/attachment-0001.jpeg
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: not available<br>
Type: image/gif<br>
Size: 166 bytes<br>
Desc: not available<br>
Url : http://lists.laptop.org/pipermail/server-devel/attachments/20080208/ce8c5729/attachment-0003.gif
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 8 Feb 2008 08:40:25 +0000<br>
From: Dafydd Harries <dafydd.harries@collabora.co.uk><br>
Subject: Re: [Server-devel] ejabberd crash<br>
To: John Watlington <wad@laptop.org><br>
Cc: olpc@collabora.co.uk, server-devel@lists.laptop.org,
Robert<br>
McQueen <robert.mcqueen@collabora.co.uk><br>
Message-ID: <20080208084025.GY939@localhost><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Ar 07/02/2008 am 21:26, ysgrifennodd John Watlington:<br>
> <br>
> ejabberd decided to eat its database again, on schoolserver.laptop.org<br>
> (http://dev.laptop.org/ticket/6365)<br>
> <br>
> The error (from sasl.log) is:<br>
> Error reading Mnesia database<br>
> <br>
> A number of laptops (25 or so) were registered with <br>
> schoolserver.laptop.org today.<br>
> <br>
> Any recommendations on how to recover without nuking the<br>
> database ? Any Mnesia experts out there ?<br>
<br>
Ouch. Perhaps we should back up the ejabberd data directory so that somebody<br>
can debug it later?<br>
<br>
> And a relevant question: what will telepathy do in this case ?
Will <br>
> it automatically<br>
> re-register if a laptop's jabber account is deleted ?<br>
<br>
No, but there is a patch that will do that:<br>
<br>
http://dev.laptop.org/ticket/6295<br>
<br>
-- <br>
Dafydd<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 08 Feb 2008 10:19:20 +0000<br>
From: Robert McQueen <robert.mcqueen@collabora.co.uk><br>
Subject: Re: [Server-devel] ejabberd crash<br>
To: John Watlington <wad@laptop.org><br>
Cc: olpc@collabora.co.uk, server-devel@lists.laptop.org, J?r? , me<br>
Sautret <jerome.sautret@process-one.net><br>
Message-ID: <47AC2CA8.8030401@collabora.co.uk><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Hi John,<br>
<br>
John Watlington wrote:<br>
> ejabberd decided to eat its database again, on schoolserver.laptop.org<br>
> (http://dev.laptop.org/ticket/6365)<br>
> <br>
> The error (from sasl.log) is:<br>
> Error reading Mnesia database<br>
> <br>
> A number of laptops (25 or so) were registered with<br>
> schoolserver.laptop.org today.<br>
> <br>
> Any recommendations on how to recover without nuking the<br>
> database ? Any Mnesia experts out there ?<br>
<br>
The contract between OLPC and Process One is in place to look at our<br>
ejabberd issues. I've CC'd J?r?me at P1 so he might consider having<br>
somebody look at this issue for us if there's time.<br>
<br>
J?r?me, would you or one of your staff like access to either of our<br>
servers on jabber.laptop.org (where most development laptop images<br>
connect to by default, so 100s of users), and schoolserver.laptop.org (a<br>
test school server at the OLPC office) for debugging?<br>
<br>
> And a relevant question: what will telepathy do in this case ?
Will it<br>
> automatically<br>
> re-register if a laptop's jabber account is deleted ?<br>
<br>
Currently no, as Daf says we have a patch for it in #6295. Might it be<br>
worth raising the priority of this patch for Update 1? dwmw2 said there<br>
was also a concern in Mongolia with laptops (particularly teachers)<br>
moving between identically-named but distinct servers (which is pretty<br>
broken, because it means we can never connect those servers together,<br>
but that's an issue for later I guess...).<br>
<br>
> wad<br>
<br>
Regards,<br>
Rob<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Fri, 8 Feb 2008 17:01:25 +0100<br>
From: " J?r?me Sautret " <jerome.sautret@process-one.net><br>
Subject: Re: [Server-devel] ejabberd crash<br>
To: "Robert McQueen" <robert.mcqueen@collabora.co.uk><br>
Cc: olpc@collabora.co.uk, server-devel@lists.laptop.org<br>
Message-ID:<br>
<8397da240802080801q3f53ffcfgd82e16c00db70796@mail.gmail.com><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
I can see that you have 2 nodes in your ejabberd cluster :<br>
ejabberd@schoolserver1 and ejabberd@schoolserver (the former is<br>
stopped). What is this ejabberd@schoolserver node, why it is stopped<br>
and where it is supposed to run ?<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Fri, 08 Feb 2008 16:03:31 +0000<br>
From: Robert McQueen <robert.mcqueen@collabora.co.uk><br>
Subject: Re: [Server-devel] ejabberd crash<br>
To: J?r?me Sautret <jerome.sautret@process-one.net><br>
Cc: olpc@collabora.co.uk, server-devel@lists.laptop.org<br>
Message-ID: <47AC7D53.7090209@collabora.co.uk><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
J?r?me Sautret wrote:<br>
> I can see that you have 2 nodes in your ejabberd cluster :<br>
> ejabberd@schoolserver1 and ejabberd@schoolserver (the former is<br>
> stopped). What is this ejabberd@schoolserver node, why it is stopped<br>
> and where it is supposed to run ?<br>
<br>
I'm not sure we've ever tried to make a cluster, maybe wad has... Could<br>
this result from changing the hostname of the machine?<br>
<br>
Regards,<br>
Rob<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Server-devel mailing list<br>
Server-devel@lists.laptop.org<br>
http://lists.laptop.org/listinfo/server-devel<br>
<br>
<br>
End of Server-devel Digest, Vol 10, Issue 14<br>
********************************************<br>
</font></tt>
<br>