CloudOps Orchestration Service
Template-driven automation engine that runs ordered O&M tasks across ECS, RDS, SLB and VPC in automated, semi-automated or interactive mode.
- Provider
- alibabacloud
- Kind
- Workflow engine
- Category
- Compute
- Official docs
- https://www.alibabacloud.com/help/en/oos/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| approvalStep | boolean | — | no | false | inherited |
| compensation | boolean | — | no | false | inherited |
| durable | boolean | — | no | true | inherited |
| executionMode | enum | automated | semi-automated | interactive | no | automated | inherited |
| humanReview | boolean | — | no | false | inherited |
| managed | boolean | — | no | false | ▸ true |
| pattern | enum | saga | tcc | two-phase-commit | dag | no | dag | ▸ dag |
| stepsIdempotent | boolean | — | no | false | inherited |
| templateSource | enum | public | custom | no | — | 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: "oos", component: "alibaba-oos" }CloudFlowalibaba-cloudflowAmazon 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-connectOracle Integration 3oci-integration
and 4 more → Workflow engine page# yaml-language-server: $schema=../../schema/component.schema.json # Operation Orchestration Service, documented as CloudOps Orchestration Service (OOS): it automates O&M tasks # across Alibaba Cloud services such as ECS, RDS, SLB and VPC, with tasks, execution order, inputs and # outputs defined in a template that is then run ("What is CloudOps Orchestration Service (OOS)?"). That page # lists automated, semi-automated and interactive execution modes, names approval workflows and scheduled, # batch and cross-region operations among the scenarios, and states OOS itself is free of charge. schemaVersion: "1" type: "component" id: "alibaba-oos" kind: "workflow-engine" provider: "alibabacloud" docs: "https://www.alibabacloud.com/help/en/oos/" defaults: managed: true pattern: "dag" properties: executionMode: type: "enum" values: ["automated", "semi-automated", "interactive"] default: "automated" templateSource: type: "enum" values: ["public", "custom"] approvalStep: type: "boolean" default: false