To coincide with a new release of vSphere 7.0U1 and vSAN 7.0U1, there is also a new release of VMware Cloud Foundation releasing. This is VCF version 4.1. In this release, as well as a bunch of updates to the versions of the various VMware products that make up the VCF bill of materials, there are also some nice new enhancements. In this post, I’ll highlight the big features that I know a number of customers are interested in. Support for vVols as a Principal Storage for Workload Domains Virtual Volumes (vVols) is gaining more and more traction among VMware…
With the release of vSphere 7.0, we also announced enhancements to our Cloud Native Storage (CNS) offering. One of the new features that we now offer in vSphere 7.0 is the ability to provision Virtual Volumes (vVols) to back Kubernetes Persistent Volumes (PVs) via our updated version of the vSphere Container Storage Interface (CSI) driver. In this post, I will walk through the steps involved in consuming vVols via Kubernetes manifest files when dynamically provisioning PVs. I will also show some enhancements to our CNS UI in vSphere 7.0 so that you can easily identify vVol backed PVs. Step 1…
Regular readers will be aware that I have been spending a lot of my time on Cloud Native Storage topics these days, whether it is bubbling up how Kubernetes clusters are consuming vSphere storage through our new CNS feature in vSphere 6.7U3, or using Velero to do lots of things like backups/restores/application mobility. However something I have been passionate about for quite a number of years now is our Virtual Volumes (vVols) feature. And while it has been rather quiet over the past couple of years, I was thrilled to see us deliver a tech preview for supporting Site Recovery…
I am in the very fortunate position of having access to a Pure Storage array, and this has been recently updated to support Virtual Volumes. With my new 6.7 vSphere cluster, I finally found some time to take a closer look at Virtual Volume (VVol) snapshots on the Pure array, something that I have been meaning to do for some time. For those of you who are new to Virtual Volumes (VVols), one of the major advantages is the granularity at which certain operations can now be done. In the past, we were always dealing with data services at the…
Hot on the heels on Pure Storage’s recent announcement on Virtual Volume (VVol) support, I wanted to take a closer look at their VVol implementation for myself. Thanks to the support team over at Pure, they were able to very quickly update our lab array to the latest release that has support for VVols. Once this upgrade was complete (which was all done remotely), I wanted to go ahead and register the VASA provider with my vCenter server. You can read more about the role of VASA here. I wanted to step through the process manually, rather than use the…
There was lots of big news yesterday from our friends over at Pure Storage. First of all, we had an announcement about their Virtual Volume (VVol) implementation going GA. This is very exciting for me, and I look forward to testing it out in our lab. The implementation is a VASA 3.0 implementation, which means support for array based replication (ABR). My good pal Pete Fletcha did a great write-up on the announcement here. And of course, Cody Hosterman of Pure Storage also gives us his low-down on what this VVol implementation means to him. One thing is for sure,…
One of the great things about presenting at VMware User Group meetings is actually talking to customers and finding out about what their pain points are, and how VMware can improve on our products and features. At the most recent VMUG I attended (in Poland), I was asked a question about storage policies, and if there was a way to allow some users to use some policies, and other users to use a different policy. Unfortunately there is no permissions associated with policies at this time, so any user can select any policy. With that in mind, I had a…