Setting Cinder Storage Credentials On Premise

This article explains how to set storage appliance credentials to your block storage node.

Prerequisites

You must have a Cinder block storage node authorized and connected.

Step 1

Log in to the Linux host which you have assigned the Cinder block storage role.

Step 2

Change directory to: /opt/pf9/etc/pf9-cindervolume-base/conf.d/ .

Bash

cd /opt/pf9/etc/pf9-cindervolume-base/conf.d/

Step 3

Create a file named cinder_override.conf (note the underscore):

Bash

touch /opt/pf9/etc/pf9-cindervolume-base/conf.d/cinder_override.conf

Add a [DEFAULT] section and list all the backends you wish to enable using the enabled_backends option in this section. Add the appropriate parameters for each backend as needed by the respective driver in a backend-specific section. Please refer to your storage vendor's manual for more information on which configuration options are available.

Note

Cinder was upgraded to the Stein release in 4.2 release of Platform9. The config options iscsi_ip_address, iscsi_port, iscsi_target_prefix and iscsi_protocol were deprecated in the Queens release and have now been removed. Deployments should now use the more general target_ip_address, target_port, target_helper, target_prefix and target_protocol options. For example, if LVM configuration has option iscsi_ip_address, it needs to be changed to target_ip_address. For more information, please check https://docs.openstack.org/releasenotes/cinder/stein.html#relnotes-14-0-0-stable-stein-upgrade-notes.

Example (for QNAP):

cinder_override.conf

[DEFAULT]
enabled_backends = qnap
[qnap]
san_login = admin
san_password = changeme

Step 4

Restart the pf9-cindervolume service. For example, on Enterprise Linux operating systems e.g. CentOS:

Bash

service pf9-cindervolume-base restart