EMC Greenplum Data Computing Appliance Site Preparation ... · EMC Greenplum DCA Site Preparation...

26
EMC ® Greenplum ® Data Computing Appliance Site Preparation Guide Version 1.2.0.0 P/N: 300-013-850 Rev: A01

Transcript of EMC Greenplum Data Computing Appliance Site Preparation ... · EMC Greenplum DCA Site Preparation...

EMC® Greenplum® Data Computing ApplianceSite Preparation Guide

Version 1.2.0.0

P/N: 300-013-850Rev: A01

Copyright © 2012 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com

All other trademarks used herein are the property of their respective owners.

Table of Contents i

EMC Greenplum DCA Site Preparation Guide – Contents

EMC Greenplum DCA Site Preparation Guide - ContentsPreface ............................................................................................... 1

Chapter 1: Preparing the Data Center Environment .............. 2Confirming Site Requirements.......................................................... 2

Floor Space Requirements .......................................................... 2Power and Cooling Requirements................................................ 3Power Cord Specifications........................................................... 3Enviromental Requirements........................................................ 4Air Quality Requirements ............................................................ 4

Optional Securing Brackets .............................................................. 5Anti-Tip Bracket.......................................................................... 6Anti-Move Bracket ...................................................................... 6Seismic Restraint Bracket ........................................................... 7

Cabinet Positioning........................................................................... 8Package Dimensions and Clearance.................................................. 9

Chapter 2: Plan for Multiple Rack DCA .....................................10

Chapter 3: Gathering Site-Specific Information ....................12Site Requirements Checklist............................................................12Plan for Hadoop Networking ............................................................14Planning for Remote Support - ESRS and Dialhome ........................15

Chapter 4: Next Steps ...................................................................16

Chapter 5: Red Hat Enterprise Linux End User License Agreement........................................................................................17

Chapter 6: Apache Hadoop End User License Agreement ...20Apache License, Version 2.0 ......................................................20

1

EMC Greenplum DCA Site Preparation Guide – Preface

Preface

This guide is intended for EMC personnel, partners and customers to plan for an installation of a new Greenplum Data Computing Appliance (DCA) into a data center. This guide provides an overview of the system, information on data center requirements, a checklist of items to gather for software configuration and links to relevant documentation for use in the next steps of deployment. The requirements listed in this document must be met prior to performing a DCA installation.

This guide contains the following chapters and appendices:

• Chapter 1, “Preparing the Data Center Environment”

• Chapter 2, “Plan for Multiple Rack DCA”

• Chapter 3, “Gathering Site-Specific Information”

• Chapter 4, “Next Steps”

EMC Greenplum DCA Site Preparation Guide – Chapter 1: Preparing the Data Center Environment

1. Preparing the Data Center Environment

• Confirming Site Requirements

• Optional Securing Brackets

• Cabinet Positioning

• Package Dimensions and Clearance

Confirming Site RequirementsThe section summarizes the site requirements for the Greenplum DCA.

• Floor Space Requirements

• Power and Cooling Requirements

• Power Cord Specifications

• Enviromental Requirements

• Air Quality Requirements

Floor Space Requirements

The following table describes the physical footprint of the DCA. A multiple rack DCA is built with a System Rack first, Aggregation Rack Second, then Expansion Racks in position 3 through 12.

Table 1.1 Physical Dimensions

Height Width Depth Weight

DCA 1 Module - System Rack

75 in

190 cm

24 in

61 cm

41.6 in

104 cm

940 lbs

DCA 4 Module - System Rack

75 in

190 cm

24 in

61 cm

41.6 in

104 cm

1700 lbs

DCA 4 Module - Aggregation Rack

75 in

190 cm

24in

61 cm

41.6 in

104 cm

1700 lbs

DCA 4 Module - Expansion Rack

75in

190 cm

48 in

122 cm

41.6 in

104 cm

1600 lbs

Confirming Site Requirements 2

EMC Greenplum DCA Site Preparation Guide – Chapter 1: Preparing the Data Center Environment

Power and Cooling Requirements

The following table describes the power and cooling requirements of the Greenplum DCA. A multiple rack DCA is built with a System Rack first, Aggregation Rack Second, then Expansion Racks in position 3 through 6.

