Hyper Scale-Out Platform Setting Up and Configuring

Transcription

1 Hyper Scale-Out Platform Setting Up and Configuring 1.1 FASTFIND LINKS Document Organization Product version Getting help Contents MK-94HSP003-01

2 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Data Systems Corporation (collectively Hitachi ). Licensee may make copies of the Materials provided that any such copy is: (i) created as an essential step in utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not make any other copies of the Materials. Materials mean text, data, photographs, graphics, audio, video and documents. Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials contain the most current information available at the time of publication. Some of the features described in the Materials may not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at Notice. Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of Hitachi products is governed by the terms of your agreements with Hitachi Data Systems Corporation. By using this software, you agree that you are responsible for: 1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and other individuals to access relevant data; and 2. Verifying that data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws. Notice Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hi-Track is a registered trademark of Hitachi, Ltd. All other trademarks, service marks, and company names in this document or website are properties of their respective owners. ii

3 Contents Preface v Intended audience v Product version vi Release notes vi Document organization vi Document conventions vi Conventions for storage capacity vii Accessing product documentation viii Getting help viii Comments viii 1 Preparing for installation Network requirements External network Internal network Client system requirements GUI browser requirement HSP hardware assembly HSP hardware overview About the racks About the nodes Assembling the hardware Overview of assembly steps Tools you need Step 1: Preparing the rack Step 2: Installing nodes Step 2a: Installing the outer rails on the rack Contents iii

4 Step 2b: Installing the node on the rack Step 3: Cabling the nodes HSP software initialization and configuration HSP software overview Initializing the cluster Monitoring cluster formation Configuring your cluster Configuring SMTP for notifications Preparing your cluster for file services Ways to manage your cluster Final preparation for client access Adding file systems using the Management Console Adding file systems using the command line interface Documentation resources iv

5 Preface Hyper Scale-Out Platform (HSP) is an OpenStack-compatible, distributed scale-out appliance solution. HSP provides a hyper-converged storage and compute environment that allows virtualized applications to run at the source of the data on a single platform. HSP aggregates the storage from multiple homogenous nodes into a single storage pool. Multiple thinly provisioned file systems are created on top of this storage pool, and client systems can access these file systems from any node in the storage pool using the NFS protocol. This Preface includes the following information: Intended audience Product version Release notes Document organization Document conventions Conventions for storage capacity Accessing product documentation Getting help Comments Intended audience This document is intended for anyone responsible for unpacking, setting up, and configuring HSP at a customer site. To setup and configure HSP, you should have experience with and knowledge of the: Basic hardware components of HSP and their functionality Linux operating system and working in a restricted shell environment Site-specific network information Preface v

6 Product version Release notes This document revision applies to Hyper Scale-Out Platform 1.1 or later. Read the release notes before installing and using this product. The release notes may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document. Document organization The following table provides an overview of the contents and organization of this document. Click the hyperlinked chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter Title Chapter 1, Preparing for installation Chapter 2, HSP hardware assembly Chapter 3, HSP software initialization and configuration Chapter 4, Preparing your cluster for file services Description Describes the required hardware, network, and client system requirements. Provides an overview of the HSP hardware and step-by-step hardware assembly instructions. Provides an overview of the HSP software and step-by-step initialization and configuration instructions. Explains the post installation steps needed to get the Hyper Scale-Out Platform ready for client file services. Document conventions This document uses the following typographic conventions: Convention Bold Italic <Italic> in angle brackets monospace Description Indicates: Text in a window or dialog box, such as menus, menu options, buttons, and labels. For example: On the Add Pair dialog box, click OK. Text appearing on screen or entered by the user. For example: The -split option Indicates important new terms. Indicates a variable, which is a placeholder for site- or installationspecific details that you need to provide. For example: copy <source-file> <target-file> Indicates text that is displayed on the screen or text that you need to enter. For example: # pairdisplay -g oradb Also, the name of a directory, folder, or file. For example: The horcm.conf file vi Preface

