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

Chapter 7. vRealize Orchestrator in High Availability via the NSX Load Balancer

While there are countless public documents that talk about the goodness of vRealize Orchestrator, we wanted to pivot our discussion on high availability configuration via the NSX load balancer for vRealize Orchestrator in this chapter. VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) can be configured to work in two server modes: standalone and cluster. To increase the availability of the VMware vRealize Orchestrator services both in standalone and cluster mode, you can put the Orchestrator behind a load balancer.

Starting with vRO 5.5, clustering has been included as an out-of-box option that enables greater availability for the Orchestrator engine. If an active Orchestrator server becomes unavailable midway through a workflow run, another active or the standby Orchestrator node will take over and complete the workflow without any service interruptions. However, we have two known limitations...