Atom feed of this document
Kilo -  Kilo -  Kilo -  Kilo -  Kilo -  Kilo -  Kilo -  Kilo - 

 EMC XtremIO Block Storage driver configuration

The high performance XtremIO All Flash Array (AFA) offers Block Storage services to OpenStack. Using the driver, OpenStack Block Storage hosts can connect to an XtermIO Storage cluster.

This section explains how to configure and connect an OpenStack block storage host to an XtremIO storage cluster.

 Support matrix

  • Xtremapp: Version 3.0 and 4.0

 Supported operations

  • Create, delete, clone, attach, and detach volumes

  • Create and delete volume snapshots

  • Create a volume from a snapshot

  • Copy an image to a volume

  • Copy a volume to an image

  • Extend a volume

  • Manage and unmanage a volume

  • Get volume statistics

 XtremIO Block Storage driver configuration

Edit the cinder.conf file by adding the configuration below under the [DEFAULT] section of the file in case of a single back end or under a separate section in case of multiple back ends (for example [XTREMIO]). The configuration file is usually located under the following path /etc/cinder/cinder.conf.

For a configuration example, refer to the configuration example.

 XtremIO driver name

Configure the driver name by adding the following parameter:

  • For iSCSI volume_driver = cinder.volume.drivers.emc.xtremio.XtremIOIscsiDriver

  • For Fibre Channel volume_driver = cinder.volume.drivers.emc.xtremio.XtremIOFibreChannelDriver

 XtremIO management server (XMS) IP

To retrieve the management IP, use the show-xms CLI command.

Configure the management IP by adding the following parameter: san_ip = XMS Management IP

 XtremIO cluster name

In XtremIO version 4.0, a single XMS can manage multiple cluster back ends. In such setups, the administrator is required to specify the cluster name (in addition to the XMS IP). Each cluster must be defined as a separate back end.

To retrieve the Cluster Name, run the show-clusters CLI command.

Configure the cluster name by adding the xtremio_cluster_name = Cluster-Name


When a single cluster is managed in XtremIO version 4.0, the cluster name is not required.

 XtremIO user credentials

OpenStack Block Storage requires an XtremIO XMS user with administrative privileges. XtremIO recommends creating a dedicated OpenStack user account that holds an administrative user role.

Refer to the XtremIO User Guide for details on user account management

Create an XMS account using either the XMS GUI or the add-user-accountCLI command.

Configure the user credentials by adding the following parameters:

san_login = XMS username

san_password = XMS username password

 Multiple back ends

Configuring multiple storage back ends enables you to create several back-end storage solutions that serve the same OpenStack Compute resources.

When a volume is created, the scheduler selects the appropriate back end to handle the request, according to the specified volume type.

 Setting thin provisioning and multipathing parameters

To support thin provisioning and multipathing in the XtremIO Array, the following parameters from the Nova and Cinder configuration files should be modified as follows:

  • Thin Provisioning

    All XtremIO volumes are thin provisioned. The default value of 20 should be maintained for the max_over_subscription_ratio parameter.

    The use_cow_images parameter in thenova.conffile should be set to False as follows:

    use_cow_images = false

  • Multipathing

    The use_multipath_for_image_xfer parameter in thecinder.conf file should be set to True as follows:

    use_multipath_for_image_xfer = true

 Restarting OpenStack Block Storage

Save thecinder.conffile and restart cinder by running the following command:

$ openstack-service restart cinder-volume

 Configuring CHAP

The XtremIO Block Storage driver supports CHAP initiator authentication. If CHAP initiator authentication is required, set the CHAP Authentication mode to initiator.

To set the CHAP initiator mode using CLI, run the following CLI command:

$ modify-chap chap-authentication-mode=initiator

The CHAP initiator mode can also be set via the XMS GUI

Refer to XtremIO User Guide for details on CHAP configuration via GUI and CLI.

The CHAP initiator authentication credentials (username and password) are generated automatically by the Block Storage driver. Therefore, there is no need to configure the initial CHAP credentials manually in XMS.

 Configuration example

cinder.conf example file

You can update the cinder.conf file by editing the necessary parameters as follows:

enabled_backends = XtremIO

volume_driver = cinder.volume.drivers.emc.xtremio.XtremIOFibreChannelDriver
san_ip = XMS_IP
xtremio_cluster_name = Cluster01
san_login = XMS_USER
san_password = XMS_PASSWD
volume_backend_name = XtremIOAFA
Questions? Discuss on
Found an error? Report a bug against this page

loading table of contents...