52
edits
Changes
Jump to navigation
Jump to search
Line 15:
Line 15: − + Line 23:
Line 23: − + − + Line 33:
Line 33: − + Line 54:
Line 54: − {{:{{PAGENAME}}/Testing}}+ + + + + Line 72:
Line 76: − + − * See [[{{TALKPAGENAME}}|the discussion tab for this feature.]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->+ + +
Features/Multiple schoolserver registration (view source)
Revision as of 18:23, 17 April 2016
, 18:23, 17 April 2016→How To Test
== Current status ==
== Current status ==
* Targeted release: (SUGAR_VERSION)
* Targeted release: 0.110
* Last updated: 18 April 2016
* Last updated: 18 April 2016
* Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].
* Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].
When a user wants to register to a new school server, they must first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an school server where their laptop has been registered before. For non-XO laptops, every new registration changes the random serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the school server. Hence registering multiple times with the same school server leads to unnecessary change in backup path on non-XO laptops.
When a user wants to register to a new school server, they must first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an school server where their laptop has been registered before. For non-XO laptops, every new registration changes the random serial number of the laptop and serial number is used in backup url and backup paths for that laptop in the school server. Hence registering multiple times with the same school server leads to unnecessary change in backup path on non-XO laptops.
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. (reported [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]). In most of the deployments, the server address is same. [As discussed here http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052114.html]
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. (reported [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]). In most of the deployments, the server address is same. As discussed [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052114.html here]
The present system for registering a Sugar laptop with an school server is depicted below. <br />
The present system for registering a Sugar laptop with an school server is depicted below. <br />
[[File:Sugar-server-present.png|1000px]]<br /><br /><br />
[[File:Sugar-server-present1.png|1000px]]<br /><br /><br />
This feature is aimed to enhance the Sugar-Server interaction that would include:
This feature is aimed to enhance the Sugar-Server interaction that would include:
**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: <br />
The following is the proposed flow being developed for the feature: <br />
[[File:Sugar-server-modified.png|1000px]]
[[File:Sugar-server-modified1.png|1000px]]
*The main advantages of the above flow are:
*The main advantages of the above flow are:
**Manual clear of previous registration and ssh configuration is not required.
**Manual clear of previous registration and ssh configuration is not required.
== How To Test ==
== How To Test ==
* Connect to XSCE network. Enter its server_address in the "Server" entry present in "Network" section of control panel and click "Connect to server" from the desktop.
* If registration was successful, use Terminal activity for the command: ssh xsce-admin@server_address . Expected behavior: It will prompt for server password.
* Connect to a different XSCE network and register to it as above.
* Try doing ssh again for this XSCE. Expected behavior: It will still prompt for password, without showing identity mis-match error in case the server_address of both XSCE are same.
== User Experience ==
== User Experience ==
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]
The user experience is believed to increase quite significantly as it can be judged from the problems that are being faced now in this [https://bugs.sugarlabs.org/ticket/362 bug] and [http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052076.html discussion]
== Comments and Discussion ==
== Comments and Discussion ==
* ''Link to the discussion of this feature on lists.sugarlabs.org''
Your comments are very welcome. Please discuss through the mailing list.
* First discussion on the mailing list:
http://lists.sugarlabs.org/archive/sugar-devel/2016-April/051805.html