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
The daily cost of a machine is based on the cost of the memory, CPU, and storage resources that it
consumes, and the blueprint cost.
Table 2‑1. Daily Cost Drivers
Cost Driver Calculated Cost
Memory Allocated memory (GB) multiplied by the daily memory cost per gigabyte specified in the cost
profile associated with the compute resource on which the machine is provisioned
CPUs Number of allocated CPUs multiplied by the daily CPU cost specified in the cost profile
associated with the compute resource on which the machine is provisioned
Storage Allocated storage (GB) multiplied by the storage cost per gigabyte specified in one of the
following places:
n
The cost profile associated with the compute resource on which the machine is provisioned
n
The storage cost profile on the datastore on which the machine is provisioned
The cost specified in a storage cost profile for a specific datastore overrides the storage cost
specified in a cost profile on the compute resource.
Blueprint cost The value for daily cost specified in the machine blueprint is added to the total cost of the
machine.
This value can represent a markup for using the machine in addition to the resources consumed
by the machine.
Lease cost is calculated as daily cost multiplied by the total number of days in the lease period, if
applicable.
Cost-to-date is calculated as daily cost multiplied by the number of days a machine is provisioned.
How Cost Is Displayed
The machine cost is displayed at various stages of the request and provisioning life cycle and is updated
according to the current information in the request or on the provisioned item.
Daily cost and lease cost appear at all stages of the lifecycle. After the machine is provisioned, the cost-
to-date also appears.
IaaS Configuration for Virtual Platforms
VMware, Inc. 49