Virtual pools allow you to assign pools of storage from the physical storage array to the virtual array. These pools are used by ViPR to provision requested storage resources. For Isilon we use the existing OneFS pool, so there is no setup on the array side. For VNX we need to create pools. In previous posts I showed you how to discover a VNX with the SMI-S provider. If you have already created pools of storage on the VNX you will see them listed here during creation. If not go and create them. Give the system about 5 minutes after creation to “discover” them. If your impatient, like me, go to the physical assets tab, SMI-S Providers, select your provider and “re-discover”
Under the Virtual Assets tab click Virtual Pools and then click Add |
|
Give the pool a name, description type (if using a unified system), storage type, and then select the virtual array to use. Select the protocol you wish to use. You can create multiple virtual pools that pull resources from the same virtual array using different physical pools and protocols. |
|
Select your Data protection, Quota, assignment, and pool to use. For Isilon there is only one pool. Click Save |
Virtual Pool for VNX
Creating a pool for VNX block is similar.
Give the pool a name, description type (if using a unified system), storage type, and then select the virtual array to use. Select the protocol you wish to use. You can create multiple virtual pools that pull resources from the same virtual array using different physical pools and protocols. |
|
Select the protocol and criteria for you block system. Your selections will be based on what the system supports. You will only see options for what is discovered. Note that Multi-Volume consistency is not supported for Openstack so make sure it’s not checked. |
|
Select the pool(s) you wish this virtual pool to use. Click save. My lab setup now looks like this |
Comments