04a325758f
Change-Id: I2276be3f2c5f1bf7a6769ca0bf200ba521b84f47 Refactoring for the new structure for Fuel 8. This change now handles multi-backend in the face of the default options (lvm, ceph) and the NetApp plugin. Note: I removed the multi-backend option, so it will always put SolidFire in it's own stanza along with everyone (in the above list) also. Change-Id: Ibc3ffe202fb405da9b566498c23f6bcda84080a9 |
||
---|---|---|
deployment_scripts/puppet | ||
docs | ||
repositories | ||
specs | ||
.gitignore | ||
.gitreview | ||
LICENSE | ||
README.md | ||
components.yaml | ||
deployment_tasks.yaml | ||
environment_config.yaml | ||
metadata.yaml | ||
pre_build_hook |
README.md
fuel-plugin-solidfire-cinder
Plugin description
SolidFire plugin for Fuel extends Mirantis OpenStack functionality by adding support for SolidFire all Flash block storage cluster.
The SolidFire cluster is an iSCSI block storage device used as a Cinder backend.
Requirements
Requirement | Version/Comment |
---|---|
Mirantis OpenStack compatibility | >= 6.1 |
Access to SolidFire MVIP via cinder-volume node | |
Access to SolidFire SVIP via compute/cinder-volume nodes | |
iSCSI initiator on all compute/cinder-volume nodes |
Limitations
Currently Fuel doesn't support multi-backend.
SolidFire configuration
Before starting a deployment there are some things that you should verify:
- Your SolidFire Cluster can route 10G Storage Network to all Compute nodes as well as the Cinder Control/Manager node.
- Create an account on the SolidFire cluster to use as the OpenStack Administrator account (use the login/password for this account as san_login/password settings).
- Obtain the MVIP address from the SolidFire cluster (uses as the san_ip)
SolidFire Cinder plugin installation
All of the needed code for using SolidFire in an OpenStack deployment is included in the upstream OpenStack distribution. There are no additional libraries, software packages or licenses.