6.2

Table Of Contents
4 Confirm your selection.
Note If the deployment status does not change to STOPPED in a reasonable amount of time, the
process may be hung, in which case you can force a hard stop by clicking Stop again. Clicking Stop
a second time forces the deployment to stop immediately without completing the normal sequence of
events employed by the stop process. You are prompted to confirm this action by clicking OK. Only
force the process to stop if the deployment status has not changed to STOPPED after an
unreasonably long time.
When you stop a deployment normally, currently running processes are stopped gracefully. When you
force a stop, the deployment is stopped abruptly and currently running processes remain running. In
either case, the associated VMs are not cleaned up.
What to do next
When you stop a deployment normally, you can resume it, tear it down from the cloud, or delete the
application deployment record from vRealize Automation. See Chapter 19 Managing Deployments.
For an update process, you can continue to interact with the deployment by starting another update
process. See Chapter 17 Updating Application Deployments.
View Policy Compliance Summary
You can view the overall compliance status and associated policy details of a deployment.
During deployment, the SCAN life cycle script in the policy definition assesses the compliance state of a
deployment. The overall compliance status icon turns red or green, depending on the violation or
compliance of policy definitions in the deployment. The status displayed on the compliance summary
page is a snapshot of the application blueprint at the time the deployment was started. The number of
compliant and violated policy definitions and critical and noncritical definitions appear in the overall
compliance status. The associated deployment profile is located next to the overall status.
Above the overall compliance status, a policy scan timeline contains a time stamp that shows when the
deployment scan was initiated and any subsequent deployment compliance scans. For example, a
subsequent scan checks whether an updated policy definition in the catalog is compliant with the existing
deployment.
Prerequisites
n
Log in to Application Services as an application publisher and deployer.
n
Verify that a policy instance is applied to the deployment.
Procedure
1 On the Application Services title bar, click the drop-down menu and select Deployments.
2 Enter the name of a deployment that has a policy definition in the search text box.
3 From the search result list, select the deployment.
The deployment summary page opens.
Using Application Services
VMware, Inc. 243