Table 1.2 Power and Cooling Specifications

Total Power VA Power Connections Cooling (BTU/HR)

DCA 1 Module - System Rack

3590 2 11260

DCA 4 Modules - System Rack

9210 4 28500

DCA 4 Modules - Aggregation Rack

8970 4 28020

DCA 4 Modules - Expansion Rack

8270 4 25630

Additional Module (Upgrade)

1870 -- 5750

Power Cord Specifications

Table 1.3 Power Cord Specifications

Power Cord Connector

Country Power Cord Model Descriptions

USA, Japan DCA1-US-15 DCA - Single Phase, 30Amp, 15ft ext cords with L6-30P plug

DCA1-US-21 DCA - Single Phase, 30Amp, 21ft ext cords with L6-30P plug

Australia DCA1-ASTL-15 DCA - Single Phase, 30Amp, 15ft ext cords with CLIPSAL 56PA332 plug

DCA1-ASTL-21 DCA - Single Phase, 30Amp, 21ft ext cords with CLIPSAL 56PA332 plug

Other Countries

DCA1-IEC3-15 DCA - Single Phase, 30Amp, 15ft ext cords with IEC309-332P6 plug

DCA1-IEC3-21 DCA - Single Phase, 30Amp, 21ft ext cords with IEC309-332P6 plug

Other Power Cord Types

DCA1-RUS-15 DCA - Single Phase, 30Amp, 15ft ext cords with RUSSELLSTOLL 3750DP plug

DCA1-RUS-21 DCA - Single Phase, 30Amp, 21ft ext cords with RUSSELLSTOLL 3750DP plug

Confirming Site Requirements 3

EMC Greenplum DCA Site Preparation Guide – Chapter 1: Preparing the Data Center Environment

Enviromental Requirements

Table 1.4 Environmental Requirements

+15°C to +32°C (59°F to 89.6°F) site temperature

40% to 55% relative humidity

0 to 2439 meters (0 to 8,000 feet) above sea level operating altitude

Air Quality Requirements

EMC products are designed to be consistent with the requirements of the American Society of Heating, Refrigeration and Air Conditioning Engineers (ASHRAE) Environmental Standard Handbook and the most current revision of Thermal Guidelines for Data Processing Environments, Second Edition, ASHRAE 2009b.

The data center should maintain a cleanliness level as identified in ISO 14664-1, class 8 for particulate dust and pollution control. The air entering the data center should be filtered with a MERV 11 filter or better. The air within the data center should be continuously filtered with a MERV 8 or better filtration system. In addition, efforts should be maintained to prevent conductive particles, such as zinc whiskers, from entering the facility.

The allowable relative humidity level is 20 to 80% non condensing, however, the recommended operating environment range is 40 to 55%. For data centers with gaseous contamination, such as high sulfur content, lower temperatures and humidity are recommended to minimize the risk of hardware corrosion and degradation. In general, the humidity fluctuations within the data center should be minimized. It is also recommended that the data center be positively pressured and have air curtains on entry ways to prevent outside air contaminants and humidity from entering the facility.

For facilities below 40% relative humidity, it is recommended to use grounding straps when contacting the equipment to avoid the risk of Electrostatic discharge (ESD), which can harm electronic equipment.

As part of an ongoing monitoring process for the corrosiveness of the environment, it is recommended to place copper and silver coupons (per ISA 71.04-1985, Section 6.1 Reactivity), in airstreams representative of those in the data center. The monthly reactivity rate of the coupons should be less than 300 Angstroms. When monitored reactivity rate is exceeded, the coupon should be analyzed for material species and a corrective mitigation process put in place.

Confirming Site Requirements 4

EMC Greenplum DCA Site Preparation Guide – Chapter 1: Preparing the Data Center Environment

This EMC® cabinet ventilates from front to back; you must provide adequate clearance to service and cool the system. Depending on component-specific connections within the cabinet, the available power cord length may be somewhat shorter than the 15-foot standard.

Figure 1.1 Access and Ventilation Requirements

