Difference between revisions of "Platform Team/Infrastructure"
| Line 10: | Line 10: | ||
* [https://addons.mozilla.org addons.mozilla.org (AMO)] - The source software for [[#Activity_Library|Activity Library]]. | * [https://addons.mozilla.org addons.mozilla.org (AMO)] - The source software for [[#Activity_Library|Activity Library]]. | ||
| − | The entire workflow is whirling following major services: | + | The entire workflow is whirling around following major services: |
[[File:Platform.png]] | [[File:Platform.png]] | ||
| − | == | + | == Services == |
| − | |||
| − | |||
| − | |||
| − | |||
=== obs.sugarlabs.org === | === obs.sugarlabs.org === | ||
Revision as of 09:43, 14 September 2011
This page describes the infrastructure map that the Platform Team provides. See also Sweets introduction page.
Introduction
Technologies involved within the Platform Team infrastructure:
- Zero Install - Decentralized cross-distribution software installation system that Sweets is based on.
- PackageKit - Is used as a backend for Zero Install to work with native package management systems.
- Open Build Service (OBS) - The hosting and build service.
- addons.mozilla.org (AMO) - The source software for Activity Library.
The entire workflow is whirling around following major services:
Services
obs.sugarlabs.org
The cornerstone component and intended to be a place to consolidate all the efforts of Sugar doers:
- hosting released sources (so, there is no need in requesting a shell account to upload files to http://download.sugarlabs.org),
- being a universal build farm for binary-based projects,
- supporting QA workflows where sweet packages might be branched, tested, and released.
It is a patched version of Open Build Service.
In many cases, Bazaar will be used implicitly:
- uploading a new version will be called from the
sweets commitcommand, - launching will happen just by calling a sweet url.
The only thing required is being registered on Bazaar. For the default http://bazaar.sugarlabs.org instance, that means being registered in the Sugar Labs Central Login system.
activity.sugarlabs.org
Is the Activity Library. Once obs.sugarlabs.org is in service, the Activity Library will be just a catalog of activities, all downloading will happen from obs.sugarlabs.org.
In the doers' environment, the Activity Library will be a catalog of sweets. In other words, activities.sugarlabs.org might be treated as a front-end for Sugar development process (where obs.sugarlabs.org is a back-end) and an analog of the current Developer Hub on Activity Library.
From usage point of view, only Zero Install interface URL is needed to obtain a new Activity Library entity; the rest will be done by Sweets under the hood.
packages.sugarlabs.org
It is an original Web interface to Open Build Service. It seems to be an overkill for regular Sugar doers' workflow (since OBS is primarily designed to support native packages workflow) when Activity Library's Developers Hub can be used as a more appropriate OBS client. But packages.sugarlabs.org will be useful when people need full OBS control for creating native packages (original ones or basing on existed sweets).
All packages on packages.sugarlabs.org split into several types:
- regular OBS packages,
- aliases that map native packages names of several GNU/Linux distributions into one OBS level name,
- sweets built only for Zero Install usage,
- native packages built basing on sweets.
sweets.sugarlabs.org
It is being used to host Zero Install feeds produced from sweet sources. After being uploaded to obs.sugarlabs.org, sweet source will be build on OBS and the final result will be shared also as Zero Install feeds on sweets.sugarlabs.org.
download.sugarlabs.org
All files, sources and binaries, that are hosted or produced on obs.sugarlabs.org, will be finally copied to download.sugarlabs.org. The reason is to reuse existed mirroring infrastructure.