Automation

How to manually install Folding @ Home on VMware Photon OS?

03/22/2020 by William Lam 11 Comments

As many of you may already know, VMware just released the VMware Appliance for Folding @ Home Fling last week and you can check out this blog post A Force for Good: VMware Appliance for Folding @ Home by Amanda Blevins for all the details. For those new to [email protected] and wish to participate, the VMware [email protected] Appliance is highly recommended as it is optimized and makes it very easy to setup and all configurations are driven through OVF properties. We certainly would appreciate it if you supported Team VMware (52737) which is the default team configuration but you can technical specify any valid [email protected] team ID during the deployment wizard.

Early next week, I expect to release another update to the appliance which will include support for vHW11, VMware Fusion and Workstation and several other enhancements and fixes. Having said that, there are a handful of folks who may not be able to use the appliance as-is or prefer to run this on another Hypervisor platform which does not support OVF properties but still wish to support Team VMware's effort with [email protected] For these reasons, here are the instructions for using VMware Photon OS, a free and tiny Linux distribution for running the [email protected] home software.

Disclaimer: VMware does not officially support the Folding At Home application. For more details or questions, please refer to the official [email protected] documentation as well as their technical forums.
[Read more...] about How to manually install Folding @ Home on VMware Photon OS?

Integrating vCenter Event Broker Appliance (VEBA) with vRealize Orchestrator

03/19/2020 by William Lam Leave a Comment

VMware vRealize Orchestrator (vRO) is still used by many of our customers to automate various infrastructure tasks whether that is running it in standalone mode connected to a vCenter Server(s) or powering the extensibility of vRealize Automation. For customers who have already built an extensive collection of vRO workflows, it certainly makes sense that they would like to reuse the Automation they have already created.

For customers that want to easily subscribe to specific vCenter Server event(s) and trigger specific Automation workflows, the vCenter Event Broker Appliance (VEBA) Fling has been a very popular solution. Customers no longer have to write or manage the code to retrieve specific event(s) from vCenter Server, instead they can focus on the really interesting part of the workflow which is automation or "business logic" that does something specific with a given vCenter Server event. Some common examples including notification using Slack or SMS, vSphere automation such as applying a vSphere Tag or hardening a VM configuration to alerting using PagerDuty to ticket creation in ServiceNow or Salesforce.com, the list goes on and on.

The great news is that vRO customers can also benefit from VEBA while leveraging their existing vRO workflows. VEBA can integrate with any vRO workflow by simply having a function, written using any language of your choice, that calls into the vRO's REST API to trigger a specific vRO workflow. To demonstrate this integration, I have built VEBA function using PowerShell which executes a vSphere Tagging vRO workflow which can be found here and below is a video on how this works.

Sneak peek at deploying Tanzu Kubernetes Grid on vSphere & VMware Cloud on AWS

03/16/2020 by William Lam Leave a Comment

Last week, VMware had its huge launch which included VMware Cloud Foundation 4, vSphere 7, vSAN 7 and the brand new VMware Tanzu Portfolio that will help organizations build, run and manage modern applications for their business. Although we still have a couple of more months before general availability, the level of excitement for these upcoming releases was pretty amazing to see on social media, especially for the highly anticipated Kubernetes with vSphere capability, formally known as Project Pacific.

When vSphere 7 is available, Kubernetes with vSphere is just one way in which customers will be able to deploy upstream and conformant Open Source Kubernetes also referred to as Tanzu Kubernetes Grid (TKG). For customers that require a solution today or for those that may not able to upgrade to vSphere 7 immediately, VMware has another option called Tanzu Kubernetes Grid Plus for vSphere and VMware Cloud on AWS which was also announced last week but albeit not many folks took notice.

There are few things worth mentioning about Tanzu Kubernetes Grid Plus:

Tanzu Kubernetes Grid Plus is a new offering that is comprised of the core TKG software and it includes support from VMware's Customer Reliability Engineering (CRE), which is a team made up of Kubernetes Architects that can help customers design and architect their Cloud Native Applications running on the VMware Tanzu Platform
For customers that do not require CRE support and just want standard VMware GSS Support, then you can simply use Tanzu Kubernetes Grid (TKG) which includes VMware Support and Subscription (SnS)
The core TKG software which Tanzu Kubernetes Grid Plus includes can deploy Tanzu Kubernetes Cluster (upstream K8s running in VMs). Customers can already do this right now by using Cluster API (CAPI) and specifically the Cluster API Provider for vSphere (CAPV) which provides lifecycle management of Tanzu Kubernetes Cluster running on any valid vSphere endpoint including VMware Cloud on AWS. The latest CAPV v1alpha3 release also introduces a new workflow that reduces the number of steps compared to v1alpha2 which is now deprecated

