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
After you select a goal, you navigate between the pages needed to accomplish the goal by clicking each
step. The goal navigator does not validate that you completed a step, or force you to complete steps in a
particular order. The steps are listed in the recommended sequence. You can return to each goal as many
times as needed.
For each step, the goal navigator provides a description of the task you need to perform on the
corresponding page. The goal navigator does not provide detailed information such as how to complete
the forms on a page. You can hide the page information or move it to a more convenient position on the
page. If you hide the page information, you can display it again by clicking the information icon on the
goal navigator panel.
Provisioning with vCloud Air or vCloud Director vApps
Users can provision vApps and their component machines in a virtual datacenter, based on an existing
vApp template, using vCloud blueprints.
Before you can integrate vCloud Air or vCloud Director with vRealize Automation, install and configure
your vCloud Air or vCloud Director instance, including setting up organizations, cloud resources, and
vApp templates.
If you intend to use a vCloud Air endpoint, set up an account with the vCloud Air support organization and
gather account information such as address and organizational unit for use when defining the vCloud
endpoint.
The vApp request owner should be a member of the domain associated with the Organization vDC on
which the vApp is provisioned. If the request owner is not a member of the domain, an owner value is not
assigned. The owner must exist in the organization.
For vCloud Director, the organization administrator or system administrator role is required for endpoint
credentials. For running data collection on the endpoint, these access rights are also required. For
consumers in a business group, if the user account does not exist, vCloud Director will perform a lookup
in the associated LDAP or Active Directory and create the account if the user exists in the identity store.
For vCloud Air, the infrastructure administrator or account administrator role is required for endpoint
credentials. For consumers in a business group, if the user account does not exist, vCloud Air will create
it. For related information about vCloud Air user management, see vCloud Air documentation.
vCloud Director user roles in an organization do not need to correspond with roles in the
vRealize Automation business group. For example, unless the vRealize Automation business group
manager or tenant administrator needs to create templates in vCloud Director, they do not need vApp
author permissions to create or edit vApp (vCloud) blueprints in vRealize Automation.
You must complete the following administrative tasks before vApp provisioning:
n
Configure cloud resources, including virtual datacenters and networks, to provision vApps.
n
Create vApp templates for vApps to provision.
For information about configuring vCloud Air or vCloud Director, see vCloud Air or vCloud Director
documentation.
IaaS Configuration for vCloud Air and vCloud Director
VMware, Inc. 6