[Bugs] #916 NORM: Allow SoaS to register with an XS server
SugarLabs Bugs
bugtracker-noreply at sugarlabs.org
Fri Jul 24 04:39:02 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 |
-----------------------------+----------------------------------------------
Comment(by hamiltonchua):
Hello Martin,
Thanks for taking a look. Please see my responses below :
- I don't understand what you mean by the diff and full files being
equivalent. I grabbed the original python scripts and diffed them against
the modified scripts I made.
- I did not intentionally replace -a with -z. It may have been a typo on
my part.
- I am replacing the gconf stuff. In order to use the values from gconf, a
session has to be active. Because of this, the script when executed in a
cron fails to get the uuid and serial. I have decided to store the values
in files instead.
- Yes, my apologies, I will use -u next time.
- The MAC address taken from the current hardware the SoaS is plugged into
is for purposes of generating a random UUID for registering into an XS.
When it is plugged in again, the SoaS should already be registered and
there is no need to check for the MAC address again. Is there a need to
remember the random value used to generate the SN and UUID ? I think once
we have an SN and UUID we don't need that random value anymore right ?
We are now testing the changes to both schoolserver.py and ds-backup.py
where we store serial and UUID in files instead of gconf. Hope to have it
posted here soon.
Thanks again.
--
Ticket URL: <http://dev.sugarlabs.org/ticket/916#comment:5>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list