Magellan Final Report - Office of Science - U.S. Department of Energy

More documents

Recommendations

Info

Magellan Final Report QDR links (120 Gb/s) configured as a fully connected mesh topology. This topology is less expensive than a traditional, full fat tree network yet still provides a relatively high bisection bandwidth. In cooperation with vendors, a set of 66 nodes has been equipped in a dual port (IB, 10 GigE) cards and connected through a 10 GigE interface to compare and explore the RoCE protocol performance. A high-performance scalable storage system was also deployed. The storage is configured to run IBM’s high-performance parallel file system, GPFS. The storage hardware consists of four scalable storage units, each with 300 1 TB SATA drives. Each unit is capable of delivering over 5 GB/s of peak bandwidth. There is approximately 240 TB of RAID storage in each scalable unit. The total system provides almost 1 PB of total storage. The existing NERSC SAN was augmented to accommodate the additional storage. Nine Magellan I/O nodes are connected to the SAN and dedicated to providing GPFS services. The file system is mounted across the cluster and service nodes. These file systems are also shared across the center. The service nodes include the network nodes that will be used for testing of the Advanced Networking Initiative (ANI). NERSC also expanded the archival storage system. A Sun (now Oracle) SL8500 library was installed and integrated with three existing SL8500 libraries. Each SL8500 is capable of holding 10,000 tapes. The library also included 35 T10K-C tape drives. The T10K-C can store 1 TB of uncompressed data on a single tape. Consequently, a single SL8500 library can potentially store up to 10 PB of uncompressed data. The hardware is managed by the High-Performance Scalable Storage (HPSS) software [42]. Table 5.2: Node configuration on the NERSC Magellan cluster. There are 720 nodes in the cluster. Feature Description Processor Dual 2.66 GHz Intel Quad-core Nehalem Memory 24 GB (48 GB in 160 nodes) Local Disk 1 TB SATA (in 360 nodes) High Performance Network 40 Gb InfiniBand (4X QDR) Ethernet Network On-board 1 Gb Management IPMI 5.2 Software Flexibility was a major objective in selecting the components of the software stack at the two sites. Since Magellan was to be used to explore a variety of cloud service models and programming models, it was critical that the software stack enable the system to be quickly reconfigured. Both sites used configuration tools often seen in the HPC computing world to provide flexible management of the software stacks. These tools allowed the sites to provision nodes in the cluster from traditional batch environments to Amazon EC2-like models to Hadoop-based MapReduce clusters with the goal of exploring how the software can be used to dynamically re-provision hardware between the different environments based on demand, energy consumption, utilization, as well as other factors. Both sites deployed Hadoop as well. Hadoop has been attracting the attention of multiple scientific communities. From the user survey and discussions with users, Hadoop was cited as an area of high interest. Argonne. The Argonne Magellan testbed uses the Argonne-developed tools bcfg2 [18, 17] and Heckle to provide advanced, bare-metal provisioning (”Hardware as a Service” or HaaS) and configuration management. Heckle allows users to dynamically provision different OS images across raw hardware quickly and easily, providing all the benefits of custom operating systems without the overheads and challenges of virtualizing specialized resources such as accelerators or high-performance networks. Bcfg2 is a system management tool that provides facilities to build sophisticated configurations across large numbers of compute nodes. In the context of providing environments for HPC users on cloud resources, 26
Magellan Final Report Figure 5.2: Photos of the Magellan System at NERSC. The top image shows the overhead cabling system which is suspended from the ceiling to seismically isolate the racks from each other. The lower image shows three racks of compute nodes. The seismic isolation platforms are visible below the racks. 27
Page 1 and 2: The Magellan Report on Cloud Comput
Page 3 and 4: Executive Summary The goal of Magel
Page 5 and 6: Key Findings The goal of the Magell
Page 7 and 8: Magellan Final Report Finding 8. DO
Page 9 and 10: Magellan Final Report role in addre
Page 11 and 12: Contents Executive Summary Key Find
Page 13 and 14: Magellan Final Report 9.7 Discussio
Page 15 and 16: Chapter 1 Overview Cloud computing
Page 17 and 18: Magellan Final Report • The Argon
Page 19 and 20: Chapter 2 Background The term “cl
Page 21 and 22: Magellan Final Report 2.1.4 Hardwar
Page 23 and 24: Magellan Final Report Table 3.1: Ke
Page 25 and 26: Magellan Final Report Little Magell
Page 27 and 28: Magellan Final Report 3.2 Advanced
Page 29 and 30: Chapter 4 Application Characteristi
Page 31 and 32: Magellan Final Report Table 4.1: Pe
Page 33 and 34: Magellan Final Report Output data
Page 35 and 36: Magellan Final Report of the pipeli
Page 37 and 38: Chapter 5 Magellan Testbed As part
Page 39: Magellan Final Report Figure 5.1: P
Page 43 and 44: Magellan Final Report NERSC deploye
Page 45 and 46: Magellan Final Report Figure 6.1: A
Page 47 and 48: Magellan Final Report greater than
Page 49 and 50: Magellan Final Report specific QoS
Page 51 and 52: Magellan Final Report configuration
Page 53 and 54: Magellan Final Report 7.4 Summary U
Page 55 and 56: Magellan Final Report Firewalls are
Page 57 and 58: Magellan Final Report Aside from le
Page 59 and 60: Magellan Final Report 9.1 Understan
Page 61 and 62: Magellan Final Report grid) on 256
Page 63 and 64: Magellan Final Report Table 9.1: HP
Page 65 and 66: Magellan Final Report 25  Ping 
Page 67 and 68: Magellan Final Report 100  12 
Page 69 and 70: Magellan Final Report case of GTC,
Page 71 and 72: Magellan Final Report 1.4 IB TCPo
Page 73 and 74: Magellan Final Report only affects
Page 75 and 76: Magellan Final Report Figure 9.11:
Page 77 and 78: Magellan Final Report charted as a
Page 79 and 80: Magellan Final Report Evaluation Cr
Page 81 and 82: Magellan Final Report Write Perform
Page 83 and 84: Magellan Final Report 3500 3000 G
Page 85 and 86: Magellan Final Report Histogram Plo
Page 87 and 88: Magellan Final Report SATA devices.
Page 89 and 90: Magellan Final Report MB/s Virident
Page 91 and 92:
Magellan Final Report and the perfo
Page 93 and 94:
Magellan Final Report (a) Hosts (b)
Page 95 and 96:
Magellan Final Report Routing IP pa
Page 97 and 98:
Chapter 10 MapReduce Programming Mo
Page 99 and 100:
Magellan Final Report 10.3 Hadoop E
Page 101 and 102:
Magellan Final Report 35000  3500
Page 103 and 104:
Magellan Final Report summarize som
Page 105 and 106:
Magellan Final Report Processing ti
Page 107 and 108:
Magellan Final Report in the networ
Page 109 and 110:
Magellan Final Report Workload Patt
Page 111 and 112:
Magellan Final Report This benchmar
Page 113 and 114:
Magellan Final Report Task Tracker
Page 115 and 116:
Magellan Final Report processing ti
Page 117 and 118:
Magellan Final Report Using ESnet
Page 119 and 120:
Magellan Final Report Figure 11.2:
Page 121 and 122:
Magellan Final Report data collecte
Page 123 and 124:
Magellan Final Report comparison to
Page 125 and 126:
Magellan Final Report 11.2.5 Integr
Page 127 and 128:
Magellan Final Report very large (4
Page 129 and 130:
Magellan Final Report for optimizat
Page 131 and 132:
Magellan Final Report One of the ad
Page 133 and 134:
Magellan Final Report commercial cl
Page 135 and 136:
Magellan Final Report Table 12.2: H
Page 137 and 138:
Magellan Final Report Cost per TF t
Page 139 and 140:
Magellan Final Report Productivity.
Page 141 and 142:
Magellan Final Report compute insta
Page 143 and 144:
Chapter 13 Conclusions Cloud comput
Page 145 and 146:
Magellan Final Report Inherently, t
Page 147 and 148:
Bibliography [1] G. Aldering, G. Ad
Page 149 and 150:
Magellan Final Report [30] I. Foste
Page 151 and 152:
Magellan Final Report [67] M. Palan
Page 153 and 154:
Appendix A Publications Selected Pr
Page 155 and 156:
Magellan Final Report Magellan Rese
Page 157 and 158:
Magellan Final Report Selected Mage
Page 159 and 160:
Appendix B Surveys B1
Page 161 and 162:
• Nuclear Physics - Accelarator P
Page 163 and 164:
Allow users to edit responses. What
Page 165 and 166:
Amazon Eucalyptus OpenStack Other:
Page 167 and 168:
Please list any publications/report
Page 169 and 170:
Hadoop Streaming Hadoop Native Prog
show all

Magellan Final Report - Office of Science - U.S. Department of Energy

Create successful ePaper yourself

Delete template?

Save as template?