Hitachi Storage Provider for VMware vCenter (VASA … Storage Platform G1000, VSP Gx00 models, VSP...

Virtual Storage Platform G1000, VSP Gx00models, VSP Fx00 models, and NAS

Platform

Hitachi Storage Provider for VMwarevCenter (VASA Provider)

Deployment Guide

Release 3.3.0

MK-92ADPTR104-03

© 2015, 2016 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form orby any means, electronic or mechanical, including copying and recording, orstored in a database or retrieval system for commercial purposes without theexpress written permission of Hitachi, Ltd., or Hitachi Data SystemsCorporation (collectively “Hitachi”). Licensee may make copies of theMaterials provided that any such copy is: (i) created as an essential step inutilization 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 theMaterials. “Materials” mean text, data, photographs, graphics, audio, videoand documents.

Hitachi reserves the right to make changes to this Material at any timewithout notice and assumes no responsibility for its use. The Materialscontain the most current information available at the time of publication.

Some of the features described in the Materials might not be currentlyavailable. Refer to the most recent product announcement for informationabout feature and product availability, or contact Hitachi Data SystemsCorporation at https://support.hds.com/en_us/contact-us.html.

Notice: Hitachi products and services can be ordered only under the termsand conditions of the applicable Hitachi agreements. The use of Hitachiproducts is governed by the terms of your agreements with Hitachi DataSystems 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 toaccess relevant data; and

2. Verifying that data continues to be held, retrieved, deleted, or otherwiseprocessed in accordance with relevant laws.

Notice on Export Controls. The technical data and technology inherent inthis Document may be subject to U.S. export control laws, including the U.S.Export Administration Act and its associated regulations, and may be subjectto export or import regulations in other countries. Reader agrees to complystrictly with all such regulations and acknowledges that Reader has theresponsibility to obtain licenses to export, re-export, or import the Documentand any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States andother countries.

AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server,eServer, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13, z/VM, and z/VSE areregistered trademarks or trademarks of International Business MachinesCorporation.

2Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

https://support.hds.com/en_us/contact-us.html

Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the InternetExplorer logo, Microsoft, the Microsoft Corporate Logo, MS-DOS, Outlook, PowerPoint,SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, VisualStudio, Windows, the Windows logo, Windows Azure, Windows PowerShell, WindowsServer, the Windows start button, and Windows Vista are registered trademarks ortrademarks of Microsoft Corporation. Microsoft product screen shots are reprintedwith permission from Microsoft Corporation.

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


Contents

Preface................................................................................................. 9About this guide.....................................................................................................10Product version......................................................................................................10Release notes........................................................................................................ 10Document conventions........................................................................................... 10Accessing product documentation........................................................................... 11Getting help...........................................................................................................12Comments.............................................................................................................12

Part I: Block storage

1 Overview........................................................................................15About the VASA Provider.........................................................................................16VASA Provider deployment architecture................................................................... 16Key terms and concepts..........................................................................................16Overview of VASA Provider Setup............................................................................ 17

2 System requirements.......................................................................19Hardware requirements.......................................................................................... 20Software requirements........................................................................................... 20Supported protocol.................................................................................................21Restrictions and considerations............................................................................... 21

3 Installing the VASA Provider.............................................................23Installation overview.............................................................................................. 24Obtaining the OVF..................................................................................................24Installing vSphere Client Integration Plug-in.............................................................24Deploying the OVF................................................................................................. 26Upgrading the OVF.................................................................................................28Powering on the VM............................................................................................... 29Creating SSL authentication files............................................................................. 29Renewing an SSL authentication file........................................................................ 30Setting up High Availability......................................................................................30


4 Verifying the installation.................................................................. 33Logging in to the Web UI........................................................................................34Verifying the VASA Provider server connections........................................................ 34

5 Setting up the VASA Provider........................................................... 35Setting up the VAAI (VMware vStorage APLs for Array Integration)............................36Setting up Hitachi Command Suite.......................................................................... 36Registering storage systems in the VASA Provider.....................................................37Setting Multi-vCenter..............................................................................................38Registering the Remote site.................................................................................... 38Registering the VASA Provider in VMware vSphere....................................................39Deploying a VVol datastore..................................................................................... 40Removing the VASA Provider from VMware vSphere................................................. 41Viewing storage systems managed by the VASA Provider.......................................... 41Changing VASA Provider credentials........................................................................ 42Removing storage systems managed by the VASA Provider....................................... 42Downloading the VASA Provider log.........................................................................43Configuring log output settings............................................................................... 43Restarting the VASA Provider.................................................................................. 44

Part II: File storage

6 About the file section.......................................................................47Audience............................................................................................................... 48Related Hitachi NAS documentation ........................................................................48Related VMware documentation ............................................................................. 49

7 About Hitachi Storage Provider for VMware vCenter...........................51Storage Provider deployment architecture................................................................52VMware terms and concepts................................................................................... 52About Virtual Volumes ........................................................................................... 54About Storage Policy-Based Management.................................................................55Understanding the Storage Provider Web user interface............................................ 56

8 System requirements.......................................................................59Software requirements........................................................................................... 60Hardware requirements.......................................................................................... 60Port requirements.................................................................................................. 61File system requirements........................................................................................ 61Protocol requirements............................................................................................ 62Licensing requirements...........................................................................................62Naming requirements............................................................................................. 62

9 Installing Storage Provider...............................................................65Install high-level process........................................................................................ 66Finding the OVF..................................................................................................... 66Deployment location...............................................................................................66


Installing vSphere Client Integration Plug-in.............................................................66Deploying the OVF................................................................................................. 68Updating software..................................................................................................74

10 Validating installation.......................................................................77Powering on the VM............................................................................................... 78Logging in to the Storage Provider Web UI...............................................................78Registering the Storage Provider with vCenter Server................................................79

11 Configuring Storage Provider............................................................81Storage Provider configuration workflow.................................................................. 83Managing NAS....................................................................................................... 84

Viewing managed hardware.............................................................................. 84Adding new hardware....................................................................................... 85Deleting managed hardware..............................................................................86

Managing storage containers.................................................................................. 86Viewing storage containers................................................................................88Adding storage containers................................................................................. 88Deleting storage containers............................................................................... 89

Managing capabilities............................................................................................. 90Understanding available capabilities................................................................... 90Viewing configured capabilities.......................................................................... 92Editing capabilities............................................................................................92

Managing profiles...................................................................................................93Viewing configured profiles................................................................................94Creating profiles............................................................................................... 94Editing profiles................................................................................................. 95Deleting profiles............................................................................................... 95

Obtaining logs........................................................................................................96Creating VVol datastores.........................................................................................96Creating VM storage policies................................................................................... 99Managing fault tolerance........................................................................................ 99Managing replication and disaster recovery.............................................................. 99Using Virtual Infrastructure Integrator for database resiliency..................................100

12 Configuring Hitachi Virtual Storage Platform unified system fitted withHitachi NAS modules..................................................................... 101

Configuring NAS modules in a unified system......................................................... 102

A Setting up the VVol environment.................................................... 103Workflow for setting up HCS for VVol usage........................................................... 104Storage Policy Based Management.........................................................................105

B Troubleshooting............................................................................ 107Collecting log data................................................................................................108Storage Provider is offline..................................................................................... 108VVol datastore is inactive...................................................................................... 109


VM is inaccessible.................................................................................................109Additional troubleshooting information...................................................................110

C Open source and third-party software licenses.................................111Apache Axis2....................................................................................................... 112Apache Tomcat.................................................................................................... 112Debian Linux........................................................................................................112Oracle Linux.........................................................................................................113OpenJDK7............................................................................................................114OpenSSL..............................................................................................................115PostgreSQL..........................................................................................................118Apache 2.0 license .............................................................................................. 141GNU General Public License (GPL) Version 2.0........................................................ 145VMware vSphere Software Development Kit License................................................152VMware Tools License...........................................................................................156


PrefaceThis manual provides information for Hitachi Storage Provider for VMwarevCenter Deployment Guide.

□ About this guide

□ Product version

□ Release notes

□ Document conventions

□ Accessing product documentation

□ Getting help

□ Comments

Preface 9Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

About this guideThis guide provides instructions for installing and using Hitachi StorageProvider for VMware vCenter for block and file storage (herein referred to as"VASA Storage Provider" or "Storage Provider). It also includes systemprerequisites, configuration procedures, and the functions provided byVMware to set up the VASA Storage Provider.

This guide is organized as follows:• Part I: Block storage• Part II: File storage

Each documents the system requirements, installation, and configuration ofthe block or file Storage Provider. While both products incorporate similarinstallation mechanisms and use a similar UI, the procedures vary betweenthe two environments. Be sure and consult the topics appropriate for eachStorage Provider.

The two appendices ("Troubleshooting" and "Open source licenses") apply toboth platforms.

Product versionThis document revision applies to 3.3.0 or later.

Release notesRead the release notes before installing and using this product. They maycontain requirements or restrictions that are not fully described in thisdocument or updates or corrections to this document. Release notes areavailable on Hitachi Data Systems Support Connect: https://support.hds.com/en_us/documents.html.

Document conventionsThis document uses the following typographic conventions:

Convention Description

Bold • Indicates text in a window, including window titles, menus, menu options,buttons, fields, and labels. Example:Click OK.

• Indicates emphasized words in list items.

Italic • Indicates a document title or emphasized words in text.

10 PrefaceHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

https://support.hds.com/en_us/documents.html


Convention Description

• Indicates a variable, which is a placeholder for actual text provided by theuser or for output by the system. Example:pairdisplay -g group(For exceptions to this convention for variables, see the entry for anglebrackets.)

Monospace Indicates text that is displayed on screen or entered by the user. Example:pairdisplay -g oradb

< > angle brackets Indicates variables in the following scenarios:• Variables are not clearly separated from the surrounding text or from

other variables. Example:Status-<report-name><file-version>.csv

• Variables in headings.

[ ] square brackets Indicates optional values. Example: [ a | b ] indicates that you can choose a,b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicates that youmust choose either a or b.

| vertical bar Indicates that you have a choice between two or more options or arguments.Examples:

[ a | b ] indicates that you can choose a, b, or nothing.

{ a | b } indicates that you must choose either a or b.

This document uses the following icons to draw attention to information:

Icon Label Description

Note Calls attention to important or additional information.

Tip Provides helpful information, guidelines, or suggestions for performingtasks more effectively.

Caution Warns the user of adverse conditions and/or consequences (forexample, disruptive operations, data loss, or a system crash).

WARNING Warns the user of a hazardous situation which, if not avoided, couldresult in death or serious injury.

Accessing product documentationProduct user documentation is available on Hitachi Data Systems SupportConnect: https://support.hds.com/en_us/documents.html. Check this site forthe most current documentation, including important updates that may havebeen made after the release of the product.

Preface 11Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide


Getting helpHitachi Data Systems Support Connect is the destination for technical supportof products and solutions sold by Hitachi Data Systems. To contact technicalsupport, log on to Hitachi Data Systems Support Connect for contactinformation: https://support.hds.com/en_us/contact-us.html.

Hitachi Data Systems Community is a global online community for HDScustomers, partners, independent software vendors, employees, andprospects. It is the destination to get answers, discover insights, and makeconnections. Join the conversation today! Go to community.hds.com,register, and complete your profile.

CommentsPlease send us your comments on this document to [email protected] the document title and number, including the revision level (forexample, -07), and refer to specific sections and paragraphs wheneverpossible. All comments become the property of Hitachi Data SystemsCorporation.

Thank you!

12 PrefaceHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide



https://community.hds.com/welcome

https://community.hds.com/welcome

mailto:[email protected]

Part

IBlock storage

□ Overview

□ System requirements

□ Installing the VASA Provider

□ Verifying the installation

□ Setting up the VASA Provider

Block storageHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Block storageHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

1Overview

This chapter provides an overview of the VASA Provider.

□ About the VASA Provider

□ VASA Provider deployment architecture

□ Key terms and concepts

□ Overview of VASA Provider Setup

Overview 15Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

About the VASA ProviderVASA Provider enables policy-based datastore operations.

In the policy-based datastore operation, you can create a datastore byselecting a Storage Container without any special knowledge of the storagesystem. You can create a virtual machine (VM) by setting policies (such ashigh IOPS and reliability) and can also verify whether the VM complies withthese policies.

As in previous releases, the usual event and alarm notifications provide thenecessary information for policy-based datastore operations.

VASA Provider deployment architectureThe following diagram depicts how the VASA Provider functions.

Key terms and conceptsThis topic describes key terms and VMware environment objects relevant tothe VASA Provider.

16 OverviewHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

The term vSphere is a collective name for the VMware-based virtualenvironment, which includes the VMware vSphere software, VMware vCenterServer software, VMware ESXi clusters and hosts managed by the vCenterServer, and the virtual machines (VMs) and vApps hosted on those ESXiclusters.

The following table describes key terms and objects.

For details about these concepts, see the Hitachi Command Suite User Guideand the VMware documentation at https://www.vmware.com/support/pubs/.

Term Description

Block Abbreviation for Block Storage. This indicates storage systems other than HNAS.

DRS vSphere Distributed Resources Scheduler. DRS allows automatic movement of thevirtual machine during maintenance without the need for suspending service. Formore information, see https://www.vmware.com/products/vsphere/features-drs-dpm.

OVF Open Virtualization Format. This standard format enables the exchange of imagefiles of virtual machine image files across different virtualization software.

VASA Abbreviation for VMware vSphere Storage APIs for Storage Awareness. This functionindicates the overall storage management functions of vSphere. See VMwaredocuments at https://www.vmware.com/support/pubs/.

Overview of VASA Provider SetupSetting up the VASA Provider requires two operations:• Registering the storage system in the VASA Provider• Registering the VASA Provider in VMware vSphere

Additional operations described in this manual should be performed asneeded.

You can use the Web UI to configure VASA Provider settings as described inthe following table.

Operation Function Description

Management Add ConfiguredHardware

Lists managed storage systems or selects thestorage system to be managed by the VASAProvider after collecting the storage systeminformation from Hitachi Command Suite.

View ConfiguredHardware

Lists the storage systems managed by theVASA Provider. You can also remove storagesystems from the VASA Provider with thisfunction.

Change Credentials Change the maintenance user accountpassword (default maintenance user accountand password are system and manager).

Maintenance Single Sign-On Setting Registers or updates vCenter Single Sign Oninformation.

Overview 17Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

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

https://www.vmware.com/products/vsphere/features-drs-dpm

https://www.vmware.com/products/vsphere/features-drs-dpm


Operation Function Description

Download Logs Downloads log files generated by the VASAProvider.

Troubleshooting Guide Displays the Troubleshooting Guide.

For storage system, storage container, and protocol endpoint settings usingDevice Manager, see the Hitachi Command Suite User Guide.

For an overview of VVol configuration after VASA Provider is complete, see Setting up the VVol environment on page 103.

For the operations and specifications of VMware, see https://www.vmware.com/support/pubs/.

18 OverviewHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide



2System requirements

This chapter describes the requirements for configuring the VASA Provider.For the operations and specifications of VMware, see https://www.vmware.com/support/pubs/.

□ Hardware requirements

□ Software requirements

□ Supported protocol

□ Restrictions and considerations

System requirements 19Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide



Hardware requirementsThe following table lists the supported models and storage systemrequirements.

Component Requirement

VirtualStoragePlatformG1000

80-03 or later

VSP G200,G400, G600,G800

83-02 or later

VSP F400,F600, F800

83-02 or later

Host busadapter

HBAs must support the "Secondary LUNID" feature to use VVols

Refer to the http://www.vmware.com/resources/compatibility/search.php?deviceCategory=io&details=1&pFeatures=206&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc&bookmark=1 web page (highlight "Secondary LUNID(Enables VVols)" in the Features list).

VMware ESXihost todeploy VASAProvider

• CPU: vCPU (4)• Main memory: 8G• HDD capacity: 100 GB• Ethernet: 1 Gbps or more is recommended

Display forWeb UI

• Display resolution: 1600 x 900 or higher (recommended)• Color depth: 24 bit or higher (recommended)

Software requirementsThis topic lists software requirements for the VASA Provider. For moreinformation on VMware requirements, see https://www.vmware.com/support/pubs/.

Software Requirements

VMware VMware vSphere Web Client 6.0 / 6.0 update 1 / 6.0 update 2

VMware vCenter Server 6.0 / 6.0 update 1 / 6.0 update 2

VMware ESXi Server 6.0 / 6.0 update 1 / 6.0 update 2

Multipath software Native VMware NMP or Dynamic Link Manager (8.2.0-01 orlater)

Browser Microsoft Internet Explorer 10.0.19 and later

Mozilla Firefox 34 and later

Google Chrome 39 and later

VASA Provider PostgreSQL 9.3

20 System requirementsHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

http://www.vmware.com/resources/compatibility/search.php?deviceCategory=io&details=1&pFeatures=206&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc&bookmark=1





Software Requirements

Oracle Linux 7.2 (This is included in OVF file. Please contactsupport at Oracle for any question. You may have to purchasesupport service from Oracle. Not recommended to updateOracle Linux itself.)

Supported protocolThe FC/iSCSI protocol is used to connect the ESXi Server and the storagesystem.

Restrictions and considerationsThe following restrictions apply when using the VASA Provider.

Provided service (operation)

VASA Provider only supports policy-based datastore operation.

Fastclone operations

VMware Horizon View and VMware vRealize Automation deployments usingLinked cloned operations (fastclone) are not supported in this release. Thesefunctions will return an error indicating it is unsupported.

LDEVs and SLU attribute

Creating and deleting LDEVs with the SLU attribute can only be managedusing VMware vCenter Server. Attempting such an operation without usingVMware vCenter Server can disrupt the storage system configuration.

Storage vMotion for VM of the snapshot configuration with branch

Storage vMotion for a VM of a snapshot configuration with branch mayappear to fail. However, the data of the virtual machine of the source are notaffected. When using Storage vMotion, execute the operation after creatingthe snapshot configuration with no branch.

VM disk format

Only Thin Provision Disk format is supported. You can choose Thick ProvisionLazy Zeroed or Thick Provision Eager Zeroed, but data are stored on thestorage system in Thin Provision format.

Cancelling a Storage vMotion migration task

When a VM migration task with Storage vMotion has started, do not cancelthe task. Such a cancellation may fail depend on the timing. However, the VMremains on normal status even though the task failed and you can continueto use it.


Cancelling a VM snapshot

Once a snapshot process starts, do not attempt to cancel the task. Instead,delete the snapshot data after the task completes.

Cancelling a task during the revert processing of snapshot

If you cancel the task during revert processing of a snapshot for a VM, thetask fails but some revert processes may not complete. Retry the operationand make certain the task completes properly.

File upload to VVol Datastore

File upload to the VVol Datastore using VMware vSphere is not recommendedbecause it may fail.

Multiple VASA Providers

You can register multiple VASA Providers in the VMware vCenter server.However, registering the same storage system in multiple VASA Providers isnot supported.

Restarting the VASA Provider

Depending on the timing of a storage failure, you might not be able to accessthe datastore or VM created on the SC. Wait for a while after the failurerecovery and, if re-scanning the VASA Provider does not restore access,restart the VASA Provider.

After restarting the VASA Provider, it will take time to clear the VM accessfailure status.


3Installing the VASA Provider

This chapter describes how to install and perform the initial configuration ofthe VASA Provider.

□ Installation overview

□ Obtaining the OVF

□ Installing vSphere Client Integration Plug-in

□ Deploying the OVF

□ Upgrading the OVF

□ Powering on the VM

□ Creating SSL authentication files

□ Renewing an SSL authentication file

□ Setting up High Availability

Installing the VASA Provider 23Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Installation overviewThe VASA Provider is distributed as an Open Virtualization Format (OVF) fileand is deployed on VMware vSphere as a packaged virtual machine (VM).(The VM includes not only the VASA Provider but all the dependencies.)

The procedure for deploying the VASA Provider is as follows.

Note: An Open Virtualization Appliance (OVA) .tar package includes the OVF.

1. Install the VASA Provider using the OVF deployment function of theVMware vSphere.

2. From the VASA Provider web UI, change VASA Provider settings asneeded.

3. Register the VASA Provider in VMware vSphere.

OVF deployment target

Connect to the vCenter Server in which the ESXi Server that becomes thedeployment target of the VASA Provider is registered by vSphere Web Client.

Obtaining the OVFThe VASA Provider OVF can be obtained from the following sources:• The VASA Provider distribution media• Download from VMware• Download from HDS Support Portal• Your Hitachi account representative

Installing vSphere Client Integration Plug-inThe vSphere 6 software features the vSphere Web Client, a thin-clientversion of the software. Confirm that the VMware Client Integration Plug-insoftware is installed in the vSphere Web Client interface or install it beforeyou 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.

Before you begin

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.

24 Installing the VASA ProviderHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide


• 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,confirm that 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.

The Launch Application dialog displays when the browser opens.

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.


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



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


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

Before you beginCheck the following:• 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 20for details.

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

• Have an VMFS/NFS datastore provisioned. This will be the datastore thatthe VM appliance installs on during deployment.

• Have the IP address of the ESXi host upon which you want to deploy theOVF.

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.

Note: Referencing the files from another location may be possible,but if the client is transferring the file over the network, then theinstall time 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 the screen, perform the

following steps:a. Select vCenter Home > vCenter Inventory Lists.b. Select Virtual Machines.c. In the Virtual Machines pane at the right side of the screen, click the

Deploy OVF template icon ( ).4. In the Select source screen, browse to the location where the OVF is

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

Next.6. In the Select name and folder screen, perform the following steps:

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


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

8. In the Select storage screen, perform the following steps:a. From the Select virtual disk format drop-down list, select applicable

disk format.b. From the VM Storage Policy drop-down list, select Datastore

Default.c. In the table of datastores, select the destination storage on which you

want the OVF to deploy.

Note: This datastore is typically the VMFS/NFS datastore youpreviously provisioned.

d. Click Next.9. In the Setup networks screen, from the Destination drop-down list,

select the network that you want the deployment to use, then click Next.10. In the two Customize template screens, perform the following steps:

Important: Complete all of the properties fields in both of theCustomize template screens or the deploy operation fails.

a. Enter a value for each deployment property.b. Click Next.c. Click the Systems Configuration drop-down icon, and arrow down to

see the remaining three fields.

Item Description

Network Configuration

IP Address IP address for the Storage Provider

DNS Server IP address for the DNS server

Gateway IP address for the default gateway

Netmask Netmask for the interface

SSO Server Configuration

FQDN or IP Address The FQDN or IP address for vCenter Single Sign-On Server

HTTPS Port The HTTPS Port Number for vCenter Single Sign-On Server

System Configuration

Domain Name Fully qualified domain name

Host Name or IP address Host name for this VM (displays after you register your StorageProvider). We recommend you use Hitachi VP for the HostName. If the host name has not been created in DNS, use theIP address. If you supply an invalid host name, vSphere doesnot assign an IP address. You will need to redeploy the OVF witha proper host name.

NTP NTP server name


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

The vCenter software deploys the OVF template and installs the StorageProvider software.

Upgrading the OVFIf you are running a previous version of the VASA Provider, upgrade the OVFas described here.

Before you begin• The OVF file is available on the local system.• vSphere 6.0 is installed and running.

Procedure

1. Remove the previous VASA Provider version from VMware vSphere.a. Log in to the vSphere Web Client.b. In the Navigator, click Home.c. Click vCenter Inventory Lists.d. On the Resources tab, click vCenter Servers.e. Select vCenter Server > Manage > Storage Providers.f. Select the previous version of the VASA Provider, then click the

removal icon (×).2. Remove the virtual machines managed by the previous version of the

VASA Provider from the inventory:a. Login to the vSphere Web Client.b. In the Navigator, click Home.c. Click VMs and Templates.d. Select the virtual machine(s) managed by the previous version of the

VASA Provider.e. Right-click, then choose Remove from Inventory from the Action

menu.3. Unmount the datastores managed by the previous version of the VASA

Provider:a. Log in to the vSphere Web Client.b. In the Navigator, click Home.c. Log in Storage.d. Select the datastore(s) managed by the previous version of the VASA

Provider.e. Right-click, then choose Unmount Datastore from the Action menu.

4. Install the current version of the VASA Provider according to theprocedure described in Installing the VASA Provider on page 23.

5. Migrate the database from the Device Manager server used by theprevious version of the VASA Provider to the HDvM included in theHitachi Storage Provider v3.3.0software package.


a. Export the data in the HDvM database used by the previous version ofthe VASA Provider.

b. Log in to the VASA Provider server. (user name: root; password:password).

c. Import the data into the HDvM database included with the currentversion of the VASA Provider.

Note: For details about the HDvM included in the VASA ProviderV03.3.0 software package, see VASA Provider deploymentarchitecture on page 16 and Setting up Hitachi Command Suite onpage 36. For details about migrating data, see the HitachiCommand Suite Administrator Guide.

6. Register the storage system as described in Registering storage systemsin the VASA Provider on page 37.

7. Create a VVol datastore as described in Deploying a VVol datastore onpage 40. Be sure to select the same storage container used by theprevious version of the VASA Provider.

8. Register the virtual machine(s) managed by the previous version of theVASA Provider:a. Log in to the vSphere Web Client.b. In the navigator, click Home.c. Click Storage.d. Right-click to select Register VM.e. Select the .vmx configuration file for the Virtual Machine.f. Set Name and Location.g. Select Host/Cluster.h. Click Finish.

Powering on the VMPower on the VM where the VASA Provider is deployed.

Procedure

1. Select the VM from the vCenter Inventory list.2. Right-click and select Power On.

Creating SSL authentication filesThis topic describes how to create SSL authentication files.

Before you begin• The VASA Provider has been installed.• The VM has been powered on.• Network settings have been configured.


Procedure

1. Log in to the VASA Provider server (default user name: system,password: manager).

2. Start the root Terminal (default password: password)3. Open the SSL certificate setting file (/root/vpcert/openssl.cnf) with a

text editor such as vi, and then change the value 0.0.0.0 to the IPaddress of the VASA Provider server.

4. At the command prompt, enter the following:cd /root/vpcert./createCertifications.sh

5. Restart the VASA Provider for your changes to take effect.

Result

The process is complete when the following files are created in the /usr/local/hitachivp-b/tomcat/conf directory:• vp.csr• keystore.jks

Note: If a certificate was created, you must restart the VASA Provider. If acertificate was not created, retrieve the following log file and contactSupport: /usr/local/hvp/log

Renewing an SSL authentication fileSSL certificates have an expiration date. To extend an expiration date youmust recreate the certificate.

Procedure

1. Follow the procedure in Removing the VASA Provider from VMwarevSphere on page 41.

2. Follow the procedure in Creating SSL authentication files on page 29.3. Follow the procedure in Registering the VASA Provider in VMware

vSphere on page 39.

Setting up High AvailabilityThe VASA Provider can secure High Availability through the VMware vSphereHigh Availability (vSphere HA) or VMware vSphere Fault Tolerance (vSphereFT) functions. Since the VVol environment may become unavailable if anerror occurs with the VASA Provider, we recommend that you create a HighAvailability setup. For details on using VMware, see https://www.vmware.com/support/pubs/.




Note:• Unexpected errors occurring with the VASA Provider may prevent normal

recovery. Periodically backing up the VASA Provider environment (VM) toanother environment is recommended.

• The use of vSphere FT may cause a reduction in performance. See http://www.vmware.com/files/pdf/techpaper/VMware-vSphere6-FT-arch-perf.pdf.

Subsequently, if an error occurs, set the environment using the followingprocedure provided by VMware: http://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.avail.doc/GUID-63F459B7-8884-4818-8872-C9753B2E0215.html.• Lower the number of run operations in the VVol environment.• Change the VASA Provider ESXi host to a CPU or Disk with better

performance.

Monitoring a virtual machine and application

The VASA Provider enables monitoring of the application level under thevSphere HA configuration. By enabling the Monitoring of the virtual machineand application option of vSphere HA, the virtual machine will automaticallyrestart when the VASA Provider service stops.

Before you begin• VMware Tools have been applied to the virtual machine of the VASA

Provider.• The monitoring of vSphere HA, virtual machines has been configured.

For more information, see the VMware documents at https://www.vmware.com/support/pubs/.

Procedure

1. Log in to the VASA Provider server as root.2. Open the VasaProvider.properties file with a text editor such as vi,

and then set the value of thevasaprovider.highavailability.isEnabledApplicationMonitoringproperty to true.The VasaProvider.properties file is located in the following directory:

/usr/local/hitachivp-b/tomcat/webapps/VasaProvider/META-INF

Note: Whenever you change the value of a property, you mustrestart the VASA Provider.


http://www.vmware.com/files/pdf/techpaper/VMware-vSphere6-FT-arch-perf.pdf

http://www.vmware.com/files/pdf/techpaper/VMware-vSphere6-FT-arch-perf.pdf

http://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.avail.doc/GUID-63F459B7-8884-4818-8872-C9753B2E0215.html





4Verifying the installation

This chapter describes the settings you should verify after installation.

□ Logging in to the Web UI

□ Verifying the VASA Provider server connections

Verifying the installation 33Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Logging in to the Web UIAfter installing the VASA Provider, start the browser and enter the URL of theVASA Provider server to verify that you can log in. Use a PC that can beconnected to the VM where the VASA Provider is deployed.

Procedure

1. In a browser, enter the following URL:https://VASA-Provider-IP-Address:50001/

2. In the Web UI window, enter vCenter SSO Username and passwordor system and manager as the user ID and password and click Login.The VASA Provider information is displayed on the Web UI main window.

Item Description

Service Name Service name of the VASA Provider

Service PortNumber

Communication port number of VMware vSphere and the VASA provider

Database PortNumber

Communication port number of the VASA Provider and DBMS

Service Version VASA Provider version

VASA Version VASA API version

Supported Model Model name of the storage system

Verifying the VASA Provider server connectionsVerify the connections between the VASA Provider server, and all VMwarevSphere servers (ESXi Server/vCenter) that communicate with the VASAProvider.

Procedure

1. Log in to the VASA Provider server (user name: root, password:password)

2. Enter the following command:ping IP-addressWhere IP-address is the IP address of the ESXi Server/vCenter server.Verify that you get a response from the server.

Note: The clocks of the VMware vSphere (ESXi Server/vCenter)and the VASA Provider must be synchronized. However, do notchange the clock of the VASA Provider operating system while theprovider is in operation.

34 Verifying the installationHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

5Setting up the VASA Provider

This chapter describes for procedures for setting up and maintaining theVASA Provider.

□ Setting up the VAAI (VMware vStorage APLs for Array Integration)

□ Setting up Hitachi Command Suite

□ Registering storage systems in the VASA Provider

□ Setting Multi-vCenter

□ Registering the Remote site

□ Registering the VASA Provider in VMware vSphere

□ Deploying a VVol datastore

□ Removing the VASA Provider from VMware vSphere

□ Viewing storage systems managed by the VASA Provider

□ Changing VASA Provider credentials

□ Removing storage systems managed by the VASA Provider

□ Downloading the VASA Provider log

□ Configuring log output settings

□ Restarting the VASA Provider

Setting up the VASA Provider 35Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Setting up the VAAI (VMware vStorage APLs for Array Integration)Within the VVols environment, offload VMware ESXi host processing to thestorage system using VAAI (VMware vStorage APIs for Array Integration).Perform the following settings to enable VAAI.

Before you begin• Host with VMware ESXi 6.0 installed.• vSphere CLI is installed or SSH access to VMware ESXi is available.

Procedure

1. Log in to the VMware ESXi. Access to the ESXi host by following VMwareprocedure.• If using vSphere CLI: https://pubs.vmware.com/vsphere-60/topic/

com.vmware.vcli.examples.doc/cli_overviews.3.7.html• If using SSH ： http://pubs.vmware.com/vsphere-60/topic/

com.vmware.vcli.getstart.doc/cli_run_local.5.3.html2. Verify the VAAI_FILTER claimrule:

# esxcli storage core claimrule list --claimrule-class=Filter | grep HITACHIFilter 65434 runtime vendor VAAI_FILTER vendor=HITACHI model=* false false 0Filter 65434 file vendor VAAI_FILTER vendor=HITACHI model=* false false 0

3. Delete the VAAI_FILTER claimrule:esxcli storage core claimrule remove --claimrule-class=Filter --rule=65434

4. Verify the VAAI claimrule:# esxcli storage core claimrule list --claimrule-class=VAAI | grep Extra IVAAI 65434 runtime vendor VMW_VAAIP_HDS vendor=HITACHI model=* false false 0VAAI 65434 file vendor VMW_VAAIP_HDS vendor=HITACHI model=* false false 0

5. Delete the VAAI claimrule: #esxcli storage core claimrule remove --claimrule-class=VAAI --rule=65434

6. Restart the VMware ESXi host.

Setting up Hitachi Command SuiteThe VASA Provider links to storage systems using Hitachi Command Suite(HCS); therefore HCS must be set up before using the VASA Provider. Thebasic settings needed to use VVols are described here.

36 Setting up the VASA ProviderHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

https://pubs.vmware.com/vsphere-60/topic/com.vmware.vcli.examples.doc/cli_overviews.3.7.html

https://pubs.vmware.com/vsphere-60/topic/com.vmware.vcli.examples.doc/cli_overviews.3.7.html

http://pubs.vmware.com/vsphere-60/topic/com.vmware.vcli.getstart.doc/cli_run_local.5.3.html

http://pubs.vmware.com/vsphere-60/topic/com.vmware.vcli.getstart.doc/cli_run_local.5.3.html

Before you begin

Make certain that:• VASA Provider is installed• A storage system is available for use and the VVol setup is complete

Before you begin

For details, see the following documentation:• Hitachi Command Suite User Guide• Hitachi Command Suite Administrator Guide

Procedure

1. Access the HCS included in the VASA Provider.

URL:http://VASA-Provider-IP-Address:22015/DeviceManagerWebService/index.jsp

User ID: system

Password: manager2. Register the license in HCS.3. Create a user in HCS.4. Create a user group in HCS.5. Register the user that you created in the step 3 and resource groups to

the user group that you created in the step 4.6. Register the storage system in HCS.7. Create a storage container.

The HCS included with the VASA Provider is to be used only within theVVol environment.

Use the normal HCS or Storage Navigator to manage storage systemoutside of the VVol environment.

When registering storage systems in the HCS, separate them per HCSuser resource. (Multiple logins by the same user may cause VVol-relatedoperations to fail.)

Registering storage systems in the VASA ProviderYou must register storage systems in the VASA Provider to pass informationto VMware vSphere.

Procedure



2. Type vCenter SSO Username and password as the user ID andpassword and click Login.

3. In the Web UI main window, click Add Configuration Hardware.4. Enter the following information to discover the storage system from

Hitachi Command Suite:• Network IP address• HCS user name and password

5. Click Discover/Update HDvM Credentials.A list of storage systems is displayed. (Only storage systems supportedby the VASA Provider are shown.)

6. Select a storage system to be managed, and click Add.

Note: Whenever you change the user ID or password for HitachiCommand Suite, you must repeat this procedure.

Setting Multi-vCenterFollow the procedure listed below to register the VASA Provider on multiplevCenter servers. If a VASA Provider is not registered on a vCenter server,then perform Steps 2-3 only. After registering a VASA Provider on a vCenterserver, perform all of the steps in the procedure to set the settings formultiple vCenter servers.

Procedure

1. Delete any VASA Provider registrations that are on the vCenter Server.2. Login to the VASA Provider server as the root user.3. Open the VasaProvider.properties file with vi or other text editor, then

set the value for multipleVcSupport to true. TheVasaProvider.properties file is located in the followingdirectory: /usr/local/hitachivp-b/tomcat/webapps/VasaProvider/META-INF

4. Run the createCertifications.sh script.5. Restart the VASA Provider by restarting the operating system or the VM.6. Register the VASA Provider with the vCenter Server.

Note: Whenever you change the value of a property, you mustrestart the VASA Provider.

Registering the Remote siteYou can consolidate landing pages as a remote site after registering filestorage from a block storage VASA Provider.

Procedure of registering a remote site is followed.


Procedure


2. In the Setup Web URL window, select the Setup tab.3. Enter the remote site IP address inNetwork IP Address.4. Enter the remote site Port Number5. Click Set.

Note: If you see an SSL certificate caution message and you areunable to access the VASA Provider's file storage through thelanding page, you must register the VASA Provider file storage URLas an exception in the web browser settings.

Registering the VASA Provider in VMware vSphereTo register the Storage Provider, you must manually add the Storage Providerto the vCenter Server by using the vSphere Web Client.

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

Note: If you cannot register the VASA provider with the vCenter Server, thecertificate may have expired. Verify the expiration date of the vCenter Servercertificate.

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.4. Click OK. If the Security Alert window appears, click Yes.

Item Description

Name Any name (example: VASA Provider for block)

URL The URL of the VASA Provider:

https://VASA-Provider-IP-Address:50001/version.xmlUser name vCenter SSO Username

(example:vsphere.local\Administrator)




Item Description

Password vCenter SSO Password

Note: When the VASA provider is registered for the first time, thefollowing error is displayed by VMware vSphere: A problem wasencountered while registering the provider. Thecertificate is not trusted.

If the VASA provider registration completes and goes online, themessage can be ignored.

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 indicates the storage array name with which it is

communicating.

Next steps

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

Deploying a VVol datastoreAfter you have successfully registered the Storage Provider, you can deploy aVVol datastore.

Before you begin

• Have the filesystem and a storage container already available on thestorage array.

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

Procedure

1. Log in to the vSphere Web Client and select Home in the Navigator.2. Under the Inventory List, select the datacenter where you want to deploy

the VVol datastore.3. In the action pane at the right side, click Actions, and then right-click

Storage > New Datastore.The New Datastore screen shows the Location with the datastore youselected.

4. In the Location screen, click Next.5. In the Type screen, select VVOL and then click Next.6. In the Name and container selection screen, select your datastore

from those listed in the Backing Storage section, and then click Next.




7. In the Select hosts accessibility screen, select the check boxes to addthe hosts that you want to associate with your datastore, and then clickNext.

8. In the Ready to complete screen, review your settings, and then clickFinish.You are returned to the Home screen, where the new VVol datastorenow displays under your datacenter in the Inventory List.

Removing the VASA Provider from VMware vSphereRemove the VASA Provider associated with the VMware vSphere server.

Procedure

1. In the VASA Provider Registration window, select the VASA Provider andclick the x icon located in the middle of the window.

2. In the Removal Confirmation window, click Yes.

Viewing storage systems managed by the VASA ProviderView the list of managed storage systems.

Procedure


2. In the Web UI Login window, enter vCenter SSO Username andpassword as the user ID and password and click Login.

3. In the Web UI main window, click View Configured Hardware.

The list of managed storage systems is displayed with the followinginformation:• Serial Number• Name• Model• Microcode• Status• Capacity (Total, Used, and Free)

Note: If Microcode, Status, Total Capacity, Used Capacity, or FreeCapacity are displayed as "-" (hyphen), the connection to DeviceManager has failed. Check the connection and repeat theprocedure.


Changing VASA Provider credentials

Before you begin

The maximum number of characters for credentials is 255. The supportedcharacters are:

A-Z a-z 0-9 ! # $ % & ' { } * + - . = @ ^ | ~ / ? `

You can change the user ID and password to be entered when you registerthe VASA Provider in VMware vSphere.

Procedure

1. Enter the following URL in your browser:https://VASA-Provider-IP-Address:50001The p50001?Block is specified using the -p option when installing theVASA Provider; the default is 50001.

2. In the Web UI Login window, enter vCenter SSO Username andpassword and click Login.

3. In the Web UI main window, click Change Credentials.4. Provide the following information:

• Current User Name and Password (currently logged in)• New User Name and Password• Confirm New Password

5. Click Change Credentials.

Removing storage systems managed by the VASA ProviderRemove storage systems managed by the VASA Provider.

Procedure

1. Enter the following URL in your browser:https://VASA-Provider-IP-Address50001

2. In the Web UI Login window, enter vCenter SSO Username andpassword and click Login.

3. In the Web UI main window, click View Configured Hardware.4. Select the storage system to be removed, and then click Remove.

Confirm your choice when prompted.The list of the storage systems is updated accordingly.

Note: When you remove storage systems, you cannot operate anexisting VM created on the target storage. Make certain the VM nolonger exists before removing a storage system.


Downloading the VASA Provider logDownload the log files created by the VASA Provider in compressed (ZIP)format. The archive contains the following files:

File Description

CLP/CommonLandingPage/CommonLandingPage.log

Common Landing Page log file

CLP/version.txt Common Landing Page version number

Others/logs/Tomcat related log Tomcat log file

VP/version.txt VASA Provider version number

VP/log/StorageProvider.log VASA Provider log file

VP/log/StorageProvider.log.tmp Temporary VASA Provider log file

WebUi/log/VasaWebUi.log WebUI log file

WebUi/version.txt WebUI version number

WebUi/log/VasaWebUi.log.tmp Temporary WebUI log file

Procedure

1. Enter the following URL in your browser:https://VASA-Provider-IP-Address:50001

2. In the Login window, enter vCenter SSO Username and password orsystem and manager as the user ID and password and click Login.

3. In the Web UI main window. click Download Logs.4. Download the log files according to the instructions in your browser.

Configuring log output settingsYou can change the maximum number of file generations to be retained andthe rotation size for log files generated by the VASA Provider(StorageProvider.log) and the VASA Provider WebUI (VasaWebUi.log).

Before you begin• The VASA Provider has been installed.• The VM has been powered on.• Network settings have been configured.• SSL files have been created.

Procedure

1. Log into the VASA Provider server (default user name: system,password: manager.)

2. Start the root Terminal (default password: password)3. Edit the hilogger.config file as desired to change the following

parameters.


Item Description

MaxBackupIndex Indicates the generation number. Range: 1-255. Default value:20. (Any value outside the range is treated as the default.)

MaxFileSize Indicates the log rotation size. Range: 1-100. Default value: 50MB. (Any value outside the range is treated as the default.)

The hilogger.config file is stored in the following locations:

For VASA Provider: /usr/local/hitachivp-b/tomcat/webapps/VasaProvider/WEB-INF/conf

For VASA Provider WebUI: /usr/local/hitachivp-b/tomcat/webapps/VasaProviderWebUi/WEB-INF/conf

For VASA Provider Common Landing Page: /usr/local/hitachivp-common/tomcat/webapps/CommonLandingPage/WEB-INF/conf

Refer to Downloading the VASA Provider log on page 43 for a descriptionof the log files.

4. Restart the VASA Provider for your changes to take effect.

Restarting the VASA ProviderRestart the VASA Provider by restarting the operating system or the VM.


Part

IIFile storage

□ About the file section

□ About Hitachi Storage Provider for VMware vCenter

□ System requirements

□ Installing Storage Provider

□ Validating installation

□ Configuring Storage Provider

□ Configuring Hitachi Virtual Storage Platform unified system fitted withHitachi NAS modules

File storageHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

File storageHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

6About the file section

This section describes the file version of the Hitachi Storage Provider forVMware vCenter 6. This version supports the vSphere APIs for StorageAwareness (VASA) 2.0 and VMware VVols (virtual volumes). The StorageProvider integrates the Hitachi NAS 4060, 4080, and 4100 and Hitachi filestorage systems with the vCenter and the VMware vSphere environment.

□ Audience

□ Related Hitachi NAS documentation

□ Related VMware documentation

About the file section 47Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

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.

Hitachi NAS VMware documentation

Hitachi Virtual Infrastructure Integrator Administration Guide MK-92HNAS003

Hitachi NAS Administration Guides

• System Access Guide (MK-92HNAS014) (MK-92USF002) Explains how tolog in to the system, provides information about accessing the NAS server/cluster CLI and the SMU CLI, and provides information about thedocumentation, help, and search capabilities available in the system.

• Server and Cluster Administration Guide (MK-92HNAS010) (MK-92USF007)Provides 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 (MK-92HNAS013)(MK-92USF011)

• Network Administration Guide (MK-92HNAS008) (MK-92USF003) Providesinformation about the server's network usage, and explains how toconfigure network interfaces, IP addressing, name and directory services.

• File Services Administration Guide (MK-92HNAS006) (MK-92USF004)Explains about file system formats, and provides information aboutcreating and managing file systems, and enabling and configuring fileservices (file service protocols).

48 About the file sectionHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

• Storage System User Administration Guide (MK-92HNAS012)(MK-92USF006) Explains user management, including the different typesof system administrator, their roles, and how to create and manage theseusers.

• Command Line Reference• Replication and Disaster Recovery Administration Guide MK-92HNAS009

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

Hitachi NAS Hardware References• Series 4000 Hitachi NAS Platform and Hitachi Unified Storage Series 4000

Hardware Reference (MK-92HNAS030)

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

(MK-92HNAS028) — This document covers best practices specific to usingVMware vSphere with the Hitachi NAS platform.

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

• Hitachi Unified Storage VM Best Practices Guide for HNAS Solutions(MK-92HNAS026) —The system is capable of heavily driving a storagearray and disks. The practices outlined in this document describe how toconfigure the 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 v 12.1 HDP Best Practices (MK-92HNAS063) Thisdocument details the best practices for configuring and using storagepools, related features, and Hitachi Dynamic Provisioning (HDP).

• Hitachi NAS 12.1 HDP Best Practices (MK-92HNAS057) —This documentlists frequently asked questions regarding the use of Hitachi DynamicProvisioning.

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

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/

About the file section 49Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide



50 About the file sectionHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

7About Hitachi Storage Provider for

VMware vCenterThe Storage Provider sets up a communication management path betweenthe VMware vCenter Server and storage platforms to enable a VMwarevSphere Virtual Volumes (VVol) environment. The Storage Provider softwareis delivered and operates as a virtual appliance in the environment. Ittranslates the vCenter management operations, such as Create VVol andSnapshot VVol, into HDS-specific calls or offload operations. The softwarealso provides the interface to share storage capabilities for storage containersbetween Hitachi storage platforms and the vCenter Server.

□ Storage Provider deployment architecture

□ VMware terms and concepts

□ About Virtual Volumes

□ About Storage Policy-Based Management

□ Understanding the Storage Provider Web user interface

About Hitachi Storage Provider for VMware vCenter 51Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

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 following table describes key terms and objects:

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

52 About Hitachi Storage Provider for VMware vCenterHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide



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.

The Storage Provider for file storage automatically creates the PEs; no useraction is required.

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

RDM Raw Device Mapping. An RDM is a type of VMware mapping file that goes in

a VMDK volume. There are two types of RDMs, physical RDM (pRDM) and

virtual (vRDM).An RDM contains metadata required for managing and redirecting diskaccess to the physical device. The file gives you some of the advantages ofdirect access to a physical device, while still having some of the advantagesof a virtual disk in VMFS.

When you need to use raw devices, you need to use an RDM.

Note: Only Command control Interface (CCI) RDMs aresupported at this time.

SPBM Storage Policy-Based Management leverages the new VVol-based storage.Storage provisioning uses SPBM to match storage array capabilities toestablished VMDK profiles. See About Storage Policy-Based Management onpage 55 for more details.

Storage array A data storage system block or file. In Hitachi NAS terms, a storage array

is a Hitachi NAS cluster or a single node NAS array.

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 and maximum capacity• Can be homogenous, such as high-end storage for high-performance

VVols or a mixture of storage with a wide range of VVols

VASA vSphere APIs for Storage Awareness. These APIs make possible theintegration between the vSphere, vCenter, and Hitachi NAS software, andthe backend storage. Using VASA, the storage array and its storagecontainers are presented 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.


Term or acronym Definition

VMFS Virtual Machine File System. VMFS is VMware's clustered file system for

vSphere. VMFS is optimized for virtual machines and works with shared

storage to allow multiple hosts to read and write to the same storage

simultaneously.

vSphere The term vSphere is used in two ways:• The VMware vSphere product is the graphical user interface (GUI) and

management interface for working with vCenter.• The term vSphere is also used as the collective name for the VMware-

based virtual environment, which includes the VMware vSpheresoftware, VMware vCenter Server software, VMware ESXi clusters andhosts managed by the vCenter Server, and the virtual machines (VMs)and vApps hosted on those ESXi clusters.

VVol Virtual Volume. The VMware Virtual Volume (VVol) feature defines a newvirtual disk container (Virtual Volume) that is independent of the underlyingphysical storage representation, allowing for finer control. In other terms,with Virtual Volumes, the virtual disk becomes the primary unit of datamanagement at the storage level. See About Virtual Volumes on page 54

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 tothe VMs provisioned in the pool. Virtual datastores are purely logicalconstructs.

About Virtual VolumesThe VMware Virtual Volumes (VVols) feature is based on a new integrationand management framework between the vSphere product software and astorage system (storage array).

The VVols technology virtualizes SAN and NAS devices by abstracting physicalhardware resources into logical pools of capacity (called virtual or VVoldatastores). These pools can be more flexibly consumed and configured tospan a portion of one or several storage arrays. VVols implements an out-of-band bidirectional control path through the vSphere APIs for StorageAwareness (VASA) and leverages unmodified standard data transportprotocols for the data path, for example NFS, iSCSI, and Fibre Channel.

On the array side, two new components are added to the storageenvironment: VASA Storage Provider for integration with the VASA APIs, andProtocol Endpoints (PE), which allow the storage controller to direct I/Os tothe correct virtual volumes.

On the vSphere product, there are three dependent features: VASA, VVols,and Storage Policy-Based Management (SPBM). To create policies at thevSphere level, a set of published capabilities must first be defined in thestorage array. Then, once defined, these capabilities are surfaced up tovSphere using the VASA Provider.

The virtual datastore defines capacity boundaries and access logic, andexposes a set of data services that are accessible to the VMs provisioned in


the pool. Virtual Datastores are purely logical constructs that can beconfigured as needed, without disruption or the requirement of a formattedfile system.

A VVol is defined as a new virtual disk container that is independent of theunderlying physical storage representation; thereby, allowing for finercontrol. In other terms, with VVols, the virtual disk becomes the primary unitof data management at the array level. This model turns the VirtualDatastore into a VM-centric pool of capacity. It then becomes possible toexecute storage operations with VM granularity and to provision native array-based data services to individual VMs. This capability allows administrators toprovide the correct storage service levels to each individual VM.

Using the VVols feature can help you:• Simplify storage operations

○ Separation of consumption and provisioning○ End-to-end visibility

• Simplify delivery of storage service levels○ Finer control, dynamic adjustment○ Improved resource utilization○ Maximized storage offload potential

The VVols feature offers the following scalability:• Snapshots:

○ For Hitachi NAS, up to 100 million snapshots and clones• VVols:

○ For Hitachi NAS, up to 400,000 initially, with architectural support for 10million VVols

○ For Hitachi Virtual Storage Platform (VSP) G1000, 64,000 VVols, 1million snapshots or clones

About Storage Policy-Based ManagementStorage Policy-Based Management (SPBM) can be viewed as efficientoperations through automation. To enable efficient storage operations atscale, even when managing thousands of VMs, VVols uses vSphere SPBM.SPBM is the implementation of the policy-driven control plane in the VMwareSoftware Defined Services (SDS) model.

SPBM allows capturing storage service levels requirements (capacity,performance, availability, and so on) in the form of logical templates(policies) to which VMs are associated. SPBM automates VM placement byidentifying available datastores that meet policy requirements, and, coupledwith VVols, SPBM dynamically instantiates the necessary data services.Through policy enforcement, SPBM also automates service level monitoringand compliance throughout the life cycle of the VM.


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.

When you login to the Storage Provider Web UI, you have the option ofworking with file storage or block storage. The unified landing page providesdisplays with tabs for File and Setup:

When you click the File tab, the Storage Provider Web UI opening page forfile storage displays. It features a list of option buttons:


Note: In some cases, to see the full Web UI screens, you may need to resizethe browser window larger.

The following table describe the options:

Item Description

Manage NAS Allows you to add new managed hardware to the Storage

Provider, or delete hardware that the Storage Provider manages.

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

specific container.

Manage Capabilities Allows you to assign capabilities to file systems, such as

availability, performance, cost, and so on. Also allows you to

view or edit existing capabilities. Later in Profiles, you can

choose to use the capabilities or not.

Manage Profiles Allows you to create a profile, by selecting some or all of

capabilities assigned by Manage Capabilities. Also allows you to

view, edit, or delete existing profiles.

Update Software Allows you to update the software for the Storage Provider and

the Web UI.

Download Logs Allows you to download and save the logs.

If you want to work with block storage, click the Setup tab to navigate to theblock storage landing page:


8System 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 requirements

□ Hardware requirements

□ Port requirements

□ File system requirements

□ Protocol requirements

□ Licensing requirements

□ Naming requirements



Software requirementsThe 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.0 or later and vCenter required components.• vSphere 6.0 or later 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.

Browsers • Storage Provider Web UI:○ Internet Explorer 11 or later.○ Firefox 35.0.1 browser or later.

• VMware

Important: See the supported browsers for vSphere 6 WebClient at http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUID-F6D456D7-C559-439D-8F34-4FCF533B7B42.html.

Hardware requirementsThe 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.









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





http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUID-F6D456D7-C559-439D-8F34-4FCF533B7B42.html



Item Requirement

Hitachi NAS Gateway Hitachi NAS 4060, 4080, and 4100

Hitachi Storage • Hitachi Virtual Storage Platform (VSP G200, G400, G600, G800,or G1000)

• Hitachi Virtual Storage Platform (VSP G400, G600, G800 or Fx00series) fitted with Hitachi NAS blades.

• Hitachi Unified Storage VM (HUS-VM)• HUS 110, 130, and 150

Port requirementsThe Storage Provider software for file storage has the following portrequirement:

Port Description

8843 vCenter and ESXi access to the Storage Provider

File system requirementsThe Storage Provider software has the following file system-specificrequirement:

Navigate to File Services > NFS Exports > NFS Export Details, and enter thefollowing text in the Access Configuration field:*(rw,insecure,no_root_squash)Click OK to save the setting.


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

Item Requirement

NFS NFS version 3

Licensing requirementsThe Storage Provider has no license requirement for this release.

Other license requirement:• Hitachi NAS server file clone

Naming requirementsThe Storage Provider software for file storage has certain namingrequirements for storage containers, capabilities, and profiles, as well asrequirements for host names.

The names for storage containers, capabilities, and profiles must:• Be a minimum of four characters in length.• Not exceed a maximum of 80 characters in length.• Not use leading and trailing whitespace.• Not use the following unsupported characters:


Symbol Description

& Ampersand

? Question mark

' Single quote

" Double quote

< Less than

> Greater than

# Hash mark

+ Plus sign

The hosts names must only contain:

• ASCII letters a through z (upper or lower case)• Numbers zero (0) through 9• Hyphen (-)


9Installing Storage Provider

This section describes how to install the Storage Provider for file storagesystems.

□ Install high-level process

□ Finding the OVF

□ Deployment location

□ Installing vSphere Client Integration Plug-in

□ Deploying the OVF

□ Updating software

Installing Storage Provider 65Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Install high-level processHitachi Data Systems delivers the Storage Provider software as a virtualmachine (VM), packaged into a tar file.

The OVA tar file uses .ova as its file extension and contains the OpenVirtualization Files (OVF). The OVA is deployed with the vSphere Web Clientto create the VM instance that runs the Storage Provider. This VM containsthe product, as well as all of its dependencies.

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

1. In the vSphere Web Client, navigate to Home > Hosts and Clusters.2. Right click the ESXi host and select Deploy OVF Template.3. In the Storage Provider Web UI, configure the Storage Provider for

managing HNAS, defining storage containers, and so on.4. In the vSphere Web Client, register the Storage Provider.

Finding the OVFObtain the Storage Provider OVA from one of the following locations:

• In the Media kit provided.• Download from VMware.• Download from HDS Support Portal.• Your Hitachi Data Systems account representative.

Deployment locationDeploy the OVA/OVF on an 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. Confirm that the VMware Client Integration Plug-insoftware is installed in the vSphere Web Client interface or install it beforeyou 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.

Before you begin

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.

66 Installing Storage ProviderHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide


• 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,confirm that 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.

The Launch Application dialog displays when the browser opens.

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.

Before you begin• 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 60for 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 the datastore that the VMappliance installs on during deployment.

• Have the IP address of the ESXi host upon which you want to deploy theOVF.

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 bepossible, but if the client is transferring the file over the network,then the install time 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 the screen, perform the

following steps:a. Select vCenter Home > vCenter Inventory Lists.b. Select Virtual Machines.c. In the Virtual Machines pane at the right side of the screen, click the

Deploy OVF template icon ( ).4. In the Select source screen, browse to the location where the OVF is

located, then click Next.


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

Next.

6. In the Accept License Agreements screen, click Accept and then click

Next.


7. In the Select name and folder screen, perform the following steps:

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

8. In the Select a resource screen, select the host or cluster on which to

deploy 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 youpreviously provisioned.

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, perform the following steps:

Important: Complete all of the properties fields in both of theCustomize template screens or the deploy operation fails.

a. Enter a value for each deployment property.b. Click Next.


c. Click the Systems Configuration drop-down icon, and arrow down tosee the remaining three fields.

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 or IP address Host name for this VM (displays after you register your StorageProvider).

Note: Hitachi Data Systems recommends you useHitachi VP for the Host Name.

If the host name has not been created in DNS, use the IPaddress.

: If you supply an invalid host name, vSphere does notassign an IP address. You will need to redeploy the OVFwith a proper host name. See Naming requirements onpage 62.

NTP NTP server name.

12. In the Ready to Complete screen, perform the following steps:


a. Confirm your settings.b. Select the checkbox to Power on after deployment if you want that

to happen.c. Click Finish.

The vCenter software deploys the OVF template and installs the StorageProvider software.

Updating softwareUse the Storage Provider Web UI to update the Storage Provider software orthe Web UI software as needed.

Important: This software update procedure does not apply to updating fromthe 3.0.0 or 3.1.0 releases.

The software comes packaged in a .war archive file. The file is named:<file_name_xxx.jar>

Where xxx is the version of the file. For example,HitachiStorageProvider-3.1.0.5132.jar

Procedure

1. From the Web UI list of options, select Update Software.A dialog displays with a Browse option for both the Storage Providersoftware and the Web UI software.

2. Click the appropriate Browse button to locate the software to update.3. Select the .jar file, then use the following steps to download and apply

the file:a. Browse to the location where you want to download the file.


b. Transfer the file to that location.c. After the software has successfully downloaded, click Apply to apply

the update.The Apply button changes to Working during the data transfer.

Important: Do not close or refresh your browser during thedata transfer.

4. Reboot the machine.The VM reboots as part of the update. Hitachi recommends you restartyour browser.


10Validating 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

□ Registering the Storage Provider with vCenter Server

Validating installation 77Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Powering on the VMAfter successful OVF deployment, a new VM is automatically created basedon the configuration you provided during the deployment process.

Important: You must power on the newly created VM before you can log into 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. Log in to the Storage Provider Web UI. See Logging in to the StorageProvider Web UI on page 78.

3. Register the Storage Provider with the vCenter software. See Registeringthe Storage Provider with vCenter Server on page 79.

4. 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.d. Enter the following credentials:

• user name: adminx• password: O2!0r1nge

Note: First character of the password is an upper case letterO, and the fourth character is the number for zero (0).

5. Open a command window (Windows, Linux, or Unix), and execute theping command using the IP address for the Storage Provider. Forexample: ping 172.19.9.160

Next steps

If, after deployment, the Storage Provider is inaccessible through ping or aWeb browser, delete and deploy the Storage Provider again.

Logging in to the Storage Provider Web UIAfter the VM has booted or the software has been updated, you can log in tothe Storage Provider Web UI.

See Understanding the Storage Provider Web user interface on page 56 forexamples of the login screen, file Web UI, and how to navigate to the blockstorage Web UI.

78 Validating installationHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide



Procedure

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

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

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 yourenvironment.

Provider URL Location of the Storage Provider. Type https://<IP address ofVP>:8843/version.xml, where <IP address of VP> is the specific IPaddress 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 Use system for the username.

Password Use manager for the password.

4. Click OK to complete.5. Confirm that the registration was successful by viewing the following:

• The Storage Providers section in the vSphere Web Client displays thenewly added Storage Provider.

• The Storage Provider Web UI indicates the storage array name withwhich it is communicating.

Validating installation 79Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide



Next steps

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

80 Validating installationHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

11Configuring 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 that displays at the centerof the screen.

□ Storage Provider configuration workflow

□ Managing NAS

□ Managing storage containers

□ Managing capabilities

□ Managing profiles

Configuring Storage Provider 81Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

□ Obtaining logs

□ Creating VVol datastores

□ Creating VM storage policies

□ Managing fault tolerance

□ Managing replication and disaster recovery

□ Using Virtual Infrastructure Integrator for database resiliency

82 Configuring Storage ProviderHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Storage Provider configuration workflowThe following workflow diagram shows the high level steps for configurationof the Storage Provider and the ultimate creation of a VVol datastore.


Managing NASThis section describes how you can view existing managed hardware, addnew NAS clusters for the Storage Provider to manage, and delete hardwarefrom being managed.

The Manage NAS screen displays as shown in the following:

From the Manage NAS screen, you can perform the following operations:

Item Description

Add Adds a new NAS cluster to be managed by the Storage Provider.

Delete Deletes the NAS cluster that is being managed by the Storage Provider.

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

Procedure

1. From the Web UI list of options, select Manage NAS.2. In the Manage NAS screen, you can view the storage arrays currently

being managed by the Storage Provider.3. Select an array from the section at the left.

The details for that array display in the Selection Details section at theright.


4. Click Done.You are returned to the Web UI list of options screen.

Adding new hardwareUse the Storage Provider Web UI to add new hardware to be managed by theStorage Provider. The new hardware can include Hitachi NAS hardwareclusters. Adding hardware in this manner enables the Storage Provider torecognize the hardware.

Before you beginHave a file system already available for use.

Procedure

1. From the Web UI list of options, select Manage NAS.2. In the Manage NAS screen, click Add.3. In the Add NAS Cluster dialog, perform the following steps:

a. Enter the values for the array you want to add.b. Click Connect to see the File System table, which lists the file

systems available for use.

Item Description

HostName or IP Admin EVS or Controller (Unified models with NAS Modules)

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

Password Password for the Admin EVS (supervisor).


Item Description

Connect Accomplish connection to the Admin EVS.

c. Select the file system and associated array in the left side of screen,and confirm the accuracy of the details in the right side of the screen.

d. Click Save to confirm the file system selection.4. Click Done to complete the hardware addition.

You are returned to the Web UI list of options screen.

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

When you delete hardware from being managed by the Storage Provider, thefollowing 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, perform the following steps:

a. In the Storage Arrays section, select the storage array or storagearrays you want to delete.

Note: If a storage array has an associated storage container,the storage container must be deleted before you can deletethat array. A message similar to the following displays: Thisstorage array cannot be deleted because it has storagecontainers. If you want to delete this storage array,delete its storage containers first.

b. After resolving any issues with storage containers, click Delete.3. Click Ok to confirm the deletion.4. Click Done.


Managing storage containersStorage containers are logical groupings of file systems. The containersprovide you with resource pools of storage and the logical abstraction formanaging very large numbers of VVols. This section describes how you canadd new containers in the Storage Provider, and view or delete existingstorage containers.

The operations are accomplished through the following interfaces:• Storage Provider Web UI


• Hitachi Command Suite (HCS) interface - Hitachi recommends you directlymanage storage container and policy-based management through the HCSinterface. This interface allows both block and file or unified VVolimplementations to be managed from a single interface.

In an HDS implementation, storage containers are one or more pools ofstorage (for example, Hitachi Dynamic Provisioning (HDP pools) or HitachiDynamic Tiering (HDT pools for block implementation) or one or morefilesystems (FS1 or FS2 in a VASA provider file implementation). Currently,storage containers do not span outside of an array. This abstraction can beused for managing multi-tenant environments, various departments within asingle organization, and so on. Storage containers can also be used to setcapacity limits for a given logical grouping of VVols.

You must add a storage container or storage containers before you can addcapabilities.

Note: A single host can have 256 storage containers maximum.

From the Manage Storage Containers screen, you can perform thefollowing operations:


Item Description

Add Adds a new storage container 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 Manage Storage Containers.2. In the Manage Storage Containers 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.

4. Click Done.You are returned to the Web UI list of options screen.

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

Before you begin• Have the file system already available on the storage array.

You can add only one VVol datastore to a Storage Container. There is a 1:1mapping between a Storage Container on the Storage Provider and a VVoldatastore in vCenter.

Procedure

1. From the Web UI list of options, select Manage Storage Containers.2. Click Add.3. In the Add Storage Containers dialog, enter values that you want the

new storage container to have.


Item Description

Storage Container Name of the new storage container. See Naming requirements on

page 62.

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

File Systems Table displays the file systems that can be assigned. The data

displayed includes:• File system name• Free Space• Total Space

4. Select one or more file systems.5. Click OK.6. Click Done 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 Manage Storage Containers.2. In the Manage Storage Containers screen, perform the following:

a. From the Storage Containers section at the left, select the storagecontainer that you want to delete.

b. Select Delete.c. Click Done to complete.



Managing capabilitiesA capability is a set of attributes that you can assign to storage for a VVol touse. The attributes include such items as availability, performance, and cost.This section describes how you can define capabilities in the StorageProvider, where you can view the defaults and edit the settings of theexisting capabilities. The operations are accomplished through the StorageProvider Web UI.

After you define the capabilities, you can then assign one of more of them tostorage profiles. These capabilities and profiles can be associated withspecific storage containers. A single storage container can export multiplecapabilities.

Understanding available capabilitiesWhen adding a capability, you specify the value you want it to have. Later,when you are adding a profile, you must assign the capabilities that you wantthe profile to use. You can use the defaults or select from the allowed valuesfor each capability.

The Manage Capabilities screen displays as shown in the following. Thecapability attribute values have already been assigned in this example.


Table 1 Available capabilities

Capability Description

Availability - Class Designates the availability level to store data: Tier 1 for critical data or

constantly accessed data, and lower tiers for non-critical or rarely

accessed data.

Cost - Class Provides a way for you to assign company-specific cost per tier-level

associations to a profile.

Drive Type/Drive Speed Designates the drive type and speed drive.

Encryption Designates whether or not to encrypt the data.

Performance IOPS - Class Designates the performance class for IOPS by tier level.

Performance Latency -

Class

Designates the performance class for latency by tier level.

Pool Type Designates whether pools use Hitachi Dynamic Provisioning (HDP) or

Hitachi Dynamic Tiering (HDT).

RAID Level Designates the level of RAID.

Snapshot Backup

Importance - Class

You can use the snapshot backup class capability to assign a class to a

VM, so that it can later be used in conjunction with your Hitachi Virtual

Infrastructure Integrator backup strategy.

Snapshot Designates whether snapshots are enabled.

Table 2 Capability values

Capability Allowed values Default value

Multiple

values

allowed

Availability - Class Tier1, Tier2, Tier3 Tier1 Yes

Cost - Class Any integer value between 10 and

1000 (inclusive)

10 No

Drive Type/Drive Speed FMC, FMD, SSD, SAS 15K, SAS 10K,

SAS 7.2K, External(any integer between 10 and 1000)

SAS 10K Yes

Encryption Yes or no None No

Performance IOPS - Class Tier1_IOPS, Tier2_IOPS, Tier3_IOPS Tier1_IOPS Yes

Performance Latency -

Class

Tier1_Latency, Tier2_Latency,

Tier3_Latency

Tier1_Latency Yes

Pool Type HDP, HDT HDP No


Capability Allowed values Default value

Multiple

values

allowed

RAID Level RAID6 (14D+2P), RAID6 (12D+2P),

RAID6 (6D+2P), RAID5 (7D+1P),

RAID5 (6D+1P), RAID5 (4D+1P),

RAID5 (3D+1P), RAID1 (2D+2D)

RAID5(3D+1P) Yes

Snapshot Backup

Importance - Class

Critical, Important, Best Effort Critical Yes

Snapshot Yes or no None No

Viewing configured capabilitiesYou can view the existing configured capabilities through the StorageProvider Web UI.

Procedure

1. From the Web UI list of options, select Manage Capabilities.2. In the Manage Capabilities screen, perform the following steps:

a. From the file system drop-down list toward the top left side of thescreen, select the file system whose settings you want to view.

b. View the existing capabilities settings.c. Click Done when finished viewing.


Editing capabilitiesYou can edit an existing capability in the Storage Provider through theStorage Provider Web UI.

Procedure

1. From the Web UI list of options, select Manage Capabilities.2. In the Manage Capabilities screen, perform the following steps:

a. Select the file system whose settings you want to edit from the drop-down list.

b. Click Edit to make the value fields selectable.


c. Edit or assign the capability values as needed.

These fields allow a system administrator to assign existingcapabilities of that filesystem resource, which is later assigned as partof storage profile creation.

Note: Some of these options may be automatically determinedif you use Hitachi Command Suite (HCS) as the VVol interface tomanage the capabilities.

See Understanding available capabilities on page 90 for moreinformation.

d. Click Save to save the values.e. Click Done to complete.


Managing profilesThis section describes how you can create a new profile in the StorageProvider or view, edit, or delete an existing profile from the Storage Provider.The operations are accomplished through the Storage Provider Web UI.


Viewing configured profilesYou can view the existing configured profiles through the Storage ProviderWeb UI.

Procedure

1. From the Web UI list of options, select Manage Profiles.2. In the Manage Profiles screen, view the list of existing profiles in the

Profiles section at the left side of the screen.3. From the profiles listed, select the file system whose profile details you

want to see.The details display in the Profiles Details section at the right side of thescreen.

4. Click Done to return to the Web UI list of options.

Creating profilesYou can create a new profile and assign it a file system through the StorageProvider Web UI.

Before you begin• Have a storage container already added.• Have capabilities already defined for the file system to be assigned with

the new profile.

Procedure

1. From the Web UI list of options, select Manage Profiles.2. In the Manage Profiles screen, select the file system to which you want

to assign a profile, then click Create.

Note: If the file system has no associated profile, the file systemdisplays as: <filesystem name>: No Profile

If all file systems have profiles, the Create function is disabled.

When you click Create, the other fields on the screen become selectable.3. In the Create Storage Profile screen, perform the following steps:

a. Enter a name for the profile. See Naming requirements on page 62.b. Select one or more of the available capabilities to use for the profile.

See Understanding available capabilities on page 90.c. Click Save to save the profile.d. Select the new profile in the Profiles section, and review the Profile

Details at the right side of screen to confirm the capabilities youselected are displayed, then click Done.


Note: If the profile name you entered contains illegalcharacters, a warning message alerts you. Modify the namefield and click Done.

You are returned to the Web UI list of options.

Editing profilesYou can edit an existing profile in the Storage Provider through the StorageProvider Web UI.

Procedure

1. From the Web UI list of options, select Manage Profiles.2. In the Manage Profiles screen, select the file system and its associated

profile in the Profiles section at the left.

The profile details display at the right side.3. In the Edit Storage Profile screen, select the profile you want to edit

from the section at the left, and then click Edit.

Note: If you change the profile name here, it will create a newprofile. It does not change the existing profile.

4. Select or unselected capabilities in the Use in Profile column, as needed.See Understanding available capabilities on page 90 for information, ifneeded.

5. Click Save to save your changes.6. In the Manage Profiles screen, select the file system and its associated

profile in the Profiles Details section, and confirm you profile detains atthe right.You are returned to the Web UI list of options screen.

7. Click Done to complete the editing operation.You are returned to the Web UI list of options screen.

Deleting profilesYou can delete an existing profile from the Storage Provider through theStorage Provider Web UI.

Procedure

1. From the Web UI list of options, select Manage Profiles.2. In the Manage Profiles screen, select the file system and its associated

profile in the Profiles section at the left.

The profile details display at the right side.3. Click Delete to remove the profile.4. Click Done to complete the operation.



Obtaining logsThis section describes how you can download logs from the Storage ProviderWeb UI.

The Storage Provider has a predetermined set of logs that are collected. TheStorage Provider (VP) logs, tomcat logs, the webui log are all collectedautomatically into an archive file (hitachi-logs.tar.gz).

Procedure

1. On the machine that contains the Storage Provider Web UI, selectDownload Logs from the list of options.

2. Locate and select the logs you want to download.3. Save the archive file containing the logs to a location of your choosing.4. If you are obtaining the logs due to a problem you are having, forward

these logs to your contact at Hitachi Data Systems customer support.

Creating VVol datastoresAfter you have successfully registered the Storage Provider, you can create aVVol datastore.

Before you begin

• Have the filesystem and a storage container already available on thestorage array.

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

Procedure

1. Log in to the vSphere Web Client and select Home in the Navigator.2. Under the Inventory List, select the datacenter where you want to create

the VVol datastore.3. In the action pane at the right side, click Actions, and then right-click

Storage > New Datastore.The New Datastore screen shows the Location with the datastore youselected.

4. In the Location screen, click Next.




5. In the Type screen, select VVOL and then click Next.

6. In the Name and container selection screen, perform the following

steps:a. Select your datastore from those listed in the Backing Storage

Container section.b. In the Datastore name field, type a name for your new VVol datastore.c. Click Next.


7. In the Select hosts accessibility screen, select the check boxes to add

the hosts that you want to associate with your datastore, and then clickNext.

8. In the Ready to complete screen, review your settings, and then click

Finish.


You are returned to the Home screen, where the new VVol datastorenow displays under your datacenter in the Inventory List.

9. Navigate to Related Objects > Datastores and perform a vSphererefresh to confirm the new VVol datastore displays.

Creating VM storage policiesAfter creating a VVol datastore, you create one or more storage policies forthe VM.

See the VMware documentation at https://www.vmware.com/support/pubs/for details about how to create virtual machine storage policies.

Managing fault toleranceFault tolerance for the VASA Provider is accomplished using the VMware FaultTolerance (FT) feature. Using FT can help eliminate downtime where theVASA Provider is unavailable due to local site issues. With this support, theVASA Provider can withstand hard failures (ESXI host) and soft failures(Provider is not responding but is online).

For more information about VMware FT, see the VMware documentationlocated at: https://www.vmware.com/support/pubs/

Managing replication and disaster recoveryThe replication and Disaster Recovery (DR) features for VVol datastoresenable you to replicate your VVol-based VMs to a second site based onHitachi Data Systems storage replication technology for DR purposes. Thissupport gives you the same level of DR capabilities that you can experiencetoday with VMFS, NFS datastores, and HDS storage.




Replication and DR for file storage through the Storage Provider areaccomplished through the use of Hitachi NAS software. See Replication andDisaster Recovery Administration Guide MK-92HNAS009 for details.

Replication and DR for block storage through the Storage Provider areaccomplished through the use of Hitachi block software. See Hitachi UniversalReplicator User Guide MK-92RD8023 and Hitachi Universal Replicator UserGuide MK-942HM8023 for details.

Using Virtual Infrastructure Integrator for database resiliencyUsing the Virtual Infrastructure Integrator product you can recover theStorage Provider VM, including the embedded VP database on the storagesystem (PostGresSQL or Hitachi Command Suite (HCS) HirDB), if necessarydue to unforeseen events.

As a best practice, you should locate your database on an NFS datastore or aVMFS datastore, and have the database be protected by Virtual InfrastructureIntegrator.

See Hitachi Virtual Infrastructure Integrator Administration GuideMK-92HNAS003 for details.


12Configuring Hitachi Virtual StoragePlatform unified system fitted with

Hitachi NAS modulesThis section describes configuration considerations for accessing andmanaging a Hitachi unified system; that is, a Hitachi Virtual Storage Platform(VSP G400, G600, or G800) fitted with Hitachi NAS modules.

The new unified system gives you the benefits of both block and file in asingle system.

□ Configuring NAS modules in a unified system

Configuring Hitachi Virtual Storage Platform unified system fitted with Hitachi NAS modules 101Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Configuring NAS modules in a unified systemThis section describes the file storage configuration considerations foraccessing and managing Hitachi NAS modules when they are part of a Hitachiunified system; that is, a Hitachi Virtual Storage Platform (VSP G400, G600,or G800) fitted with Hitachi NAS modules.

For this configuration, the system uses a controller IP address, instead of anAdmin EVS IP address. The configuration screen and configuration sequenceis unchanged. However, some of the UI labels have changed. You only needto input the IP address of one of the controllers in the system.

Once configured and accessed through a provided Controller IP Address, theUnified Management Provider can be queried (Hitachi NAS OS v12.6 or later)to obtain the second controller's IP Address. Both IP addressed are stored, soif a run-time call to one IP address fails, the fail-over controller's IP addresscan be used.

102 Configuring Hitachi Virtual Storage Platform unified system fitted with Hitachi NAS modulesHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

ASetting up the VVol environment

This appendix introduces additional configuration steps necessary toimplement VVol in your environment. For full details on how to perform eachtask, see these manuals:• Hitachi Command Suite User Guide (MK-90HC172)• Hitachi Command Suite Administrator Guide (MK-90HC175)

□ Workflow for setting up HCS for VVol usage

□ Storage Policy Based Management

Setting up the VVol environment 103Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

https://download.hds.com/download/epcra/hc17222.pdf

https://download.hds.com/download/epcra/hc17522.pdf

Workflow for setting up HCS for VVol usage

This topic describes workflow for setting the environment of HitachiCommand Suite to use the VVol functionality. After installing and setting upthe products on the management server and the management server forVVols, the storage administrator registers storage systems and ESXi hosts,and specifies settings for the storage systems.

Note: This workflow applies to both block and file storage implementations.

104 Setting up the VVol environmentHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Storage Policy Based ManagementOne of the prerequisites for configuring a VMware VVol environment involvesdefining the Storage Policy Based Management (SPBM). An SPBM is astructure that is based on a defined VM storage policy, where the VASAprovider and Hitachi Command Suite (HCS) automatically select the storageresources that meet the VM storage policy, and creates VVols.

After DP pools (or Thin Image pools) have been specified and grouped (or,file systems have been specified when working with VVols for file storage),

Setting up the VVol environment 105Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

they can be defined as a storage container, for which a capability profile canbe set. A capability profile defines the capabilities of a storage container (forexample, IOPS, Latency, Availability). Afterward, both the storage containerand associated capability profile can be disclosed to the VM administrator.

Note: After you change the configuration of a DP pool for block storage or afile system for file storage, check and if needed, change the capability profile.

The following steps outline the general task workflow for creating an SPBMstructure. The tasks that apply to the VMware vSphere administrator (VMadministrator) are noted in parenthesis:1. Define capability profiles. Set the capability profile in the storage

container for each DP pool for block storage and for each file system, forfile storage.

2. Define VM Storage Policies (applies to the VM administrator). Createvirtual machine storage policies based on the contents of the capabilityschema. The content that is defined in the capability schema can beviewed as the data service from vCenters.

3. Check storage policy compatibility (applies to the VM administrator).The vCenter reports whether storage containers exist that meet thepolicy criteria. This is done by comparing the capability profiles and VMstorage policies.

4. Create a VVol (applies to the VM administrator).

106 Setting up the VVol environmentHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

BTroubleshooting

This appendix includes troubleshooting information for the VASA Provider(block and file).

□ Collecting log data

□ Storage Provider is offline

□ VVol datastore is inactive

□ VM is inaccessible

□ Additional troubleshooting information

Troubleshooting 107Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Collecting log dataBefore contacting support personnel, you should collect the log informationlisted here.

Component Document Topic

VASA Provider(block)

- Downloading the VASA Provider log onpage 43

VASA Provider (file) - Obtaining logs on page 96

HCS Hitachi Command SuiteAdministrator Guide

Acquiring maintenance information on themanagement server (hcmds64getlogscommand)

Log in to the VASA Provider Server as rootand execute the following command:

/opt/HiCommand/Base64/bin/hcmds64getlogs

Send all of the generated jar files listedbelow as attachments:• HiCommand_log_64.jar• HiCommand_log_64.hdb.jar• HiCommand_log_64.db.jar• HiCommand_log_64.csv.jar

vCenter/ESXi VMware Knowledge Base http://kb.vmware.com/kb/653

Storage SystemLogs

Hitachi Command Suite AuditLog Reference Guide

Downloading syslog files

Maintenance Manual (DKC810I) Collect Dump/Log

Storage Provider is offlineWhen the Storage Provider is offline, the connection with the StorageProvider may have failed.

Procedure

1. Rescan the Storage Provider to confirm whether the status hasrecovered.

2. Confirm whether the Storage Provider time setting matches the vCentertime.

3. Confirm whether the Storage Provider, the storage systems, and thestorage management software are suspended or an error has occurred.

4. Update the SSL certificate of the Storage Provider, and confirm whetherthe status has been recovered.

5. Confirm whether the storage systems have been registered in thestorage management software.

108 TroubleshootingHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

http://kb.vmware.com/kb/653

6. If the related hardware or the software does not have any problems,collect the log of the Storage Provider to confirm that the ERROR is notoutput.If the ERROR is displayed, take the countermeasure which iscorresponding to the ID.

7. If no problem is found, allow some time for the internal processes of thevCenter to complete, then confirm again

VVol datastore is inactiveWhen a VVol datastore is inactive, the datastore is not in a usable state.

Procedure

1. Confirm the Protocol Endpoint information from the summary of StorageContainer.When it is not displayed, a problem may have occurred in the connectionbetween ESXi and the storage system.

2. Rescan the Storage Device to confirm whether the status is recovered.3. Rescan the Storage Provider to confirm whether the status is recovered.4. Confirm whether the Storage Provider, the storage systems, and the

storage management software are suspended or an error has occurred.5. If the related hardware or the software does not have any problems,

collect the log of the Storage Provider to confirm that the ERROR is notoutput.

6. If ERROR is displayed, take the countermeasure that corresponds to theID.

7. If no problem is found, confirm again after waiting a while as the internalprocess of vCenter is running.

VM is inaccessibleWhen the VM is inaccessible, the VM is not usable.

Procedure

1. Rescan the Storage Device to confirm whether the status is recovered.2. Rescan the Storage Provider to confirm whether the status is recovered.3. Confirm whether the Storage Provider, the storage systems, and the

storage management software are suspended or an error occurred.4. Confirm whether the status recovers by restarting the VM for Storage

Provider.5. If the related hardware or the software does not have any problems,

collect the log of the Storage Provider to confirm that ERROR is notoutput.When there is an error, take the action that corresponds to the ID.

Troubleshooting 109Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

6. If no problem is found, confirm again after waiting a while as the internalprocess of vCenter is running.

Additional troubleshooting informationFor the block Storage Provider, click the Help link in the Web Setup UI todisplay troubleshooting scenarios and error codes.

110 TroubleshootingHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

COpen source and third-party software

licenses

This appendix includes the copyrights and licenses for Open Source and third-party software used by the VASA Provider.

□ Apache Axis2

□ Apache Tomcat

□ Debian Linux

□ Oracle Linux

□ OpenJDK7

□ OpenSSL

□ PostgreSQL

□ Apache 2.0 license

□ GNU General Public License (GPL) Version 2.0

□ VMware vSphere Software Development Kit License

□ VMware Tools License

Open source and third-party software licenses 111Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

Apache Axis2This 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 141

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/

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

Debian LinuxCopyright © 1997-2012 SPI and others

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

112 Open source and third-party software licensesHitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

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 145

Oracle LinuxORACLE LINUX LICENSE AGREEMENT

"We," "us," "our" and "Oracle" refers to Oracle America, Inc. "You" and "your" refers to the individualor entity that has acquired the Oracle Linux programs. "Oracle Linux programs" refers to the Linuxsoftware product which you have acquired. "License" refers to your right to use the Oracle Linuxprograms under the terms of this Oracle Linux License Agreement (the "Agreement") and the licensesreferenced herein. This Agreement shall be governed by and construed in accordance with Californialaw, except for that body of California law concerning the conflict of laws, and you and Oracle agreeto submit to the exclusive jurisdiction of, and venue in, the courts of San Francisco or Santa Claracounties in California in any dispute arising out of or relating to this Agreement.

We are willing to provide a copy of the Oracle Linux programs to you only upon the condition that youaccept all of the terms contained in this Agreement. Read the terms carefully and indicate youracceptance by either selecting the "Accept" button at the bottom of the page to confirm youracceptance, if you are downloading the Oracle Linux programs, or continuing to install the OracleLinux programs, if you have received this Agreement during the installation process. If you are notwilling to be bound by these terms, select the "Do Not Accept" button or discontinue the installationprocess.

1. Grant of Licenses to the Oracle Linux programs. Subject to the terms of this Agreement, Oraclegrants to you a license to the Oracle Linux programs under the GNU General Public License version2.0. The Oracle Linux programs contain many components developed by Oracle and various thirdparties. The license for each component is located in the licensing documentation and/or in thecomponent's source code. In addition, a list of components may be delivered with the Oracle Linuxprograms and the Additional Oracle Linux programs (as defined below) or accessed online at http://oss.oracle.com/linux/legal/oracle-list.html. The source code for the Oracle Linux Programs and theAdditional Oracle Linux programs can be found and accessed online at https://oss.oracle.com/sources/. This Agreement does not limit, supersede or modify your rights under the license associatedwith any separately licensed individual component.

2. Licenses to Additional Oracle Linux programs. Certain third-party technology (collectively the"Additional Oracle Linux programs") may be included on the same medium or as part of the downloadof Oracle Linux programs you receive, but is not part of the Oracle Linux programs. Each AdditionalOracle Linux program is licensed solely under the terms of the Mozilla Public License, Apache License,Common Public License, GNU Lesser General Public License, Netscape Public License or similar licensethat is included with the relevant Additional Oracle Linux program.

3. Ownership. The Oracle Linux programs and their components and the Additional Oracle Linuxprograms are owned by Oracle or its licensors. Subject to the licenses granted and/or referencedherein, title to the Oracle Linux programs and their components and the Additional Oracle Linuxprograms remains with Oracle and/or its licensors.

4. Trademark License. You are permitted to distribute unmodified Oracle Linux programs orunmodified Additional Oracle Linux programs without removing the trademark(s) owned by Oracle orits affiliates that are included in the unmodified Oracle Linux programs or unmodified AdditionalOracle Linux programs (the "Oracle Linux Trademarks"). You may only distribute modified OracleLinux programs or modified Additional Oracle Linux programs if you remove relevant imagescontaining the Oracle Linux Trademarks. Certain files, identified in http://oss.oracle.com/linux/legal/oracle-list.html, include such trademarks. Do not delete these files, as deletion may corrupt theOracle Linux programs or Additional Oracle Linux programs. You are not granted any other rights tothe Oracle Linux Trademarks, and you acknowledge that you shall not gain any proprietary interest inthe Oracle Linux Trademarks. All goodwill arising out of use of the Oracle Linux Trademarks shall inureto the benefit of Oracle or its affiliates. You may not use any trademarks owned by Oracle or itsaffiliates (including "ORACLE") or potentially confusing variations (such as, "ORA") as a part of yourlogo(s), product name(s), service name(s), company name, or domain name(s) even if suchproducts, services or domains include, or are related to, the Oracle Linux programs or AdditionalOracle Linux programs.

5. Limited Warranty. THE ORACLE LINUX PROGRAMS AND ADDITIONAL ORACLE LINUX PROGRAMSARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. WE FURTHER DISCLAIM ALLWARRANTIES, EXPRESS AND IMPLIED, INCLUDING WITHOUT LIMITATION, ANY IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

6. Limitation of Liability. IN NO EVENT SHALL WE BE LIABLE FOR ANY INDIRECT, INCIDENTAL,SPECIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE,DATA OR DATA USE, INCURRED BY YOU OR ANY THIRD PARTY, WHETHER IN AN ACTION INCONTRACT OR TORT, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.


http://oss.oracle.com/linux/legal/oracle-list.html


https://oss.oracle.com/sources/




OUR ENTIRE LIABILITY FOR DAMAGES HEREUNDER SHALL IN NO EVENT EXCEED ONE HUNDREDDOLLARS (U.S.).

7. No Technical Support. Our technical support organization will not provide technical support, phonesupport, or updates to you for the materials licensed under this Agreement. Technical support, ifavailable, may be acquired from Oracle or its affiliates under a separate agreement.

8. Relationship Between the Parties. The relationship between you and us is that of licensee/licensor.Neither party will represent that it has any authority to assume or create any obligation, express orimplied, on behalf of the other party, nor to represent the other party as agent, employee, franchisee,or in any other capacity. Nothing in this Agreement shall be construed to limit either party's right toindependently develop or distribute programs that are functionally similar to the other party"sproducts, so long as proprietary information of the other party is not included in such programs.

9. Entire Agreement. You agree that this Agreement is the complete Agreement for the Oracle Linuxprograms and the Additional Oracle Linux programs, and this Agreement supersedes all prior orcontemporaneous Agreements or representations. If any term of this Agreement is found to be invalidor unenforceable, the remaining provisions will remain effective. Neither the Uniform ComputerInformation Transactions Act nor the United Nations Convention on the International Sale of Goodsapplies to this Agreement.

You can find a copy of the GNU General Public License version 2.0 in the "copying" or "license" fileincluded with the Oracle Linux programs or here: http://oss.oracle.com/licenses/GPL-2.

OFFER TO PROVIDE SOURCE CODE

For software that you receive from Oracle in binary form that is licensed under an open source licensethat gives you the right to receive the source code for that binary, you can obtain a copy of theapplicable source code from https://oss.oracle.com/sources/ or http://www.oracle.com/goto/opensourcecode. Alternatively, if the source code for the technology was not provided to you with thebinary, you can also receive a copy of the source code on physical media by submitting a writtenrequest to:

Oracle America, Inc.

Attn: Associate General Counsel

Development and Engineering Legal

500 Oracle Parkway, 10th Floor

Redwood Shores, CA 94065

Or, you may send an email to Oracle using the form linked from http://www.oracle.com/goto/opensourcecode. Your written or emailed request should include:

* The name of the component or binary file(s) for which you are requesting the source code

* The name and version number of the Oracle product

* The date you received the Oracle product

* Your name

* Your company name (if applicable)

* Your return mailing address and email

* A telephone number in the event we need to reach you.

We may charge you a fee to cover the cost of physical media and processing. Your request must besent (i) within three (3) years of the date you received the Oracle product that included thecomponent or binary file(s) that are the subject of your request, or (ii) in the case of code licensedunder the GPL v3, for as long as Oracle offers spare parts or customer support for that product modelor version.

Last updated 29 September 2015

OpenJDK7© 2007, 2014 Oracle and/or its affiliates

http://openjdk.java.net/install


http://oss.oracle.com/licenses/GPL-2


http://www.oracle.com/goto/opensourcecode




http://openjdk.java.net/install

GNU General Public License (GPL) Version 2.0: GNU General Public License(GPL) Version 2.0 on page 145

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/

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


http://www.openssl.org/

* 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 IFADVISED* 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 BUSINESS


INTERRUPTION)* 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.

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.


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

expat license

Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd andClark Cooper Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006 Expatmaintainers. Permission is hereby granted, free of charge, to any personobtaining a copy of this software and associated documentation files (the"Software"), to deal in the Software without restriction, including withoutlimitation the rights to use, copy, modify, merge, publish, distribute,sublicense, and/or sell copies of the Software, and to permit persons towhom the Software is furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in allcopies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHTHOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISINGFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OROTHER DEALINGS IN THE SOFTWARE.

FreeType license

The FreeType Project LICENSE

2006-Jan-27 Copyright 1996-2002, 2006 by David Turner, Robert Wilhelm,and Werner Lemberg

Introduction

The FreeType Project is distributed in several archive packages; some of themmay contain, in addition to the FreeType font engine, various tools andcontributions which rely on, or relate to, the FreeType Project. This licenseapplies to all files found in such packages, and which do not fall under theirown explicit license. The license affects thus the FreeType font engine, thetest programs, documentation and makefiles, at the very least. This licensewas inspired by the BSD, Artistic, and IJG (Independent JPEG Group)licenses, which all encourage inclusion and use of free software in commercialand freeware products alike. As a consequence, its main points are that:• We don't promise that this software works. However, we will be interested

in any kind of bug reports. (`as is' distribution)• You can use this software for whatever you want, in parts or full form,

without having to pay us. (`royalty-free' usage)• You may not pretend that you wrote this software. If you use it, or only

parts of it, in a program, you must acknowledge somewhere in yourdocumentation that you have used the FreeType code. (`credits')

We specifically permit and encourage the inclusion of this software, with orwithout modifications, in commercial products. We disclaim all warranties


covering The FreeType Project and assume no liability related to The FreeTypeProject.

Finally, many people asked us for a preferred form for a credit/disclaimer touse in compliance with this license. We thus encourage you to use thefollowing text:Portions of this software are copyright (c) <year> The FreeTypeProject (www.freetype.org). All rights reserved.Please replace <year> with the value from the FreeType version you actuallyuse.

Legal Terms

0. Definitions

Throughout this license, the terms `package', `FreeType Project', and`FreeType archive' refer to the set of files originally distributed by the authors(David Turner, Robert Wilhelm, and Werner Lemberg) as the `FreeTypeProject', be they named as alpha, beta or final release.

`You' refers to the licensee, or person using the project, where ùsing' is ageneric term including compiling the project's source code as well as linking itto form a `program' or èxecutable'. This program is referred to as àprogram using the FreeType engine'.

This license applies to all files distributed in the original FreeType Project,including all source code, binaries and documentation, unless otherwisestated in the file in its original, unmodified form as distributed in the originalarchive. If you are unsure whether or not a particular file is covered by thislicense, you must contact us to verify this.

The FreeType Project is copyright (C) 1996-2000 by David Turner, RobertWilhelm, and Werner Lemberg. All rights reserved except as specified below.

1. No Warranty

THE FREETYPE PROJECT IS PROVIDED ÀS IS' WITHOUT WARRANTY OF ANYKIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE. IN NO EVENT WILL ANY OF THE AUTHORS OR COPYRIGHTHOLDERS BE LIABLE FOR ANY DAMAGES CAUSED BY THE USE OR THEINABILITY TO USE, OF THE FREETYPE PROJECT.

2. Redistribution

This license grants a worldwide, royalty-free, perpetual and irrevocable rightand license to use, execute, perform, compile, display, copy, create derivativeworks of, distribute and sublicense the FreeType Project (in both source andobject code forms) and derivative works thereof for any purpose; and toauthorize others to exercise some or all of the rights granted herein, subjectto the following conditions:


• Redistribution of source code must retain this license file (`FTL.TXT')unaltered; any additions, deletions or changes to the original files must beclearly indicated in accompanying documentation. The copyright notices ofthe unaltered, original files must be preserved in all copies of source files.

• Redistribution in binary form must provide a disclaimer that states that thesoftware is based in part of the work of the FreeType Team, in thedistribution documentation. We also encourage you to put an URL to theFreeType web page in your documentation, though this isn't mandatory.

These conditions apply to any software derived from or based on theFreeType Project, not just the unmodified files. If you use our work, you mustacknowledge us. However, no fee need be paid to us.

3. Advertising

Neither the FreeType authors and contributors nor you shall use the name ofthe other for commercial, advertising, or promotional purposes withoutspecific prior written permission.

We suggest, but do not require, that you use one or more of the followingphrases to refer to this software in your documentation or advertisingmaterials: `FreeType Project', `FreeType Engine', `FreeType library', or`FreeType Distribution'.

As you have not signed this license, you are not required to accept it.However, as the FreeType Project is copyrighted material, only this license, oranother one contracted with the authors, grants you the right to use,distribute, and modify it. Therefore, by using, distributing, or modifying theFreeType Project, you indicate that you understand and accept all the termsof this license.

4. Contacts

There are two mailing lists related to FreeType:

[email protected]

Discusses general use and applications of FreeType, as well as future andwanted additions to the library and distribution. If you are looking forsupport, start in this list if you haven't found anything to help you in thedocumentation.

[email protected]

Discusses bugs, as well as engine internals, design issues, specific licenses,porting, etc. Our home page can be found at http://www.freetype.org

memcached License

Copyright (c) 2003, Danga Interactive, Inc. All rights reserved. Redistributionand use in source and binary forms, with or without modification, arepermitted provided that the following conditions are met: Redistributions of


source code must retain the above copyright notice, this list of conditions andthe following disclaimer. Redistributions in binary form must reproduce theabove copyright notice, this list of conditions and the following disclaimer inthe documentation and/or other materials provided with the distribution.Neither the name of the Danga Interactive nor the names of its contributorsmay be used to endorse or promote products derived from this softwarewithout specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ANDCONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 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 IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Openldap License

The OpenLDAP Public License Version 2.8, 17 August 2003

Redistribution and use of this software and associated documentation("Software"), with or without modification, are permitted provided that thefollowing conditions are met: 1. Redistributions in source form must retaincopyright statements and notices, 2. Redistributions in binary form mustreproduce applicable copyright statements and notices, this list of conditions,and the following disclaimer in the documentation and/or other materialsprovided with the distribution, and 3. Redistributions must contain a verbatimcopy of this document. The OpenLDAP Foundation may revise this licensefrom time to time. Each revision is distinguished by a version number. Youmay use this Software under terms of this license revision or under the termsof any subsequent revision of the license.

THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND ITSCONTRIBUTORS ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE OPENLDAP FOUNDATION, ITSCONTRIBUTORS, OR THE AUTHOR(S) OR OWNER(S) OF THE SOFTWARE BELIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR


TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.

The names of the authors and copyright holders must not be used inadvertising or otherwise to promote the sale, use or other dealing in thisSoftware without specific, written prior permission. Title to copyright in thisSoftware shall at all times remain with copyright holders. OpenLDAP is aregistered trademark of the OpenLDAP Foundation. Copyright 1999-2003 TheOpenLDAP Foundation, Redwood City, California, USA. All Rights Reserved.Permission to copy and distribute verbatim copies of this document isgranted.

Openssl License

LICENSE ISSUES

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of theOpenSSL License and the original SSLeay license apply to the toolkit. Seebelow for the actual license texts. Actually both licenses are BSD-style OpenSource licenses. In case of any license issues related to OpenSSL pleasecontact [email protected].

OpenSSL License

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

Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, thislist 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 documentationand/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software mustdisplay the following acknowledgment: "This product includes softwaredeveloped 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 used toendorse or promote products derived from this software without prior writtenpermission. 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 theOpenSSL Project. 6. Redistributions of any form whatsoever must retain thefollowing acknowledgment: "This product includes software developed by theOpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"


THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS'' AND ANYEXPRESSED 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 OpenSSLPROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODSOR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OFTHIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

SSLeay License

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 withNetscapes SSL. This library is free for commercial and non-commercial use aslong as the following conditions are aheared to. The following conditionsapply 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 thisdistribution is covered by the same copyright terms except that the holder isTim Hudson ([email protected]). Copyright remains Eric Young's, and assuch any Copyright notices in the code are not to be removed. If this packageis used in a product, Eric Young should be given attribution as the author ofthe parts of the library used. This can be in the form of a textual message atprogram startup or in documentation (online or textual) provided with thepackage. Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list ofconditions and the following disclaimer.


3. All advertising materials mentioning features or use of this software mustdisplay the following acknowledgement: "This product includes cryptographicsoftware written by Eric Young ([email protected])" The word'cryptographic' can be left out if the routines from the library being used arenot cryptographic related :-).


4. If you include any Windows specific code (or a derivative thereof) from theapps directory (application code) you must include an acknowledgement:"This product includes software written by Tim Hudson ([email protected])"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 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 IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publically available version orderivative of this code cannot be changed. i.e. this code cannot simply becopied and put under another distribution licence [including the GNU PublicLicence.]

proj License

Copyright (c) 2000, Frank Warmerdam Permission is hereby granted, free ofcharge, to any person obtaining a copy of this software and associateddocumentation files (the "Software"), to deal in the Software withoutrestriction, including without limitation the rights to use, copy, modify,merge, publish, distribute, sublicense, and/or sell copies of the Software, andto permit persons to whom the Software is furnished to do so, subject to thefollowing conditions: The above copyright notice and this permission noticeshall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHTHOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISINGFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OROTHER DEALINGS IN THE SOFTWARE.

zlib License

zlib.h -- interface of the 'zlib' general purpose compression library version1.2.7, May 2nd, 2012 Copyright (C) 1995-2012 Jean-loup Gailly and MarkAdler.

This software is provided 'as-is', without any express or implied warranty. Inno event will the authors be held liable for any damages arising from the use


of this software. Permission is granted to anyone to use this software for anypurpose, including commercial applications, and to alter it and redistribute itfreely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must notclaim that you wrote the original software. If you use this software in aproduct, an acknowledgment in the product documentation would beappreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not bemisrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.Jean-loup Gailly Mark Adler [email protected] [email protected]

gdal, libxm2, libxslt License

Copyright (C) 1996 X Consortium

Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rights touse, copy, modify, merge, publish, distribute, sublicense, and/or sell copies ofthe Software, and to permit persons to whom the Software is furnished to doso, subject to the following conditions:

The above copyright notice and this permission notice shall be included in allcopies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE X CONSORTIUM BE LIABLEFOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTIONOF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR INCONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE.

Except as contained in this notice, the name of the X Consortium shall not beused in advertising or otherwise to promote the sale, use or other dealings inthis Software without prior written authorization from the X Consortium. XWindow System is a trademark of X Consortium, Inc.

Retrieved from "http://directory.fsf.org/wiki/License:X11" Permission isgranted to copy, distribute and/or modify this document under the terms ofthe GNU Free Documentation License, Version 1.3 or any later versionpublished by the Free Software Foundation; with no Invariant Sections, noFront-Cover Texts, and no Back-Cover Texts. A copy of the license is includedin the page GNU Free Documentation License. The copyright and licensenotices on this page only apply to the text on this page. Any software


described in this text has its own copyright notice and license, which canusually be found in the distribution itself.

geos, gettext, libgcrypt, libgpg_error, libiconv, pthreads, termcap, unixODBC,uuid License

GNU LESSER GENERAL PUBLIC LICENSE

Version 2.1, February 1999 Copyright (C) 1991, 1999 Free SoftwareFoundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USAEveryone is permitted to copy and distribute verbatim copies of this licensedocument, but changing it is not allowed. [This is the first released version ofthe Lesser GPL. It also counts as the successor of the GNU Library PublicLicense, version 2, hence the version number 2.1.]

Preamble

The licenses for most software are designed to take away your freedom toshare and change it. By contrast, the GNU General Public Licenses areintended to guarantee your freedom to share and change free software--tomake sure the software is free for all its users.

This license, the Lesser General Public License, applies to some speciallydesignated software packages--typically libraries--of the Free SoftwareFoundation and other authors who decide to use it. You can use it too, but wesuggest you first think carefully about whether this license or the ordinaryGeneral Public License is the better strategy to use in any particular case,based on the explanations below.

When we speak of free software, we are referring to freedom of use, notprice. Our General Public Licenses are designed to make sure that you havethe freedom to distribute copies of free software (and charge for this serviceif you wish); that you receive source code or can get it if you want it; thatyou can change the software and use pieces of it in new free programs; andthat you are informed that you can do these things.

To protect your rights, we need to make restrictions that forbid distributors todeny you these rights or to ask you to surrender these rights. Theserestrictions translate to certain responsibilities for you if you distribute copiesof the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for afee, you must give the recipients all the rights that we gave you. You mustmake sure that they, too, receive or can get the source code. If you link othercode with the library, you must provide complete object files to therecipients, so that they can relink them with the library after making changesto the library and recompiling it. And you must show them these terms sothey know their rights.


We protect your rights with a two-step method: (1) we copyright the library,and (2) we offer you this license, which gives you legal permission to copy,distribute and/or modify the library.

To protect each distributor, we want to make it very clear that there is nowarranty for the free library. Also, if the library is modified by someone elseand passed on, the recipients should know that what they have is not theoriginal version, so that the original author's reputation will not be affectedby problems that might be introduced by others.

Finally, software patents pose a constant threat to the existence of any freeprogram. We wish to make sure that a company cannot effectively restrictthe users of a free program by obtaining a restrictive license from a patentholder. Therefore, we insist that any patent license obtained for a version ofthe library must be consistent with the full freedom of use specified in thislicense.

Most GNU software, including some libraries, is covered by the ordinary GNUGeneral Public License. This license, the GNU Lesser General Public License,applies to certain designated libraries, and is quite different from the ordinaryGeneral Public License. We use this license for certain libraries in order topermit linking those libraries into non-free programs.

When a program is linked with a library, whether statically or using a sharedlibrary, the combination of the two is legally speaking a combined work, aderivative of the original library. The ordinary General Public Licensetherefore permits such linking only if the entire combination fits its criteria offreedom. The Lesser General Public License permits more lax criteria forlinking other code with the library.

We call this license the "Lesser" General Public License because it does Lessto protect the user's freedom than the ordinary General Public License. It alsoprovides other free software developers Less of an advantage over competingnon-free programs. These disadvantages are the reason we use the ordinaryGeneral Public License for many libraries. However, the Lesser licenseprovides advantages in certain special circumstances.

For example, on rare occasions, there may be a special need to encouragethe widest possible use of a certain library, so that it becomes a de-factostandard. To achieve this, non-free programs must be allowed to use thelibrary. A more frequent case is that a free library does the same job aswidely used non-free libraries. In this case, there is little to gain by limitingthe free library to free software only, so we use the Lesser General PublicLicense.

In other cases, permission to use a particular library in non-free programsenables a greater number of people to use a large body of free software. Forexample, permission to use the GNU C Library in non-free programs enablesmany more people to use the whole GNU operating system, as well as itsvariant, the GNU/Linux operating system.


Although the Lesser General Public License is Less protective of the users'freedom, it does ensure that the user of a program that is linked with theLibrary has the freedom and the wherewithal to run that program using amodified version of the Library. The precise terms and conditions for copying,distribution and modification follow. Pay close attention to the differencebetween a "work based on the library" and a "work that uses the library". Theformer contains code derived from the library, whereas the latter must becombined with the library in order to run.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION ANDMODIFICATION

0. This License Agreement applies to any software library or other programwhich contains a notice placed by the copyright holder or other authorizedparty saying it may be distributed under the terms of this Lesser GeneralPublic License (also called "this License"). Each licensee is addressed as"you".

A "library" means a collection of software functions and/or data prepared soas to be conveniently linked with application programs (which use some ofthose functions and data) to form executables.

The "Library", below, refers to any such software library or work which hasbeen distributed under these terms. A "work based on the Library" meanseither the Library or any derivative work under copyright law: that is to say, awork containing the Library or a portion of it, either verbatim or withmodifications and/or translated straightforwardly into another language.(Hereinafter, translation is included without limitation in the term"modification".)

"Source code" for a work means the preferred form of the work for makingmodifications to it. For a library, complete source code means all the sourcecode for all modules it contains, plus any associated interface definition files,plus the scripts used to control compilation and installation of the library.

Activities other than copying, distribution and modification are not covered bythis License; they are outside its scope. The act of running a program usingthe Library is not restricted, and output from such a program is covered onlyif its contents constitute a work based on the Library (independent of the useof the Library in a tool for writing it). Whether that is true depends on whatthe Library does and what the program that uses the Library does.

1. You may copy and distribute verbatim copies of the Library's completesource code as you receive it, in any medium, provided that youconspicuously and appropriately publish on each copy an appropriatecopyright notice and disclaimer of warranty; keep intact all the notices thatrefer to this License and to the absence of any warranty; and distribute acopy of this License along with the Library.


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 Library or any portion of it,thus forming a work based on the Library, and copy and distribute suchmodifications or work under the terms of Section 1 above, provided that youalso meet all of these conditions:

a) The modified work must itself be a software library.

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

c) You must cause the whole of the work to be licensed at no charge to allthird parties under the terms of this License.

d) If a facility in the modified Library refers to a function or a table of data tobe supplied by an application program that uses the facility, other than as anargument passed when the facility is invoked, then you must make a goodfaith effort to ensure that, in the event an application does not supply suchfunction or table, the facility still operates, and performs whatever part of itspurpose remains meaningful. (For example, a function in a library to computesquare roots has a purpose that is entirely well-defined independent of theapplication. Therefore, Subsection 2d requires that any application-suppliedfunction or table used by this function must be optional: if the applicationdoes not supply it, the square root function must still compute square roots.)

These requirements apply to the modified work as a whole. If identifiablesections of that work are not derived from the Library, and can be reasonablyconsidered independent and separate works in themselves, then this License,and its terms, do not apply to those sections when you distribute them asseparate works. But when you distribute the same sections as part of a wholewhich is a work based on the Library, the distribution of the whole must beon the terms of this License, whose permissions for other licensees extend tothe entire whole, and thus to each and 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 the Library.

In addition, mere aggregation of another work not based on the Library withthe Library (or with a work based on the Library) on a volume of a storage ordistribution medium does not bring the other work under the scope of thisLicense.

3. You may opt to apply the terms of the ordinary GNU General Public Licenseinstead of this License to a given copy of the Library. To do this, you mustalter all the notices that refer to this License, so that they refer to theordinary GNU General Public License, version 2, instead of to this License. (Ifa newer version than version 2 of the ordinary GNU General Public License


has appeared, then you can specify that version instead if you wish.) Do notmake any other change in these notices.

Once this change is made in a given copy, it is irreversible for that copy, sothe ordinary GNU General Public License applies to all subsequent copies andderivative works made from that copy.

This option is useful when you wish to copy part of the code of the Libraryinto a program that is not a library.

4. You may copy and distribute the Library (or a portion or derivative of it,under Section 2) in object code or executable form under the terms ofSections 1 and 2 above provided that you accompany it with the completecorresponding machine-readable source code, which must be distributedunder the terms of Sections 1 and 2 above on a medium customarily used forsoftware interchange.

If distribution of object code is made by offering access to copy from adesignated place, then offering equivalent access to copy the source codefrom the same place satisfies the requirement to distribute the source code,even though third parties are not compelled to copy the source along withthe object code.

5. A program that contains no derivative of any portion of the Library, but isdesigned to work with the Library by being compiled or linked with it, iscalled a "work that uses the Library". Such a work, in isolation, is not aderivative work of the Library, and therefore falls outside the scope of thisLicense.

However, linking a "work that uses the Library" with the Library creates anexecutable that is a derivative of the Library (because it contains portions ofthe Library), rather than a "work that uses the library". The executable istherefore covered by this License. Section 6 states terms for distribution ofsuch executables.

When a "work that uses the Library" uses material from a header file that ispart of the Library, the object code for the work may be a derivative work ofthe Library even though the source code is not. Whether this is true isespecially significant if the work can be linked without the Library, or if thework is itself a library. The threshold for this to be true is not preciselydefined by law.

If such an object file uses only numerical parameters, data structure layoutsand accessors, and small macros and small inline functions (ten lines or lessin length), then the use of the object file is unrestricted, regardless ofwhether it is legally a derivative work. (Executables containing this objectcode plus portions of the Library will still fall under Section 6.)

Otherwise, if the work is a derivative of the Library, you may distribute theobject code for the work under the terms of Section 6. Any executables


containing that work also fall under Section 6, whether or not they are linkeddirectly with the Library itself.

6. As an exception to the Sections above, you may also combine or link a"work that uses the Library" with the Library to produce a work containingportions of the Library, and distribute that work under terms of your choice,provided that the terms permit modification of the work for the customer'sown use and reverse engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the Library isused in it and that the Library and its use are covered by this License. Youmust supply a copy of this License. If the work during execution displayscopyright notices, you must include the copyright notice for the Libraryamong them, as well as a reference directing the user to the copy of thisLicense. Also, you must do one of these things:

a) Accompany the work with the complete corresponding machine-readablesource code for the Library including whatever changes were used in thework (which must be distributed under Sections 1 and 2 above); and, if thework is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, sothat the user can modify the Library and then relink to produce a modifiedexecutable containing the modified Library. (It is understood that the userwho changes the contents of definitions files in the Library will not necessarilybe able to recompile the application to use the modified definitions.)

