vSAN 6.7 U1 Deep Dive book now available in Traditional Chinese

A very short post to highlight to my Asian readers that the vSAN 6.7 U1 Deep Dive book has now been translated into Traditional Chinese by Taiwanese company DrMaster. If you are interested in picking up a copy, we have been provided with the following links to web sites where you can purchase the book. This is opportune timing, as VMware has only just announced the newest release of vSAN, version 6.7 U3. Here are the links provided by DrMaster to online book stores in Asia where the book can be found. Tenlong Computer Books. This is the most famous…

Celebrating 20,000 #vSAN Customers – Thank you

Wow – more than 20,000 vSAN customers. What an amazing journey it has been. If you haven’t seen it, vSAN license bookings grew over 50% year-over-year in Q1 with a total customer count growing to over 20,000 (seekingalpha.com). Now we need to keep the pace and, as Duncan put it, remain the number 1 player in the hyperconverged and hybrid cloud world! As a sort of thank you to everyone who helped make this happen,  Duncan and I have decided to lower the price of our vSAN Deep Dive book for 1 week. So, until Friday, June 7th, we have…

Fun with PKS, K8s, MongoDB Helm Charts and vSAN

I’ve been spending a bit of time lately look at our Heptio Velero product, and how it works with various cloud native applications. Next application on my list is MongoDB, another NoSQL database. I looked at various deployment mechanisms for MongoDB, and it seems that using Helm Charts is the most popular approach. This led me to the Bitnami MongoDB Stack Chart GitHub Repo. At this point, I did spin my wheels a little trying to get MongoDB stood up. In this post, I’ll talk through some of the gotchas I encountered. Once again, my environment is vSphere 6.7 and…

vSAN Erasure Coding Failure Handling

I had a very interesting question recently about how vSAN handles a failure in an object that is running with an erasure coding configuration. In the case of vSAN this is either a RAID-5 or a RAID-6. On vSAN, a RAID-5 is implemented with 3 data segments and 1 parity segment (3+1), with parity striped across all four components. RAID-6 is implemented as 4 data segments and 2 parity segments (4+2), again with the parity striped across all of the six components. So what happens when we need to continue writing to one of these objects after a component/segment has…

VMware vSAN 6.7U1 deep dive book now available

I am delighted to announce the availability of our newly updated VMware vSAN 6.7U1 Deep Dive book. This is the 3rd edition of the book. As the title states, this book’s content has been updated to include information about the latest version of vSAN, which is of course 6.7U1. Much thanks to my good friend and co-author, Duncan Epping. As well as doing his share of the content, Duncan took care of all of the admin to get the book available online, something I have no clue about. Thanks man! Also a great big shout out to both Pete Koehler…

Kubernetes, Hadoop, Persistent Volumes and vSAN

At VMworld 2018, one of the sessions I presented on was running Kubernetes on vSphere, and specifically using vSAN for persistent storage. In that presentation (which you can find here), I used Hadoop as a specific example, primarily because there are a number of moving parts to Hadoop. For example, there is the concept of Namenode and a Datanode. Put simply, a Namenode provides the lookup for blocks, whereas Datanodes store the actual blocks of data. Namenodes can be configured in a HA pair with a standby Namenode, but this requires a lot more configuration and resources, and introduces additional…

vSAN 6.7U1 – Capacity History – Unable to query charts data

A very quick heads-up to let you know about an issue some of us experienced with vSAN 6.7U1 and about how to resolve it. We noticed that after upgrading to vSAN 6.7U1, the new Capacity History view did not work. However brand new installs of 6.7U1 worked just fine. The error that one gets from trying to look at the capacity history is “Unable to query charts data for capacity history” as shown below: I’m pleased to report that we have a solution for this issue already. It was caused by an inability to update the database schema in the…