6.2
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Introducing vRealize Automation
- Tenancy and User Roles
- Service Catalog
- Infrastructure as a Service
- Advanced Service Designer
- Common Components
- Extensibility
- vRealize Automation Extensibility Options
- Leveraging Existing and Future Infrastructure
- Configuring Business-Relevant Services
- Integrating with Third-Party Management Systems
- Adding New IT Services and Creating New Actions
- Calling vRealize Automation Services from External Applications
- Distributed Execution
Information about the compute resources on each infrastructure source endpoint and machines
provisioned on each compute resource is collected at regular intervals.
Table 4‑2. 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.
Table 4‑3. Data Collection Types
Data Collection Type Description
Infrastructure Source Endpoint Data Collection Updates information about virtualization hosts, templates, and
ISO images for virtualization environments. Updates virtual
datacenters and templates for vCloud Director. Updates regions
and machines provisioned on them for Amazon. Updates
installed memory and CPU count for physical management
interfaces.
Endpoint data collection runs every 4 hours.
Inventory Data Collection Updates the record of the virtual machines whose resource use
is tied to a specific compute resource, including detailed
information about the networks, storage, and virtual machines.
This record also includes information about unmanaged virtual
machines, which are machines provisioned outside of
vRealize Automation.
Inventory data collection runs every 24 hours.
The default timeout interval for inventory data collection is 2
hours.
State Data Collection Updates the record of the power state of each machine
discovered through inventory data collection. State data
collection also records missing machines that
vRealize Automation manages but cannot be detected on the
virtualization compute resource or cloud endpoint.
State data collection runs every 15 minutes.
The default timeout interval for state data collection is 1 hour.
Foundations and Concepts
VMware, Inc. 27