Platform Team/Server Kit/sugar-server - Revision history

Alsroot: moved Sugar Server Kit/sugar-server to Platform Team/Server Kit/sugar-server: Move SSK to HSD

2012-03-21T09:48:42Z

← Older revision	Revision as of 05:48, 21 March 2012
(No difference)

2011-12-04T15:46:54Z

Configuration: fix link to templates

← Older revision		Revision as of 11:46, 4 December 2011
Line 219:		Line 219:
	sugar-server config		sugar-server config

	See [http://git.sugarlabs.org/server/templates/trees/master/~~etc~~/sugar-server sugar-server-templates] sources for an example.		See [http://git.sugarlabs.org/server/templates/trees/master/mace/sugar-server sugar-server-templates] sources for an example.

	== Getting involved ==		== Getting involved ==

2011-12-04T14:28:59Z

registry: fix typo

← Older revision		Revision as of 10:28, 4 December 2011
Line 84:		Line 84:
	''dict'' '''register'''(''str'' machine_sn, ''str'' nickname, ''str'' machine_uuid, ''str'' pubkey)		''dict'' '''register'''(''str'' machine_sn, ''str'' nickname, ''str'' machine_uuid, ''str'' pubkey)

	To support OLPC's XS clients, RPC function to serve registration requests. The XML-~~RPM~~ service will be listening to the {{Code\|8080}} port on the {{Code\|--host}} host.		To support OLPC's XS clients, RPC function to serve registration requests. The XML-RPC service will be listening to the {{Code\|8080}} port on the {{Code\|--host}} host.

	=== backup ===		=== backup ===

2011-12-04T14:25:51Z

Registry: fix typo

← Older revision		Revision as of 10:25, 4 December 2011
Line 21:		Line 21:
	* {{Code\|machine_sn}}, serial number of hardware Sugar user is running on, e.g., serial number of a XO laptop;		* {{Code\|machine_sn}}, serial number of hardware Sugar user is running on, e.g., serial number of a XO laptop;
	* {{Code\|machine_uuid}}, UUID value of hardware Sugar user is running on, e.g., UUID of a XO laptop;		* {{Code\|machine_uuid}}, UUID value of hardware Sugar user is running on, e.g., UUID of a XO laptop;
	* {{Code\|pubkey}}, SSH public key, this is the exact line that needs to be placed as-is to {{Code\|~/.ssh/authorized_keys}} file; note that OLPC XS operates with ~~striped~~ version of public keys.		* {{Code\|pubkey}}, SSH public key, this is the exact line that needs to be placed as-is to {{Code\|~/.ssh/authorized_keys}} file; note that OLPC XS operates with stripped version of public keys.

	== Services ==		== Services ==

2011-12-03T01:51:08Z

2011-11-30T22:19:10Z

Registry

← Older revision		Revision as of 18:19, 30 November 2011
Line 9:		Line 9:
	=== Registry ===		=== Registry ===

	During the sugar-server work, all its components have access to a registry, an analog of database to keep information about registered users or activated machines. The registry is file based, i.e., every item is being kept in one file (in JSON notation) in {{Code\|registry~~-dir~~}} directory.		During the sugar-server work, all its components have access to a registry, an analog of database to keep information about registered users or activated machines. The registry is file based, i.e., every item is being kept in one file (in JSON notation) in {{Code\|<root-option>/home/registry}} directory.

	There are two subdirectories, i.e., "tables":		There are two subdirectories, i.e., "tables":

2011-11-30T22:17:59Z

backup

← Older revision		Revision as of 18:17, 30 November 2011
Line 89:		Line 89:

	Process backup and restore for students' Journals. The service is accepting requests that clients send before starting backup process. If server accepts requests, clients start Rsync'ing Journal data via SSH. The Rsync url needs to be gotten from {{Code\|/client/status}} request and be used without any modification on the client side, i.e., the process is fully server driven.		Process backup and restore for students' Journals. The service is accepting requests that clients send before starting backup process. If server accepts requests, clients start Rsync'ing Journal data via SSH. The Rsync url needs to be gotten from {{Code\|/client/status}} request and be used without any modification on the client side, i.e., the process is fully server driven.

			Users' backups are being stored in {{Code\|<root-option>/home/backups/<UID's-last-two-chars>/<UID>}} directories.

	Interface:		Interface:

2011-11-30T22:15:51Z

activation

← Older revision		Revision as of 18:15, 30 November 2011
Line 110:		Line 110:
	=== activation ===		=== activation ===

	This service is intended to process anti-thief requests XO laptops send to the server during the boot process.		This service is intended to process anti-thief requests XO laptops send to the server during the boot process. It is looking for precreated leases using {{Code\|<root-option>/share/leases/<SN's-last-two-chars>/<SN>}} paths. If there is no existing leases and {{Code\|delegation}} option is {{Code\|True}}, it will ask the [[#keyring\|keyring]] service to generate new one using delegated leases.

	Interface:		Interface:

2011-11-18T19:02:10Z

registry

← Older revision		Revision as of 15:02, 18 November 2011
Line 68:		Line 68:
	* {{Code\|jabber-url}}, if {{Code\|registered}} is {{Code\|True}}, Jabber server url;		* {{Code\|jabber-url}}, if {{Code\|registered}} is {{Code\|True}}, Jabber server url;
	* {{Code\|backup-url}}, if {{Code\|registered}} is {{Code\|True}}, Rsync url to backup Journal to, needs to be used as-is.		* {{Code\|backup-url}}, if {{Code\|registered}} is {{Code\|True}}, Rsync url to backup Journal to, needs to be used as-is.
			* {{Code\|pending-restore}}, is there pending restore, i.e., if {{Code\|True}}, during the registration on a server, there was an existing backup; any further, after registration, backup or restore will clean up {{Code\|pending-restore}} flag.

	Requested uid might be not registered in cases like:		Requested uid might be not registered in cases like:

2011-11-13T13:26:42Z

backup

← Older revision		Revision as of 09:26, 13 November 2011
Line 87:		Line 87:
	=== backup ===		=== backup ===

	Process backup and restore for students' Journals. The service is accepting ~~RESTfull~~ requests that clients send before starting backup process. If server accepts requests, clients start Rsync'ing Journal data via SSH. The Rsync url needs to be gotten ~~while registration via Id service~~ and ~~will~~ be used without any modification on the client side, i.e., the process is fully server driven.		Process backup and restore for students' Journals. The service is accepting requests that clients send before starting backup process. If server accepts requests, clients start Rsync'ing Journal data via SSH. The Rsync url needs to be gotten from {{Code\|/client/status}} request and be used without any modification on the client side, i.e., the process is fully server driven.

	Interface:		Interface: