VMware Event Broker Appliance
Table of Contents
Getting Started
Visit our website vmweventbroker.io and explore our documentation to get started quickly.
Overview
The VMware Event Broker
Appliance
Fling enables customers to unlock the hidden potential of events in their SDDC
to easily create event-driven
automation. The
VMware Event Broker Appliance includes support for vCenter Server and VMware
Horizon events as well as any valid CloudEvent through the native webhook
event provider. Easily triggering custom or prebuilt actions to deliver powerful
integrations within your datacenter across public cloud has never been more
easier before. A detailed list of use cases and possibilities with VMware Event
Broker Appliance is available here
With this solution, end-users, partners and independent software vendors only have to write minimal business logic without going through a steep learning curve understanding the vSphere or Horizon APIs. As such, we believe this solution not only offers a better user experience in solving existing problems for VI/Cloud Admins, SRE/Operators, Automation Engineers and 3rd Party Vendors. More importantly, it will enable new integration use cases and workflows to grow the VMware ecosystem and community, similar to what AWS has achieved with AWS Lambda.
Learn more about the VMware Event Broker Appliance here.
Additional resources can be found here and some quick references are highlighted below
- Watch Michael Gasch and William Lam of VMware present a session at VMworld 2019 called "If This Then That" for vSphere- The Power of Event-Driven Automation and at VMworld 2020 "VEBA and the Power of Event-Driven Automation – Reloaded"(free VMworld account login is required to view).
- Watch Partheeban Kandasamy (PK), Michael Gasch and William Lam present about Unlocking the potential of Events for SDDC automation
- Watch Michael Gasch and William
Lam present the latest updates on VEBA at the
recent Omaha
VMUG
(password:
MYN%0k9)
Architecture
VMware Event Broker Appliance is provided as a Virtual Appliance that can be deployed to any vSphere-based infrastructure, including an on-premises and/or any public cloud environment, running on vSphere such as VMware Cloud on AWS or VMware Cloud on Dell-EMC.
The VMware Event Broker Appliance follows a highly modular approach, using Kubernetes and containers as an abstraction layer between the base operating system (Photon OS) and the required application services. Currently the following components are used in the appliance:
For more details about the individual components and how they are used in the VMware Event Broker Appliance, please see the Architecture page.
Getting in touch
Community Calls
Public VEBA community meetings are held every last Tuesday in the month at 8AM Pacific Time (US).
- Zoom: https://via.vmw.com/veba-ama
- Note: The meeting is password protected to mitigate abuse. Please join the VEBA Slack channel to receive the Zoom password or contact us in case of issues.
- Notes: https://via.vmw.com/veba-notes
Other Channels
Feel free to reach out to Team #VEBA and the community via:
- Email us at [email protected]
- Join our users on slack #vcenter-event-broker-appliance which is part of the VMware {Code} Slack instance
- Follow for updates @VMWEventBroker
Contributing
The VMware Event Broker Appliance team welcomes contributions from the community.
To help you get started making contributions to VMware Event Broker Appliance, we have collected some helpful best practices in the Contributing guidelines.
Before submitting a pull request, please make sure that your change satisfies the requirements specified here
License
VMware Event Broker Appliance is available under the BSD-2 license. Please see LICENSE.txt.