HP XP Storage Cinder Volume Driver Software User Guide

Transcription

1 HP XP Storage Cinder Volume Driver Software User Guide Abstract HP XP Storage Cinder Volume Driver Software is a driver for Cinder, which is the block storage management component, in OpenStack environments. This software allows you to use high-performance and high-reliability HP storage features for backend storage managed by Cinder. Part Number: Z Published: November 2015 Edition: 1.1

2 Copyright 2015 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Acknowledgments Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are trademarks of the Microsoft group of companies. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java and Oracle are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group. Warranty WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website: Revision History Date Version Edition Description October First First Edition November Second Second Edition

3 Contents 1 Overview...7 OpenStack...7 Cinder HP XP Storage Cinder Volume Driver Software features...8 Backend storage management configuration...8 Volume operation...8 Creating and deleting a volume...8 Extending a volume...8 Copying a volume...9 Creating snapshots...9 Using snapshots to create a volume...10 Creating a cloned volume...10 Function for sharing the V-VOL as a read-only volume (HP extended)...10 Function for snapshot or volume restoration (HP extended)...10 Volume connection function...11 Attach volumes and Detach volumes function...12 HP XP7 Cinder Driver Software supported functions...12 OpenStack feature support Operating environment for HP XP Storage Cinder Volume Driver Software...15 Hardware...15 Software...15 Hardware and software restrictions Installation and configuration of HP XP7 Storage Cinder Volume Driver Software...19 Installing HP XP7 Storage Cinder Volume Driver Software...19 Environment setup...19 Pre-check storage setting...20 Connection setting of the node...20 Node setting...20 Resource setting of the storage...21 Creating a Resource-Group...21 Creating an account...21 Creating a THP pool...22 Setting port security...22 Manually setting the storage control path for the Controller node...22 Creating a host group for I/O data path...22 Setting FC zoning...23 System rebooting...23 Configure the storage management software...23 HP XP7 Cinder Driver software Installation...24 Memory size...24 Disk space...24 Pre-installation check...24 HP XP7 Cinder Driver software Installation...24 Initial settings...25 Preparation...25 Associating Volume type and backend...27 Adding the configuration of HP XP7 Cinder Driver software...27 Restarting Cinder...28 Operation check...29 Contents 3

4 HP XP7 Cinder Driver software Updating...30 HP XP7 Cinder Driver software Uninstallation...30 Usage of Manage Volume...30 Setting for the live migration function...30 Redundancy setup of I/O data path in each node...31 Setting up redundant control paths to the storage device...31 Redundancy setup of command device (In-Band) in HP XP7/P HA support on Controller node...32 Pacemaker configurations for Cinder-Volume...33 Configuration of HP XP7 Cinder Driver software in HA environment...34 Failure range to be able to save by system switching...35 Handling process for remaining resources when system switching...35 Restrictions on HA environment...36 Notes on use...37 Notes on operation time of HP XP Cinder Driver software Syntax of HP XP Storage Cinder Volume Driver Software...41 Configuration file...41 Notes for setting parameters...45 Cinder commands...45 Using HP s extended functions...45 Selecting a volume copy method...45 Restoring a volume or snapshot...46 Sharing by using a read-only volume...47 hpxpgetinfo command...47 Files...49 Files installed by HP XP7 Cinder Driver software...49 Files created by HP XP7 Cinder Driver software Troubleshooting for HP XP7 Storage Cinder Driver Software...52 Openstack-cinder-volume service does not start...52 Volume (snapshot) cannot be created...52 Volume (snapshot) cannot be attached...52 Collecting data s of HP XP Storage Cinder Volume Driver Software...53 s output in volume.log...53 Format of output messages...53 Format of message explanations...53 List of messages...54 MSGID0000-I...54 MSGID0001-I...54 MSGID0002-I...54 MSGID0003-I...54 MSGID0300-W...54 MSGID0301-W...54 MSGID0302-W...55 MSGID0304-W...55 MSGID0305-W...55 MSGID0306-W...55 MSGID0308-W...55 MSGID0310-W...56 MSGID0311-W...56 MSGID0312-W...56 MSGID0313-W...56 MSGID0314-W Contents

5 MSGID0315-W...56 MSGID0317-W...57 MSGID0318-W...57 MSGID0319-W...57 MSGID0320-W...57 MSGID0322-W...57 MSGID0323-W...58 MSGID0324-W...58 MSGID0325-W...58 MSGID0326-W...58 MSGID0327-W...58 MSGID0329-W...58 MSGID0600-E...59 MSGID0601-E...59 MSGID0602-E...59 MSGID0603-E...59 MSGID0606-E...59 MSGID0608-E...60 MSGID0609-E...60 MSGID0610-E...60 MSGID0611-E...60 MSGID0612-E...60 MSGID0613-E...61 MSGID0614-E...61 MSGID0615-E...61 MSGID0616-E...61 MSGID0617-E...61 MSGID0618-E...62 MSGID0619-E...62 MSGID0620-E...62 MSGID0624-E...62 MSGID0631-E...62 MSGID0632-E...62 MSGID0633-E...63 MSGID0634-E...63 MSGID0636-E...63 MSGID0637-E...63 MSGID0638-E...63 MSGID0639-E...64 MSGID0640-E...64 MSGID0648-E...64 MSGID0649-E...64 MSGID0650-E...64 MSGID0652-E...64 MSGID0653-E...65 MSGID0654-E...65 MSGID0655-E...65 MSGID0656-E...65 MSGID0657-E...65 MSGID0658-E...66 MSGID0659-E...66 MSGID0660-E...66 MSGID0700-E...66 MSGID0701-E...66 MSGID0702-E...67 Contents 5

