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

Types of Orchestrator configuration


Clustered Orchestrator servers guarantee high availability and load balancing to protect production installations, such as vRealize Automation.

The Orchestrator can be configured in two modes:

  • Active-Active

  • Active-Standby

Active-Active

Active nodes are the Orchestrator server instances that run workflows and respond to client requests. If an active Orchestrator node stops responding, it is replaced by one of the inactive Orchestrator server instances:

  • All nodes in the cluster are active and provide concurrent connections to the sessions

  • There is no service interruption because if one node fails, then the other active nodes keep the client session active

  • Workflows should be first created in standalone mode and then imported after configuring the Orchestrator in active–active cluster mode

  • The maximum number of nodes in active state is five

Active-Standby

In active-standby configuration, at least one node will be in standby state:

  • If the standby node does not receive...