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 vSphere Endpoint


Once the credentials are created, add the vSphere endpoint by navigating to Endpoints in the Infrastructure tab. Click New Endpoint and browse to Virtual | vSphere (vCenter):

Enter the details as shown in the following screenshot:

While adding vCenter as an Endpoint, it's worth noting a few items:

  1. Add /sdk (lowercase) towards the end of IP/FQDN of vCenter.

  2. You should use the same name that was used at the time of installing the vSphere proxy agent. If you fail to recollect the name, you may navigate to Infrastructure | Monitoring | Log; you will find an error similar to the following screenshot. Anything within the vRA and agent texts will be the agent name: