Use orchestrators with provisioning
In Deploy, an orchestrator combines the steps for individual component changes into an overall deployment or provisioning workflow. Orchestrators are also responsible for deciding which parts of the deployment or provisioning plan are executed sequentially or in parallel. You can combine multiple orchestrators for more complex workflows.
Deploy supports several orchestrators for provisioning. To configure orchestrator(s), add them to the Orchestrator list on the provisioning package.
In Deploy 6.0.0 and later, provisioning-specific orchestrators are not available. The same types of orchestrators are used for both deployment and provisioning.
provisioning orchestrator
The provisioning orchestrator is the default orchestrator for provisioning. This orchestrator interleaves all individual component changes by running all steps of a given order for all components. This results in an overall workflow in which all virtual instances are created, all virtual instances are provisioned, a new environment is created, and so on.
sequential-by-provisioned orchestrator
The sequential-by-provisioned orchestrator provisions all virtual instances sequentially. For example, suppose you are provisioning an environment with Apache Tomcat and MySQL. The sequential-by-provisioned orchestrator will provision the Tomcat and MySQL provisionables sequentially as shown below.
parallel-by-provisioned orchestrator
The parallel-by-provisioned orchestrator provisions all virtual instances in parallel.