7 Convention Description [ ] square brackets Indicates optional values. For example: [ a b ] indicates that you can choose a, b, or nothing. { } braces Indicates required or expected values. Example: { a b } indicates that you must choose either a or b. vertical bar Indicates that you have a choice between two or more options or arguments. Examples: [ a b ] indicates that you can choose a, b, or nothing. { a b } indicates that you must choose either a or b. This document uses the following icons to draw attention to information: Icon Meaning Description Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Important Calls attention to information that is essential to the completion of a task. cv Caution Electric shock hazard Warns that failure to take or avoid a specified action could result in adverse conditions or consequences (for example, loss of access to data). Warns of electric shock hazard. Failure to take appropriate precautions such as not opening or touching hazardous areas of the equipment could result in injury or death. ESD sensitive Sharp edges or corners Warns that the equipment is sensitive to electrostatic discharge (ESD) and could be damaged if you do not take appropriate precautions such as using a grounded wrist strap when touching or handling the equipment. Warns that the surface has sharp edges or corners. Avoid touching or wear gloves. Conventions for storage capacity Hyper Scale-Out Platform uses the International Electrotechnical Commission (IEC) binary definition for storage capacity units: Capacity unit Value 1 kibibyte (KiB) 1,024 (2 10 ) bytes 1 mebibyte (MiB) 1,024 2 (2 20 ) bytes 1 gibibyte (GiB) 1,024 3 (2 30 ) bytes 1 tebibyte (TiB) 1,024 4 (2 40 ) bytes 1 pebibyte (PiB) 1,024 5 (2 50 ) bytes 1 exbibyte (EiB) 1,024 6 (2 60 ) bytes Preface vii

8 Accessing product documentation Getting help Comments Product documentation is available on Hitachi Data Systems Support Connect: Check this site for the most current documentation, including important updates that may have been made after the release of the product. Hitachi Data Systems Support Connect is the destination for technical support of products and solutions sold by Hitachi Data Systems. To contact technical support, log on to Hitachi Data Systems Support Connect for contact information: Hitachi Data Systems Community is a global online community for HDS customers, partners, independent software vendors, employees, and prospects. It is the destination to get answers, discover insights, and make connections. Join the conversation today! Go to community.hds.com, register, and complete your profile. Please send your comments on this document to: hsp.documentation.comments@hds.com Include the document title, number, and revision, and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems. Thank you! viii Preface

9 1 Preparing for installation Carefully review the various prerequisite requirements detailed in this chapter prior to setting up and configuring your Hyper Scale-Out Platform (HSP): Network requirements External network Internal network Client system requirements GUI browser requirement Network requirements External network HSP has specific network requirements that need to be met prior to operation. Each node in a cluster requires access to two distinct standard GbE IP networks: an external facing network, as well as an internal facing network. File storage, data migration, and access communications required between the cluster and its clients are accomplished using an external, public network. Client machines access the storage in a cluster using the NFS file access protocol. External addresses are not hard-assigned to specific nodes in a cluster. We call these floating IP addresses because they can migrate or float from one node to another to provide continuous, uninterrupted file services when individual nodes go down and up. External IP addresses are automatically assigned to the nodes by the HSP software from a pool of external IP addresses that you specify from the address space of your company s network when you initially configure the cluster. The address pool needs at least as many IP addresses as there are nodes in the cluster twice the number of IP addresses per node per node is recommended. Preparing for installation 1

10 Internal network You will specify a pool of IP addresses when you initially configure your cluster using the Management Console. As your cluster grows, you can add more IP addresses to this pool using any one of the three management interfaces: the Management API, the Management Console GUI, or the command line interface (CLI). You will also assign one of these external IP address to serve as the cluster virtual IP address. This is the IP address through which administrators will manage the cluster and through which clients mount NFS shares in the most advantageous manner. We recommend that you add the cluster virtual IP address to your local DNS server. Communications between the nodes within the cluster are accomplished using an internal, private network. Internal IP addresses are automatically assigned by the HSP software when a node is discovered and added to a cluster. These internal IP addresses are not visible or manageable within the cluster. The internal network uses a supernetwork ( ) of the x.x and x.x ranges. No external systems or routers in this IP address range can access an HSP cluster. If you have conflicts with this reserved range in your network, contact Customer Support for assistance. Client system requirements Ensure that client systems have the software installed that can communicate with the Hyper Scale-Out Platform using the NFS v3 protocol. A client cannot access a file system in the cluster until you share that file system and create the appropriate access rules. See Hitachi Hyper Scale- Out Platform NFS Client Access Instructions for detailed information about client access. GUI browser requirement The 1.1 version of HSP Management Console has been thoroughly tested with version 36 of the Google Chrome web browser. Other browsers or versions may work, but have not been formally tested. In addition, to display correctly and completely, the browser window must be at least 1,021 pixels wide by 768 pixels tall. 2 Preparing for installation