b) Use a suitable shared library mechanism for linking with the Library. Asuitable mechanism is one that (1) uses at run time a copy of the libraryalready present on the user's computer system, rather than copying libraryfunctions into the executable, and (2) will operate properly with a modifiedversion of the library, if the user installs one, as long as the modified versionis interface-compatible with the version that the work was made with.

c) Accompany the work with a written offer, valid for at least three years, togive the same user the materials specified in Subsection 6a, above, for acharge no more than the cost of performing this distribution.

d) If distribution of the work is made by offering access to copy from adesignated place, offer equivalent access to copy the above specifiedmaterials from the same place.

e) Verify that the user has already received a copy of these materials or thatyou have already sent this user a copy.

For an executable, the required form of the "work that uses the Library" mustinclude any data and utility programs needed for reproducing the executablefrom it. However, as a special exception, the materials to be distributed neednot include anything that is normally distributed (in either source or binaryform) with the major components (compiler, kernel, and so on) of the


operating system on which the executable runs, unless that component itselfaccompanies the executable.

It may happen that this requirement contradicts the license restrictions ofother proprietary libraries that do not normally accompany the operatingsystem. Such a contradiction means you cannot use both them and theLibrary together in an executable that you distribute.

7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered bythis License, and distribute such a combined library, provided that theseparate distribution of the work based on the Library and of the other libraryfacilities is otherwise permitted, and provided that you do these two things:

