Dell Cloud Solution for
OpenStack? Solutions Crowbar Deployment Guide
DOCUMENT PROVIDED UNDER APACHE 2 LICENSE
Notes, Cautions, and Warnings
CAUTION: A CAUTION indicates potential damage to hardware or loss of data if
instructions are not followed.
Information in this document is subject to change without notice.
? 2011 Dell Inc. All rights reserved.
Reproduction of these materials is allowed under the Apache 2 license.
Trademarks used in this text: Dell?, the DELL logo, OpenStack ?, Nagios?, Ganglia?, Opscode Chef?, Canonical Ubuntu? , VmWare?Other trademarks and trade names may be used in this publication to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.
Contents
1 Simple environment setup (4)
1.1
Hardware setup (4)
1.1.1 Recommended setup (4)
1.1.2 Site preparation needed for the deployment (5)
1.2
Network setup (5)
1.2.1 Switch Configuration (8)
1.2.2 Physical configuration (9)
1.2.3 Single rack expansion from Starter Solution (10)
1.2.4 Multi Rack Expansion (11)
1.3
Installing admin node OS (11)
1.4
Installing Crowbar (13)
Enabling the Public Network Port on the Admin Server (15)
1.5
1.6
Verifying admin node state (15)
1.7
Installing nodes (16)
2 Installing components (16)
2.1
Example: Implementing a Proposal via Cmd. Line (16)
2.1.1 Obtain a proposal (17)
2.1.2 Update a proposal (17)
2.1.3 Committing proposal (17)
2.1.4 Modifying an active configuration (17)
3 Appendix A: End User License Agreement (18)
1Simple environment setup
This section describes the required steps to achieve the default setup.
Hardware setup
1.1
This guide assumes the minimal hardware footprint described below. Please see the Reference Architecture for more details.
Role Count Usage Notes
Bootstrap system 1 Runs the VMPlayer image needed to
bootstrap
- Has VMPlayer and the proper
VMPlayer image
Admin node 1 Runs Crowbar and infrastructure services - Console access (KVM)*
- 2 NICs
Compute node 3-5 Runs cloud components - For Swift storage, should have
at least 2 disks
- Ideally, 2 NICs
*In the current release, console access to the admin node is required. In future versions, all configuration tasks will be performed without the need for console access.
The hardware on the admin node should be configured as follows:
?Boot sequence: BIOS is set to b oot from local disk. Note that this is the “normal” operating setting, but for its initial setup boot, the admin node will need to boot from network in order to bootstrap the installation from the VMPlayer image.
?RAID controller: All disks should be in a RAID 10 configuration.
BMC and networking settings are configured using Crowbar, and manual steps are not required.
1.1.1Recommended setup
The minimum configuration for the recommended Starter Solution is 6 nodes (3 two sled C6100s). This configuration can be easily expanded to 10 nodes without any changes to the networking infrastructure. Expansion beyond 10 nodes is accomplished by simply adding blocks of servers and networking them.
In this release of the solution, you can deploy the hardware platform and software on: ?PowerEdge C6100 (two sled configuration)
?Dell PC6248
The PowerEdge C6100 is a multi-node shared infrastructure platform delivered in a 2U chassis. There are two or four compute nodes (servers) that install in the chassis. The PowerEdge C6100 configuration for this release is the 2-node configuration. The PowerEdge C6100 compute node is a dual socket Intel XEONTM server. The only difference is the form factor and number of PCIe slots. Each compute node in the PowerEdge C6100 chassis has access to 12 hot-swappable 2.5” drives.
Compute Node C6100 (2-node)
Platform C6100
12 2.5” Drive, 2-node BP per node
CPU X5620
RAM 96GB (1333 MHz) per node
Additional Network Controller None
RAID Controller LSI 2008
DISK 12 x 600GB 2.5” SAS 10K per node
Cluster Switch PC 6248
1.1.2Site preparation needed for the deployment
Solution deployment needs some preliminary preparation. This solution does not supply any firewalls or load-balancers. You may want to use firewalls or load-balancing to access and use portions of the solution. Indirectly, a bastion host, installed behind appropriate site specific security systems, can be used to access the Starter Solution and the VMs remotely. This means that direct access to
local/internal/external networks should not be done.
For the setup of the admin node, connect a keyboard and monitor. In addition, all that is required is a laptop or another machine that can run VMware Player and connect to the admin node via a crossover network cable.
Estimate the electrical power and cooling usage using the Dell Energy Smart Solution Advisor
(https://www.wendangku.net/doc/ac17658925.html,/content/topics/topic.aspx/global/products/pedge/topics/en/config_calculator?c= us&cs=555&l=en&s=biz). Using this tool to plan the appropriate PDU and make sure the cooling is adequate.
Network setup
1.2
The network configuration assumes a flat L2 wiring – all network connections should be accessible at that layer. Where isolation between different logical networks is required, VLANs are used.
The default networks are presented in the following table.
Usage Description Default
reserved
vLAN tag Tagged 802.1q
Admin/Internal vLAN Used for administrative functions such as Crowbar node
installation, TFTP booting, DHCP assignments, KVM,
system logs, backups, and other monitoring. There is only
one vLAN set up for this function and it is spanned across
the entire network.
100 Not tagged
BMC vLAN Used for connecting to the BMC of each node. 100 Not tagged Storage vLAN Used by the Swift storage system for replication of data
between machines, monitoring of data integrity, and other
storage specific functions. (802.1q Tagged)
200 Tagged
300 Tagged External vLANs Used for connections to devices external to the OpenStack
Cloud infrastructure; these include externally visible
services such as load balancers and web servers. Use one or
many of these networks, dependent on the need to segregate
traffic among groups of servers. (802.1q Tagged)
400 Tagged Nova Floating Assigned to Nova VMs by the Nova manager. (802.1q
Tagged)
Nova Fixed Assigned to Nova VMs by the Nova manager. (802.1q
500 Tagged Tagged)
Note: The admin and BMC networks are expected to be in the same L2 network.
The figure below shows example cabling of network connectivity inside the cluster. The network in this solution is not configured for redundancy.
Node Starter Solution Cabling:
Component LOM0 LOM1 BMC CH1SL1 SW1-1 SW2-1 SW1-31 CH1SL2 SW1-2 SW2-2 SW2-31
CH2SL1 SW1-3 SW2-3 SW1-32
CH2SL2 SW1-4 SW2-4 SW2-32
CH3SL1 SW1-5 SW2-5 SW1-33
CH3SL2 SW1-6 SW2-6 SW2-33
(Note: CH = chassis, SL = sled, SW = switch)
All nodes have two (2) 1 Gb NICs. The admin node configures the BMC and the OS is configured to bond the two LOMs. Each NIC and BMC is cabled to the Dell PowerConnect PC6248 per the cabling setup outlined above.
1.2.1Switch Configuration
When deploying the switches the following configuration should be used to appropriately setup the VLANs. The following commands are to be used with a Dell PowerConnect 6248 switch. Modifications will be required depending on the network configuration of the environment.
1#
2#
3vlan databse
4vlan 100,200,300,400,500
5exit
6interface vlan 100
7name Admin_Net
8exit
9interface vlan 200
10name Storage_Net
11exit
12interface vlan 300
13name External_Net
14exit
15interface vlan 400
16name Nova_Floating
17exit
18interface vlan 500
19name Nova_Fixed
20exit
21#
22#
23interface range ethernet 1/g1-1/g48
24shutdown
25spanning-tree portfast
26switchport mode general
27switchport general pvid 100
28switchport general allowed vlan add 100
29switchport general allowed vlan add 200,300,400,500 tagged
30switchport general allowed vlan remove 1
31no switchport general acceptable-frame-type tagged-only
32lldp transmit-tlv port-desc sys-name sys-desc sys-cap
33lldp transmit-mgmt
34lldp notification
35no shutdown
36exit
37#
38#
39ip address xxx.xxx.xxx.xxx
40ip address vlan ???
41ip ssh server
42#
43#
44UPLINK Port
45interface ethernet 1/gxxx
46switchport general pvid XXXX
47no switchport general acceptable-frame-type tagged-only
48switchport general allowed vlan add xxxx
49switchport general allowed vlan add 300 tagged
50switchport general allowed vlan remove 1
51lldp transmit-tlv port-desc sys-name sys-desc sys-cap
52lldp transmit-mgmt
53lldp notification
54exit
1.2.2Physical configuration
This setup will give the user 1 admin node and 5 compute/storage nodes. There will be 30TB (10 TB usable with a replication factor of 3) of storage and 40 CPU cores. This is done by:
?One 42U rack
?Dell Power Connect 6248
?1U horizontal cable management
?C6100C 2 sled nodes
? 2 PDUs
Typical Install Solution (rear):
1.2.3Single rack expansion from Starter Solution
You can build the solution to a full rack of nodes to give a total storage of 180 TB (90 TB usable with a replication factor of 3) across 360 Spindles and 240 CPU cores. This configuration gives you 29 Nova and/or Swift nodes and one (1) admin node. You would add:
?12 C6100C 2 Sled Nodes (7.2TB /Sled)
? 2 PDUs
?Additional cable management
This would appear as in the following diagram (original sleds shaded):
1.2.4Multi Rack Expansion
Expand the solution further by adding EOR 10 GbE switches and additional racks or equipment. The networking would need to use one the various hyperscale networking deployments using multiple 10GB LAGs between each of the racks. This will not be covered in the Deployment Guide.
1.3
Installing admin node OS
To use Crowbar, you must first install an admin node. Installing the admin node involves installing the base operating system, optionally customizing the Crowbar configuration, and installing Crowbar itself. The first step is to bootstrap the admin node by PXE booting:
1.The user is expected to make the physical arrangements to connect this VM to the network such
that the machine to be used as the admin node can PXE boot from it. A network crossover cable might be required.
2. A VM image with an initial TFTP/DHCP/boot-server is provided. VMware Player is required to
execute it. VMware Player may be freely downloaded from VMware’s website.
When prepared, install the admin node. (The following steps assume use of a laptop to run VMware Player.)
1.Make sure you have VMware Player installed on the laptop.
2.Open the VMware machine configuration distributed with Crowbar (this will be a .vmx file).
3.Edit the machine settings within Player and ensure that the network adapter is configured to
use Bridged Networking (see images below).
4.Obtain the ISO distribution of Crowbar and configure Player to mount it as a DVD in the VM.
5.Plug the Crossover Cable into eth0 of the server and connect it to the network port of the
laptop.
6.Start the VM – it should present a login prompt in under a minute.
7.Power on the admin node, and ensure that:
a.It is set up to boot from the hard disk for subsequent boots
b.This first boot (and only this first boot) is a network boot
8.Once the installation is complete power down the installer VM.
The machine should obtain its image from the VM and start the installation process.
VMware Player configuration for DVD:
VMware Player configuration for network adapter:
1.4
Installing Crowbar
The image installed in the previous steps includes all the required Crowbar components. Before actually installing Crowbar, the user may customize the installation to fit their deployment environment (see accompanying documentation). The steps below assume use of the default configuration.
1.Log onto the admin node. The default username is openstack, password: openstack.
2.If necessary edit the file /opt/dell/chef/data_bags/crowbar/ bc-template-network.json to
customize the network information for the deployment. The networks cannot be reconfigured once the system is installed.
Network configuration options are:
Name Default Description
mode single A string value of either single, dual, or team. This specifies the default network interface construction model.
teaming map A map of values specific to teaming
networks map A map of networks that this barclamp should manage
The teaming sub-parameters are:
The system provides the following default networks.
Name Usage Notes
admin Private network for node
to node communication A router, if wanted, is external to the system. This network must be owned by the crowbar system to run DHCP on.
bmc Private network for bmc
communication This can be the same as the admin network by using the ranges to limit what IP goes where. A router, if wanted, is external to the system.
bmc_vlan Private network for admin
nodes on the bmc network This must be the same as the bmc network and have the same vlan. This will be used to generate a vlan tagged interface on the admin nodes that can access the bmc lan.
storage Private network for
storage traffic
A router, if wanted, is external to the system
public Public network for
crowbar and other
components
A router, if wanted, is external to the system.
nova_fixed Public network for nova
Virtual Machines The nova-network node acts as a router. This must be completely owned by the nova system.
nova_floating Broken deprecated - most likely to be replaced by nova config. Each network has the following parameters:
Name Default Description
vlan Integer The vlan to use on the switch and interfaces for this network
use_vlan true A value of true indicates that the vlan should applied to the interface. A value
of false assumes that the node will receive untagged traffic for this network. add_bridge false indicates if the network should have a bridge built on top of it. The bridge will be br. This is mostly for Nova compute.
subnet IP
The subnet for this network
Address
netmask Netmask The netmask for this network
router IP
The default router for this network
Address
The default broadcast address for this network
broadcast IP
Address
ranges map This contains a map of strings to start and stop values for network. This allows
for sub-ranges with the network for specific uses. e.g. dhcp, admin, bmc,
hosts.
The range map has a string key that is the name and map defining the range.
Name Type Description
start IP Address First address in the range, inclusive
end IP Address Last address in the range, inclusive
3. cd /tftpboot/ubuntu_dvd/extra
4. sudo ./install https://www.wendangku.net/doc/ac17658925.html,
The rest of the installation is automated and will take a little while to complete.
Enabling the Public Network Port on the Admin Server
1.5
It may be desirable to enable an interface in order to allow external access to the to the admin server. On possible requirement for this would be that the user requires external DNS or NTP servers to interact with the environment. In order to accomplish this please run the following commands from the cmd line on the Admin server after performing the install. The variable
1.Log onto the admin node. The default username is openstack, password: openstack.
2.sudo su –
3.crowbar network allocate_ip default "
4.knife ssh "name:'
1.6
Verifying admin node state
When the admin node finishes installation, it will remain at a shell prompt. At this point, all Crowbar services have started. Consult the table below to access these services.
Crowbar UI http://192.168.124.10:3000/crowbar / crowbar
Nagios http://192.168.124.10/nagios3 nagiosadmin / password
Logging into the UI requires acceptance of the EULA. It can be found on the Dashboard under EULA, in Appendix A of this document or at this web page:
https://www.wendangku.net/doc/ac17658925.html,/content/topics/global.aspx/policy/en/policy?c=us&l=en&s=gen&~section=015#dsl a
Installing nodes
1.7
Nodes are installed automatically when they are first powered up. The machine will be PXE booted by the admin node. It will then proceed to go through several installation phases (involving several automatic reboots) culminating in the deployment of a minimal OS image installed on its local drive. Part of the basic installation incl udes “hooking” the nodes int o the infrastructure services: NTP, DNS, Nagios, and Ganglia.
After the installation process, the node should be listed in the Crowbar UI. From the UI, a node can be powered on and off, rebooted, and reconfigured (see accompanying documentation for details). Functional components are installed on nodes by including them in one or more proposals. For example, when a node is listed as a storage node in a proposal for Swift, the relevant packages, services and settings are deployed to that node upon committing the proposal within Crowbar.
2Installing components
The general workflow to install any component (e.g. Nova, Swift) is the same:
a.Obtain a default proposal which includes the parameters for the component and a mapping of
nodes to the roles they are assigned
b.If desired, edit the proposal for a custom configuration
c.Save the proposal to Crowbar
https://www.wendangku.net/doc/ac17658925.html,mit the proposal
This may be done through the use of the Crowbar command line tool or the web based UI. The sections that follow use the command line tool: /opt/dell/bin/crowbar (for details on using the UI, see the Crowbar Users Guide).
When using the crowbar tool on the admin node, the user may first have to set the following
environment variable:
export CROWBAR_KEY=`cat /etc/crowbar.install.key`
If on a non-admin node, one may also use:
export CROWBAR_KEY=crowbar:crowbar (the default username/password)
Example: Implementing a Proposal via Cmd. Line
2.1
You must be root in order to run the crowbar command
2.1.1Obtain a proposal
Crowbar will inspect the current known nodes and provide a proposal that it believes will best utilize available systems for the component being installed. To obtain and inspect this proposed configuration:
/opt/dell/bin/crowbar
/opt/dell/bin/crowbar
Where:
?
?
i.e. if 2 swift clusters are being installed, the proposals for each should have unique names. They
need not be unique between components of different types
?
2.1.2Update a proposal
The local file created above can be inspected and modified. Common changes include:
?Changing default passwords and other Barclamp parameters (e.g. Swift replica count)
?Changing the assignment of machines to roles
Once edits are completed, crowbar must be updated. To update Crowbar with a modified proposal:
/opt/dell/bin/crowbar
where the parameters in this command are the same as mentioned above. Crowbar will validate the proposal for syntax and make some basic sanity checks as part of this process.
2.1.3Committing proposal
Once the proposal content is satisfactory, the Barclamp instance can be activated:
/opt/dell/bin/crowbar
This might take a few moments, as Crowbar is deploying the required software to the machines mentioned in the proposal.
2.1.4Modifying an active configuration
When committing a proposal which was previously committed, Crowbar compares the new configuration to the currently active state and applies the deltas.
To force crowbar to reapply a proposal, the active state needs to be deleted via:
/opt/dell/bin/crowbar
Then commit the proposal again as described above.
3Appendix A: End User License Agreement
DELL SOFTWARE LICENSE AGREEMENT
This is a legal agreement ("Agreement") between you, the user, and Dell Products L.P or Dell Global B.V. ("Dell"). This Agreement covers all software that is distributed with or for the Dell product (and upgrades and updates thereto), for which there is no separate license agreement between you and the manufacturer or owner of the software (collectively the "Software"). This Agreement is not for the sale of Software or any other intellectual property. All title and intellectual property rights in and to Software is owned by the manufacturer or owner of the Software. All rights not expressly granted under this Agreement are reserved by the manufacturer or owner of the Software. By opening or breaking the seal on the Software packet(s), installing or downloading the Software, or using the Software that has been preloaded or is embedded in your product, you agree to be bound by the terms of this Agreement. If you do not agree to these terms, promptly return all Software items (media, written materials, and packaging) and delete any preloaded or embedded Software.
You may use one copy of the Software on only one Dell computer or device at a time. If you have multiple licenses for the Software, you may use as many copies at any time as you have licenses. "Use" means loading the Software in temporary memory or permanent storage on the computer or device. Installation on a network server solely for distribution to other computers or devices is not "use" if (but only if) you have a separate license for each computer or device to which the Software is distributed. You must ensure that the number of persons using the Software installed on a network server does not exceed the number of licenses that you have. If the number of users of Software installed on a network server will exceed the number of licenses, you must purchase additional licenses until the number of licenses equals the number of users before allowing additional users to use the Software. If you are a commercial customer of Dell or a Dell affiliate, you hereby grant Dell, or an agent selected by Dell, the right to perform an audit of your use of the Software during normal business hours, you agree to cooperate with Dell in such audit, and you agree to provide Dell with all records reasonably related to your use of the Software. The audit will be limited to verification of your compliance with the terms of this Agreement.
The Software is protected by United States and other applicable copyright laws and international treaties. You may make one copy of the Software solely for backup or archival purposes or transfer it to a single hard disk or storage device provided you keep the copy solely for backup or archival purposes. You shall reproduce and include copyright and other proprietary notices on and in any copies for the Software. You may not sublicense, rent or lease the Software or copy the written materials accompanying the Software, but you may transfer the Software and all accompanying materials on a permanent basis as part of a sale or transfer of the Dell product if you retain no copies and the recipient agrees to the terms hereof. Any transfer must include the most recent update and all prior versions. You may not reverse engineer, decompile or disassemble, modify or create derivative works of the Software. If the package accompanying your computer or device contains optical discs, or other storage media, you may use only the media appropriate for your computer or device. You may not use the optical discs or storage media on another computer, device or network, or loan, rent, lease, or transfer them to another user except as permitted by this Agreement.
LIMITED WARRANTY
Dell warrants that the Software media will be free from defects in materials and workmanship under normal use for 90 days from the date you receive them. This warranty is limited to you and is not transferable. Any implied warranties are limited to 90 days from the date you receive the Software. Some jurisdictions do not allow limits on the duration of an implied warranty, so this limitation may not apply to you. The entire liability of Dell and its suppliers, and your exclusive remedy, shall be, at Dell's option, either (a) termination of this Agreement and return of the price paid for the Software or (b) replacement of any media not meeting this warranty that is sent with a return authorization number to Dell, within the 90 day warranty period, at your cost and risk. This limited warranty is void if any media damage has resulted from accident, abuse, misapplication, or service or modification by someone other than Dell. Any replacement media is warranted for the remaining original warranty period or 30 days, whichever is longer.
Dell and its suppliers do NOT warrant that the functions of the Software will meet your requirements or that operation of the Software will be uninterrupted or error free. You assume responsibility for selecting the Software to achieve your intended results and for the use and results obtained from the Software.
DELL, ON BEHALF OF ITSELF AND ITS SUPPLIERS, DISCLAIMS ALL OTHER WARRANTIES, EXPRESS, IMPLIED, OR OTHERWISE, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE OR ANY WARRANTY REGARDING TITLE OR AGAINST INFRINGEMENT, FOR THE SOFTWARE AND ALL ACCOMPANYING WRITTEN MATERIALS. THIS LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS; YOU MAY HAVE OTHERS, WHICH VARY FROM JURISDICTION TO JURISDICTION.
IN NO EVENT SHALL DELL OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF USE OR INABILITY TO USE THE SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME JURISDICTIONS DO NOT ALLOW AN EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
OPEN SOURCE SOFTWARE
A portion of the Software may contain or consist of open source software, which you can use under the terms and conditions of the specific license under which the open source software is distributed.
THIS OPEN SOURCE SOFTWARE IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL, BUT IS PROVIDED "AS IS" WITHOUT ANY WARRANTY, EXPRESS,IMPLIED OR OTHERWISE, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE OR ANY WARRANTY REGARDING TITLE OR AGAINST INFRINGEMENT. IN NO EVENT SHALL DELL, THE COPYRIGHT HOLDERS, OR THE CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTUTUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED 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 OPEN SOURCE SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
U.S. GOVERNMENT RESTRICTED RIGHTS
The software and documentation are "commercial items" as that term is defined at 48 C.F.R. 2.101, consisting of "commercial computer software" and "commercial computer software documentation" as such terms are used in 48 C.F.R. 12.212. Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4, all U.S. Government end users acquire the software and documentation with only those rights set forth herein. Contractor/manufacturer is Dell Products L.P., One Dell Way, Round Rock, Texas 78682.
GENERAL
This license is effective until terminated. It will terminate upon the conditions set forth above or if you fail to comply with any of its terms. Upon termination, you agree that the Software and accompanying materials, and all copies thereof, will be destroyed. This Agreement is governed by the laws of the State of Texas, without regard to principles of conflicts of laws. Each provision of this Agreement is severable. If a provision is found to be unenforceable, this finding does not affect the enforceability of the remaining provisions of this Agreement. This Agreement is binding on successors and assigns. Dell agrees and you agree to waive, to the maximum extent permitted by law, any right to a jury trial with respect to the Software or this Agreement. Because this waiver may not be effective in some jurisdictions, this waiver may not apply to you. You acknowledge that you have read this Agreement, that you understand it, that you agree to be bound by its terms, and that this is the complete and exclusive statement of the Agreement between you and Dell regarding the Software.
SUPPLEMENTAL TERMS FOR EMC SOFTWARE
You may use one copy of the Software on only one computer or device at a time for your own internal business purposes. You shall not, without Dell's prior written consent copy, provide, disclose or otherwise make available Software in any form to anyone other than your employees, consultants or independent contractors who shall use the Software in a manner that is consistent with this Agreement.
Notwithstanding anything to the contrary in the Agreement, licenses to Software are non-exclusive, non-transferable and non-sub licensable and subject to the restriction that the Software be used solely in conjunction with the equipment (storage system or switch/hub) or related central processing unit for which it was licensed.
Rev. 110109
DELL EQUALLOGIC PS SERIES ARRAY END USER LICENSE AGREEMENT
This License Agreement ("Agreement") is made as of the date of shipment of the Products to the Customer (the "Effective Date") by and between Dell, Inc, its subsidiaries and affiliates, with offices at 300 Innovative Way, Suite 301, Nashua, NH 03062 ("collectively "the Company"), and the Customer. In consideration of the mutual obligations set forth below the parties, intending to be legally bound, agree as follows:
1. Definitions
"Customer" means the end user of the Products.
"Hardware" means the Dell EqualLogic PS Series branded array hardware along with any end user manuals supplied by the Company.
"Maintenance Releases" means any update, upgrade, revision, patch, bug fix or an improved, upgraded or enhanced version of the Products released by the Company to which Customer is rightfully entitled by way of a valid maintenance agreement, warranty, or other Company offering. Third Party Products are excluded and subject to their own terms and conditions.
"Object Code" means computer programs assembled, compiled, or converted to magnetic or electronic binary form on software or hardware media, which are readable and usable by computer equipment, but not generally readable
by humans without reverse assembly, reverse compiling, reverse conversion, reverse engineering and/or any other disassembly or decompilation.
"Product(s)" means, collectively, the Hardware and Software which may be supplied to Customer.
"Software" means all components of the Company's storage management software and related documentation made generally available by the Company from time to time not accompanied by its own license agreement. The term "Software" shall include any and all software, scripts, firmware, and microcode running on Hardware or any computer system, including all Maintenance Releases supplied in accordance with this Agreement. The Software shall be provided in Object Code form only. No source code will be provided.
"Third Party Products" means any hardware or software licensed or distributed by the Company to Customer that is not owned by the Company.
2. Grant of License
The Company hereby grants to Customer a nonexclusive, nontransferable license to install and use the Software solely for Customer's ordinary internal business purposes and solely for Software's intended use in conjunction with Product. The Software is in use if it is loaded on the Product or any computer's permanent or temporary memory. Customer may make one copy of the Software for archive and security backup purposes only. You must include on any backup copy all copyright and other notices included on the Software as supplied by the Company. Installation on a network server for the sole purpose of your internal distribution of the Software is permitted so long as all arrays are properly licensed Products to which the Software is distributed. All rights not expressly granted to Customer in this Agreement are reserved by the Company. There are no implied rights. Unless otherwise indicated on the sales quotation, this License is perpetual (subject to termination pursuant to Section 6 below).
3. Payments