VMware vRealize Automation

VMware vRealize Automation 8.0.1 - Hotfix 2 Released

Reading time: 3 minutes
On March 27, 2020, VMware released the second hotfix for vRealize Automation 8.0.1. Included in it are sixty-three fixes for items relating to the Provisioning, vRealize Orchestrator (vRO), vRealize CodeStream, and Virtual appliance/clustering. The hotfix can be installed using vRealize Suite Lifecycle Manager 8.0.1. It is recommended to install vRealize Suite Lifecycle Manager 8.0.1 Patch 1 before installing vRealize Automation 8.0.1 Hotfix 2 (Build For complete details on the items that have been resolved with this hotfix, review the VMware KB article Cumulative Update for vRealize Automation 8.

VMware vRealize Automation 7.6 – Hotfix 3 Released

Reading time: 1 minute
While vRealize Automation 8.0 may be the hot new cloud management platform from VMware, vRealize Automation 7.6 still enjoys widespread usage due to its long life and rich feature set. As such, VMware continues to provide bug fixes for vRealize Automation 7.6. Continuing this trend, VMware recently released Hotfix 3 for vRealize Automation 7.6 on February 25, 2020. This cumulative update brings us fixes for 14 separate issues relating to performance, UI, vRealize Operations integration, and adds support for Red Hat Enterprise Linux 8.

Custom Hostname Generation in vRealize Automation 8

Reading time: 12 minutes
If you’re like most large IT environments, a device naming standard is common to maintain order on your network when deploying new devices. Some IT environments utilize simple naming standards, while others are complex and might vary depending on location, device type, device usage, or some other abstract reason. vRealize Automation 8 introduced significant improvements over vRealize Automation 7 when it comes to machine naming including support for naming templates based on:

vRealize Automation 7.x Data Collection Stuck "In Progress" for Compute Resource

Reading time: 3 minutes
Over the past several years of operating multiple vRealize Automation 7.x deployments, I’ve come across a situation where the data collection status for the Inventory or State data stays stuck at “In Progress” for a particular vSphere cluster. Usually, this occurs because a vSphere Agent executing the job was stopped mid-process. I initially searched online for a solution and could not find anything that helped. This left me to digging through the vRealize Automation 7.

VMware vRealize Automation 8.0 Logs

Reading time: 8 minutes
Over the past several years of using vRealize Automation 6.x and 7.x, I have generated numerous dashboards and search queries within Splunk to explore the log data generated by these products. Knowing that vRealize Automation 8.0 is an entirely new product compared to previous versions, I decided that it was time to begin reviewing the log data being generated by the appliance to determine what information could be obtained from the logs.

5 / 6


Get Notified of Future Posts

Follow Me

Twitter Icon
LinkedIn Icon
RSS Icon

Recent Posts