I have created a map with every region available for VMware Cloud on AWS (VMC on AWS), Azure VMware Solution (AVS), Google Cloud VMware Engine (GCVE) and Oracle Cloud VMware Solution (OVS). These are cloud services that allow you to run VMware workloads natively on different cloud platforms.

I created the spreadsheet with all the available regions for VMware Cloud on AWS (VMC-A), including the services available there (like VSR, VCDR, etc), node types (i3, i3en, i4i), and other characteristics (like stretched cluster support and compliance). Also add plans from public roadmaps for both AWS and VMC-A.

With the appearance of i4i nodes in VMC, I realized that I was missing a table in which I could compare all available nodes (i3, i3en, i4i) in details.

Well, let's go through the points outlined in Part 1 and Part 2 and look at an example of how testing might look end-to-end.

As I mentioned in the first part of the guide, defining the goals and success criteria is a mandatory step for a successful POC. Of course, success criteria will vary, but they all have something in common — they should follow the S.M.A.R.T. rules:

For more than ten years in the IT industry, I have conducted a lot of tests and proof-of-concepts (POC) of various storage systems. While it was a completely different type of storage — traditional FC-connected SAN storage, NAS, SDS (Software Defined Storage), and HCI (Hyper Converged Infrastructure) platforms, the challenges were nearly the same. And quite often I faced a situation where tests were not anyhow aligned with the business needs and even were technically incorrect which led to the impossibility to deliver any meaningful results.