a) Accompany the combined library with a copy of the same work based onthe Library, uncombined with any other library facilities. This must bedistributed under the terms of the Sections above.

b) Give prominent notice with the combined library of the fact that part of itis a work based on the Library, and explaining where to find theaccompanying uncombined form of the same work.

8. You may not copy, modify, sublicense, link with, or distribute the Libraryexcept as expressly provided under this License. Any attempt otherwise tocopy, modify, sublicense, link with, or distribute the Library is void, and willautomatically terminate your rights under this License. However, parties whohave received copies, or rights, from you under this License will not havetheir licenses terminated so long as such parties remain in full compliance.

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

10. Each time you redistribute the Library (or any work based on theLibrary), the recipient automatically receives a license from the originallicensor to copy, distribute, link with or modify the Library subject to theseterms and conditions. You may not impose any further restrictions on therecipients' exercise of the rights granted herein. You are not responsible forenforcing compliance by third parties with this License.

11. 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 pertinent


obligations, then as a consequence you may not distribute the Library at all.For example, if a patent license would not permit royalty-free redistribution ofthe Library by all those who receive copies directly or indirectly through you,then the only way you could satisfy both it and this License would be torefrain entirely from distribution of the Library.

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.

12. If the distribution and/or use of the Library is restricted in certaincountries either by patents or by copyrighted interfaces, the originalcopyright holder who places the Library 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.

