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

Summary


Since the HA design holds a significant purpose in the vRealize automation distributed architecture, concluding that the failover test has been a success is an absolute step before endorsing it as a production-ready setup.

Testing the failover for every component is mandatory and the recipe for a successful failover is to follow the steps in a logical sequence for CAFÉ and Manager Service as described in this chapter. The failovers of other components are straightforward and does not require special instructions during and after the failover.

If you want to track the failure component, I would recommend the following approach:

  • Check in the load balancer pool setting if the required nodes are in the UP state

  • Corroborate whether the expected health monitor string is received by surfing the health monitor URL for every component behind the load balancer

  • Exercise the health monitor URL against the nodes directly bypassing the load balancer, especially for the component that has the active...