Dell Storage Center Back End Guide

This document describes how to configure OpenStack to use one or more Dell Storage Center back ends. The following sections assume that:

When you deploy Red Hat OpenStack Platform (RHOSP) through director, you must also define and orchestrate all major overcloud settings through director, in particular, the Block Storage service back end. This ensures that the settings persist through any further overcloud updates. For more information about deploying OpenStack through the Director, see Director Installation and Usage.

The purpose of this document is to explain how to orchestrate your Dell Storage Center back end configuration to the overcloud Block Storage service. This document does not discuss the different deployment configurations that are possible with the back end. To learn more about the different available deployment configurations, see the product documentation of your device.

When you are familiar with the resulting back end configuration you want to deploy, and its corresponding settings, see this document for instructions about how to orchestrate it through director.

Before deploying Red Hat OpenStack Platform (RHOSP) with a Dell Storage Center back end, review the following limitations:

Red Hat OpenStack Platform (RHOSP) includes the drivers required for all Dell devices supported by the Block Storage service. In addition, director also has the puppet manifests, environment files, and Orchestration templates necessary for integrating the device as a back end to the overcloud.

Configuring a single Dell device as a back end involves editing the default environment file and including it in the overcloud deployment. This file is available locally on the undercloud, and can be edited to suit your environment.

After you edit this file, invoke it through director. Doing so ensures that it persists through future overcloud updates. The following sections describe this process in greater detail. In addition, the default environment file already contains enough information to call the necessary puppet manifests and Orchestration (heat) templates that configure the rest of the required Block Storage settings.

With a Director deployment, the easiest way to define a single Dell Storage Center back end is through the integrated environment file. This file is located in the following path of the Undercloud node:

/usr/share/openstack-tripleo-heat-templates/environments/cinder-dellsc-config.yaml

Copy this file to a local path where you can edit and invoke it later. For example, to copy it to ~/templates/:

$ cp /usr/share/openstack-tripleo-heat-templates/environments/cinder-dellsc-config.yaml ~/templates/

Afterwards, open the copy (~/templates/cinder-dellsc-config.yaml) and edit it as you see fit. The following snippet displays the default contents of this file:

# A Heat environment file which can be used to enable a
# a Cinder  Dell Storage Center ISCSI backend, configured via puppet
resource_registry:
  OS::TripleO::Services::CinderBackendDellSc: ../puppet/services/cinder-backend-dellsc.yaml # 1

parameter_defaults: # 2
  CinderEnableDellScBackend: true # 3
  CinderDellScBackendName: 'tripleo_dellsc'
  CinderDellScSanIp: ''
  CinderDellScSanLogin: 'Admin'
  CinderDellScSanPassword: ''
  CinderDellScSsn: '64702'
  CinderDellScIscsiIpAddress: ''
  CinderDellScIscsiPort: '3260'
  CinderDellScApiPort: '3033'
  CinderDellScServerFolder: 'dellsc_server'
  CinderDellScVolumeFolder: 'dellsc_volume'

To define your Dell Storage Center back end, edit the settings in the parameter_defaults section as you see fit. The following table explains each parameter, and also lists its corresponding /etc/cinder/cinder.conf setting.

The Director installation uses a non-root user to execute commands, which includes orchestrating the deployment of the Block Storage back end. In Creating a Director Installation User, a user named stack is created for this purpose. This user is configured with elevated privileges.

To deploy the lone back end configured in Chapter 3, Define a Single Back End, first log in as the stack user to the Undercloud. Then, deploy the back end (defined in the edited ~/templates/cinder-dellsc-config.yaml) by running the following:

$ openstack overcloud deploy --templates -e ~/templates/cinder-dellsc-config.yaml

Test the back end after director orchestration is complete. See Chapter 5, Test the Configured Back End.

After deploying the back end, test whether you can successfully create volumes on it. Doing so will require loading the necessary environment variables first. These variables are defined in /home/stack/overcloudrc by default.

To load these variables, run the following command as the stack user:

$ source /home/stack/overcloudrc

You should now be logged in to the Controller node. From there, you can create a volume type, which can be used to specify the back end you want to use (in this case, the newly-defined back end in Chapter 3, Define a Single Back End). This is required in an OpenStack deployment where you have other back ends enabled (preferably, also through Director).

To create a volume type named dellsc, run:

$ cinder type-create dellsc

Next, map this volume type to the back end defined in ]. Given the back end name tripleo_dellsc (as defined through the CinderDellScBackendName parameter, in xref:edityaml[), run:

$ cinder type-key dellsc set volume_backend_name=tripleo_dellsc

You should now be able to create a 2GB volume on the newly defined back end by invoking its volume type. To do so, run:

$ cinder create --volume-type dellsc 2