Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning VMware vRealize Automation

You're reading from   Learning VMware vRealize Automation Learn the fundamentals of vRealize Automation to accelerate the delivery of your IT services

Arrow left icon
Product type Paperback
Published in Feb 2016
Publisher Packt
ISBN-13 9781785885839
Length 230 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Sriram Rajendran Sriram Rajendran
Author Profile Icon Sriram Rajendran
Sriram Rajendran
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. vRealize Automation and the Deconstruction of Components FREE CHAPTER 2. Distributed Installation Using Custom Certificates 3. Functional Validation – Phase 1 and Installing Secondary Nodes 4. Configuring a Guest OS for vRealize Automation vSphere Blueprints 5. Functional Validation – Phase 2 and Zero to VM Provisioning 6. Testing Failover Scenarios for vRealize Automation Components 7. vRealize Orchestrator in High Availability via the NSX Load Balancer 8. The Power of Advanced Service Designer (ASD) 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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image