<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article The future of VMware storage - vVol demo in Around the Storage Block Blog</title>
    <link>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/ba-p/123309</link>
    <description>&lt;p&gt;&lt;font size="3"&gt;&lt;img src="/t5/image/serverpage/image-id/12665i1A24103FE4BC3DE6/image-size/original?v=mpbl-1&amp;amp;px=-1" border="0" alt="Headshot 100X100.jpg" title="Headshot 100X100.jpg" width="100" height="100" align="left" /&gt;By Calvin Zito, @&lt;u&gt;&lt;strong&gt;&lt;a title="Follow me on Twitter" href="http://twitter.com/HPStorageGuy" target="_blank"&gt;HPStorageGuy&lt;/a&gt;&lt;/strong&gt;&lt;/u&gt;&lt;strong&gt;&amp;nbsp;&amp;nbsp;&lt;/strong&gt;&lt;u&gt;&lt;strong&gt;&lt;img src="/t5/image/serverpage/image-id/13027i3E6867B5EA554E19/image-size/original?v=mpbl-1&amp;amp;px=-1" border="0" alt="vexpert 2012 logo.gif" title="vexpert 2012 logo.gif" width="225" height="33" align="middle" /&gt;&lt;/strong&gt;&lt;/u&gt;&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;font size="3"&gt;Last year at VMworld, VMware did an NDA&amp;nbsp;technology preview for partners about their vision for the future of storage - something they called vVols (virtual volumes).&amp;nbsp; While VMware is allowing partners working with them to talk about it and demonstrate early functionality, I want to be clear - this is still a technology preview and neither VMware nor HP is making any commitments on delivering this.&amp;nbsp; So with that disclosure, let me tell you a bit about what it is.&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;font size="3"&gt;&lt;strong&gt;Intro to VMware vVol&lt;/strong&gt; &lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&lt;font size="3"&gt;For awhile now, HP Storage has been working with VMware as a design partner to define and develop a VM-granular storage architecture to potentially replace vSphere’s VMFS/datastore model. This new model is called VMware Virtual Volumes (vVols). Virtual Volumes introduces a 1:1 mapping of VMs (more specifically VMDKs or VM LUNs) to storage volumes—in other words, each VM will be associated with its own, unique storage volume. &lt;/font&gt;&lt;font size="3"&gt;With vVols we could finally have the VMDK representation in vSphere match the representation on storage. &lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;font size="3"&gt;As a result, the storage system could now have the ability to operate at the same level of granularity as vSphere, which means that vSphere could better leverage, and take advantage of, the native strengths and capabilities of modern, intelligent storage arrays, like HP 3PAR.&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;font size="3"&gt;Again, I want to be clear that this is a possible future technology from VMware. Essentially, vVols could replace VMFS as we know it today and the concept of datastore. The key thing is that a vVol allows for per-VM data services on the storage array and vSphere hosts. Data services that inherently run more efficiently on intelligent storage, which owns and stores all of our critical data, could include:&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;font size="2"&gt;Replication&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Snaps&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Caching&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Encryption&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Security&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;and more&lt;/font&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;&lt;font size="3"&gt;Why vVol?&lt;/font&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;font size="3"&gt;I think the big thing VMware and storage partners like HP want to overcome is the inefficiencies and the challenges that exist today as a result of working at the LUN or volume level with vSphere. Despite all the advances that have been made, when a VM and VMDK is the unit of data management, a LUN is too coarse to gain the efficiency and flexibility customers need.&amp;nbsp;The granularity mismatch between vSphere and storage systems needs to be resolved. Enter vVols.&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;font size="3"&gt;What are the benefits&amp;nbsp;&lt;/font&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;font size="3"&gt;Here's a summary of what vVols will do:&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;font size="2"&gt;Enables VMware to offload per VMDK-level operations to storage systems&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Enables storage systems to provide data services to individual applications and VM’s&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Enables application profile-based provisioning, monitoring and management of VM Volumes via vSphere and VASA&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Levels the playing field in how storage is deployed, regardless of protocol -- with vVols, storage systems create and manage VMDK objects the same way regardless of the protocol frontend (FC, iSCSI, NFS) that is used to export said objects&lt;/font&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;&lt;font size="3"&gt;Seeing is believing&lt;/font&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;font size="3"&gt;What better way to help you see all this but to share a video demo, so here's a demo showing several things&amp;nbsp;using vVols and HP&amp;nbsp;3PAR:&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;font size="2"&gt;Create virtual volume VM on HP 3PAR&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Clone a virtual volume VM&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Create virtual volume VM snapshot (array-based&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Recover a virtual volume VM from a 3PAR snapshot&lt;/font&gt;&lt;/li&gt;
&lt;li&gt;&lt;font size="2"&gt;Delete the virtual volume VM snapshot&lt;/font&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;font size="3"&gt;Here's the video&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;iframe src="http://www.youtube.com/embed/KKVui0W3NT0" width="640" height="480"&gt;&lt;/iframe&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;font size="3"&gt;What do you think about the VMware vVols? I'd love to hear your thoughts.&lt;/font&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;font size="3"&gt;UPDATE: I'm trying a new communication format - the ATSB eBook.&amp;nbsp; My first one&amp;nbsp;includes&amp;nbsp;&lt;u&gt;&lt;a title="PDF | 5.8MB" href="http://bit.ly/RwuTX3" target="_blank"&gt;&lt;strong&gt;screen shots of the vVol demo&lt;/strong&gt; &lt;/a&gt;&lt;/u&gt;that I have on video.&amp;nbsp; Check it out and expect more of these in the future. &amp;nbsp;&lt;/font&gt;&lt;/p&gt;</description>
    <pubDate>Wed, 10 Oct 2012 14:55:29 GMT</pubDate>
    <dc:creator>CalvinZ</dc:creator>
    <dc:date>2012-10-10T14:55:29Z</dc:date>
    <item>
      <title>The future of VMware storage - vVol demo</title>
      <link>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/ba-p/123309</link>
      <description>&lt;p&gt;&lt;font size="2"&gt;Last year at VMworld, VMware did an NDA technology preview for partners about their vision for the future of storage - something they called vVols (virtual volumes).&amp;nbsp; While VMware is allowing partners working with them to talk about it and demonstrate early functionality, I want to be clear - this is still a technology preview and neither VMware nor HP is making any commitments on delivering this.&amp;nbsp; So with that disclosure, let me tell you a bit about what it is.&lt;/font&gt;&lt;/p&gt;&#xD;
&lt;p&gt;&lt;font size="2"&gt;&amp;nbsp;&lt;/font&gt;&lt;/p&gt;&#xD;
&lt;p&gt;&lt;font size="2"&gt;&lt;strong&gt;Intro to VMware vVol&lt;/strong&gt; &lt;/font&gt;&lt;/p&gt;&#xD;
&lt;p&gt;&lt;font size="2"&gt;For awhile now, HP Storage has been working with VMware as a design partner to define and develop a VM-granular storage architecture to potentially replace vSphere&amp;rsquo;s VMFS/datastore model. This new model is called VMware Virtual Volumes (vVols). Virtual Volumes introduces a 1:1 mapping of VMs (more specifically VMDKs or VM LUNs) to storage volumes&amp;mdash;in other words, each VM will be associated with its own, unique storage volume. With vVols we could finally have the VMDK representation in vSphere match the representation on storage. &lt;/font&gt;&lt;/p&gt;&#xD;
&lt;p&gt;&lt;font size="2"&gt;&amp;nbsp;&lt;/font&gt;&lt;/p&gt;&#xD;
&lt;p&gt;&lt;font size="2"&gt;As a result, the storage system could now have the ability to operate at the same level of granularity as vSphere, which means that vSphere could better leverage, and take advantage of, the native strengths and capabilities of modern, intelligent storage arrays, like HP 3PAR.&lt;/font&gt;&lt;/p&gt;&#xD;
&lt;p&gt;&lt;font size="2"&gt;&amp;nbsp;&lt;/font&gt;&lt;/p&gt;&#xD;
&lt;p&gt;&lt;font size="3"&gt;&lt;font size="2"&gt;UPDATE: I'm trying a new communication format - the ATSB eBook.&amp;nbsp; My first one includes &lt;u&gt;&lt;a title="PDF | 5.8MB" href="http://bit.ly/RwuTX3" target="_blank"&gt;&lt;strong&gt;screen shots of the vVol demo&lt;/strong&gt; &lt;/a&gt;&lt;/u&gt;that I have on video.&amp;nbsp; Check it out and expect more of these in the future.&amp;nbsp;&lt;/font&gt; &lt;/font&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 10 Oct 2012 14:55:29 GMT</pubDate>
      <guid>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/ba-p/123309</guid>
      <dc:creator>CalvinZ</dc:creator>
      <dc:date>2012-10-10T14:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: The future of VMware storage - vVol demo</title>
      <link>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123369#M2067</link>
      <description>&lt;p&gt;Interesting stuff Calvin! How are the VMDK's mapped to the host?&lt;/p&gt;</description>
      <pubDate>Wed, 10 Oct 2012 08:03:44 GMT</pubDate>
      <guid>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123369#M2067</guid>
      <dc:creator>VirtualVaughan</dc:creator>
      <dc:date>2012-10-10T08:03:44Z</dc:date>
    </item>
    <item>
      <title>Re: The future of VMware storage - vVol demo</title>
      <link>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123415#M2068</link>
      <description>&lt;p&gt;This is an awesome post! Thanks for the info.. I had been hearing bits and pieces on VVOL over the past year but when I run searches online there is really very little information that I could find. Now I have something I can link to! (wasn't sure if the info I knew about VVOLs was under NDA or not so I didn't write anything on it myself!)&lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;VVOLs sound pretty neat in concept, though that is a lot of objects to manage! For both the storage system as well as vCenter itself. I think the architecture of 3PAR with the CPGs, fine grained allocation for the 3PAR VVs, and even Dynamic optimization itself lends themselves very well to the VMware VVOL concept.&lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;I think it presents some sort of managment challenge from a storage UI perspective though, my arrays have always been fairly organized, volumes are easy to identify their purpose, with VVOLs there will be tons of extra stuff in there that can be distracting.&lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;All round it sounds good, I'm pretty excited.&lt;/p&gt;</description>
      <pubDate>Wed, 10 Oct 2012 15:07:40 GMT</pubDate>
      <guid>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123415#M2068</guid>
      <dc:creator>nate</dc:creator>
      <dc:date>2012-10-10T15:07:40Z</dc:date>
    </item>
    <item>
      <title>Re: The future of VMware storage - vVol demo</title>
      <link>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123417#M2069</link>
      <description>&lt;p&gt;VirtualVaughan - I don't know how that mapping happens but I'm pretty certain it happens when you create the VM; the VM and vVol get created at the same time. Another source for information here is &lt;u&gt;&lt;a href="http://www.yellow-bricks.com/2012/08/07/vmware-vstorage-apis-for-vm-and-application-granular-data-management/" target="_blank"&gt;&lt;strong&gt;Duncan Epping's Yellow-Bricks.com&lt;/strong&gt; &lt;/a&gt;&lt;/u&gt;blog.&amp;nbsp; He has a post he did recently talking more about vVols.&lt;/p&gt;</description>
      <pubDate>Wed, 10 Oct 2012 15:24:10 GMT</pubDate>
      <guid>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123417#M2069</guid>
      <dc:creator>CalvinZ</dc:creator>
      <dc:date>2012-10-10T15:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: The future of VMware storage - vVol demo</title>
      <link>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123541#M2070</link>
      <description>&lt;p&gt;Hey Nate - not sure how I missed your comment.&amp;nbsp;I'll preface what I say with "I know nothing" ... of our future plans.&amp;nbsp; But I do know our team is looking at what we can do and is needed to better manage HP Storage in a VMware environment.&amp;nbsp; Obviously we already have the Insight Control for HP Storage plug-ins; they're thinking about the future beyond that based on where VMware is going.&amp;nbsp; Exciting times!&lt;/p&gt;</description>
      <pubDate>Thu, 11 Oct 2012 21:06:05 GMT</pubDate>
      <guid>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123541#M2070</guid>
      <dc:creator>CalvinZ</dc:creator>
      <dc:date>2012-10-11T21:06:05Z</dc:date>
    </item>
    <item>
      <title>Re: The future of VMware storage - vVol demo</title>
      <link>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123699#M2074</link>
      <description>&lt;p&gt;Thanks Calvin,&lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;What is the protocol that is used between the ESX host machine and the external storage array? Is it the T10 OSD? Also, how does it affects the performance comparing to the good old block level protocols?&lt;/p&gt;</description>
      <pubDate>Sun, 14 Oct 2012 09:52:16 GMT</pubDate>
      <guid>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123699#M2074</guid>
      <dc:creator>Jephtah</dc:creator>
      <dc:date>2012-10-14T09:52:16Z</dc:date>
    </item>
    <item>
      <title>Re: The future of VMware storage - vVol demo</title>
      <link>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123819#M2078</link>
      <description>&lt;p&gt;Sounds cool intially, im just thinking of more management for storage people though.  I would think that storage drs answers the inefficency your mentioning....Interesting article thanks for sharing.  &lt;/p&gt;</description>
      <pubDate>Tue, 16 Oct 2012 01:48:19 GMT</pubDate>
      <guid>http://h30507.www3.hp.com/t5/Around-the-Storage-Block-Blog/The-future-of-VMware-storage-vVol-demo/bc-p/123819#M2078</guid>
      <dc:creator>jeffrey wolfanger</dc:creator>
      <dc:date>2012-10-16T01:48:19Z</dc:date>
    </item>
  </channel>
</rss>

