Automating a vRA instance in Orchestrator

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.

Getting ready

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.

How to do it...

This recipe is split into Preparation and Example.

Preparation

To configure the vRA plugin, perform the following steps:

  1. Log in to the Orchestrator Client.
  2. Run the workflow Library | vRealize Automation | Configuration | Add a vRA host.
  3. Add a name for the vRA host.
  4. Enter the HTTPS URL of the vRA installation, as https://vra.mylab.local.
  5. Agree to install the SSL certificates.
  6. Leave the connection variables at their defaults and click Next.
  7. Choose Shared session and enter the name of the Tenant as vSphere.local.
  8. Enter a vRA Infrastructure Admin account.
  9. Click on Submit and wait till the workflow has finished.
  10. Run the workflow Library | vRealize Automation | Configuration | Add the IaaS host of a vRA host.
  11. Select the vRA host from the Inventory.
  12. Accept the defaults, but don't forget to add the Administrator password for the Windows IaaS host.
  13. Check out your Orchestrator Inventory.

Example

Let's run an example by creating a new Machine Prefix:

  1. Log in to the Orchestrator Client.
  2. Run the workflow Library | vRealize Automation | Infrastructure Administration | Extensibility | Machine Prefix | Create a Machine Prefix.
  3. Set the IaaS host from vRealize Automation Infrastructure, as shown in the following screenshot:

    Example

  4. Enter the New Machine Prefix, such as Test, as well as the number of digits and the next number.
  5. Check on vRA for the new Machine Prefix.

How it works...

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.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset