Deploy Windows VMs for vRealize Automation Installation using vRealize Suite Lifecycle Manager 2.0
In this post I am going to describe , how to deploy Windows VMs for vRealize Automation Installation using vRealize Suite Lifecycle Manager 2.0
vRealize Suite Lifecycle Manager 2.0, you can install or deploy IaaS windows of a vRealize Automation deployment without having to provision it before trying to create an environment with vRealize Automation in vRealize Suite Lifecycle Manager.
The pre-check run ensures the system requirements are met, while the Windows OS template (one or more for specific IaaS component) itself is provided by any user.
· You can deploy IaaS components with a minimum number of steps.
· IaaS component deployments are part of vRealize Automation deployment.
· Pre-validations on the IaaS components should try to fix the issues wherever possible and when an issue is automatically handled you can fix from the UI.
1- Enter the Windows Username, and Password.
2- Select the Applicable Time Sync mode.
I do not have NTP server so I have selected use host time .
3-Select the Time Server (NTP). For more information, see Configure NTP Servers.
4- Configure Cluster Virtual IPs, select the Yes or No options.
If you select yes, then the load balancer is connected to the individual product and then configure the vRA Appliance, IaaS Web, and IaaS Manager manually.
5 -cloud admin you can deploy Windows VMs that are required for vRealize Automation installation, using vRSLCM installation wizard. Click Yes, and from the Configure Windows box under Product properties, select the required windows template and its associated spec.
When you select Yes, the Window box section appears. If you select no, then vRSLCM will not deploy new Windows VMs for IaaS components.
6 -deploying IaaS VMs, you can either select ISO or Template.
A-When you select ISO, map a valid windows ISO image along with a correct license key in vRSLCM. For more information on ISO mapping, see ISO Mapping in vRealize Suite Lifecycle Manager.B-When you select Template as an option for IaaS, you are asked to select a template from a pre-populated list. The templates in the list are collected from the vCenter specified at the in Infrastructure Details section. For more details on usage of templates, see Templates and Custom Specification in vCenter Server
7 -For a customization specification, select Existing Spec or User Input. An existing spec provides an option to select a spec from the vCenter Server. For a user input, enter the fields manually. The entries for user input are not saved but will be applied for the current deployment of vRealize Automation.
8 -Enter the details required for each of the Components. For each components advanced property can be accessed to override details provided in the Windows Box section.
9- Click Next to continue to PreCheck Details section.
10 -Before proceeding with precheck and deploy Iaas windows VM we need to see Best Practices.
You can follow the listed practices when you are installing IaaS VMs using vRealize Suite Lifecycle Manager.
· Windows update, if pre-configured in the templates used for a IaaS deployment, can lead to failure. Turn off the Windows update in the templates or create the template after performing recent most applicable update of the OS.
· Have unique names for the templates in a vCenter inventory. If for a given vCenter, there are templates that do not have a unique name, then it is difficult to identify the correct one from LCM installation UI.
Windows ISO Image
we can use the ISO-based deployments of IaaS for development and test environments.
If an ISO-based IaaS deployment is used, then IaaS database VM should be pre-deployed. Deployment of database VM using ISO is not supported in vRealize Suite Lifecycle Manager 2.0.
If an existing customization specification is being used for an IaaS deployment, then ensure that all the inputs for the custom spec are consistent and correct. Also, ensure that a valid NIC configuration with subnet details is present in the customization specification details.
IaaS installation from LCM does not support use of Run Once Commands in a customization specification. Also, the process does not configure policies, firewall rules, Antivirus, or any other software pre-bundled in the VM template or ISO. As a work-around, configure the appropriate services in the template to have them functional after first start of the deployed VMs. After you validate and deploy reports successfully, you can access the console of the deployed VMs and configure the required policies in the respective VM as per requirement
11- click on validate and deploy in Precheck Details
12- Once precheck done , LCM will start deploying IAAS windows VM .
13- we will see Successful message, Once Windows VM get deploy inside vCenter .