OpenStack Mistral
Workflow service that executes graphs of tasks with transitions, retries, joins and cron triggers while tracking their state.
- Provider
- openstack
- Kind
- Workflow engine
- Category
- Compute
- Official docs
- https://docs.openstack.org/mistral/latest/
- Also known as
- Workflow service
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| compensation | boolean | — | no | false | inherited |
| cronTriggers | boolean | — | no | false | inherited |
| durable | boolean | — | no | true | inherited |
| humanReview | boolean | — | no | false | inherited |
| join | boolean | — | no | false | inherited |
| managed | boolean | — | no | false | ▸ false |
| pattern | enum | saga | tcc | two-phase-commit | dag | no | dag | ▸ dag |
| retryPolicy | boolean | — | no | false | inherited |
| stepsIdempotent | boolean | — | no | false | inherited |
| workflowType | enum | direct | reverse | no | direct | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "mistral", component: "openstack-mistral" }CloudFlowalibaba-cloudflowCloudOps Orchestration Servicealibaba-oosAmazon Augmented AI (A2I)aws-augmented-aiAmazon Managed Workflows for Apache Airflowaws-mwaaAWS Systems Manager Incident Manager and Change Manageraws-ssm-incident-and-change-managerAWS Step Functionsaws-step-functionsAmazon Simple Workflow Serviceaws-swfAzure Durable Functionsazure-durable-functionsAzure Logic Appsazure-logic-appsCloudflare Workflowscloudflare-workflowsApache AirflowairflowArgo Workflowsargo-workflowsAstronomer AstroastronomerCadencecadenceCamunda 8camundaConductorconductorDagsterdagsterDigdagdigdagFlowableflowableInngestinngestjBPMjbpmKestrakestraLuigiluigin8nn8nNode-REDnode-redPrefectprefectPrefect Cloudprefect-cloudRestaterestateTemporaltemporalTemporal Cloudtemporal-cloudTrigger.devtrigger-devWindmillwindmillWorkatoworkatoGeneric workflow engineworkflow-engineZapierzapierApplication Integrationgoogle-application-integrationCloud Composer (Managed Service for Apache Airflow)google-cloud-composerWorkflowsgoogle-cloud-workflowsOrchestration Pipelinesgoogle-orchestration-pipelinesIBM App Connectibm-app-connect
and 4 more → Workflow engine page# yaml-language-server: $schema=../../schema/component.schema.json # OpenStack Mistral: workflow service that runs a set of tasks and the relations between them, handling state, # sequencing, parallelism and synchronisation. Per "Mistral Workflow Language v2" a workflow is "direct" by # default - a graph of tasks with explicit transitions - with the reverse (dependency) type as the alternative, # and both the retry policy and join are optional, so a task neither retries nor joins unless declared. schemaVersion: "1" type: "component" id: "openstack-mistral" kind: "workflow-engine" provider: "openstack" docs: "https://docs.openstack.org/mistral/latest/" aliases: ["Workflow service"] defaults: pattern: "dag" managed: false properties: workflowType: type: "enum" values: ["direct", "reverse"] default: "direct" retryPolicy: type: "boolean" default: false join: type: "boolean" default: false cronTriggers: type: "boolean" default: false