WilliamLam.com

Using the new vSphere Guest OS Customization with cloud-init in vSphere 7.0 Update 3

by // 11 Comments

In vSphere 7.0 Update 3, the vSphere Guest Operating System (OS) Customization Engine has added native support for using cloud-init, which is an industry standard for customizing Linux-based operating systems. This additional GuestOS customization option is currently only available when using the vSphere API, either vSphere SOAP API or vSphere REST API and is not available for consumption when using the vSphere UI.

As part of a recent project, I was exploring some of the customization options and since I had not played with this specific API before, I figured this would be a good exercise. I quickly found that it was not very user intuitive in getting started, especially with the lack of end-to-end examples since this can only be consumed using the vSphere API. I also came across a number of different VMware KBs (here, here and here) that outlined various requirements and constraints when using cloud-init which also added to the confusion.

The high level requirements for using the new vSphere Guest OS Customization with cloud-init is the following:

  • vSphere 7.0. Update 3 or later (vCenter and ESXi)
  • VMware Tools running 11.3 or later
  • cloud-init running 21.1 or later

Note: Although VMware PhotonOS does support cloud-init natively, it is not a supported operating system when using the new vSphere GuestOS Customization with cloud-init due to how cloud-init has been integrated. For customers that require customization via cloud-init with PhotonOS, should continue using either the seed ISO option or the GuestInfo OVF option.

In this blog post, I will explore the complete end-to-end workflow from preparing a GuestOS for customization to applying the actual vSphere customization spec using the new cloud-init option. In addition, I have also created a simple PowerShell script which demonstrates the use of the vSphere REST API on constructing the required specification for using the new cloud-init option and this should hopefully help folks understand how the underlying API works with a working example.

[Read more...]

Heads Up - No healthy upstream error with VEBA vSphere UI plugin with vSphere 7.0 Update 3

by // Leave a Comment

After upgrading my homelab to vSphere 7.0 Update 3, I noticed that my VMware Event Broker Appliance (VEBA) vSphere UI Plugin which is included as part of the VEBA Appliance was no longer functioning properly and would display no healthy upstream error message.


I initially thought this might be environmental, since I had just upgraded from lab from vSphere 7.0 Update 2d to 7.0 Update 3. I had reported the issue to our vSphere UI Engineers who built the VEBA UI plugin and while they were looking into the issue, we had another report from a VEBA user who also was hitting the same issue. Today, I got an update from Engineering and it looks like there was a regression in the Envoy service running in the VCSA which had caused this issue. This issue will be fixed in a future patch update for the VCSA, but in the mean time, VEBA users can apply the workaround outlined below.

Note: This workaround is required for vSphere 7.0 Update 3 or later. The issue has been fixed in vSphere 8.0 but if you are running any version of 7.0 Update 3 or newer, you will still need to apply this workaround.

[Read more...]

Integrated NSX-T deployment in vSphere 7.0 Update 3 fails with timeout

by // 2 Comments

One of the new features highlighted in the latest vSphere 7.0 Update 3 release is the integrated NSX-T deployment and configuration workflow found directly within the vSphere UI as shown in the screenshot below.


After you click on the the "Install NSX" button, it will prompt for the NSX-T OVA and then take users through a guided wizard to on deploying and configuring NSX-T. I noticed that a few users were reporting a timeout issue after running through the workflow:

Cannot complete the operation: See the event log for details. Timeout: The task did not complete within the expected time span

I have not used this plugin before, so I was not sure what the issue was until I came across this Tweet from Validimir Velikov, a vSphere UI Engineer who had worked on the integrated NSX-T plugin and shared the reason for this error. A newer version of NSX-T will be needed to use this feature as the vSphere UI expects a "callback" from NSX-T Manager when the deployment and configuration is complete, which the current released version of NSX-T (3.1.3.1) does not support.

I think we could have provided a better user experience by first checking the NSX-T OVA version and ensuring that it meets the minimum version that supports this capability. Hopefully this is something we can improve upon in the future.