Not only can vRA use Orchestrator to access vCenter or other plugins, but you can also automate your vRA instance using Orchestrator. In this recipe, we will show you how to do the initial steps.
Please make sure that you read the introduction to vRA at the beginning of this chapter. We need a functional and configured vRA. We also need the vRA plugin for Orchestrator installed.
The vRA plugin is integrated into Orchestrator from version 7.1 onward.
However, you should be aware that even the plugin (7.1 at the time of writing) still shows vCAC and vCACCafe in Control Center, and it shows up in the Library as vRealize Automation.
This recipe is split into Preparation and Example.
To configure the vRA plugin, perform the following steps:
vSphere.local
.Let's run an example by creating a new Machine Prefix:
Test
, as well as the number of digits and the next number.You have hooked up Orchestrator to vRA and are able to do a lot of things. You can now use vRO to configure vRA.
With this plugin, you can create and configure vRA tenants automatically. It becomes even more handy when you are using the Event Broker and want to retrieve some additional information from vRA.
The difference between the vRA Host (VCAC:VcacCafeHost) and the IaaS Host (VCAC:VcacHost) is that things such as requests and catalog items are stored in the vRA Host and objects such as VMs in the IaaS host.
For any automation of vRA you need to configure this plugin.