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

Failover of Model Manager Web


The Web nodes fall under the active-active HA design with the failover taking place automatically if the active node fails. If the Web node, where the Model Manager Data is installed goes down, the impact will be visible during the following:

  • vRealize Automation upgrade

  • Executing the register solution rser and RepoUtil commands

When any or one Model Manager Web node goes down, the failover process is straightforward and seamless. Unlike CAFÉ or Manager Service, there are no special instructions required to recover the nodes if all the Web nodes fail due to any datacenter-wide crash or maintenance activities.

At any time, use the health monitor URL to check the status of the node:

  • IaaS Manager Node: https://<FQDN_of_WEB_virtual-IP_in_Loadbalancer>/WAPI/api/status—in our setup it will be—https://WEB.PKCT.LOCAL/WAPI/api/status

If at least one node is active behind the load balancer, you should receive a response similar to the following screenshot:

To access the...