With the release of Photon Controller v0.9, there were a lot of nice new features. My colleague Sarge has a good bit of detail on the new features in his blog post. One of the interesting additions, in my opinion, is the introduction of support for kube-up and kube-down for deploying Kubernetes frameworks (I will have a blog post on this ready to go shortly). If you are a regular reader, you might remember that we had another, more photon controller-centric way of rolling out K8S on Photon Controller that I wrote about here. That was using the “cluster” concept…
Before I get into this post, I do want to highlight that you probably will not do this in any production type environment. The reason why I implemented this, and how this post came about, is because I was helping out with our new edition of the VSAN 6.2. Hands-On-Lab (which should be available imminently by the way). Part of the lab involved demonstrating checksum functionality. Since VSAN has a distributed architecture, there was a requirement to run commands on different hosts. Rather than having lab participants input the password each and every time to run a command on the…
Last week I wrote a post on Horizon View 7 on VSAN. That was all about showing the policies that were associated with the different desktops that can be deployed. I did mention that while one could use vmFork/Instant Clones for desktops, they did not include any sort of persistence. I did add a caveat to say that you could provide persistent storage to these desktops using App Volumes. In this post, I wanted to give some details on App Volumes, and the different moving components one will need if they want to deploy View desktops with App Volumes. However,…
It has been some time since I last looked at Horizon View on Virtual SAN. The last time was when we first released VSAN, back in the 5.5 days. This was with Horizon View 5.3.1, which was the first release that inter-operated with Virtual SAN. At the time, there was some funkiness with policies. View could only use the default policy at the time, and the default policy used to show up as “none” in the UI. The other issue is that you could not change the default policy via the UI, only through CLI commands. Thankfully, things have come…
Earlier this month I had the opportunity to meet with a number of VMware customers in both Singapore and in the UAE. Most of the sessions were enablement and education type sessions, where there was a lot of white-boarding of VSAN (VMware’s hyper-converged infrastructure product) and Virtual Volumes (VVols – Software Defined Storage or SDS for the storage arrays). This wasn’t a sales session; I’m not in sales. The objective of these sessions was simply to educate. I guess when you are immersed in this stuff 24×7, it easy to fall into the trap of believing that everyone is well…
There are many occasions where the information displayed in the vSphere client is not sufficient to display all relevant information about a particular storage device, or indeed to troubleshoot problems related to a storage device. The purpose of this post is to explain some of the most often used ESXCLI commands that I use when trying to determine storage device information, and to troubleshoot a particular device.
A quick reference to vSAN content Books vSAN 8.0 U1 Express Storage Architecture book – paper / kindle (released 25 April 2023) vSAN 7.0 U3 Deep Dive book – paper / kindle (released 09 May 2022) A link to the vSAN 6.7 U1 Deep Dive book Posts New Book: VMware vSAN 8.0U1 Express Storage Architecture now available Dynamic RWX volumes now supported in TKC in vSphere with Tanzu vSAN Data Persistence platform (DPp) Revisited Announcement! vSAN Deep Dive book updated for 7.0 U3 vSAN File Service and K8s PV quota (Video) Adding network permissions to K8s PVs backed by vSAN…