As a consultant I’ve had the opportunity to design, install and configure dozens of production vRealize Automation deployments, from reasonably small Proof of Concept environments to globally-scaled multi-datacenter fully distributed behemoths. It’s fair to say, that I’ve made mistakes along the way – and learned a lot of lessons as to what makes a deployment a success.
In the end, pretty much everything comes down to getting the pre-requisites right. Nothing that I’ve written here is not already documented in the official documentation, and the installation wizard does a huge amount of the work for you.
For the purposes of this post, I am working with the following components, which have been pre-deployed on a single flat network.
vRA Appliances
|
Server
|
CPU
|
RAM
|
Disk
|
|
vra-app-1
|
4
|
18
|
140
|
|
vra-app-2
|
4
|
18
|
140
|
|
Server
|
CPU
|
RAM
|
Disk
|
|
vra-web-1
|
2
|
8
|
60
|
|
vra-web-2
|
2
|
8
|
60
|
|
vra-man-1
|
2
|
8
|
60
|
|
vra-man-2
|
2
|
8
|
60
|
|
vra-dem-1
|
2
|
4
|
60
|
|
vra-dem-2
|
2
|
4
|
60
|
|
vra-sql
|
2
|
8
|
60
|
One of the cool new features released with vRealize Automation 7.2 was the integration of VMware Admiral (container management) into the product, and recently VMware made version 1 of vSphere Integrated Containers generally available (GA), so I thought it was time I started playing around with the two.
Big thanks to 