13. The Free Software Foundation may publish revised and/or new versionsof the Lesser General Public License from time to time. Such new versionswill be similar in spirit to the present version, but may differ in detail toaddress new problems or concerns. Each version is given a distinguishingversion number. If the Library specifies a version number of this Licensewhich applies to it and "any later version", you have the option of followingthe terms and conditions either of that version or of any later versionpublished by the Free Software Foundation. If the Library does not specify alicense version number, you may choose any version ever published by theFree Software Foundation.

14. If you wish to incorporate parts of the Library into other free programswhose distribution conditions are incompatible with these, write to the authorto ask for permission. 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

15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NOWARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLELAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHTHOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THEQUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THELIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARYSERVICING, REPAIR OR CORRECTION. 16. IN NO EVENT UNLESS REQUIREDBY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHTHOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTETHE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIALDAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY(INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEINGRENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIESOR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE),EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THEPOSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Libraries

If you develop a new library, and you want it to be of the greatest possibleuse to the public, we recommend making it free software that everyone canredistribute and change. You can do so by permitting redistribution underthese terms (or, alternatively, under the terms of the ordinary General PublicLicense).

To apply these terms, attach the following notices to the library. It is safest toattach them to the start of each source file to most effectively convey theexclusion of warranty; and each file should have at least the "copyright" lineand a pointer to where the full notice is found.one line to give the library's name and a brief idea of what it does.Copyright (C) year name of author