6 MSGID0703-E...67 MSGID0704-E...67 MSGID0706-E...67 MSGID0707-E...68 MSGID0710-E...68 MSGID0711-E...68 s output by the hpxpgetinfo command...68 Format of message explanations...68 List of messages...68 s output by the installer...70 Format of message explanations...70 List of messages Support and other resources...72 Contacting HP...72 Subscription service...72 Related information...72 Websites...73 Prerequisites...73 Typographic conventions...73 Customer self repair Product feedback Documentation feedback...75 A Regulatory information Turkey RoHS material content declaration...76 Ukraine RoHS material content declaration...76 Warranty information...76 Glossary...77 Index Contents

7 1 Overview OpenStack OpenStack is the open source software for cloud environment configuration of the IaaS layer and consists of several components. By mutual cooperation of several components, OpenStack automatically makes the necessary resource in hardware pools such as servers, storages, networks according to user-request and provides it to users. Table 1 Main components of OpenStack Component OpenStack Compute (Nova) OpenStack Image (Glance) OpenStack Network (Neutron) OpenStack Object Storage (Swift) OpenStack Block Storage (Cinder) OpenStack Identity (Keystone) OpenStack Dashboard (Horizon) Feature Hypervisor control Image and Snapshot control Virtual network control Object storage control Block storage control Integrated authentication infrastructure Self-service WebUI Description Virtual machine management in the multi-hypervisor environment. VM image management. L2/L3 network management. Provision of high-availability distributed object storage. Provision of permanent block storage to VM Management of authentication of each component in common and operation authorization. Provision of the self-service Web portal. Cinder Cinder is a component that provides a block device to a VM as a volume. The data remains on the block device corresponding to the volume and you can use it permanently by changing the connection to other VMs. In addition, the direct access to block device corresponding to the volume from the VM sets an expectation of high I/O performance. Each storage array must have a corresponding Cinder driver. OpenStack 7

8 2 HP XP Storage Cinder Volume Driver Software features HP XP Storage Cinder Volume Driver Software is a driver for Cinder, which is the block storage management component, in OpenStack environments. HP XP7 Cinder Driver software allows you to use high-performance and high-reliability HP storage features for backend storage managed by Cinder. This chapter describes the HP XP7 Cinder Driver software features. Backend storage management configuration HP XP7 Cinder Driver software uses a THP pool of HP XP Thin Provisioning (a HP storage features that provides virtual volume capability) as backend storage. To use multiple THP pools, register each THP pool as separate backend storage. Volume operation HP XP7 Cinder Driver software provides volume functions that operate on the LDEV (logical device or logical unit) in the target backend storage (THP pool) for each backend. Figure 1 (page 8) shows an overview of the volume operations. Figure 1 Overview of volume operations Creating and deleting a volume Upon receiving Create volume request, HP XP7 Cinder Driver software uses the storage function to create a virtual volume (THP V-VOL) as an LDEV from the THP pool. The THP V-VOL allocates pages only when required, thus saving capacity usage. The created volume can be deleted by using the delete volume storage feature. Because the storage feature clears the contents of the deleted volume to zero, data will not be leaked even if another user recreates the volume. Extending a volume Upon receiving Extend Volume request, HP XP7 Cinder Driver software can extend the size of a THP V-VOL created from the THP pool. This ensures that the extension of volume to the required size without the recreation of a new THP-VOL. 8 HP XP Storage Cinder Volume Driver Software features

9 Copying a volume Upon receiving a Copy volume request, HP XP7 Cinder Driver software uses Business Copy, Fast Snap, or the Linux dd command to copy an LDEV in the HP storage. Figure 2 (page 9) shows an overview of the volume copy functions. Table 2 (page 9) describes the copy methods available to HP XP7 Cinder Driver software. You can select the Business Copy function or the Fast Snap function. However, note that a volume (THP V-VOL) that was copied by using the Fast Snap function is copied to the destination volume by executing the Linux dd command on the Controller node. You need a license to use either Fast Snap or Business Copy. An attempt to copy will fail if you do not have the necessary license. Figure 2 Overview of volume copy Table 2 HP XP7 Cinder Driver software copy methods Copy feature Business Copy (license required) Fast Snap (license required) Execution of the dd command in the Controller node Description All data in the copy source volume (THP V-VOL) is asynchronously copied to the destination volume (THP V-VOL). The user can use both volumes during asynchronous copy. Differential data from the source volume (THP V-VOL) is copied to the virtual volume (V-VOL) as an LDEV at any time. The user can use both volumes. If the source volume is a V-VOL, the dd command is executed in the Controller node to copy the volume to the destination volume (THP V-VOL). The user can use both volumes after the copy is completed. Creating snapshots Upon receiving Create snapshots request, HP XP7 Cinder Driver software uses the copy functions available (see Table 2 (page 9)) to create an LDEV corresponding to the snapshot, and then Copying a volume 9

