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
Checklist for Preparing for Linux Kickstart Provisioning by using
Configuration Files
If you are not using Solaris Automated Installer to provision machines, you can create Kickstart or
autoYaST configuration files that automate the installation of the vRealize Automation guest agent and a
Linux operating system on newly provisioned machines.
Table 3‑6. Checklist for Preparing for Linux Kickstart Provisioning by using Configuration
Files
Linux Kickstart by using a configuration file
Ensure that a DHCP server is available on the network. vRealize Automation cannot provision machines by using Linux
Kickstart provisioning unless DHCP is available.
Prepare the configuration file. In the configuration file, you must specify the locations of the vRealize Automation server and the
Linux agent installation package. See Prepare the Linux Kickstart Configuration Sample File.
Edit the isolinux/isolinux.cfg or loader/isolinux.cfg to specify the name and location of the configuration file and the
appropriate Linux distribution source.
(Optional) Add customization scripts.
1 To specify post-installation customization scripts in the configuration file, see Specify Custom Scripts in a kickstart/autoYaST
Configuration File.
2 To call Visual Basic scripts in blueprint, see Enabling Visual Basic Scripts in Provisioning.
Create the boot ISO image and save it to the location required by your virtualization platform. Please see the documentation
provided by your hypervisor if you do not know the required location.
Gather the following information so that tenant administrators and business group managers can include it in their blueprints:
1 The name and location of the ISO image.
2 For vCenter Server integrations, the vCenter Server guest operating system version with which vCenter Server is to create the
machine.
Note You can create a build profile with the property set BootIsoProperties to include the required ISO information. This makes it
easier for tenant administrators and business group managers to include this information correctly in their blueprints.
Prepare the Linux Kickstart
Configuration Sample File
vRealize Automation provides sample configuration files that you can modify and edit to suit your needs.
There are several changes required to make the files usable.
Procedure
1 Navigate to the vCloud Automation Center Appliance management console installation page.
For example: https://vcac-hostname.domain.name:5480/installer/.
2 Download and save the Linux Guest Agent Packages.
3 Unpack the LinuxGuestAgentPkgs file.
4 Navigate to the LinuxGuestAgentPkgs file and locate the subdirectory that corresponds to the guest
operating system that you are deploying during provisioning.
5 Open the sample-https.cfg file.
IaaS Configuration for Virtual Platforms
VMware, Inc. 78