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
Configuring Advanced Blueprint
Settings 5
Tenant administrators and business group managers can use custom properties and optional policies to
configure advanced blueprint settings such as reservation policies, Visual Basic scripts, and Active
Directory cleanup.
This chapter includes the following topics:
n
Assigning Datastores to Machine Volumes
n
Reservation Policies
n
Configuring Network Settings
n
Enable Users to Select Datacenter Locations
n
Allow Requesters to Specify Machine Host Name
n
Enabling Visual Basic Scripts in Provisioning
n
Add Active Directory Cleanup to a Blueprint
n
Enable Machine Users to Create Snapshots
n
RDP Connections
n
Enable Connections Using SSH
Assigning Datastores to Machine Volumes
Storage assignment is determined by reservations. Tenant administrators and business group managers
can further restrict storage volume assignment by specifying a single datastore or a storage reservation
policy that represents multiple datastores to a volume. With the multi-storage feature you can assign the
volumes of a virtual machine to different datastores for the vSphere, KVM (RHEV), and SCVMM
platforms.
When you assign the volumes of a virtual machine to different datastores, you can control and use
storage space more effectively. For example, you might deploy the operating system volume to a slower,
less expensive datastore and the database volume to a faster datastore.
You can assign a single datastore or a storage reservation policy that represents multiple datastores to a
volume. When you assign a single datastore to a volume, that datastore is used at provisioning time, if
possible. When you assign a storage reservation policy to a volume, one of its datastores is used at
provisioning time.
VMware, Inc.
158