Features/Multiple schoolserver registration: Difference between revisions

(3 intermediate revisions by the same user not shown)

Line 15:

== Current status ==

* Targeted release: ~~(SUGAR_VERSION)~~

* Targeted release: 0.110

* Last updated: 18 April 2016

* Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].

Line 25:

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.

[[File:Sugar-server-~~present~~.png|1000px]]

[[File:Sugar-server-present1.png|1000px]]

This feature is aimed to enhance the Sugar-Server interaction that would include:

Line 33:

**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:

[[File:Sugar-server-~~modified~~.png|1000px]]

[[File:Sugar-server-modified1.png|1000px]]

*The main advantages of the above flow are:

**Manual clear of previous registration and ssh configuration is not required.

Line 54:

== How To Test ==

{{:~~{{PAGENAME}}/Testing}}~~

* 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 ==

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]

Line 72:

Line 76:

== 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.

* See [[{{TALKPAGENAME}}|the discussion tab for this feature.]] 

* First discussion on the mailing list:

http://lists.sugarlabs.org/archive/sugar-devel/2016-April/051805.html

@@ Line 15: / Line 15: @@
 == Current status ==
-* Targeted release: (SUGAR_VERSION)
+* Targeted release: 0.110
 * Last updated: 18 April 2016
 * Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].
@@ Line 25: / Line 25: @@
 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 />
-[[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:
@@ Line 33: / Line 33: @@
 **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 />
-[[File:Sugar-server-modified.png|1000px]]
+[[File:Sugar-server-modified1.png|1000px]]
 *The main advantages of the above flow are:
 **Manual clear of previous registration and ssh configuration is not required.
@@ Line 54: / Line 54: @@
 == How To Test ==
-{{:{{PAGENAME}}/Testing}}
+* 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 ==
 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]
@@ Line 72: / Line 76: @@
 == 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.
-* 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. -->
+* First discussion on the mailing list:
+  http://lists.sugarlabs.org/archive/sugar-devel/2016-April/051805.html