Once you have seen my previous blog <here> and all the pre-requisites are in place; it’s time to getting started with vRealize Automation Cloud.
Pre-Requisite for this blog step:
Creating a New Image Mapping
The name “Image Mapping” is exactly what it means, it’s the fact where you can map a single Name into many different Cloud (hosting platforms) to the VM image (templates).
As example we could say:
|Account / Cloud / Region…||Template / Image Name|
|vSphere On-Prem (Our Tests)||vSphere-CentOS-Template|
|AWS||CentOS Linux 7|
Understood and time to select at left side to create a new Image Mappings, Select: Configure > Image Mappings .
The mapping as explained priorly, linking an CentOS image to our On-Premise CentOS / Windows 2019 Template.
We are using for this blog post the vCenter On-Premise as Cloud end-point. Feel free to configure other end points and extra Image mappings, so you may deploy the blueprint later in many different environments using combination of tags.
Now, we have a new image mapping and we will be able to deploy soon our 1st blueprint into vRealize Automation Cloud or the vRealize Automation 8.1 On-Premise (if you are testing on it).
Let’s continue in setting up the vRealize Automation Cloud platform.
What is next
vRealize Automation Cloud – Cloud Assembly – Create a New Network Profile