For customers that want to further customize how Tanzu Kubernetes Cluster are deployed and configured including tools that they are already using, CAPV will be the most flexible option. Having gone through the CAPV workflows myself, I think it can still be daunting if you are new to this space, not to mention the different CLI tools that you will have to learn to have a successful deployment. Luckily, the VMware TKG team has also been thinking about the overall user experience and how they can build on top of CAPV to provide a much more simpler and more intuitive interface for customers that is just looking for a turnkey option.

Here is a sneak peek (Technical Preview) of the upcoming Tanzu Kubernetes Grid CLI or TKG CLI for short which will make deploying Tanzu Kubernetes Cluster on ANY vSphere endpoint incredibly EASY!

Using vRO REST API to execute a workflow with SDK objects

03/13/2020 by William Lam Leave a Comment

I was working on something last week which involved vRealize Orchestrator and I wanted to execute a vRO worklfow but rather than using the UI, I wanted to use the vRO REST API. Although there are a couple of blog posts such as this one which demonstrates how to use the vRO REST API, they all use a very simple workflow that only contains string inputs. In my opinion, this does not actually reflect practical workflows which usually contains a mix of strings but also SDK-based objects like vSphere VMs, ESXi hosts, Networks, etc.

It actually took me awhile to wrap my head around how to call these more complex workflows using the vRO REST API and after a ton of trial/error and some help from Kasey Linden and one of the vRO Engineers, I now have a method in which users can follow to identify the required payload for a given vRO workflow when using the vRO REST API. The instructions below is using the latest vRO 8.0.1 release which has a new HMTL5 UI, it has been awhile and I am not sure when this new UI was introduced but the instructions may work for older clients but I would recommend standing up the latest version for developing your automation.

Step 1 - Retrieve the vRO workflow ID by selecting the workflow in the vRO UI. In the example below, my Tag a VM workflow ID is 9d95c7f5-a563-413f-af42-fd7e09275216

Big updates to the vCenter Event Broker Appliance (VEBA) Fling

03/10/2020 by William Lam 1 Comment

The vCenter Event Broker Appliance (VEBA) team has been working hard over the last couple of months on some pretty exciting enhancements and today we are pleased to announce the release of VEBA v0.3 which can be download from the VMware Fling site. Although this is a "dot" release, do not let that fool you as this release contains a large number updates including a major re-architecture in how events are consumed and processed at the core of VEBA.

While this re-architecture does introduce some breaking changes, it does unlock a number of new capabilities that our current users have been asking for. It also provides us with a solid foundation for delivering on future enhancements such as multi-vCenter Server support and additional event sources from NSX-T, vSAN and other VMware Cloud Services to just name a few. Today, the "V" in VEBA stands for vCenter, but in the future, I do see it changing to just "VMware" as it can support so many other solutions.

Having said that, some of the breaking changes also improves the overall user experience, especially as it relates to defining and consuming vCenter Server events as well as troubleshooting and debugging. The team is super excited to get this release in the hands of our community and we look forward to hearing your feedback!

What's New:

Introduction of the VMware Event Router which provides a modular and flexible architecture for decoupling the stream "Providers" such as vCenter Server from the actual stream "Processors" like OpenFaaS. More details including its architecture and design can be found here

Automating the creation of NSX-T “Disconnected” Segments for DR testing on VMware Cloud on AWS

03/05/2020 by William Lam 1 Comment

Disaster Recovery (DR) and Disaster Avoidance (DA) on VMware Cloud on AWS is still one of the most popular use case amongst our customers, just second to Datacenter Migration and Evacuation. The VMware Site Recovery service makes it extremely easy and cost effective for customers to protect their critical workloads without having to worry about the underlying infrastructure. Most often, the biggest cost of having a dedicated DR site is the on-going operational and maintenance cost of that infrastructure.

Most recently I have seen several requests come in where customers were looking to streamline their DR testing which is fantastic to hear. Just having a DR solution is not enough, you actually need to exercise it and verify that your workloads and applications are functioning as expected. Today, customers can verify that their applications are functioning as expected by creating NSX-T network segments that are "Disconnected" and then using a VM-based router to provide internal connectivity between these isolated environments.

Here is a screenshot of the VMware Cloud console and under the Networking & Security tab, when creating a new segment you can specify whether the segment is "Connected" (Routed) or "Disconnected".

Obviously, the NSX-T UI is just one way of creating a segment. In fact, most customers that have asked about this is wanting to do this via Automation which not only brings speed to testing but also consistency! With that, I have updated my NSX-T PowerShell Community Module for VMC to include two new updates. If you have never used this VMC module before, please take a look at the Getting Started guide here.