6.2
Table Of Contents
- Using Application Services
- Contents
- Using Application Services
- Updated Information
- Introducing Application Services
- Install and Configure Application Services
- Installing Application Services
- Preparing to Install Application Services
- Start the Application Services Appliance
- Troubleshooting Problems Connecting to the Application Services Web Interface
- Unlock Your darwin_user Account
- Restart Application Services
- Configure Application Services to Use a Proxy for External URLs
- Register Application Services to vRealize Automation
- Upgrading Application Services
- Setting Up Users and Groups
- Using Tenants and Business Groups in Application Services
- Import Predefined Content to a Tenant
- Using the Application Services Web Interface
- Setting Up Application Provisioning for the Application Services Environment
- Virtual Machine Requirements for Creating vRealize Automation Custom Templates
- Creating Virtual Machine Templates in vRealize Automation
- Updating Existing Virtual Machine Templates in vRealize Automation
- Register the vRealize Automation Cloud Provider and Template
- Create a vRealize Automation Deployment Environment
- Setting Up Application Provisioning for the vCloud Director Environment
- Virtual Machine Requirements for Creating vCloud Director Custom Templates
- Creating Windows Virtual Machine Templates in vCloud Director
- Create Linux Virtual Machine Templates in vCloud Director
- Verify Cloud Template Configuration from the vCloud Director Catalog
- Updating Existing Virtual Machine Templates in vCloud Director
- Exporting Virtual Machine Templates with OVF Format
- Register the vCloud Director Cloud Provider and Template
- Create a vCloud Director Deployment Environment
- Setting Up Application Provisioning for the Amazon EC2 Environment
- Developing Application Services Components
- Managing the Application Services Library
- Creating Applications
- Working with Artifacts
- Deploying Applications
- Setting Up and Configuring a Deployment Profile
- Deploying with Deployment Profiles
- Publishing Deployment Profiles to the vCloud Automation Center Service Catalog
- Request a vRealize Automation Service Catalog Item
- Using the Deployment Summary Page
- Using the Composite Deployment Summary Page
- Understanding the Deployment and Update Process
- Understanding Deployment Failures
- Updating Application Deployments
- Initiate an Update Process to Scale Out Deployments
- Initiate an Update Process to Scale In Deployments
- Initiate an Update Process to Modify Configurations
- Use an Existing Update Profile
- Promote an Update Profile
- Rollback an Update Process
- Understanding Run Custom Task Update
- Troubleshoot Failed Update Process to Scale Deployments
- Troubleshoot Failed Update Process to Modify Configuration
- Deploying Predefined Library Components
- Managing Deployments
- View Deployment Task and Blueprint Details for an Application
- View Deployed VM Details and Execution Plan of an Application
- Start a Policy Scan
- Tear Down an Application from the Cloud
- Scale In Deployments from vCloud Automation Center
- Scale Out Deployments from vCloud Automation Center
- Tear Down an Application from vCloud Automation Center
- Delete an Application Deployment from Application Services
- Cancel a Deployment or an Update Process
- View Policy Compliance Summary
- Using the Application Services CLI
- Using the CLI Import and Export Functions
Script Input
Variable Description
var min_cpu_count Corresponds to min_cpu_count property and the value for the script is set to consume.
eventPayload Includes the details of the deployment assessed for policy compliance.
For regular properties, var eventPayload must be added to access the eventPayload object.
The policy script might regard the eventPayload variable as a java object with the following properties:
deploymentProfile of
type DeploymentProfile
as defined in V2 API
Represents the deployment profile capturing latest details of deployment. In
the case of updates, this includes all of the changes that are part of update
profile.
blueprint of type
Blueprint as defined in
V2 API
Represents the actual blueprint object that's referenced from
deploymentProfile.
logicalTemplates of type
ListLogicalTemplate
where LogicalTemplate
is as defined in V2 API
Represents the list of logical templates referenced from various nodes inside
the application blueprint.
serviceVersions of type
ListServiceVersion
where ServiceVersion is
as defined in V2 API
Represents the list of service versions references from various nodes inside
the application blueprint.
Policy scripts are expected to output the following properties to communicate the result of the compliance
assessment. Scripts must declare them as variables.
Script Output Variable Description
complianceResult Type of string that is mandatory. If script fails to set it then the compliance result is assumed as an Error.
The valid values for the variable are:
Compliant Indicates that a deployment is compliant against the policy being
assessed.
Non_Compliant Indicates that a deployment violates the policy being assessed.
Error Indicates failure to produce an assessment result.
complianceMessage Type of string.
This optional value provides a high-level summary of the reason behind policy violation. Value can be any
string with less than 2048 characters.
The scripts can create log messages with the standard println function available in Java Script. The log is
captured by Application Services, which is useful to diagnose errors in policy scripts or provide details for
a policy assessment result.
Prerequisites
n
Log in to Application Services as an application cloud administrator and an application publisher
and deployer.
n
Verify that at least one policy is created in the library. See Add a Policy to the Library.
Using Application Services
VMware, Inc. 144