Difference between revisions of "Deployment Platform/Internet"

From Sugar Labs
Jump to navigation Jump to search
 
(11 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
== Background ==
 
== Background ==
  
This is [[Harmonic_Distribution/Deployment|one of possible]] deployment scenarios of [[Harmonic Distribution]].
+
This is [[Deployment_Platform/Deployment|one of the possible]] deployment scenarios for [[Deployment Platform]]. This page is intended to describe procedures for end users connected to the [[#Targeting_environment|Internet]].
  
This page is intended to describe procedures for school servers and end users in the [[#Targeting_environment|Internet]] environment. Using [[#Recipes|predefined recipes]], it should be possible to fully support such deployments.
+
<big>'''Targeting environment'''</big>
  
=== Targeting environment ===
+
The standard targeting environment assumes:
 +
 
 +
* End users have reliable Internet connectivity at all times.
 +
* Server is located on the Internet and has singular access point.
 +
 
 +
== Server side ==
 +
 
 +
For now, there are the following Sugar Network servers publicly available on the Internet:
 +
 
 +
* [http://node-devel.sugarlabs.org/ node-devel.sugarlabs.org]<br>Development server that does not contain important data and is free for any experiments (administrative privileges for anonymous users);
 +
 
 +
* [http://node-testing.sugarlabs.org/ node-testing.sugarlabs.org]<br>Recent stable release with regular data import from the production server; is still free for any experiments;
 +
 
 +
* [http://node.sugarlabs.org/ node.sugarlabs.org]<br>Production server.
 +
 
 +
== Client side ==
 +
 
 +
<div id="Configuration"><big>'''Configuration'''</big></div>
 +
 
 +
Point clients to one of the existing Sugar Network servers by populating the {{Code|/etc/sweets.conf}} configuration file with the following options:
 +
 
 +
[client]
 +
api-url = ''SERVER-API-URL-HERE''
 +
 
 +
By default, clients look for the production server.
 +
 
 +
<div id="Configuration"><big>'''Run Sugar Network clients'''</big></div>
 +
 
 +
Follow the [[Sugar_Network#On_desktop|Try it]] install instructions to setup Sugar Network client.
 +
 
 +
While working, Sugar Network client logs can be found {{Code|~/.sugar/default/logs/sugar-network-client}} file. The logging verbosity level depends on the [[BugSquad/Get_Logs#Enabling_Sugar_debug_logging|global Sugar setting]].
  
The standard targeting environment assumes:
+
== Getting involved ==
  
* End users have reliable Internet connectivity all time.
+
{{:Deployment_Platform/Feedback}}
* Server is located in the Internet and has singular access point.
 
  
=== Objects ===
+
<!--
 +
=== Client updates ===
  
What kind of objects involved to the process:
+
The common part of all [[#Reference_distributions|reference implementations]] is existence of deployment package with all dependencies and configuration files. Since this scenario environment assumes Internet connection, end users might be updated using regular GNU/Linux distribution procedures.
  
* '''Server'''<br>Sugar Network server accessible via the Internet via public API url. This tutorial is using http://api-testing.network.sugarlabs.org to refer to testing Sugar Network Master launched on Sugar Labs server.
+
Include [[Platform_Team/Server_Kit/sugar-client|sugar-client]] to distribution to proceed [[Platform_Team/Server_Kit/sugar-client#Unattended_system_update|unattended system update]] on client side.
  
* '''Clients'''<br>Users connected to the Server via the Internet. In server-less environment, users restricted only to content they already downloaded from the server.
+
=== Collect usage statistics ===
  
== Recipes ==
+
If there is a need to collect [[Platform_Team/Usage_Statistics|usage statistics]] from users, include [[Platform_Team/Server_Kit/sugar-client|sugar-client]] to distribution and [[Platform_Team/Server_Kit/sugar-client#Collecting_usage_statistics|collecting usage statistics]] functionality. The same utility will be used to upload collected stats to the Server. Unfortunately, there is no yet users friendly utility to browse statistics from server side, instead, login to the Server and [[Platform_Team/Sugar_Network/Implementation#Collecting_usage_statics|analyze]] raw [http://oss.oetiker.ch/rrdtool/ RRD] files.
  
 
== Reference distributions ==
 
== Reference distributions ==
  
List of reference distributions that might be useful for this scenario:
+
List of [[Deployment_Platform/Deployment#Reference_distributions|reference distributions]] that might be useful for this scenario:
  
* [[Harmonic_Distribution/XO_reference_distribution|XO distribution]]<br>For users with XO laptop.
+
* [[Deployment_Platform/XO_reference_distribution|XO distribution]]<br>For users with XO laptop.
* [[Harmonic_Distribution/Ubuntu_desktop_reference_distribution|Ubuntu desktop distribution]]<br>For users on Ubuntu.
+
* [[Deployment_Platform/Ubuntu_desktop_reference_distribution|Ubuntu desktop distribution]]<br>For users on Ubuntu.
* [[Harmonic_Distribution/Debian_server_reference_distribution|Debian server distribution]]<br>For servers on Debian, Ubuntu or their derivates.
+
* [[Deployment_Platform/Debian_server_reference_distribution|Debian server distribution]]<br>For servers on Debian, Ubuntu or their derivates.
 +
--!>

Latest revision as of 09:50, 12 August 2013

Background

This is one of the possible deployment scenarios for Deployment Platform. This page is intended to describe procedures for end users connected to the Internet.

Targeting environment

The standard targeting environment assumes:

  • End users have reliable Internet connectivity at all times.
  • Server is located on the Internet and has singular access point.

Server side

For now, there are the following Sugar Network servers publicly available on the Internet:

  • node-devel.sugarlabs.org
    Development server that does not contain important data and is free for any experiments (administrative privileges for anonymous users);
  • node-testing.sugarlabs.org
    Recent stable release with regular data import from the production server; is still free for any experiments;

Client side

Configuration

Point clients to one of the existing Sugar Network servers by populating the /etc/sweets.conf configuration file with the following options:

[client]
api-url = SERVER-API-URL-HERE

By default, clients look for the production server.

Run Sugar Network clients

Follow the Try it install instructions to setup Sugar Network client.

While working, Sugar Network client logs can be found ~/.sugar/default/logs/sugar-network-client file. The logging verbosity level depends on the global Sugar setting.

Getting involved

  • Subscribe to the sugar-devel mailing list and email with the subject prefixed with [PLATFORM].
  • Ask your question on IRC channels, #sugar (not logged) or #sugar-newbies (logged).