Automation

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.

How to prevent physical CD-ROM from ejecting after installing or upgrading ESXi?

07/15/2019 by William Lam Leave a Comment

While catching up on some news over the weekend, I had noticed a VMware Reddit thread asking a pretty interesting question on how to prevent the physical CD-ROM tray from ejecting after installing or upgrading ESXi? This behavior occurs whether you are using a physical CD-ROM media or a "Virtual" ISO image via an out-of-band interface like an iDRAC or iLO. If you are automating the installation or upgrade using Auto Deploy or network installation such as Kickstart, this is not a problem.

However, I was a bit surprised to hear that this was still a pain point in 2019, as many of the new servers in market do not even include an option for CD-ROM. Some of the suggestions really brought me back to the early 2000's including physically taping up the CD-DROM tray, which I have definitely seen customers doing but this is not a scalable solution and it requires a visit to the datacenter.

One easy solution that I had suggested was to take advantage of ESXi's scripted installation capability also known as Kickstart and use the supported ESXi --noeject option after reboot. Since the install/upgrade was being done manually, the added benefit of this solution is that you can now have it automated 🙂 The other nice thing about this option is that you can specify the kickstart using the default ESXi ISO or you can take it a step further and embed the Kickstart with a custom ESXi ISO.

Configuring Standalone vRealize Orchestrator with VMware Cloud on AWS

07/11/2019 by William Lam Leave a Comment

vRealize Orchestrator (vRO) is powerful workflow engine that many of our customers have been using to automate across a number of different VMware and 3rd party solutions. It is also a foundational component to vRealize Automation (vRA) and it enables our customers to build end-to-end IT and Developer workflows across different Clouds: Private, Public and Hybrid.

It should come as no surprise that existing vRO/vRA customers would like to take advantage of VMware Cloud on AWS and be able to add its vCenter Server instance to vRO for Automation purposes. A few weeks back, I had heard mixed results from our field and customers when attempting to add VMware Cloud on AWS vCenter Server endpoint to vRO. I was actually working with another customer on a related topic and I decided I give this a try in my lab, which was running the standalone vRO 7.5 Appliance.

I did indeed run into a problem when attempting to add vCenter Server as an endpoint in vRO. It turns out this was due to a bug with the vSphere vRO Plugin which has since been resolved with the latest vRO 7.6 release. In any case, there is a simple workaround for customers that are currently not running the latest vRO appliance and you can find the instructions below.

Automated ESXi Installation to USB using Kickstart

07/09/2019 by William Lam 6 Comments

I frequently re-install ESXi on my physical host for various types of testing as I normally work with a number of future releases. Although the process just takes a couple of minutes, having to enter the exact same information each time and also requiring a keyboard and monitor is not really ideal. For the majority, this is really not a problem and manually going through the install workflow is fine for most folks, especially as this is an infrequent operation.

However, with some recent customer conversations, I thought it was worth while to re-visit this topic and demonstrating just how easy it is to automate the installation of ESXi with just a single bootable USB device and embedding an ESXi Kickstart Script. Even for infrequent installation and/or upgrades of ESXi for home labs, this can be a time saver, especially if you do not have monitor and keyboard just lying around. Below are instructions including a reference Kickstart example that folks can use as a starting point. For more advanced automation, please take a look at my ESXI Kickstart Resources as well as the official VMware documentation for ESXi Scripted Installations.