Optional Securing BracketsIf you intend to secure the optional stabilizer brackets to your site floor, prepare the location for the mounting bolts. The additional brackets help to prevent the cabinet from tipping while you service cantilevered levels, or from rolling during minor seismic events. The brackets provide three levels of protection for stabilizing the unit.

• Anti-Tip Bracket

• Anti-Move Bracket

• Seismic Restraint Bracket

Optional Securing Brackets 5

EMC Greenplum DCA Site Preparation Guide – Chapter 1: Preparing the Data Center Environment

Anti-Tip Bracket

Use this bracket to provide an extra measure of anti-tip security. One or two kits may be used. For cabinets with components that slide, EMC recommends that you use two kits.

Figure 1.2 Anti-Tip Bracket Placement

Anti-Move Bracket

Use this bracket to permanently fasten the unit to the floor.

Figure 1.3 Anti-Move Bracket Placement

Optional Securing Brackets 6

EMC Greenplum DCA Site Preparation Guide – Chapter 1: Preparing the Data Center Environment

Seismic Restraint Bracket

Use this bracket to provide the highest protection from moving or tipping.

Figure 1.4 Seismic Restraint Bracket Placement

Optional Securing Brackets 7

EMC Greenplum DCA Site Preparation Guide – Chapter 1: Preparing the Data Center Environment

Cabinet PositioningThe cabinet bottom includes four caster wheels. The front wheels are fixed; the two rear casters swivel in a 1.75-inch diameter. Swivel position of the caster wheels will determine the load-bearing points on your site floor, but does not affect the cabinet footprint. Once you have positioned, leveled, and stabilized the cabinet, the four leveling feet determine the final load-bearing points on your site floor.

Figure 1.5 Cabinet Positioning

When the cabinet is centered over two typical 24 in. (60.96 cm) by 24 in. (60.96 cm) floor tiles:

• Cutouts should be 8 in. (20.32 cm) by 6 in. (15.24 cm).

• Cutouts should be centered on the tiles, 9 in. (22.86 cm) from the front and rear and 8 in. (20.32 cm) from sides.

Cabinet Positioning 8

EMC Greenplum DCA Site Preparation Guide – Chapter 1: Preparing the Data Center Environment

Package Dimensions and ClearanceMake certain your doorways and elevators are wide enough and tall enough to accommodate the shipping pallet and cabinet. Use a mechanical lift or pallet jack to position the packaged cabinet in its final location.

Figure 1.6 Door Clearance

Leave approximately 2.43 meters (8 feet) of clearance at the back of the cabinet to unload the unit and roll it off the pallet.

Figure 1.7 Unloading Clearance

Package Dimensions and Clearance 9

EMC Greenplum DCA Site Preparation Guide – Chapter 2: Plan for Multiple Rack DCA

2. Plan for Multiple Rack DCA

This section contains information required to plan for a multiple rack DCA. Plan for cabling based on the size of the DCA - a cluster larger than 6 racks requires different cabling than a cluster 6 racks or smaller.

Cable Kits

There are a several length cable kits for multi-rack connectivity. Use the table below to determine and order the length of cabling that will best fit the customer’s environment.

Kit NamePart Number

Quantity

Component Description

DCA1-CBL5 100-652-574 1 BRCD 10GBE TWINAX COPPER 5M 8-PACK

038-003-476 1 25’ CAT6 Ethernet Cable

DCA1-CBL10

100-652-576 2 BRCD 10GBE SFP+ SHORT WAVE 8-PACK

038-003-733 8 10m LC to LC Optical 50 Micron MM Cable Assemblies

038-003-476 1 25’ CAT6 Ethernet Cable

DCA1-CBL30

100-652-576 2 BRCD 10GBE SFP+ SHORT WAVE 8-PACK

038-003-740 8 30m LC to LC Optical 50 Micron MM Cable Assemblies

038-003-475 1 100’ CAT6 Ethernet Cable

Table 2.1 Cabling Kit Part Number and Contents

6 Rack Cable Kits

Use the following table to plan for installation or upgrade of a cluster 6 racks or smaller.

FROM AGGREG (Rack 2) TO Cable Kit

Rack 1 - SYSRACK DCA1-CBL5

Rack 2 - AGGREG DCA1-CBL5

