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

Configuring the vRealize Orchestrator cluster


The Orchestrator cluster provides not only high availability, but also load balancing when configured with NSX or another third-party load balancer. Orchestrator clustering is a zero-touch configuration, which means that the Orchestrator cluster is managing itself. The maximum number of active nodes that you define in the configuration dictates how many nodes are switched from standby to running. For example:

  • You define the number of active nodes as two; however, you configure three Orchestrator installations in this cluster and power them all on. This would result in two nodes being active and one being in standby mode.

  • If you now proceed to power off one of the active nodes, the standby node will become active. You could test this by setting the number of active nodes to 1 in the setup we are about to build.

There are certain drawbacks you should be aware of. It is not recommended to use the Orchestrator client to connect to the nodes running...