{"id":443,"date":"2023-06-30T17:09:22","date_gmt":"2023-06-30T17:09:22","guid":{"rendered":"https:\/\/tristantodd.com\/?p=443"},"modified":"2023-06-30T17:12:51","modified_gmt":"2023-06-30T17:12:51","slug":"why-vvols-in-2023","status":"publish","type":"post","link":"https:\/\/tristantodd.com\/?p=443","title":{"rendered":"Why vVols in 2023?"},"content":{"rendered":"\n

Remember when those of use in the VDI space used to joke around about \u201cthis is the year of the desktop!\u201d? Well, for the last 10 months I\u2019ve been very busy talking about vVols in a variety of forums. It is a wildly popular topic and i\u2019m seeing a surge in adoption (shoutout to my awesome customers and partners!) So – why are vVols a hot topic right now?<\/p>\n\n\n\n

Let’s realize some value of a core vSphere feature<\/strong><\/p>\n\n\n\n

Development of vVols started back in 2011 and was announced at VMWorld in 2013. vVols were then shipped with vSphere 6.0 in 2015. This vSphere-Land post provides a very nice overview of the history of vVols – https:\/\/tinyurl.com\/bdza3tbu<\/a><\/p>\n\n\n\n

\"\"
Basic vVols Logical View<\/figcaption><\/figure>\n\n\n\n

So\u2026for the last 8 years, vVols have been part of the core SDDC stack. The Storage Policy Based Management (SPBM) policy engine has been a mainstream feature in vSphere for a significant amount of time. Numerous best-in-class storage and data protection solutions now support vVols. We can\u2019t consider vVols to be a fringe or nouveau feature any longer. So, now in 2023, doesn\u2019t it make sense to deploy the powerful capabilities in this core feature? Let\u2019s talk about some of the features that are especially relevant today.<\/p>\n\n\n\n

vVols Technology has matured<\/strong><\/p>\n\n\n\n

Let\u2019s face it – when vVols were first launched, things were a little rough around the edges. Scale and performance were a problem. Solutions integrations were sparse. And there weren\u2019t a lot of platforms that supported vVols. <\/p>\n\n\n\n

In 2023, things have evolved. The performance\/scale\/resiliency attributes in vSphere (especially in vSphere 8u1) are very refined. Many of the core innovations in vSphere 8<\/a> are focused on vVols and the roadmap looks amazing. There are numerous great storage platforms out there that support vVols. Lots of amazing backup solutions are vVols ready. And most industry-leading monitoring\/reporting solutions support vVols. <\/p>\n\n\n\n

Efficiency through Automation<\/strong><\/p>\n\n\n\n

I talk to numerous IT organizations every week and I consistently hear that teams are interested in automation as a means to add efficiency to routine operations. vVols and SPBM offer built-in SDDC automation where you can easily and flexibly apply data service policies to VMs and even individual disks. This means that you can create and enforce consistent SLAs easily, AND you can rely on vSphere policy enforcement to keep things tight. Changing data services policies (to adapt to a changing set of of business requirements) is as easy as applying a new SPBM policy! And if SPBM can\u2019t do it, it is easy to leverage PowerCLI and REST API to operationalize your blueprints.<\/p>\n\n\n\n

\"\"
PowerCLI and vVols automation magic<\/figcaption><\/figure>\n\n\n\n

Operational Rigor and Consistency<\/strong><\/p>\n\n\n\n

From accurate workload placement to consistent policy-based assignment of data protection services, vVols SPBM can lead to more consistent services that can lead to greater consistency and uniformity of services. This leads to a consistent SDDC foundation and better shot at true intrinsic security. Entropy and sloppiness in storage service configurations can make it harder to spot data service policy violations. An application server that is classified as production could be better protected from malware attacks if a \u201csnapshot locally every hour\u201d policy is enforced. And SPBM and vVols make this easy!<\/p>\n\n\n\n

\"\"
Myriad options available with SPBM Policies!<\/figcaption><\/figure>\n\n\n\n

Silos as barriers<\/strong><\/p>\n\n\n\n

The divide between storage and virtualization teams is much less today. In the good old days, there was a organizational fence between storage and virtualization teams. These days I\u2019m seeing fewer and fewer operational silos between storage and virtualization teams. The operational aspects of vVols shift the way that storage capacity is consumed and the way that data services policies are assigned. Virtualization ops teams are put in direct control of many functions that were the responsibility of the storage teams in the VMFS age. As IT organizations become less specialized, it is far easier for vVols to be introduced without causing tension and angst in IT camps and silos.<\/p>\n\n\n\n

\"\"
Are the days of tech silos over?<\/figcaption><\/figure>\n\n\n\n

Increased efficiency at scale<\/strong><\/p>\n\n\n\n

With vVols we can enjoy better efficiency in allocating capacity with vVols (provision required vDisk capacity and not a bunch of VMFS overhead). It is not uncommon to see a 10 to 15% reduction in capacity consumption when the same workload is moved from VMFS to vVols. I see this routinely when working with small and large customers. <\/p>\n\n\n\n

The performance benefits of vVols can also be significant. with storage provider based snapshots is huge. This VMware whitepaper provides weighty arguments in favor of vVols based storage if virtual machine snapshots are employed – https:\/\/tinyurl.com\/2adjn4eu<\/a> The comparison graphs that show VMFS versus vVols performance when vVols are present is eye-opening! Other performance benefits can come from thinks like vDisk level QoS policies, where IO or throughput limits can be set and enforced. What a great way to reduce noisy neighbor issues!<\/p>\n\n\n\n

\"\"
Seriously – you need to read this amazing VMware paper!<\/figcaption><\/figure>\n\n\n\n

Telemetry and metrics<\/strong><\/p>\n\n\n\n

This is one of things that I find the most compelling about vVols in 2023. I love me some data and vVols lets us derive performance and capacity insights at a VM and vDisk level of granularity. With VMFS, we can\u2019t easily see back-end performance and capacity utilization statistics or trends when tens or hundreds of VMs are deployed on a shared datastore. Since vVols operate as individual volumes, we get to enjoy more granular views of storage stats. And with modern data services platforms like Pure Storage, we present these statistics right in the vSphere Web Client via our plugin integration. This means that an operator doesn\u2019t need to access a backend storage interface to consume these stats – they are right there in the vCenter UI and available via REST API as well!<\/p>\n\n\n\n

\"\"
vDisk level telemetry is a game changer!<\/figcaption><\/figure>\n\n\n\n

Summary<\/strong><\/p>\n\n\n\n

So, why are we still talking about vVols in 2023? <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The efficiency, automation, and telemetry benefits that come with vVols help us more easily adopt a cloud operating model. In the same way that large service providers and public clouds operate efficiently, consistently, and securely – modern IT organizations desire the same operational capabilities. vVols have matured and are now considered as a core vSphere feature. It\u2019s a great time to take \u2018em for a spin!<\/p>\n","protected":false},"excerpt":{"rendered":"

Remember when those of use in the VDI space used to joke around about \u201cthis is the year of the desktop!\u201d? Well, for the last 10 months I\u2019ve been very busy talking about vVols in a variety of forums. It is a wildly popular topic and i\u2019m seeing a surge in adoption (shoutout to my … <\/p>\n

Continue reading<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"amp_status":"","footnotes":""},"categories":[19,1,20],"tags":[],"class_list":["post-443","post","type-post","status-publish","format-standard","hentry","category-tech","category-uncategorized","category-vsphere","item-wrap"],"_links":{"self":[{"href":"https:\/\/tristantodd.com\/index.php?rest_route=\/wp\/v2\/posts\/443","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tristantodd.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tristantodd.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tristantodd.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/tristantodd.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=443"}],"version-history":[{"count":2,"href":"https:\/\/tristantodd.com\/index.php?rest_route=\/wp\/v2\/posts\/443\/revisions"}],"predecessor-version":[{"id":461,"href":"https:\/\/tristantodd.com\/index.php?rest_route=\/wp\/v2\/posts\/443\/revisions\/461"}],"wp:attachment":[{"href":"https:\/\/tristantodd.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=443"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tristantodd.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=443"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tristantodd.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=443"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}