This topic describes basic concepts of Operation Orchestration Service (OOS). These concepts can help you to understand OOS.
|Template||A YAML or JSON file that includes one or more tasks.|
|Task||The main component of a template. A task describes the details of a specific O&M action. An action is specified by a task in the template.|
|Action||A specific operation. An action is the minimum O&M unit.
Actions are divided into the following types: API actions, product actions, trigger actions, control actions, and embedding actions.
The format of an action name is
|API action||The action in which an API operation is called. It currently supports
|Cloud product action (or product action)||The action used to perform a common O&M operation on other Alibaba Cloud services. API operations for the services are encapsulated in product actions. When you create a template, you can simplify the writing of code by using encapsulated product actions. For example,
The format of a product action name is
|Trigger action (or trigger)||The action that defines a condition used to trigger the execution of a template. It currently supports ACS::TimerTrigger.|
|Control action||The action used to specify the order and method of executing tasks. For example, you can use
|Embedding action||The action used to reference another template (child template) as a task. It currently only supports
|Execution||The process of running a template.|
|Task execution||The process of running a task.|
|Loop task||The task that is iteratively executed by using input values from a list.|