7.4
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Foundations and Concepts
- Using Scenarios
- Using the Goal Navigator
- Introducing vRealize Automation
- Tenancy and User Roles
- Service Catalog
- Infrastructure as a Service
- XaaS Blueprints and Resource Actions
- Common Components
- Life Cycle Extensibility
- vRealize Automation Extensibility Options
- Leveraging Existing and Future Infrastructure
- Configuring Business-Relevant Services
- Extending vRealize Automation with Event-Based Workflows
- Integrating with Third-Party Management Systems
- Adding New IT Services and Creating New Actions
- Calling vRealize Automation Services from External Applications
- Distributed Execution
- Foundations and Concepts
An IaaS administrator configures an infrastructure source by specifying the endpoint details and
credentials that vRealize Automation can use to communicate with the source.
vRealize Automation collects information about all configured infrastructure sources at regular intervals.
Table 6. Examples of Infrastructure Source Endpoints
Infrastructure Source Endpoints
vSphere vCenter Server
vCloud Air vCloud Air OnDemand or subscription service
vCloud Director vCloud Director server
Amazon or OpenStack Cloud service account
Hyper-V (SCVMM) Microsoft System Center Virtual Machine Manager server
KVM (RHEV) Red Hat Enterprise Virtualization server
Compute Resources
A compute resource is an object that represents a host, host cluster, or pool in a virtualization platform, a
virtual datacenter, or an Amazon region on which machines can be provisioned.
An IaaS administrator can add compute resources to or remove compute resources from a fabric group. A
compute resource can belong to more than one fabric group, including groups that different fabric
administrators manage. After a compute resource is added to a fabric group, a fabric administrator can
create reservations on it for specific business groups. Users in those business groups can then be
entitled to provision machines on that compute resource.
Information about the compute resources on each infrastructure source endpoint and machines
provisioned on each compute resource is collected at regular intervals.
Table 7. Examples of Compute Resources for Infrastructure Sources
Infrastructure Source Compute Resource
vSphere (vCenter) ESX or ESXi host or cluster
Hyper-V (SCVMM) Hyper-V host
KVM (RHEV) KVM host
vCloud Director virtual datacenter
Amazon AWS Amazon region
Data Collection
vRealize Automation collects data from infrastructure source endpoints and their compute resources.
Data collection occurs at regular intervals. Each type of data collection has a default interval that you can
override or modify. Each type of data collection also has a default timeout interval that you can override or
modify.
IaaS administrators can manually initiate data collection for infrastructure source endpoints and fabric
administrators can manually initiate data collection for compute resources.
Foundations and Concepts
VMware, Inc. 30