WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple

Search Results for: vsphere events

Configuring NSX Advanced Load Balancer with Tanzu Kubernetes Grid (TKG) on VMware Cloud on AWS

06.22.2021 by William Lam // 1 Comment

One of the exciting new features of the Tanzu Kubernetes Grid (TKG) 1.3 release is the support for NSX Advanced Load Balancer (NSX ALB) as a Layer-4 load balancer solution for your Kubernetes (K8s) based workloads. Most recently, there were a couple of customer inquiries asking whether TKG 1.3 and NSX ALB is supported on VMware Cloud on AWS (VMConAWS) and the answer is yes!


I suspect part of the reason on why this question came up is that it may have been difficult to find a clear support stance for this configuration and although there is some documentation in the AVI Portal for installing NSX ALB on VMConAWS, it certainly was not easy to find. I personally also found the instructions to a be on the lighter side after reading through a few times. Since I already had my TKG Demo Appliance Fling deployed in my VMConAWS SDDC, it was easy enough to un-deploy my existing TKG Management Cluster and set it up with NSX ALB. You can find the detailed instructions below and although the setup of NSX ALB and TKG is similiar to an on-premises vSphere deployment as recently documented by Cormac Hogan, there are still some subtle differences, especially if you are not placing both TKG and NSX ALB systems all on the same single, which you may find in demos 🙂

[Read more...]

Categories // NSX, VMware Cloud on AWS, VMware Tanzu Tags // NSX Advanced Load Balancer, Tanzu Kubernetes Grid, VMware Cloud on AWS

Why does Deploy OVF Template operation show vpxd-extension-[uuid]?

04.26.2021 by William Lam // 4 Comments

A question that I had received awhile ago from a customer was how to identify the specific user(s) who have deployed an OVF/OVA? Customers can easily do this by leveraging vCenter Serve Events, which are extremely rich with information that can help answer this and many other questions you might have in your vSphere enviornment.


The first challenge that you will find is that an OVF/OVA import operation is mapped to a generic vCenter TaskEvent, which will require some additional filtering. Secondly, depending on the method that was used to deploy the OVF/OVA such as the vSphere UI or using Automation tools like OVFTool or PowerCLI, you will also slightly diffrent behaviors in terms of the vCenter Server Events that are emitted.

If you deploy an OVF/OVA using the vSphere UI, you may have noticed there are actually two vCenter tasks which are displayed and running simultaneously as shown in the screenshot above. The first task is called "Import OVF package" and you will see that this task is associated with the actual user who initiated the import. The second task called "Deploy OVF template" is then associated with a vCenter system account that handles the actual deployment which will show up with a vpxd-extension-[uuid] username. This occurs because the user who is performing the import is not interacting directly with with vCenter Server, but rather through the vSphere UI which uses a system account to then communicate the operation to vCenter Server.

For this reason, when an OVF/OVA is imported through the vSphere UI, you will need to look at the TaskEvent and filter for the initial import operation. If an OVF/OVA is imported using the vSphere API using something like OVFTool, PowerCLI or any other vSphere SDK, then you will only see the Deploy OVF Template operation and the user associated with that operation is the person who initiated the import.

Using PowerCLI and the Get-VIEvent cmdlet, we can easily filter out these two types of TaskEvents.

Get-VIEvent | where {$_.GetType().Name -eq "TaskEvent" -and $_.FullFormattedMessage -eq "Task: Import OVF package"}

Info                 : VMware.Vim.TaskInfo
Key                  : 2036862
ChainId              : 2036862
CreatedTime          : 4/23/2021 9:30:36 AM
UserName             : vsphere.local\william
Datacenter           : VMware.Vim.DatacenterEventArgument
ComputeResource      : VMware.Vim.ComputeResourceEventArgument
Host                 :
Vm                   :
Ds                   :
Net                  :
Dvs                  :
FullFormattedMessage : Task: Import OVF package
ChangeTag            :

Get-VIEvent | where {$_.GetType().Name -eq "TaskEvent" -and $_.FullFormattedMessage -eq "Task: Import OVF package"}

Info                 : VMware.Vim.TaskInfo
Key                  : 2036869
ChainId              : 2036869
CreatedTime          : 4/23/2021 9:31:01 AM
UserName             : VSPHERE.LOCAL\vpxd-extension-767f8016-870d-4a98-a457-8247454fa759
Datacenter           : VMware.Vim.DatacenterEventArgument
ComputeResource      : VMware.Vim.ComputeResourceEventArgument
Host                 :
Vm                   :
Ds                   :
Net                  :
Dvs                  :
FullFormattedMessage : Task: Deploy OVF template
ChangeTag            :

Categories // Automation, vSphere Web Client Tags // event, ova, ovf, vsphere web client

VMware Event Broker Appliance (VEBA) v0.6 is now available!

04.20.2021 by William Lam // Leave a Comment

I am super excited today to announce the release of version v0.6 of the VMware Event Broker Appliance (VEBA)! The team and I have been heads down for the past several months working on a number of exciting and brand new capabilities that I think both, existing and new customers, will really enjoy.

In addition to the core team and community contributions, I would also like to welcome and thank two of our newest contributors to the VEBA project, both making significant contributions to our v0.6 release:

  • Denis Chorbadzhiyski (Engineer on the vSphere UI team at VMware)
  • Dimitar Milov (Engineer on the PowerCLI team at VMware)

Release v0.6 is an important milestone for the team and for the VEBA project. VEBA now leverages an end-to-end VMware OSS stack by default, which also provides a strong architectural foundation for future product updates and innovations. We could not be more excited to share this release with our community 🥳 and below are just some of the key feature highlights.

Embedded Knative


Knative is a Kubernetes-based platform to deploy and manage modern serverless workloads. Support for Knative in VEBA was first introduced in our v0.5 release last December and only supported an external Knative deployment. With this latest release, VEBA now supports an embedded Knative deployment which includes the full Knative Serving and Eventing components which is automatically configured within VEBA.

[Read more...]

Categories // Automation, vSphere Tags // Knative, VEBA, VMware Event Broker Appliance

  • « Previous Page
  • 1
  • …
  • 18
  • 19
  • 20
  • 21
  • 22
  • …
  • 36
  • Next Page »

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • VMUG Connect 2025 - Minimal VMware Cloud Foundation (VCF) 5.x in a Box  05/15/2025
  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...