Rack 3 - 1st EXPAND DCA1-CBL5

Rack 4 - 2nd EXPAND DCA1-CBL10

10

EMC Greenplum DCA Site Preparation Guide – Chapter 2: Plan for Multiple Rack DCA

Table 2.2 Cabling Kits for 6 Rack DCA

12 Rack Cable Kits

Use the following table to plan for installation or upgrade of a cluster up to 12 racks. In a 12 rack DCA, cabling must run from each rack to the aggregation switches located in rack 2 and 7.

FROM AGGREG TO Cable Kit

Rack 2

Rack 1 - SYSRACK DCA1-CBL5

Rack 2 - AGGREG 1 DCA1-CBL5

Rack 3 - 1st EXPAND DCA1-CBL5

Rack 4 - 2nd EXPAND DCA1-CBL10

Rack 5 - 3rd EXPAND DCA1-CBL10

Rack 6 - 4th EXPAND DCA1-CBL10

Rack 7 - AGGREG 2 DCA1-CBL30

Rack 8 - 5th EXPAND DCA1-CBL30

Rack 9 - 6th EXPAND DCA1-CBL30

Rack 10 - 7th EXPAND DCA1-CBL30

Rack 11 - 8th EXPAND DCA1-CBL30

Rack 12 - 9th EXPAND DCA1-CBL30

Rack 7

Rack 1 - SYSRACK DCA1-CBL30

Rack 2 - AGGREG 1 DCA1-CBL10

Rack 3 - 1st EXPAND DCA1-CBL10

Rack 4 - 2nd EXPAND DCA1-CBL10

Rack 5 - 3rd EXPAND DCA1-CBL5

Rack 6 - 4th EXPAND DCA1-CBL5

Rack 7 - AGGREG 2 DCA1-CBL5

Rack 8 - 5th EXPAND DCA1-CBL5

Rack 9 - 6th EXPAND DCA1-CBL5

Rack 10 - 7th EXPAND DCA1-CBL10

Rack 11 - 8th EXPAND DCA1-CBL10

Rack 12 - 9th EXPAND DCA1-CBL10

Table 2.3 Cable Kits for 12 Rack DCA

Rack 5 - 3rd EXPAND DCA1-CBL10

Rack 6 - 4th EXPAND DCA1-CBL10

FROM AGGREG (Rack 2) TO Cable Kit

11

EMC DCA Getting Started Guide – Chapter 3: Gathering Site-Specific Information

3. Gathering Site-Specific Information

In order to complete an installation of an EMC Greenplum DCA, the following information should be gathered from the customer’s network and database personnel. The following sections are included:

• Site Requirements Checklist

• Plan for Hadoop Networking

• Planning for Remote Support - ESRS and Dialhome

Site Requirements Checklist

Table 3.1 Site-Specific Information

Information Description

External IP and hostname of the primary master

This is the IP address and hostname that the customer will use to connect to the primary master host from their public LAN.

The master hostname is also used for client connections to Greenplum Database.

External IP and hostname of the standby master

This is the IP address and hostname that the customer will use to connect to the standby master host from their public LAN.

Virtual IP Address A Virtual IP Address (VIP) is required to use master server failover features. A VIP will simply be a third external IP address . In the event of a master server failure, the VIP will moved from primary to standby master server. This should be the IP address client tools connect to.

If the subnet and gateway for the VIP differ from the other external IP addresses, this should be collected also.

External IP and hostname for DIA hosts

An IP address and hostname is required for each DIA host. The source data will be transferred to the DIA through this connection. Four IP addresses and hostnames are required per DIA module.

Netmask Netmask of the customer’s network.

Gateway Default gateway of the customer’s network and the IP address and interface name of the router.

NTP server IP The IP address or hostname of the customer’s preferred NTP (Network Time Protocol) server.

DNS name server IP The IP address of the customer’s DNS name server.

iDRAC password This is the password used for remote access to the master, standby master and segment hosts using the integrated Dell Remote Access Controller (iDRAC) interface. The default iDRAC password is calvin.

root password Customer supplied root password for the master, standby master and segment hosts. The default root password is changeme.

Site Requirements Checklist 12

EMC DCA Getting Started Guide – Chapter 3: Gathering Site-Specific Information

