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

vRealize Automation components and HA modes


vRealize Automation components in a high availability cluster are groups of computers that support server applications that can be reliably utilized with a minimum downtime. They operate in HA mode to harness redundant computers in groups that provide a continued service when system components fail. Without high availability, if a server running a particular application crashes, the application will be unavailable until the crashed server is fixed:

Active-Active configuration

All nodes are in active mode while handling the alike function on the same state. If there is a failure of one active node, then the other active node automatically handles the traffic. After the restoration of the failed node, it will enter the active mode routinely, where the load will be shared between the nodes. However, this depends on the session persistence settings used in the load balancer. CAFÉ, IaaS web server, DEM Worker, and proxy agents comes under this category...