6.2
Table Of Contents
- IaaS Configuration for Cloud Platforms
- Contents
- IaaS Configuration for Cloud Platforms
- Configuring IaaS
- Configuring IaaS for Cloud Checklist
- Custom Properties in Machine Provisioning, Blueprints, and Build Profiles
- Bringing Resources Under vRealize Automation Management
- Configure Machine Prefixes
- Create a Business Group
- Managing Key Pairs
- Cloud Reservations
- Optional Configurations
- Preparing for Provisioning
- Choosing a Cloud Provisioning Scenario
- Preparing for Amazon Provisioning
- Preparing for OpenStack Provisioning
- Preparing for Virtual Machine Image Provisioning
- Preparing for Linux Kickstart Provisioning
- Preparing for WIM Provisioning
- Creating a Cloud Blueprint
- Configuring Advanced Blueprint Settings
- Managing Cloud Infrastructure
- Monitoring Workflows and Viewing Logs
- Machine Life Cycle and Workflow States for Cloud Platforms
Table 6‑2. Choose a Resource Monitoring Scenario (Continued)
Resource Monitoring Scenario Privileges Required Location
Monitor the amount of storage,
memory, and machine quota of your
reservation that is currently allocated
and determine the capacity that
remains available to the reservation.
Fabric Administrator (monitor resource
usage for reservations on your compute
resources and physical machines)
Infrastructure > Reservations >
Reservations
Monitor the amount of storage,
memory, and the machine quota that
your business groups are currently
consuming and determine the capacity
that remains on reserve for them.
n
Tenant Administrator (monitor
resource usage for all groups in your
tenant)
n
Business Group Manager (monitor
resource usage for groups that you
manage)
Infrastructure > Groups > Business
Groups
You can also add resource monitoring portlets to your vRealize Automation homepage to monitor different
resource usage statistics. See Tenant Administration.
Data Collection
vRealize Automation collects data from both 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. IaaS administrators can manually initiate data collection for infrastructure source
endpoints and fabric administrators can manually initiate data collection for compute resources.
Table 6‑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.
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.
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.
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.
IaaS Configuration for Cloud Platforms
VMware, Inc. 106