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, vCloud Automation Center uses DHCP to assign IP addresses to provisioned machines. For
cloud and virtual machines provisioned by using cloning or Linux kickstart/autoYaST provisioning, it is
possible to assign static IP addresses from a predefined range. Static IP address assignment can be
configured either at the reservation level or at the blueprint level.
Note This information does not apply to Amazon Web Services.
Add a Network Proļ¬le for Static IP Assignment to a Blueprint
Tenant administrators and business group managers can configure static IP assignment at the blueprint
level.
Note This information does not apply to Amazon Web Services.
For a list of custom properties related to networking, see Custom Properties for Networking.
Prerequisites
n
Log in to the vRealize Automation console as a tenant administrator or business group manager.
n
A fabric administrator must Create a Network Profile for Static IP Address Assignment.
n
Create at least one blueprint that is eligible for static IP assignment. Static IP is supported with cloud
and virtual machines provisioned by cloning or Linux kickstart/autoYaST. For SCVMM, you can only
use static IP addresses if you are cloning Linux machines and you installed the guest agent on your
template.
n
For vSphere clone blueprints, you must specify a valid customization specification on the Build
Information tab of the blueprint.
Procedure
1 Select Infrastructure > Blueprints > Blueprints.
2 Point to the blueprint for which you want to enable static IP assignment and click Edit.
3 Click the Properties tab.
4 Specify a network profile to use for assigning static IP addresses to a network device on machines
provisioned from this blueprint.
a Click New Property.
b Type VirtualMachine.NetworkN.ProfileName in the Name text box, where N is the number of
the network device for which to enable static IP assignment.
For example: VirtualMachine.Network0.ProfileName.
c Type the name of the network profile that defines the static IP addresses that can be assigned to
the network device.
IaaS Configuration for Virtual Platforms
VMware, Inc. 166