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
A storage reservation policy is a tag applied to one or more datastores by a fabric administrator and is
used to group datastores that have similar characteristics, such as speed or price. A datastore can be
assigned to only one storage reservation policy at a time, but a storage reservation policy can have many
different datastores. A fabric administrator creates a storage reservation policy and assigns it to one or
more datastores. A tenant administrator or business group manager then assigns the storage reservation
policy to a volume in a virtual blueprint. When a user requests a virtual machine that uses the blueprint,
the storage reservation policy specified in the blueprint is used to select a datastore for the machine’s
volume.
When you add or edit a volume in a virtual blueprint, you can make the following assignments:
n
Assign a single datastore to the volume. This one-to-one relationship assigns only the specified
datastore at provisioning time. If the datastore is not available or lacks sufficient space, provisioning
fails.
n
Assign a storage reservation policy to the volume. This assignment allows the selection of one of the
datastores associated with the storage reservation policy at provisioning time. If the policy’s
datastores are unavailable or lack sufficient space, provisioning fails.
n
Assign a storage reservation policy to the volume and include the custom property
VirtualMachine.DiskN.StorageReservationPolicyMode with the value of NonExact. This
configuration allows you to assign a datastore that is not included in the storage reservation policy.
n
Do not assign a datastore or a storage reservation policy to a volume. Not making an assignment
allows selection from all available datastores at provisioning time. Provisioning fails if a datastore with
sufficient space is not available.
Datastore priority, as assigned by a datastore reservation, is also used to select a datastore at
provisioning time.
Avoid specifying a storage path and a storage reservation policy for the same volume. If you must specify
a storage path and a storage reservation policy for the same volume, the storage path takes precedence
over the storage reservation policy.
Choosing a Storage Scenario
When creating vSphere, KVM (RHEV), or SCVMM Create, Clone, FlexClone, or Linked Clone blueprints,
tenant administrators and business group managers can assign datastores to volumes, or assign storage
reservation policies to volumes.
Depending on the type of blueprint you are working with and your storage needs, the procedure to assign
datastores to volumes differs slightly.
IaaS Configuration for Virtual Platforms
VMware, Inc. 159