10 stores the current data of the target volume. The snapshot cannot be attached to a VM, but can be retained as a data backup. Using snapshots to create a volume Upon receiving Create volumes from snapshots request, HP XP7 Cinder Driver software uses copy functions available (see Table 2 (page 9)) to create an LDEV corresponding to the volume, and then stores the data of the specified snapshot. If, for example, data of the source volume of the snapshot is corrupted after the snapshot was taken, you can create a new volume and can replace the corrupted volume. Creating a cloned volume Upon receiving Create cloned volumes request,hp XP7 Cinder Driver software uses copy functions available (see Table 2 (page 9)) to create an LDEV corresponding to the volume, and then store the data of the specified volume. This function is useful when multiple users use the same volume data. Function for sharing the V-VOL as a read-only volume (HP extended) In the case of Create volumes from snapshots operation, when the target LDEV snapshot is a V-VOL, the dd command is executed on the Controller node to copy data to the volume, which might require some time. Use this function for sharing the V-VOL as a read-only volume. The V-VOL of the snapshot can be shared with the new volume. The copy time can be reduced during volume creation (see Figure 3 (page 10)). NOTE: Do not attempt to write to the created volume which is attached to a VM. Figure 3 Volume sharing Function for snapshot or volume restoration (HP extended) If data in the original volume is corrupted, the snapshot function provided by Cinder restores data by creating a new volume from the snapshot. In this case, free space for the created volume is temporarily taken, and the original volume is replaced with the new volume. When you use this function for snapshot or volume restoration, data from the specified snapshot or volume is restored 10 HP XP Storage Cinder Volume Driver Software features

11 to the original volume. This eliminates the need to create a new volume. You can still use the original volume if required (see Figure 4 (page 11)). Figure 4 Snapshot or volume restoration Volume connection function HP XP7 Cinder Driver software provides a volume connection (FC/FCoE) function that attaches the target volume to a VM and detaches it from the VM in a Compute Node. HP XP7 Cinder Driver software can use the multipath configuration.figure 5 (page 12) shows an overview of the volume connection function. Volume connection function 11

12 Figure 5 Overview of volume connection Attach volumes and Detach volumes function Upon receiving Attach Volume request, HP XP7 Cinder Driver software attaches the target volume to a VM in the specified Compute Node. At this time, HP XP7 Cinder Driver software directly connects the HP storage and the Compute Node using FC, or FCoE. This allows the VM in the Compute Node to access the target volume to store data. It is also possible to detach the volume. The volume can be attached to another VM as the data constantly remains in the detached volume. You can also set up a multipath configuration when attaching a volume to a Compute Node. HP XP7 Cinder Driver Software supported functions Table 3 (page 12) lists the functions supported by HP XP7 Cinder Driver software. Table 3 Cinder-specified functions supported by HP XP7 Cinder Driver software Function Create volume Delete volume Attach volume Detach volume Extend volume Migrate volume Create snapshot Delete snapshot Description Creates a volume. Deletes the target volume. Connects a volume to the specified instance. Disconnects the target volume. Expands the size of the target volume. Moves a volume to a THP pool managed by another HP XP7 Cinder Driver software. Creates a snapshot that retains the data of a volume at a given time. If the Fast Snap function is used, snapshot data can be restored to the volume from the snapshot. Deletes the target snapshot. Supported Supported Supported Supported Supported Supported Supported Supported 1, 2 Supported 12 HP XP Storage Cinder Volume Driver Software features

13 Table 3 Cinder-specified functions supported by HP XP7 Cinder Driver software (continued) Function List snapshots Create volume from snapshot Create volume from image Create volume from volume (Clone) Create image from volume Volume migration (host assigned) Get volume status Backup volumes Restore backup Manage volumes Unmanage volumes Description Lists the snapshots. Creates a volume with the same content of a snapshot. If the snapshot is a V-VOL, the V-VOL can be shared with the created volume as a read-only volume. Retrieves images stored from Glance and loads it onto the specified volume. You can start a VM based on the stored images. Creates a volume and then stores the data of the replication source volume. If the Fast Snap function is used, snapshot data can be restored to the volume from the snapshot. Takes images from the volume and registers them in Glance. Moves a volume to a THP pool managed by another HP XP Cinder Driver software. Returns the storage information (the whole virtual capacity, free virtual space, etc). Virtual capacity is the capacity reserved for the overprovisioning of the actual capacity of the THP pool. For example, if the total capacity is 100GB and the subscription rate is 150%: Virtual capacity = 100GB x 150% (150GB) Backs up the data of a volume to Swift using Cinder backup service. Restores data to a specified volume from Swift using Cinder backup service. Adds the LDEV created by a Cinder of other OpenStack system to the management of the target Cinder. Removes the volume which the Cinder created from the Cinder management. Supported Supported Supported 1, 2 Supported Supported 1, 2 Supported Supported Supported Supported Supported Supported 3 Supported 3 Retype volumes Changes the volume type of the volume. 1 The size of the snapshot (volume) to be created cannot be changed. Supported 3 2 HP XP Cinder Driver software can utilize storage copy PP (faster, license required) required or host based dd copy command (longer operation time) (see Table 2 (page 9)) 3 If using the target function by cinder command, it is necessary to set the environment variable OS_VOLUME_API_VERSION=2. OpenStack feature support Table 4 (page 13) lists the OpenStack features supported by HP XP7 Cinder Driver software. Table 4 OpenStack features supported by HP XP7 Cinder Driver software OpenStack features Live Migration Multipath for I/O path Description A running VM attached to the volume managed by HP XP Cinder Driver software can migrate from one Compute node to another Compute node. Multipath enabled for a HP XP7 Cinder Driver software managed volume. Supported Supported Supported OpenStack feature support 13

