From the deployment summary page, you can expand the VM Details status window for virtual machine-specific information. You can also expand the Execution Plan status window to view the provisioning tasks running based on the dependencies defined in the application.
About this task
Virtual machine-related information, such as node name, logical template, and cloud template in vCloud Director, vRealize Automation, or Amazon EC2, memory allocation, number of CPUs, and network connection details are available. You can also view the host name to easily identify the virtual machine in the vCloud Director or vRealize Automation deployments.
- To locate the IP addresses of virtual machines, look at the VM Details status window.
IP addresses for each virtual machine appear in the IP address column when they are assigned.
For example, in a three-tiered application that includes a load balancer node, you might find the IP address of the load balancer and give that IP address to your end users.
- Locate virtual machine-specific agent bootstrap logs in the table of virtual machines of the VM Details status window.
Agent bootstrap logs for each virtual machine are updated in the Log column. If the bootstrap process fails, the deployment is labeled Failed Deployment and the reason appears in the Task Details window.
- Expand the window and click the ellipses button (...) in the Cloud Template column to retrieve the detailed virtual machine-specific cloud template information from either vCloud Director, vRealize Automation, or Amazon EC2.
This information includes information such as disk size, CPU, memory.
- Expand the window and click the ellipses (...) in the Network Information column to retrieve the network details from either vCloud Director or Amazon EC2.
- To view the custom properties defined for each node to override properties in the vRealize Automation blueprint, click the Extra Configuration icon ().
- For a deployment in progress, click Refresh in the upper-right corner of the page to update the status.
The page refreshes in approximately 30 seconds.
- For specific task details such as start time, end time, and last updated time, expand the Execution Plan status window.
For each task, after the IP addresses are acquired and agents are bootstrapped, the components are deployed, installed, and configured. These processes occur according to the dependencies of the application shown by the arrows between the tasks in the execution plan.
- Review the status of each task.
Depending on the status of the task, an icon appears next to it.
Task has not yet begun or did not run.
Task is in progress. The status icon appears when a task successfully completes. This icon also appears to show the overall completion status of the host, agent bootstrap, and network bootstrap provisioning tasks.
Expand and view the details of each provisioning task.
Task requires reboot .
Task has failed. The status icon appears when a task fails. This icon also appears to show the overall failed status of the host, agent bootstrap, or network bootstrap provisioning task.
Expand and view the logs of one or more failed provisioning tasks.
Task is waiting for one of the dependencies to finish running
- For details about a component or action script and its properties, expand the Execution Plan status window, click the arrow icon () next to the task, and select View Component Properties.
The details listed there are the settings and definitions that the blueprint contained at the time of deployment.
- To view an action script, expand the Execution Plan status window, click the arrow icon () next to the task, and select View Action Script.
- To access the virtual machine log files, click the arrow icon () next to the task and select View Virtual Machine Logs.
- To view the property values for the script, click the arrow icon () next to the task and select View Component Properties.
- For details about updated deployments, expand the Execution Plan status window and examine the updated nodes.
For a scaled deployment, the execution plan displays the clustered nodes that were modified and the update scripts of the impacted nodes. The host, agent bootstrap, and network bootstrap provisioning tasks appear only on the scaled out node. The dependent nodes do not have any provisioning tasks.
For an update process to modify the configuration of a deployed application, the execution plan displays the update scripts of the changed and impacted nodes.
What to do next
To tear down a deployed application from the cloud, see Tear Down an Application from the Cloud.
To delete a deployment record from Application Services, see Delete an Application Deployment from Application Services.