VEBA

This is a blog series on the vCenter Event Broker Appliance. The vCenter Event Broker Appliance (VEBA) enables customers to easily create event-driven automation based on vCenter Server Events.

A major component under the hood of this fling is OpenFaaS. I don’t yet have a full handle on everything that OpenFaaS does, but hope to blog more on the appliance’s architecture and a deeper dive into OpenFaaS as this series expands.

I am not a developer! This series is written from the perspective of a system administrator. In the course of developing this series, I have picked up many new skills. I even managed to do my first Open Source contribution – committing changes to the VEBA repository! What you’re seeing is essentially realtime blogging – I’m blogging what I learn as I learn it.

 

Part I – vCenter Event Broker Appliance – Deployment

Part II – vCenter Event Broker Appliance – Sample Code Prereqs

Part III – vCenter Event Broker Appliance – Tags and Clones

Part IV – vCenter Event Broker Appliance – Deploying the First Sample Function

Part V – vCenter Event Broker Appliance – Contributing to the VEBA Project

Part VI – vCenter Event Broker Appliance – Syncing Your Fork

Part VII – vCenter Event Broker Appliance – Deploy the Sample Host Maintenance Function

Part VIII – vCenter Event Broker Appliance – Basic Troubleshooting Techniques

 

Changelog:

2020-01-23 – Updated Part I with new screenshots from the VEBA 0.2 release.