introducing hitachi scale-out platform · 3 introducing hyper scale-out platform the hyper...

MK-94HSP001-01

Introducing Hyper Scale-Out Platform

1.1

ii


© 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 https://portal.hds.com.

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.

https://portal.hds.com

Contents

What is Hyper Scale-Out Platform (HSP)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Hardware components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Internal private network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3External public network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

How the components interact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Software operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5File storage and access operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Data management and migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Data access during failure and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . 5File-level management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Target file update workloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

High availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Policy-based data protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Node access failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Fault tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Basic node health monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Rolling upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Hi-Track support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Cluster and virtual machine management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Command line interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Management API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Advantages of the architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Contents iii

Hyper Scale-Out Platform

iv

Hyper Scale-Out Platform

What is Hyper Scale-Out Platform (HSP)?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.

The convergence of storage and compute on the HSP platform:• Eliminates the risks and potential bottlenecks associated with moving

data between storage and compute platforms. Data and applications work together on a converged platform.

• Eliminates the need for separate virtualization, server and storage infrastructure, reducing both operating and capital costs.

• Features massive data ingest at high speed and at scale. HSP is optimized for data management frameworks, such as Hadoop, making it ideal for analytics applications.

• Provides OpenStack compatibility, making it ideal for enterprises deploying private clouds or managed service providers who want to manage heterogeneous virtualization environments as one with consistent, simplified operations, data access from the cloud, robust content delivery, fast client onboarding, and relief from expensive virtualization licensing fees.

1


Hardware componentsHyper Scale-Out Platform consists of multiple cooperating servers called Nodes that are organized into units called Clusters. Cluster communications are accomplished using two separate and distinct standard IP networks, which are described in “Networking” on page 3.

ClustersClusters are organizational units that allow for connectivity, data segmentation, and storage management.

HSP clusters are highly scalable, consisting of: • Conventional 2U nodes with internal disks• 5 to 100 nodes• 20 nodes per rack• 12 disks per node• 2 X 40 GbE internal networks• 10 GbE external network interface• Color-coded internal network cables• Cable harnesses for cable dressing management and ease of

installation

NodesNodes are the physical machines that provide collective file storage for the cluster. Nodes and their underlying disks are automatically discovered when they are added to the cluster. The operating system and HSP software are preinstalled and preconfigured as much as possible—to form the cluster, you need only supply a few site-specific network details and a single virtual IP address you will use to manage the cluster.

The aggregate storage from multiple homogenous nodes appears as 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 NFSv3 protocol.

The storage pool is centrally managed at the cluster level using your choice of one of the three management interfaces described in “Cluster and virtual machine management” on page 8. Nodes do not need to be individually configured for file sharing or access permissions.

Automated storage integration and migration features make the addition of new storage devices trivial, transparent, and non-disruptive. It is similarly easy to transparently and non-disruptively decommission old storage devices and recreate their contents on other storage devices.

2


The Hyper Scale-Out Platform 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).

NetworkingTwo separate and distinct standard IP networks are used for cluster communications. Separating the internal cluster network communications from the external network communications provides significant performance advantages.

Internal private network

Communications between the nodes within the cluster are accomplished using an internal, private network. Internal IP addresses are automatically assigned by the software when a node is discovered and added to a cluster. These internal IP addresses are not visible or manageable within the cluster.

External public 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. You can add more IP addresses to this pool as your cluster grows.

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.

3


How the components interactThe following illustrates how the components of an HSP cluster interact:•

•

4


Software operationsThis section provides an understanding of Hyper Scale-Out Platform’s key software operations.

File storage and access operationsA file system is a namespace that provides access to files that reside in a pool of aggregate storage.

The HSP architecture is based on well-known and understood algorithms for placing, moving, and locating data across a very large number of storage devices. Data is replicated and balanced across all available storage disks within a cluster in accordance with administrator-defined data protection policies that dictate how many instances of each file are maintained and stored within a cluster.

There is an internal mapping between the file names within a file system and their physical disk location in a cluster. Any one of the nodes within the cluster is capable of servicing a request for any file that is within a file system that has been shared.

Data management and migrationFile copy and migration operations are constantly taking place within an HSP cluster:• When a file is updated, the changes must be propagated from the node

where the changes were made to all of the other nodes that store that file.

• When a file is deleted, it is deleted from each node that stored another instance of that file.

• When new nodes or disks are added to the cluster, files residing on heavily loaded nodes or disks are moved to the new ones.

• When a node or disk needs maintenance or replacement, the files on that node must be recreated and copied to other nodes and disks.

Data access during failure and recoveryRead or write requests for files that are already open are handled directly by the nodes. Nodes regularly obtain leases for any files they are serving for their clients. If node services are down for a few seconds, there may be no interruption in read or write requests for files that are already open. Once a lease has expired, client requests are blocked until node services are restored, at which point all pending requests should complete normally.

The behavior seen by the client when a node fails: • For file reads, the observed behavior depends on the options the client

used to mount the file system, and follows NFS behavior for hard, soft, or intr.

• For file writes, clients will get a write error, but can recover from the error by reopening and rewriting the file.

5


File-level managementMany products make placement, file copy, and migration decisions on a block-by-block basis. Products that perform block-level management have some significant shortcomings in that they:• Cannot distinguish between blocks in a directory, a database, a picture,

or an editor recovery buffer, and as such, impose the same cost/performance/reliability trade-offs on these very different types of data

• Cannot tell which files are being updated and which files are being used how often, by which clients, and therefore cannot adjust placement to minimize network traffic and overhead

By managing files rather than blocks, an HSP cluster is able to:• Distinguish between files within different file systems, apply the

appropriate file data protection policies, and maintain the number of instances specified by each policy

• Ensure that files are copied in a consistent manner• Make intelligent file placement decisions

Target file update workloadsThere are a few general types of file updates:• File replacements—for example, web pages that are periodically

updated with new content or text files that are edited and written back• File appends—for example, log files to which new entries are

continuously appended• Record-type file updates—for example, database files to which multiple

writers continuously perform simultaneous updates to different parts of the file, but are serialized for access to a single record

• Single-writer updates—for example, files that are read by many clients, but whose contents are regularly updated by a single writer

• Multi-writer updates—for example, a database where multiple writers continuously perform updates to different parts of the file, and the updates are serialized when they are made to a particular file

The HSP software is designed and optimized for file replacement and append-type updates, which are typical of most emerging digital content depots or corporate archives. The software also correctly handles single-writer updates, ensuring that readers see the newest content.

The HSP software provides support for atomic updates through file versioning. Readers never see a new or updated file until any changes have been committed, and then they will see all of the new content. Any given read operation is guaranteed to be from one version of the file.

The HSP software is not designed to support database-type file updates from multiple concurrent writers, but does support smaller, single-access databases and NoSQL workloads.

6


High availabilityThe Hyper Scale-Out Platform software provides multiple features that ensure continuous operation of the cluster.

Policy-based data protectionAdding, upgrading, or removing nodes and their underlying disks are online operations and require little to no client services outage. When a node or disk is down or deleted, HSP detects that the number of file instances maintained in the cluster is now insufficient and not in compliance with what has been specified by the administrator for the file system data protection policy. The software automatically performs the file copy and migration activities needed to bring the file protection in compliance with the policy set.

Node access failoverHSP continuously monitors all of the active nodes. If a node goes down, its external floating IP address is reassigned to another node, which takes over for the failed node. If and when the failed node comes back up and rejoins the cluster (for example, after it is repaired and/or rebooted), the node is reassigned its original external floating IP address.

Fault toleranceHSP is fully fault tolerant at any hardware failure level:• Lose a disk, recreate and rebuild data on other disks• Lose a node, recreate and rebuild data on other nodes• Lose a rack, recreate and redistribute data to other racks

Basic node health monitoringAll HSP services that run on the nodes are continuously monitored. These services are automatically restarted if the software detects they have failed, so there is no need for an administrator to monitor or be concerned with internal HSP services.

Rolling upgradesTo ensure there is no service interruption or down time, HSP supports rolling software upgrades across the cluster.

Hi-Track supportHSP can integrate with the Hi-Track Remote Monitoring system to provide additional proactive monitoring and tracking of your cluster.

7


Cluster and virtual machine managementCluster management is centralized, eliminating the need to manage each node independently. Centralized management also extends to managing file services, as well as managing the virtualization environment for your applications.

Each entity that you can manage independently in the HSP is referred to as a resource. The cluster API allows configuration and management access to the following HSP resources:

HSP resource Description

Clusters Clusters are the collection of nodes that are interconnected on two networks (one external and one internal) and have one or more underlying file systems that provide client file access through the NFS protocol.

Nodes Nodes are the physical machines that provide collective storage for the cluster. Nodes are centrally managed and do not need to be individually configured for file sharing or access. Nodes:• Manage the underlying disks • Store files, provide access to those files using remote file

access protocols, and balance client connections and storage capacity within a cluster

• Maintain the configuration and file system information for the cluster

• Control the local redundancy and migration of files within the cluster to maintain the data protection policy you set for your files

Disks Disks are the physical storage devices in a node.

Racks In the context of the HSP software, racks are a “virtual” organizational resource that you can define and organize in a way that makes sense for your installation. The configuration and management of this virtual resource is optional, but the software does exercise internal rack-aware file placement and rebalancing enhancements if you define racks and distribute the nodes across the racks.

IP Addresses A pool of external IP addresses are allocated to the cluster when you initially configured the cluster or can be added later to accommodate more storage.

IP addresses can move or float from the assigned node to a different node if the assigned node goes down or is taken off line for any reason, so there is no loss of service to the clients. Clients can access the cluster using any one of the external IP addresses associated with any one of the nodes.

File systems File systems are the namespaces within the HSP in which files are created and accessed. Each file exists in only one file system, but the files themselves can be stored on multiple disks and spread across multiple nodes. A file system is not limited by the underlying storage available on a single machine.

