x
/
fuel-plugin-external-emc
Code Issues Proposed changes
RETIRED, Fuel plugin for Cinder with EMC integration
13 Commits 4 Branches 1 Tag 15 MiB
Go to file
Oleksandr Martsyniuk 5117cc5144 Plugin metadata updated for Fuel 8.0 
- support for new version of plugins SDK added
- deployment tasks updated for latest Fuel version

Change-Id: I34bffaf3c39d3fcf6c0464d536914df160404166
 		2016-04-21 13:04:52 +03:00
deployment_scripts/puppet Plugin metadata updated for Fuel 8.0 2016-04-21 13:04:52 +03:00
doc documentation update: add limitation about emc plugin and cinder role 2015-09-16 12:25:22 +02:00
repositories add EMC VNX plugin code 2015-04-23 21:45:57 +02:00
specs fix MOS version in Dependencies section in the spec file 2015-04-28 16:18:14 +02:00
.gitignore change compatible MOS version and OS releases in the metadata.yaml 2015-08-07 13:42:16 +02:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:23:14 +00:00
LICENSE add EMC VNX plugin code 2015-04-23 21:45:57 +02:00
README.md Plugin metadata updated for Fuel 8.0 2016-04-21 13:04:52 +03:00
components.yaml Plugin metadata updated for Fuel 8.0 2016-04-21 13:04:52 +03:00
deployment_tasks.yaml Plugin metadata updated for Fuel 8.0 2016-04-21 13:04:52 +03:00
environment_config.yaml add EMC VNX plugin code 2015-04-23 21:45:57 +02:00
metadata.yaml Plugin metadata updated for Fuel 8.0 2016-04-21 13:04:52 +03:00
pre_build_hook change compatible MOS version and OS releases in the metadata.yaml 2015-08-07 13:42:16 +02:00
tasks.yaml Plugin metadata updated for Fuel 8.0 2016-04-21 13:04:52 +03:00

README.md

EMC VNX Plugin for Fuel

EMC VNX plugin

EMC VNX plugin for Fuel extends Mirantis OpenStack functionality by adding support for EMC VNX arrays in Cinder using iSCSI protocol. It replaces Cinder LVM driver which is the default volume backend that uses local volumes managed by LVM.

Requirements

Requirement Version/Comment
Mirantis OpenStack compatibility 8.0

Limitations

Since only one storage network is available in Fuel 6.x on OpenStack nodes, multipath will bind all storage paths from EMC on one network interface. In case this NIC fails, the communication with storage is lost.

Installation Guide

EMC VNX configuration

Before starting a deployment you have to preconfigure EMC VNX array and connect it properly to the environment. Both EMC SP IPs and all iSCSI ports should be available over storage interface from OpenStack nodes. To learn more about EMC VNX configuration, see the official EMC VNX series documentation

EMC VNX configuration checklist:

  1. create username/password
  2. create at least one storage pool
  3. configure network for A and B Service Processors
  4. configure network for all iSCSI ports

EMC VNX plugin installation

To install EMC VNX plugin, follow these steps:

  1. Download the plugin from Fuel Plugins Catalog

  2. Copy the plugin on already installed Fuel Master node; ssh can be used for that. If you do not have the Fuel Master node yet, see Quick Start Guide:

     # scp emc_vnx-3.0-3.0.0-0.noarch.rpm root@<Fuel_master_ip>:/tmp

  3. Log into the Fuel Master node. Install the plugin:

     # cd /tmp
 # fuel plugins --install emc_vnx-2.0-2.0.0-0.noarch.rpm

  4. Check if the plugin was installed successfully:

     # fuel plugins
 id | name    | version | package_version
 ---|---------|---------|----------------
 1  | emc_vnx | 3.0.0   | 3.0.0

EMC VNX plugin configuration

  1. Create an environment with the default backend for Cinder.
  2. Enable the plugin on the Settings tab of the Fuel web UI and fill in form fields:
    • username/password - access credentials configured on EMC VNX
    • SP A/B IP - IP addresses of the EMC VNX Service Processors
    • pool name (optional) - a name of the EMC VNX storage pool on which all Cinder volumes will be created. Provided storage pool must be available on EMC VNX. If pool name is not provided then EMC VNX driver will use a random storage pool available on EMC VNX. You can also use a Volume Type OpenStack feature to create a volume on a specific storage pool. For more information, see [Multiple pools support](https://github.com/emc-openstack/vnx-direct-driver /blob/master/README_ISCSI.md#multiple-pools-support)
  3. Deploy the environment without a Cinder node. All required Cinder services are run on Controller nodes.