EMC SMI-S iSCSI and FC drivers

Install the python-pywbem package for your distribution, as follows:

You can install SMI-S on a non-OpenStack host. Supported platforms include different flavors of Windows, Red Hat, and SUSE Linux. SMI-S can be installed on a physical server or a VM hosted by an ESX server. Note that the supported hypervisor for a VM running SMI-S is ESX only. See the EMC SMI-S Provider release notes for more information on supported platforms and installation instructions.

	Note
	You must discover storage arrays on the SMI-S server before you can use the Cinder driver. Follow instructions in the SMI-S release notes.

SMI-S is usually installed at /opt/emc/ECIM/ECOM/bin on Linux and C:\Program Files\EMC\ECIM\ECOM\bin on Windows. After you install and configure SMI-S, go to that directory and type TestSmiProvider.exe.

Use addsys in TestSmiProvider.exe to add an array. Use dv and examine the output after the array is added. Make sure that the arrays are recognized by the SMI-S server before using the EMC Cinder driver.

To export a VNX volume to a Compute node or a Volume node, you must register the node with VNX.

For a VNX volume to be exported to a Compute node or a Volume node, SAN zoning needs to be configured on the node and WWNs of the node need to be registered with VNX in Unisphere.

For VMAX iSCSI and FC drivers, you need to do initial setup in Unisphere for VMAX. In Unisphere for VMAX, create an initiator group, a storage group, and a port group. Put them in a masking view. The initiator group contains the initiator names of the OpenStack hosts. The storage group will contain volumes provisioned by Block Storage.

Make the following changes in /etc/cinder/cinder.conf.

For VMAX iSCSI driver, add the following entries, where 10.10.61.45 is the IP address of the VMAX iSCSI target:

iscsi_target_prefix = iqn.1992-04.com.emc
iscsi_ip_address = 10.10.61.45
volume_driver = cinder.volume.drivers.emc.emc_smis_iscsi.EMCSMISISCSIDriver
cinder_emc_config_file = /etc/cinder/cinder_emc_config.xml

For VNX iSCSI driver, add the following entries, where 10.10.61.35 is the IP address of the VNX iSCSI target:

iscsi_target_prefix = iqn.2001-07.com.vnx
iscsi_ip_address = 10.10.61.35
volume_driver = cinder.volume.drivers.emc.emc_smis_iscsi.EMCSMISISCSIDriver
cinder_emc_config_file = /etc/cinder/cinder_emc_config.xml

For VMAX and VNX FC drivers, add the following entries:

volume_driver = cinder.volume.drivers.emc.emc_smis_fc.EMCSMISFCDriver
cinder_emc_config_file = /etc/cinder/cinder_emc_config.xml

Restart the cinder-volume service.

Create the /etc/cinder/cinder_emc_config.xml file. You do not need to restart the service for this change.

For VMAX, add the following lines to the XML file:

<?xml version="1.0" encoding="UTF-8"?>
<EMC>
    <StorageType>xxxx</StorageType>
    <MaskingView>xxxx</MaskingView>
    <EcomServerIp>x.x.x.x</EcomServerIp>
    <EcomServerPort>xxxx</EcomServerPort>
    <EcomUserName>xxxxxxxx</EcomUserName>
    <EcomPassword>xxxxxxxx</EcomPassword>
    <Timeout>xx</Timeout>
</EMC>

For VNX, add the following lines to the XML file:

<?xml version="1.0" encoding="UTF-8"?>
<EMC>
    <StorageType>xxxx</StorageType>
    <EcomServerIp>x.x.x.x</EcomServerIp>
    <EcomServerPort>xxxx</EcomServerPort>
    <EcomUserName>xxxxxxxx</EcomUserName>
    <EcomPassword>xxxxxxxx</EcomPassword>
    <Timeout>xx</Timeout>
</EMC>

Where:

	Note
	To attach VMAX volumes to an OpenStack VM, you must create a Masking View by using Unisphere for VMAX. The Masking View must have an Initiator Group that contains the initiator of the OpenStack compute node that hosts the VM.

Volume type support enables a single instance of cinder-volume to support multiple pools and thick/thin provisioning.

When the StorageType tag in cinder_emc_config.xml is used, the pool name is specified in the tag. Only thin provisioning is supported in this case.

When the StorageType tag is not used in cinder_emc_config.xml, the volume type needs to be used to define a pool name and a provisioning type. The pool name is the name of a pre-created pool. The provisioning type could be either thin or thick.

Here is an example of how to set up volume type. First create volume types. Then define extra specs for each volume type.

In the above example, two volume types are created. They are High Performance and Standard Performance. For High Performance , storagetype:pool is set to smi_pool and storagetype:provisioning is set to thick. Similarly for Standard Performance, storagetype:pool. is set to smi_pool2 and storagetype:provisioning is set to thin. If storagetype:provisioning is not specified, it will default to thin.

Note

Volume type names High Performance and Standard Performance are user-defined and can be any names. Extra spec keys storagetype:pool and storagetype:provisioning have to be the exact names listed here. Extra spec value smi_pool is your pool name. The extra spec value for storagetype:provisioning has to be either thick or thin. The driver will look for a volume type first. If the volume type is specified when creating a volume, the driver will look for the volume type definition and find the matching pool and provisioning type. If the volume type is not specified, it will fall back to use the StorageType tag in cinder_emc_config.xml.