Configuring vRA Management Pack for vROps

Before upgrading some of the vRealize components in our lab, I wanted to check the existing operations between some of the components, namely vROps and vRA. It turns out that the configuration requirements are quite different with the newer versions of vRA and the vRA Management Pack for vROps.

Support

Recently we had a customer query what functionality was possible between their instance of vRA v6.2.3 and a proposed vROps v6.6.1. The answer was none, or at least none that is supported.

Note that there is native interop between both vRA and vROps, and there’s also the vRA Management Pack for vROps, which is separate.

Exact support can get confusing, depending on the angle from which it is approached:

  • The vRA Mgmt Pack v2.1 for vROps does support vROps v6.2.3
  • The vRA Mgmt Pack v2.1 for vROps does support vRA v6.2.3
  • vROps v6.2.1 does support vRA v6.2.3
  • vROps v6.6.1 does not support vRA v6.2.3

So while the vRA Mgmt Pack v2.1 for vROps states support for vRA v6.2.x, vROps v6.2.1 as well as vROps v6.6.1, it is not supported to run vROps v6.6.1 with vRA v6.2.3.

Exact support details in Management Pack v2.1 Release Notes.

It’s always useful to check what’s supported with what across the vRealize Suite @ VMware Product Interoperability Matrices

 

Configure the vRA Management Pack for vROps

Some time ago I had configured vRA and vROps to communicate with one another, and posted about it here, but those versions are now quite extremely old.

Our lab currently (as of 22/11/2017) runs

  • vRA v7.1
  • vROps v6.2.1

and the plan is to upgrade vR Ops to v6.6.1.

Before upgrading vROps, I wanted to confirm that the vRA Management Pack was working ok. The vRA v2.1 Management Pack Guide doesn’t provide enough detail around the required user credentials to get this all working, but luckily @vAficianado does cover what’s required, so go look through this post for full details of what needs to be configured in vRA as well as in vROps.

When configuring the vRA Adapter, the initial settings are straightforward enough, as displayed below:

MgmtPack_Configure00

  • Enter the FQDN or IP Address
    • Specify the virtual ip name if vRA is load-balanced (as above)
  • Specify the individual vRA Tenants to monitor
    • Or use the asterisk to select ALL vRA Tenants
  • Specify the credential
    • A dedicated service account should be used as best practice

In my case the trouble lay with the credentials used, and here’s what resolved it.

2 user credentials are required:

  • SysAdmin – This is a system-wide role where administrator@vsphere.local can be used
  • SuperUser – This user needs to have multiple vRA Roles, as follows
    • Tenant Admin
    • IaaS Admin
    • Fabric Group Admin
    • Software Architect

We use a dedicated AD service account, app_vrops_vra@PPSILVER.lab.local, which we place/nest within higher level AD User Groups for the vRA Tenant Admins, IaaS Admins and Fabric Group Admins, as shown below

ADuserGroups

 

To enable the Software Architect role, we logged into the vRA Tenant (in this case the EHC tenant) as the Tenant Admin, navigated to Administration > Users and Groups and searched for the service account, as shown below:

ArchitectRole_00

 

Selecting that user then brings up the User Details panel from where the Software Architect Role should be assigned to this app_vrops_vra user/service account.

MgmtPack_Configure_vRA_Roles00

 

Click Finish etc etc, go back to vROps UI and Test Connection for the vRA instance, hopefully you get a Test Successful message, Save your settings, and ultimately have the collection state of the adapter looking like the following:

adapterCollectingOK

 

The vRA Dashboards should be selected/enabled from the vROps UI Home, looking something like the following:

vRA_dashboard

 

Sooo, with all of that now completed, onwards to upgrade vROps from v6.2.1 to v6.6.1, for which I plan to follow the instructions as laid out by this post on VMware Communities.

 

Update 23/11/2017

Upgrade of vROps from v6.2.1 to v6.6.1 completed, very straightforward, no issues, though on my system, after initial login to https://vrops/UI  the Chrome Browser (v62.0) wouldn’t resolve the new vROps UI properly, so I used FireFox.

The upgrade of vROps to v6.6.1 also upgraded the vRA Management Pack to v3.0 (which now comes integrated out of the box with vROps v6.6 along with vRealize Business for Cloud and Log Insight).

OOTB_vRAMgmtPack

There is a slight difference in the available dashboards and related views for vRA. Whereas previously in vROps v6.2.1, as shown above, 3 individual vRA-related dashboards were available, with vROps v6.6.1 these vRA views are split out into 2 Dashboards and a couple of Environmental views.

The 2 vRA Dashboards are available as show below:

  • vRealize Automation Top-N Dashboard
  • vRealize Automation Env Overview

vops661_vRADashboards

 

The Environmental views are available from the Environment space in the vROps UI.

  • Select Environment at the top of the page
  • Expand Other Inventories

From here a number of vRA-related vies are available, such as:

  • Automation Tenant Deployment and Virtual Machines
  • Blueprint View
  • vRealize Automation Tenant View (shown below)

vops661_vRATenantView

 

To recap on versions, the environment is now running:

  • vROps v6.6.1
  • vRA v7.1
  • vRA Management Pack v2.1 / v3.0
  • vSphere v6.0

Hope that helps for those interested!

 

 

 

 

 

 

 

Advertisements

One comment

  1. Pingback: vRealize Integrations – vRA and vR Ops | Scamallach

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s