content_image/985774.jpg
After you initiate the template deployment, the build process starts. If the build encounters any errors, they are shown in the Log File window. On successful deployment, you see a window similar to Figure 4-16. This window shows details of your deployment, including which IBM PowerVC management device manages the partition, the last state the partition was placed into by Cloud Automation Manager, the template version that was used for the deployment, and the IP address of the newly created partition. 

<img src='content_image/985774.jpg'>

After deploying the workload, you can delete the workload when it is no longer required, and power on and off the workload. 

The provisioning process for your workloads can be further extended by adding provisioners to your Terraform templates or by using Cloud Automation Managers content run times. 

A list of Terraform supported provisioners can be viewed on the Terraform website. 

Cloud Automation Manager also comes with a selection of content providers. For more information, see IBM Knowledge Center. 

## 4.4 Ansible automation and AIX 

Ansible is an open source third-party tool that you can use for configuration management and automation of repetitive tasks. Ansible is agent-less and performs actions on a set of servers from an Ansible control node. The Ansible engine needs to be installed only on the system that operates as the control node. 

Ansible communicates with your AIX based system securely by using the OpenSSH protocol. Ansible can use either password-based authentication or SSH key-based authentication. 

