<div dir="ltr"> Fri, Oct 11, 2013 at 10:04 AM, <span dir="ltr"><<a href="mailto:tkkang@nurturingasia.com" target="_blank">tkkang@nurturingasia.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Managed to install it. Nice ansible and all the goodies for server management<br>
</blockquote><div><br></div><div>An install note - sometimes the first runthrough of runansible fails for me. Not always, I think it's the vagaries of my internet and/or wifi. I simply runansible again (and again, if needed) until it finally finishes. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
How stable is the system? I am able to load the IIAB demo files (on a USB stick). It will work for a while and then crash...</blockquote><div><br></div><div>Just as on the XSCE, on the DXS we've noticed stability issues on low end 1.75 units. The 1.75's with 512MB of RAM, to be specific. In particular, yes, IIAB crashes the low end 1.75 if a few (as in 3) clients try to access IIAB content at the same time. I think folks determined it was some sort of kernel issue. But yeah, the system freezes up, is totally unresponsive even on the local console, and I have to do a "hard reboot" (as in walk over to it, press down the power button till it powers off, then power back up). I don't try to put that "crappy 1.75" up on my public URL anymore, I've found it to be entirely too unstable. However, my testing cycles can be very short and rather specific, thus sometimes I need to reflash a unit several times a day. For those testing cycles confined to my LAN, I mostly use the "crappy 1.75" because it wouldn't break my heart if it broke, unlike these units below:</div>
<div><br></div><div><u>What I have found to be very stable for XSCE and DXS</u></div><div><br></div><div>1. The XO 1.5 (got one up right now public, uptime 9 days with the full IIAB TB drive)</div></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div class="gmail_extra"><div class="gmail_quote"><div>Apparently there's almost 1GB RAM</div></div></div><div class="gmail_extra"><div class="gmail_quote"><div><div>[root@schoolserver] html >free -m</div></div></div>
</div><div class="gmail_extra"><div class="gmail_quote"><div><div> total used free shared buffers cached</div></div></div></div><div class="gmail_extra"><div class="gmail_quote"><div><div>
Mem: 936 824 112 0 60 543</div></div></div></div></blockquote><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>2. The XO 1.75 HS with the "chicklet" keyboard</div>
</div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><div class="gmail_quote"><div>Looks like this thing has 840MB RAM?</div></div></div><div class="gmail_extra"><div class="gmail_quote">
<div><div>-bash-4.2# free -m</div></div></div></div><div class="gmail_extra"><div class="gmail_quote"><div><div> total used free shared buffers cached</div></div></div></div><div class="gmail_extra">
<div class="gmail_quote"><div><div>Mem: 840 418 422 0 21 146</div></div></div></div></blockquote><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>3. The XO-4</div>
<div><br></div><div>For stability testing, I typically make the XSCE or DXS public. During "end of cycle" testing, I try to keep the install up public at least a week, if not longer. I have ejabberd users who always notice when my server goes down. Not only can I see downtime in my scrollback in Pidgin or Psi or Gajim (any chat client that handles XMPP), but my users will literally call me on my telephone to let me know if my server is down. So far with XSCE/DXS testing, I haven't gotten any phone calls. Again, the only stability issue we've run into was when I tried to run the XSCE/DXS on the "crappy" 1.75 with IIAB.</div>
<div><br></div><div>Anna</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><div class="h5"><br>
>-----Original Message-----<br>
>From: Anna [mailto:<a href="mailto:aschoolf@gmail.com">aschoolf@gmail.com</a>]<br>
>Sent: Friday, October 11, 2013 08:20 AM<br>
>To: 'xsce-devel'<br>
>Cc: 'Server Devel'<br>
>Subject: Re: [XSCE] ansible<br>
><br>
>Couple of postinstall notes:<br>
><br>
>xs-authserver has some sort of conflict with the library versions that IIAB<br>
>installs. This gets xs-authserver working (don't worry, it doesn't break<br>
>IIAB):<br>
>pip install --upgrade --force-reinstall Werkzeug Flask<br>
>systemctl restart xs-authserver<br>
><br>
>OLPC Backup needs a permissions fix in /etc/rssh.conf, so uncomment:<br>
>allowrsync<br>
>allowsftp<br>
><br>
>Here's my testing checklist. Thought I'd paste this in so y'all can see<br>
>how similar to XSCE DXS is, and also how to access DXS specific things like<br>
>Munin, Ajenti, and xs-authserver.<br>
><br>
> Item Access from Note dhcpd Client Client gets an IP address in the<br>
>172.18.x.x range dhcpd Server Check /var/lib/dhcpd/dhcpd.leases for<br>
>client leases idmgr Client Registration - Register the XO idmgr<br>
>Server Check<br>
>/library/users for the XO's Serial Number dir ejabberd Client 2<br>
>registered clients can see each other ejabberd Server `ejabberdctl<br>
>connected_users` reports the 2 registered clients ejabberd Clients Share<br>
>the chat activity and communicate httpd Client <a href="http://schoolserver" target="_blank">http://schoolserver</a> and<br>
><a href="http://schoolserver.local" target="_blank">http://schoolserver.local</a> resolves to Apache test page Moodle Client<br>
><a href="http://schoolserver.local/moodle" target="_blank">http://schoolserver.local/moodle</a> autologs in Authserver Client<br>
><a href="http://schoolserver.local:5000" target="_blank">http://schoolserver.local:5000</a> greets with the XO buddy name Squid<br>
>Server Check<br>
>/library/cache size, load webpage on client, verify size has increased<br>
>Dansguardian Client Try to look at porn? No way! IIAB Client<br>
><a href="http://schoolserver/iiab" target="_blank">http://schoolserver/iiab</a> resolves OLPC-Backup Server du -sk<br>
>/library/users/* indicates backups Stats Server A client's rrds are in<br>
>/library/sugar-stats/rrd/ Monit Server Halt services and see if they<br>
>restart Munin Client <a href="http://schoolserver/munin" target="_blank">http://schoolserver/munin</a> user:admin pass:munindxs<br>
>Ajenti Client <a href="http://schoolserver:9990" target="_blank">http://schoolserver:9990</a> user:root pass:admin Ajenti<br>
>Wondershaper Client Verify bandwidth edits via online speedtest such as<br>
><a href="http://speakeasy.net/speedtest" target="_blank">speakeasy.net/speedtest</a> Upload Activity N/A /var/www/html/upload_activity.php<br>
>is currently not present - WIP<br>
><br>
><br>
>On Thu, Oct 10, 2013 at 2:46 PM, Anish Mangal <<a href="mailto:anish@activitycentral.com">anish@activitycentral.com</a>>wrote:<br>
><br>
>> Documented in the githup repo here:<br>
>><br>
>> <a href="https://github.com/activitycentral/dxs/blob/master/docs/INSTALL.rst" target="_blank">https://github.com/activitycentral/dxs/blob/master/docs/INSTALL.rst</a><br>
>><br>
>><br>
>> On Thu, Oct 10, 2013 at 12:38 PM, Anna <<a href="mailto:aschoolf@gmail.com">aschoolf@gmail.com</a>> wrote:<br>
>><br>
>>> Some quick instructions for installing the DXS. I've only tested on a XO<br>
>>> 1.75 as the target so far.<br>
>>><br>
>>> On your target machine:<br>
>>> Flash 13.2.0-13<br>
>>> Turn off power management<br>
>>> Connect to internet<br>
>>> Get a root terminal<br>
>>><br>
>>> Install from git source:<br>
>>><br>
>>> wget<br>
>>> <a href="http://xsce.activitycentral.com/repos/xs-extra/noarch/ansible-1.3.1-0.git201309161027.fc18.noarch.rpm" target="_blank">http://xsce.activitycentral.com/repos/xs-extra/noarch/ansible-1.3.1-0.git201309161027.fc18.noarch.rpm</a><br>
>>> yum -y localinstall ansible*<br>
>>> yum -y install git<br>
>>> git clone <a href="https://github.com/activitycentral/dxs.git" target="_blank">https://github.com/activitycentral/dxs.git</a> dxs-master<br>
>>> cd dxs-master<br>
>>> git fetch -u --all<br>
>>> git checkout master<br>
>>> git pull<br>
>>> [plug in all your dongles]<br>
>>> ./runansible xo<br>
>>> reboot<br>
>>> cd dxs-master<br>
>>> ./runansible<br>
>>> reboot<br>
>>><br>
>>> Default is hostname = schoolserver.local and a one dongle install (WAN =<br>
>>> "ears" and LAN = usb ethernet dongle to AP).<br>
>>> To change that, edit dxs-master/vars/default_vars.yml accordingly before<br>
>>> doing ./runansible xo:<br>
>>><br>
>>> #Domain name<br>
>>> xsce_hostname : schoolserver<br>
>>> xsce_domain: local<br>
>>><br>
>>> #Network<br>
>>> xsce_networks:<br>
>>> wan:<br>
>>> iface: eth0<br>
>>> ip: dhcp<br>
>>> lan:<br>
>>> iface: eth1<br>
>>> ip: 172.18.96.1<br>
>>> network: 172.18.96.0<br>
>>> netmask: 255.255.224.0<br>
>>><br>
>>><br>
>>> On Thu, Oct 10, 2013 at 2:18 PM, Tim Moody <<a href="mailto:tim@timmoody.com">tim@timmoody.com</a>> wrote:<br>
>>><br>
>>>> Anna, you mentioned instructions for doing an ansible install. can<br>
>>>> you point me to them?<br>
>>>><br>
>>><br>
>>><br>
>><br>
><br>
<br>
<br>
</div></div></blockquote></div><br></div></div>