Hitachi Storage Provider for VMware vCenter Deployment ... · Hi tachi Storage Provider for VMware...

Hitachi NAS Platform

Hitachi Storage Provider for VMwarevCenter Deployment Guide for File

StorageRelease 3.0

MK-92HNAS054-00

© 2011-2015 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by anymeans, electronic or mechanical, including photocopying and recording, or stored in adatabase or retrieval system for any purpose without the express written permission ofHitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time withoutnotice and assumes no responsibility for its use. This document contains the mostcurrent information available at the time of publication. When new or revised informationbecomes available, this entire document will be updated and distributed to all registeredusers.

Some of the features described in this document might not be currently available. Referto the most recent product announcement for information about feature and productavailability, or contact Hitachi Data Systems Corporation at https://portal.hds.com.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms andconditions of the applicable Hitachi Data Systems Corporation agreements. The use ofHitachi, Ltd., products is governed by the terms of your agreements with Hitachi DataSystems Corporation.

2Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

https://portal.hds.com

Hitachi Data Systems products and services can be ordered only under the terms andconditions of Hitachi Data Systems’ applicable agreements. The use of Hitachi DataSystems products is governed by the terms of your agreements with Hitachi DataSystems.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and othercountries. Hitachi Data Systems is a registered trademark and service mark ofHitachi, Ltd., in the United States and other countries.

Archivas, Dynamic Provisioning, Essential NAS Platform, HiCommand, Hi-Track,ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy,Universal Star Network, and Universal Storage Platform are registered trademarks ofHitachi Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS8000, Enterprise Storage Server, ESCON, FICON,FlashCopy, IBM, Lotus, OS/390, RS6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/OS, z9, zSeries, z/VM, z/VSE are registered trademarks and DS6000, MVS,and z10 are trademarks of International Business Machines Corporation.

All other trademarks, service marks, and company names in this document orwebsite are properties of their respective owners.

Microsoft product screen shots are reprinted with permission from MicrosoftCorporation.

