6.2
Table Of Contents
- IaaS Configuration for vCloud Air and vCloud Director
- Contents
- IaaS Configuration for vCloud Air and vCloud Director
- Updated Information
- Using the Goal Navigator
- Provisioning with vCloud Air or vCloud Director vApps
- Configuring IaaS for vApps
- Configuring IaaS for vCloud Air or vCloud Director Checklist
- Using Custom Properties in vApp Machine Provisioning, Blueprints, and Build Profiles
- Bringing Resources Under vRealize Automation Management
- Configure Machine Prefixes
- Create a Business Group for vCloud Provisioning
- vCloud Reservations
- Optional Configurations
- Preparing for vApp Provisioning
- Creating vApp and vApp Component Blueprints
- Configuring Advanced Blueprint Settings
- Monitoring Workflows and Viewing Logs
- Machine Life Cycle and Workflow States for vCloud Air or vCloud Director vApps
Comparing Multi-Machine Services and vApps
You can use vRealize Automation multi-machine services or vApps to group component machines.
Table 2. Comparison of Multi-Machine Service and vApp (vCloud) Features
vRealize Automation Multi-Machine Service vApp (vCloud)
Create a multi-machine blueprint that references individual
machine blueprints in vRealize Automation.
Use existing vApp templates created in vCloud Director or
vCloud Air.
Provision machines of any type (virtual, physical, or cloud) as
part of a service.
Provision virtual machines from vCloud Director or vCloud Air.
Use vRealize Automation to manage component machines of a
multi-machine service.
Use vCloud Director or vCloud Air to manage vApp machines.
Application-specific networks can be defined in a multi-machine
blueprint for vCloud Networking and Security and NSX.
Application-specific networks are defined in a vApp.
Component machines can be added or removed after initial
provisioning.
Component machines cannot be added or removed after initial
provisioning.
vRealize Automation defines startup and shutdown order. The vApp template defines startup and shutdown order.
For both, access to the component portal for Microsoft Remote Desktop Protocol, Virtual Network
Computing, and SSH depends on the guest and console and the endpoint.
Integration Considerations for vCloud Air and vCloud Director
Several considerations exist for vCloud Air and vCloud Director vApps in vRealize Automation.
As you prepare to provision vApps in vRealize Automation, be mindful of the following considerations.
n
If you import a vApp with multiple component virtual machines into vRealize Automation but the
import process fails for one or more component machines, you cannot import any of the virtual
machines that failed the import process.
n
When you configure vRealize Automation for vCloud Director, if you have users who are configured in
the vCloud Director identity store as LDAP users, configure these users for LDAP in the
vRealize Automation identity store so that the same set of users are available in both products.
n
The following actions are not supported in vRealize Automation:
n
Creating vApp templates
n
Defining vApp (vCloud) and vApp Component (vCloud) blueprints without specifying a vApp
template
n
Moving vApps between virtual datacenters
n
Moving virtual machines between reservations
n
Adding or removing components from a vApp
n
Creating or using vApp snapshots
n
Using a static IP address
IaaS Configuration for vCloud Air and vCloud Director
VMware, Inc. 9