[Server-devel] Nepal project plan and requirements

[Bryan Berry]

Greg and Wad, 
> The network is the biggest headache right now.  Are you planning to
> deploy in any schools larger than 150 students ?

We will have about 150-170 total laptops, which included students+teachers


> After we lock down SSO strategy, what do you want to focus on next? I
> > think we should switch from design to implementation in less than two
> > weeks. Hot topics we could try to flush out include:
> > - Moodle design and usage
> > - Backup and reliability, including storage and network aspects

The # 1 thing is backup and reliability
- 

#2 Students need to be able to be able to "archive" their files to the server
once they run out of local space, or at least able to browse the regular
backup of their files to the server. This could conceivably be done using Moodle.

#3 Moodle


Localization -- We are taking care of this. Don't worry about it.

Sulochan, any other thoughts?

> Message: 2
> Date: Fri, 8 Feb 2008 01:02:17 -0500
> From: John Watlington <wad at laptop.org>
> Subject: Re: [Server-devel] Nepal project plan and requirements
> 	updated
> To: "Greg Smith (gregmsmi)" <gregmsmi at cisco.com>
> Cc: server-devel <server-devel at lists.laptop.org>
> Message-ID: <3D76415A-971C-46B6-86E4-406A217E4B3F at laptop.org>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
> 
> 
> On Feb 7, 2008, at 5:04 PM, Greg Smith (gregmsmi) wrote:
> 
> > Hi All,
> >
> > The Nepal project plan and school server specification Wiki pages have
> > been updated.
> > See:
> > http://wiki.laptop.org/go/Nepal#Planning
> >
> > We need to pick the XS server image we will deploy ASAP. Teacher
> > training starts April 1!
> >
> > Will there be another XS server image blessed by OLPC beyond
> > OLPC_XS_150.iso in the next few weeks?
> >
> Yes.  We are hoping to get one including some critical new
> services (activation and update) out in the next week.
> 
> > One open question is the status of single sign on.
> >
> > I see three options:
> > 1 - Don't use it in phase 1
> > 2 - Use one of the proposed work arounds. See Single Sign On  
> > section at:
> > http://wiki.laptop.org/go/ 
> > Nepal:School_Server_Specification#Requirements
> > _Not_Specific_to_a_Core_Software_Module_
> > 3 - Use some other OLPC developed solution. (Bitfrost?)
> >
> > Let me know if option 3 has a chance to make a new build or if we  
> > should
> > focus on the first two for now.
> 
> Focus on one of the first two.   I'm curious what you mean by  
> "BitFrost", cause
> the BitFrost document didn't really extend past the laptop.   The  
> current ID scheme
> (described in earlier mail to Martin) IS the BitFrost ID scheme.   A  
> private/public
> key pair is used to identify the student.   As this is kind of  
> awkward for a username,
> two derivatives are in use:  the laptop serial number and a hash of  
> the public key.
> This is probably changing somewhat in the future.
> 
> > Any other comments on the which of the listed requirements are  
> > addressed
> > in which XS server build are appreciated.
> >
> > Also, clarifications, additions and suggestions are welcome. I will  
> > try
> > to improve the formatting and add detail regularly.
> >
> > For the Nepal team,
> >
> > After we lock down SSO strategy, what do you want to focus on next? I
> > think we should switch from design to implementation in less than two
> > weeks. Hot topics we could try to flush out include:
> > - Moodle design and usage
> > - Backup and reliability, including storage and network aspects
> 
> The network is the biggest headache right now.  Are you planning to
> deploy in any schools larger than 150 students ?
> 
> > - Caching and filtering
> 
> Squid is working fine, although I'm not sure the logs get deleted as
> well as rotated...    Update to the testing repository (edit /etc/ 
> yum.repos.olpc.d/testing
> and /etc/yum.repos.olpc.d/stable) --- make sure you get xs-config 2.5-8.
> Restart the httpd server, and now you should be able to start and  
> stop web caching with
> /etc/sysconfig/olpc-scripts/TURN_SQUID_ON and TURN_SQUID_OFF.
> These persist across reboots.
> 
> I'm working on getting Dansguardian packaged and configured.
> 
> > - Localization
> > Something else?
> >
> > Pick an area and we'll try to suggest and help implement a design  
> > ASAP.
> >
> > Thanks,
> >
> > Greg Smith
> >
> > _______________________________________________
> > Server-devel mailing list
> > Server-devel at lists.laptop.org
> > http://lists.laptop.org/listinfo/server-devel
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Fri, 8 Feb 2008 11:18:50 -0500
> From: John Watlington <wad at laptop.org>
> Subject: Re: [Server-devel] ejabberd crash
> To: "J?r?me Sautret" <jerome.sautret at process-one.net>
> Cc: olpc at collabora.co.uk, server-devel at lists.laptop.org,	Robert
> 	McQueen <robert.mcqueen at collabora.co.uk>
> Message-ID: <FADC65D5-F6EA-44DE-BBFD-BFCF041754E5 at laptop.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> 
> We shouldn't have a ejabberd node named schoolserver1.
> It might have happened as part of a recent upgrade.
> 
> I'll look into it.
> wad
> 
> On Feb 8, 2008, at 11:01 AM, J?r?me Sautret wrote:
> 
> > I can see that you have 2 nodes in your ejabberd cluster :
> > ejabberd at schoolserver1 and ejabberd at schoolserver (the former is
> > stopped). What is this ejabberd at schoolserver node, why it is stopped
> > and where it is supposed to run ?
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Fri, 8 Feb 2008 11:29:17 -0500
> From: John Watlington <wad at laptop.org>
> Subject: Re: [Server-devel] ejabberd crash
> To: "J?r?me Sautret" <jerome.sautret at process-one.net>
> Cc: olpc at collabora.co.uk, server-devel at lists.laptop.org,	Robert
> 	McQueen <robert.mcqueen at collabora.co.uk>
> Message-ID: <90277CD9-371A-4BD8-8EFE-4FA89E231853 at laptop.org>
> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
> 
> 
> The init.d script grabs the node name from the hostname.
> My problem is that a server many have serveral names....
> 
> schoolserver, school always resolves to the principal server in a  
> school.
> schoolserver1, schoolserver2, etc... resolve to particular servers
> (any of which may become the principal server).
> I want the ejabberd node to be school.domainname, not
> schoolserver1.domainname.
> 
> Is there going to be a problem if I just change /etc/init.d/ejabberd to
> hardwire a node name ?
> 
> On Feb 8, 2008, at 11:01 AM, J?r?me Sautret wrote:
> 
> > I can see that you have 2 nodes in your ejabberd cluster :
> > ejabberd at schoolserver1 and ejabberd at schoolserver (the former is
> > stopped). What is this ejabberd at schoolserver node, why it is stopped
> > and where it is supposed to run ?
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Server-devel mailing list
> Server-devel at lists.laptop.org
> http://lists.laptop.org/listinfo/server-devel
> 
> 
> End of Server-devel Digest, Vol 10, Issue 13
> ********************************************