Difference between revisions of "Features/Sugar Update Control ASLO"

From Sugar Labs
Jump to: navigation, search
(Current status)
Line 63: Line 63:
== Scope ==
== Scope ==
Technically the scope is limited.  Most of the changes are inside sugar-update-control or are in ASLO.
Technically the scope is limited.  Most of the changes are inside the control panel extension or in ASLO.
There will not be external api changes.
There will not be external api changes.
Line 71: Line 71:
=== Implementation ===
=== Implementation ===
* [http://git.sugarlabs.org/projects/sugar/repos/updater Updater component for control panel]
* [http://git.sugarlabs.org/projects/sugar/repos/mainline/trees/master/extensions/cpsection/updater Updater component for control panel]
== How To Test ==
== How To Test ==

Revision as of 04:33, 15 August 2009


Modify the existing Sugar Update Control to pull from activities.sugarlabs.org


Current status

  • Targeted release: .86
  • Last updated: 15 August 2009
  • Percentage of completion: 100%



Detailed Description

Update enables users to update their installed activities from the Activities Library at activities.sugarlabs.org. Activities.sugarlabs.org is base on the well established addons.mozilla.org.

Using ASLO the client can request information about updated by sending a url of the form


ASLO responds by returning XML of the form

<?xml version="1.0" encoding="UTF-8"?>
<RDF:RDF xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:em="http://www.mozilla.org/2004/em-rdf#"><RDF:Description about="urn:mozilla:extension:org.laptop.WebActivity">
           <RDF:li resource="urn:mozilla:extension:org.laptop.WebActivity:102"/>
<RDF:Description about="urn:mozilla:extension:org.laptop.WebActivity:102">

Benefit to Sugar

1. This benefits Sugar by moving the entire activities infrastructure to activities.sugarlabs.org rather than being spread across a wiki and aslo.

2. It reduces activity developer work load by using the established activites.sugarlabs.org upload process to update activities.

3. It reduces and isolates infrastructure load between wiki, activities.sl.o, and download system.

a. ASLO provides all necessary update information in a single network transaction.
b. ASLO is backed by memcache, so standard update pings are very cheap.
c. ASLO can be configured to store and serve downloads from download-farm to ease scaling issues.


Technically the scope is limited. Most of the changes are inside the control panel extension or in ASLO.

There will not be external api changes.

Over the last several months, ASLO has been improving and proving it's reliability. Many activities are being served via ASLO as their information is marked deprecated on wiki.laptop.org. Shifting update to point to also will require clear communication to end users and developers.


How To Test

Click on M Settings -> Software update.

Visually verify the "From Version XXX to XXX" is correct for your system.

NOTE: the updater currently reports information on all activities, not just the ones with valid updates. This is for debug purposes.

User Experience

Nothing should change from user point of view.



Contingency Plan

None necessary, revert to previous release behaviour.



Release Notes

As of Sugar .86, upload will default to activities.sugarlabs.org

Comments and Discussion