WilliamLam.com

vSphere Event-Driven Automation using Tanzu Application Platform (TAP) on Tanzu Community Edition

by // 2 Comments

Right before the holiday, I had spent some time exploring Tanzu Application Platform (TAP), which also recently GA'ed. TAP provides developers with an application-aware platform that focuses on making the developer experience easy for developing, building and running applications on Kubernetes.


If you are interested in a quick technical deep dive into TAP, check out this video by Scott Sisil, introducing TAP:

One of the core components of TAP is the Cloud Native Runtime (CNR), which is VMware's commercial offering of the popular open source project Knative. The VMware Event Broker Appliance (VEBA) project also makes use of Knative as our backend to provide customers with an event-driven automation solution.

Early on in the VEBA project, we knew that we wanted to develop and innovate with the community in the open but we also understood there would be users who would want an officially supported offering that they can call or file support requests when needed. Early last year, Michael Gasch, the lead architect for VEBA started to port the code from the VMware Event Router, which is the heart of VEBA into CNR's Tanzu Sources for vSphere and start unifying the two code bases. The goal is to ensure that users of the open source project VEBA will also have a consistent user experience in terms of function deployment when using the commercial offering.

As shared back in Dec, I was able to successfully deploy TAP, CNR and Sources for vSphere all running in Tanzu Community Edition (TCE), which is a completely free Enterprise-grade Kubernetes available to anyone in the community to use. For those interested, you can find the instructions below on how to deploy and configure TAP to enable vSphere event-driven automation capabilities for your infrastructure. If you are interested in deploying this using the Tanzu Kubernetes Grid (TKG) Service, check out this other recent blog post that outlines the specific steps.

[Read more...]

vSphere Event-Driven Automation using Tanzu Application Platform (TAP) on Tanzu Kubernetes Grid Service

by // Leave a Comment

Right before the holiday, I had spent some time exploring Tanzu Application Platform (TAP), which also recently GA'ed. TAP provides developers with an application-aware platform that focuses on making the developer experience easy for developing, building and running applications on Kubernetes.


If you are interested in a quick technical deep dive into TAP, check out this video by Scott Sisil, introducing TAP:

One of the core components of TAP is the Cloud Native Runtime (CNR), which is VMware's commercial offering of the popular open source project Knative. The VMware Event Broker Appliance (VEBA) project also makes use of Knative as our backend to provide customers with an event-driven automation solution.

Early on in the VEBA project, we knew that we wanted to develop and innovate with the community in the open but we also understood there would be users who would want an officially supported offering that they can call or file support requests when needed. Early last year, Michael Gasch, the lead architect for VEBA started to port the code from the VMware Event Router, which is the heart of VEBA into CNR's Tanzu Sources for vSphere and start unifying the two code bases. The goal is to ensure that users of the open source project VEBA will also have a consistent user experience in terms of function deployment when using the commercial offering.

As shared back in Dec, I was able to successfully deploy TAP, CNR and Sources for vSphere all running on our Tanzu Kubernetes Grid Service which includes both our on-premises offering called vSphere with Tanzu and our managed service offering called VMware Cloud with Tanzu services. For those interested, you can find the instructions below on how to deploy and configure TAP to enable vSphere event-driven automation capabilities for your infrastructure.

[Read more...]

VMware Event Broker Appliance (VEBA) v0.7.1

by // 2 Comments

The VMware Event Broker Appliance (VEBA) team is excited to share that we have just delivered our final VEBA release for 2021, VEBA v0.7.1, which is a minor update that contains a couple of fixes that was observed in the original v0.7 release. With the recent log4j vulnerability disclosure, I also want to mention that VEBA is NOT affected.

As 2021 starts to wrap up, I also wanted to take this opportunity and thank everyone in our VEBA community for your continued support and engagement. Our public VEBA Slack channel has more than doubled in size since launching and we just had our 250th user join this week! We also recently launched our VEBA Monthly Community Call, where folks can bring questions and use cases to discuss with others on how best to achieve certain outcomes. All sessions are recorded including meeting notes, which you can review in case you can not make. The community call occurs on the last Tuesday of each month at 8am PST (we will not be doing Dec call due to upcoming holidays).

Lastly, I could not be more excited for VEBA in 2022 and hopefully we will be able to share more news in the upcoming year. If you still have not heard of VEBA before and wish to learn more, I highly encourage you check out our VMworld 2021 session VEBA Revolutions - Unleashing the Power of Event-Driven Automation #CODE2773 and start on your Event-Driven Automation journey with our community.

Have a happy and safe holiday everyone! ☃️🥳🍾

What's New

Note: If you currently have vCenter Server 7.0 Update 3 installed, you may run into an issue when using the VEBA vSphere UI plugin. This is currently a known issue which will be fixed in a future vCenter Server update, however you can follow this blog post for a workaround.

New VEBA Logo

Last but not least, we also want to share that the VEBA project now has an official VMware logo! A big thanks to the VMware Brand team who helped create our logo in such a short amount of time, it turned out amazing and conceptualizes VEBA in such a simple, yet powerful graphic 👌


We certainly will miss the Otto the Orca as the "unofficial" VEBA logo that was designed and created by fellow VEBA teammate Robert Guske.