This library is free software; you can redistribute it and/ormodify it under the terms of the GNU Lesser General PublicLicense as published by the Free Software Foundation; eitherversion 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful,but WITHOUT ANY WARRANTY; without even the implied warranty ofMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNULesser General Public License for more details.


You should have received a copy of the GNU Lesser General PublicLicense along with this library; if not, write to the Free SoftwareFoundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USAAlso add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or yourschool, if any, to sign a "copyright disclaimer" for the library, if necessary.Here is a sample; alter the names:Yoyodyne, Inc., hereby disclaims all copyright interest inthe library `Frob' (a library for tweaking knobs) writtenby James Random Hacker.

signature of Ty Coon, 1 April 1990Ty Coon, President of ViceThat's all there is to it!

libedit, libevent, libmemcached, tiff License

Libevent is available for use under the following license, commonly known asthe 3-clause (or "modified") BSD license:

Copyright (c) 2000-2007 Niels Provos <[email protected]> Copyright(c) 2007-2010 Niels Provos and Nick Mathewson Redistribution and use insource and binary forms, with or without modification, are permittedprovided that the following conditions are met:



3. The name of the author may not be used to endorse or promote productsderived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLEFOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, ORTORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.


Portions of Libevent are based on works by others, also made available bythem under the three-clause BSD license above. The copyright notices areavailable in the corresponding source files; the license is as above. Here's alist: log.c: Copyright (c) 2000 Dug Song <[email protected]> Copyright(c) 1993 The Regents of the University of California. strlcpy.c: Copyright (c)1998 Todd C. Miller <[email protected]> win32select.c: Copyright(c) 2003 Michael A. Davis <[email protected]> evport.c: Copyright (c)2007 Sun Microsystems ht-internal.h: Copyright (c) 2002 Christopher Clarkminheap-internal.h: Copyright (c) 2006 Maxim Yegorushkin<[email protected]>

The arc4module is available under the following, sometimes called the"OpenBSD" license: Copyright (c) 1996, David Mazieres <[email protected]>Copyright (c) 2008, Damien Miller <[email protected]> Permission to use,copy, modify, and distribute this software for any purpose with or without feeis hereby granted, provided that the above copyright notice and thispermission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALLWARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THEAUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, ORCONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTINGFROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OFCONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OFOR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

wxwidget License

wxWidgets is currently licensed under the "wxWindows Licence" pendingapproval of the "wxWidgets Licence" which will be identical apart from thename. The wxWindows Licence is essentially the L-GPL (Library GeneralPublic Licence), with an exception stating that derived works in binary formmay be distributed on the user's own terms. This is a solution that satisfiesthose who wish to produce GPL'ed software using wxWidgets, and also thoseproducing proprietary software. wxWindows Library Licence, Version 3.1

Copyright (C) 1998-2005 Julian Smart, Robert Roebling et al Everyone ispermitted to copy and distribute verbatim copies of this licence document,but changing it is not allowed. WXWINDOWS LIBRARY LICENCE TERMS ANDCONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION This libraryis free software; you can redistribute it and/or modify it under the terms ofthe GNU Library General Public Licence as published by the Free SoftwareFoundation; either version 2 of the Licence, or (at your option) any laterversion. This library is distributed in the hope that it will be useful, butWITHOUT ANY WARRANTY; without even the implied warranty ofMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNULibrary General Public Licence for more details. You should have received acopy of the GNU Library General Public Licence along with this software,


usually in a file named COPYING.LIB. If not, write to the Free SoftwareFoundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.

EXCEPTION NOTICE

1. As a special exception, the copyright holders of this library give permissionfor additional uses of the text contained in this release of the library aslicenced under the wxWindows Library Licence, applying either version 3.1 ofthe Licence, or (at your option) any later version of the Licence as publishedby the copyright holders of version 3.1 of the Licence document.

2. The exception is that you may use, copy, link, modify and distribute underyour own terms, binary object code versions of works based on the Library.

3. If you copy code from files distributed under the terms of the GNU GeneralPublic Licence or the GNU Library General Public Licence into a copy of thislibrary, as this licence permits, the exception does not apply to the code thatyou add in this way. To avoid misleading anyone as to the status of suchmodified files, you must delete this exception notice from such code and/oradjust the licensing conditions notice accordingly.

4. If you write modifications of your own for this library, it is your choicewhether to permit this exception to apply to your modifications. If you do notwish that, you must delete the exception notice from such code and/or adjustthe licensing conditions notice accordingly.

ncurses License

Copyright (c) 2006 Free Software Foundation, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rights touse, copy, modify, merge, publish, distribute, distribute with modifications,sublicense, and/or sell copies of the Software, and to permit persons towhom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in allcopies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. INNO EVENT SHALL THE ABOVE COPYRIGHT HOLDERSBE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN ANACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF ORIN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE.


Except as contained in this notice, the name(s) of the above copyrightholders shall not be used in advertising or otherwise to promote the sale, useor other dealings in this Software without prior written authorization.

$Id: AUTHORS,v 1.2 2006/10/28 21:44:52 tom Exp $These are the principalauthors/contributors of ncurses since 1.9.9e, in decreasing order of theircontribution: TD Thomas E. Dickey JPF Juergen Pfeifer ESR Eric S RaymondAVL Alexander V Lukyanov PB Philippe Blain SV Sven Verdoolaege

krb5 License

Copyright (C) 1985-2012 by the Massachusetts Institute of Technology. Allrights reserved. Export of software employing encryption from the UnitedStates of America may require a specific license from the United StatesGovernment. It is the responsibility of any person or organizationcontemplating export to obtain such a license before exporting.

WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distributethis software for any purpose and without fee is hereby granted, providedthat the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supportingdocumentation, and that the name of M.I.T. not be used in advertising orpublicity pertaining to distribution of the software without specific, writtenprior permission. Furthermore if you modify this software you must label yoursoftware as modified software and not distribute it in such a fashion that itmight be confused with the original MIT software. M.I.T. makes norepresentations about the suitability of this software for any purpose. It isprovided "as is" without express or implied warranty. Documentationcomponents of this software distribution are licensed under a CreativeCommons Attribution-ShareAlike 3.0 Unported License. (`http://creativecommons.org/licenses/by-sa/3.0/') Individual source code files arecopyright MIT, Cygnus Support, Novell, OpenVision Technologies, Oracle, RedHat, Sun Microsystems, FundsXpress, and others. Project Athena, Athena,Athena MUSE, Discuss, Hesiod, Kerberos, Moira, and Zephyr are trademarksof the Massachusetts Institute of Technology (MIT). No commercial use ofthese trademarks may be made without prior written permission of MIT."Commercial use" means use of a name in a product or other for-profitmanner. It does NOT prevent a commercial firm from referring to the MITtrademarks in order to convey information (although in doing so, recognitionof their trademark status should be given).

