<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Nepal team - here are a few questions, suggestions and decisions needed:<br>
1 - Need to decide ASAP if we will deploy the new XS image or the<br>current one. Also, please confirm if we have two XS boxes in the school<br>or one.</blockquote><div><span style="color: rgb(0, 0, 153);">>>Yeah i think we are going to use two XS boxes in each school, for redundancy purpose as proposed by Tony and others.</span><br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>2 - I suggest that people try upgrading their XS to the latest image and<br>take notes on how its done. Even if we deploy OLPC_XS_150.iso it helps<br>
to have docs on to re-image. We want to know what Nepal or user specific<br>content can be preserved. We may also want to upgrade modules one at a<br>time. Does anyone know of docs or best practices on upgrading whole<br>
boxes or by components for LAMP servers?</blockquote><div><span style="color: rgb(0, 0, 153);">>>The latest stable built is 150, and yeah we can update modules through yum.</span> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>3 - Need closure on SSO. Pending Martin's comments on the applicability<br>of the existing paradigm, you should pick a solution. Sounds like John W<br>suggests no user tracking or possibly one of the work arounds.<br>
See item 3 at this link for proposed workarounds:<br>If it's a workaround we better clarify which right away.</blockquote><div><span style="color: rgb(0, 0, 153);">>>I dont see SSO working anytime soon. It would be great to have it, because it would solve quite a few auth problems. If Ivan can make it work great, but we should not depend on it at least fot the test phase.</span> <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>4 - Based on SSO decision you need to confirm what kind of Moodle<br>interface and services will be in phase 1. My main question is if we<br>
will use Moodle to access activities.</blockquote><div><span style="color: rgb(0, 0, 153);">>>Needs testing. Will update later. </span><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>5 - On the school network. Can you confirm if we can get 2 x router +<br>wireless Access points per XS? We need to flush out the failure cases<br>and the available HW will have a big effect on that. Let us know what HW<br>
is in place. If ts just a matter of buying a few Linksys routers, I<br>think we can find a way to do that.</blockquote><div><span style="color: rgb(0, 0, 153);">>> The network structure might be a little different. Please take a look at the attached file and let me know what you guys think. </span><br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br></blockquote></div><span style="color: rgb(0, 0, 153);">>>Moodle does not handle IP based authentication. <br>
<br>>>I am attaching a file that shows cache and xs structure for the pilot. I think its a good idea to run proxy and content on different machines. On a long run it becomes more efficient to do it like that. It also reduces content handling and traffic processing on the XS. What do you guys think?<br>
</span>