Book Image

Learning VMware vRealize Automation

By : SRIRAM RAJENDRAN, Sriram Rajendran
Book Image

Learning VMware vRealize Automation

By: SRIRAM RAJENDRAN, Sriram Rajendran

Overview of this book

With the growing interest in Software Defined Data Centers (SDDC), vRealize Automation offers data center users an organized service catalog and governance for administrators. This way, end users gain autonomy while the IT department stays in control, making sure security and compliance requirements are met. Learning what each component does and how they dovetail with each other will bolster your understanding of vRealize Automation. The book starts off with an introduction to the distributed architecture that has been tested and installed in large scale deployments. Implementing and configuring distributed architecture with custom certificates is unarguably a demanding task, and it will be covered next. After this, we will progress with the installation. A vRealize Automation blueprint can be prepared in multiple ways; we will focus solely on vSphere endpoint blueprint. After this, we will discuss the high availability configuration via NSX loadbalancer for vRealize Orchestrator. Finally, we end with Advanced Service Designer, which provides service architects with the ability to create advanced services and publish them as catalog items.
Table of Contents (15 chapters)
Learning VMware vRealize Automation
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Failover of DEM Worker and proxy agent


Both DEM Worker and the proxy agents follow the active-active HA configuration and failover process is automatic.

DEM Worker

If the worker service stops or loses its connection to the repository (Model Manager Web), the DEM Orchestrator clears all the associated workflow instances to the nonfunctional DEM Worker, thus allowing the other DEM Workers to pick up the workflow. This explains why the failover process is seamless and fluid without the requirement of any extra steps for it to function during and after the failover.

Proxy agents

If you have more than one vCenter endpoints, then you have to install an additional vSphere Agent. It's a 1:1 mapping between the vCenter endpoint and vSphere Agent. You can have multiple agents talking to the same vCenter endpoint in case of high availability but each agent should be on a different server, and they all should have the same name; otherwise, you will run into many issues. For example, if you have three agents...