VMware dropped a bunch of Q2 updates for vRealize and vSphere 6.7 yesterday so I wanted to note the current interoperability with our integrations.
Starting with vRealize, these new versions are now available:
- vRealize Log Insight 4.8
- vRealize Automation 7.6
- vRealize Orchestrator 7.6
- vRealize Operations 7.5
Beginning with vRealize Log Insight, our Dell EMC VMAX and PowerMax Content Pack is fully supported. Upgrades to Log Insight are very straightforward. Download the 4.8 .pak file and upgrade the cluster from within the GUI. Navigate to Administration -> Management -> Cluster. Select UPGRADE CLUSTER, provide the .pak file, then select UPGRADE from the dialog box. Accept the license and the upgrade will move forward.
For vRealize Automation and Orchestrator, our VMware vRealize Orchestrator Plug-in for Dell EMC PowerMax has not yet been qualified internally with version 7.6. We do not have VMware certification, so this is just internal testing we need to go through. I think it won’t take too long for that to happen. For something like this it should be a mere formality.
Finally, Dell EMC Enterprise Storage Analytics version 4.6 was released last June and in September was VMware certified with vRealize Operations 7.0. VMware has been leap-frogging vROps versions to try to align with the other vRealize products so the newest is version 7.5 not 7.1. We will undertake a qualification process in conjunction with a hot fix for another platform and have an ESA point release in a month’s time.
The final release yesterday was vSphere 6.7 Update 2 (U2). You can see it here:
Generally the updates to vSphere are for bug fixes, though occasionally new features are added as with U1 and pathing latency. In this U2 release, there is nothing to that level, but I did want to point out a change to the UNMAP primitive in the Release Notes because it may be confusing. Here is the highlighted text:
Depending on how you read this, it may sound like VMware is now allowing changes to UNMAP granularity (default 1 MB). It is not. What the statement means is that arrays that do not advertise a granularity of 1 MB (or smaller), can now be supported in U2 for automated UNMAP. Before U2, automated UNMAP would not function on datastores (devices) presented from those arrays. Automated UNMAP has always worked on VMAX and PowerMax so this feature is not pertinent. I thought it important to mention so that customers do not attempt to change the granularity via CLI (you will also get an error if you try). Feel free to update to U2, however, as it is always a good practice.
I’ll add updates to this post as our integration support changes.