vRealize Operations 6.7 Pre-Upgrade Readiness Assessment Tool

Overview
If you’re fortunate enough to have the ability to create custom dashboards in vROps, you’ve also most likely had the misfortune of having those dashboard and supporting views get broken during vROps upgrades when certain metrics and properties are removed or replaced. This past year I was able to participate in the vROps Design Partner Program and contribute ideas and feedback to the product management team at VMware. Because of this participation I feel a closeness to the 6.7 release and the improvements it includes. One such feature is the pre-upgrade readiness assessment tool. This tool will identify dashboards, views and metrics that may be affected by changes from previous versions of vRealize Operations Manager and the latest 6.7 release. These items, when identified, will need to be manually corrected after upgrade complete but the big news is you know about any impact BEFORE you start the upgrade. No more surprises weeks after the upgrade by some app team saying their dashboard is messed up.

VMware lists four distinct step for using the Assessment Tool:

  1. Download the PAK file from https://my.vmware.com/group/vmware/get-download?downloadGroup=VROPS-670
  2. Run the vROps Pre-Upgrade Readiness Assessment Tool
  3. Extract the report from the generated ZIP file
  4. Click the various items in the report to link to the solutions grid. You might also choose to send the report to VMware for analysis

These four steps will get you the list of things to work on to ensure all your views and dashboards keep providing you the valuable data vROps is so good at. After you have the list is where the work comes in to update and modify your custom dashboards. Keep reading for the step-by-step how to use the vRealize Operations 6.7 Pre-Upgrade Readiness Assessment Tool.

Running the Pre-Upgrade Readiness Assessment Tool
Logon to Admin page URL at https://[vrops-hostname-or-IP]/admin

Click Software Update then install a software update

Click Browse and select the upgrade check file. Check the box to install even if already installed, then click upload

When the file is uploaded and ready, click Next

Agree to the license terms and click Next

Review the release information and click Next

To start the update, click INSTALL

The software installation process starts. There are 9 phases that take various amounts of time. In my case on a small lab instance the total duration was right around a mere 2 minutes.
Once the update process is done it’s time to view the assessment report and see how bad the damage is.

In navigation menu, go to Support > Support bundles. Click drop down on the most recent bundle and click on the node info. Download (green arrow) the bundle to your local machine
When downloaded, unzip the package

Browse to the apuat-data\report folder and open the index.html file to view report

What’s super cool about this report is for each impacted metric it has live links to the online VMware documentation with the recommended replacements for that metric or property.

Here’s a link to the whole list of depricated vROps content if you want to browse around: http://partnerweb.vmware.com/programs/vrops/DeprecatedContent.html

At this point any metrics used in older versions of vRops but no longer available in vROps 6.7 have been inventoried and ready for taking action.

Fix Dashboards and Views
Now that we have this awesome report showing all the items that need to be fixed, we just need to update the views with the updated metrics.

Since the pre-upgrade assessment tool identified an impacted view, it needs to be updated to use the new values

Go to Dashboards > Views and locate the “M+S Bug: Idle VMs” view

Edit the view by clicking the pencil

The report identified two metrics and using the provided link to replacements we see this outcome

In this case, the necessary action is to remove the old cpu|idlePct metric and not replace it. Since the replacement is simply an indicator of 1 (idle) and 0 (not idle) this isn’t useful to the view since it is already filtered on idle VMs.
Update the metrics included in the data section by removing the cpu|idlePct metric

After making the edits to the view, be sure to click Save

View the dashboard that uses the updated view

And with that, disaster and embarrassment are avoided with super human strength.

Please follow and like us:

Leave a Reply

Your email address will not be published. Required fields are marked *