Difference between revisions of "Mistral/Blueprints/PoC"
< Mistral | Blueprints
(→Mistral Proof of Concept) |
|||
| Line 1: | Line 1: | ||
== Mistral Proof of Concept == | == Mistral Proof of Concept == | ||
| − | We need to create a small PoC project illustrating main Mistral ideas. Capabilities implemented in the scope of PoC should include: | + | We need to create a small PoC project illustrating main Mistral ideas. |
| + | |||
| + | === Etherpads === | ||
| + | * https://etherpad.openstack.org/p/TaskServiceDesign | ||
| + | * https://etherpad.openstack.org/p/MistralDesignAndDependencies | ||
| + | |||
| + | === Requirements === | ||
| + | Capabilities implemented in the scope of PoC should include: | ||
* Basic Workflow Engine capable of analyzing task graphs, resolving dependencies between tasks and processing them in the right order | * Basic Workflow Engine capable of analyzing task graphs, resolving dependencies between tasks and processing them in the right order | ||
* Simple storage (RDBMS for now) access layer to it for storing task graphs and workflow execution states | * Simple storage (RDBMS for now) access layer to it for storing task graphs and workflow execution states | ||
Revision as of 07:57, 18 November 2013
Mistral Proof of Concept
We need to create a small PoC project illustrating main Mistral ideas.
Etherpads
- https://etherpad.openstack.org/p/TaskServiceDesign
- https://etherpad.openstack.org/p/MistralDesignAndDependencies
Requirements
Capabilities implemented in the scope of PoC should include:
- Basic Workflow Engine capable of analyzing task graphs, resolving dependencies between tasks and processing them in the right order
- Simple storage (RDBMS for now) access layer to it for storing task graphs and workflow execution states
- Basic DSL for defining tasks, task dependencies, actions and action transports (currently HTTP and AMQP)
- REST API for uploading task graphs and executing workflows
- Necessary test suite to validate the above functionality