gpadmin password Customer supplied Greenplum Database superuser password. The default gpadmin password is changeme.

System locale The preferred locale to be used on the master, standby master and segment hosts. en_US.UTF-8 is the default locale for the Greenplum DCA (U.S. English and Unicode character set encoding).

A locale identifier consists of a language identifier and a region identifier, and optionally a character set encoding. For example, sv_SE is Swedish as spoken in Sweden, en_US is U.S. English, and fr_CA is French Canadian. If more than one character set encoding can be useful for a locale, then the specifications look like this: en_US.UTF-8 (locale specification and character set encoding).

System timezone The local timezone to be used on the master, standby master and segment hosts. The default timezone is PST.

Database character set encoding

UNICODE (UTF-8) is the default character set encoding for Greenplum Database (server-side encoding). This is usually the best choice, as it allows the customer to store all possible Unicode characters from any language, but if all data you are storing is from a single language (now and in the future), it does entail a slight storage space penalty compared to an encoding specific to that language.

If the space savings is key, the customer should consider Latin-1, Latin-9, or WIN1252 for US or Western European installations, since those encodings use a single byte per character. Likewise in Thailand you might consider WIN874 to store Thai, since it uses a single byte per character. However, keep in mind that this prevents storing any data outside those character sets. Even in the US or Western Europe, customers might find that some of their data is Latin-1, while some is Latin-9 or Win1252, so any choice of single-byte encoding will not accommodate all of their data needs. See the Greenplum Database Administrator Guide for a list of all supported character set encodings.

Software Tools Connection to the DCA for setup and management requires an SSH utility. EMC recommends Putty or Cygwin.

Hardware Tools The following hardware tools will be required during installation of the DCA:

• Utility Knife

• 9/16’’ Socket Wrench

• ESD (electro-static discharge) kit

Power Connection for Service Laptop

Power for external devices should not be drawn from the DCA cabinet. A power connection is required for the EMC personnel service laptop. The connection should be a standard AC 100-240V~1.5A, 50-60hz outlet.

Table 3.1 Site-Specific Information

Information Description

Site Requirements Checklist 13

EMC DCA Getting Started Guide – Chapter 3: Gathering Site-Specific Information

Plan for Hadoop NetworkingHadoop modules have specific networking requirements. It is important to plan these requirements with the customer prior to an installation - Hadoop services cannot be started without the proper networking configuration.

Item Description

Hadoop Namenode Virtual IP Address Virtual IP Address to use for Hadoop namenodes. This IP address will move to the standby namenode during a failover.

Custom VLAN ID VLAN ID

IP Addresses for VLAN IP addresses to use for Hadoop nodes. The amount of addresses required depends on the total number of Hadoop nodes being deployed.

Netmask for VLAN The netmask for IP addresses on the VLAN.

Gateway for VLAN The gateway IP addresse for the VLAN.

Table 3.2 Hadoop Networking Requirements

Dial-home and ESRS Connectivity

The DCA supports dial-home for event notification to EMC Global Services support center. Communication from the DCA to EMC is done via FTPS. Firewall access should be setup to allow FTPS traffic from the DCA’s external IP address to the following EMC addresses:

corpusfep3.emc.comcorpusfep4.emc.com

The DCA also support remote support through an ESRS Gateway. If the DCA is to be setup in an environment with ESRS, the Gateway IP address should be identified prior to installation. The DCA supports FTP, SMTP and HTTPS connection types to the ESRS Gateway.

Ethernet Connections to Network

The DCA connects to a network through the master and standby master servers. Two ethernet connections are required to the master and standby master server. Ethernet cables for external connections are not included with the system.

DIA modules connect to the network through an ethernet connection on each DIA host. Each DIA module requires four connections (1 per server).

Table 3.1 Site-Specific Information

Information Description

Plan for Hadoop Networking 14

EMC DCA Getting Started Guide – Chapter 3: Gathering Site-Specific Information

Planning for Remote Support - ESRS and DialhomeThe Greenplum DCA supports remote support and dialhome through EMC Secure Remote Support (ESRS) as well as secure direct dialhome. Use the following information to plan remote support for the DCA.

