There is a new VMware Fling on the block and its pretty powerful. Whenever you thought of reacting based on a VMware vSphere event, the vCenter Event Broker Appliance (vEBA) could be your choice. The excellent team of Michael Gasch and William Lam created that neat appliance.

For the impatient guy – you can download the appliance and the documentation here and just skip this blog post:


If you want to get some real life experience – here we go, basically with the same example adding a tag whenever a virtual machine is powered on:


After downloading the virtual appliance as an ova file, simply deploy it the usual way:

VMware vCenter Event Broker Appliance

To avoid a nasty troubleshooting later on, make sure to set the hostname of the appliance correctly, so it can be resolved. When entering the vCenter address, make sure the vEBA can resolve it.

veba appliance name

I can really recommend making sure that name resolution is set up correctly, as the web applications might not show up. 

Don’t just try the ip address or a different name than used during the deployment.

Therefore, either have DNS setup or use your local host file on the client and the system you’re using to deploy the FaaS stuff (in case its not the same system).

Then it will work as expected.

First start

After powering on the virtual machine, the system will setup itself with a neat Kubernetes cluster inside.


To check the OpenFaaS, simply visit https:// and login using admin and the password you configured during deployment.

You should see an empty OpenFaaS Portal without any functions. We’re going to change that now.

OpenFaaS initial

Install required tools

Next step is the installation of the tools that are required to configure the vCenter Event Broker.


Of course you could also create the tags we’re going to use in the demo yourself and figure out what URN it is, but govc makes it damn simple.


# Download govcwget https://github.com/vmware/govmomi/releases/download/v0.21.0/govc_linux_amd64.gz# extractgunzip govc_linux_amd64.gz# make executablechmod +x govc_linux_amd64.gz# move into a pathsudo mv govc_linux_amd64 /usr/local/bin/govc

You can already set the environment variables we need for govc:

# only required if you have a self-signed certificateexport GOVC_INSECURE=true# set the passwordGOVC_URL="administrator@vsphere.local:whatastrongpassword@vcsa.mydomain.local"


Most people have it probably installed anyway. Just in case, if you’re using Ubuntu or Debian: sudo apt-get install git

OpenFaaS CLI

That one is probably something  rare to have installed, but its easy to get:


# install OpenFaaS clicurl -sSL https://cli.openfaas.com | sudo sh# let’s set the environment variable for the server connection as wellexport OPENFAAS_URL=https://veba.mydomain.local

Create the tag to be used

As we have the govc environment variables already set, let’s check the existing tags first: govc tags.ls

If there is a tag you want to use, get the urn path: govc tags.info

get tag urn

Remember the urn!

If there is no tag you want to use, you can simply create one:

# first create the category govc tags.category.create democat1# then create the tag using that categorygovc tags.create -c democat1 demotag1

When creating the tag you get the urn shown as a result. Copy that one!

Configure OpenFaaS

Next thing to do is to tell OpenFaaS what to do, when a vCenter event happens. The Fling creators Michael Gasch and William Lam were so nice, to create a demo repository as well.

Start by cloning the repository:

git clone https://github.com/embano1/pytagfn

Step 1: change the secret

Enter the vCSA URL, your user account and the password as well as the urn you remembered when creating the tag.

cd pytagfncat
cat vcconfig.toml
server = "vcsa.mydomain.local"
user = "administrator@vsphere.local"
password = "whatastrongpassword"
urn = "urn:vmomi:InventoryServiceTag:d1c0516f-ec8a-4e3d-b064-21dc573e3cf2:GLOBAL"
action = "attach" # or detach

Deploy the secret to OpenFaaS

faas-cli login -p –tls-no-verify

faas-cli secret create vcconfig –from-file=vcconfig.toml –tls-no-verify

If the return code is success, you can delete the vcconfig.toml.

Step 2: configure and deploy the function

simply change the function file within the git project stack.yml to reflect your environment:

cat stack.ymlprovider:
name: faas
gateway: https://veba.mydomain.local
lang: python3
handler: ./pytag-fn
image: embano1/pytag-fn:0.2
write_debug: true
read_debuge: true

  • vcconfig
    topic: drs.vm.powered.on

It’s important to note, that the gateway needs to be set to your vEBA fqdn and the annotations need to contain the event your want to react on. 

vm.powered.on = virtual machine is powered on without DRS

drs.vm.powered.on = virtual machine is powered on by DRS

required if you never used faas-cli before to deploy somethingfaas-cli template pull#deploy the functionfaas deploy -f stack.yml –tls-no-verify

You should be able to see the function in the OpenFaaS portal as well:

OpenFaaS function


When starting a virtual machine a tag should be added automatically by the vCenter Event Broker.

Tag set

That’s a nice start but there are so many other things that can be done using a event-driven approach. Curious what the community is going to build on top of it.


That part can be quite tough. First of all make sure, you follow all the steps carefully, especially the DNS part. Then make sure to chose the correct event based on manual or DRS.

You can also log into the appliance with ssh using the root account and the configured password and running the following command:

kubectl -n openfaas logs deploy/vcenter-connector -f

That way you get information about the events the vCenter connector is receiving from the vCenter. That helps a lot to check, if the connectivity is working well and you react on the correct events.

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials


Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).


immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance


Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.


While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace


No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data


IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.


immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence


CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.


As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.