Blueprints use workflows to perform the actions necessary to build and manage an environment.
A workflow is a series of actions that are performed in a specific order. Workflows call scripts or code, typically in plugi-ns, to build an environment to the required state. After a deployment is created from a blueprint, the workflow can be initiated. Workflows can be used to manage blueprint deployments after they have been initially deployed.
The following table describes the built-in workflows available in the Dell Telecom Infrastructure Automation Suite (Automation Suite).
Workflow name | Description | Continuous or ad-hoc |
install | Run this workflow to install applications. | Continuous |
check_status | Run this workflow to check the status of the deployment. | Ad-hoc |
uninstall | Run this workflow to uninstall applications. | Ad-hoc |
start | Run this workflow to start all, or a subset of, node templates. | Ad-hoc |
stop | Run this workflow to stop all, or a subset of, node templates. | Ad-hoc |
restart | Run this workflow to restart all, or a subset of, node templates. | Ad-hoc |
execute_operation | Run this workflow to perform arbitrary operations on nodes. | Ad-hoc |
heal | Run this workflow to heal node-instances of a deployment, or a subset of a deployment. | Ad-hoc |
scale | Run this workflow to scale in or out the subgraph of the system topology. | Ad-hoc |
install_new_agents | Run this workflow to install agents on all virtual machines (VMs) related to a deployment. | Ad-hoc |
For more information about initiating a workflow, see Initiate a workflow.