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

Infrastructure agent


The agents are designed to interact with external systems. There are different types of agents, each having specific functions:

  • Virtualization proxy agents: These interact with hypervisors (vSphere, KVM, Hyper-V) to provision virtual machines and the data collection of an inventory. There can be multiple proxy agents to the same hypervisor (N: 1).

  • Integration agents: Virtual desktop integration (VDI) and external provisioning integration (EPI) fall under this purview.

  • WMI agents: These enable data collection from the Windows machines managed by vRealize Automation.

Note

If you have more than one vCenter endpoint, then you have to install an additional vSphere agent—it's a 1:1 mapping between the vCenter endpoint and the vSphere Agent. You can have multiple agents talking to the same vCenter endpoint in case of high availability but each agent should be on a different server, and they all should have the same name else you will run into many issues. For example if you have three agents pointing to a single vCenter Server, then all the three agents pointing to this vCenter Server should be named as Agent. Please refer to KB: 2052062 for additional details.