If you plan to have Cloud Foundation automate the deployment of vRealize Automation for cloud management, you must define hostnames and IPs prior to deployment.

vRealize Automation requires specific external services to be available prior to deployment. This includes a Microsoft SQL Server instance which can be deployed within the management domain or externally to the solution. Regardless of the location, vRealize Automation deployment requires the hostname and IP information for the SQL Server instance before beginning deployment. See "Deploy vRealize Automation in Cloud Foundation" in the VMware Cloud Foundation Operations and Administration Guide.

Deployment of vRealize Automation also deploys a virtual machine for vRealize Suite Lifecycle Manager (vRSLCM) and a edge device used for load balancing within the management domain. These two components are shared between vRealize Operations and vRealize Automation and are automatically installed if either product is deployed. Hostname and IP information is required to be defined for the vRealize Automation components to be installed within the solution and the shared components if not previously deployed.

During the deployment wizard for vRealize Automation, you are given the opportunity to select the number of nodes to be deployed. The samples shown within this document reflect a three node deployment. You will need to adjust accordingly if you deploy more than three nodes.

The following table provides an example of the information to be collected for the cloud management layer, including the shared components with vRealize Operations. If you deploy both vRealize Operations and vRealize Automation, the shared components are only installed once . This example uses a fictional DNS domain called rainpole.local for illustration purposes. Modify the sample information to conform to your site's configuration.

Table 1. Sample Hostnames and IP Addresses for the Cloud Management Layer

Component Group

Hostname

DNS Zone

IP Address

Description

vRealize Automation

vra01svr01

rainpole.local

172.16.11.80

Virtual IP address of the vRealize Automation Appliance

vra01svr01a

rainpole.local

172.16.11.81

vRealize Automation Appliance

vra01svr01b

rainpole.local

172.16.11.82

vRealize Automation Appliance

vra01svr01c

rainpole.local

172.16.11.83

vRealize Automation Appliance

vra01iws01

rainpole.local

172.16.11.84

Virtual IP address of the vRealize Automation IaaS Web Server

vra01iws01a

rainpole.local

172.16.11.85

vRealize Automation IaaS Web Server

vra01iws01b

rainpole.local

172.16.11.86

vRealize Automation IaaS Web Server

vra01ims01

rainpole.local

172.16.11.87

Virtual IP address of the vRealize Automation IaaS Manager Service

vra01ims01a

rainpole.local

172.16.11.88

vRealize Automation IaaS Manager Service and DEM Orchestrator

vra01ims01b

rainpole.local

172.16.11.89

vRealize Automation IaaS Manager Service and DEM Orchestrator

vra01dem01a

rainpole.local

172.16.11.90

vRealize Automation DEM Worker

vra01dem01b

rainpole.local

172.16.11.91

vRealize Automation DEM Worker

sfo01ias01a

sfo.rainpole.local

172.16.11.92

vRealize Automation Proxy Agent

sfo01ias01b

sfo.rainpole.local

172.16.11.93

vRealize Automation Proxy Agent

vrslcm01

rainpole.local

172.16.11.78

vRealize Suite Lifecycle Manager (shared component with vRealize Automation)

vredge01

rainpole.local

172.16.11.79

vRealize Edge load balancer (shared component with vRealize Automation)

Microsoft SQL Server (external)

vra01mssql01

sfo.rainpole.local

10.0.0.10

Microsoft SQL Server for vRealize Automation