[Sugar-devel] Sugar-Server enhancement

Tony Anderson tony_anderson at usa.net
Wed Apr 13 20:43:59 EDT 2016


Adam

The original proposal was to provide a method for an XO to be registered 
to multiple school servers simultaneously. That doesn't seem to relate 
to any
of your use cases. My concern is increasing the complexity of use by our 
students. We shouldn't force a configuration decision or action on the 
user unless absolutely necessary.

As a developer, I am moving an XO to different servers daily. The 
process requires deleting known_hosts and registering with the new 
server. Not too hard for the exceptional case of a teacher using 
multiple school servers - shouldn't justify every child in the various 
schools having to deal with the network control section.

Tony

On 04/14/2016 08:30 AM, Adam Holt wrote:
> On Wed, Apr 13, 2016 at 8:17 PM, Tony Anderson <tony_anderson at usa.net 
> <mailto:tony_anderson at usa.net>> wrote:
>
>     James
>
>     I can't think of a use case for an XO to access multiple school
>     servers.
>
>
> Apologies am not following all the details of this conversation, but 
> just to point out some of our newer work in Haiti will experiment with 
> XO laptops moving between different school servers, in off-campus 
> computer club(s), librar(ies), and at school, etc.
>
> Likewise there are definitely teachers who work in multiple schools, 
> and need to bring their main XO to each school, impressive!
>
> Also some schools campuses are just too large to tie in all the IT 
> infra together, with buildings just too far apart.  So there will be 
> several inexpensive school servers likely in these schools, who do not 
> want to network their buildings together at this point.
>
> Finally George Hunt is advising us on how to construct even more 
> mobile servers too, based on a large USB battery packs supporting 
> Raspberry Pi 3 (or XO-4 or whatever) permitting increasingly 
> ruggedized knowledge hotspots.
>
> /Not sure how we will deal with naming all these different school 
> servers coming down the pike, but definitely something to start 
> thinking about now, a great question :}/
>
>     If a school is so large (> 200 XOs), the easy solution is two
>     school servers. However, the XOs access the schoolserver based on
>     SSID and so users can be divided to their own schoolserver by the
>     connection - defining the LAN.
>
>     The OLE Nepal solution clearly satisfies the requirement to avoid
>     any unnecessary configuration option or 'onboarding' step.
>
>     The current placement of the code has been working for years.
>     Showing the server in the network section was added at a late
>     release, as I recall because the register menu item disappeared
>     after registration and so a user did not know for sure if the XO
>     was registered. This was later fixed with 'register again' so
>     putting the name in the network section is now redundant.
>
>     Tony
>
>     On 04/14/2016 07:35 AM, James Cameron wrote:
>
>         On Wed, Apr 13, 2016 at 06:13:42PM -0500, Jerry Vonau wrote:
>
>
>                 On April 13, 2016 at 5:37 PM James Cameron
>                 <quozl at laptop.org <mailto:quozl at laptop.org>> wrote:
>
>
>                 On Thu, Apr 14, 2016 at 02:44:25AM +0530, Manash Raja
>                 wrote:
>
>                     Hi Jerry,
>
>                          Please don't forget
>                     jarabe/desktop/schoolserver.py is involved, I
>                          personally would prefer that code to be moved
>                     into
>                     control-panel/network.
>                          Others please chime with your thoughts on
>                     this one.
>
>                     Yes, if register option is brought to network
>                     section, then it will
>                     provide
>                     better space for managing multiple different XS
>                     servers.
>
>                 Yes, add registration function to the network section,
>                 or move server
>                 to a new section ... but for ease of first-use where
>                 only one server
>                 is present, the register option can remain on the main
>                 menu.
>
>                 (Why do I suggest a new section?  The Network section
>                 has become
>                 cluttered with radio device controls, access point
>                 cache control,
>                 jabber server, social help, and soon proxy settings.)
>
>             Wouldn't the backup related fields be more relevant in the
>             backup section
>             of control-panel? Maybe the 'new' proxy settings could
>             have its own control
>             panel section also?
>
>         Yes, yes.
>
>
>     _______________________________________________
>     Sugar-devel mailing list
>     Sugar-devel at lists.sugarlabs.org
>     <mailto:Sugar-devel at lists.sugarlabs.org>
>     http://lists.sugarlabs.org/listinfo/sugar-devel
>
>     -- 
>     Unsung Heroes of OLPC, interviewed live @
>     <http://lists.sugarlabs.org/listinfo/sugar-devel>http://unleashkids.org
>     !
>
>
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20160414/12bc18a3/attachment.html>


More information about the Sugar-devel mailing list