Curl License

COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1996 - 2011, DanielStenberg, <[email protected]>. All rights reserved. Permission to use, copy,modify, and distribute this software for any purpose with or without fee ishereby granted, provided that the above copyright notice and this permissionnotice appear in all copies.


THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGESOR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OROTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THESOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall notbe used in advertising or otherwise to promote the sale, use or other dealingsin this Software without prior written authorization of the copyright holder.

cyrus-sasl License

CMU libsasl Tim Martin Rob Earhart Rob Siemborski

Copyright (c) 1998-2003 Carnegie Mellon University. All rights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:



3. The name "Carnegie Mellon University" must not be used to endorse orpromote products derived from this software without prior writtenpermission. For permission or any other legal details, please contact Office ofTechnology Transfer Carnegie Mellon University 5000 Forbes AvenuePittsburgh, PA 15213-3890 (412) 268-4387, fax: (412) 268-7395 [email protected]

4. Redistributions of any form whatsoever must retain the followingacknowledgment: "This product includes software developed by ComputingServices at Carnegie Mellon University (http://www.cmu.edu/computing/).

CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITHREGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLONUNIVERSITY BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIALDAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OROTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THEUSE OR PERFORMANCE OF THIS SOFTWARE.


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.

"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.


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

"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 bycombination 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 theterms 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 A


