vRealize Automation 8: Image Mappings

Table of Contents:

Tags:

Introduction to Image Mappings in vRealize Automation

In order to create a blueprint with a virtual machine, there is need to import images from the underlying cloud provider.

In contrast to vRealize Automation 7, administrators have full control which images should be imported into vRealize Automation 8, hence there is a dedicated menu item called „Image Mappings“ on the Infrastructure tab.

The image displays a user interface from VMware vRealize Automation (vRA) focused on the "Image Mappings" section under "Infrastructure". In the center of the screen, there are two entries for image mappings: "ubuntu1604" and "ubuntu1804", each with options to open or delete them. In the top right corner, the username "Guido Söldner" and the identity "VR-IDENTITY" are visible. The left sidebar provides additional navigation options including "Configure", "Resources", and "Activity".

Importing an Image is quite easy and can be done via the [+ New Image Button] button.

If you are using vSphere as a cloud provider (what most users certainly do), be sure to configure the template in vSphere beforehand.

The image displays a user interface from VMware vRealize Automation (vRA), specifically showing the screen for creating a new image mapping. The title "New Image Mapping" is displayed at the top. The user is in the process of defining a new image with the name "Windows 2016". Below the name field, there is a "Configuration" section with fields for "Account / Region" and "Image", populated with "SC labs / SCLABS" and "w2k16fcm", respectively. There are also fields for "Constraints" and "Cloud Configuration", with an option to add more configurations. At the bottom, there are buttons for "CREATE" and "CANCEL".

Advanced Image Mapping Techniques

Alternatively, you can directly reference cloud images. For example, when instead of manually importing an Ubuntu template in vSphere, you can just use the URL to import the image. That’s definitively a cool feature, however, please be aware that provisioning might take some more time, as the backing ovf-file has to be downloaded first.


The image displays a user interface from VMware vRealize Automation (vRA), specifically showing the screen for editing an image mapping. The screen is titled "Edit Image Mapping" with a "DELETE" option at the top right. The user is modifying an existing image mapping named "Ubuntu1804". The "Configuration" section lists the "Account / Region" as "SC labs / SCLABS" and provides a URL in the "Image" field, pointing to an Ubuntu image hosted at "https://cloud-images.ubuntu.com/releases/bionic/release-2019". There is also a space for "Constraints" and "Cloud Configuration", with an option to add additional configurations. At the bottom, there are buttons for "SAVE" and "CANCEL".

Once the configuration has been completed, you are able to see the OVF details:


The image displays the "OVF Details" dialog from a VMware vRealize Automation (vRA) interface, specifically for an Ubuntu cloud image. The top of the dialog contains a link to the Ubuntu cloud image release and a "COPY ALL PROPERTIES" button. The details are organized into a table format with columns labeled "Label", "Property", "Default Value", "Qualifiers", and "Required".

Key properties listed include:

hostname: Default value "ubuntuguest", indicating the hostname for the appliance.
instance-id: Labeled as "id-ovf", a unique identifier for the instance.
password: A default password is not set, allowing for a password-based login. The password field can be set to "RANDOM" for generating a random password upon each login.
public-keys: Indicates the SSH public keys used for instance access; by default, no keys are provided.
seedfrom: Specifies the URL to seed instance data from, optional and not set by default.
user-data: Encoded user data, to be base64 encoded and included as part of the instance's startup configuration.
The dialog provides comprehensive information necessary for deploying and configuring the Ubuntu cloud image within a vRA environment.

Setting up Constraints and Cloud Configuration will be discussed in a later post and are optional.

Autor

Dr. Guido Söldner

Geschäftsführer

Guido Söldner ist Geschäftsführer und Principal Consultant bei Söldner Consult. Sein Themenfeld umfasst Cloud Infrastruktur, Automatisierung und DevOps, Kubernetes, Machine Learning und Enterprise Programmierung mit Spring.