ESRS Considerations

Review the following considerations for implementing remote support on DCA through an ESRS gateway:

• The ESRS Gateway must be running a minimum version of 2.08

• Port 22 between the ESRS Gateway and DCA must be open to allow for INCOMING support - from the EMC Support Center.

• SMTP is supported for OUTGOING (dialhome) support. Port 25 must be open between the ESRS Gateway and DCA for SMTP support.

• FTP is supported for OUTGOING (dialhome) support. Port 21 must be open between the ESRS Gateway and DCA for FTP support.

• HTTPS is supported for OUTGOING (dialhome) support. Port 443 must be open between the ESRS Gateway and DCA for HTTPS support.

Secure Direct Dialhome Considerations

Review the following considerations for implementing dialhome on the DCA directly to EMC - using the FTPS protocol:

• The DCA must have access to corpusfep3.emc.com and corpusfep4.emc.com using the passive FTPS protocol. The passive FTPS protocol uses ports 990 to establish a connection and a dynamic port range of 20000-30000 to transfer data.

• OUTGOING (dialhome) support only, INCOMING is not supported.

Planning for Remote Support - ESRS and Dialhome 15

16

EMC Greenplum DCA Site Preparation Guide – Next Steps:

4. Next Steps

The following documentation is available on Powerlink and may be used during the next steps of deployment:

Powerlink.emc.com > Support > Technical Documentation and Advisories > Hardware/Platforms Documentation > Greenplum DCA

• EMC Greenplum Data Computing Appliance Getting Started Guide

Powerlink.emc.com > Support > Technical Documentation and Advisories > Software ~ E-I ~ Documentation > Greenplum Family

• Greenplum Database 4.1 Administrator Guide

• Greenplum Database 4.1 Release Notes

EMC DCA Getting Started Guide – Chapter 5: Red Hat Enterprise Linux End User License Agreement

5. Red Hat Enterprise Linux End User License

AgreementLICENSE AGREEMENT AND LIMITED PRODUCT WARRANTY RED HAT® ENTERPRISE LINUX® AND RED HAT® APPLICATIONS

This agreement governs the use of the Software and any updates to the Software, regardless of the delivery mechanism. The Software is a collective work under U.S. Copyright Law. Subject to the following terms, Red Hat, Inc. (“Red Hat”) grants to the user (“Customer”) a license to this collective work pursuant to the GNU General Public License.

1. The Software. Red Hat Enterprise Linux and Red Hat Applications (the “Software”) are either a modular operating system or application consisting of hundreds of software components. The end user license agreement for each component is located in the component's source code. With the exception of certain image files identified in Section 2 below, the license terms for the components permit Customer to copy, modify, and redistribute the component, in both source code and binary code forms. This agreement does not limit Customer's rights under, or grant Customer rights that supersede, the license terms of any particular component.

2. Intellectual Property Rights. The Software and each of its components, including the source code, documentation, appearance, structure and organization are owned by Red Hat and others and are protected under copyright and other laws. Title to the Software and any component, or to any copy, modification, or merged portion shall remain with the aforementioned, subject to the applicable license. The “Red Hat” trademark and the “Shadowman” logo are registered trademarks of Red Hat in the U.S. and other countries. This agreement does not permit Customer to distribute the Software using Red Hat's trademarks. Customer should read the information found at http://www.redhat.com/about/corporate/trademark/ before distributing a copy of the Software, regardless of whether it has been modified. If Customer makes a commercial redistribution of the Software, unless a separate agreement with Red Hat is executed or other permission granted, then Customer must modify any files identified as “REDHAT-LOGOS” and “anaconda-images” to remove all images containing the “Red Hat” trademark or the “Shadowman” logo. Merely deleting these files may corrupt the Software.

3. Limited Warranty. Except as specifically stated in this agreement or a license for a particular component, to the maximum extent permitted under applicable law, the Software and the components are provided and licensed “as is” without warranty of any kind, expressed or implied, including the implied warranties of merchantability, non-infringement or fitness for a particular purpose. Red Hat warrants that the media on which the Software is furnished will be free from defects in materials and manufacture under normal use for a period of 30 days from the date of delivery to Customer. Red Hat does not warrant that the

