Mistral/Blueprints/PoC - Revision history

Rakhmerov: /* Demo App */

2013-11-28T07:08:27Z

‎Demo App

Rakhmerov: /* Demo App */

2013-11-28T07:07:22Z

‎Demo App

Rakhmerov: /* Design */

2013-11-28T06:26:17Z

‎Design

Rakhmerov: /* Workflow Execution */

2013-11-28T06:20:11Z

‎Workflow Execution

Rakhmerov: /* Design */

2013-11-28T06:13:43Z

‎Design

Rakhmerov: /* Design */

2013-11-28T05:55:16Z

‎Design

Rakhmerov: /* Design */

2013-11-28T05:09:44Z

‎Design

Rakhmerov at 04:53, 28 November 2013

2013-11-28T04:53:29Z

Rakhmerov at 04:50, 28 November 2013

2013-11-28T04:50:02Z

Rakhmerov: /* Mistral Proof of Concept */

2013-11-18T07:57:35Z

‎Mistral Proof of Concept

@@ Line 77: / Line 77: @@
 And can be uploaded to Mistral using the following HTTP requests:
 POST /workbooks/
+{
      "name" : "demo_workbook",
@@ Line 86: / Line 86: @@
 </pre>
 PUT /workbooks/demo_workbook/definition
 [YAML definition described above]
 ==== DSL Parser ====

← Older revision		Revision as of 07:07, 28 November 2013
Line 32:		Line 32:

	Demo App is an application written to demonstrate Mistral PoC capabilities. It will be publishing a workflow into Mistral and have Mistral run it at a certain time (on-demand and on-schedule). Some of the workflow actions may be handled by the application itself (via exposing HTTP endpoints).		Demo App is an application written to demonstrate Mistral PoC capabilities. It will be publishing a workflow into Mistral and have Mistral run it at a certain time (on-demand and on-schedule). Some of the workflow actions may be handled by the application itself (via exposing HTTP endpoints).
		+
		+	The demo workbook definition may look like:
		+
		+	<pre>
		+	Service:
		+	name: Nova
		+	type: OPENSTACK_SERVICE
		+	parameters:
		+	baseUrl:
		+	actions:
		+	create-vm:
		+	parameters:
		+	url: servers
		+	method: POST
		+	task-parameters:
		+	flavor_id:
		+	optional: false
		+	image_id:
		+	optional: false
		+	delete-vm:
		+	.....
		+	Workflow:
		+	tasks:
		+	create-vms:
		+	action: Nova:create-vm
		+	parameters:
		+	image_id: 1234
		+	flavor_id: 42
		+	attache-volumes:
		+	.....
		+	backup-vms:
		+	action:Nova:create-backup
		+	parameters:
		+	....
		+	dependsOn: [detach-volume]
		+	events:
		+	backup-vm:
		+	type: periodic
		+	tasks: backup-vms
		+	parameters:
		+	cron-pattern:1 0 * * *
		+	</pre>
		+
		+	And can be uploaded to Mistral using the following HTTP requests:
		+
		+	POST /workbooks/
		+
		+	<pre>
		+	{
		+	"name" : "demo_workbook",
		+	"description" : "A workbook containing a demo workflow definition for Mistral PoC"
		+	}
		+	</pre>
		+
		+	PUT /workbooks/demo_workbook/definition
		+	[YAML definition described above]

	==== DSL Parser ====		==== DSL Parser ====

← Older revision		Revision as of 06:26, 28 November 2013
Line 44:		Line 44:

	The core component of Mistral. It takes commands from other components to run workflows (given a workbook name and a target task) assuming that all necessary objects are stored in DB. When running a workflow Workflow Execution creates one Execution object (see API spec) and multiple Task objects that hold state of corresponding tasks. Execution and Task objects are exposed via REST API.		The core component of Mistral. It takes commands from other components to run workflows (given a workbook name and a target task) assuming that all necessary objects are stored in DB. When running a workflow Workflow Execution creates one Execution object (see API spec) and multiple Task objects that hold state of corresponding tasks. Execution and Task objects are exposed via REST API.
		+
		+	==== DB ====
		+
		+	A storage for Mistral objects like workbooks, tasks, executions, events, actions. For PoC the suggested storage is MySQL. However, moving forward we may want to use something like MongoDB that could be the better fit for storing workbook definitions (DSL). That way, we wouldn't need to create all the objects as relational model and could just keep everything in Mongo and select required objects right from definitions written in Mistral DSL. Currently, we'd like to avoid a dependency like MongoDB to simplify installation and make the project more understandable for most developers.

← Older revision		Revision as of 06:20, 28 November 2013
Line 43:		Line 43:
	==== Workflow Execution ====		==== Workflow Execution ====

−	The core component of Mistral. It takes commands from other components to run workflows (given a workbook name and a target task) assuming that all necessary objects are stored in DB.	+	The core component of Mistral. It takes commands from other components to run workflows (given a workbook name and a target task) assuming that all necessary objects are stored in DB. When running a workflow Workflow Execution creates one Execution object (see API spec) and multiple Task objects that hold state of corresponding tasks. Execution and Task objects are exposed via REST API.

@@ Line 26: / Line 26: @@
 ==== Mistral Python Client ====
 ==== Demo App ====
 ==== Event Scheduler ====
-==== DSL Parser ====
+This is the component responsible for executing workflows at a right time. Strictly speaking, it's not supposed to execute workflows itself, it should tell Workflow Execution to do that. Event Scheduler only reads necessary information about events from a workbook (DSL) and maintains the queue of upcoming events.
 ==== Workflow Execution ====

← Older revision		Revision as of 05:55, 28 November 2013
Line 21:		Line 21:
	==== Mistral REST API ====		==== Mistral REST API ====

		+	Mistral API server built with Pecan/WSME. Here's the etherpad that describes the suggested API: https://etherpad.openstack.org/p/MistralAPISpecification
		+
		+	The main capability of the API server is to provide actions for uploading workbooks (description of tasks, actions etc. written in Mistral DSL) and running workflows.

	==== Mistral Python Client ====		==== Mistral Python Client ====

@@ Line 15: / Line 15: @@
 === Design ===
-[[File:Mistral PoC Architecture.png|700x500px|thumbnail|left|Mistral PoC Architecture]]
+[[File:Mistral PoC Architecture.png|700x500px|thumbnail|center|Picture 1. Mistral PoC Architecture]]
 ==== Mistral REST API ====
 ==== Mistral Python Client ====
-==== Workflow Execution ====
+==== Demo App ====
 ==== Event Scheduler ====

← Older revision		Revision as of 04:53, 28 November 2013
Line 15:		Line 15:

	=== Design ===		=== Design ===
−	[[File:Mistral PoC Architecture.png\|~~800x600px~~\|thumbnail\|left\|Mistral PoC Architecture]]	+	[[File:Mistral PoC Architecture.png\|700x500px\|thumbnail\|left\|Mistral PoC Architecture]]
		+
		+	==== Mistral REST API ====
		+
		+	==== Mistral Python Client ====
		+
		+	==== Workflow Execution ====
		+
		+	==== Event Scheduler ====

← Older revision		Revision as of 04:50, 28 November 2013
Line 13:		Line 13:
	* REST API for uploading task graphs and executing workflows		* REST API for uploading task graphs and executing workflows
	* Necessary test suite to validate the above functionality		* Necessary test suite to validate the above functionality
		+
		+	=== Design ===
		+	[[File:Mistral PoC Architecture.png\|800x600px\|thumbnail\|left\|Mistral PoC Architecture]]

@@ Line 1: / Line 1: @@
 == 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.
 * 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