7.1
Table Of Contents
- Foundations and Concepts
- Contents
- 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
- Index
Table 8. 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 Amazon regions and machines provisioned on
Amazon regions.
Endpoint data collection runs every 4 hours.
Inventory Data Collection Updates the record of the virtual machines whose resource
use is tied to a specic 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.
Performance Data Collection (vSphere compute resources
only)
Updates the record of the average CPU, storage, memory,
and network usage for each virtual machine discovered
through inventory data collection.
Performance data collection runs every 24 hours.
The default timeout interval for performance data
collection is 2 hours.
Network and security inventory data collection (vSphere
compute resources only)
Updates the record of network and security data related to
vCloud Networking and Security and NSX, particularly
information about security groups and load balancing, for
each machine following inventory data collection.
WMI data collection (Windows compute resources only) Updates the record of the management data for each
Windows machine. A WMI agent must be installed,
typically on the Manager Service host, and enabled to
collect data from Windows machines.
Fabric Groups
An IaaS administrator can organize virtualization compute resources and cloud endpoints into fabric
groups by type and intent. One or more fabric administrators manage the resources in each fabric group.
Fabric administrators are responsible for creating reservations on the compute resources in their groups to
allocate fabric to specic business groups. Fabric groups are created in a specic tenant, but their resources
can be made available to users who belong to business groups in all tenants.
Business Groups
A business group associates a set of services and resources to a set of users, often corresponding to a line of
business, department, or other organizational unit.
Business groups are managed in Administration > Users and Groups and are used when creating
reservations and entitling users to items in the service catalog.
Foundations and Concepts
26 VMware, Inc.