Please provide your feedback in this short Flings' survey.

VMware Event Broker Appliance

version 0.6.1 — June 16, 2021

Contributors 2
View All
Comments 46
View All

Release Date: October 07, 2019

Summary

The VMware Event Broker Appliance (VEBA) Fling enables customers to unlock the hidden potential of events in their SDDC to easily event-driven automation based on vCenter Server Events and take vCenter Server Events to the next level! Extending vSphere by easily triggering custom or prebuilt actions to deliver powerful integrations within your datacenter across public cloud has never been more easier before.

With this appliance, end-users, partners and independent software vendors only have to write minimal business logic without going through a steep learning curve understanding vSphere APIs. As such, we believe this solution not only offers a better user experience in solving existing problems for vSphere operators. More importantly, it will enable new integration use cases and workflows to grow the vSphere ecosystem and community, similar to what AWS has achieved with AWS Lambda.

Continue the conversation with us on Slack: #vcenter-event-broker-appliance on VMware {code}

Requirements
  • 4 vCPU and 8GB of memory for VMware Event Broker Appliance
  • vCenter Server 6.x or greater
    • Note: The VEBA UI requires vCenter Server 7.0 or greater
  • Account to login to vCenter Server (readOnly is sufficient)
    • (Optional) Account (Register Extension, Update Extension and Manage Plugins privilege) to login to vCenter Server for VEBA UI
Instructions
Please take a look at the VMware Event Broker Appliance site: https://vmweventbroker.io/
Video
Changelog

Known Issues:


1. After deploying VEBA v0.6 using the Embedded Knative deployment model and not enabling VEBA UI, you are unable to browser to /stats, /status and /events endpoint.

Enable SSH to VEBA Appliance and run the following command, if you do NOT see the STATUS column showing Valid HTTPProxy, you will need to apply the following workaround.
kubectl -n vmware-system get httpproxy event-router

NAME           FQDN                          TLS SECRET        STATUS   STATUS DESCRIPTION
event-router   veba.primp-industries.local   eventrouter-tls   valid    Valid HTTPProxy
Step 1) Download ingressroute-gateway-modified.yaml to the VEBA Appliance and replace REPLACE-WITH-VEBA-FQDN with the FQDN of your VEBA Appliance and save the file

Step 2) Apply the modified Ingress YAMl by running the follwoing command:
kubectl -f apply ingressroute-gateway-modified.yaml
Step 3) Verify the HTTPProxy status is now valid by running the following command:
kubectl -n vmware-system get httpproxy event-router