VMware vRealize Automation is a cloud management platform which helps us to automate the delivery of IT Services by providing a secure portal where administrators, end users can request and create new IT services. VMware vRealize Automation is not just limited to VMware as backend platform but also works with different vendors across platforms.
Dedicated this article to discuss VMware vRealize Automation logical architecture which can be deployed as a simple architecture and can also be deployed as distributed architecture depending upon the size of your infrastructure. Simple installation is good for a POC environment, however, if you are planning to deploy vRealize Automation for a large organization distributed architecture should be given as priority.
Simple Logical Architecture – which has only the mandatory components starting with VMware vRealize Automation appliance includes all the core services like vRealize Automation, vRealize Identity Manager (Previous Versions of VMware vRealize Automation uses VMware SSO architecture however in Version 7 of vRealize Automation SSO is replaced by Identity Manager which has built-in multitenancy support), vRealize Orchestrator integrates with vRealize Automation to help us extend the automation capabilities of our cloud infrastructure and vPostrgres Database.
Next thing on the list that we need when proceeding with Simple Logical Architecture is IaaS component of vRealize Automation which has several key components including IaaS web Site which provides the infrastructure administration, Model Manager, Manager Service coordinates communication between agents and the IaaS database, Agents are used for provisioning and managing machines and services on the external systems including VMware vSphere, Citrix, Xen Server, Hyper-V, Database and Distributed Execution Manager are used for vRealize Automation Functionalities, as highlighted above it’s good for proof of concept however if you are thinking to deploy VMware vRealize Automation in our organization we need to consider the enterprise deployment architecture.
Distributed Logical Architecture – When working with distributed Logical architecture we have many possible configurations to think about depending upon the use cases and requirements, all the mandatory components that we discussed in Simple Logical Architecture are required when proceeding further with distributed architecture deployment.
We need to make use of load balancers to balance parts of vRealize Automation deployment and when working on the configuration of load balancers we need to make use of Least Response Time or Round Robin Method to balance traffic to vRealize Automation Appliances and Infrastructure Web Servers. NSX, F5 Big-IP Hardware and F5 Big-IP Virtual Edition are some of the recommended Load Balancers.
Deploy proxy agents in the same datacenter as the endpoint to which they are associated, which will give an increase in the data collection performance, when considering the configuration of Distributed Execution Manager (DEMs) ensure they are as close as possible to Model Manager host, create two DEM Orchestrator instances, one for failover and two DEM Worker instances when planning a vRealize Automation Distributed Logical Architecture.
Follow our Twitter and Facebook feeds for new releases, updates, insightful posts and more.
