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 vRO at CAFÉ or IaaS makes a difference!


Before we conclude this chapter, I want to talk about how vRO can be leveraged depending on the use case:

  • Use case 1: For instance, if you want to automate any post provisioning operations, then you may want to add vRO at the CAFÉ layer. This enables to create Anything as a Service (XaaS) by exposing the service blueprint to the customers utilizing the power of vRealize Orchestrator (vRO) called Advanced Service Designer. You will see more about ASD in the next chapter.

  • Use case 2: The Orchestrator can be configured as an endpoint at the IaaS level if you would like to provision or decommission a machine, especially for mission-critical systems that typically require interactions with a number of different management systems including DNS servers, load balancers, CMDBs, IP address management, and other systems.

    Note

    For additional details, I would encourage you to read—http://pubs.vmware.com/vra-62/topic/com.vmware.vra.extensibility.doc/GUID...