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
Table 4‑5. Custom Properties for Linked Clone Blueprints (Continued)
Custom Property Description
Linux.ExternalScript.Name
Specifies the name of an optional customization script, for
example config.sh, that the Linux guest agent runs after the
operating system is installed. This property is available for Linux
machines cloned from templates on which the Linux agent is
installed.
If you specify an external script, you must also define its location
by using the Linux.ExternalScript.LocationType and
Linux.ExternalScript.Path properties.
Linux.ExternalScript.LocationType
Specifies the location type of the customization script named in
the Linux.ExternalScript.Name property. This can be either
local or nfs.
You must also specify the script location using the
Linux.ExternalScript.Path property. If the location type is
nfs, also use the Linux.ExternalScript.Server property.
Linux.ExternalScript.Server
Specifies the name of the NFS server, for example lab-
ad.lab.local, on which the Linux external customization script
named in Linux.ExternalScript.Name is located.
Linux.ExternalScript.Path
Specifies the local path to the Linux customization script or the
export path to the Linux customization on the NFS server. The
value must begin with a forward slash and not include the file
name, for example /scripts/linux/config.sh.
If you installed the guest agent to customize cloned machines, you use some custom properties more
often than others.
Table 4‑6. Custom Properties for Customizing Cloned Machines with a Guest Agent
Custom Property Description
VirtualMachine.Admin.UseGuestAgent
If the guest agent is installed as a service on a template for
cloning, set to True on the machine blueprint to enable the guest
agent service on machines cloned from that template. When the
machine is started, the guest agent service is started. Set to
False to disable the guest agent. If set to False, the enhanced
clone workfow will not use the guest agent for guest operating
system tasks, reducing its functionality to
VMwareCloneWorkflow. If not specified or set to anything other
than False, the enhanced clone workflow will send work items to
the guest agent.
VirtualMachine.Admin.CustomizeGuestOSDelay
Specifies the time to wait after customization is complete and
before starting the guest operating system customization. The
value must be in HH:MM:SS format. If the value is not set, the
default value is one minute (00:01:00). If you choose not to
include this custom property, provisioning can fail if the virtual
machine reboots before guest agent work items are completed.
IaaS Configuration for Virtual Platforms
VMware, Inc. 117