14 Table 4 OpenStack features supported by HP XP7 Cinder Driver software (continued) OpenStack features FC Zoning Manager High Availability for Controller nodes Description When a volume managed by HP XP7 Cinder Driver software is attached to a VM using FC, FC zoning can automatically be created between the Compute Node and the storage system. Controller nodes can be set to Active/Standby redundant using HA cluster software. Supported Supported Supported (RHEL OSP6 only) 14 HP XP Storage Cinder Volume Driver Software features

15 3 Operating environment for HP XP Storage Cinder Volume Driver Software Hardware Software This chapter describes the hardware and software necessary for using HP XP7 Cinder Driver software. The following describes the hardware necessary for using HP XP7 Cinder Driver software. Hardware configuration: System devices None Maximum/minimum memory size A memory size required by the prerequisite operating environment is required. Storage devices HP XP P9500 Storage (1 FC/FCoE can be used) HP XP7 Storage (1 FC/FCoE can be used) The following describes the necessary software to use HP XP7 Cinder Driver software. 1. OpenStack a. Red Hat Enterprise Linux OpenStack Platform 6 Table 5 Prerequisite operating environment (RHEL OSP6) Node Controller node Item Linux Environment Components Red Hat Enterprise Linux 7 Supported kernel el7(EM64T) or later python-six or later Other software sysfsutils, sg3_utils, iscsi-initiator-utils, device-mapper-multipath OpenStack Environment Openstack-cinder or later Python-cinder or later Python-oslo-config or later Python-oslo-utils or later Compute node Linux Environment Red Hat Enterprise Linux 7 Supported kernel el7 (EM64T) or later Other software sysfsutils, sg3_utils, iscsi-initiator-utils, device-mapper-multipath b. Red Hat Enterprise Linux OpenStack Platform 7 Hardware 15

16 Table 6 Prerequisite operating environment (RHEL OSP7) Node Controller node Item Linux Environment Components Red Hat Enterprise Linux 7 Supported kernel el7 (EM64T) or later python-six or later Other software sysfsutils, sg3_utils, iscsi-initiator-utils, device-mapper-multipath OpenStack Environment Openstack-cinder or later Python-cinder or later Python-oslo-config or later Python-oslo-utils or later Compute node Linux Environment Red Hat Enterprise Linux 7 Supported kernel el7 (EM64T) or later Other software sysfsutils, sg3_utils, iscsi-initiator-utils, device-mapper-multipath c. SUSE OpenStack Cloud 5 Table 7 Prerequisite operating environment (SUSE OpenStack Cloud 5) Node Controller node Item Linux Environment Components SUSE Linux Enterprise Server 11 SP3 Supported kernel (EM64T) or later python-six or later Other software sysfsutils, sg3_utils, open-iscsi, multipath-tools OpenStack Environment Openstack-cinder or later Python-cinder or later Python-oslo-config or later Python-oslo-utils or later Compute node Linux Environment SUSE Linux Enterprise Server 11 SP3 Supported kernel (EM64T) or later Other software sysfsutils, sg3_utils, open-iscsi, multipath-tools 2. Storage management software HP XP7 and HP XP9500 uses the RAID Manager software. 3. Storage software license HP XP7 and HP XP9500 requires the following storage software licenses: Thin provisioning Business Copy Fast Snap 16 Operating environment for HP XP Storage Cinder Volume Driver Software

17 4. Support matrix for HP XP7 Cinder Driver software Table 8 Support Scope for HP XP7 Cinder Driver Software (Storage) Software HP XP7 HP XP9500 v1.3 v1.4 RHEL OSP6 RHEL OSP6 Supported ( or later) Supported ( or later) RHEL OSP7 SUSE OpenStack Cloud 5 Supported ( x or later) Table 9 Support Scope for HP XP7 Cinder Driver software (Storage management software) Software v1.3 v1.4 RHEL OSP6 RHEL OSP6 RHEL OSP7 SUSE OpenStack Cloud 5 RAID Manager Supported (In-Band) ( or later) Supported (In-Band) ( or later) 5. Excluded software None Hardware and software restrictions Hardware restrictions For all HP storages, the name of resources such as pool, host group, and so on (see Environment setup (page 19)) that are used by HP XP Cinder Driver software must not be kept blank. For HP XP7 storage, virtual LDEV operations defined for virtual storage machines that are commonly used with High Availability or after migration with Online Migration are not supported. Use the volume operations with THP-VOL targets that are not assigned to a virtual storage machine. Software restrictions When using dm-multipath on the Controller node, you must not use command devices like a multi-path device. Register the command devices in the blacklist in the configuration file multipath.conf. In the case of a single node configuration (which combines Controller node and Compute Node), the following operations cannot be performed for the volume attached to the VM. If you perform the following operations, VM cannot access the volume. If a V-VOL is attached, you cannot create cloned volumes or create snapshots for the volume. If a THP V-VOL/V-VOL is attached, you cannot copy the volume to images. If a Read-only volume is attached, you cannot create volumes for the original snapshot for the volume. Hardware and software restrictions 17

18 Perform the operations for the volume after the volume has been detached. After the operation, attach it again. Temporary restrictions regarding software None 18 Operating environment for HP XP Storage Cinder Volume Driver Software

19 4 Installation and configuration of HP XP7 Storage Cinder Volume Driver Software This chapter describes how to use the HP XP7 Cinder Driver software. Installing HP XP7 Storage Cinder Volume Driver Software The following procedure describes how to install HP XP7 Cinder Driver software. A Linux superuser (i.e. root) is required to install HP XP7 Cinder Driver software. Figure 3-5 shows the HP XP7 Cinder Driver software installation procedure. Figure 3-5 HP XP7 Cinder Driver software installation procedure HP XP7 Cinder Driver software installation procedure: 1. Environment setup a. Pre-check storage setting Confirm that the basic operations for the storage are carried out. b. Connection setting of the node Connect each nodes and the storage. c. Node setting Set each node to the necessary setting. d. Resource setting of the storage Perform the resource setting of the storage using HP XP7 Cinder Driver software. e. Setting of the storage operation software Install operation software for the storage. 2. HP XP7 Cinder Driver software installation a. Memory size check Verify that the memory is adequate. b. Disk usage check Confirm that the disk space requirements are met. c. Pre-installation check Confirm that the prerequisite software are present and are in a normal state. d. Installation Install HP XP Storage Cinder Volume Driver Software. e. Initial settings Specify the initial settings required to operate HP XP Storage Cinder Volume Driver Software. f. Operation check Environment setup Confirm that HP XP Storage Cinder Volume Driver Software is operating correctly. It is necessary to set the storage device to allow HP XP7 Cinder Driver software to use it. For more information, see the HP XP7 Array Configuration User Guide. Installing HP XP7 Storage Cinder Volume Driver Software 19

20 Pre-check storage setting Before setting the storage device to allow HP XP7 Cinder Driver software to use it, using Remote Web Console software, confirm that LDEVs can be created, deleted, connected to the server, and asynchronously copied, and host groups can be created and deleted. Connection setting of the node Connect between each Controller/Compute Node and the storage device. HP XP7 Cinder Driver software can separately manage the ports which Controller node uses and the ports which Compute Node uses as data path. Therefore design the connection setting based on an operation policy. Figure 6 (page 20) shows an example of connection configuration. Figure 6 Connection configuration example for HP XP7/P9500 Node setting Build the Controller node and Compute nodes in advance using the OpenStack configuration installer (for example, Foreman) provided by each distribution. A multi-node configuration (which is a separate Controller node and Compute Node) is recommended. Some OpenStack configuration installers might require you to specify a Cinder driver when the OpenStack configuration installer deploys Cinder component. As selection of HP XP Cinder Driver software is not possible at this point, specify another driver (such as NFS). After the deployment, install HP XP Cinder Driver software. See the Red Hat Enterprise Linux website for information on using OpenStack. After building Controller node and Compute nodes, set the following in each node. 20 Installation and configuration of HP XP7 Storage Cinder Volume Driver Software

21 Table 10 Setting contents for each node Node type Controller node Compute Node Items my_ip for cinder service (/etc/cinder/cinder.conf) my_ip for Nova Compute service (/etc/nova/nova.conf) Contents Specify IPv4 address for management LAN of the node. The IPv4 address must be a unique value among other nodes. (less than 15 characters) Specify IPv4 address for management LAN of the node. The IPv4 address must be a unique value among other nodes. (less than 15 characters) Resource setting of the storage For a target storage device, set the following resources to allow HP XP7 Cinder Driver software to use each FC connection. Creating a Resource-Group Creating an account Creating a THP pool Setting port security Manually setting the storage control path for the Controller node Creating a host group for I/O data path Setting FC zoning System rebooting NOTE: For FC connection, after all host groups are created, reboot Controller node and Compute Nodes to recognize the path to a storage device. Creating a Resource-Group If you are using a new Resource-Group for an OpenStack system, create the new Resource-Group and assign the necessary resources (for example, LDEVs (for command device and pool included), port, host group, and so on) to the new Resource-Group. Creating an account To log in to the target storage from HP XP7 Cinder Driver software, you must create an account which is a member of each user group. The user groups are: Storage Administrator (View Only) Storage Administrator (Provisioning) Storage Administrator (Local Copy) Storage Administrator (Performance Management) These user groups have management privileges for the created Resource-Group. NOTE: If HP XP7 Cinder Driver software uses multiple storage devices, create the same account name and password, and set the same Resource-Group and original authority. Environment setup 21

22 Creating a THP pool Create a THP pool that the backend of HP XP7 Cinder Driver software uses. HP XP7 Cinder Driver software manages it by a virtual capacity (the capacity reserved for over provisioning of the actual capacity of the THP pool), thus set the over provisioning based on an operation policy. If the over provisioning is set to 100%, space for the actual capacity is guaranteed. If you are using Fast Snap, create a pool for Fast Snap. Setting port security For the port used by HP XP7 Cinder Driver software, enable Port Security. Manually setting the storage control path for the Controller node Manually set the host group for the Controller node so that the Controller node operates the target storage device using the command device (In-Band). Creating a command device Create a command device (In-Band) which has the LDEV number assigned to the created Resource-Group, and set Command Device Attributes (Security is disable, User Authentication is enable, Device Group Definition is disable). Manually creating the host group for the Controller node Manually create the host group for the Controller node at the ports that are used as storage control path, and manually set WWN, ports, and FC zoning depending on the configuration. The ports that the Controller node uses as storage control path is also used as I/O data path. In this case, create the host group according to the description provided in Creating a host group for I/O data path (page 22) Mapping the command device Map the command device (In-Band) to the new host group for the Controller node. Creating a host group for I/O data path Manual setting When you are creating a host group manually consider the following. In the multipath configuration, create a host group for connecting ports. Unit for creating a host group. Create a host group for each node in the port that connects to the Controller node and Compute Nodes. In the multipath configuration, create it in multiple ports. Host group name The Host group must be named HPXP--<mu_ip>. For example HPXP The IP address needs to match the IP of the controller node. WWN Register the WWN of the connecting node in the new host group. Automatically setting When HP XP7 Cinder Driver software attaches an LDEV to a target VM, the software automatically creates the host group for the node of the target VM at the ports which are specified by hpxp_target_ports or hpxp_computer_target_ports if the host groups do not exist in the ports. The hpxp_group_request parameter must be True to automatically create the host group. 22 Installation and configuration of HP XP7 Storage Cinder Volume Driver Software

23 Setting FC zoning To recognize the LDEV to the node with creating the host group simultaneously: The node and the storage device must be connected by FC switches. The FC zoning manager function must be enabled. For all ports that are specified by hpxp_target_ports or hpxp_computer_target_ports parameter, HP XP7 Cinder Driver software creates host groups, and registers all WWN that belongs to the node. Manual setting For FC switches between a node and the storage device, manually set FC zoning. Automatically setting System rebooting When HP XP7 Cinder Driver software attaches a volume to the target VM, FC zoning manager automatically creates FC zoning between the target node and the port used by HP XP7 Cinder Driver software. To automatically create FC zoning: FC zoning manager must be enabled. hpxp_zoning_request must be True. If the host groups for the Controller node and Compute node are created manually, reboot the nodes to recognize these paths. (When you add a new Compute node, if the host group for this node is created manually, rebooting is necessary for only this node.) Configure the storage management software Designated management software must be configured on the Controller node for each target storage device. Setting HP XP 7 RAID Manager for HP XP7/P9500 storage Use HP XP 7 RAID Manager to operate for HP XP7/P9500: 1. Install HP XP 7 RAID Manager Install RAID Manager on the Controller node. Refer to the HP XP7 RAID Manager Installation and Configuration User Guide for installation instructions. Then, set the command device (In-Band) in the Controller node to operate the target storage. 2. At the command device (In-Band) Confirm that there is a connection to a command device Controller node uses a command device to operate the target storage device. Confirm that the Controller node recognizes the command device by using the inqraid command. # /HORCM/usr/bin/inqraid -CLI /dev/sd* Create the configuration file for horcm instance The horcmxxx.conf (XXX instance number used by HP XP7 Cinder Driver software) file for the horcm instance used by HP XP7 Cinder Driver software is automatically created by default if horcmxxx.conf does not exist when the driver starts. HP XP7 Cinder Driver software registers one command device which has the storage device specified in the horcmxxx.conf file. So, in case of automatic creation by HP XP7 Cinder Driver software, manual editing of horcmxxx.conf is unnecessary. Environment setup 23

24 Set hpxp_horcm_add_conf parameter to False to prevent HP XP7 Cinder Driver software from overwriting the horcmxxx.conf. See the HP XP7 RAID Manager User Guide for installation instructions about horcmxxx.conf. NOTE: In case of other existing backends, the operating instance number and pairing instance number must have different values. The instance number that is already used by other applications in the Controller node must not be used. HP XP7 Cinder Driver software Installation Memory size Disk space The following amount of physical memory is used for HP XP7 Cinder Driver software: Memory size = 1 MB x number of backends x 2 1. For installation Table 11 (page 24) shows the disk space required to install HP XP7 Cinder Driver software. Table 11 Disk space required to install HP XP7 Cinder Driver software Item HP XP7 Cinder Driver software file rootwrap file sudo file hpxpgetinfo Size 1MB 1MB 1MB 1MB Location <PATH>/ site-packages/cinder/volume/drivers/san/hp/hpxp <PATH>: RHEL7 is /usr/lib/python2.7 SLES11 is /usr/lib64/python /etc/cinder/rootwrap.d/ /etc/sudoers.d /opt/hp/hpxp 2. For operation Table 12 (page 24) shows the disk space required to operate HP XP7 Cinder Driver software. Table 12 Disk space required to operate HP XP7 Cinder Driver software Item HP XP7 Cinder Driver software log file Size 100MB Location /var/log/hpxp/ Pre-installation check Check for missing or invalid packages, see Software (page 15) Use the rpm command with the -V option specified to confirm that these packages are installed and in a normal state. If a package is not installed or an invalid package is found, install the package again. HP XP7 Cinder Driver software Installation Use the rpm command to install HP XP7 Cinder Driver software. You must log in as a superuser (root) on the machine where you need to install HP XP7 Cinder Driver software. For details about how to use the rpm command, see the online manual for the rpm command. 24 Installation and configuration of HP XP7 Storage Cinder Volume Driver Software

25 1. Mounting the CD-ROM file system To mount the CD-ROM file system when HP XP7 Cinder Driver software is installed from CD-ROM, enter the following command: # /bin/mount -r -o mode=0544 /dev/cdrom /media Change the device special file name and mount directory name (dev/cdrom and /media) for the CD-ROM file system according to your environment. 2. Performing the installation Use the rpm command to install HP XP7 Cinder Driver software. Install the RPM package appropriate for your OpenStack environment. HP XP7 Cinder Driver software RPM package and supported OpenStack version: Table 13 RPM package Supported OpenStack Version HP XP Cinder Driver software version HP XP Cinder Driver software RPM package name RPM storage directory RHEL OSP6 v1.4 hpxp _ el7.noarch.rpm RPMS/RHEL/noarch RHEL OSP7 v1.4 hpxp _ el7.noarch.rpm SUSE OpenStack Cloud 5 v1.4 hpxp _ noarch.rpm RPMS/SUSE/noarch Before you attempt to install HP XP7 Cinder Driver software, stop the openstack-cinder-volume and openstack-cinder-backup services. # /sbin/service openstack-cinder-volume stop # /sbin/service openstack-cinder-backup stop For RHEL7, use systemctl command. After these services are stopped, execute the rpm command to install HP XP7 Cinder Driver software. The mount directory name for the CD-ROM file system is the same as the directory name that was specified when the CD-ROM was mounted. # /bin/rpm -ivh /media/rpm-storage-directory/rpm-package-name The following shows an example of installing HP XP7 Cinder Driver software: # /bin/rpm -ivh /media/rpms/noarch/rhel/hpxp _ el7.noarch.rpm 3. Unmounting the CD-ROM file system Initial settings Preparation After the installation is completed, enter the command to unmount the CD-ROM file system. The mount directory name (/media) for the CD-ROM file system is the same as the directory name that was specified when the CD-ROM was mounted. # /bin/umount/media The configuration of HP XP Cinder Driver software is added to the configuration file (/etc/ cinder/cinder.conf) provided by openstack-cinder package. Some OpenStack configuration installers might automatically reflect the configurations to cinder.conf by using a configuration management software (for example, puppet). The preparation and the place where configuration of HP XP7 Cinder Driver software is added differs with each OpenStack configuration installer. Initial settings 25

26 1. Using packstack provided by RHEL OSP If you are using packstack, preparation is not necessary. To configure HP XP Cinder Driver software, edit the configuration file (/etc/cinder/cinder.conf) on the Controller node. 2. Using Foreman provided by RHEL OSP6 Puppet agent runs when HA configuration is built using Foreman. Puppet agent restores cinder.conf of Controller node according to the template if there is a part that is different from template. Therefore, the configuration is reverted by Puppet agent, even though HP XP7 Cinder Driver software is configured in cinder.conf. To resolve this issue, register the name of backend definition section for HP XP Cinder Driver software (see Adding the configuration of HP XP7 Cinder Driver software (page 27)) in enabled_backends for the file on the Foreman server (/etc/puppet/environments/ production/modules/quickstack/ manifests/cinder_volume.pp). To use multiple backends, specify the names of backend definition section. Before modification: # ensure multiple backends config option is empty class { 'cinder::backends': enabled_backends => [], } After modification: # ensure multiple backends config option is empty class { 'cinder::backends': enabled_backends => ['XP7'], } To configure HP XP Cinder Driver software, edit the configuration file (/etc/cinder/ cinder.conf) on all Controller nodes. Then add the names of backend definition section to the file. 3. Using Director provided by RHEL OSP7 Puppet agent runs on the Controller node when HA configuration is built by using Director. Puppet agent restores cinder.conf of Controller node according to template if there is a part that is different from template. Therefore, the configuration is reverted using Puppet agent, even though HP XP7 Cinder Driver software configuration occurs in cinder.conf. To resolve this issue, disable Puppet agent on all Controller nodes. # puppet agent --disable To configure HP XP7 Cinder Driver software, edit the configuration file (/etc/cinder/ cinder.conf) on all Controller nodes. The Director cannot add nodes when the Puppet agent is stopped. Before you add a node backup cinder.conf and run the Puppet agent. Then add the node. After you add the node, disable the Puppet agent, and restore the configuration file with the backed-up cinder.conf. 4. Using Crowbar provided by SUSE OpenStack Cloud5 Chef agent runs on the Controller node when HA configuration is built by using Crowbar. Chef restores cinder.conf of Controller node according to template if there is a part that is different from template. Therefore, the configuration is reverted using Chef, even though HP XP7 Cinder Driver software configuration occurs in cinder.conf. To resolve this issue, add configuration of HP XP Cinder Driver software to the page adding Cinder backend on WebGUI of Crowbar. Input procedure on Crowbar is as follows: 1. Access WebGUI of Crowbar, and select OpenStack from Barclamps drop-down-menu. 26 Installation and configuration of HP XP7 Storage Cinder Volume Driver Software

27 2. Click Edit in Cinder. 3. Select Other Driver in Type of Volume menu on Add new Cinder Backend field. Input the name of backend in Name of Backend input-field, and click Add Backend option. 4. In created backend filed, input the driver path for HP XP7 Cinder Driver software to Driver and the parameters for HP XP7 Cinder Driver software to Options in the input-fields. 5. In Deployment field, set the using Controller node (only one selectable) to cinder-controller. And specify the using Cinder backends (some selectable) to cinder-volum in the input-field. 6. 6) Click Apply to save the configuration and execute to deploy. Associating Volume type and backend To specify a backend when creating a volume for users, you must first create a volume type using the cinder command in the controller node. Next, associate the volume_backend_name name/value pair with the volume type. # /usr/bin/cinder type-create <volume type name> # /usr/bin/cinder type-key <volume type name> set volume_backend_name=<volume backend name> The following shows an example in which a volume type named HPXP_SAMPLE1 is created and the backend name hpxp_backend1 is registered: # /usr/bin/cinder type-create HPXP_SAMPLE1 # /usr/bin/cinder type-key HPXP_SAMPLE1 set volume_backend_name=hpxp_backend1 Use the cinder extra-specs-list command to check the volume type that you created and the value registered for the volume_backend_name key. # /usr/bin/cinder extra-specs-list ID Name extra_specs <Volume Type ID> HPXP_SAMPLE1 {u'volume_backend_name': u'hpxp_backend1'} By specifying the above backend name for the parameter volume_backend_name during backend setup, you can associate the volume type and backend. Adding the configuration of HP XP7 Cinder Driver software Add the configuration of HP XP7 Cinder Driver software to the editing target (see Preparation (page 25)). After this, adding it to the configuration file (/etc/cinder/cinder.conf) provided by the openstack-cinder package is explained. Edit the configuration file (/etc/cinder/cinder.conf) provided by the openstack-cinder package. For details about editing, see Configuration file (page 41). The following provides an example in which a THP pool for HP XP7 is registered in Cinder as backend storage. In Default section: Enable backend list: HP XP7 Cinder Driver software (shown in the cinder.conf sample below) logging format: Thread information is add to default format to log analisys. Initial settings 27

28 In HP XP7 section: Backend definition section: HP XP7 Cinder Driver software (any string) Backend name registered with the volume type using the cinder type-key command shown in Associating Volume type and backend (page 27).: hpxp_backend1 Volume driver: cinder.volume.drivers.san.hp.hpxp.hp_xp_fc.hpxpfcdriver Storage device serial number: THP pool ID: 0 TI pool ID for Fast Snap: 1 Login user name to the target storage: user Login password to the target storage: password Storage controller port names which Controller node uses: CL1-A,CL2-A Storage controller port names which Compute Nodes use: CL1-B,CL2-B ###################### # cinder.conf sample # ###################### [DEFAULT] (Omitted) enabled_backends=xp7 (*Note) (logging_context_format_string=%(asctime)s.%(msecs)03d %(process)d %(thread)s %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s (*Note) (Omitted) [XP7] volume_driver=cinder.volume.drivers.san.hp.hpxp.hp_xp_fc.hpxpfcdriver volume_backend_name=hpxp_backend1 hpxp_storage_cli=horcm hpxp_storage_id=12345 hpxp_pool=0 hpxp_thin_pool=1 hpxp_horcm_user=user hpxp_horcm_password=password hpxp_target_ports=cl1-a,cl2-a hpxp_compute_target_ports=cl1-b,cl2-b NOTE: The parameter enabled_backends and logging_context_format_string must be included in the DEFAULT section. To specify multiple backends, add each backend definition section in the same way as above, and then use commas to separate the backend definition sections when specifying the labels for the parameter enabled_backends. If the ports which each backend uses are shared among backends, specify the same ports to the parameter for each backends (for example, backend1=cl1-a,cl1-b backend2=cl1-a,cl1-b). In the case that the ports are shared partly among backends (ex: backend1=cl1-a,cl1-b backend2=cl1-b,cl3-a), the Attach volume command might fail in multipath configurations. Restarting Cinder Restart the Cinder service. # /sbin/service openstack-cinder-volume restart Currently stopped openstack-cinder-volume: [ OK ] Currently starting openstack-cinder-volume: [ OK ] For RHEL7, use systemctl command. Restart the openstack-cinder-backup service. 28 Installation and configuration of HP XP7 Storage Cinder Volume Driver Software

29 Operation check 1. Pre-operation check by the storage operation software Before you confirm the usage of HP XP7 Cinder Driver software, using the storage operation software (for example, HP XP 7 RAID Manager), confirm that the LDEVs can be created, deleted, connected to the controller node and compute node, and asynchronously copied, and that host groups can be created and deleted. If either operation fails, see the troubleshooting manual for the storage operation software, and review the built environment. 2. Confirm that HP XP7 Cinder Driver software is used After restarting the Cinder service, confirm that MSGID0003-I is output to the log file (RHEL OSP: /var/log/cinder/volume.log, SUSE OpenStack Cloud: /var/log/cinder-volume.log ) for the number of backends that have been set. Use the command cinder service-list to confirm that the status of the host having the same backend name as above is up. The backends for which confirmation is successful can be used for the volume operations described later. If the message MSGID0003-I is not output, check and, if necessary, revise the configuration file, including the settings for other backends. # /bin/grep MSGID0003-I/var/log/cinder/volume.log :34: WARNING cinder.volume.drivers.san.hp.hpxp.hp_xp_common [req-c9c a-4bcb-8c6d-ac48910e5052 None None] MSGID0003-I: The storage backend can be used. (config group: XP7) # /usr/bin/cinder service-list Binary Host Zone Status State Updated_at cinder-backup hostname.localdomain nova enabled up T12:31: cinder-scheduler hostname.localdomain nova enabled up T12:31: cinder-volume hostname.localdomain@hpxp nova enabled up T02:55: Confirming Create volume From the Horizon portal site, confirm that a volume can be created for a backend of HP XP7 Cinder Driver software. 4. Confirming Attach volume From the Horizon portal site, confirm that a volume can be attached to a VM. 5. Confirming Detach volume From the Horizon portal site, confirm that a volume can be detached from a VM. 6. Confirming Create Snapshot From the Horizon portal site, confirm that a snapshot of a volume can be created. 7. Confirming Create volume from Snapshot From the Horizon portal site, confirm that a volume can be created based on a snapshot. 8. Confirming Delete volume From the Horizon portal site, confirm that volumes created based on snapshots can be deleted. 9. Confirming Delete Snapshot From the Horizon portal site, confirm that snapshots can be deleted. Operation check 29