I had someone reach out to me recently, asking for a way to change the policy on a file that was uploaded to a vSAN datastore, e.g. an ISO image. When a file is uploaded to the vSAN datastore, a VM Home namespace object is created. It is into this ‘file system’ type object that the files/ISOs are stored. Initially, I looked at ways to change the VM Home namespace. I looked at various commands to change the policy and I did find some in RVC, the Ruby vSphere Console. Unfortunately all the spbm.namespace_change commands look for a VM as…
I mentioned in a previous post that we have recently released Photon Controller version 1.1, and one of the major enhancements was the inclusion of support for vSAN. I wrote about the steps to do this in the previous post, but now I want to show you how to utilize vSAN storage for the orchestration frameworks (e.g. Kubernetes) that you deploy on top of Photon Controller. In other words, I am going to describe the steps that need to be taken in order for these Kubernetes VMs (master, etcd, workers) to be able to consume the vsanDatastore that is now…
Many of you will have seen the recent announcement for Photon Controller version 1.1. For me, the interesting part of this announcement is the support for vSAN as a storage platform with Photon Controller v1.1. I should think that the first question that those of you are familiar with both vSAN and Photon Controller will ask is “how do I configure vSAN for Photon Controller when there is no vCenter server in the mix?”. This is a very good question, and one which I will highlight in this blog post. There are also a few line items in the release…