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
By default, vRealize Automation uses Dynamic Host Configuration Protocol (DHCP) to assign IP
addresses to provisioned machines.
Fabric administrators can create network profiles to define a range of static IP addresses that can be
assigned to machines. Network profiles can be assigned to specific network paths on a reservation. Any
cloud machine or virtual machine provisioned by cloning or kickstart/autoYaST that is attached to a
network path that has an associated network profile is provisioned using static IP address assignment.
Tenant administrators or business group managers can also assign network profiles to blueprints by using
the custom property VirtualMachine.NetworkN.ProfileName. If a network profile is specified in both the
blueprint and the reservation, the profile specified in the blueprint takes precedence.
When a machine that has a static IP address is destroyed, its IP address is made available for use by
other machines. The process to reclaim static IP addresses runs every 30 minutes, so unused addresses
may not be available immediately after the machines using them are destroyed. If there are not available
IP addresses in the network profile, machines cannot be provisioned with static IP assignment on the
associated network path.
Create a Network Profile for Static IP Address Assignment
Fabric administrators can create network profiles to define a range of static IP addresses that can be
assigned to machines.
Prerequisites
Log in to the vRealize Automation console as a fabric administrator.
Procedure
1 Specify Network Profile Information
The network profile information identifies the external network profile and specifies settings for an
existing network.
2 Configure IP Ranges
A fabric administrator can define one or more ranges of static IP addresses for use in provisioning a
machine.
What to do next
You can assign a network profile to a network path in a reservation, or a tenant admin or business group
manager can specify the network profile in a blueprint.
Specify Network Profile Information
The network profile information identifies the external network profile and specifies settings for an existing
network.
Prerequisites
Log in to the vRealize Automation console as a fabric administrator.
IaaS Configuration for Virtual Platforms
VMware, Inc. 45