Automation

Listing all Events for vCenter Server

12/16/2019 by William Lam 1 Comment

I had a conversation with one of our VMware Cloud on AWS field leaders a couple of weeks ago at reInvent on his initial experience with the vCenter Event Broker Appliance (VEBA) Fling. There were lots great feedback but one thing that stood out to me which looks to have been a barrier to getting started was being able to figure out a specific vCenter Event and its respective identifier. Although the list of "default" vCenter Events are documented in the vSphere API, it is definitely not the first place most folks would go to look nor is it very intuitive to browse.

To be honest, this is not a unique ask for VEBA. I have also seen this requests come up from customers who are automating vCenter Alarms, which can also be based off of vCenter Events and the same question has come up on before. One challenge with such a request is that the number and the types of vCenter Events will vary from customer to customer depending on the number of 2nd and 3rd party solutions deployed, not to mention it will also vary from version to version. In addition, as a customer, you can also publish your own custom Events into vCenter Server which makes this difficult to provide a single list that would cover all possible scenarios.

Ultimately, this ask is completely valid and I started to look at the vSphere API to see if there was something that could help. It did not take look before I stumbled onto the EventDescription which is part of the EventManager, which provides a nice registry for all currently registered vCenter Events. Time for some Automation 🙂

Configure NSX-T Enhanced Data path / Network Stack (ENS) for Nested ESXi

12/10/2019 by William Lam Leave a Comment

After publishing my Running Nested ESXi, NSX-V or NSX-T on top of NSX-T article which actually turned out to be quite popular, I received an interesting question on whether ENS for NSX-T could also be configured within a Nested ESXi deployment? I was a little familiar with ENS, which I will explain in a second. However, I was not completely sure about the benefits of running ENS in a Nested environment.

With the help from my friend Frank Escaros-Buechsel, who actually works in our NFV group at VMware. Frank helped validate the instructions but he also provided some additional insights on why this could be useful in a lab setup for verifying configuration and behaviors when additional tuning maybe required. If you are NOT running NFV-based workloads, ENS is not something you need to configure when running NSX-T using Nested ESXi.

So what is ENS? Enhanced Network Stack (ENS) also referred to as Enhanced Data Path is an NSX-T capability which was first introduced with NSX-T 2.3. ENS is specifically designed for Network Function Virtualization (NFV) workloads that require a high performance data path. Such workloads include Telco, 5G and IoT based deployments where improved packet throughput is critical for the responsiveness of these applications.

Packer reference for building PhotonOS Virtual Appliance using OVF properties

11/25/2019 by William Lam Leave a Comment

I was introduced to HashiCorp Packer several years back by Timo Tsugliani, who if you are not following on Twitter, you are missing a TON of really useful nuggets which this guys shares both VMware/IT related and cool stuff. I am constantly learning about new things things from Timo and this guys is just a wealth of knowledge if you get the chance to work with him. At the time, I had played with Packer for a bit but did not have an actual use case for it, so I mostly forgot about it.

Fast forward a few years later and with recent projects like the vCenter Event Broker Appliance (VEBA) Fling, I have really spent time learning about Packer in greater depth and I now realize how powerful Packer is for building various artifacts including VMware-based templates that is not only easy but consistently from source control. It took me awhile to get to the aha moment but now I use Packer for so many different things to help simplify my life.

With the recent open sourcing of our VEBA Fling which includes the use of PhotonOS and Packer, I was reminded of a blog series that I did earlier on how to build your own Linux and/or Windows Virtual Appliance using OVF properties (Part 1, Part 2 and Part 3). I realized it would have been useful to have an actual reference implementation on building a very simple PhotonOS Virtual Appliance that exercises some basic OVF properties so folks could quickly get started beyond the manual steps that were documented. I was also motivated by a chat I had with Luc Dekens (Godfather of PowerCLI) last week on some of the Automation he was trying to with PhotonOS and I figured this might be something he and others could also benefit from.

vCenter Event Broker Appliance Updates – VMworld, Fling, Community & Open Source

11/21/2019 by William Lam Leave a Comment

VMworld

At VMworld Barcelona, Michael Gasch and I had the privilege of presenting our #CODE1379E "If This Then That" for vSphere - The Power of Event Driven Automation session. The room was completely packed for a 9am session on Thursday after the big VMworld Party and we just wanted to thank everyone who attended the session and for those that came up to talk to us afterwards. We really had no idea how the session would be received but from the feedback, tweets and DM's we have received and continue to receive, it looks like the session really resonated with customers. In case you missed the session or could not attend VMworld, the session was recorded and is actually available for everyone to view. You just need to sign in with a free VMworld account.

VMware Fling

For those who attended the VMworld session in person, there was a nice surprise at the very end, which I think may be a VMworld first. Michael and I have been working on a side project in our spare time called the vCenter Event Broker Appliance or VEBA for short. This solution enables customers to easily create Event Driven Automation based on vCenter Server Events and rather than just showing off some cool demos, we wanted to leave the audience with something they can actually use right now!

With a little chant that was started by Emad Younis (this was NOT planned), the audience had spoken and wanted us to publish the planned VMware Fling which we were going to release in the coming days since we had just finished the process literally the week of VMworld. I figure its VMworld, this is what customers, partners and colleagues come here for and with a click of a button and crossing my fingers, the vCenter Event Broker Appliance Fling went LIVE.

How to debug NSX-T API Automation with PowerCLI?

10/25/2019 by William Lam Leave a Comment

I recently needed to deploy the latest version of NSX-T (2.5) for some work I was doing with Project Pacific and of course it was related to Automation 🙂 It has been some time since I have touched the NSX-T Manager API (2.0) and although most of my existing code still worked, there were some things that broke due to API deprecation and also net new functionality that I needed to use.

I normally use PowerCLI for my Automation work and/or for prototyping purposes, not only is it easy to do but PowerCLI is still one of the most popular tool used by our customers and it means that they can easily benefit from my work. However, one of my pet peeves when working with the NSX-T APIs and PowerCLI is simply the lack of useful error messages. Here is the generic error message that you would normally see even checking the $Error[0].Exception.ServerError variable, it generally does not contain anything useful or actionable.

A server error occurred: 'com.vmware.vapi.std.errors.invalid_request': . Check $Error[0].Exception.ServerError for more details.

Here is a concrete example where I am attempting to create a new Transport Zone but I am purposing leaving out a required parameter and as you can see from the output, the same generic error message is shown and not very actionable.

I normally debug NSX-T API issue whether it is a syntax or usage problem by SSH'ing to the NSX-T Manager and monitoring the actual API logs to figure out what is actually going. It usually has exactly what I am looking for in terms of the actual server error message along with details on how to fix the problem.

Automate disabling @channel & @here notifications using private Slack API

10/17/2019 by William Lam Leave a Comment

Slack is a popular communication and collaboration tool which has been adopted by many organizations including the one I work for. I am a fan of Slack and use it on a regular basis. Like most users, I am a member of several different workspaces and a ton of different channels.

I think most Slack users would agree that one of the most commonly miss-used feature of Slack is the @channel and @here notifications which allows a user to broadcast a message that notifies everyone within a specific channel. I most often see this when a user is looking for immediate assistance and think that this is the best way to get help, it is not. In some cases, inpatient uses end up spamming multiple channels which can have up to 1K+ members! As you can imagine, this type of behavior is usually not well received.

This is the modern day "reply-all" email storms that I am sure many of you have at experienced at least once if not many more times within your organization 🙂 Slack does provide a few ways of disabling notification, either within the workspace but this would disable the feature completely and I do see value in this feature when used correctly or disabling notifications on a per-channel basis as shown in the screenshot below.