RETIRED, Fuel plugin for SolidFire with Cinder integration
541320330b
1) Use SolidFire puppet module which matches the release of OpenStack in this Fuel release 2) Rename the modules class to controller 3) Call out the module at the correct time within deploy and correct class of node 4) Make environment_config.yaml appropriate for this version of the driver (i.e. no caching) 5) Documents as required 6) Clean up what is checked into git Change-Id: I05283107291d7d8a29502f043a5bb7d49b0c3bb8 |
||
---|---|---|
deployment_scripts/puppet | ||
docs | ||
repositories | ||
specs | ||
.gitignore | ||
.gitreview | ||
environment_config.yaml | ||
LICENSE | ||
metadata.yaml | ||
pre_build_hook | ||
README.md | ||
tasks.yaml |
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.