Virtual Volumes (VVols) is a new storage integration and management framework appearing in VMware vSphere 6.0. Virtual Volumes virtualize SAN and NAS arrays in order to offer simplified storage provisioning and consumption for the VMDKs supporting VMware virtual servers. Now you can experience how this technology will be integrated into future versions of EMC’s mid-range array for file storage through this unique VVols Tech Preview software download.

VMware Virtual Volumes (VVols)

      VMware Virtual Volumes (VVols) is an integration and management framework delivering a new operational model for external storage (SAN/NAS). It is comprised of a control plane using Storage Policy-Based Management, and a data plane using VASA APIs for external storage and vSphere APIs for IO Filtering for in-hypervisor software data services.

      To use VVols storage, you will need vSphere 6.0 or higher and certified array vendor Virtual Volumes software (VASA Provider). Details on supported array models is available at the hardware compatibility guide page: http://www.vmware.com/resources/compatibility/

      There are 3 major objects in VVols: the storage provider, the protocol endpoint and the storage container.

      Storage Provider:We mentioned the fact that a vSphere admin create a set of storage requirements for an application/VM. How does an admin know what an array is capable of offering in terms of performance, availablity, features, etc? This is where the Storage Provider comes in. Out of band communication between vCenter and the storage array is achieved via the Storage Provider. Those of you familiar with VASA will be familiar with this concept. It allows capabilities from the underlying storage to be surfaced up into vCenter. VVOLs uses this so that storage container capabilities can be surfaced up. But there is a significant difference in VVOLs – we can now use the storage provider/VASA to push information down to the array also. This means that we can create requirements for our VMs (availability, performance, etc) and push this profile down to the storage layer, and ask it to build out the VMDK (or virtual volume) based on the requirements in the profile. The Storage Provider is created by the storage array vendor, using an API defined by VMware.

      Protocol Endpoint: Since the ESXi will not have direct visibility of the VVOLs which back the VMDKs, there needs to be an I/O demultiplexor device which can communicate to the VVOLs (VMDKs) on its behalf. This is the purpose of the protocol endpoint devices, which in the case of block storage is a LUN, and in the case of NAS storage is a share or mountpoint. When a VM does I/O, the I/O is directed to the appropriate virtual volume by the protocol endpoint. This now allows us to scale to very, very many virtual volumes, and the multipathing characteristics of the protocol endpoint device are implicitly inherited by the VVOLs.

   

      Storage Container:This is your storage pool on the array. Currently, one creates a pool of physical spindles on an array, perhaps building a raid across them and then carves this up into LUNs or shares to be presented to the ESXi hosts. In VVOLs, only the container/pool needs to be created. Once we have the storage provider and protocol endpoints in place, the storage container becomes visible to the ESXi hosts. From then on, as many VVOLs can be created in the container as there is available space, so long as the characteristics defined in the storage profiles matches the storage container.

      With Virtual Volumes, it is much simpler to deliver and enable the right storage service levels according to the specific requirements of individual VMs. By having finer control over storage resources and data services down to the VM level, the VI administrator can create exact combinations and precisely deliver storage service levels.

   

vVNX with VVols

      VVols Technical Preview for vVNX software can be downloaded from EMC Trial Software Downloads page, or the direct link http://www.emc.com/products-solutions/trial-software-download/vvols.htm

 

      The software supports in the Open Virtualization Appliance (OVA) format, which requires VMware ESXi and vCenter environment.

To download the software you need to register an account on support.emc.com first. You can skip this step if you already have the account.

 

      To successfully run vVNX VVols software in your VMware environment, please verify the follow system requiremnts:

     -    VMware infrastructure: VMware vCenter and ESXi Server, release 6.0 or later

-                -    Network infrastructure: 2x 1 GbEOR 2x 10 GbE

-                -    Battery-backed Hardware RAID controller required (512MB NV Cache recommended)

      Virtual appliance configuration options:

-    2 vCPUs at 2GHz+

-    12 GB RAM

-    Up to 4 TB Storage

      Then you can connect ESXi host with vSphere Client, deploy vVNX with the “Deploy OVF Template” wizard.

 

   

      After the deployment, point the browser to vVNX management IP address, the default administrator account is admin, Password123#.

      Note: you need to change the default password at first login.

      To activate the product, you need to manually register VVolsTechnical Preview for vVNX software:

      1. Note the system UUID provided on the License dialog in the Configuration Wizard.

      2. Go to the Electronic License Management System (ELMS) download page at www.emc.com/auth/elmeval.htm.

      3. Enter the system UUID and select VVols Tech Preview for vVNX as the product type.

      4. Click Download to save the license to your local system.

Note: An email confirming that you have successfully obtained the evaluation license is sent to the email address you provided when you registered.

      5. Return to the License dialog in the Configuration Wizard and click Install License File.

      6. Locate the license file, select it, and click Upload to install and activate it.

Note: Do not repeat this procedure once you have saved the license and received the confirmation email. If you try to enter the VVols Tech Preview system UUID again, you will receive a "Duplicate UUID" error message.