WilliamLam.com

ESXi on SimplyNUC Ruby and Topaz

by // 5 Comments


Ruby and Topaz is the latest in SimplyNUC's custom lineup of NUC-like systems which they started to build and sell a couple of years ago. The Ruby platform is based on the AMD Ryzen 4000 Series and the Topaz platform is based on Intel 11th Gen Tiger Lake Series.

Given the current global chip shortage that may last a couple more years, it may take some time before everyone can get their hands on either of these platforms, but I have slowly been seeing new inquiries about these platforms as folks are starting to receive their units. Of course, the most popular inquiry that I have received is whether these systems can be used with ESXi? 😀

Topaz

Since Topaz uses the same Intel 11th Gen Tiger Lake CPU, it works exactly the same as the Intel NUC 11 Performance (Panther Canyon) and Intel NUC 11 Pro (Tiger Canyon), which requires the Community Networking Driver for ESXi to enable both the 2.5GbE and 1GbE onboard network adapters when installing ESXi on Topaz. One really nice feature of Topaz is that all three models (i7, i5 and i3) include dual onboard network adapters, where as this option is only available on Intel NUC 11 Pro as an add-on card that must be purchased separately.

Here is screenshot of the latest ESXi 7.0 Update 2 release running on Topaz

Ruby

Although there was quite a bit of community interests in running ESXi on the Ruby platform, I was not particularly optimistic mainly because both the onboard network adapters are from Realtek. Since there are no ESXi networking drivers from Realtek, ESXi would not be able to detect either of the network adapters which is the same behavior that I have seen for other AMD-NUC like kits such as the ASRock Gen 1 and Gen 2 systems.

Unfortunately, there has been no progress with Realtek joining VMware's I/O Vendor Partner (IOVP), which would enable the development of an official network driver for ESXi. Although folks can add networking to these platforms leveraging the USB Network Native Driver for ESXi, it is less than ideal. At this point in time, I can not recommend Ruby or other AMD-based NUCs that uses Realtek-based network adapters.

Here is screenshot of ESXi 7.0 with USB network adapter running on Ruby

IT Admins can be a key enabler to an organizations App Modernization efforts

by // Leave a Comment

Whether you call it Digital Transformation, Digital First, Application Modernization (App Modernization) or some other fancy name, the fact of the matter is, almost every single business is going through some form of transformation to become more competitive in this new digital era. According to a recent survey by VMware, 91% of executives agree their major app initiative in 2021 is to migrate and modernize legacy apps. While this transformation has been going on for some time, the COVID-19 global pandemic has certainly super charged its acceleration and is now a critical imperative for many organizations to be able to create and deliver new digital experiences for their end users.

As part of my role within the VMware Cloud team, I have been taking a closer look at how some of our customers are thinking about their App Modernization strategy and to better understand their overall plan and thought process. With some of the recent customer conversations that I have had, many organizations are just starting their App Modernization journey and one of the challenges that I have observed is simply where and how to get started. There are certainly many different factors that can affect or even slow down these initiatives including organizational structure, tension between lines of businesses, development, operations and IT teams. However, before an organization can decide what application/services they are interested in modernizing, they need to first have a complete understanding of their current application estate.

This understanding is critical before an organization can determine the appropriate modernization strategy (Retain, Rehost, Replatform, Refactor or Retire) for a given application.


[Read more...]

Configuring NSX Advanced Load Balancer with Tanzu Kubernetes Grid (TKG) on VMware Cloud on AWS

by // 1 Comment

One of the exciting new features of the Tanzu Kubernetes Grid (TKG) 1.3 release is the support for NSX Advanced Load Balancer (NSX ALB) as a Layer-4 load balancer solution for your Kubernetes (K8s) based workloads. Most recently, there were a couple of customer inquiries asking whether TKG 1.3 and NSX ALB is supported on VMware Cloud on AWS (VMConAWS) and the answer is yes!


I suspect part of the reason on why this question came up is that it may have been difficult to find a clear support stance for this configuration and although there is some documentation in the AVI Portal for installing NSX ALB on VMConAWS, it certainly was not easy to find. I personally also found the instructions to a be on the lighter side after reading through a few times. Since I already had my TKG Demo Appliance Fling deployed in my VMConAWS SDDC, it was easy enough to un-deploy my existing TKG Management Cluster and set it up with NSX ALB. You can find the detailed instructions below and although the setup of NSX ALB and TKG is similiar to an on-premises vSphere deployment as recently documented by Cormac Hogan, there are still some subtle differences, especially if you are not placing both TKG and NSX ALB systems all on the same single, which you may find in demos 🙂

[Read more...]