VCF

Recently I stumbled upon a limitation in VCF that isn’t very clearly documented, and while not an issue you would regularly come accross. It is an import limitation to be aware of if you plan to adjust your pNIC configuration of any VCF hosts post deployment/commisioning.

The Problem

We have a few customers who will not be able to commision their new hosts with the desired pNIC configuration due to current hardware availability. The availability of the pNICs due to global supply challenges has meant severe delays in availability.

On the 10th February VCF 4.4 was released, this was quite a significant milestone as it removed a few things from the equation and also provided more flexbility.

Firstly and arguably the big change.

vRealize Suite

vRealize Lifecycle Manager 8.6.2, upgrade and deployment of the vRealize Suite products is managed by vRealize Suite Lifecycle Manager. You can upgrade vRealize Suite products as new versions become available in your vRealize Suite Lifecycle Manager. vRealize Suite Lifecycle Manager will only allow upgrades to compatible and supported versions of vRealize Suite products. Specific vRealize Automation, vRealize Operations, vRealize Log Insight, and Workspace ONE Access versions will no longer be listed in the VMware Cloud Foundation BOM.