PARTICULAR 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.


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 alsorecommend 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.

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 recipients


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

to 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 andappropriately 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 pertinent


obligations, 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.


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 exclusionof 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 thelibrary. 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/>.#

VMware vSphere Software Development Kit LicenseVMware vSphere Software Development Kit License Agreement

VMware, Inc. (“VMware”) provides the VMware vSphere SoftwareDevelopment Kit (collectively the “Software”) to you subject to thefollowing terms and conditions. By downloading, installing, or usingthe Software, you (the individual or legal entity) agree to be boundby the terms of this license agreement (the “Agreement”). If youdisagree with any of the following terms, then do not use theSoftware.

1. The Software contains a variety of materials, interface definitions,documentation, sample utility applications and sample code regardingprogramming interfaces to one or more VMware products that are referencedin such materials (the referenced products, “VMware Products”). ThisSoftware is intended to be used to develop software that interacts with theVMware Products.

2. Use Rights: Subject to the restrictions below, you may download andmake a reasonable number of copies of the Software for your use solely forthe purpose of creating software that communicates with VMware Products(your software, “Developer Software”). Some code may be designated as“distributable code” and/or “modifiable code” at http://www.vmware.com/go/vwssdk-redistribution-info. You may use and merge all or portions of the“distributable code” with your Developer Software. Any merged portion ofany “distributable code” is subject to this Agreement. Additionally, you maymodify or create derivative works of all or portions of the “modifiable code.”You are permitted to re-distribute the “distributable code” and the modifiedor derivative works of the “modifiable code” only as part of your DeveloperSoftware for non-commercial or commercial use; provided that you shall onlydistribute such code subject to a license agreement that protects VMware’sand its licensors’ interests consistent with the terms contained in thisAgreement. Open source software components provided with the Softwareare licensed to you under the terms of the applicable license agreementsincluded with such open source software components. The open sourcesoftware licenses can be found in the open_source_licenses.txt file, othermaterials accompanying the Software, the documentation or correspondingsource files available at http://www.vmware.com/download/open_source.html.

3. Restrictions: You agree that you will not (1) use the Software to create,design or develop anything other than Developer Software; (2) make anymore copies of the Software than are reasonably necessary for the authorized


http://www.vmware.com/go/vwssdk-redistribution-info

http://www.vmware.com/go/vwssdk-redistribution-info

http://www.vmware.com/download/open_source.html

http://www.vmware.com/download/open_source.html

use and backup and archival purposes; (3) modify, create derivative worksof, reverse engineer, reverse compile, or disassemble the Software except asexpressly permitted in Section 2; (4) distribute, sell, lease, rent, lend, orsublicense any part of the Software to any third party except as expresslypermitted in Section 2; or (5) use the Software in any manner to (a)circumvent any technical restrictions of VMware Products or violate anyadditional licensing terms applicable to VMware Products that VMwareprovides through product documentation, email notification on the VMwarewebsite or in the terms of the End User License Agreements; (b) disable,remove, over-ride or modify the display of any VMware Product End UserLicense Agreements that the VMware Products present to the end customers;or (c) upload or otherwise transmit any material containing software virusesor other computer code, files or programs designed to interrupt, destroy, orlimit the functionality of any software or hardware.

The restrictions in this Section 3 shall not apply if and to the extent theycontradict mandatory local law (including, but not limited to, lawimplementing the EC Software Directive).

4. VMware retains ownership of the Software and all intellectual propertyrights embodied in the Software, including without limitation all copyrights,trade secrets and patents. You may not remove, delete or modify any ofVMware copyright statements in the Software. ALL RIGHTS NOT EXPRESSLYGRANTED HEREUNDER ARE RESERVED TO VMWARE.

5. You may not use VMware’s name, trademarks or service marks inconnection with your Developer Software in a way that suggests yourDeveloper Software is certified or endorsed by VMware.

6. You are not entitled under this Agreement to receive any VMware supportor subscription services for the Software or any other services from VMwarein connection with the Software. If you have purchased support and/orsubscription services for a VMware product, such support and/or subscriptionservices shall not apply to the Software or your use of the Software.

7. Term, Termination and Changes: This Agreement shall continue as longas you are in compliance with the terms specified herein or until otherwiseterminated. You or VMware each may terminate this Agreement for anyreason at any time. You agree, upon termination, to destroy all copies of theSoftware within your possession or control. The Confidential Information,Limitations of Warranties and Liability, and Indemnification sections set out inthis Agreement shall survive any termination or expiration of this Agreement.

8. Confidential Information: “Confidential Information” means anyinformation disclosed by VMware to you pursuant to this Agreement that ismarked “Confidential,” “Proprietary,” or in some similar manner and anyinformation which you knew or reasonably should have known to beconfidential. You shall treat as confidential all Confidential Information ofVMware and shall not use such Confidential Information except to exerciseyour rights or perform your obligations under this Agreement. You will protect


Confidential Information from unauthorized use, access, or disclosure in thesame manner as you protect your own confidential or proprietary informationof a similar nature but with no less than reasonable care. You shall notdisclose such Confidential Information to any third party during or after theterm of this Agreement. This paragraph will not apply to any ConfidentialInformation that: (a) was rightfully in your possession prior to receipt of suchConfidential Information from VMware; (b) is or becomes a matter of publicknowledge through no fault of you; (c) is rightfully received from a thirdparty without a duty of confidentiality; (d) is independently developed by youwithout breach of any confidentiality obligations; (e) is disclosed by you withVMware’s prior written approval; or (f) you are required to disclose byapplicable law or court order, provided that you notify VMware of suchrequired disclosure promptly in writing and cooperate with VMware in anylawful action to contest or limit the scope of such required disclosure. Youacknowledge that breach of this Section 8 will cause irreparable damage toVMware for which monetary damages will be an inadequate remedy.Accordingly, VMware will be entitled to seek and obtain injunctive and anyother relief (legal or equitable) to restrain any breach or anticipated breach ofthis Section 8.

9. Limitations of Warranties and Liability: THE SOFTWARE IS PROVIDED“AS IS” WITHOUT ANY WARRANTIES OF ANY KIND. TO THE MAXIMUMEXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ANY IMPLIEDWARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY IMPLIEDWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSEAND NON-INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENTWILL VMWARE BE LIABLE FOR ANY LOST PROFITS OR BUSINESSOPPORTUNITIES, LOSS OF USE, BUSINESS INTERRUPTION, LOSS OF DATA,OR ANY OTHER INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIALDAMAGES ARISING OUT OF THE SOFTWARE OR YOUR USE OF THESOFTWARE, UNDER ANY THEORY OF LIABILITY, WHETHER BASED INCONTRACT, TORT, NEGLIGENCE, PRODUCT LIABILITY, OR OTHERWISE.BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION ORLIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES,THE PRECEDING LIMITATION MAY NOT APPLY TO YOU.

VMWARE’S LIABILITY ARISING OUT OF THIS AGREEMENT AND THESOFTWARE PROVIDED HEREUNDER WILL NOT, IN ANY EVENT, EXCEED US$100.00.

THE FOREGOING LIMITATIONS SHALL APPLY TO THE MAXIMUM EXTENTPERMITTED BY APPLICABLE LAW, REGARDLESS OF WHETHER VMWARE HASBEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND REGARDLESSOF WHETHER ANY REMEDY FAILS OF ITS ESSENTIAL PURPOSE.

10. Indemnification: You agree to defend, indemnify and hold harmlessVMware, and any of its directors, officers, employees, affiliates and agents,


from and against any and all claims, losses, damages, liabilities and otherexpenses (including reasonable attorneys’ fees), arising from yourmodification of the “modifiable code,” the distribution or use of yourDeveloper Software by you or anyone else, and your breach of thisAgreement.

11. Export Control: You acknowledge that the Software is of United Statesorigin, is provided subject to the U.S. Export Administration Regulations, maybe subject to the export control laws of the applicable territory, and thatdiversion contrary to applicable export control laws is prohibited. Yourepresent, warrant and covenant that (1) you are not, and are not acting onbehalf of, (a) any person who is a citizen, national, or resident of, or who iscontrolled by the government of any country to which the United States hasprohibited export transactions; or (b) any person or entity listed on the U.S.Treasury Department list of Specially Designated Nationals and BlockedPersons, or the U.S. Commerce Department Denied Persons List or EntityList; and (2) you will not permit the Software to be used for any purposesprohibited by law, including, any prohibited development, design,manufacture or production of missiles or nuclear, chemical or biologicalweapons.

12. Data Privacy:

(a) Consent for Collection and Use of Technical Data. You agree that VMwaremay periodically collect, process and store technical and related informationabout your device, system, application, peripherals and your use of theSoftware, including without limitation: internet protocol address, hardwareidentification, operating system, application software, peripheral hardware,number of active plugins and software development kits, the successfulinstallation and launch of Software, and Software usage statistics(collectively, “Technical Data”). VMware will use Technical Data for internalstatistical and analytical purposes to facilitate support, invoicing or onlineservices, the provisioning of updates, and the development of VMwareproducts and services. VMware may transfer Technical Data to othercompanies in the VMware worldwide group of companies from time to time.

(b) Log Files. You acknowledge that correspondence and log files generatedin conjunction with a request for support services may contain sensitive,confidential or personal information. You are solely responsible for taking thesteps necessary to protect such data, including obfuscating the logs orotherwise guarding such information prior to sending it to VMware.

13. These terms are governed by the laws of the State of California and theUnited States of America without regard to conflict of laws principles. TheUnited Nations Convention for the International Sale of Goods shall not apply.You may not assign this Agreement. Any attempted assignment by you shallbe void. These terms constitute the entire agreement between you andVMware with respect to the Software and supersede all prior written or oralcommunications, understandings and agreements. Any waiver of these terms


must be in writing and signed by the waiving party to be effective. If anyprovision of these terms is found to be invalid or unenforceable, theremaining terms will continue to be valid and enforceable to the fullest extentpermitted by law.

VMware Tools License

PLEASE NOTE THAT THE TERMS OF THIS END USER LICENSEAGREEMENT SHALL GOVERN YOUR USE OF THE SOFTWARE,REGARDLESS OF ANY TERMS THAT MAY APPEAR DURING THEINSTALLATION OF THE SOFTWARE.

IMPORTANT-READ CAREFULLY: BY DOWNLOADING, INSTALLING, ORUSING THE SOFTWARE, YOU (THE INDIVIDUAL OR LEGAL ENTITY) AGREE TOBE BOUND BY THE TERMS OF THIS END USER LICENSE AGREEMENT(“EULA”). IF YOU DO NOT AGREE TO THE TERMS OF THIS EULA, YOU MUSTNOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND YOU MUST DELETEOR RETURN THE UNUSED SOFTWARE TO THE VENDOR FROM WHICH YOUACQUIRED IT WITHIN THIRTY (30) DAYS AND REQUEST A REFUND OF THELICENSE FEE, IF ANY, THAT YOU PAID FOR THE SOFTWARE.

EVALUATION LICENSE. If You are licensing the Software for evaluationpurposes, Your use of the Software is only permitted in a non-productionenvironment and for the period limited by the License Key. Notwithstandingany other provision in this EULA, an Evaluation License of the Software isprovided “AS-IS” without indemnification, support or warranty of any kind,expressed or implied.

1. DEFINITIONS.

1.1 “Affiliate” means, with respect to a party at a given time, an entity thatthen is directly or indirectly controlled by, is under common control with, orcontrols that party, and here “control” means an ownership, voting or similarinterest representing fifty percent (50%) or more of the total interests thenoutstanding of that entity.

1.2 “Documentation” means that documentation that is generally providedto You by VMware with the Software, as revised by VMware from time totime, and which may include end user manuals, operation instructions,installation guides, release notes, and on-line help files regarding the use ofthe Software.

1.3 “Guest Operating Systems” means instances of third-party operatingsystems licensed by You, installed in a Virtual Machine and run using theSoftware.

1.4 “Intellectual Property Rights” means all worldwide intellectualproperty rights, including without limitation, copyrights, trademarks, servicemarks, trade secrets, know how, inventions, patents, patent applications,


moral rights and all other proprietary rights, whether registered orunregistered.

1.5 “License” means a license granted under Section 2.1 (General LicenseGrant).

1.6 “License Key” means a serial number that enables You to activate anduse the Software.

1.7 “License Term” means the duration of a License as specified in theOrder.

1.8 “License Type” means the type of License applicable to the Software,as more fully described in the Order.

1.9 “Open Source Software” or “OSS” means software componentsembedded in the Software and provided under separate license terms, whichcan be found either in the open_source_licenses.txt file (or similar file)provided within the Software or at www.vmware.com/download/open_source.html.

1.10 “Order” means a purchase order, enterprise license agreement, orother ordering document issued by You to VMware or a VMware authorizedreseller that references and incorporates this EULA and is accepted byVMware as set forth in Section 4 (Order).

1.11 “Product Guide” means the current version of the VMware ProductGuide at the time of Your Order, copies of which are found atwww.vmware.com/download/eula.

1.12 “Support Services Terms” means VMware’s then-current supportpolicies, copies of which are posted at www.vmware.com/support/policies.

1.13 “Software” means the VMware Tools and the VMware computerprograms listed on VMware’s commercial price list to which You acquire alicense under an Order, together with any software code relating to theforegoing that is provided to You pursuant to a support and subscriptionservice contract and that is not subject to a separate license agreement.

1.14 “Territory” means the country or countries in which You have beeninvoiced; provided, however, that if You have been invoiced within any of theEuropean Economic Area member states, You may deploy the correspondingSoftware throughout the European Economic Area.

1.15 “Third Party Agent” means a third party delivering informationtechnology services to You pursuant to a written contract with You.

1.16 “Virtual Machine” means a software container that can run its ownoperating system and execute applications like a physical machine.

1.17 “VMware” means VMware, Inc., a Delaware corporation, if You arepurchasing Licenses or services for use in the United States and VMware


International Limited, a company organized and existing under the laws ofIreland, for all other purchases.

1.18 “VMware Tools” means the suite of utilities and drivers, Licensed byVMware under the “VMware Tools” name, that can be installed in a GuestOperating System to enhance the performance and functionality of a GuestOperating System when running in a Virtual Machine.

2. LICENSE GRANT.

2.1 General License Grant. VMware grants to You a non-exclusive, non-transferable (except as set forth in Section 12.1 (Transfers; Assignment)license to use the Software and the Documentation during the period of thelicense and within the Territory, solely for Your internal business operations,and subject to the provisions of the Product Guide. Unless otherwiseindicated in the Order, licenses granted to You will be perpetual, will be foruse of object code only, and will commence on either delivery of the physicalmedia or the date You are notified of availability for electronic download.

2.2 Third Party Agents. Under the License granted to You in Section 2.1(General License Grant) above, You may permit Your Third Party Agents toaccess, use and/or operate the Software on Your behalf for the sole purposeof delivering services to You, provided that You will be fully responsible forYour Third Party Agents’ compliance with terms and conditions of this EULAand any breach of this EULA by a Third Party Agent shall be deemed to be abreach by You.

2.3 Copying Permitted. You may copy the Software and Documentation asnecessary to install and run the quantity of copies licensed, but otherwise forarchival purposes only.

2.4 Benchmarking. You may use the Software to conduct internalperformance testing and benchmarking studies. You may only publish orotherwise distribute the results of such studies to third parties as follows: (a)if with respect to VMware’s Workstation or Fusion products, only if Youprovide a copy of Your study to [email protected] to distribution;(b) if with respect to any other Software, only if VMware has reviewed andapproved of the methodology, assumptions and other parameters of thestudy (please contact VMware at [email protected] request suchreview and approval) prior to such publication and distribution.

2.5 VMware Tools. You may distribute the VMware Tools to third partiessolely when installed in a Guest Operating System within a Virtual Machine.You are liable for compliance by those third parties with the terms andconditions of this EULA.

2.6 Open Source Software. Notwithstanding anything herein to thecontrary, Open Source Software is licensed to You under such OSS’s ownapplicable license terms, which can be found in the open_source_licenses.txtfile, the Documentation or as applicable, the corresponding source files for


the Software available at www.vmware.com/download/open_source.html.These OSS license terms are consistent with the license granted in Section 2(License Grant), and may contain additional rights benefiting You. The OSSlicense terms shall take precedence over this EULA to the extent that thisEULA imposes greater restrictions on You than the applicable OSS licenseterms. To the extent the license for any Open Source Software requiresVMware to make available to You the corresponding source code and/ormodifications (the "Source Files"), You may obtain a copy of the applicableSource Files from VMware's website at www.vmware.com/download/open_source.htmlor by sending a written request, with Your name andaddress to: VMware, Inc., 3401 Hillview Avenue, Palo Alto, CA 94304, UnitedStates of America. All requests should clearly specify: Open Source FilesRequest, Attention: General Counsel. This offer to obtain a copy of theSource Files is valid for three years from the date You acquired this Software.

3. RESTRICTIONS; OWNERSHIP.

3.1 License Restrictions. Without VMware’s prior written consent, You mustnot, and must not allow any third party to: (a) use Software in an applicationservices provider, service bureau, or similar capacity for third parties, exceptthat You may use the Software to deliver hosted services to Your Affiliates;(b) disclose to any third party the results of any benchmarking testing orcomparative or competitive analyses of VMware’s Software done by or onbehalf of You, except as specified in Section 2.4 (Benchmarking); (c) makeavailable Software in any form to anyone other than Your employees orcontractors reasonably acceptable to VMware and require access to useSoftware on behalf of You in a matter permitted by this EULA, except asspecified in Section 2.2 (Third Party Agents); (d) transfer or sublicenseSoftware or Documentation to an Affiliate or any third party, except asexpressly permitted in Section 12.1 (Transfers; Assignment); (e) useSoftware in conflict with the terms and restrictions of the Software’s licensingmodel and other requirements specified in Product Guide and/or VMwarequote; (f) except to the extent permitted by applicable mandatory law,modify, translate, enhance, or create derivative works from the Software, orreverse engineer, decompile, or otherwise attempt to derive source code fromthe Software, except as specified in Section 3.2 (Decompilation); (g) removeany copyright or other proprietary notices on or in any copies of Software; or(h) violate or circumvent any technological restrictions within the Software orspecified in this EULA, such as via software or services.

3.2 Decompilation. Notwithstanding the foregoing, decompiling theSoftware is permitted to the extent the laws of the Territory give You theexpress right to do so to obtain information necessary to render the Softwareinteroperable with other software; provided, however, You must first requestsuch information from VMware, provide all reasonably requested informationto allow VMware to assess Your claim, and VMware may, in its discretion,either provide such interoperability information to You, impose reasonableconditions, including a reasonable fee, on such use of the Software, or offer


to provide alternatives to ensure that VMware’s proprietary rights in theSoftware are protected and to reduce any adverse impact on VMware’sproprietary rights.

3.3 Ownership. The Software and Documentation, all copies and portionsthereof, and all improvements, enhancements, modifications and derivativeworks thereof, and all Intellectual Property Rights therein, are and shallremain the sole and exclusive property of VMware and its licensors. Yourrights to use the Software and Documentation shall be limited to thoseexpressly granted in this EULA and any applicable Order. No other rights withrespect to the Software or any related Intellectual Property Rights areimplied. You are not authorized to use (and shall not permit any third partyto use) the Software, Documentation or any portion thereof except asexpressly authorized by this EULA or the applicable Order. VMware reservesall rights not expressly granted to You. VMware does not transfer anyownership rights in any Software.

3.4 Guest Operating Systems. Certain Software allows Guest OperatingSystems and application programs to run on a computer system. Youacknowledge that You are responsible for obtaining and complying with anylicenses necessary to operate any such third-party software.

4. ORDER. Your Order is subject to this EULA. No Orders are binding onVMware until accepted by VMware. Orders for Software are deemed to beaccepted upon VMware’s delivery of the Software included in such Order.Orders issued to VMware do not have to be signed to be valid andenforceable.

5. RECORDS AND AUDIT. During the License Term for Software and for two(2) years after its expiration or termination, You will maintain accuraterecords of Your use of the Software sufficient to show compliance with theterms of this EULA. During this period, VMware will have the right to auditYour use of the Software to confirm compliance with the terms of this EULA.That audit is subject to reasonable notice by VMware and will notunreasonably interfere with Your business activities. VMware may conduct nomore than one (1) audit in any twelve (12) month period, and only duringnormal business hours. You will reasonably cooperate with VMware and anythird party auditor and will, without prejudice to other rights of VMware,address any non-compliance identified by the audit by promptly payingadditional fees. You will promptly reimburse VMware for all reasonable costsof the audit if the audit reveals either underpayment of more than five (5%)percent of the Software fees payable by You for the period audited, or thatYou have materially failed to maintain accurate records of Software use.

6. SUPPORT AND SUBSCRIPTION SERVICES. Except as expresslyspecified in the Product Guide, VMware does not provide any support orsubscription services for the Software under this EULA. You have no rights toany updates, upgrades or extensions or enhancements to the Softwaredeveloped by VMware unless you separately purchase VMware support or


subscription services. These support or subscription services are subject tothe Support Services Terms.

7. WARRANTIES.

7.1 Software Warranty, Duration and Remedy. VMware warrants to Youthat the Software will, for a period of ninety (90) days following notice ofavailability for electronic download or delivery (“Warranty Period”),substantially conform to the applicable Documentation, provided that theSoftware: (a) has been properly installed and used at all times in accordancewith the applicable Documentation; and (b) has not been modified or addedto by persons other than VMware or its authorized representative. VMwarewill, at its own expense and as its sole obligation and Your exclusive remedyfor any breach of this warranty, either replace that Software or correct anyreproducible error in that Software reported to VMware by You in writingduring the Warranty Period. If VMware determines that it is unable to correctthe error or replace the Software, VMware will refund to You the amount paidby You for that Software, in which case the License for that Software willterminate.

7.2 Software Disclaimer of Warranty. OTHER THAN THE WARRANTYABOVE, AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW,VMWARE AND ITS SUPPLIERS MAKE NO OTHER EXPRESS WARRANTIESUNDER THIS EULA, AND DISCLAIM ALL IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AND ANY WARRANTY ARISING BY STATUTE, OPERATION OFLAW, COURSE OF DEALING OR PERFORMANCE, OR USAGE OF TRADE.VMWARE AND ITS LICENSORS DO NOT WARRANT THAT THE SOFTWAREWILL OPERATE UNINTERRUPTED OR THAT IT WILL BE FREE FROM DEFECTSOR THAT IT WILL MEET YOUR REQUIREMENTS.

8. INTELLECTUAL PROPERTY INDEMNIFICATION.

8.1 Defense and Indemnification. Subject to the remainder of this Section8 (Intellectual Property Indemnification), VMware shall defend You againstany third party claim that the Software infringes any patent, trademark orcopyright of such third party, or misappropriates a trade secret (but only tothe extent that the misappropriation is not a result of Your actions) under thelaws of: (a) the United States and Canada; (b) the European Economic Area;(c) Australia; (d) New Zealand; (e) Japan; or (f) the People’s Republic ofChina, to the extent that such countries are part of the Territory for theLicense (“Infringement Claim”) and indemnify You from the resulting costsand damages finally awarded against You to such third party by a court ofcompetent jurisdiction or agreed to in settlement. The foregoing obligationsare applicable only if You: (i) promptly notify VMware in writing of theInfringement Claim; (ii) allow VMware sole control over the defense for theclaim and any settlement negotiations; and (iii) reasonably cooperate inresponse to VMware requests for assistance. You may not settle or


compromise any Infringement Claim without the prior written consent ofVMware.

8.2 Remedies. If the alleged infringing Software become, or in VMware’sopinion be likely to become, the subject of an Infringement Claim, VMwarewill, at VMware’s option and expense, do one of the following: (a) procure therights necessary for You to make continued use of the affected Software; (b)replace or modify the affected Software to make it non-infringing; or (c)terminate the License to the affected Software and discontinue the relatedsupport services, and, upon Your certified deletion of the affected Software,refund: (i) the fees paid by You for the License to the affected Software, lessstraight-line depreciation over a three (3) year useful life beginning on thedate such Software was delivered; and (ii) any pre-paid service feeattributable to related support services to be delivered after the date suchservice is stopped. Nothing in this Section 8.2 (Remedies) shall limitVMware’s obligation under Section 8.1 (Defense and Indemnification) todefend and indemnify You, provided that You replace the allegedly infringingSoftware upon VMware’s making alternate Software available to You and/orYou discontinue using the allegedly infringing Software upon receivingVMware’s notice terminating the affected License.

8.3 Exclusions. Notwithstanding the foregoing, VMware will have noobligation under this Section 8 (Intellectual Property Indemnification) orotherwise with respect to any claim based on: (a) a combination of Softwarewith non-VMware products (other than non-VMware products that are listedon the Order and used in an unmodified form); (b) use for a purpose or in amanner for which the Software was not designed; (c) use of any olderversion of the Software when use of a newer VMware version would haveavoided the infringement; (d) any modification to the Software made withoutVMware’s express written approval; (e) any claim that relates to open sourcesoftware or freeware technology or any derivatives or other adaptationsthereof that is not embedded by VMware into Software listed on VMware’scommercial price list; or (f) any Software provided on a no charge, beta orevaluation basis. THIS SECTION 8 (INTELLECTUAL PROPERTYINDEMNIFICATION) STATES YOUR SOLE AND EXCLUSIVE REMEDY ANDVMWARE’S ENTIRE LIABILITY FOR ANY INFRINGEMENT CLAIMS OR ACTIONS.

9. LIMITATION OF LIABILITY.

9.1 Limitation of Liability. TO THE MAXIMUM EXTENT MANDATED BY LAW,IN NO EVENT WILL VMWARE AND ITS LICENSORS BE LIABLE FOR ANY LOSTPROFITS OR BUSINESS OPPORTUNITIES, LOSS OF USE, LOSS OF REVENUE,LOSS OF GOODWILL, BUSINESS INTERRUPTION, LOSS OF DATA, OR ANYINDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES UNDERANY THEORY OF LIABILITY, WHETHER BASED IN CONTRACT, TORT,NEGLIGENCE, PRODUCT LIABILITY, OR OTHERWISE. BECAUSE SOMEJURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OFLIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE PRECEDINGLIMITATION MAY NOT APPLY TO YOU. VMWARE’S AND ITS LICENSORS’


LIABILITY UNDER THIS EULA WILL NOT, IN ANY EVENT, REGARDLESS OFWHETHER THE CLAIM IS BASED IN CONTRACT, TORT, STRICT LIABILITY, OROTHERWISE, EXCEED THE GREATER OF THE LICENSE FEES YOU PAID FORTHE SOFTWARE GIVING RISE TO THE CLAIM OR $5000. THE FOREGOINGLIMITATIONS SHALL APPLY REGARDLESS OF WHETHER VMWARE OR ITSLICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGESAND REGARDLESS OF WHETHER ANY REMEDY FAILS OF ITS ESSENTIALPURPOSE.

9.2 Further Limitations. VMware’s licensors shall have no liability of anykind under this EULA and VMware’s liability with respect to any third partysoftware embedded in the Software shall be subject to Section 9.1(Limitation of Liability). You may not bring a claim under this EULA more thaneighteen (18) months after the cause of action arises.

10. TERMINATION.

10.1 EULA Term. The term of this EULA begins on the notice of availabilityfor electronic download or delivery of the Software and continues until thisEULA is terminated in accordance with this Section 10.

10.2 Termination for Breach. VMware may terminate this EULA effectiveimmediately upon written notice to You if: (a) You fail to pay any portion ofthe fees under an applicable Order within ten (10) days after receivingwritten notice from VMware that payment is past due; or (b) You breach anyother provision of this EULA and fail to cure within thirty (30) days afterreceipt of VMware’s written notice thereof.

10.3 Termination for Insolvency. VMware may terminate this EULAeffective immediately upon written notice to You if You: (a) terminate orsuspend your business; (b) become insolvent, admit in writing Your inabilityto pay Your debts as they mature, make an assignment for the benefit ofcreditors; or become subject to control of a trustee, receiver or similarauthority; or (c) become subject to any bankruptcy or insolvency proceeding.

10.4 Effect of Termination. Upon VMware’s termination of this EULA: (a)all Licensed rights to all Software granted to You under this EULA willimmediately cease; and (b) You must cease all use of all Software, andreturn or certify destruction of all Software and License Keys (includingcopies) to VMware, and return, or if requested by VMware, destroy, anyrelated VMware Confidential Information in Your possession or control andcertify in writing to VMware that You have fully complied with theserequirements. Any provision will survive any termination or expiration if by itsnature and context it is intended to survive, including Sections 1(Definitions), 2.6 (Open Source Software), 3 (Restrictions; Ownership), 5(Records and Audit), 7.2 (Software Disclaimer of Warranty), 9 (Limitation ofLiability), 10 (Termination), 11 (Confidential Information) and 12 (General).

11. CONFIDENTIAL INFORMATION.


11.1 Definition. “Confidential Information” means information or materialsprovided by one party (“ Discloser”) to the other party (“Recipient”) whichare in tangible form and labelled “confidential” or the like, or, informationwhich a reasonable person knew or should have known to be confidential.The following information shall be considered Confidential Informationwhether or not marked or identified as such: (a) License Keys; (b)information regarding VMware’s pricing, product roadmaps or strategicmarketing plans; and (c) non-public materials relating to the Software.

11.2 Protection. Recipient may use Confidential Information of Discloser;(a) to exercise its rights and perform its obligations under this EULA; or (b) inconnection with the parties’ ongoing business relationship. Recipient will notuse any Confidential Information of Discloser for any purpose not expresslypermitted by this EULA, and will disclose the Confidential Information ofDiscloser only to the employees or contractors of Recipient who have a needto know such Confidential Information for purposes of this EULA and who areunder a duty of confidentiality no less restrictive than Recipient’s dutyhereunder. Recipient will protect Confidential Information from unauthorizeduse, access, or disclosure in the same manner as Recipient protects its ownconfidential or proprietary information of a similar nature but with no lessthan reasonable care.

11.3 Exceptions. Recipient’s obligations under Section 11.2 (Protection)with respect to any Confidential Information will terminate if Recipient canshow by written records that such information: (a) was already known toRecipient at the time of disclosure by Discloser; (b) was disclosed toRecipient by a third party who had the right to make such disclosure withoutany confidentiality restrictions; (c) is, or through no fault of Recipient hasbecome, generally available to the public; or (d) was independentlydeveloped by Recipient without access to, or use of, Discloser’s Information.In addition, Recipient will be allowed to disclose Confidential Information tothe extent that such disclosure is required by law or by the order of a court ofsimilar judicial or administrative body, provided that Recipient notifiesDiscloser of such required disclosure promptly and in writing and cooperateswith Discloser, at Discloser’s request and expense, in any lawful action tocontest or limit the scope of such required disclosure.

11.4 Data Privacy. You agree that VMware may process technical andrelated information about Your use of the Software which may includeinternet protocol address, hardware identification, operating system,application software, peripheral hardware, and non-personally identifiableSoftware usage statistics to facilitate the provisioning of updates, support,invoicing or online services and may transfer such information to othercompanies in the VMware worldwide group of companies from time to time.To the extent that this information constitutes personal data, VMware shall bethe controller of such personal data. To the extent that it acts as a controller,each party shall comply at all times with its obligations under applicable dataprotection legislation.


12. GENERAL.

12.1 Transfers; Assignment. Except to the extent transfer may not legally berestricted or as permitted by VMware’s transfer and assignment policies, in allcases following the process set forth at www.vmware.com/support/policies/licensingpolicies.html, You will not assign this EULA, any Order, or any rightor obligation herein or delegate any performance without VMware’s priorwritten consent, which consent will not be unreasonably withheld. Any otherattempted assignment or transfer by You will be void. VMware may use itsAffiliates or other sufficiently qualified subcontractors to provide services toYou, provided that VMware remains responsible to You for the performance ofthe services.

12.2 Notices. Any notice delivered by VMware to You under this EULA will bedelivered via mail, email or fax.

12.3 Waiver. Failure to enforce a provision of this EULA will not constitute awaiver.

12.4 Severability. If any part of this EULA is held unenforceable, thevalidity of all remaining parts will not be affected.

12.5 Compliance with Laws; Export Control; Government Regulations.Each party shall comply with all laws applicable to the actions contemplatedby this EULA. You acknowledge that the Software is of United States origin, isprovided subject to the U.S. Export Administration Regulations, may besubject to the export control laws of the applicable territory, and thatdiversion contrary to applicable export control laws is prohibited. Yourepresent that (1) you are not, and are not acting on behalf of, (a) anyperson who is a citizen, national, or resident of, or who is controlled by thegovernment of any country to which the United States has prohibited exporttransactions; or (b) any person or entity listed on the U.S. TreasuryDepartment list of Specially Designated Nationals and Blocked Persons, or theU.S. Commerce Department Denied Persons List or Entity List; and (2) youwill not permit the Software to be used for, any purposes prohibited by law,including, any prohibited development, design, manufacture or production ofmissiles or nuclear, chemical or biological weapons. The Software andaccompanying documentation are deemed to be “commercial computersoftware” and “commercial computer software documentation”, respectively,pursuant to DFARS Section 227.7202 and FAR Section 12.212(b), asapplicable. Any use, modification, reproduction, release, performing,displaying or disclosing of the Software and documentation by or for the U.S.Government shall be governed solely by the terms and conditions of thisEULA.

12.6 Construction. The headings of sections of this EULA are forconvenience and are not to be used in interpreting this EULA. As used in thisEULA, the word ‘including’ means “including but not limited to”.


12.7 Governing Law. This EULA is governed by the laws of the State ofCalifornia, United States of America (excluding its conflict of law rules), andthe federal laws of the United States. To the extent permitted by law, thestate and federal courts located in Santa Clara County, California will be theexclusive jurisdiction for disputes arising out of or in connection with thisEULA. The U.N. Convention on Contracts for the International Sale of Goodsdoes not apply.

12.8 Third Party Rights. Other than as expressly set out in this EULA, thisEULA does not create any rights for any person who is not a party to it, andno person who is not a party to this EULA may enforce any of its terms orrely on any exclusion or limitation contained in it.

12.9 Order of Precedence. In the event of conflict or inconsistency amongthe Product Guide, this EULA and the Order, the following order ofprecedence shall apply: (a) the Product Guide, (b) this EULA and (c) theOrder. With respect to any inconsistency between this EULA and an Order, theterms of this EULA shall supersede and control over any conflicting oradditional terms and conditions of any Order, acknowledgement orconfirmation or other document issued by You.

12.10 Entire Agreement. This EULA, including accepted Orders and anyamendments hereto, and the Product Guide contain the entire agreement ofthe parties with respect to the subject matter of this EULA and supersede allprevious or contemporaneous communications, representations, proposals,commitments, understandings and agreements, whether written or oral,between the parties regarding the subject matter hereof. This EULA may beamended only in writing signed by authorized representatives of both parties.

12.11 Contact Information. Please direct legal notices or othercorrespondence to VMware, Inc., 3401 Hillview Avenue, Palo Alto, California94304, United States of America, Attention: Legal Department.


Hitachi Storage Provider for VMware vCenter (VASA Provider) Deployment Guide

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-92ADPTR104-03

http://www.hds.com

MAILTO:[email protected]



Hitachi Storage Provider for VMware vCenter (VASA … Storage Platform G1000, VSP Gx00 models, VSP...

Documents

Transcript of Hitachi Storage Provider for VMware vCenter (VASA … Storage Platform G1000, VSP Gx00 models, VSP...