Features/Multiple schoolserver registration - Revision history

ManashRaja: /* How To Test */

2016-04-17T22:23:16Z

How To Test

← Older revision		Revision as of 18:23, 17 April 2016
Line 57:		Line 57:
	* If registration was successful, use Terminal activity for the command: ssh xsce-admin@server_address . Expected behavior: It will prompt for server password.		* 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.		* Connect to a different XSCE network and register to it as above.
	* Try doing ssh again for this XSCE. ~~Ecpected~~ behavior: It will still prompt for password, without showing identity mis-match error in case the ~~ip-address~~ of both XSCE are same.		* 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 ==

ManashRaja at 22:18, 17 April 2016

2016-04-17T22:18:04Z

← Older revision		Revision as of 18:18, 17 April 2016
Line 54:		Line 54:

	== How To Test ==		== 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. Ecpected behavior: It will still prompt for password, without showing identity mis-match error in case the ip-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]
Line 72:		Line 77:
	== 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.
	* 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

ManashRaja at 21:49, 17 April 2016

2016-04-17T21:49:40Z

← Older revision		Revision as of 17:49, 17 April 2016
Line 15:		Line 15:

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

ManashRaja at 21:27, 17 April 2016

2016-04-17T21:27:05Z

← Older revision		Revision as of 17:27, 17 April 2016
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]		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:
Line 33:		Line 33:
	**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.

ManashRaja: /* Detailed Description */

2016-04-17T21:13:22Z

Detailed Description

← Older revision		Revision as of 17:13, 17 April 2016
Line 23:		Line 23:
	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-present.png\|1000px]]<br /><br /><br />

ManashRaja at 21:09, 17 April 2016

2016-04-17T21:09:46Z

← Older revision		Revision as of 17:09, 17 April 2016
Line 7:		Line 7:

	== Summary ==		== Summary ==
	~~Easily hop between multiple XS servers.~~ Sugar will be able to register to multiple XS servers easily, without the need of clearing the registrations manually.		Sugar will be able to register to multiple school servers easily, without the need of clearing the registrations or configuring server ssh identity manually.

	== Owner ==		== Owner ==
Line 16:		Line 16:
	== Current status ==		== Current status ==
	* Targeted release: (SUGAR_VERSION)		* Targeted release: (SUGAR_VERSION)
	* Last updated: 16 April 2016		* Last updated: 18 April 2016
	* Status: Being discussed and ~~draft developed~~ [https://github.com/~~ManashRaja~~/sugar/~~commit~~/~~660985d2183416cd3ed758095e92adf82f87a10c link~~]		* Status: Being discussed in sugar-devel and [https://github.com/sugarlabs/sugar/pull/679 pull requested].
	~~<!--~~* Percentage of completion: 10%~~-->~~		* Percentage of completion: 90%

	== Detailed Description ==		== Detailed Description ==
	When a user wants to register to a new XS 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 XS 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 XS server. Hence registering multiple times with the same XS 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. ([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. (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]
	The present system for registering a Sugar laptop with an XS 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-present.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:
	**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 school server with only one click regardless of the server being new or previously registered, hence enabling quick hop between multiple servers.
			**The ssh identity for the servers where registration was successfully done will be added to ~/.ssh/known_hosts so that users (teachers) would not have to face identity errors while trying to establish ssh communication.
	**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.
Line 34:		Line 35:
	[[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 previous registration and ssh configuration 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 XSCE:/library/users) for a particular XSCE 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 XSCE 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. (This is only supported in XSCE due to the presence of xs-authserver)
	**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 school server network, specify the jabber-server address and click on "Connect to server"

	== Benefit to Sugar ==		== Benefit to Sugar ==
	This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].		This feature has emerged from a [https://bugs.sugarlabs.org/ticket/362 bug].
	The feature is supposed to bring Sugar closer to XS server and improve the user experience.		The feature is supposed to bring Sugar closer to school server and improve the user experience.

	== Scope ==		== Scope ==
	''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''		''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

	* ~~the~~ changes only affect use of Sugar with compatible school servers, such as XS or XSCE,		* The changes only affect use of Sugar with compatible school servers, such as XS or XSCE.
	* ~~use~~ of Sugar without a school server shall not be affected.		* Also no change is required on the school server side.
			* Use of Sugar without a school server shall not be affected.

	==UI Design==		==UI Design==
Line 54:		Line 56:
	{{:{{PAGENAME}}/Testing}}		{{:{{PAGENAME}}/Testing}}
	== 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]		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]

	== Dependencies ==		== Dependencies ==

ManashRaja: ManashRaja moved page Features/Multi XS-server registration to Features/Multiple schoolserver registration: Replaced XS with schoolver on title

2016-04-17T20:36:51Z

ManashRaja moved page Features/Multi XS-server registration to Features/Multiple schoolserver registration: Replaced XS with schoolver on title

← Older revision	Revision as of 16:36, 17 April 2016
(No difference)

Quozl at 23:35, 15 April 2016

2016-04-15T23:35:32Z

← Older revision		Revision as of 19:35, 15 April 2016
Line 21:		Line 21:

	== Detailed Description ==		== Detailed Description ==
	When a user wants to register to a new XS server, they to first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an XS 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 XS server. Hence registering multiple times with the same XS server leads to unnecessary change in backup path on non-XO laptops.		When a user wants to register to a new XS 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 XS 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 XS server. Hence registering multiple times with the same XS 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. ([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].

Quozl: neutral pronouns

2016-04-15T23:34:37Z

neutral pronouns

← Older revision		Revision as of 19:34, 15 April 2016
Line 21:		Line 21:

	== Detailed Description ==		== 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. 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 XS server. Hence registering multiple times with the same XS server leads to unnecessary change in backup path on non-XO laptops.		When a user wants to register to a new XS server, they to first manually clear the previous registration details (if present). Then they have to create new registration even if they are returning back to an XS 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 XS server. Hence registering multiple times with the same XS 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. ([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].
Line 49:		Line 49:

	==UI Design==		==UI Design==
	The user does not have to provide any extra input. ~~He/she has~~ to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "~~Server~~" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.		The user does not have to provide any extra input. The user is to provide the jabber server url and click on the button to register to it as before. So no change of UI is required to achieve the functionality. But as discussed in the developer mailing list ([http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052071.html link]), it has been emphasized that a new control panel section named "Servers" should be created. This section will as of now only have two user inputs "Jabber Server" and "Collaboration Server" which will be moved in from its present location of the "Network" control panel section.

	== How To Test ==		== How To Test ==

Quozl: constrain scope, only server usage affected

2016-04-15T23:31:29Z

constrain scope, only server usage affected

← Older revision		Revision as of 19:31, 15 April 2016
Line 44:		Line 44:
	== Scope ==		== Scope ==
	''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''		''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

			* the changes only affect use of Sugar with compatible school servers, such as XS or XSCE,
			* use of Sugar without a school server shall not be affected.

	==UI Design==		==UI Design==