Embed Size (px)
Citation preview
Guide to the EMC VNX Plugin version 1.0.0 for Fuel
1
Guide to the EMC VNX Plugin version 1.0.0 for Fuel Revision history Document purpose Key terms, acronyms and abbreviations EMC VNX Plugin
Requirements Limitations
Installation Guide EMC VNX backend configuration EMC VNX plugin installation EMC VNX plugin configuration
User Guide Creating Cinder volume
Appendix Components licenses
2
Revision history
Version Revision date Editor Comment
0.1 01.23.2014 Irina Povolotskaya ([email protected])
Created the template structure.
0.2 02.16.2015 Piotr Misiak ([email protected]) Szymon Bańka ([email protected])
Created the first version of document.
0.3 02.17.2015 Irina Povolotskaya ([email protected])
Minor changes.
0.4 03.30.2015 Irina Povolotskaya ([email protected])
Added Document purpose and Key terms, acronyms and abbreviations sections.
0.5 03.31.2015 Piotr Misiak ([email protected]) Installation guide changed to rpm package
0.6 04.02.2015 Piotr Misiak ([email protected]) User guide added
1.0 04.14.2015 Piotr Misiak ([email protected]) Major version
3
Document purpose This document provides instructions for installing, configuring and using EMC VNX plugin for Fuel.
Key terms, acronyms and abbreviations
Term/acronym/abbreviation Definition
EMC VNX Unified, hybridflash storage used for virtual applications and cloudenvironments.
Cinder OpenStack Block Storage.
iSCSI Internet Small Computer System Interface. an Internet Protocol (IP)based storage networking standard for linking data storage facilities. By carrying SCSI commands over IP networks, iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable locationindependent data storage and retrieval.
LVM LVM is a logical volume manager for the Linux kernel that manages disk drives and similar massstorage devices.
LUN Logical Unit Number
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. Enabling EMC VNX plugin in Mirantis OpenStack means that all Cinder services are run on Controller nodes.
4
Requirements EMC VNX plugin for Cinder has the following requirements:
Requirement Version/Comment
Fuel 6.1 release
EMC VNX array It should be configured and deployed. It should be reachable via one of the Mirantis OpenStack networks.
Limitations
1. 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.
2. Fibre Channel driver is not supported.
Installation Guide
EMC VNX backend 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:
Item to confirm Status (tick if done)
Create username/password
Create at least one storage pool
Configure network: for A and B Service Processors for all iSCSI ports
5
EMC VNX plugin installation
1. Download the plugin from the Fuel Plugins Catalog.
2. Copy the plugin on already installed Fuel Master node. If you do not have the Fuel Master node yet, see Quick Start Guide:
# scp emc_vnx-1.0-1.0.0-0.noarch.rpm root@<the_Fuel_Master_node_IP>:/tmp
3. Log into the Fuel Master node. Install the plugin:
# cd /tmp
# fuel plugins --install emc_vnx-1.0-1.0.0-0.noarch.rpm
4. Check if the plugin was installed successfully:
# fuel plugins
id | name | version | package_version
---|---------|---------|----------------
1 | emc_vnx | 1.0.0 | 2.0.0
EMC VNX plugin removal
To uninstall EMC VNX plugin, follow these steps:
1. Delete all Environments in which EMC VNX plugin has been enabled. 2. Uninstall the plugin:
# fuel plugins --remove emc_vnx==1.0.0
1. Check if the plugin was uninstalled successfully:
# fuel plugins
id | name | version | package_version
---|---------------------------|----------|----------------
6
EMC VNX plugin configuration
1. Create an environment with the default backend for Cinder. Do not add Cinder role to any node, because all Cinder services will be run on Controllers. For more information about environment creation, see Mirantis OpenStack User Guide.
2. Open Settings tab of the Fuel web UI and scroll the page down. Select the plugin checkbox and fill in form fields:
Field Comment
Username/password Access credentials configured on EMC VNX.
SP A/B IP IP addresses of the EMC VNX Service Processors.
pool name(optional) The name of the EMC VNX storage pool on which all Cinder volumes will be created. The 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.
3. Adjust other environment settings to your requirements and deploy the environment.
For more information, see Mirantis OpenStack User Guide.
7
User Guide
Creating Cinder volume To verify that EMC VNX plugin is properly installed, you should create a Cinder volume and attach it to a newly created VM using for example OpenStack CLI tools. 1. Create a Cinder volume. In this example, a 10GB volume was created using cinder create <volume size> command:
2. Using cinder list command (see the screenshot above), let’s check if the volume was created. The output provides information on ID, Status (it’s available), Size (10) and some other parameters.
8
3. Now you can see how it looks on the EMC VNX. In the example environment, EMC VNX SP has 192.168.200.30 IP address. Before you do this, add /opt/Navisphere/bindirectory to PATH environment variable using export PATH=$PATH:/opt/Navisphere/bincommand and save your EMC credentials using naviseccli -addusersecurity -password <password> -scope 0 -user <username>
command to simplify syntax in succeeding naviseccli commands. Use naviseccli -h <SP IP> lun -list command to list LUNs created on the EMC:
In the given example there is one LUN with ID: 0, name: volume-e1626d9e-82e8-4279-808e-5fcd18016720 (naming schema is “volume<Cinder volume id>”) and it is in “Ready” state, so everything is fine.
9
4. Now create a new VM. To do this, you have to know IDs of a glance image (use glance image-list command) and a network (use nova net-list command):
Note the VM’s ID which is 48e70690-2590-45c7-b01d-6d69322991c3 in the given example.
10
5. Show details of the new VM to check its state and to see on which node it has been created (use nova show <id> command). In the output, we see that the VM is running on the node3 and it is active:
6. Attach the Cinder volume to the VM (use nova volume-attach <VM id> <volume id>) and verify using cinder list command:
11
7. To list storage groups configured on EMC VNX, use naviseccli -h <SP IP> storagegroup -list command:
There is one “node3” storage group with one LUN attached. The LUN has local ID 0 (ALU Number) and it is available as LUN 133 (HLU Number) for the node3. There are four iSCSI HBA/SP Pairs one per the SPPort pair.
12
8. You can also check if iSCSI sessions are active using naviseccli -h <SP IP> port -list -hba command:
Look at “Logged In” parameter of each port. In the given example, all four sessions are active (in the output, it looks like Logged In: YES).
13
9. When you log into the node3 node, you can verify the following; if iSCSI sessions are active using iscsiadm -m session command, if a multipath device has been created by multipath daemon using multipath -ll command, if VM is using the multipath device using lsof -n -p pgrep -f <VM id> | grep /dev/<DM device name> command:
In the example, there are four active sessions (the same as on the EMC) and the multipath device dm2 has been created. The multipath device has four paths and all are running (each one per iSCSI session). In the output of the third command, you can see that qemu is using /dev/dm2 multipath device, so everything is fine.
Appendix Multiple pools support OpenStack CLI Fuel Plugins CLI guide
Components licenses deb packages: multipathtools: GPL2.0 naviclilinux64x86enus: EMC Freeware Software License rpm packages: kpartx: GPL+ devicemappermultipath: GPL+ devicemappermultipathlibs: GPL+ NaviCLILinux64x86en_US: EMC Freeware Software License
14
