WilliamLam.com

Identifying vSphere with Tanzu Managed VMs

by // Leave a Comment

With an increasing number of customers enabling the vSphere with Tanzu capability, which is included in both VMware vSphere Foundation (VVF) and VMware Cloud Foundation (VCF), more and more Virtual Machines will be deployed using the more modern approach of declarative provisioning using the powerful VM Service feature.


When using the vSphere UI, you can easily distinguish between a vSphere with Tanzu managed VM from a traditional VM by checking whether it is provisioned within a vSphere Namespace or whether it contains the "Developer Managed" label as shown in the screenshot above.

However, how do you identify a vSphere with Tanzu managed VM when using the vSphere API for Automation purposes?

[Read more...]

Minimum vSphere privileges to install or remove patch from ESXi

by // Leave a Comment

I recently got a question from our field inquiring about the minimum vSphere privileges that would be required to either install or remove a patch (VIB/Component) from an ESXi host. The customer was interested in using PowerCLI and specifically the ESXLI interface to automate the installation and removal of a VIB and wanted to create a custom vSphere Role with the minimum privileges, which can be done with vCenter Server or even a standalone ESXi host (properly licensed).

Since I was familiar with the underlying ESXi patch API that is used for these operations, a nice benefit of the vSphere API Reference is that it also lists the specific vSphere Privileges that is required for a given operation and in this case, it is just Host.Config.Patch privilege.

However, when the customer attempted to create a custom vSphere Role with just this privilege and perform the installation operation, they still received an error as shown in the screenshot below, which was a bit cryptic but they had assumed it was still permissions related as full administrative account had worked:

OperationStopped: Response status code does not indicate success: 500 (Internal Server Error)


[Read more...]

Disable IPv6 in ESXi Kickstart without additional reboot

by // 2 Comments

ESXi supports dual stack networking (IPv4 and IPv6) by default, however users can also configure just IPv4 or IPv6, which requires a system reboot for the changes to go into effect.

Recently, I received a question from a colleague asking if there was a way to disable IPv6 during ESXi Kickstart (aka scripted installation) but NOT require an additional reboot as this setting is typically added in the %post or %firstboot section, which will require an additional reboot due to changing the networking stack default.

The solution was actually quite simple by just leveraging the %pre section, which would ensure that IPv6 is disabled upon the initial reboot after the ESXi installation.

[Read more...]