The installation of the vRealize Orchestrator (vRO) Management Pack for vRealize Operations Manager (vROps) is quite straightforward, though the configuration of the adapter takes a little more than is outlined in the official Mgmt Pack for vRO v1.0 Guide
Installation of the vRO Management Pack is quick and simple. From the vROps Admin UI e.g. https://vrops/ui go to the Administration tab, select Solutions, and click Add. Locate and select the appropriate .pak file and click Upload. Accept the EULA, and click Finish, The installation is very quick, <2mins for me.
The Management Pack is available to download from VMware Solution Exchange.
Once successfully installed, a vRO adapter must be configured. From the vROps UI, go to the Administration tab, from Solutions select the Management Pack for vRealize Orchestrator solution, and click the Gears icon, as highlighted below
This brings you to the most important piece of identifying the correct vRO instance and entering the correct connection details.
Following the Admin Guide for this was not as straightforward as I had hoped, so I had to do some digging and basic trial and error with the vRO Host url and the credentials.
As shown above, the vRealize Orchestrator Host should be the Hostname or Host IP Address only. No url, no FQDN.
As we use embedded vRO instances, as part of a clustered vRealize Automation (vRA) deployment, the hostname used is the virtual IP address/hostname for vRA, with port 443 required.
The credential used is a dedicated vRA to vRO Active Directory service account. This AD account is a member of a vcoadmins AD group, whose members are assigned vcoadmin privileges. Just the Username needs to be entered, no domain extension requirements.
Also, as per the Release Notes, the Advanced Settings > Workflow Execution Metric Collection Time needs to be changed from the default of 720 to a value that fits with the associated widgets e.g. 360, as shown below
Click Test Connection, and if successful, click Save Settings. After a period of time you should see the Collection State/Status for the adapter showing as Collecting/Data Receiving, as shown below
You can go validate that the vRO workflows are now displaying correctly in vROps by navigating to the Administration > Configuration > Inventory Explorer. Expand and select the packages to view the associated workflows. Example below
Currently this mgmt pack offers just a single predefined dashboard for vRealize Orchestrator Top-N Workflows. To view this dashboard, go to the Dashboards tab and enable the view. Our environment looked like the following:
This vRO Management Pack for vROps also provides the ability to import and monitor other vRO packages beyond the default vRO packages. So hopefully I will have another post soon covering how to configure some vRA XaaS packages and workflows.
Related Tech Specs
Our environment was running vRA/vRO v7.3 with vROps v6.6.1. The Management Pack for vRealize Orchestrator is compatible with:
- vRealize Orchestrator v7.3 and v7.4
- vRealize Operations Manager v6.6.1 and v6.7
In terms of web browsers, Internet Explorer worked best across the board. FireFox plain wouldn’t work, Chrome seemed OK for most but had issues later on.
John Dias of VMware has a number of great vROps posts including the following specific to vRO and vROps: