A couple of weeks ago I delivered a brief webcast presentation on Storage Policy-Based Management and its use across mixed vSphere storage environments. This has been one of my favorite topics for a couple of years. I have spent a lot of time developing guidelines for different scenarios so that vSphere customers can see and understand the value of what this policy framework introduces for the management, and consumption of storage.
In this brief presentation, I covered some basic concepts of the policy framework and how SPBM is designed to work. Today, all of the Software-Defined Storage technologies supported in vSphere (vSAN, VVols, VAIO) natively support and depend on SPBM as part of their technological value proposition, but more importantly from an operational efficiency standpoint as well.
New features like vSphere Encryption and traditional vSphere storage features like Storage I/O Control (SIOC) are now being delivered via policies. In the presentation below, I walk through a couple of demonstrations that include building policies for a vSphere infrastructure composed of mixed storage abstractions, vendor solution, and management portals (vSohere Web Client, and vRealize Automation).
In my last point in the demonstration, I reintroduce the case for SPBM utilized in cloud type of infrastructures with mixed storage self-serve storage offerings. SPBM can be used with traditional vSphere datastore constructs such as NFS, and VMFS and it can tie it into cloud scale type production environments with vRealize Automation and event OpenStack.
For future updates on Virtual SAN (VSAN), vSphere Virtual Volumes (VVol) and other Storage and Availability technologies, as well as vSphere Integrated OpenStack (VIO), and Cloud-Native Applications (CNA) be sure to follow me on Twitter: @PunchingClouds.