17

EMC DCA Getting Started Guide – Chapter 5: Red Hat Enterprise Linux End User License Agreement

functions contained in the Software will meet Customer's requirements or that the operation of the Software will be entirely error free or appear precisely as described in the accompanying documentation. This warranty extends only to the party that purchases the Software from Red Hat or a Red Hat authorized distributor.

4. Limitation of Remedies and Liability. To the maximum extent permitted by applicable law, the remedies described below are accepted by Customer as its only remedies. Red Hat's entire liability, and Customer's exclusive remedies, shall be: If the Software media is defective, Customer may return it within 30 days of delivery along with a copy of Customer's payment receipt and Red Hat, at its option, will replace it or refund the money paid by Customer for the Software. To the maximum extent permitted by applicable law, Red Hat or any Red Hat authorized dealer will not be liable to Customer for any incidental or consequential damages, including lost profits or lost savings arising out of the use or inability to use the Software, even if Red Hat or such dealer has been advised of the possibility of such damages. In no event shall Red Hat's liability under this agreement exceed the amount that Customer paid to Red Hat under this agreement during the twelve months preceding the action.

5. Export Control. As required by U.S. law, Customer represents and warrants that it: (a) understands that the Software is subject to export controls under the U.S. Commerce Department’s Export Administration Regulations (“EAR”); (b) is not located in a prohibited destination country under the EAR or U.S. sanctions regulations (currently Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria); (c) will not export, re-export, or transfer the Software to any prohibited destination, entity, or individual without the necessary export license(s) or authorizations(s) from the U.S. Government; (d) will not use or transfer the Software for use in any sensitive nuclear, chemical or biological weapons, or missile technology end-uses unless authorized by the U.S. Government by regulation or specific license; (e) understands and agrees that if it is in the United States and exports or transfers the Software to eligible end users, it will, as required by EAR Section 740.17(e), submit semi-annual reports to the Commerce Department’s Bureau of Industry & Security (BIS), which include the name and address (including country) of each transferee; and (f) understands that countries other than the United States may restrict the import, use, or export of encryption products and that it shall be solely responsible for compliance with any such import, use, or export restrictions.

6. Third Party Programs. Red Hat may distribute third party software programs with the Software that are not part of the Software. These third party programs are subject to their own license terms. The license terms either accompany the programs or can be viewed at http://www.redhat.com/licenses/. If Customer does not agree to abide by the applicable license terms for such programs, then Customer may not install them. If Customer wishes to install the programs on more than one system or transfer the programs to another party, then Customer must contact the licensor of the programs.

18

EMC DCA Getting Started Guide – Chapter 5: Red Hat Enterprise Linux End User License Agreement

7. General. If any provision of this agreement is held to be unenforceable, that shall not affect the enforceability of the remaining provisions. This agreement shall be governed by the laws of the State of North Carolina and of the United States, without regard to any conflict of laws provisions, except that the United Nations Convention on the International Sale of Goods shall not apply.

Copyright © 2003 Red Hat, Inc. All rights reserved. "Red Hat" and the Red Hat "Shadowman" logo are registered trademarks of Red Hat, Inc. "Linux" is a registered trademark of Linus Torvalds. All other trademarks are the property of their respective owners.

19

EMC DCA Getting Started Guide – Chapter 6: Apache Hadoop End User License Agreement

6. Apache Hadoop End User License

Agreement

Apache License, Version 2.0

FoundationProjectsPeopleGet InvolvedDownloadSupport ApacheHome » Licenses

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, and distribution as defined by Sections 1 through 9 of this document.

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

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

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

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

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, 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 is included in or attached to the work (an example is provided in the Appendix below).

"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 editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

20

EMC DCA Getting Started Guide – Chapter 6: Apache Hadoop End User License Agreement

"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes 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, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants 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 and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

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

You must cause any modified files to carry prominent notices stating that You changed the files; and

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

21

EMC DCA Getting Started Guide – Chapter 6: Apache Hadoop End User License Agreement

If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor 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 for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated 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 deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such 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 to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or

22

EMC DCA Getting Started Guide – Chapter 6: Apache Hadoop End User License Agreement

rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

23