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
When a virtual reservation’s machine quota, memory, or storage is fully allocated, no further virtual
machines can be provisioned from it. Resources may be reserved beyond the physical capacity of a
virtualization compute resource (overcommitted), but when the physical capacity of a compute
resource is 100% allocated, no further machines can be provisioned on any reservations with that
compute resource until the resources are reclaimed.
n
If the blueprint has specific network settings, the reservation must have the same networks.
If the blueprint or reservation specifies a network profile for static IP address assignment, an IP
address must be available to assign to the new machine.
n
If the blueprint or request specifies a location, the compute resource must be associated with that
location.
If the value of the custom property VRM.Datacenter.Policy is Exact and there is no reservation for a
compute resource associated with that location that satisfies all the other criteria, then provisioning
fails.
If the value of VRM.Datacenter.Policy is NotExact and there is no reservation for a compute resource
associated with that location that satisfies all the other criteria, provisioning can proceed on another
reservation regardless of location. This option is the default.
n
If the blueprint or request specifies the custom property VirtualMachine.Host.TpmEnabled, trusted
hardware must be installed on the compute resource for the reservation.
n
If the blueprint specifies a reservation policy, the reservation must belong to that reservation policy.
Reservation policies are a way to guarantee that the selected reservation satisfies any additional
requirements for provisioning machines from a specific blueprint. For example, you can use
reservation policies to limit provisioning to compute resources with a specific template for cloning.
If no reservation is available that meets all of the selection criteria, provisioning fails.
If multiple reservations meet all of the criteria, the reservation from which to provision a requested
machine is determined by the following logic:
n
Reservations with higher priority are selected over reservations with lower priority.
n
If multiple reservations have the same priority, the reservation with the lowest percentage of its
machine quota allocated is selected.
n
If multiple reservations have the same priority and quota usage, machines are distributed among
reservations in round-robin fashion.
If multiple storage paths are available on a reservation with sufficient capacity to provision the machine
volumes, storage paths are selected according to the following logic:
n
If the blueprint or request specifies a storage reservation policy, the storage path must belong to that
storage reservation policy.
If the value of the custom property VirtualMachine.DiskN.StorageReservationPolicyMode is NotExact
and there is no storage path with sufficient capacity within the storage reservation policy, then
provisioning can proceed with a storage path outside the specified storage reservation policy. The
default value of VirtualMachine.DiskN.StorageReservationPolicyMode is Exact.
IaaS Configuration for Virtual Platforms
VMware, Inc. 31