From the Management Type drop down menu select VMware Virtual Volumes (VVols), and select the vCenter server that will be managing the Virtual Volumes, click Create. If required you can set a usage limit on the folder, this does not create a reservation but puts a cap on the amount of storage VMware can use for Virtual Volumes. If you have setup multiple pools of storage then select the pool to use, otherwise leave at default. From the drop down Manage menu select Data Storage, change the view to Folder and click the Add button.Įnter a name and description for the new folder. The next task is to setup a folder for VMware to use as a storage container. Add the vCenter Server or edit an existing vCenter integration to select the VASA Provider (VVols) check box and click Save. From the drop down Administration menu select VMware Integration. The first thing we need to do is integrate the VASA provider with vSphere. Log into the web interface of the Nimble device. If you are using an alternative storage provider cross check your hardware with VVols in the VMware Compatibility Guide. At the time of writing all Nimble storage support VVols.Check with your storage provider that they support VASA 2.0 (vSphere 6.0) or VASA 3.0 (vSphere 6.5). Nimble have included the vStorage APIs for Storage Awareness (VASA) in the software.There are no additional licensing requirements or costs to use VVols with Nimble.Nimble arrays must be running OS v3.x or above.If you have already licensed vSphere for standard or above there is no additional cost.Before you can implement VVols you need to be running vSphere 6 or above.
Nimble folders were added in v3 of the OS and represent a logical allocation of capacity, vSphere sees the folders as containers where virtual volumes can reside. Virtual machines are provisioned based on the VMware Storage Policy Based Management (SPBM) framework which uses the VASA client, both features are key to VVols and were introduced with vSphere 6. This design also benefits from the highly available setup of Nimble controllers. This means that the VASA provider and Protocol Endpoint run natively from the controller, so there is no additional installation or configuration required.
#Provision a share on nimble san software
Nimble software includes the vStorage APIs for Storage Awareness (VASA) provider and the PE (Protocol Endpoint) built into the operating system. The terminology and features of Virtual Volumes are detailed in KB 2113013 (Understanding Virtual Volumes (VVols) in VMware vSphere 6.7). The post was originally published in September 2016 and has subsequently been brought up to date, the process remains largely the same and in this example we will use the vSphere 6.7 HTML5 client and Nimble software version 5.0.4. This post will walk through the setup of VMware Virtual Volumes (VVols) with HPE Nimble Storage.
0 kommentar(er)
