Views
Release Infrastructure/BOSS
From MeeGo wiki
< Release Infrastructure(Difference between revisions)
m (→Requirements) |
Informatiq (Talk | contribs) (→BOSS Implementation and Design) |
||
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
| - | + | = BOSS "Build Orchestration Supervision System" = | |
BOSS is a workflow orchestrator, a system that can be configured to automate your workflow requirements; it interacts with the OBS and with people and systems around it to apply your workflow steps. | BOSS is a workflow orchestrator, a system that can be configured to automate your workflow requirements; it interacts with the OBS and with people and systems around it to apply your workflow steps. | ||
| - | MeeGo | + | MeeGo and the MeeGo Community Edition use BOSS to automate processes and to orchestrate a CI (Continuous Integration) ecosystem around OBS. |
| + | |||
| + | See also: | ||
| + | * [[/Installation|Installation]] | ||
| + | * [[/Roadmap|Roadmap]] | ||
| + | |||
| + | == Overview == | ||
[[File:Boss0.png]] | [[File:Boss0.png]] | ||
| - | + | == Why == | |
* we need a robust, flexible way of configuring a set of triggers (ex. OBS event or a submit request) and responses | * we need a robust, flexible way of configuring a set of triggers (ex. OBS event or a submit request) and responses | ||
* OBS is a build system, not a general workflow system | * OBS is a build system, not a general workflow system | ||
| Line 14: | Line 20: | ||
* Hermes is there, but it is just taking care of notifications | * Hermes is there, but it is just taking care of notifications | ||
| - | + | == Requirements == | |
* parallel workflows for parallel software programmes | * parallel workflows for parallel software programmes | ||
* allows for parallel implementation of the system | * allows for parallel implementation of the system | ||
| Line 20: | Line 26: | ||
* take away the productization process/logic from the build infrastructure | * take away the productization process/logic from the build infrastructure | ||
| - | + | == BOSS Implementation and Design == | |
| - | There is a page describing the details of the [[/Design|design]] | + | There is a page describing the details of the [[/Design|design]] |
* a workflow framework allowing site-specific workflow definition | * a workflow framework allowing site-specific workflow definition | ||
| Line 27: | Line 33: | ||
* a queue-based job distribution system that handles delivery to pools of workers | * a queue-based job distribution system that handles delivery to pools of workers | ||
| - | + | = Resources = | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
* AMQP: [http://www.amqp.org AMQP.org] has the very readable [http://www.amqp.org/confluence/download/attachments/720900/amqp0-9-1.pdf?version=1&modificationDate=1227526523000 0.9.1 specification (pdf)] | * AMQP: [http://www.amqp.org AMQP.org] has the very readable [http://www.amqp.org/confluence/download/attachments/720900/amqp0-9-1.pdf?version=1&modificationDate=1227526523000 0.9.1 specification (pdf)] | ||
* Ruote: [http://wiki.github.com/jmettraux/ruote/overview An overview of Ruote] | * Ruote: [http://wiki.github.com/jmettraux/ruote/overview An overview of Ruote] | ||
* [[/Performance/Results|Performance tests]] | * [[/Performance/Results|Performance tests]] | ||
Latest revision as of 11:19, 3 August 2011
Contents |
BOSS "Build Orchestration Supervision System"
BOSS is a workflow orchestrator, a system that can be configured to automate your workflow requirements; it interacts with the OBS and with people and systems around it to apply your workflow steps.
MeeGo and the MeeGo Community Edition use BOSS to automate processes and to orchestrate a CI (Continuous Integration) ecosystem around OBS.
See also:
Overview
Why
- we need a robust, flexible way of configuring a set of triggers (ex. OBS event or a submit request) and responses
- OBS is a build system, not a general workflow system
- there is need for automation of responses to OBS actions results
- OBS requests are good but not flexible nor extensible
- there's fear of OBS becoming a big black box doing all the magic (maintainability)
- Hermes is there, but it is just taking care of notifications
Requirements
- parallel workflows for parallel software programmes
- allows for parallel implementation of the system
- plugins are usable independently
- take away the productization process/logic from the build infrastructure
BOSS Implementation and Design
There is a page describing the details of the design
- a workflow framework allowing site-specific workflow definition
- a message bus and queue-manager to handle delivery of incoming messages from all existing systems to the worklow framework
- a queue-based job distribution system that handles delivery to pools of workers
Resources
- AMQP: AMQP.org has the very readable 0.9.1 specification (pdf)
- Ruote: An overview of Ruote
- Performance tests