Configuring IBM Storwize Cinder driver

You can configure IBM Cloud Manager with OpenStack to use the IBM Storwize® Cinder driver.

About this task

The IBM Storwize Cinder driver is supported in the following environments:
Table 1. Summary of support details
Support options Details
Supported hypervisor types and architectures? KVM or QEMU on x86_64, KVM for IBM z, PowerKVM, Hyper-V, and z/VM®
Support for post-deployment customization? Yes
Supported topologies? All, except Minimal.
Storage (Cinder) node? Controller or block storage node
Note: For the HA controller +n compute topology, the storage node must be the controller node.
Operating system and architecture on storage node? Red Hat Enterprise Linux® 7.1, 7.2, or 7.3 on x86_64, or KVM for IBM z Systems® version 1.1
The following storage systems are supported by the IBM Storwize Cinder driver:
Table 2. Storage systems supported by the IBM Storwize Cinder driver
Storage system Code version
SAN Volume Controller 1 6.4, 7.1, 7.2, 7.3, 7.4
Storwize V7000 6.4, 7.1, 7.2, 7.3, 7.4
Storwize V3500 6.4, 7.1, 7.2, 7.3, 7.4
Storwize V3700 6.4, 7.1, 7.2, 7.3, 7.4
Storwize V5000 7.1, 7.2, 7.3, 7.4
Storwize V7000 Unified 1.4.2, 1.4.3, 1.5
IBM Flex System® V7000 6.4, 7.1, 7.2
FlashSystem V9000 7.4
1 The Volume Replication feature requires at least code version 7.2.

Complete the following steps to configure IBM Cloud Manager with OpenStack to use the IBM Storwize Cinder driver.

Procedure

  1. Create an SSH public / private key pair for authenticating to the SAN controller, or use an existing key pair.
    The public key should be placed on the SAN controller as described in the SAN storage documentation. Place the private key on the Cinder volume server (typically the controller node), and record its location for use below.
    Note: For the HA controller +n compute topology, the private key must be placed on each controller node in the same location in the file system.

    The file permissions for this file are set during deployment so that it is owned and readable only by the OpenStack block storage user (Cinder).

  2. Add the following attribute to the default_attributes section of your environment file.
    • openstack.block-storage.volume.driver: Set to cinder.volume.drivers.ibm.storwize_svc.StorwizeSVCDriver
  3. Add the following attributes as needed to the default_attributes section of your environment file. The values for these attributes must be based on your IBM Storwize Cinder configuration.
    Note: For the HA controller +n compute topology, the following properties need to be put in a openstack.block-storage.volume.multi_backend.storwize-1 block. For more information, see Deploying an advanced configuration with KVM or QEMU compute nodes (HA controller nodes).
    • openstack.block-storage.san.san_ip: IP address of SAN controller. The default value is 127.0.0.1.
    • openstack.block-storage.san.san_login: User name for SAN controller. The default value is admin.
    • openstack.block-storage.san.san_private_key: File name of the private key to use for SSH authentication. The default is /v7000_rsa.
    • openstack.block-storage.san.san_private_key_url: The location (URL) of the san_private_key. You may specify HTTP (http://), FTP ("ftp://"), or local (file://). If the SAN private key is local, specify this attribute using (file://).
    • openstack.block-storage.storwize.storwize_svc_volpool_name: Storage system storage pool for volumes. The default is volpool.
    • openstack.block-storage.storwize.storwize_svc_vol_rsize: Storage system space-efficiency parameter for volumes. The default value is 2.
    • openstack.block-storage.storwize.storwize_svc_vol_warning: Storage system threshold for volume capacity warnings. The default value is 0.
    • openstack.block-storage.storwize.storwize_svc_vol_autoexpand: Storage system auto-expand parameter for volumes. The default is true.
    • openstack.block-storage.storwize.storwize_svc_vol_grainsize: Storage system grain size parameter for volumes. The default is 256.
    • openstack.block-storage.storwize.storwize_svc_vol_compression: Storage system compression option for volumes. The default value is false.
    • openstack.block-storage.storwize.storwize_svc_vol_easytier: Enable Easy Tier® for volumes. The default value is true.
    • openstack.block-storage.storwize.storwize_svc_flashcopy_timeout: Maximum number of seconds to wait for FlashCopy® to be prepared. The default value is 120.
    • openstack.block-storage.storwize.storwize_svc_vol_iogrp: The I/O group in which to allocate volumes. The default value is 0.
    • openstack.block-storage.storwize.storwize_svc_connection_protocol: Connection protocol (iSCSI or Fibre Channel). The default value is iSCSI.
      Note: Only iSCSI is supported by Hyper-V compute nodes. KVM for IBM z Systems compute nodes and storage nodes supports only Fibre Channel.
    • openstack.block-storage.storwize.storwize_svc_iscsi_chap_enabled: Configure CHAP authentication for iSCSI connections. The default value is true.
      Note: If the compute node is Hyper-V, specify the value in the environment file as false.
    • openstack.block-storage.storwize.storwize_svc_multipath_enabled: Connect with multipath (Fibre Channel only; iSCSI multipath is controlled by Nova). The default value is false.
    • openstack.block-storage.storwize.storwize_svc_multihostmap_enabled: Allows vdisk to multi-host mapping. The default value is true.
  4. When complete, return to the relevant topology deployment or update process and complete the remaining steps.