This product includes software developed by the OpenSSL Project for use in theOpenSSL Toolkit (http://www.openssl.org/). Some parts of ADC use open source codefrom Network Appliance, Inc. and Traakan, Inc.

Part of the software embedded in this product is gSOAP software. Portions created bygSOAP are copyright 2001-2009 Robert A. Van Engelen, Genivia Inc. All rightsreserved. The software in this product was in part provided by Genivia Inc. and anyexpress or implied warranties, including, but not limited to, the implied warranties ofmerchantability and fitness for a particular purpose are disclaimed. In no event shallthe author be liable for any direct, indirect, incidental, special, exemplary, orconsequential damages (including, but not limited to, procurement of substitutegoods or services; loss of use, data, or profits; or business interruption) howevercaused and on any theory of liability, whether in contract, strict liability, or tort(including negligence or otherwise) arising in any way out of the use of this software,even if advised of the possibility of such damage.

The product described in this guide may be protected by one or more U.S. patents,foreign patents, or pending applications.

Notice of Export Controls

Export of technical data contained in this document may require an export licensefrom the United States government and/or the government of Japan. Contact theHitachi Data Systems Legal Department for any export compliance questions.


Contents

1 About this document..............................................................................6Audience................................................................................................................. 7Related Hitachi NAS documentation ..........................................................................7Related VMware documentation ............................................................................... 9

2 About Hitachi Storage Provider for VMware vCenter............................... 10Storage Provider deployment architecture................................................................11VMware terms and concepts................................................................................... 11Understanding the Storage Provider Web user interface............................................ 13

3 System requirements........................................................................... 16Software................................................................................................................17Hardware.............................................................................................................. 18Protocols............................................................................................................... 18Licensing............................................................................................................... 18

4 Installing Storage Provider....................................................................20Install high-level process........................................................................................ 21Where to find the OVF............................................................................................21Where to deploy the OVF........................................................................................21Installing vSphere Client Integration Plug-in.............................................................21Deploying the OVF................................................................................................. 23

5 Validating installation........................................................................... 32Powering on the VM............................................................................................... 33Logging in to the Storage Provider Web UI...............................................................33

6 Configuring Storage Provider................................................................ 34Managing maintenance mode..................................................................................35


Setting maintenance mode................................................................................35Exiting maintenance mode................................................................................ 35

Managing hardware................................................................................................36Viewing managed hardware.............................................................................. 36Adding new hardware....................................................................................... 37Deleting managed hardware..............................................................................38

Managing storage containers.................................................................................. 39Viewing storage containers................................................................................40Adding storage containers................................................................................. 40Deleting storage containers............................................................................... 41

Registering the Storage Provider with vCenter Server................................................42

7 Open source licensing.......................................................................... 44Apache Axis...........................................................................................................45Apache Tomcat...................................................................................................... 45Debian Linux..........................................................................................................45OpenJDK7............................................................................................................. 46OpenSSL............................................................................................................... 46PostgreSQL............................................................................................................49Google Gson library................................................................................................50Apache 2.0 license ................................................................................................ 50GNU General Public License (GPL) Version 2.0..........................................................54


1About this document

This document describes the Hitachi Storage Provider for VMware® vCenter™2015. This version of the vCenter product features the vSphere APIs forStorage Awareness (VASA) 2.0 and includes the VMware VVols (virtualvolumes) feature. This Storage Provider integrates the Hitachi NAS Platformsand Hitachi file storage systems with the vCenter and the VMware vSphere®environment.

□ Audience

□ Related Hitachi NAS documentation

□ Related VMware documentation

6 About this documentHitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

AudienceThis guide was written for expert administrators who want to install, deploy,and configure the Hitachi Storage Provider for VMware vCenter in a VMwareenvironment.

These administrators want to use Storage Provider with:• Hitachi NAS Platforms (HNAS servers)• Hitachi file storage systems• VMware vCenter 6 (with support for VASA 2.0 and virtual volumes (VVols))• VMware vSphere 6

These administrators must be highly proficient with:• Install, configuration, and management of HNAS platform servers.• Administration of Hitachi file storage systems.• Install, configuration, and management of vCenter and vSphere.

Related Hitachi NAS documentationRelease Notes provide the most up-to-date information about the system,including new feature summaries, upgrade instructions, and fixed and knowndefects.

Administration Guides

• System Access Guide —In PDF format, this guide explains how to log in tothe system, provides information about accessing the NAS server/clusterCLI and the SMU CLI, and provides information about the documentation,help, and search capabilities available in the system.

• Server and Cluster Administration Guide —In PDF format, this guideprovides information about administering servers, clusters, and serverfarms. Includes information about licensing, name spaces, upgradingfirmware, monitoring servers and clusters, the backing up and restoringconfigurations.

• Storage System User Administration Guide —In PDF format, this guideexplains user management, including the different types of systemadministrator, their roles, and how to create and manage these users.

• Network Administration Guide —In PDF format, this guide providesinformation about the server's network usage, and explains how toconfigure network interfaces, IP addressing, name and directory services.

• File Services Administration Guide —In PDF format, this guide explainsabout file system formats, and provides information about creating andmanaging file systems, and enabling and configuring file services (fileservice protocols).

About this document 7Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

• Storage Subsystem Administration Guide —In PDF format, this guideprovides information about managing the supported storage subsystems(RAID arrays) attached to the server/cluster. Includes information abouttiered storage, storage pools, system drives (SDs), SD groups, and otherstorage device related configuration and management features andfunctions.

• Command Line Reference Opens in a browser, and describes thecommands used to administer the system.

Note: For a complete list of Hitachi NAS open source software copyrights andlicenses, see the System Access Guide.

Hardware References• Series 4000 Hardware Reference —Provides an overview of the server

hardware, describes how to resolve any problems, and how to replacepotentially faulty components.

Best Practices• Hitachi NAS Platform Best Practices Guide for NFS with VMware vSphere

(MK-92HNAS028)—This document covers VMware best practices specific toHDS HNAS storage.

• Hitachi USP-V/VSP Best Practice Guide for HNAS Solutions(MK-92HNAS025)—The HNAS practices outlined in this document describehow to configure the HNAS system to achieve the best results.

• Hitachi Unified Storage VM Best Practices Guide for HNAS Solutions(MK-92HNAS026)—The HNAS system is capable of heavily driving astorage array and disks. The HNAS practices outlined in this documentdescribe how to configure the HNAS system to achieve the best results.

• Brocade VDX 6730 Switch Configuration for use in an HNAS ClusterConfiguration Guide (MK-92HNAS046)—This document describes how toconfigure a Brocade VDX 6730 switch for use as an ISL (inter-switch link)or an ICC (inter-cluster communication) switch.

• Hitachi NAS Platform Storage Pool and HDP Best Practices(MK-92HNAS048)—This document details the best practices for configuringand using HNAS storage pools, related features, and Hitachi DynamicProvisioning (HDP).

• Hitachi NAS Platform Hitachi Dynamic Provisioning with HNAS v12.1(MK-92HNAS057)—This document lists frequently asked questionsregarding the use of Hitachi Dynamic Provisioning.

• Hitachi Multi-tenancy Implementation and Best Practice Guide(MK-92HNAS059)—This document details the best practices for configuringand using HNAS Multi-Tenancy and related features, and EVS security.

8 About this documentHitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

Related VMware documentationFor more information about VMware vSphere, refer to the vSphere 6 guidesprovided by VMware. VMware documentation is located at: https://www.vmware.com/support/pubs/

Hitachi Storage Provider for VMware vCenter documentation includes:• Hitachi Storage Provider for VMware vCenter Release Notes for File

Storage—In PDF form, this guide provides the most up-to-date informationabout the software, including new feature summaries, and known issues.

• Hitachi Storage Provider for VMware vCenter Deployment Guide for FileStorage—In PDF form, this guide provides a complete reference for usingthe Hitachi Storage Provider for VMware vCenter for file storage.

About this document 9Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

https://www.vmware.com/support/pubs/


2About Hitachi Storage Provider for

VMware vCenterThe VASA Storage Provider sets up a communication management pathbetween the VMware® vCenter Server™ and storage platforms to enable aVMware® vSphere® Virtual Volumes (VVol) environment. The StorageProvider software is delivered and operates as a virtual appliance in theenvironment. It translates the vCenter management operations, such asCreate VVol and Snapshot VVol, into HDS-specific calls or offload operations.The software also provides the interface to share storage capabilities forstorage containers between Hitachi storage platforms and the vCenter Server.

□ Storage Provider deployment architecture

□ VMware terms and concepts

□ Understanding the Storage Provider Web user interface

10 About Hitachi Storage Provider for VMware vCenterHitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

Storage Provider deployment architecture

VMware terms and conceptsThis section briefly describes key terms and VMware environment objectsthat are relevant to the Storage Provider for file storage.

The term vSphere is a collective name for the VMware-based virtualenvironment, which includes the VMware® vSphere® software, VMware®

About Hitachi Storage Provider for VMware vCenter 11Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

vCenter Server™ software, VMware® ESXi™ clusters and hosts managed bythe vCenter Server, and the virtual machines (VMs) and vApps hosted onthose ESXi clusters.

The following table describes key terms and objects:

Note: See the VMware documentation at https://www.vmware.com/support/pubs/ for more details.

Term or acronym Definition

Protocol endpoint PE. An ESXi host uses a PE as a logical I/O proxy to communicate withvirtual volumes (VVols) and the virtual machine disks (VMDKs) that theVVols contain. The PE must be accessible on the physical fabric and is usedas the data path by the ESXi host for direct access to the VVols. Theattached storage manages all other aspects of VVols.

For a NAS file system, a PE is a fully-qualified NFS export comprised of ahost name (or IP address) and an export name.

For example: 172.19.9.160:/hnas1/test

SPBM Storage policy-based management leverages the new VVol-based storage.Storage provisioning uses SPBM to match storage array capabilities toestablished VMDK profiles.

Storage array A data storage system – block or file. In HNAS terms, a storage array is an

HNAS cluster or a single node HNAS.

Storage container A logical grouping of virtual volumes. New virtual volumes (VVols, or theirderivatives) are created inside a storage container. Consider a storagecontainer a pool of raw storage capacity or an aggregation of storagecapabilities that a storage system can provide to VVols.

Storage containers:• Are not known to protocol endpoints (PEs)• Are not discoverable using in-band means• Have two attributes:

○ Name○ Maximum capacity

• Can be homogenous, such as high-end storage for high-performanceVVols or a mixture of storage with a wide range of VVols

VASA vSphere APIs for Storage Awareness. APIs that make possible integrationbetween the vSphere, vCenter, and HNAS software, and the backendstorage. Using VASA, the storage array and its storage containers arepresented to VMs for consumption.

VMDK Virtual machine disk. With the transformation of SAN and NAS storageentities into VM-centric devices, a VMDK becomes the native representationof the VM at the array level.

VVol Virtual Volume. The Virtual Volume (VVol) feature defines a new virtual diskcontainer (Virtual Volume) that is independent of the underlying physicalstorage representation, allowing for finer control. In other terms, withVirtual Volumes, the virtual disk becomes the primary unit of datamanagement at the storage level.

VVol datastore A VVol datastore or virtual datastore represents a storage container to thevCenter Server software. The VVol datastore defines capacity boundariesand access logic, and exposes a set of data services that are accessible to




Term or acronym Definition

the VMs provisioned in the pool. Virtual datastores are purely logicalconstructs.

Understanding the Storage Provider Web user interfaceThe Storage Provider Web UI permits you to specify which storage systemsare managed by the Storage Provider, and configure and manage thosestorage systems, and the associated storage containers.

The Storage Provider Web UI opening page displays a list of option buttons:

The following table describes the options:

Item Description

Set or Exit Maintenance Mode Puts the Storage Provider in maintenance mode.

Note: This option toggles between Set MaintenanceMode and Exit Maintenance Mode.

Manage Hardware Allows you to discover hardware, add new managed hardware to

the Storage Provider, or edit which managed hardware that the

Storage Provider manages.


Item Description

Storage Containers Allows you to either define a new storage container or modify a

specific container.


3System requirements

The Hitachi Storage Provider for VMware vCenter product for file storagesystems has specific requirements.

See VMware documentation at https://www.vmware.com/support/pubs/ forinformation about VMware products.

□ Software

□ Hardware

□ Protocols

□ Licensing

16 System requirementsHitachi Storage Provider for VMware vCenter Deployment Guide for File Storage


SoftwareThe Storage Provider for file storage requires the following software.

Item Requirement

Hitachi Data Systems • Hitachi NAS File Operating System 12.2.3753.08 or later.• Hitachi NAS SMU 12.2.3753.10 or later.

VMware

Note: See the vSphere 6 documentation at https://www.vmware.com/support/pubs/ for details.

• vCenter 6 and vCenter required components.• vSphere 6 and vSphere Web Client required components.• vSphere Client Integration Plug-in 6.0.0.2799 or later for vSphere Web

Client (thin-client) installs, and its software requirements.

Note: The following links are valid at time of publication.Should a link not respond, go to https://www.vmware.com/support/pubs/ and navigate to Support Resources >Documentation > VMware vSphere 6 > vSphere Installation andSetup Guide > Deploying the vCenter Server Appliance > Installthe Client Integration Plug-In.

○ See the vSphere 6 Client Integration Plug-in software requirementsat http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-C17B5998-1B86-4E15-9E59-6DD969B07247.html.

○ See the vSphere 6 Client Integration Plug-in install instructions at http://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.install.doc/GUID-CA16F78B-7890-4357-9760-AF8648806FE7.html.

○ Find the installer located at http://vsphereclient.vmware.com/vsphereclient/VMware-ClientIntegrationPlugin-6.0.0.exe.

Important: Only use the released versions of vSphere 6 andCenter 6 software.

Browsers • Storage Provider Web UI:○ Storage Provider supports only the Firefox 35.0.1 browser or later

for this release.• VMware

○ Important: See the supported browsers for vSphere 6Web Client at http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-F6D456D7-C559-439D-8F34-4FCF533B7B42.html.

System requirements 17Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage





http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-C17B5998-1B86-4E15-9E59-6DD969B07247.html



http://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.install.doc/GUID-CA16F78B-7890-4357-9760-AF8648806FE7.html



http://vsphereclient.vmware.com/vsphereclient/VMware-ClientIntegrationPlugin-6.0.0.exe


http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-F6D456D7-C559-439D-8F34-4FCF533B7B42.html



HardwareThe Storage Provider software supports the following Hitachi Data Systemsgateways and storage systems.

Important: The Storage Provider software requires a Hitachi NAS Gatewaydirectly attached to supported Hitachi Storage.

Item Requirement

Hitachi NAS Gateway HNAS 4060, 4080, and 4100

Hitachi Storage • Hitachi Virtual Storage Platform (VSP and VSP G1000)• Hitachi Unified Storage VM (HUS-VM)• HUS 110, 130, and 150

Note:

ProtocolsThis release of the Storage Provider software for file storage supports thefollowing protocols.

Item Requirement

NFS NFS version 3

LicensingThe Storage Provider has no license requirement for this release.

Other license requirements:• Hitachi NAS Gateway license• HNAS file clone on the HNAS

18 System requirementsHitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

System requirements 19Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

4Installing Storage Provider

This section describes how to the Storage Provider for file storage systems.

□ Install high-level process

□ Where to find the OVF

□ Where to deploy the OVF

□ Installing vSphere Client Integration Plug-in

□ Deploying the OVF

20 Installing Storage ProviderHitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

Install high-level processHitachi Data Systems provides you with the Storage Provider software in anOpen Virtualization Appliance (OVA) tar package.

The OVA uses .ova as its file extension and contains the Open VirtualizationFiles (OVF). The OVA is deployed with the vSphere Web Client to create theVM instance that runs the Storage Provider. This VM contains the product aswell as all of its dependencies.

The high-level process for installing the Storage Provider includes thefollowing steps:

1. In the vSphere Web Client, install the Storage Provider by using thevSphere Deploy OVF feature.

2. In the Storage Provider Web UI, configure the Storage Provider formanaging HNAS, defining storage containers, and so on.

3. In the vSphere Web Client, register the Storage Provider.

Where to find the OVFObtain the Storage Provider OVA from one of the following locations.

• Media kit provided.• Download from VMware.• Download from HDS Support Portal.• Your Hitachi account representative.

Where to deploy the OVFDeploy the OVA/OVF on a NFS datastore that has been previouslyprovisioned.

Installing vSphere Client Integration Plug-inThe vSphere 6 software features the vSphere Web Client, a thin-clientversion of the software. For the Storage Provider to work with the vSphereWeb Client, you must install the VMware Client Integration Plug-in software inthe vSphere Web Client interface before you deploy the OVF.

The Client Integration Plug-in enables you to access a virtual machine'sconsole and connect virtual devices to virtual machines through the vSphereWeb Client. You only need to install the Client Integration Plug-in once.

Installing Storage Provider 21Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

Prerequisites

Note: The following links are valid at time of publication. Should a link notrespond, go to https://www.vmware.com/support/pubs/ and navigate toSupport Resources > Documentation > VMware vSphere 6 > vSphereInstallation and Setup Guide > Deploying the vCenter Server Appliance >Install the Client Integration Plug-In.

• Have the Client Integration Plug-in software requirements met. See http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-C17B5998-1B86-4E15-9E59-6DD969B07247.html for details.

• Have the Client Integration Plug-in software. The installer is located at http://vsphereclient.vmware.com/vsphereclient/VMware-ClientIntegrationPlugin-6.0.0.exe .

• Have administrator privileges.• Have the browser closed.

Important: If the machine is a shared administration system, be surethat other users of the system do not have a browser open.

Procedure

1. Right-click the downloaded Client Integration Plug-in software, and selectRun As administrator.








2. Test the installation of the Plug-in by launching a browser and logginginto the vSphere Web Client software.

In the Launch Application dialog, perform the following steps:a. In the Choose an application field, select the path to the vmware-

csd.exe file.b. Select the checkbox for Remember my choices for vmware-csd

links.c. Click OK to confirm.You can now proceed to deploying the OVF.

Deploying the OVFDeploying the OVF installs the Storage Provider software to the location youspecify. Use these steps to install the Storage Provider software.

Prerequisites• OVF package is available.• vSphere 6 environment is installed and running.• Software and version requirements are met for vSphere Web Client. Using

the required versions can help avoid possible instability of the vSphereWeb Client running in the browser. See Software requirements on page 17for details.

• When deploying with the vSphere Web Client, have the vSphere ClientIntegration Plug-in installed and successfully tested.

• Have an NFS datastore provisioned. This will be datastore that the VMappliance installs on during deployment.


Procedure

1. Locate the OVF package files to a storage location that is local to theclient system on which you want to launch the Web browser and log in tothe vCenter Server.

Important: Referencing the files from another location may be possible,but if the client is transferring the file over the network, then the installtime can be severely impacted.

2. Launch a browser and log in to the vSphere Web Client interface.3. In the Navigator pane at the left side of screen, perform the following

steps:a. Select vCenter Home > vCenter Inventory Lists.b. Select Virtual Machines.c. In the Virtual Machines pane, click the Deploy OVF template icon.


4. In the Select source screen, enter a URL or browse to the locationwhere the OVF is located, then click Next.

5. In the Review details screen, verify the OVF details, then click Next.


6. In the Accept License Requirements screen, click Accept and thenNext.

7. In the Select Name and Folder screen, perform the following steps:

a. Enter a name for the template.b. Select a datacenter location for the template.c. Click Next.


8. In the Select a resource screen, select the host or cluster on which todeploy the OVF, then click Next.

9. In the Select storage screen, perform the following steps:

a. From the Select virtual disk format drop-down list, select ThinProvision.

b. From the VM Storage Policy drop-down list, select DatastoreDefault.

c. In the table of datastores, select the destination storage on which youwant the OVF to deploy.


Note: This datastore is typically the NFS datastore you previouslyprovisioned.

d. Click Next.

10. In the Setup networks screen, from the Destination drop-down list,

select the network that you want the deployment to use, then click Next.


11. In the two Customize Template screens, enter values for each of thefollowing deployment properties, and then click Next.

Important: You must complete all of the properties fields in both of theCustomize template screens.

Note: Hitachi Data Systems recommends you use Hitachi VP for theHost Name .


Item Description

Network Configuration

IP Address IP address for the Storage Provider.

DNS Server IP address for the DNS server you primarily use.

Gateway IP address for the default gateway you use.

Netmask Netmask you use for this interface.

System Configuration

Domain Name Fully qualified domain name.

Host Name Host name for this VM (displays after you register your Storage

Provider).

NTP NTP server name.

Vasa Provider Configuration

User Name For Storage Provider login.

Password For Storage Provider login.


12. In the Ready to Complete screen, confirm your settings, then clickFinish.

The OVF deploys and installs the Storage Provider software.


5Validating installation

You must validate the software installation by confirming that you havesecure communication between the vSphere, vCenter, and Storage Providersoftware. As well, you must confirm that the Storage Provider's Web UI isaccurately reporting status to the Storage Provider software.

Validating the install helps you avoid troubleshooting communication andinstallation problems should an issue occur later during storage provisioningand management operations.

□ Powering on the VM

□ Logging in to the Storage Provider Web UI

32 Validating installationHitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

Powering on the VMAfter successful OVF deployment, a new VM is automatically created basedon the configuration you provided during the deployment process. You mustpower on that VM before you can log in to it.

Procedure

1. In the vSphere Web Client, power ON the newly created VM.See the VMware documentation at https://www.vmware.com/support/pubs/ for more details.

2. In the vSphere Web Client, log in to a command line console with thefollowing steps:a. Navigate to vCenter Inventory Lists > Virtual Machines.b. Select the powered-on VM.c. Select Open console to open a command window.

3. Issue the command ifconfig to check the network configuration.4. Validate that the settings are what was provided during the OVF

deployment process.

Logging in to the Storage Provider Web UIAfter the VM has booted, you can login to the Storage Provider Web UI.

The login screen displays with the default user root. The root user hasadministrator privileges.

Procedure

1. Open a browser and enter the following path for the Storage ProviderWeb UI: https://[storage provider IP]:8843/version.xml

2. In the Storage Provider Web UI login screen dialog, enter the user nameand password as admin and nasadmin respectively.The Storage Provider Web UI displays.

Validating installation 33Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage



6Configuring Storage Provider

This section describes configuring the Storage Provider for file storagesystems.

Access the various Storage Provider configuration options through thebuttons in the Storage Provider Web UI option list.

□ Managing maintenance mode

□ Managing hardware

□ Managing storage containers

□ Registering the Storage Provider with vCenter Server

34 Configuring Storage ProviderHitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

Managing maintenance modeTo perform certain operations, the Storage Provider must be in maintenancemode.

Consider the following characteristics about maintenance mode andoperational mode:• After you install and launch the Storage Provider software, the Storage

Provider starts up in maintenance mode and remains there until you definea storage container.

• The Storage Provider must be in maintenance mode to accomplish dutiesassociated with the following functions:○ Manage Hardware○ Storage Containers

Note: The Manage Hardware and Storage Containers buttons are grayedout when they are not available.

• The Storage Provider maintenance mode toggles between maintenancemode and operational mode. These modes are mutually exclusive. Whenyou exit maintenance mode, you enter operational mode.

• The mode button itself toggles between Set Maintenance Mode and ExitMaintenance Mode.○ If the Storage Provider is in maintenance mode, the mode button

displays as Exit Maintenance Mode.○ If the Storage Provider is in operational mode, the mode button displays

as Set Maintenance Mode.

Setting maintenance modeUse the Storage Provider Web UI to enter or exit Maintenance Mode.

Procedure

1. From the Web UI list of options, select Set Maintenance Mode.2. In the confirmation dialog, confirm you want to proceed.

The Storage Provider mode moves to maintenance mode.

Exiting maintenance modeUse the Storage Provider Web UI to exit maintenance mode. You can exitmaintenance mode if one or more storage containers exist in the hardwareconfiguration.

Procedure

1. From the Web UI list of options, select Exit Maintenance Mode.2. In the confirmation dialog, confirm you want to proceed.

Configuring Storage Provider 35Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

The Storage Provider mode moves to operational mode.

Managing hardwareThis section describes how you can view existing managed hardware, addnew hardware for the Storage Provider to manage, and delete hardware frombeing managed.

The Manage Hardware screen displays as shown in the following:

From this screen, you can perform the following operations:

Item Description

Add Adds new hardware to be managed by the Storage Provider.

Delete Deletes hardware that is being managed by the Storage Provider.

Viewing managed hardwareYou can view the managed hardware through the Storage Provider Web UI.

Prerequisites• Have the Storage Provider in maintenance mode.

Procedure

1. From the Web UI list of options, select Managed Hardware.


2. In the Manage Hardware screen, you can view the storage arrayscurrently being managed by the Storage Provider.

3. Select an array from the Storage Arrays section at the left.The details for that array display in the Selection Details section at theright.

Adding new hardwareUse the Storage Provider Web UI to add new hardware to be managed by theStorage Provider. The new hardware can include HNAS hardware clusters .Adding hardware in this manner enables the Storage Provider to recognizethe hardware.


Procedure

1. From the Web UI list of options, select Managed Hardware.2. In the Managed Hardware screen, click Add.


3. In the Add Storage Arrays dialog, enter values for the array you wantto add, then click Connect to see the File System table, which lists of filesystems available for use.

Item Description

HostName or IP Name or IP of the Admin EVS to be managed.

User ID User identification for the Admin EVS (admin).

Password Password for the Admin EVS (nasadmin).

Connect Accomplish connection to the Admin EVS.

4. Click Save to complete the hardware addition.

Deleting managed hardwareYou can delete hardware being managed by the Storage Provider through theStorage Provider Web UI.


When you deleted hardware from being managed by the Storage Provider,the following actions also occur:• Any encapsulated file systems and protocol endpoints are deleted.• If a storage container still has references to the file systems in this storage

array, the storage container is modified to exclude these file systems.


Procedure

1. From the Web UI list of options, select Managed Hardware.2. In the Manage Hardware screen, select Delete.3. In the dialog that displays, select the storage arrays you want to delete.4. Click Ok to complete.

Managing storage containersStorage containers are logical groupings of file systems. This sectiondescribes how you can view, add and delete storage containers in the StorageProvider through the Storage Provider Web UI.

Note: The Storage Provider must be in maintenance mode to managestorage containers.

The Storage Containers screen displays as shown in the following:

From this screen, you can perform the following operations:

Item Description

Add Adds new storage containers to the Storage Provider.

Delete Deletes an existing storage container.


Viewing storage containersYou can view the configured storage containers through the Storage ProviderWeb UI.


Procedure

1. From the Web UI list of options, select Storage Containers.2. In the Storage Containeres screen, you can view the existing storage

containers in the Storage Provider.3. Select a storage container from the section at the left.

The details for that container display in the Selection Details section atthe right.

Adding storage containersYou must configure a storage container to make the VVol datastores visible tothe vCenter Server software. You can add a new storage container to theStorage Provider through the Storage Provider Web UI.

Prerequisites• Have the Storage Provider in maintenance mode.• Filesystems and LUNs must be greater than 0.

Procedure

1. From the Web UI list of options, select Storage Containers.2. Select Add.


3. In the Add Storage Container dialog, enter values for the storagecontainer you want to add:

Item Description

Storage Container Name of the new storage container.

Max vVol Size Size in Terabytes.

Storage Array Storage array where the container is to be located.

File System Table displays the file systems that can be attached. Data

displayed includes:• File System• Free Space• Total Space• Assignment: Type of data

4. Click Save to complete the storage container addition.

Deleting storage containersYou can delete an existing storage container from the Storage Providerthrough the Storage Provider Web UI.


Procedure

1. From the Web UI list of options, select Storage Containers.2. In the Storage Containers screen, select Delete.


3. In the dialog that displays, select the storage container you want todelete.

4. Click Ok to complete.

Registering the Storage Provider with vCenter ServerTo register the Storage Provider, you must manually add the Storage Providerto the vCenter Server. Registration is performed through the vSphere WebClient.

This registration makes the vCenter application aware of the Storage Providerand establishes communication between them.

Procedure

1. Log in to the vSphere Web Client, and perform the following steps:a. In the Navigator, select Storage.b. In the right pane, select the Manage tab, then Storage Providers.See the VMware documentation at https://www.vmware.com/support/pubs/ for more details.

2. Click the + icon to register a new storage provider.3. In the New Storage Provider dialog, enter values for the following

fields.

Item Description

Name Name for the Storage Provider that is meaningful in your

environment.

Provider URL Location of the Storage Provider. Type https://<IP address of VP>:

8843/version.xml, where <IP address of VP> is the specific IP

address of the Storage Provider in your environment.

Important: Type https://<IP address of VP>:8843/version.xml with your IP address exactly as shown.

Username Name of the administrator or primary user.

Password Password of your choosing.

4. Click OK to complete.After successful registration, and

5. Confirm that the registration was successful by viewing the following:• The Storage Providers section in the vSphere Web Client displays the

newly added Storage Provider.• The Storage Provider Web UI indicates the storage array name with

which it is communicating.




Postrequisites

The system is now configured. Further confirm successful configuration byproceeding with creating a VVol datastore and provisioning a VM on that VVoldatastore.


7Open source licensing

This section lists the Open Source Software Copyrights and Licenses forsoftware used by Hitachi Storage Provider for VMware vCenter.

□ Apache Axis

□ Apache Tomcat

□ Debian Linux

□ OpenJDK7

□ OpenSSL

□ PostgreSQL

□ Google Gson library

□ Apache 2.0 license

□ GNU General Public License (GPL) Version 2.0

44 Open source licensingHitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

Apache AxisThis product includes software developed by The Apache Software Foundation(http://www.apache.org/).

Portions Copyright 2006 International Business Machines Corp.

Portions Copyright 2005-2007 WSO2, Inc.

This product also includes schemas and specification developed by:

- the W3C consortium (http://www.w3c.org)

This product also includes WS-* schemas developed by InternationalBusiness Machines Corporation, Microsoft Corporation, BEA Systems, TIBCOSoftware, SAP AG, Sonic Software, and VeriSign.

This product also includes a WSDL developed by salesforce.com

- Copyright 1999-2006 salesforce.com, inc.

Portions of the included xmlbeans library were originally based on thefollowing:

- software copyright (c) 2000-2003, BEA Systems, <http://www.bea.com/>.

Please read the different LICENSE files present in the lib directory of thisdistribution.

http://axis.apache.org/axis2/java/core/

Apache License, Version 2.0: Apache 2.0 license on page 50

Apache TomcatCopyright 1999-2014 The Apache Software Foundation

This product includes software developed at The Apache Software Foundation(http://www.apache.org/).

http://tomcat.apache.org/


Debian LinuxCopyright © 1997-2012 SPI and others

https://www.debian.org/distrib/

Open source licensing 45Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

http://axis.apache.org/axis2/java/core/

HTTP://TOMCAT.APACHE.ORG/

https://www.debian.org/distrib/

GNU General Public License, Version 2: GNU General Public License (GPL)Version 2.0 on page 54

OpenJDK7© 2007, 2014 Oracle and/or its affiliates

http://openjdk.java.net/install

GNU General Public License (GPL) Version 2.0 : Appendix B

with Classpath Exception (http://openjdk.java.net/legal/gplv2+ce.html):

"CLASSPATH" EXCEPTION TO THE GPL

Certain source files distributed by Oracle America and/or its affiliates aresubject to the following clarification and special exception to the GPL, butonly where Oracle has expressly included in the particular source file's headerthe words "Oracle designates this particular file as subject to the "Classpath"exception as provided by Oracle in the LICENSE file that accompanied thiscode."

Linking this library statically or dynamically with other modules is making acombined work based on this library. Thus, the terms and conditions of theGNU General Public License cover the whole combination.

As a special exception, the copyright holders of this library give youpermission to link this library with independent modules to produce anexecutable, regardless of the license terms of these independent modules,and to copy and distribute the resulting executable under terms of yourchoice, provided that you also meet, for each linked independent module, theterms and conditions of the license of that module. An independent module isa module which is not derived from or based on this library. If you modify thislibrary, you may extend this exception to your version of the library, but youare not obligated to do so. If you do not wish to do so, delete this exceptionstatement from your version.

OpenSSLCopyright (c) 1998-2011 The OpenSSL Project. All rights reserved.

Copyright (C) 1995-1998 Eric Young ([email protected])

This product includes cryptographic software written by Eric Young. Thisproduct includes software written by Tim Hudson ([email protected]).

http://www.openssl.org/


HTTP://OPENJDK.JAVA.NET/INSTALL

HTTP://WWW.OPENSSL.ORG/

OpenSSL License

/*===============================================* Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.** Redistribution and use in source and binary forms, with or without* modification, are permitted provided that the following conditions* are met:** 1. Redistributions of source code must retain the above copyright* notice, this list of conditions and the following disclaimer.** 2. Redistributions in binary form must reproduce the above copyright* notice, this list of conditions and the following disclaimer in* the documentation and/or other materials provided with the* distribution.** 3. All advertising materials mentioning features or use of this* software must display the following acknowledgment:* "This product includes software developed by the OpenSSL Project* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"** 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be usedto* endorse or promote products derived from this software without* prior written permission. For written permission, please contact* [email protected].** 5. Products derived from this software may not be called "OpenSSL"* nor may "OpenSSL" appear in their names without prior written* permission of the OpenSSL Project.** 6. Redistributions of any form whatsoever must retain the following* acknowledgment:* "This product includes software developed by the OpenSSL Project* for use in the OpenSSL Toolkit (http://www.openssl.org/)"** THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' ANDANY* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECTOR* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT,* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF


ADVISED* OF THE POSSIBILITY OF SUCH DAMAGE.*===============================================** This product includes cryptographic software written by Eric Young* ([email protected]). This product includes software written by Tim* Hudson ([email protected]).**/

Original SSLeay License/* Copyright (C) 1995-1998 Eric Young ([email protected])* All rights reserved.** This package is an SSL implementation written* by Eric Young ([email protected]).* The implementation was written so as to conform with Netscapes SSL.** This library is free for commercial and non-commercial use as long as* the following conditions are aheared to. The following conditions* apply to all code found in this distribution, be it the RC4, RSA,* lhash, DES, etc., code; not just the SSL code. The SSL documentation* included with this distribution is covered by the same copyright terms* except that the holder is Tim Hudson ([email protected]).** Copyright remains Eric Young's, and as such any Copyright notices in* the code are not to be removed.* If this package is used in a product, Eric Young should be given attribution* as the author of the parts of the library used.* This can be in the form of a textual message at program startup or* in documentation (online or textual) provided with the package.** Redistribution and use in source and binary forms, with or without* modification, are permitted provided that the following conditions* are met:* 1. Redistributions of source code must retain the copyright* notice, this list of conditions and the following disclaimer.* 2. Redistributions in binary form must reproduce the above copyright* notice, this list of conditions and the following disclaimer in the* documentation and/or other materials provided with the distribution.* 3. All advertising materials mentioning features or use of this software* must display the following acknowledgement:* "This product includes cryptographic software written by* Eric Young ([email protected])"* The word 'cryptographic' can be left out if the rouines from the library* being used are not cryptographic related :-).* 4. If you include any Windows specific code (or a derivative thereof) from* the apps directory (application code) you must include anacknowledgement:* "This product includes software written by Tim Hudson([email protected])"** THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND


* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORSBE LIABLE* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OFSUBSTITUTE GOODS* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION)* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISINGIN ANY WAY* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF* SUCH DAMAGE.** The licence and distribution terms for any publically available version or* derivative of this code cannot be changed. i.e. this code cannot simply be* copied and put under another distribution licence* [including the GNU Public Licence.]*/

PostgreSQLPortions Copyright (c) 1996-2013, PostgreSQL Global Development Group

Portions Copyright (c) 1994, The Regents of the University of California

http://www.postgresql.org/download/linux/debian/

PostgreSQL Database Management System

(formerly known as Postgres, then as Postgres95)

Portions Copyright (c) 1996-2013, PostgreSQL Global Development Group

Portions Copyright (c) 1994, The Regents of the University of CaliforniaPermission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies.

IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


HTTP://WWW.POSTGRESQL.ORG/DOWNLOAD/LINUX/DEBIAN/

THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

Google Gson libraryCopyright (C) 2008 Google Inc.

https://code.google.com/p/google-gson/


Apache 2.0 licensehttp://www.apache.org/licenses/LICENSE-2.0

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, anddistribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by thecopyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entitiesthat control, are controlled by, or are under common control with that entity.For the purposes of this definition, "control" means (i) the power, direct orindirect, to cause the direction or management of such entity, whether bycontract or otherwise, or (ii) ownership of fifty percent (50%) or more of theoutstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercisingpermissions granted by this License.

"Source" form shall mean the preferred form for making modifications,including but not limited to software source code, documentation source, andconfiguration files.


https://code.google.com/p/google-gson/

http://www.apache.org/licenses/LICENSE-2.0

"Object" form shall mean any form resulting from mechanical transformationor translation of a Source form, including but not limited to compiled objectcode, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form,made available under the License, as indicated by a copyright notice that isincluded in or attached to the work (an example is provided in the Appendixbelow).

"Derivative Works" shall mean any work, whether in Source or Object form,that is based on (or derived from) the Work and for which the editorialrevisions, annotations, elaborations, or other modifications represent, as awhole, an original work of authorship. For the purposes of this License,Derivative Works shall not include works that remain separable from, ormerely link (or bind by name) to the interfaces of, the Work and DerivativeWorks thereof.

"Contribution" shall mean any work of authorship, including the originalversion of the Work and any modifications or additions to that Work orDerivative Works thereof, that is intentionally submitted to Licensor forinclusion in the Work by the copyright owner or by an individual or LegalEntity authorized to submit on behalf of the copyright owner. For thepurposes of this definition, "submitted" means any form of electronic, verbal,or written communication sent to the Licensor or its representatives,including but not limited to communication on electronic mailing lists, sourcecode control systems, and issue tracking systems that are managed by, or onbehalf of, the Licensor for the purpose of discussing and improving the Work,but excluding communication that is conspicuously marked or otherwisedesignated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalfof whom a Contribution has been received by Licensor and subsequentlyincorporated within the Work.

2. Grant of Copyright License.

Subject to the terms and conditions of this License, each Contributor herebygrants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,irrevocable copyright license to reproduce, prepare Derivative Works of,publicly display, publicly perform, sublicense, and distribute the Work andsuch Derivative Works in Source or Object form.

3. Grant of Patent License.

Subject to the terms and conditions of this License, each Contributor herebygrants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,irrevocable (except as stated in this section) patent license to make, havemade, use, offer to sell, sell, import, and otherwise transfer the Work, wheresuch license applies only to those patent claims licensable by suchContributor that are necessarily infringed by their Contribution(s) alone or by


combination of their Contribution(s) with the Work to which suchContribution(s) was submitted. If You institute patent litigation against anyentity (including a cross-claim or counterclaim in a lawsuit) alleging that theWork or a Contribution incorporated within the Work constitutes direct orcontributory patent infringement, then any patent licenses granted to Youunder this License for that Work shall terminate as of the date such litigationis filed.

4. Redistribution.

You may reproduce and distribute copies of the Work or Derivative Worksthereof in any medium, with or without modifications, and in Source orObject form, provided that You meet the following conditions:

1. You must give any other recipients of the Work or Derivative Works a copyof this License; and

2. You must cause any modified files to carry prominent notices stating thatYou changed the files; and

3. You must retain, in the Source form of any Derivative Works that Youdistribute, all copyright, patent, trademark, and attribution notices from theSource form of the Work, excluding those notices that do not pertain to anypart of the Derivative Works; and

4. If the Work includes a "NOTICE" text file as part of its distribution, thenany Derivative Works that You distribute must include a readable copy of theattribution notices contained within such NOTICE file, excluding those noticesthat do not pertain to any part of the Derivative Works, in at least one of thefollowing places: within a NOTICE text file distributed as part of theDerivative Works; within the Source form or documentation, if provided alongwith the Derivative Works; or, within a display generated by the DerivativeWorks, if and wherever such third-party notices normally appear. Thecontents of the NOTICE file are for informational purposes only and do notmodify the License. You may add Your own attribution notices withinDerivative Works that You distribute, alongside or as an addendum to theNOTICE text from the Work, provided that such additional attribution noticescannot be construed as modifying the License. You may add Your owncopyright statement to Your modifications and may provide additional ordifferent license terms and conditions for use, reproduction, or distribution ofYour modifications, or for any such Derivative Works as a whole, providedYour use, reproduction, and distribution of the Work otherwise complies withthe conditions stated in this License.

5. Submission of Contributions.

Unless You explicitly state otherwise, any Contribution intentionally submittedfor inclusion in the Work by You to the Licensor shall be under the terms andconditions of this License, without any additional terms or conditions.Notwithstanding the above, nothing herein shall supersede or modify the


terms of any separate license agreement you may have executed withLicensor regarding such Contributions.

6. Trademarks.

This License does not grant permission to use the trade names, trademarks,service marks, or product names of the Licensor, except as required forreasonable and customary use in describing the origin of the Work andreproducing the content of the NOTICE file.

7. Disclaimer of Warranty.

Unless required by applicable law or agreed to in writing, Licensor providesthe Work (and each Contributor provides its Contributions) on an "AS IS"BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, eitherexpress or implied, including, without limitation, any warranties or conditionsof TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR APARTICULAR PURPOSE. You are solely responsible for determining theappropriateness of using or redistributing the Work and assume any risksassociated with Your exercise of permissions under this License.

8. Limitation of Liability.

In no event and under no legal theory, whether in tort (including negligence),contract, or otherwise, unless required by applicable law (such as deliberateand grossly negligent acts) or agreed to in writing, shall any Contributor beliable to You for damages, including any direct, indirect, special, incidental, orconsequential damages of any character arising as a result of this License orout of the use or inability to use the Work (including but not limited todamages for loss of goodwill, work stoppage, computer failure ormalfunction, or any and all other commercial damages or losses), even ifsuch Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability.

While redistributing the Work or Derivative Works thereof, You may choose tooffer, and charge a fee for, acceptance of support, warranty, indemnity, orother liability obligations and/or rights consistent with this License. However,in accepting such obligations, You may act only on Your own behalf and onYour sole responsibility, not on behalf of any other Contributor, and only ifYou agree to indemnify, defend, and hold each Contributor harmless for anyliability incurred by, or claims asserted against, such Contributor by reason ofyour accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work

To apply the Apache License to your work, attach the following boilerplatenotice, with the fields enclosed by brackets "[]" replaced with your ownidentifying information. (Don't include the brackets!) The text should beenclosed in the appropriate comment syntax for the file format. We also


recommend that a file or class name and description of purpose be includedon the same "printed page" as the copyright notice for easier identificationwithin third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License"); you may notuse this file except in compliance with the License. You may obtain a copy ofthe License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributedunder the License is distributed on an "AS IS" BASIS, WITHOUTWARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. Seethe License for the specific language governing permissions and limitationsunder the License.

GNU General Public License (GPL) Version 2.0GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

http://www.gnu.org/licenses/old-licenses/gpl-2.0.html

Copyright (C) 1989, 1991 Free Software Foundation, Inc.

51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA

Everyone is permitted to copy and distribute verbatim copies of this licensedocument, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom toshare and change it. By contrast, the GNU General Public License is intendedto guarantee your freedom to share and change free software--to make surethe software is free for all its users. This General Public License applies tomost of the Free Software Foundation's software and to any other programwhose authors commit to using it. (Some other Free Software Foundationsoftware is covered by the GNU Lesser General Public License instead.) Youcan apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. OurGeneral Public Licenses are designed to make sure that you have the freedomto distribute copies of free software (and charge for this service if you wish),that you receive source code or can get it if you want it, that you can changethe software or use pieces of it in new free programs; and that you know youcan do these things.


http://www.gnu.org/licenses/old-licenses/gpl-2.0.html

To protect your rights, we need to make restrictions that forbid anyone todeny you these rights or to ask you to surrender the rights. These restrictionstranslate to certain responsibilities for you if you distribute copies of thesoftware, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or fora fee, you must give the recipients all the rights that you have. You mustmake sure that they, too, receive or can get the source code. And you mustshow them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2)offer you this license which gives you legal permission to copy, distributeand/or modify the software.

Also, for each author's protection and ours, we want to make certain thateveryone understands that there is no warranty for this free software. If thesoftware is modified by someone else and passed on, we want its recipientsto know that what they have is not the original, so that any problemsintroduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. Wewish to avoid the danger that redistributors of a free program will individuallyobtain patent licenses, in effect making the program proprietary. To preventthis, we have made it clear that any patent must be licensed for everyone'sfree use or not licensed at all.

The precise terms and conditions for copying, distribution and modificationfollow.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION ANDMODIFICATION

0. This License applies to any program or other work which contains a noticeplaced by the copyright holder saying it may be distributed under the termsof this General Public License. The "Program", below, refers to any suchprogram or work, and a "work based on the Program" means either theProgram or any derivative work under copyright law: that is to say, a workcontaining the Program or a portion of it, either verbatim or withmodifications and/or translated into another language. (Hereinafter,translation is included without limitation in the term "modification".) Eachlicensee is addressed as "you".

Activities other than copying, distribution and modification are not covered bythis License; they are outside its scope. The act of running the Program is notrestricted, and the output from the Program is covered only if its contentsconstitute a work based on the Program (independent of having been madeby running the Program). Whether that is true depends on what the Programdoes.

1. You may copy and distribute verbatim copies of the Program's source codeas you receive it, in any medium, provided that you conspicuously and


appropriately publish on each copy an appropriate copyright notice anddisclaimer of warranty; keep intact all the notices that refer to this Licenseand to the absence of any warranty; and give any other recipients of theProgram a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you mayat your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it,thus forming a work based on the Program, and copy and distribute suchmodifications or work under the terms of Section 1 above, provided that youalso meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating thatyou changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or inpart contains or is derived from the Program or any part thereof, to belicensed as a whole at no charge to all third parties under the terms of thisLicense.

c) If the modified program normally reads commands interactively when run,you must cause it, when started running for such interactive use in the mostordinary way, to print or display an announcement including an appropriatecopyright notice and a notice that there is no warranty (or else, saying thatyou provide a warranty) and that users may redistribute the program underthese conditions, and telling the user how to view a copy of this License.(Exception: if the Program itself is interactive but does not normally printsuch an announcement, your work based on the Program is not required toprint an announcement.)

These requirements apply to the modified work as a whole. If identifiablesections of that work are not derived from the Program, and can bereasonably considered independent and separate works in themselves, thenthis License, and its terms, do not apply to those sections when youdistribute them as separate works. But when you distribute the samesections as part of a whole which is a work based on the Program, thedistribution of the whole must be on the terms of this License, whosepermissions for other licensees extend to the entire whole, and thus to eachand every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rightsto work written entirely by you; rather, the intent is to exercise the right tocontrol the distribution of derivative or collective works based on theProgram.

In addition, mere aggregation of another work not based on the Programwith the Program (or with a work based on the Program) on a volume of astorage or distribution medium does not bring the other work under thescope of this License.


3. You may copy and distribute the Program (or a work based on it, underSection 2) in object code or executable form under the terms of Sections 1and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable sourcecode, which must be distributed under the terms of Sections 1 and 2 aboveon a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to giveany third party, for a charge no more than your cost of physically performingsource distribution, a complete machine-readable copy of the correspondingsource code, to be distributed under the terms of Sections 1 and 2 above ona medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer todistribute corresponding source code. (This alternative is allowed only fornoncommercial distribution and only if you received the program in objectcode or executable form with such an offer, in accord with Subsection babove.)

The source code for a work means the preferred form of the work for makingmodifications to it. For an executable work, complete source code means allthe source code for all modules it contains, plus any associated interfacedefinition files, plus the scripts used to control compilation and installation ofthe executable. However, as a special exception, the source code distributedneed not include anything that is normally distributed (in either source orbinary form) with the major components (compiler, kernel, and so on) of theoperating system on which the executable runs, unless that component itselfaccompanies the executable.

If distribution of executable or object code is made by offering access to copyfrom a designated place, then offering equivalent access to copy the sourcecode from the same place counts as distribution of the source code, eventhough third parties are not compelled to copy the source along with theobject code.

4. You may not copy, modify, sublicense, or distribute the Program except asexpressly provided under this License. Any attempt otherwise to copy,modify, sublicense or distribute the Program is void, and will automaticallyterminate your rights under this License. However, parties who have receivedcopies, or rights, from you under this License will not have their licensesterminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it.However, nothing else grants you permission to modify or distribute theProgram or its derivative works. These actions are prohibited by law if you donot accept this License. Therefore, by modifying or distributing the Program(or any work based on the Program), you indicate your acceptance of thisLicense to do so, and all its terms and conditions for copying, distributing ormodifying the Program or works based on it.


6. Each time you redistribute the Program (or any work based on theProgram), the recipient automatically receives a license from the originallicensor to copy, distribute or modify the Program subject to these terms andconditions. You may not impose any further restrictions on the recipients'exercise of the rights granted herein. You are not responsible for enforcingcompliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patentinfringement or for any other reason (not limited to patent issues), conditionsare imposed on you (whether by court order, agreement or otherwise) thatcontradict the conditions of this License, they do not excuse you from theconditions of this License. If you cannot distribute so as to satisfysimultaneously your obligations under this License and any other pertinentobligations, then as a consequence you may not distribute the Program at all.For example, if a patent license would not permit royalty-free redistribution ofthe Program by all those who receive copies directly or indirectly throughyou, then the only way you could satisfy both it and this License would be torefrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under anyparticular circumstance, the balance of the section is intended to apply andthe section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents orother property right claims or to contest validity of any such claims; thissection has the sole purpose of protecting the integrity of the free softwaredistribution system, which is implemented by public license practices. Manypeople have made generous contributions to the wide range of softwaredistributed through that system in reliance on consistent application of thatsystem; it is up to the author/donor to decide if he or she is willing todistribute software through any other system and a licensee cannot imposethat choice.

This section is intended to make thoroughly clear what is believed to be aconsequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certaincountries either by patents or by copyrighted interfaces, the originalcopyright holder who places the Program under this License may add anexplicit geographical distribution limitation excluding those countries, so thatdistribution is permitted only in or among countries not thus excluded. Insuch case, this License incorporates the limitation as if written in the body ofthis License.

9. The Free Software Foundation may publish revised and/or new versions ofthe General Public License from time to time. Such new versions will besimilar in spirit to the present version, but may differ in detail to address newproblems or concerns.


Each version is given a distinguishing version number. If the Programspecifies a version number of this License which applies to it and "any laterversion", you have the option of following the terms and conditions either ofthat version or of any later version published by the Free SoftwareFoundation. If the Program does not specify a version number of this License,you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programswhose distribution conditions are different, write to the author to ask forpermission. For software which is copyrighted by the Free SoftwareFoundation, write to the Free Software Foundation; we sometimes makeexceptions for this. Our decision will be guided by the two goals of preservingthe free status of all derivatives of our free software and of promoting thesharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NOWARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLELAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHTHOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRERISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITHYOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OFALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO INWRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAYMODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BELIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE ORINABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSSOF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINEDBY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATEWITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTYHAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possibleuse to the public, the best way to achieve this is to make it free softwarewhich everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attachthem to the start of each source file to most effectively convey the exclusion


of warranty; and each file should have at least the "copyright" line and apointer to where the full notice is found.

one line to give the program's name and an idea of what it does. Copyright(C) yyyy name of author

This program is free software; you can redistribute it and/or modify it underthe terms of the GNU General Public License as published by the FreeSoftware Foundation; either version 2 of the License, or (at your option) anylater version.

This program is distributed in the hope that it will be useful, but WITHOUTANY WARRANTY; without even the implied warranty of MERCHANTABILITY orFITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public Licensefor more details.

You should have received a copy of the GNU General Public License alongwith this program; if not, write to the Free Software Foundation, Inc., 51Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when itstarts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of authorGnomovision comes with ABSOLUTELY NO WARRANTY; for detailstype `show w'. This is free software, and you are welcometo redistribute it under certain conditions; type `show c' for details.The hypothetical commands `show w' and `show c' should show theappropriate parts of the General Public License. Of course, the commandsyou use may be called something other than `show w' and `show c'; theycould even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or yourschool, if any, to sign a "copyright disclaimer" for the program, if necessary.Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyrightinterest in the program `Gnomovision'(which makes passes at compilers) written by James Hacker.signature of Ty Coon, 1 April 1989Ty Coon, President of ViceThis General Public License does not permit incorporating your program intoproprietary programs. If your program is a subroutine library, you mayconsider it more useful to permit linking proprietary applications with the


library. If this is what you want to do, use the GNU Lesser General PublicLicense instead of this License.

# Copyright (c) 2000, 2002 Silicon Graphics, Inc. All Rights Reserved.# Copyright (C) 2009 Andreas Gruenbacher <[email protected]>## This program is free software: you can redistribute it and/or modify it# under the terms of the GNU General Public License as published by# the Free Software Foundation, either version 2 of the License, or# (at your option) any later version.## This program is distributed in the hope that it will be useful,# but WITHOUT ANY WARRANTY; without even the implied warranty of# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the# GNU General Public License for more details.## You should have received a copy of the GNU General Public License# along with this program. If not, see <http://www.gnu.org/licenses/>.#


Hitachi Storage Provider for VMware vCenter Deployment Guide for File Storage

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]

MK-92HNAS054-00

http://www.hds.com

MAILTO:[email protected]



Hitachi Storage Provider for VMware vCenter Deployment ... · Hi tachi Storage Provider for VMware...

Documents

Transcript of Hitachi Storage Provider for VMware vCenter Deployment ... · Hi tachi Storage Provider for VMware...