6.2
Table Of Contents
- IaaS Configuration for Virtual Platforms
- Contents
- IaaS Configuration for Virtual Platforms
- Configuring IaaS
- Configuring IaaS Checklist
- Custom Properties in Machine Provisioning, Blueprints, and Build Profiles
- Bringing Resources Under vRealize Automation Management
- Choosing an Endpoint Scenario
- Store User Credentials for Endpoints
- Create a vSphere Endpoint
- Create a vSphere Endpoint with Networking Integration
- Create a NetApp ONTAP Endpoint
- Create a KVM (RHEV) Endpoint
- Create a Standalone Hyper-V Endpoint
- Create an SCVMM Endpoint
- Create a Xen Pool Endpoint
- Create a XenServer Endpoint
- Preparing an Endpoint CSV File for Import
- Import a List of Endpoints
- Create a Fabric Group
- Configure Machine Prefixes
- Create a Business Group
- Virtual Reservations
- Optional Configurations
- Build Profiles and Property Sets
- Reservation Policies
- Storage Reservation Policies
- Static IP Address Assignment
- Cost Profiles
- Enabling Users to Select Datacenter Locations
- Active Directory Cleanup Plugin
- Enabling Remote Desktop Connections
- Enabling Connections to Machines Using SSH
- Preparing for Provisioning
- Space-Efficient Storage for Virtual Provisioning
- Preparing Your SCVMM Environment
- Enabling Visual Basic Scripts in Provisioning
- Choosing a Provisioning Scenario
- Checklist for Virtual Provisioning by Cloning Preparation
- Choosing Your Linux Kickstart Provisioning Preparation Method
- Preparing for SCCM Provisioning
- Preparing for WIM Provisioning
- Creating Blueprints
- Space-Efficient Storage for Virtual Provisioning
- Choosing a Blueprint Scenario
- Create a Blueprint for the Basic Workflow
- Create a Blueprint for Cloning
- Create a Linked Clone Blueprint
- Create a Blueprint for Net App FlexClone Provisioning
- Create a Blueprint for WIM Provisioning
- Create a Blueprint for Linux Kickstart Provisioning
- Create a Blueprint for SCCM Provisioning
- Troubleshooting Blueprints for Clone and Linked Clone
- Publish a Blueprint
- Configuring Advanced Blueprint Settings
- Assigning Datastores to Machine Volumes
- Choosing a Storage Scenario
- Add a Datastore to a Create, Clone, or FlexClone Blueprint
- Add a Datastore to a Linked Clone Blueprint
- Add a Storage Reservation Policy to a Create, Clone, or FlexClone Blueprint
- Add a Storage Reservation Policy to a Linked Clone Blueprint
- Allow Alternative Datastores at Provisioning Time
- Reservation Policies
- Configuring Network Settings
- Enable Users to Select Datacenter Locations
- Allow Requesters to Specify Machine Host Name
- Enabling Visual Basic Scripts in Provisioning
- Add Active Directory Cleanup to a Blueprint
- Enable Machine Users to Create Snapshots
- RDP Connections
- Enable Connections Using SSH
- Assigning Datastores to Machine Volumes
- Infrastructure Organizer
- Managing Infrastructure
- Monitoring Workflows and Viewing Logs
- Appendix A: Machine Life Cycle and Workflow States
Managing Infrastructure 7
Different vRealize Automation roles monitor resource usage and manage infrastructure in different ways.
This chapter includes the following topics:
n
Managing Resource Usage
n
Data Collection
n
vSphere Host Maintenance
n
Decommissioning a Storage Path
Managing Resource Usage
Fabric administrators manage the resource usage of the compute resources and reservations they own,
and tenant administrators and business group managers manage the resource usage of the business
groups they own.
Resource Usage Terminology
vRealize Automation uses explicit terminology to distinguish between resources that are available,
resources that have been set aside for specific usages, and resources that are actively being consumed
by provisioned machines.
The Resource Usage Terminology table explains the terminology vRealize Automation uses to display
resource usage.
Table 7‑1. Resource Usage Terminology
Term Description
Physical Indicates the actual memory or storage capacity of a compute resource.
Reserved Indicates the machine quota, memory, and storage capacity set aside for a reservation. For example, if a compute
resource has a physical capacity of 600 GB and there are three reservations on it for 100 GB each, then the reserved
storage of the compute resource is 300 GB and the storage reserved is 50 percent.
For physical machines, this term indicates machines that are reserved for a reservation but not yet provisioned.
Managed For physical machines, this indicates that the machine is provisioned and currently under vRealize Automation
management.
VMware, Inc. 189