With the release of vRealize Automation 7 a few things have changed in regards to the sizing of the platform. In this article I will share some important changes and we will also take a look at the small, medium and large configurations for vRA 7.
With vRealize Automation 7:
- There’s no identity or SSO appliance anymore, the new VMware Identity Manager is now part of the vRA appliance.
- You cannot use an external Postgres database anymore, the progress database server is part of the vRA appliance. This is the only database server you can use.
- The appliance database is now clustered automatically with the appliance.
- vRealize Orchestrator 7 is also part of the appliance, vRO is now clustered automatically with the appliance. You’re still allowed to run an external vRO server (and sometimes this is recommended).
- vRealize Application Services has been merged into vRealize Automation 7.
- vRealize Business Standard is still contained in a separate appliance.
Let’s now have a look at the implications for the small, medium and large configurations of vRealize Automation.
Small configuration
Key figures: 10.000 managed VMs, 500 catalog items, 10 concurrent deployments.
This configuration requires one vRA appliance and one infrastructure core server. The Windows based infrastructure core server (f.k.a. the IaaS server) contains the:
- Web server;
- Manager server;
- DEM Orchestrator;
- DEM Worker(s);
- Proxy Agent(s).
A separate vRealize Business appliance is required and connects to the vRA appliance and infrastructure core server. Also a separate SQL Server is required for the infrastructure core server.
Additional details on this configuration here.
Medium configuration
Key figures: 30.000 managed VMs, 1000 catalog items, 50 concurrent deployments.
This configuration includes two vRA appliances and two servers running the infrastructure web + manager services. These four nodes are all behind a load balancer (required). Two infrastructure agent servers are required, and two infrastructure DEM servers are required as well. These nodes are not behind a load balancer.
A separate vRealize Business appliance is required and connects to the vRA appliance and infrastructure web servers. Also a separate clustered SQL Server is required for the infrastructure servers.
Additional details on this configuration here.
Large configuration
Key figure: 50.000 managed VMs, 2500 catalog items, 100 concurrent deployments.
This configuration includes two vRA appliances, two servers running the infrastructure web service and two servers running the infrastructure manager service. These six nodes are all behind a load balancer (required). Two infrastructure agent servers are required, and two infrastructure DEM servers are required as well. These nodes are not behind a load balancer.
The large configuration runs a separate vRO cluster of two nodes, these nodes are also behind a load balancer.
A separate vRealize Business appliance is required and connects to the vRA appliance and infrastructure web servers. Also a separate clustered SQL Server is required for the infrastructure servers. A second clustered SQL Server is required for the vRO cluster.
Additional details on this configuration here.
