6.2
Table Of Contents
- IaaS Configuration for Cloud Platforms
- Contents
- IaaS Configuration for Cloud Platforms
- Configuring IaaS
- Configuring IaaS for Cloud Checklist
- Custom Properties in Machine Provisioning, Blueprints, and Build Profiles
- Bringing Resources Under vRealize Automation Management
- Configure Machine Prefixes
- Create a Business Group
- Managing Key Pairs
- Cloud Reservations
- Optional Configurations
- Preparing for Provisioning
- Choosing a Cloud Provisioning Scenario
- Preparing for Amazon Provisioning
- Preparing for OpenStack Provisioning
- Preparing for Virtual Machine Image Provisioning
- Preparing for Linux Kickstart Provisioning
- Preparing for WIM Provisioning
- Creating a Cloud Blueprint
- Configuring Advanced Blueprint Settings
- Managing Cloud Infrastructure
- Monitoring Workflows and Viewing Logs
- Machine Life Cycle and Workflow States for Cloud Platforms
A virtual machine image is a template that contains a software configuration, including an operating
system. Virtual machine images are managed within the Red Hat OpenStack provider and are imported
during data collection.
If an image that is used in a blueprint is later deleted from the Red Hat OpenStack provider, it is also
removed from the blueprint. If all the images have been removed from a blueprint, the blueprint is
disabled and cannot be used for machine requests until it is edited to add at least one image.
OpenStack Flavors
A tenant administrator or business group manager selects one or more flavors when creating
Red Hat OpenStack blueprints.
Flavors are virtual hardware templates that define the machine resource specifications for instances
provisioned in Red Hat OpenStack. Flavors are managed within the Red Hat OpenStack provider and are
imported during data collection.
If a flavor that is used in a blueprint is later deleted from the Red Hat OpenStack provider, it is also
removed from the blueprint. If all the flavors have been removed from a blueprint, the blueprint is disabled
and cannot be used for machine requests until it is edited to add at least one flavor.
Preparing for Linux Kickstart Provisioning
Linux Kickstart provisioning uses a configuration file to automate a Linux installation on a newly
provisioned machine. To prepare for provisioning you must create a bootable ISO image and a kickstart
or autoYaST configuration file.
The following is a high-level overview of the steps required to prepare for Linux Kickstart provisioning:
1 Ensure that a DHCP server is available on the network. vRealize Automation cannot provision
machines by using Linux Kickstart provisioning unless DHCP is available.
2 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.
3 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.
4 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.
5 (Optional) Add customization scripts.
a To specify post-installation customization scripts in the configuration file, see Specify Custom
Scripts in a kickstart/autoYaST Configuration File.
b To call Visual Basic scripts in blueprint, see Enabling Visual Basic Scripts in Provisioning.
6 Gather the following information so that tenant administrators and business group managers can
include it in their blueprints:
a The name and location of the ISO image.
IaaS Configuration for Cloud Platforms
VMware, Inc. 51