52
edits
Changes
Features/Multiple schoolserver registration (view source)
Revision as of 21:46, 14 April 2016
, 21:46, 14 April 2016→Detailed Description
In case a user wants to register to a new XS server, he/she has to first manually clear the previous registration details(if present). He/she has to create new registration even if he/she returns back to an XS server where his laptop has been registered before. Every new registration changes the serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the XS server. Hence registering multiple times with the same XS server leads to unnecessary change in backup path.
In case a user wants to register to a new XS server, he/she has to first manually clear the previous registration details(if present). He/she has to create new registration even if he/she returns back to an XS server where his laptop has been registered before. Every new registration changes the serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the XS server. Hence registering multiple times with the same XS server leads to unnecessary change in backup path.
Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. ([https://bugs.sugarlabs.org/ticket/362 one such report here])
Also from the various field reports where a user (generally a teacher) has to register to multiple XS servers on move, it becomes difficult to keep clearing the registration details manually. ([https://bugs.sugarlabs.org/ticket/362 one such report here].
The present system for registering a Sugar laptop with an XS server is depicted below.
The present system for registering a Sugar laptop with an XS server is depicted below. <br />
[[File:Sugar-server-present.png|1000px]]
[[File:Sugar-server-present.png|1000px]]<br /><br /><br />
This feature is aimed to enhance the Sugar-Server interaction that would include:
**Automated management of registration data so that a user can connect to an XS server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple XS servers.
**Automated management of registration data so that a user can connect to an XS server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple XS servers.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Creating a new control panel section named "Server" to house the server related settings and provide a reorganized place for future settings to come.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
**Retain the registration data required for ds-backup if present in the system so that it can maintain its functionality.
The following is the proposed flow being developed for the feature:
The following is the proposed flow being developed for the feature: <br />
[[File:Sugar-server-modified.png|1000px]]
[[File:Sugar-server-modified.png|1000px]]
*The main advantages of the above flow are:
*The main advantages of the above flow are:
**Manual clear of registration is not required.
**Manual clear of registration is not required.
**Each laptop will have same backup url and backup path (in XS:/library/users) for a particular XS as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XS where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups.
**Each laptop will have same backup url and backup path (in XS:/library/users) for a particular XS as it was created on first registration with the server. As registration will be done only once. The "Register" button would rather say "Connect to Server". When user connects to an XS where it has registered previously (identified by the presence of pubkey), it would simply set its serial number, uuid and backup-url with the pre-registration data. This would enable better and advanced management of backups.
*No extra input is required from the user. The user just has to connect to the XS server ssid and specify the jabber-server address as before.
**No extra input is required from the user. The user just has to connect to the XS server ssid and specify the jabber-server address as before.
== Benefit to Sugar ==
== Benefit to Sugar ==