Norway VMware User Group Meetings – May/June 2017

I'm delighted to report that I've been invited to speak at the upcoming Norway VMUG (VMware User Group) meetings. These take place in three different cities over the week of May 29th (week 22), with three meetings in three days. On Tuesday, May 30th, the Oslo VMUG will take place. On May 31st, it's the turn of the Trondheim VMUG and we will finish with the [...]

Read more

Kubernetes on vSphere with kubernetes-anywhere

I already described how you can get started with Kubernetes natively on vSphere using the kube-up/kube-down mechanism. This was pretty straight-forward, but not ideal as it [...]

Storage for containers with VMware? You got it!

Last week during a visit to VMware headquarters in Palo Alto, I had the opportunity to catch up with our engineering team who are responsible for developing storage solutions [...]

A closer look at Rubrik Cloud Data Management v3.1

When I started to write this post, I looked back over my notes from previous conversations with the team at Rubrik and realized that my first conversation with them was almost [...]

Catch me at Cisco Live EMEA 2017 – Berlin

Later on this month, I will be attending my first Cisco Live event. This year, it is taking place in Berlin, Germany. As part of the event, I have the opportunity to deliver a [...]

Another recovery from multiple failures in a vSAN stretched cluster

In a previous post related to multiple failures in a vSAN stretched cluster, we showed that if a failure caused the data components to be out of sync, the most recent copy of [...]

Understanding recovery from multiple failures in a vSAN stretched cluster

Sometime back I wrote an article that described what happens when an object deployed on a vSAN datastore has a policy of Number of Failures to Tolerate set to 1 (FTT=1), and [...]

The continued rise of HCI, and especially vSAN

This morning, twitter is alive with VMware's Q4 2016 results. In a nutshell, its been a phenomenal quarter. Of course, the first thing I wanted to check out was how vSAN did. [...]