[Bugs] #916 NORM: Allow SoaS to register with an XS server
SugarLabs Bugs
bugtracker-noreply at sugarlabs.org
Thu Jul 23 10:15:47 EDT 2009
#916: Allow SoaS to register with an XS server
-----------------------------+----------------------------------------------
Reporter: hamiltonchua | Owner: sdz
Type: enhancement | Status: new
Priority: Normal | Milestone: Unspecified by Release Team
Component: SoaS | Version: Unspecified
Severity: Unspecified | Resolution:
Keywords: | Distribution: Unspecified
Status_field: Unconfirmed |
-----------------------------+----------------------------------------------
Changes (by martin.langhoff):
* cc: martin.langhoff (added)
Comment:
Hamilton, thanks for the patches. There are few issues however.
- I take it the diffs and the full files are equivalent, yes?
- Why do you remove -z from the rsynz invokation?
- Why do you set -a? In my testing, this will cause trouble as we want
different mode on the XS.
- The code won't work on old Sugar. Better to make the gconf codepaths
conditional, so we have a single ds-backup that works on both.
- I agree - gconf is a bad place to store info that may be needed from
cron, have you got the new, updated patch?
- Can you make your diffs with '-u' so we get nice unified diffs? :-)
- The code in schoolserver.py that sets that SN/UUID should create them
based on random values the first time it is called, and _store_ them.
Right now you are tying the UUID to the MAC address of the machine. If
SoaS is used as designed, the user may change the actual hardware on every
run, effectively changing the MAC address. Not so good. Forget about the
physical machine -- get a random value, make SN & UUID from it, store it,
reuse it forevermore.
Put myself in CC.
~ cheers ~
--
Ticket URL: <http://dev.sugarlabs.org/ticket/916#comment:4>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list