11 2 HSP hardware assembly The Hyper Scale-Out Platform can ship as a preassembled or partially preassembled appliance in one or more racks or as individual unracked components. This chapter covers: HSP hardware overview About the racks About the nodes Assembling the hardware Overview of assembly steps Tools you need Step 1: Preparing the rack Step 2: Installing nodes Step 3: Cabling the nodes HSP hardware overview The HSP appliance hardware consists of: 5 to 100 nodes Ethernet switches for internal networking no fibre or SAN Additional infrastructure items including racks, cables, and PDUs Important: The Hyper Scale-Out Platform does not ship with an external network switch by default customers are expected to supply their own switch and cables. You can choose to remove one of the nodes in a fully populated rack to install your external switch. HSP hardware assembly 3

12 About the racks An HSP cluster is housed in one or more 42U racks. Inside each rack, four vertical rails two in front and two in back form a cage. The rack frame has Velcro straps attached to the rear rails. These straps are used to hold the Ethernet cable harnesses in place and to manage the power cords as needed. The rack has two grounding cables: One in the front. One end of the cable is attached to the hinged side of the door, and the other is attached to the top side rail of the rack frame. One end of the cable is attached to the hinged side of the door, and the other is attached to the top side rail of the rack frame. The rack comes with 1U solid blanking plates that cover any empty node slots. You will remove the blanking plates as you add additional nodes to the rack. This photograph shows the front of a six-node HSP cluster. 4 HSP hardware assembly

13 This photograph shows the back of a six-node HSP cluster. HSP hardware assembly 5

14 About the nodes Each 2U node is exactly the same and performs the same function within the cluster. There are no nodes that perform special storage or compute functions each node is capable of all operations. Each node comes preinstalled from the vendor with the HSP appliance operating system (which is a standard, unmodified Debian 7.3 wheezy Linux kernel) and the HSP appliance software you will not need to install any software. Each node has: Dual, 6 core Intel Xeon E Sandy Bridge-EP 2.0 GHz processors with 15 MB L3 cache 192 GB of Memory (12 X 16GB 1600 MHz DDR3) 12 x 4 TB 3.5 SAS hot-swappable data drives, configured as 12 single drive Raid 0 arrays 2 x 300 GB 2.5 hot-swappable boot drives, configured as two Raid 1 array Redundant power & cooling when properly installed and connected to different PDUs 6 HSP hardware assembly

15 Assembling the hardware You should unpack and assemble the HSP cluster is a clean, dust-free, well ventilated, and sufficiently air conditioned area. Additionally, you need to place the cluster in close proximity to two grounded power outlets. Overview of assembly steps Tools you need The first/initial rack comes with the minimum number of cluster nodes (five) preinstalled starting at the bottom of the rack and the two internal switches preinstalled at the top of the rack. The PDUs are also installed at the factory. Additional nodes come in boxes with the rack rails preinstalled and ready to install in the rack. Here is an overview of the remaining assembly steps: Step 1: Preparing the rack Step 2: Installing nodes Step 3: Cabling the nodes To assemble the hardware for an HSP cluster, you need the following tools: Phillips screwdriver Tip: The hardware assembly is easier using a magnetic screwdriver. Step 1: Preparing the rack The first/initial rack comes with the minimum number of cluster nodes (five) preinstalled starting at the bottom of the rack and the two internal switches preinstalled at the top of the rack. Additional nodes come in boxes with the rack rails preinstalled and ready to install in the rack. 1. Place each rack in its permanent location. 2. Remove the blanking plates at the front of the rack for any additional nodes you will be installing. HSP hardware assembly 7

16 Step 2: Installing nodes Add additional nodes to the rack using the instructions in this section. WARNING! Sharp edges or corners. Node and rail surfaces have sharp edges or corners. Avoid touching or wear gloves. WARNING! ESD sensitive. Equipment is sensitive to electrostatic discharge (ESD) and could be damaged if you do not take appropriate precautions such as using a grounded wrist strap when touching or handling the equipment. WARNING! Electric shock hazard. Failure to take appropriate precautions such as not opening or touching hazardous areas of the equipment and power receptacles could result in injury or death. Step 2a: Installing the outer rails on the rack 1. Press upward on the locking tab at the rear end of the middle rail. 2. Push the middle rail back into the outer rail. 3. Hang the hooks of the front of the outer rail onto the slots on the front of the rack. Secure the outer rails to the rack, as illustrated above. 4. Pull out the rear of the outer rail, adjusting the length until it fits within the posts of the rack. 8 HSP hardware assembly

17 5. Hang the hooks of the rear portion of the outer rail onto the slots on the rear of the rack. Secure the outer rails to the rack, as illustrated in diagram 3 above. 6. Repeat steps 1-5 for the outer rail on the other side. Step 2b: Installing the node on the rack Caution: You need two people or a lift to perform this task, as each node weighs 52 pounds. 1. Pull the middle rail out from the front of the outer rail and make sure that the ball-bearing shuttle is at the front locking position of the middle rail. 2. Align the chassis inner rails with the front of the middle rails. 3. Slide the inner rails on the chassis into the middle rails, keeping the pressure even on both sides, until the locking tab of the inner rail clicks into the front of the middle rail, locking the chassis into the fully extended position. 4. Depress the locking tabs of both sides at the same time and push the chassis all the way into the rear of the rack. 5. Use screws to secure the chassis handles to the front of the rack. HSP hardware assembly 9

18 Step 3: Cabling the nodes Important: Make sure you screwed the nodes into the racks before you start cabling, otherwise they will move as you are trying to seat the cables. Cabling is performed at the back of the rack using two 20-cable bundles. Cables are installed in the switches at the factory. Cable bundles are routed along the right side of the cabinet. Each individual cable is marked with a red or blue tab insert to identify which switch and which 40 GbE port they are to be plugged into: Red cables go into the top switch in rack unit 42 and are plugged into the left 40 GbE port on each node. Blue cables go into the bottom switch in rack unit 41 and are plugged into the right 40 GbE port on each node. Cable bundles contain cables in two lengths: 3-meter cable lengths to cable the switches to racked nodes 1 through 10 in the lower part of the rack 1-meter to cable the switches to racked nodes 11 through 20 in the upper part of the rack. Cables are labeled with the node numbers on both ends of the cables. 10 HSP hardware assembly

19 The HSP rack comes with all of the cables preinstalled in the switches. The following illustration shows how the labeled cables have been installed in the switch slots at the factory: Important: Be sure each Ethernet cable is properly seated at both ends. There is an audible click when the cables are properly seated. 1. Starting with the blue cable harness, locate the cable labeled with the node number of the first node you installed and plug that cable into the right 40 GbE slot in node. For example, if you were shipped a rack with 10 nodes installed and the first node you installed is number 11, locate the blue cable numbered Continuing from the next node closest to the bottom that you installed and moving up the rack, continue to plug each incrementally numbered cable into the next node in the rack you will plug in as many blue node cables as you installed nodes in the rack. 3. Moving to the red cable harness, locate the cable labeled with the node number of the first node you installed and plug the cable into the left 40 GbE slot in node. For example, if you were shipped a rack with 10 nodes installed and the first node you installed is number 11, locate the red cable numbered Continuing from the node closest to the bottom and moving up the rack, continue to plug each incrementally numbered cable into the next node in the rack you will plug in as many red node cables as you installed nodes in the rack. HSP hardware assembly 11

20 12 HSP hardware assembly

21 3 HSP software initialization and configuration The appliance operating system (OS), as well as the Hyper Scale-Out Platform (HSP) software are both factory installed on each HSP node. Once the nodes and switches are assembled in the rack and properly cabled, the appliance software initialization and configuration tasks are easy to perform. This chapter covers: HSP software overview Initializing the cluster Monitoring cluster formation Configuring your cluster Configuring SMTP for notifications HSP software overview The HSP appliance operating system (OS) is a standard, unmodified Debian 7.3 (wheezy) Linux kernel. HSP is a shared nothing, distributed architecture each node is independent and self-sufficient, so there is no single point of failure, contention, or bottleneck across the cluster. Each node maintains the cluster configuration and file system information (all of the metadata). The HSP software contains a number of third-party software components that are embedded in or distributed with the software. See the Third-Party Copyrights and Licenses document for details. HSP software initialization and configuration 13

22 Initializing the cluster Once the cluster is fully assembled as described in Chapter 2, HSP hardware assembly, you need to run a script that initializes the cluster. You will need to supply the virtual IP address you will use to access and manage the cluster and your site-specific network gateway. To initialize the cluster software 1. Power on all of the nodes in the cluster. The power button is located on the lower left side of the front of each node. Power Button Power LED The power LED should be illuminated when the system is node is powered on. 2. Attach a USB console monitor and keyboard to one of the node s the serial ports, located on the back of the node. 3. Press Enter and at the command prompt, log in as hds_init: pcsnode login: hds_init password: hds_init 4. Run the cluster_initialize script: pcsnode:~$ cluster_initialize 5. Enter the virtual IP address that you want to use to access and manage the cluster at the prompt. For example: Cluster Virtual IP Address (CIDR notation): /21 6. Enter your site-specific network gateway the prompt. For example: Gateway (IPv4): HSP software initialization and configuration

23 Cluster initialization begins when you see the following feedback from the cluster_initialize script: Waiting for cluster to initialize. Cluster Virtual IP Address: /21 Gateway: The cluster_initialize script deletes the hds_init account when complete this account is used only tor the initialization operation. 7. When directed to do so, exit out of the script to return to the command prompt where you can log in as an HSP administrator to use the command line interface (CLI). pcsnode:~$ exit Monitoring cluster formation Depending on how many nodes are in your cluster, the process of nodes joining the cluster can take time. You can monitor this process using the CLI from the console monitor and keyboard that you attached to one of the nodes to run the initialization script. To monitor cluster formation 1. At the command prompt, log in as admin with a password of admin: Node001:~$ admin admin@ 's password: admin 2. Run the hspadm node list command to see which nodes have joined the cluster, for example: Node001:~$ hspadm node list Name Run State Identify Maintenance Mode Version Rack Name Node001 UP No No Node002 UP No No Node003 UP No No Node004 UP No No Node005 UP No No If you were monitoring a five-node cluster, the example output shows five nodes with a Run State of UP the cluster is fully formed. 3. Continue monitoring the cluster by repeating the hspadm node list command until all nodes have joined and the cluster is fully formed. 4. Wait until the internal HSP file systems are created before using the cluster: reference, system_archive, and system_info. Run the hspadm file-system list command to monitor the file systems, for example: Node001:~$ hspadm file-system list HSP software initialization and configuration 15

24 Configuring your cluster We ask that you use the HSP Management Console to perform initial cluster configuration. While it is possible to configure your cluster using the management API or the command line interface (CLI), the Management Console presents all the configuration properties in an organized way so that nothing can be overlooked. This is extremely important if this is the first time you have configured an HSP cluster. We do not provide configuration guidance using the management API or the command line interface (CLI) interfaces. A companion document, the Configuration Checklist, can aid you in collecting and organizing the information required to configure the HSP cluster. To configure your cluster using the Management Console The initial configuration screen is displayed the first time you access the HSP Management Console. You must initialize the cluster before you can configure the cluster. See Initializing the cluster on page 14 for details. 1. Launch the Google Chrome Web browser. 2. Enter the virtual IP address of the cluster in the address bar of the browser. For example: 3. Log into the Management Console using the User Name of admin and a Password of admin. The HSP software automatically creates the administrative account called admin. You will be prompted for a new password for this account during initial configuration. The HSP software detects that no configuration has yet been performed for the cluster and opens the Initial Cluster Configuration page. 16 HSP software initialization and configuration

25 4. Accept the default values provided or specify values for the following cluster configuration properties: Configuration Property Name (required) ID Description By default, the name of the cluster is MyCluster. You can, however, modify the name of your cluster. There is only one virtual IP address associated with a cluster. If you modify the name of the cluster, add the new name and its corresponding virtual IP address to your local DNS server or to the /etc/hosts files on all of the hosts that need to access the cluster. Cluster names can be from 1 to 255 characters and can contain any UTF-8 characters. Cluster's universally unique identifier (UUID). The ID is assigned by the HSP software and cannot be changed. HSP software initialization and configuration 17

26 Configuration Property Virtual IP Address (required) Storage Space HWM (required) Storage Space LWM (required) File System Space HWM (required) File System Space LWM (required) Version Description Virtual IP address through which clients will access file systems and administrators access the management interfaces within a cluster. There is only one virtual IP address associated with a cluster. Note: The IP Address displayed in this field was specified by the person who set up your hardware. We recommend consulting with them before making arbitrary changes to this address. Valid IP address specified in IPv4 CIDR notation, for example: /21. Storage space usage high water mark percentage defined for the cluster. When the remaining cluster storage space usage reaches the high water mark percentage, an alert is raised until the storage space usage falls below the low water mark percentage. Specify a value from 1 to 98 that is greater than the Storage Space LWM. By default, Storage Space HWM is set to 80. Storage space usage low water mark percentage defined for the cluster. Existing storage space usage alerts are automatically cleared once the low water mark percentage is achieved. The low water mark is typically 10 to 20 percent less than the high water mark. Specify a value from 1 to 98. By default, Storage Space LWM is set to 70. High water mark usage percentage set by default for any new file system added to a cluster. You can override this usage percentage at the file system level. When the remaining allocated file system space usage reaches the high water mark percentage, an alert is raised until the file system space usage falls below the low water mark percentage. Specify a value from 1 to 100 that is greater than the File System Space LWM. By default, File System Space HWM is set to 90. Low water mark usage percentage set by default for any new file system added to a cluster. You can override this usage percentage at the file system level. Existing file system space usage alerts are automatically cleared once the low water mark percentage is achieved. The low water mark is typically 10 to 20 percent less than the high water mark. Specify a value from 1 to 100. By default, File System Space LWM is set to 85. Version of HSP software running on the cluster. The first three period-separated numbers (1.1.0) are the version number, and the digits after the last period following the version number are the build number. You cannot change Version. 18 HSP software initialization and configuration

27 Configuration Property Hide Shares Gateway (required) Domain Name (required) DNS Server IP Address (required) NTP Server or IP Address (required) Description Checkbox that specifies whether or not share visibility is restricted only to clients that have permission to access the share. By default, the checkbox is not marked and clients can see all file system shares. You can restrict share visibility in multi-tenant environments by marking the checkbox. Clients will then only see the shares for which they have access permissions. IP address of your network gateway. This is used by HSP to access external services (for example, NTP for time synchronization and SMTP for notification delivery). Valid IP address specified in IPv4 notation, for example: Your company s valid domain name, for example: YourCompanyName.com IP address of your DNS server. Valid IP address specified in IPv4 notation, for example: IP address or fully qualified host name of your NTP server. Network Time Protocol (NTP) is used to synchronization time on the nodes within a cluster. Debian has an external NTP server that is configured at installation time by default. If specified as an IP address, use IPv4 notation, for example: HSP software initialization and configuration 19

28 Configuration Property External Floating IP Address Pool Description The pool of IP addresses that are assigned to the nodes by the HSP software. We call these floating IP addresses because they can migrate or float from one node to another to provide continuous service when individual nodes go down and up. As such, you do not explicitly assign an external address to each node. Notes: You should maintain at least as many IP addresses as there are nodes in the cluster twice the number of IP addresses per node is recommended. Also, you cannot assign IP addresses to an HSP cluster that are already in use within your network. IP addresses are specified in IPv4 CIDR notation. You can specify the IP addresses as: A range of IP addresses, for example: / /21 A range of IP addresses using a special notation for contiguous addresses, for example: /21+10 which is the same as specifying the range above. A comma-separated list of IP addresses, for example: /21, /21, /21 The HSP software automatically generates a name for each IP address, which is a comma-separated version of the IP address (for example /21 becomes ). Optionally, you can also specify a prefix that will be added to the name. For example, if you specify a prefix of floating, then /21 becomes floating HSP software initialization and configuration

29 Configuration Property Virtual Machine IP Address Pool Description Tags Password for admin User (required) Confirm Password for admin User (required) Description The pool of IP addresses that are assigned by the HSP software to VM instances when a VM template is deployed. Notes: You need at least as many IP addresses as the number of instances you want to deploy. Also, you cannot assign IP addresses to an HSP cluster that are already in use within your network. IP addresses are specified in IPv4 CIDR notation. You can specify IP addresses as: A range of IP addresses, for example: / /21 A range of IP addresses using a special notation for contiguous addresses, for example: /21+10 which is the same as specifying the range above. A comma-separated list of IP addresses, for example: /21, /21, /21 The HSP software automatically generates a name for each IP address, which is a comma-separated version of the IP address (for example /21 becomes ). Optionally, you can also specify a prefix that will be added to the name. For example, if you specify a prefix of hadoop, then /21 becomes hadoop Description of the cluster. Free-flowing text, allowing up to 255 characters. User-defined tags that can be used to organize and/or filter the response results. Free-flowing text, allowing up to 255 characters. The HSP software automatically creates an administrative account called admin with a password of admin. You are required to provide a new password (other than admin) for this account during configuration. The password must be a minimum of 5 and a maximum of 255 characters. You cannot specify the initial default password of admin. Must match what you entered in Password for admin User. Text input fields, drop-downs, and checkboxes are provided for those attribute fields that you can add and/or edit in the Initial Cluster Configuration page. You cannot blank out any of the required fields that are marked with a red asterisk (*). HSP software initialization and configuration 21

30 5. Optionally, you can configure SMTP now, or you can finish cluster configuration and configure SMTP at a later time. See Configuring SMTP for notifications on page 22 for details. 6. Review the values you specified for cluster properties. 7. Click Save to configure the cluster, or Cancel to exit the Initial Cluster Configuration page without making changes. 8. Scroll back to the top of the Initial Configuration page to monitor the status of the configuration submission status messages are displayed just above the page title bar. After you have successfully configured the cluster and changed the admin user account s password, you will need to log into the Management Console using the updated credentials. Configuring SMTP for notifications A valid SMTP configuration is required for an HSP user to receive notifications of alert conditions. The HSP software comes with a predefined, but disabled SMTP configuration called SMTPConfig. You need to edit this configuration with your site-specific properties and enable SMTPConfig before alert condition message notification will work properly. Note that you cannot delete this SMTP configuration or add another SMTP configuration you can only edit the existing configuration. You will also need to set up user subscriptions to receive notifications for alert conditions. See the user account management sections of the API, CLI, and Management Console documentation for details. To configure SMTP 1. Accept the default values provided or specify values for the following SMTP configuration properties: Property Name (required) Enabled Description By default, the name of SMTP configuration is SMTPConfig. You can, however, modify the name of your SMTP configuration. SMTP configuration names can be from 1 to 255 characters and can contain any UTF-8 characters. Checkbox that specifies whether or not the SMTP configuration is enabled. By default, the initial default SMTP configuration is disabled because the SMTP configuration requires editing for your environment. 22 HSP software initialization and configuration

31 Property SMTP Server (required) SMTP Server Port (required) Display Name Address (required) Security Enabled User Name Password Description Tags Description IP address or fully qualified host name of the SMTP server, for example: smtp.gmail.com If specified as an IP address, use IPv4 notation, for example: The outgoing SMTP server port. The default port for a non-ssl configuration is 25. The default port for an SSL configuration is 465. The from display name that will be associated with sent alert messages, for example: bsmith Required if the SMTP configuration is enabled. From address that will be associated with sent alert messages. For example, you could specify the name of the cluster: WestCoastCluster@hds.com Required if the SMTP configuration is enabled. Checkbox that specifies if the client should use Secure Socket Layer (SSL)-based security when sending . If you use SSL, you are required to provide a user name and password that will be passed to the service provider for authentication. The user ID that is passed to the service provider for authentication. Required if Security Enabled is marked. User password that is passed to the service provider for authentication. Required if Security Enabled is marked. Description of the SMTP configuration. Free-flowing text, allowing up to 255 characters. User-defined tags that can be used to organize and/or filter the response results. Free-flowing text, allowing up to 255 characters. Text input fields, drop-downs, and checkboxes are provided for those attribute fields that you can add and/or edit in the Initial Cluster Configuration page. You cannot blank out any of the required fields that are marked with a red asterisk (*). 2. Click Save to configure the cluster, or Cancel to exit the Initial Cluster Configuration page without making changes. 3. Scroll back to the top of the Initial Cluster Configuration page to monitor the status of the configuration submission status messages are displayed just above the page title bar. 4. You will need to log back into the Management Console using the updated credentials you specified for the admin user account. HSP software initialization and configuration 23

32 24 HSP software initialization and configuration

33 4 Preparing your cluster for file services After the hardware is installed and the cluster has been initialized and configured, there are some management tasks you need to perform to prepare the cluster for file services. This chapter covers: Ways to manage your cluster Final preparation for client access Documentation resources Ways to manage your cluster HSP provides three interfaces that you can use to manage an HSP cluster: Management Console GUI Command line interface (CLI) Management API Each of these management interfaces are full featured, so that you can choose the interface or combination of interfaces that best suits your needs and preference. Cluster resource and property names are consistent between the interfaces, so you can easily transfer knowledge of one interface to another. The HSP software automatically creates an administrative account called admin. You were prompted for a new password for this account during initial configuration. Use these credentials to log into the Management Console, ssh into the CLI, or authenticate API requests. Preparing your cluster for file services 25

34 Final preparation for client access Use one of the available management interfaces to perform the tasks to get HSP ready for file services. Three tightly coupled resources must be added to provide client access to the configured cluster: File systems the namespaces in which files are created and accessed Shares resources that explicitly share out individual file systems Access rules resources that grant permissions to the shares By default, the HSP software automatically creates the required associated share and access rule when you create a file system. Note: There is a cluster-level property you can change if you do not want this automatic creation behavior and prefer to manually create the required share and access rule. (See the documentation for the management interface you are using for details.) The documentation for the management interface you choose will guide you through the management tasks in more detail: Comprehensive, context sensitive online help is available for administrators managing HSP using the Management Console. You can also generate a viewable or printable version of the online help by clicking the PDF icon, located in the upper right corner of the help. A comprehensive man page is available for administrators managing HSP using the CLI. Type help at the hspadm command prompt. You can also view a searchable PDF version of the hspadm man page, available in the reference file system on any installed HSP node. A comprehensive document with detailed examples is available for administrators managing HSP using the API. You can find the Hitachi Hyper Scale-Out Platform Management API document in the reference file system on any installed HSP node. In addition to the written examples embedded in this document, a complete collection of the Python coding examples for the HSP management API are provided on any installed node and accessible from the reference file system share in the following location: /examples/api This section guides you through basic steps for creating file systems using the Management Console and the CLI. See the Hitachi Hyper Scale-Out Platform Management API document for creating file systems using the API. 26 Preparing your cluster for file services

35 Adding file systems using the Management Console To add a file system using the Management Console 1. Go to File Systems. 2. On the File Systems page, click Add File System. 3. In the Add File System dialog, enter the properties for the file system you want to add. The online help provides comprehensive descriptions for all of the file system properties. 4. Click OK. The added file system is displayed in the File Systems page and the first colored box to the right of the file system name is green if you enabled the file system when you added it. If you allowed the HSP software to automatically add the associated required share and access rule, all three colored boxes will be green. Adding file systems using the command line interface To add a file system using the CLI hspadm file-system add --name <file-system-name> --quota <quota-and-unit> [--enabled {Y N}] [--data-protection {raid1_3instance}] [--space-hwm <file-system-space-high-water-mark-%>] [--space-lwm <file-system-space-low-water-mark-%>] [--record-access-time {Y N}] [--description <description>] [--tags> <user-defined-tag>] For example, to add a file system: $ hspadm file-system add --name marketing --quota 100TiB Preparing your cluster for file services 27

36 Documentation resources The following documentation is also available for Hitachi Hyper Scale-Out Platform: Release Notes contains a high-level overview of general HSP product and release-specific features. This document also summarizes product issues and behaviorsthat you should be aware of before using the HSP software. Introducing Hitachi Hyper Scale-Out Platform provides an overview of the HSP components, architecture, and product features. Configuration Checklist is a checklist that assists in collecting and organizing the information required to configure the HSP cluster. Using the Management API provides detailed information for administrators wanting to perform API-based cluster management operations and for developers wanting to integrate HSP administrative and management operations with existing infrastructure management systems and applications using REST. Client Access Instructions provides instructions to client users for accessing cluster shares. This document also provides a form that administrators can fill out and give to their users to provide detailed, cloud-specific client access information. Hyper Scale-Out Platform Maintaining and Troubleshooting provides detailed information for adding and replacing certain hardware components, troubleshooting HSP issues, and collecting diagnostic information. Third-Party Copyrights and Licenses provides the third-party copyrights and licenses for the components that are distributed with the HSP software. For your convenience, these documents are located in the reference file system located on any installed node. Online help details all of the tasks necessary for HSP administration and management using the HSP Management Console graphical user interface: To access contextual page-level online help, click the icon, located at the top right of the individual Management Console pages. You can then navigate through the entire help system using the Contents, Index, and Search navigation control tabs. To create and print a PDF version of the Management Console online help, click the icon, located at the top right of the help system. Comprehensive man-style documentation is available for hspadm, the command line interface for HSP management. SSH to the cluster virtual IP address (or one of the nodes), and type man or help at the shell command prompt to access this documentation. In addition, a PDF version of the hspadm man page is located in the reference file system located on any installed node. 28 Preparing your cluster for file services

37

38 Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California U.S.A. Regional Contact Information Americas Europe, Middle East, and Africa +44 (0) Asia Pacific MK-94HSP003-01