WilliamLam.com

Enhancements to VMware Cloud Foundation (VCF) & vSphere Automated Lab Deployment Scripts

by // 2 Comments

Simplicity is something I try to strive for when creating automation, whether that is for myself or for our customers. When I develop a script, I try to keep everything within a single file, so that it is easy to share and consume. As a script increases in functionality, it may be useful to break out some of its functions, typically libraries or modules.

I was recently debugging an issue with my popular automated lab deployment script for VMware Cloud Foundation (VCF) and while looking through the script that the user had been using, I found numerous variables that were commented out and replaced with their own values, which looked like they had different configuration and environments where they were using this single script.

It then hit me, why have I not considered externalizing all the variables that the script relied on, such that a user could easily supply different configuration options without needing to edit the primary deployment script!? 😅

[Read more...]

vSAN ESA hardware mock VIB for physical ESXi deployment for VMware Cloud Foundation (VCF)

by // Leave a Comment

Several weeks back I had shared a solution in which you can install a hardware mock VIB for Nested ESXi when using vSAN Express Storage Architecture (ESA) and VMware Cloud Foundation (VCF) to work around the vSAN ESA certified disks pre-check validations.


While the majority of my testing uses Nested ESXi, I have recently been deploying a physical VCF environment and I due to the limited number of NVMe devices, I wanted to use vSAN ESA for the VCF Management Domain but of course I would run into the same vSAN ESA certified disks pre-check validations, which would prevent the installer from proceeding.

I was hoping that I could also use the mocking method to allow my physical deployment but after some trial and error, I ran into inconsistent behaviors and after speaking with Engineering, I came to learn that the existing solution would also apply to a physical ESXi deployment as the physical storage controllers are made hidden by the mocking method and as long as you have vSAN ESA capable NVMe devices, it should allow vSAN ESA HCL pre-check to pass and continue with the installation!

[Read more...]

vSAN ESA HCL hardware mock VIB for Nested ESXi

by // 1 Comment

Whether you are configuring vSAN Express Storage Architecture (ESA) directly from vCenter Server or from VMware Cloud Foundation (VCF), the underlying ESXi hardware is automatically validated against the vSAN ESA Hardware Compatibility List (HCL) to ensure that you are using supported vSAN hardware.

In the case of vCenter Server, you can simply ignore the HCL warnings and accept the risks and proceed with the configuration but when using VCF, the operation is blocked to ensure customers have a good experience when selecting vSAN ESA when deploying a VCF Management or Workload  Domain.


With that said, there is workaround where you can create your own custom vSAN ESA HCL JSON based on the hardware that you have and then upload that to either Cloud Builder for setting up a new VCF Management Domain or to SDDC Manager for deploying a new VCF Workload Domain, which I have blogged about HERE and HERE.

The use of Nested ESXi is a very popular way to deploy VCF, especially if you are new to solution and allows you to easily experiment and learn. More recently, I have noticed an uptick in the interests for deploying VCF with vSAN ESA and while you can certainly generate a custom vSAN ESA HCL as mentioned earlier, the process still requires some effort and in some situations the vSAN ESA HCL could get overwritten leading some frustration in debugging.

After helping some folks debug their VCF environments recently, I was thinking about a better experience and leveraging another technique that may not be very well known externally ...

UPDATE (02/03/25) - This solution can also be used for a physical ESXi deployment for use with vSAN ESA and VCF.

[Read more...]