This example is just a small lab environment however if you multiply this up to a production environment then the resources are quite astounding. Like most companies who saw the considerable amount of VMware vRealize Orchestrator workflow changes required to make the migration from vRealize Automation v7.x to vRealize Automation v8.x there are also other considerations like resources.

VRAM Increase = ( 40 + 16 ) = 56 / ( 40 + 6 ) = 46 = 1.21 therefore 21%įor a lab installation of VMware vRealize Automation v8.0 with one (1) Automation Appliance and one (1) vIDM Appliance the minimum memory and CPU requirements were four (12) vCPUs and 40GB for the Automation Appliance and two (8) vCPUs and 16GB for the vIDM Appliance. VRAM Increase = ( 40 + 6 ) = 46 / ( 32 + 6 ) = 38 = 1.2 therefore 20%įor a lab installation of VMware vRealize Automation v8.1 with one (1) Automation Appliance and one (1) vIDM Appliance the minimum memory and CPU requirements were four (12) vCPUs and 40GB for the Automation Appliance and two (2) vCPUs and 6GB for the vIDM Appliance.

VRAM Increase = ( 32 + 6 ) = 38 / ( 18 + 4 ) = 22 = 1.72 therefore 72%įor a lab installation of VMware vRealize Automation v8.0 with one (1) Automation Appliance and one (1) vIDM Appliance the minimum memory and CPU requirements were four (8) vCPUs and 32GB for the Automation Appliance and two (2) vCPUs and 6GB for the vIDM Appliance. VRAM Increase = ( 18 + 4 ) = 22 / ( 18 + 4 ) = 22 = 1 therefore 0%įor a lab installation of VMware vRealize Automation v7.6 with one (1) Automation Appliance and one (1) Windows IaaS node the minimum memory and CPU requirements were four (4) vCPUs and 18GB for the Appliance and two (2) vCPUs and 4GB for the Windows IaaS node. For a lab installation of VMware vRealize Automation v7.5 with one (1) Automation Appliance and one (1) Windows IaaS node the minimum memory and CPU requirements were four (4) vCPUs and 18GB for the Appliance and two (2) vCPUs and 4GB for the Windows IaaS node.

Set up a vrealize automation lab