To deploy an application, you must configure CAL. When you model a blueprint you can use virtual machine templates that you obtain directly from a cloud provider library, as well as an extensible library of ready-to-use application infrastructure components and scripts. After you model your application deployment topology, you can create dependencies and edit configurations to finalize your execution plan. After you deploy the application, you can also initiate an update process to scale clustered nodes, or change the configuration or code of deployed applications when a new version is available.

The following definitions help you understand the provisioning and updating workflow.

Main components of CAL.

cloud template

Cloud template that contains a predefined reusable machine image that includes an operating system and data. When you create virtual machines for your cloud environment, the specifications and software defined in the cloud template are applied to that virtual machine.

Table 1. Cloud Template Mapping to Supported Cloud Environments

Application Services Environment

Cloud Environment

Cloud template

Application Services template

vRealize Automation blueprint

Amazon Machine Image (AMI)

cloud provider

A cloud instance for deployment. You can define several cloud providers for a cloud provider type.

Table 2. Cloud Provider Mapping to Supported Cloud Environments

Application ServicesEnvironment

Cloud Environment

Cloud provider

vCloud Director organization

vRealize Automation 6.1 business group

Amazon Region

cloud provider type

Type of cloud infrastructure on which deployments can be made. Application Services supports only vCloud Director, vRealize Automation, and Amazon EC2.

deployment environment

An environment in a cloud provider, for example, development, test, staging, and production. A cloud provider can have multiple deployment environments.

Table 3. Deployment Environment Mapping to Supported Cloud Environments

Application Services Environment

Cloud Environment

Deployment environment

vCloud Director organization vDC

vRealize Automation reservation policy

Amazon VPC

For vCloud Director, a deployment environment maps to an organization virtual datacenter (vDC) for a defined cloud provider and uses resources from that vDC. An organization vDC provides resources to an organization and is partitioned from a provider vDC. Organization vDCs provide an environment where virtual systems can be stored, deployed, and operated. They also provide storage for virtual media, such as floppy disks and CD ROMs. A single organization can have multiple organization vDCs.

For vRealize Automation, a deployment environment maps to a reservation policy. If a deployment environment is not selected, vRealize Automation assigns a reservation policy depending on the resource requirements of the virtual machine in the vRealize Automation blueprint.

For Amazon EC2, a deployment environment maps to a combination of Amazon Virtual Private Cloud (VPC) and one of the Availability Zones in a region.

Main library components.

library

Library that contains logical templates, which are pointers to cloud templates. Reusable services that can be used in multiple applications and installed on a virtual machine. Tasks that can perform additional customized tasks in an application deployment.

service

Scripted software that can be installed on a virtual machine and reused in multiple applications.

external services

An application service such as a hardware load-balancer or a preinstalled database that is installed external to the deployment of the application. The application and the external service must be configured to work with each other.

logical template

A predefined virtual machine definition in Application Services. A logical template can be mapped to an actual cloud template in the cloud library and supported services. Logical templates allow an application blueprint to remain cloud agnostic.

policy

A user-defined set of definitions to govern application life cycle operations. For example, a policy can blacklist the use of certain software based on corporate guidelines. Policies are enforced when they are enabled in specific deployment environments through the use of policy instances.

custom tasks

From the execution plan, you can add custom tasks to perform additional customized tasks such as run security patches in an application deployment. You can create a custom task in the library and add it to an application deployment. Application Services also provides predefined tasks in the library that you can use to configure an APT repository, a YUM repository, register a machine with a Red Hat Network, or Join Domain.

operating system

Specifies an operating system that the IT organization for logical templates and services supports. A list of operating systems appears in the Operating systems menu, and you can add to the list.

tag

Organizes the lists of logical templates and services to enhance readability in the blueprint editor. A list of tags appears in the Tags menu, and you can add new tags to the list.

Main components of application provisioning.

application

Logical deployment unit, which defines the relationship between operating system templates, application components and their dependent services that can be distributed across multiple virtual machines.

application components

Custom code used as a template for components such as EAR files, WAR files, and so on. They are custom script packages for the install, configure, start, update, rollback, and teardown actions on a node or service.

application blueprint

Logical topology of an application for deployment. A blueprint captures the structure of an application with logical nodes, their corresponding services and operating systems, dependencies, default configurations, and network and storage topology requirements.

node

Virtual machine defined in the blueprint.

clustered node

Cluster of virtual machines defined in the blueprint.

disks

Additional disks to be added to the corresponding virtual machine or node.

properties

Configuration name-value pairs for services and application components. These are variables used by the scripts to set parameters on a script and run various configurations. For example, you can set the installation_path property value and configure installation scripts to use this property to specify the path to use to install a service during the application deployment process.

actions

Life cycle stages for the install, configure, start, update, rollback, and teardown scripts for services and application components to be installed.

storage

Space provided by cloud provider to place the disk into different storages to meet the performace requirements.

deployment profile

Collection of deployment settings for a blueprint, including cluster size, CPU, memory, cloud templates, and networks.

logical network

An entity created as a logical abstraction for a network. A logical network is a cloud agnostic abstraction used to indicate network locality between nodes in an application. A logical network is dynamically mapped to a cloud network during the configuration of a deployment profile.

cloud network

A network defined within the cloud deployment environment.

execution plan

Task plan for viewing the order in which virtual machines are created and action scripts for library and application components are installed, configured, started, and updated. The order in which an agent performs a task is defined in the deployment execution plan.

teardown

Removal of deployed virtual machines from the cloud. For example, you can tear down vCloud Director vApp and associated virtual machines, vRealize Automation virtual machine and the associated virtual machine in vCenter Server, or Amazon EC2 instances of a deployed application from the cloud environment. After the teardown process is complete, all of the other resources such as storage and IP addresses that are used by these virtual machines are returned to their respective pools.