Platform Team/Server Kit/sugar-server: Difference between revisions
No edit summary |
|||
| Line 17: | Line 17: | ||
* update native packages. | * update native packages. | ||
Interface: | |||
Service is listening {{Code|--id-port}} port on the {{Code|--host}} host to serve XML-RPC requests. There is only one RPC function: | Service is listening {{Code|--id-port}} port on the {{Code|--host}} host to serve XML-RPC requests. There is only one RPC function: | ||
| Line 42: | Line 42: | ||
Note, this backup functionality does not compatible with client tools that work with OLPC XS. The problem is that these tools construct backup url on a client side (using only server host name from backup url given after registration on a server) with relying that every client has its own system user on a server side. That doesn't work with new backup functionality where there is only one system user on a server side and authorisation happens on SSH level (using {{Code|command}} option in {{Code|~/.ssh/authorized_keys}} file). | Note, this backup functionality does not compatible with client tools that work with OLPC XS. The problem is that these tools construct backup url on a client side (using only server host name from backup url given after registration on a server) with relying that every client has its own system user on a server side. That doesn't work with new backup functionality where there is only one system user on a server side and authorisation happens on SSH level (using {{Code|command}} option in {{Code|~/.ssh/authorized_keys}} file). | ||
Interface: | |||
From {{Code|--httpd-port}} on {{Code|--host}} host, service is processing HTTP requests for url: | From {{Code|--httpd-port}} on {{Code|--host}} host, service is processing HTTP requests for url: | ||
| Line 60: | Line 60: | ||
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. | ||
Interface: | |||
Service is listening {{Code|--activation-port}} port on the {{Code|--host}} host to process TCP requests. If sent data starts from serial number, the service will reply with: | Service is listening {{Code|--activation-port}} port on the {{Code|--host}} host to process TCP requests. If sent data starts from serial number, the service will reply with: | ||
| Line 72: | Line 72: | ||
Keyring service is needed to work with activation one. It signs delegated leases for activation requests if pre-existed leases weren't found. | Keyring service is needed to work with activation one. It signs delegated leases for activation requests if pre-existed leases weren't found. | ||
Interface: | |||
There is no public interface, the service is being used internally by sugar-server. | There is no public interface, the service is being used internally by sugar-server. | ||