[Sugar-devel] Sugar-Server enhancement
Manash Raja
mpdmanash at gmail.com
Wed Apr 13 17:14:25 EDT 2016
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.
Off topic, what steps did you take and how did you find the install?
I cloned the previous virtualbox install of XS server. The difference was
in the server ip address. Even though, I don't think it matters.
To clear a registration, Sugar only resets the backup-url field. Hence only
this field is used to differentiate between servers. Though it
also creates unique serial number and uuid and saves them along with the
server url at /home/.sugar/defualt/identifiers.
Hence it does not matter if we try to register to multiple XS or multiple
times to same XS.
Yes, idmgr should return that value once registered. This value is read by
> the olpc backup client backend to find its 'mothership' This would rpm
> would not be installed on SoaS.
Ya, idmgr returns 'succes, backupurl, backuppath, jabberserver'[1
<http://wiki.laptop.org/go/School_Identity_Manager>] out of which only
backupurl and jabberserver is stored.
I was able to register multiple times from one Sugar on Fedora23 to one XS.
And the auth-server showed multiple entries for each containing
' pk_hash, serial, nickname, pubkey and full_name ' as its fields. Among
which only the serial differed. And this makes the backup-url
unique as it has the format "<serial>@<jabberserver>:backup".
So, I guess I would update the network section for a prototype (with
schoolserver.py code in network/model.py). Each XS server profile would
have backup-url, jabberserver, serial number, and uuid.On selecting a
server, the backup-url and jabberserver will be set in the schema while
the serial number and uuid will be set in corresponding filesinside
identifiers folder.
One issue that I found was that, when sugar registers at url
http://schoolserver, the jabberserver should return the same but rather it
returns
http://schoolserver.lan
Thanks
On Thu, Apr 14, 2016 at 1:10 AM, Jerry Vonau <me at jvonau.ca> wrote:
> Manash,
>
> > On April 13, 2016 at 1:58 PM Manash Raja <mpdmanash at gmail.com> wrote:
> >
> >
> > Hello Jerry,
> >
> > Thank you for your help. It worked! As you said, the _REGISTER_URL was
> > getting overridden by what was set in network control panel.
> >
>
> Cool, glad it was that easy to fix.
>
> > I am visiting IRC chat room through http://webchat.freenode.net/ in
> > browser
> > as I am facing some troubles with clients due to my proxy enabled
> > internet
> > connection. Hence, I am not able to stay logged in into IRC for long.
> > Hence
> > apologize for the same. I am getting a Raspberry pi though to use openvpn
> > and then I can stay logged in for long :)
> >
>
> No worries.
>
> > I will document the steps I went through for the setup in virtualbox if
> > it
> > might help new developers.
> >
>
> That will help others immensely.
>
> > Okay, so registration is done. What I find in cpsection/network/model.py
> > is
> > that to clear the registration the schema org.sugarlabs backup-url is set
> > to blank in clear_registration() method.
>
> 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.
>
> > I am setting up another XS now to
> > register with.
>
> Off topic, what steps did you take and how did you find the install?
>
> > So is only the value in org.sugarlabs backup-url is specific
> > to a server?
>
> Yes, idmgr should return that value once registered. This value is read by
> the olpc backup client backend to find its 'mothership' This would rpm
> would not be installed on SoaS.
>
> > And of we can provide option to the user for the same, will it
> > solve the issue as it seems?
> >
>
> Yes, that would be the forward facing UI. The other advanced tasks would be
> to figure out a non-olpc client backend and corresponding service for the
> XSCE. Tony should have some ideas on that.
>
> Jerry
>
>
> > On Thu, Apr 14, 2016 at 12:03 AM, Jerry Vonau <me at jvonau.ca> wrote:
> >
> > > Just had a thought, SoaS might have the collaboration server already
> > > set in
> > > the control-panel -> network, this is different from XOs that have this
> > > field blank. Having that field populated would cause jabber_server to
> > > override the predefined _REGISTER_URL in
> > > src/jarabe/desktop/schoolserver.py.
> > >
> > > I would ensure that logging is enabled, collaboration server is blank,
> > > and
> > > try registration again. Should that fail the logs would be useful to
> > > have a
> > > look at.
> > >
> > > Jerry
> > >
> > >
> > >
> > > > On April 13, 2016 at 11:49 AM Jerry Vonau <me at jvonau.ca> wrote:
> > > >
> > > >
> > > > Hello Manash,
> > > >
> > > > I'll have a bunch of questions, because my crystal ball is in the
> > > > repair
> > > > shop. ;)
> > > >
> > > > > On April 13, 2016 at 10:45 AM Manash Raja <mpdmanash at gmail.com>
> > > > > wrote:
> > > > >
> > > > >
> > > > > I have installed XSCE schoolserver on CentOS running in Virtualbox.
> > > > >
> > > >
> > > > I saw your question in the chat-room, please be patient for a reply,
> > > > timezones come into play. Does this XSCE VM have one or two network
> > > > interfaces? I'm asking as iptables comes into play with 2 or more
> > > > interfaces.
> > > >
> > > > > 1. Sugar running on another Virtualbox instance can visit
> > > > > http://schoolserver from its browser, but server registration
> is
> > > > > failing
> > > > > in Sugar if I try clicking on "XO" and then "Register".
> > > >
> > > > This could be related to dns resolution with a single interface or
> > > > iptables
> > > > with 2+ interfaces.
> > > >
> > > > > 2. It seems that sugar registers at http://schoolserver:8080 .
> > > > > 3. When I visited http://schoolserver:8080, it showed me page
> > > > > not
> > > > > found
> > > > > error.
> > > > > 4. I configured XSCE server to support XO registration and
> > > > > backup
> > > > > from
> > > > > its menu.
> > > > > 5. Now when I visit http://schoolserver:8080, I see a different
> > > > > error
> > > > > "Error 501."
> > > > >
> > > > > Please help me to get sugar registered on XSCE server and how do we
> > > > > configure the XSCE server for sugar. (Any specific config files or
> > > > > ports)
> > > > >
> > > >
> > > > There really is nothing to open up, with a single interface the
> > > > server is
> > > > wide open and if there is more than one, all connections from the LAN
> > > > are
> > > > allowed with http and ssh allowed from the WAN.
> > > >
> > > > > Thanks
> > > >
> > > > Can you start with the number of network interfaces on the XSCE, and
> > > > the
> > > > and the contents of /etc/hosts from the sugar client please.
> > > >
> > > > Jerry
> > > >
> > > >
> > > > >
> > > > > Manash Pratim Das
> > > > >
> > > > > On Mon, Apr 4, 2016 at 3:31 AM, James Cameron <quozl at laptop.org>
> > > wrote:
> > > > >
> > > > > > The ticket is up to date.
> > > > > >
> > > > > > Your task would be to set up a server, e.g. XSCE,
> > > > > > http://schoolserver.org/ and then register to it; which is a UI
> > > step.
> > > > > >
> > > > > > Then set up a second server, and register to it; which is a
> > > > > > manual
> > > > > > process.
> > > > > >
> > > > > > Then design a UI and UX for either switching registration or
> > > > > > detecting
> > > > > > environment and testing server connection.
> > > > > >
> > > > > > On Sun, Apr 03, 2016 at 04:32:02PM +0530, Manash Raja wrote:
> > > > > > > Hello everyone,
> > > > > > >
> > > > > > > I was looking at this bug
> > > > > > > [1]https://bugs.sugarlabs.org/ticket/362
> > > > > > > ,
> > > > > > but I
> > > > > > > couldn't understand its status quite well. I am interested to
> > > > > > > work
> > > > > > > on
> > > > > > this
> > > > > > > enhancement as it is related to my proposed GSoC 2016 proposal
> > > > > > > and
> > > > > > > would
> > > > > > give
> > > > > > > me a head start on understanding the present Sugar-Server
> > > > > > > integration.
> > > > > > >
> > > > > > > So, I would appreciate if someone can help me to start and
> > > > > > > direct
> > > > > > > me
> > > > > > where I
> > > > > > > should focus on right now.
> > > > > > >
> > > > > > > Thanks.
> > > > > > > Regards.
> > > > > > >
> > > > > > > Manash Pratim Das (ManashRaja)
> > > > > > >
> > > > > > > References:
> > > > > > >
> > > > > > > [1] https://bugs.sugarlabs.org/ticket/362
> > > > > >
> > > > > > > _______________________________________________
> > > > > > > Sugar-devel mailing list
> > > > > > > Sugar-devel at lists.sugarlabs.org
> > > > > > > http://lists.sugarlabs.org/listinfo/sugar-devel
> > > > > >
> > > > > >
> > > > > > --
> > > > > > James Cameron
> > > > > > http://quozl.netrek.org/
> > > > > >
> > > > > _______________________________________________
> > > > > Sugar-devel mailing list
> > > > > Sugar-devel at lists.sugarlabs.org
> > > > > http://lists.sugarlabs.org/listinfo/sugar-devel
> > > > _______________________________________________
> > > > Sugar-devel mailing list
> > > > Sugar-devel at lists.sugarlabs.org
> > > > http://lists.sugarlabs.org/listinfo/sugar-devel
> > >
> > _______________________________________________
> > 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/ff076ce5/attachment-0001.html>
More information about the Sugar-devel
mailing list