Platform Team/Infrastructure - Revision history

Alsroot at 05:30, 23 September 2012

2012-09-23T05:30:32Z

← Older revision		Revision as of 01:30, 23 September 2012
Line 30:		Line 30:
	* being a universal build farm for binary-based projects.		* being a universal build farm for binary-based projects.

	It is an [[Platform Team/Open Build ~~System~~\|instance]] of [http://openbuildservice.org Open Build Service].		It is an [[Platform Team/Open Build Service\|instance]] of [http://openbuildservice.org Open Build Service].

	In many cases, obs.sugarlabs.org will be used implicitly:		In many cases, obs.sugarlabs.org will be used implicitly:

FGrose at 18:16, 2 October 2011

2011-10-02T18:16:35Z

Alsroot: /* activities.sugarlabs.org */

2011-10-02T16:52:09Z

activities.sugarlabs.org

← Older revision		Revision as of 12:52, 2 October 2011
Line 41:		Line 41:
	=== activities.sugarlabs.org ===		=== activities.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 download.sugarlabs.org.		Is the [[Activity Library]]. Once obs.sugarlabs.org is in service, the Activity Library will be (for now, it is entirely [[Development_Team/Almanac/Activity_Bundles\|.xo]] based) just a catalog of activities, all downloading will happen from download.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.		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.

FGrose: imagemap

2011-09-29T18:34:20Z

imagemap

← Older revision		Revision as of 14:34, 29 September 2011
Line 11:		Line 11:

	The entire workflow is whirling around following major services:		The entire workflow is whirling around following major services:
			<imagemap>
	[[File:Platform.png]]		File:Platform.png
			rect 8 144 192 184 [http://packages.sugarlabs.org/]
			rect 280 160 423 200 [http://obs.sugarlabs.org/]
			rect 504 200 679 240 [http://activities.sugarlabs.org/]
			rect 72 223 239 264 [http://sweets.sugarlabs.org/]
			rect 8 296 184 336 [http://download.sugarlabs.org/]
			desc none
			</imagemap>

	== Services ==		== Services ==

Alsroot: /* obs.sugarlabs.org */

2011-09-29T16:53:50Z

obs.sugarlabs.org

← Older revision		Revision as of 12:53, 29 September 2011
Line 23:		Line 23:
	* being a universal build farm for binary-based projects.		* being a universal build farm for binary-based projects.

	It is a [~~http:~~/~~/git.sugarlabs.org/0sugar/build-service patched~~] ~~version~~ of [http://openbuildservice.org Open Build Service].		It is an [[Platform Team/Open Build System\|instance]] of [http://openbuildservice.org Open Build Service].

	In many cases, obs.sugarlabs.org will be used implicitly:		In many cases, obs.sugarlabs.org will be used implicitly:

FGrose at 19:47, 14 September 2011

2011-09-14T19:47:46Z

← Older revision		Revision as of 15:47, 14 September 2011
Line 27:		Line 27:
	In many cases, obs.sugarlabs.org will be used implicitly:		In many cases, obs.sugarlabs.org will be used implicitly:
	* while uploading a new version from the {{Code\|sweets commit}} command,		* while uploading a new version from the {{Code\|sweets commit}} command,
	* while managing already released versions (and uploading new ones using Web UI) from [[Activity Library]]'s Developers Hub,		* while managing already released versions (and uploading new ones using Web UI) from [[Activity Library]]'s [http://activities.sugarlabs.org/en-US/developers Developers Hub],
	* launching will happen just by calling a sweet url.		* launching will happen just by calling a sweet url.

Alsroot: /* obs.sugarlabs.org */ it seems that would be better to be stuck to "obs.sl." instead of "bazaar.sl.o" to not interfere with Canonical's Bazaar and to expose the upstream name "OBS"

2011-09-14T18:27:31Z

obs.sugarlabs.org: it seems that would be better to be stuck to "obs.sl." instead of "bazaar.sl.o" to not interfere with Canonical's Bazaar and to expose the upstream name "OBS"

← Older revision		Revision as of 14:27, 14 September 2011
Line 17:		Line 17:

	=== obs.sugarlabs.org ===		=== obs.sugarlabs.org ===
	~~(Bazaar)~~

	The cornerstone component that's intended to be a place to consolidate all the efforts of Sugar doers regarding the sharing of code:		The cornerstone component that's intended to be a place to consolidate all the efforts of Sugar doers regarding the sharing of code:
Line 26:		Line 25:
	It is a [http://git.sugarlabs.org/0sugar/build-service patched] version of [http://openbuildservice.org Open Build Service].		It is a [http://git.sugarlabs.org/0sugar/build-service patched] version of [http://openbuildservice.org Open Build Service].

	In many cases, ~~Bazaar~~ will be used implicitly:		In many cases, obs.sugarlabs.org will be used implicitly:
	* uploading a new version ~~will be called~~ from the {{Code\|sweets commit}} command,		* while uploading a new version from the {{Code\|sweets commit}} command,
			* while managing already released versions (and uploading new ones using Web UI) from [[Activity Library]]'s Developers Hub,
	* launching will happen just by calling a sweet url.		* 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 [https://cas.sugarlabs.org/ Sugar Labs Central Login] system.		The only thing required is being registered in the [https://cas.sugarlabs.org/ Sugar Labs Central Login] system.

	=== activities.sugarlabs.org ===		=== activities.sugarlabs.org ===

Alsroot: /* activity.sugarlabs.org */

2011-09-14T18:17:17Z

activity.sugarlabs.org

← Older revision		Revision as of 14:17, 14 September 2011
Line 32:		Line 32:
	The only thing required is being registered on Bazaar. For the default http://bazaar.sugarlabs.org instance, that means being registered in the [https://cas.sugarlabs.org/ Sugar Labs Central Login] system.		The only thing required is being registered on Bazaar. For the default http://bazaar.sugarlabs.org instance, that means being registered in the [https://cas.sugarlabs.org/ Sugar Labs Central Login] system.

	=== ~~activity~~.sugarlabs.org ===		=== activities.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.		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 download.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.		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.

FGrose at 16:19, 14 September 2011

2011-09-14T16:19:55Z

← Older revision		Revision as of 12:19, 14 September 2011
Line 17:		Line 17:

	=== obs.sugarlabs.org ===		=== obs.sugarlabs.org ===
			(Bazaar)

	The cornerstone component that's intended to be a place to consolidate all the efforts of Sugar doers regarding sharing ~~the~~ code:		The cornerstone component that's intended to be a place to consolidate all the efforts of Sugar doers regarding the sharing of code:

	* hosting released sources (so, there is no need in requesting a shell account to upload files to http://download.sugarlabs.org),		* hosting released sources (so, there is no need in requesting a shell account to upload files to http://download.sugarlabs.org),
Line 37:		Line 38:
	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.		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.		From a usage point of view, only the 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 ===		=== packages.sugarlabs.org ===

	It is an [https://build.opensuse.org/ 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).		It is an [https://build.opensuse.org/ 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 those based on existing sweets).

	All packages on packages.sugarlabs.org split into several types:		All packages on packages.sugarlabs.org split into several types:
Line 48:		Line 49:
	* aliases that map native packages names of several GNU/Linux distributions into one OBS level name,		* aliases that map native packages names of several GNU/Linux distributions into one OBS level name,
	* sweets built only for Zero Install usage,		* sweets built only for Zero Install usage,
	* native packages built ~~basing~~ on sweets.		* native packages built based on sweets.

	=== sweets.sugarlabs.org ===		=== sweets.sugarlabs.org ===
Line 56:		Line 57:
	=== download.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.		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 the existing mirroring infrastructure.

Alsroot: /* Services */

2011-09-14T15:00:46Z

Services

← Older revision		Revision as of 11:00, 14 September 2011
Line 18:		Line 18:
	=== obs.sugarlabs.org ===		=== obs.sugarlabs.org ===

	The cornerstone component ~~and~~ intended to be a place to consolidate all the efforts of Sugar doers:		The cornerstone component that's intended to be a place to consolidate all the efforts of Sugar doers regarding sharing the code:

	* hosting released sources (so, there is no need in requesting a shell account to upload files to http://download.sugarlabs.org),		* 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,		* being a universal build farm for binary-based projects.
	* supporting QA workflows where sweet packages might be branched, tested, and released.

	It is a [http://git.sugarlabs.org/0sugar/build-service patched] version of [http://openbuildservice.org Open Build Service].		It is a [http://git.sugarlabs.org/0sugar/build-service patched] version of [http://openbuildservice.org Open Build Service].

← Older revision		Revision as of 14:16, 2 October 2011
Line 3:		Line 3:
	== Introduction ==		== Introduction ==

	Technologies involved within the Platform Team infrastructure:		Technologies involved within the Platform Team infrastructure

	* [http://0install.net Zero Install] - Decentralized cross-distribution software installation system that Sweets is based on.		* [http://0install.net Zero Install] - Decentralized cross-distribution software installation system that Sweets is based on.
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 around following major services:		The entire workflow is whirling around the following major services:
	<imagemap>		<imagemap>
	File:Platform.png		File:Platform.png
Line 34:		Line 34:
	In many cases, obs.sugarlabs.org will be used implicitly:		In many cases, obs.sugarlabs.org will be used implicitly:
	* while uploading a new version from the {{Code\|sweets commit}} command,		* while uploading a new version from the {{Code\|sweets commit}} command,
	* while managing already released versions (and uploading new ones using Web UI) from [[Activity Library]]'s [http://activities.sugarlabs.org/en-US/developers Developers Hub],		* while managing already released versions (and uploading new ones using the Web UI) from [[Activity Library]]'s [http://activities.sugarlabs.org/en-US/developers Developers Hub],
	* launching will happen just by calling a sweet ~~url~~.		* launching will happen just by calling a sweet URL.

	The only thing required is being registered in the [https://cas.sugarlabs.org/ Sugar Labs Central Login] system.		The only thing required is being registered in the [https://cas.sugarlabs.org/ Sugar Labs Central Login] system.
Line 41:		Line 41:
	=== activities.sugarlabs.org ===		=== activities.sugarlabs.org ===

	Is the [[Activity Library]]. Once obs.sugarlabs.org is in service, the Activity Library will be (for now, it is entirely [[Development_Team/Almanac/Activity_Bundles\|.xo]] based) just a catalog of activities, all downloading will happen from download.sugarlabs.org.		This is the [[Activity Library]]. Once obs.sugarlabs.org is in service, the Activity Library will be (for now, it is entirely [[Development_Team/Almanac/Activity_Bundles\|.xo]] based) just a catalog of activities, all downloading will happen from download.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.		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 the Sugar development process (where obs.sugarlabs.org is a back-end) and an analog of the current Developer Hub on Activity Library.

	From a usage point of view, only the Zero Install interface URL is needed to obtain a new Activity Library entity; the rest will be done by Sweets under the hood.		From a usage point of view, only the Zero Install interface URL is needed to obtain a new Activity Library entity; the rest will be done by Sweets under the hood.
Line 49:		Line 49:
	=== packages.sugarlabs.org ===		=== packages.sugarlabs.org ===

	It is an [https://build.opensuse.org/ 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 those based on existing sweets).		It is an [https://build.opensuse.org/ 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 a 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 those based on existing sweets).

	All packages on packages.sugarlabs.org split into several types:		All packages on packages.sugarlabs.org split into several types:
Line 60:		Line 60:
	=== sweets.sugarlabs.org ===		=== 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.		It is being used to host Zero Install feeds produced from sweet sources. After being uploaded to obs.sugarlabs.org, a sweet source will be built on OBS, and the final result will be shared as Zero Install feeds on sweets.sugarlabs.org.

	=== download.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 the existing mirroring infrastructure.		All files, sources, and binaries, that are hosted or produced on obs.sugarlabs.org, will be finally copied to download.sugarlabs.org. This allows us to reuse the existing mirroring infrastructure.