WilliamLam.com

Quick Tip - How to check if vSAN TRIM/UNMAP is enabled in VMware Cloud on AWS Cluster?

by // 2 Comments

While the original question was for checking whether a specific VMware Cloud on AWS (VMC-A) cluster has the vSAN TRIIM/UNMAP feature enabled, the solutions below is applicable to any recent vSAN 7.x or 8.x deployment. There are two ways you check, either using the vSphere UI by selecting the cluster and navigating to Configure->vSAN->Services and expanding the Advanced Options tile or simply leveraging PowerCLI and the vSAN API to retrieve the exact same information.

vSphere UI

vSAN API using PowerCLI

$clusterName = "Cluster-1"
$vsanConfigSystem = Get-VsanView -Id VsanVcClusterConfigSystem-vsan-cluster-config-system
$clusterMoRef = (Get-Cluster $clusterName).ExtensionData.MoRef
$vsanConfigSystem.VsanClusterGetConfig($clusterMoRef).unmapConfig

 

Using vCenter Converter 6.3 with vSphere 8 or VMware Cloud on AWS (VMC-A)

by // 5 Comments

Since the announcement that vCenter Converter was re-returning, customers have been looking forward to the day that vCenter Converter would be an officially supported product again. Luckily, folks did not have to wait long from the early beta almost a month ago and just a couple of days ago, vCenter Converter 6.3 has officially GA'ed!

The goal of this initial vCenter Converter release was to bring functional parity with the last supported release, updated development and security practices and a few minor enhancements including some new Guest Operating Systems and vSphere 7.0 support. The team still has a ton in store for subsequent releases and if there are certain features you really want to see, feel free to leave a comment and I will be sure to share it with PM/Engr team.

With that said, I have also been getting a lot of questions from customers interested in using Converter to migrate workloads to VMware Cloud on AWS (VMC-A), especially as they think about modernizing and consolidating their Datacenter infrastructure. While, VMware Cloud on AWS as a destination will be in scope for the next release, I was curious on whether it would work given that vSphere 7.0 support was added to latest vCenter Converter release.

You know what happens when I get curious ... I just have to try it out! 😅

[Read more...]

vSphere Event-Driven Automation using VMware Event Router on VMware Cloud on AWS with Knative or AWS EventBridge

by // Leave a Comment

The VMware Event Broker Application (VEBA) is a popular VMware Event-Driven Automation solution that can be consumed using either the open source or commercial offering from VMware. The commercial offering of VEBA is already available to customers today via our Tanzu Application Platform (TAP) offering, which I have previously written about here. The open source offering of VEBA can be consumed in either a pre-packaged Virtual Appliance or a native Kubernetes Application called for those with an existing Kubernetes cluster.

Deploying the VEBA Virtual Appliance is well documented (here and here) and I wanted to spend some time covering the native Kubernetes deployment model, as it there are actually a couple of options and most recently, this came up in a customer discussions as they were interested in forwarding vSphere Events from VEBA to AWS EventBridge.

In the open source version of VEBA, there is a component called the VMware Event Router, which is responsible for connecting to an event source such as vCenter Server and then forwarding those events to a processor which can either be a a function that you have written to react to a specific event using Knative or to AWS EventBridge to integrate with other AWS native services like CloudWatch as an example.

To demonstrate the two different ways to deploy the VMware Event Router, I have created the following Github repo https://github.com/lamw/vsphere-event-driven-automation-vmware-event-router that provides an example to easily deploy the VMware Event Router to an existing Kubernetes cluster. For my environment, I will be using VMware Cloud on AWS and the managed Kubernetes offering called Tanzu services, which is included as part of the base offering and there is no additional cost of running the Kubernetes infrastructure, which is certainly an added bonus 😀

[Read more...]