Tenants Administrative entity that owns and manages a file system and associated resources.

8


HSP provides three interfaces you can use to manage a cluster:• Management Console• 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 property names are consistent between the interfaces, so you can easily transfer knowledge of one management interface to another. Great effort has also been made to provide “intelligent” property configuration defaults whenever possible.

File system shares Files systems are shared out using the NFSv3 protocol. Clients can only access files in a file system that is shared out. You can also define and manage host-level access control rules for NFS shares.

Users In addition to the default HSP user account called admin, you can add and maintain other administrative user accounts.

VM Templates Templates let you install and launch virtual machines on multiple HSP nodes so that you can run analytic applications.

VM Instances Instances are the running instances of virtual machines within the cluster.

HSP resource Description

9


Management ConsoleThe HSP Management Console is a web-based graphical user interface. Minimally, you will use the Management Console to perform initial cluster configuration. Launch the Management Console by entering the virtual IP address of the cluster in the address bar of a Web browser. For example:

https://172.20.135.20

The Initial Configuration wizard is automatically launched if the cluster has not yet been configured. •

•

If the cluster has already been configured, you can log in using the credentials specified in the initial configuration.

The Management Console provides a consistent list/details view of all cluster resources, including:

10


• Top navigation menu to access cluster dashboard, jobs, and monitoring, as well as settings, and online help

• Point and click resource selection• Right-click context menus from which to perform resource-specific

management tasks•

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.

11


Command line interface (CLI)HSP administrators ssh into virtual IP address of the cluster to run the hspadm command line interface in a restricted shell.

Management tasks are performed using the CLI in a straightforward resource verb --property value manner and displays the output in a user friendly, formatted output. for example: •

The CLI also supports extended, detailed resource output similar to what is available from the REST API, using the --json argument. For example:•

•

12


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.

13


Management APIThe HSP management API is a Representational State Transfer Protocol (REST) API that you can use to manage HSP cluster resources and to facilitate application development and integration with existing infrastructure applications.

HTTP defines a set of methods that define the actions that can be performed on a resource. The HSP management API supports the following HTTP methods:

When you add or modify (POST) a resource through the HSP management API, you will use JSON to specify the resource properties. When you retrieve (GET) information about a resource, the response will also be returned as JSON. The HSP management API does not currently support XML.

All responses returned through the management API are UTF-8 encoded. All request bodies you create for input to the API must also be UTF-8 encoded.

In a JSON request or response body:• Properties are specified by name/value pairs that describe or define the

resource. For the POST (add/edit) method, these name/value pairs are included in the body of the message. For example, the URL specification to create a file system called sales:

POST https://172.20.135.20/hspapi/file-systems/

with body properties of:

Method Description

GET Retrieves information about an individual resource or retrieves a list of resources of a given type.

GET is a synchronous operation. a

a. GET is a synchronous operation. This means that each request completes andreturns a response code that conveys the result of the operation.

POST Adds or edits the properties of a resource. POST is also used to execute an action on a particular resource.

When adding a resource, you need to provide values for any required properties of a resource that do not have default values. To override a default value, include the property and provide an override value for that property in the request body.

When editing the properties of a resource, supply values only for the properties that you want to change. Properties that are not specified in the request body remain unchanged.

POST is an asynchronous operation. b

b. POST and DELETE are asynchronous operations. When a request is submittedfor one of these methods.

DELETE Deletes a resource.

DELETE is an asynchronous operation.

14


"name": "sales","enabled": true,"data-protection": "raid1_3instance","space-hwm": 90,"space-lwm": 85,"quota": 1099511627776,"record-access-time": true,"description": "Sales organization data","tags": "2013"

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

15


Advantages of the architectureHyper Scale-Out Platform has a deceptively simple sounding architecture, but achieves many goals that benefit the HSP user:• Extraordinary scalability in terms of both machine bandwidth and

storage capacity—if you need more storage, you simply add more nodes or more disks to an existing node that you manage as a single resource pool.

• Eliminates typical bandwidth and network bottlenecks—the separation of data network traffic from metadata network traffic and the autonomous nature of the nodes allow them to service client requests independently.

• Automation of common, yet often difficult, storage management operations—storage is automatically discovered and necessary file copy, migration, and load-balancing operations are achieved without administrative intervention.

• Easy to install, configure, and manage your HSP cluster. Adding and expanding storage and the underlying file systems is easy and requires no system down time. All of the storage in a cluster is managed through your choice or combination of the management interfaces described in “Cluster and virtual machine management” on page 8.

• Highly available data and storage management services—hardware failures are transparent to clients and policy-based, automated file copy and instance creation ensures data availability.

• Bringing applications to the data in a virtualized environment offers considerable performance advantages, management simplicity, as well as cost savings.

16


MK-94HSP001-01

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0)1753 [email protected]

Asia Pacific+852 3189 [email protected]

introducing hitachi scale-out platform · 3 introducing hyper scale-out platform the hyper...

Documents