This section describes how to map LogicalVolume discovered using OpenStack and ScsiLun discovered using EMC M&R.

Whenever a volume is created from OpenStack, a corresponding Lun gets created in the storage array (VMAX and VNX). The ID of the volume is present as LUN Name.

VMAX case:

In case of VMAX, whenever a volume is created, ScsiLUN CanonicalName exactly matches with the LogicalVolume ID in OpenStack, and hence you get a proper mapping between the LUN and the volume.

VNX case:

In case of VNX, ScsiLun Canonical Name does not exactly match with the LogicalVolume ID in OpenStack. The ScsiLUN will be prefixed with the “vulme_name_template” string which is configured in the OpenStack.

The default value of this string is “volume-s”. If the user modifies this value and configures a new volume, the mapping between the ScsiLUN and the volume may not happen.

In order to have a proper mapping between the ScsiLUN and the volume, the user needs to complete the following step:

A new parameter called as PreficVolume is added in esm-param.conf file, as follows:

PrefixVolume-<CloudController-IP> <value>

This flag is used to capture the value for volume_name_template specified in the cinder.conf file.

For example:

If the user changes the default value of the “volume_name_template” value in the cinder.conf from “volume-%s” to “Test-%s”, the user needs to make the following changes in the esm-param.conf file in ESM Server.

PrefixVolume- Test-.

The user can also specify multiple values for the same CloudController instance.

For example:

PrefixVolume- Test-|volume-

If there are multiple Cloud Controllers which are monitored, the value must be:

  • PrefixVolume- Test-|volume-

  • PrefixVolume- Test-|volume-