6.4 KiB

Raw Blame History

Guide to the Pure Storage Cinder Plugin version 2.0-2.0.0-1 for Fuel

This document provides instructions for installing, configuring and using Pure Storage Cinder plugin for Fuel.

Pure Storage Cinder

The Pure Storage Cinder Fuel plugin provides an automated method to insert the necessary lines into the cinder.conf file. The plugin extends the Fuel Web UI to provide the necessary entry locations for the information for the configuration file. Thus, the plugin incorporates OpenStack Cinder Driver for Pure Storage Flash Array. Thus, the plugin provides the ability to create a configuration file stanza so that when multi-backend support is selected, the stanza is correct.

License

Component	License type
No Components are present

Requirements

Requirement	Version/Comment
Fuel	8.0

Pre-requisites

The Pure Storage array should be configured and connected to your network prior to configuring your OpenStack deployment.

For more information on the Array configuration, follow the official documentation available from within the array GUI as shown below (top right of screen under Help section)

Limitations

No limitations are present

Installation Guide

Pure Storage Cinder Plugin installation

Download the plugin from the Fuel Plugins Catalog.
Copy the plugin to an already installed Fuel Master node. If you do not have the Fuel Master node yet, please follow the instructions:
```
scp  fuel-plugin-purestorage-cinder-2.0-2.0.0-1.noarch.rpm \
root@:<the_Fuel_Master_node_IP>:/tmp
```
Log into the Fuel Master node.

Install the plugin

cd /tmp
fuel plugins --install fuel-plugin-purestorage-cinder-2.0-2.0.0-1.noarch.rpm

Check if the plugin was installed successfully

# fuel plugins
id | name                           | version | package_version
---|--------------------------------|---------|----------------
 1 | fuel-plugin-purestorage-cinder | 2.0.0   | 4.0.0

After the plugin is installed, create a new OpenStack environment using the Fuel UI Wizard.
Configure your environment.
Open the Settings tab of the Fuel Web UI and scroll down the page. Select the Storage section to enable Pure Storage driver in Cinder plugin checkbox.

Enter the Purity API Token and the IP address of the management VIP of the Pure Storage FlashArray.

Obtain the Purity API token from the Pure Storage GUI

System->Users->API Tokens: Select User, click gear icon by user \
and select 'Show API Token'

or use the following Purity CLI command to obtain the API token:

# pureadmin list --api-token --expose <USER>

Obtain the Pure Storage VIP from the Pure Storage GUI

System->System->Configuration->Networking: Use the IP address associated \
with 'vir0'

or use the following Purity CLI command to obtain the VIP address:

# purenetwork list vir0

Select the defaults for all other Pure Storage options. Each selectable option has a description in the Fuel GUI.
If using Fibre Channel as the storage protocol you need to select the zoning method to be used in your deployment. If you are configuring your own zones then select 'Manual' but you can select 'Automatic' if you wish to use the Openstack Fibre Channel Zone Manager. If 'Automatic' is selected you will need to provide the necessary information for the Zone Manager to communicate and configure your fibre channel switches.

User Guide

Once the OpenStack instance is deployed by Fuel the Pure Storage plugin provides no user configurable or maintainable options.

Validation of the plugins correct operation can be performed by comparing the parameters selected in the Fuel GUI to those added into the /etc/cinder/cinder.conf and /etc/nova/nova.conf files on the Controller and Compute nodes respectively.

As part of this installation a new multipath.conf file is provided to all nodes. Ensure that other device entries required for your local environment are added to these files and multipath is restarted to accept any changes.

The Pure Storage driver (once configured by Fuel) will output all logs into the cinder-volume process log file with the 'Pure Storage' title.

Known issues

Ensure your controller nodes have access to the public internet to allow for correct Python module installation required by the Fuel plugin
If you environment is deployed with multiple controllers for HA, you cannot run all the Cinder Volume services at the same time in Active-Active mode
There are specific changes that need to be made to the local deb packages. More details can be found in the Pure Storage/Mirantis Reference Architecture

6.4 KiB Raw Blame History