Cover image for Grid computing : the savvy manager's guide
Title:
Grid computing : the savvy manager's guide
Personal Author:
Publication Information:
San Francisco, CA : Elsevier/Morgan Kaufmann, 2005
ISBN:
9780127425030
Added Author:

Available:*

Library
Item Barcode
Call Number
Material Type
Item Category 1
Status
Searching...
30000010104150 QA76.9.C58 P52 2005 Open Access Book Book
Searching...
Searching...
30000010168953 QA76.9.C58 P52 2005 Open Access Book Book
Searching...

On Order

Summary

Summary

A decade ago, the corporate world viewed grid computing as a curiosity. Today, it views it as an opportunity--a chance to reduce costs, improve performance, fund new projects, and take advantage of under-utilized capacity. The engineering behind this transformation has been amply documented. Until now, however, little has been written to prepare managers, executives, and other decision-makers to implement grid computing in a sensible and effective way.

Grid Computing: The Savvy Manager's Guide examines the technology from a rigorous business perspective, equipping you with the practical knowledge you need to assess your options and determine what grid computing approach is right for your enterprise. This book is heavy on real-world experience, distilling from a rich assortment of case studies the best practices currently at work in a variety of industries. Always attentive to grid computing's many competitive advantages, it is also realistic about the challenges of selling the idea to staff and making it a part of your company's culture.


Author Notes

The American Museum of Natural History in New York City is one of the largest and most respected museums in the world, and welcomes millions of visitors each year. Plan a trip to the museum to see some of its 32 million specimens and artifacts, including the largest collection of dinosaur fossils anywhere, or visit online at www.amnh.org .


Table of Contents

Forewordp. xiii
Prefacep. xv
1 Introductionp. 1
Problems of today and promise of Grid computingp. 5
A vision of the Gridp. 6
Example 1 Techman runs simulations using on-demand CPU-hoursp. 6
Example 2 HydroTech offers secure, remote processing of sensitive datap. 9
Example 3 InvestIT automatically acquires information on foreign markets for niche customersp. 10
The feel of the Grid todayp. 12
Google and the World Wide Webp. 13
Travelocity, Sabre, and Global Distribution Systemsp. 17
Summaryp. 23
2 The Basicsp. 25
This chapter in two paragraphsp. 25
Scientific rootsp. 26
Early proto-grids (meta-computers)p. 29
Noncomputational resourcesp. 33
Virtualizationp. 35
Note on the term virtualizationp. 37
Scientific roots: Summaryp. 37
Business perspectivep. 38
Standing on the shoulders of giantsp. 38
Web servicesp. 39
Service-oriented architecturep. 39
Today's Web services are not enoughp. 40
The prospect of utility computingp. 41
Business meets academiap. 42
WS-Resource Frameworkp. 44
Note on the term Grid servicep. 45
The meaning of WSRFp. 45
Note: OGSI, the predecessor to WSRFp. 46
Virtual organizationp. 47
Security for virtual organizationsp. 48
The case for Open Grid Service Architecturep. 50
OGSA services: Overviewp. 53
Virtual organizationp. 53
Composition, grouping, orchestration, workflowp. 53
Transactionsp. 54
Metering, accounting, and billingp. 54
Installation, deployment, provisioningp. 54
Application contentsp. 54
Information and monitoringp. 55
Loggingp. 55
Messagingp. 55
Securityp. 55
Policyp. 56
Datap. 56
Program executionp. 56
Grid computing defined and redefinedp. 57
Note on spelling of "grids," "Grid," and "Grid computing"p. 60
Disagreement on the definitionsp. 60
Cluster of clustersp. 61
Cycle scavengingp. 61
Grid versus distributed computingp. 61
Grid versus Web servicesp. 62
Grid versus peer-to-peer (P2P)p. 62
Other definitions of Grid computingp. 63
Will there be the Grid?p. 63
3 Grid Computing Enters Businessp. 65
How the market understands gridsp. 66
Departmental gridsp. 66
Enterprise gridsp. 68
Partner gridsp. 69
Open grids and the Gridp. 70
Taxonomy summaryp. 71
What is the market?p. 72
The educational and public research marketp. 72
Engineering and manufacturingp. 73
Life sciencesp. 73
Financial sectorp. 74
The future marketp. 74
How can market segmentation hamper open grids?p. 74
Case study: The MCNC Enterprise Gridp. 76
Servicep. 77
Customersp. 78
Financialsp. 79
Resourcesp. 80
Locationp. 81
Who is who: The ecosystem of the Gridp. 82
Standard bodies and consortiap. 83
Academic projects and groups of interestp. 84
Large vendorsp. 85
Grid-specializing vendors and niche vendorsp. 86
Application vendorsp. 87
Vendor taxonomy according to the 451p. 88
Grid resource providersp. 88
Consultantsp. 89
Media and other information providersp. 90
The panorama of today's productsp. 90
Distributed resource managementp. 91
SUN N1 Grid Engine familyp. 91
LSF Suite from Platform Computingp. 92
Service containers and hosting environmentsp. 94
Note on service containers, server containers, and service provisioning systemsp. 95
Globus Toolkit 4 Grid service containerp. 95
Portals and end-user interfaces to the Gridp. 97
Security solutionsp. 98
Data solutionsp. 99
Avakip. 99
Applicationsp. 101
Case Study: The NEESgrid cyberinfrastructurep. 101
Technical overviewp. 103
Hardwarep. 105
Softwarep. 106
Planning the communication with usersp. 106
Testing and quality managementp. 108
Accomplishmentsp. 109
Summaryp. 109
4 Joining the Gridp. 111
Strategies for participatingp. 113
What does it mean to "plug in"?p. 114
Build an enterprise gridp. 114
Case study: Wachovia's Grid-powered trade floorp. 116
Business casep. 117
Transitionp. 117
Applicationsp. 118
Standardsp. 119
Summaryp. 119
Participate in a partner gridp. 120
Join the industry-wide Grid as end-userp. 123
Case study: Synopsys: Software release engineering on the Gridp. 125
Deploy monitoring before transitionp. 127
The transitionp. 127
Technologyp. 129
Problemsp. 130
Summaryp. 131
What does it mean to provide a Grid-enabled solution?p. 131
Become a Grid infrastructure providerp. 131
Become a service provider on the Gridp. 134
Provide a Grid-enabled productp. 136
Refactor application for horizontal scalability and on-demand business modelp. 136
Refactor applications for Grid-compliant connectivityp. 138
Become a middleware vendorp. 140
Case study: Rolls-Royce and Data Systems & Solutions develop grid for Equipment Health Monitoringp. 141
The support services modelp. 141
Data systems & solutionsp. 142
Equipment Health Monitoring (EHM) problem descriptionp. 143
DAMEp. 146
Generalizationp. 146
Analysisp. 147
Summaryp. 149
5 Technical Issuesp. 151
High-level system designp. 151
Organizational security requirements and firewallsp. 152
Data sensitivityp. 154
CPU peak requirements and duty cyclesp. 155
Data storagep. 156
Internet bandwidth availabilityp. 157
Existing resourcesp. 159
Custom resourcesp. 160
Potential for portingp. 162
Side trip: Analogiesp. 163
The Webp. 163
Peer to Peerp. 164
CORBA, DCOMp. 164
Technology Areasp. 165
Data management and databasesp. 165
Secure remote accessp. 166
Taking advantage of clustersp. 167
Secure delegationp. 167
Federated databasesp. 167
Storage managementp. 169
Resource managementp. 173
Supercomputersp. 174
Clusters and farmsp. 175
On-demand CPU resourcesp. 175
Workflow managementp. 176
Guaranteed executionp. 177
Securityp. 177
Internal versus external securityp. 178
Techman case revisitedp. 179
Feasibility studyp. 182
Authorization scalability and federationsp. 183
Other security concernsp. 185
Pragmatic viewp. 185
Other Grid security solutionsp. 186
Where do the standards go?p. 188
Security summaryp. 189
6 Management Issuesp. 191
Building and selling Grid business casep. 191
Identify problems to solvep. 193
Marketing mixp. 196
Product and product differential advantagep. 196
Pricep. 198
Promotionp. 201
Place (channels)p. 202
Pressp. 203
Eventsp. 204
Partneringp. 205
SWOT matrixp. 206
Strengthsp. 206
Weaknessp. 206
Opportunitiesp. 207
Risksp. 207
Change and transition period managementp. 207
Change driven by technologyp. 208
Change driven by organizationp. 208
Change resulting from introduction of new productsp. 209
Change readinessp. 209
Identify charismatic leadersp. 209
Motivate peoplep. 210
Minimize hierarchyp. 210
Planning the changep. 211
Engage team to identifying solutionsp. 211
Construct the vision shared by everyonep. 212
Build a sensible deployment planp. 212
Start transition from peripheries and let it radiatep. 213
Adjust strategy to the observed transition processp. 213
Address human factorp. 213
Single change versus constant changep. 214
Migrate in three stagesp. 214
Scale up the pilot systemp. 215
Internal change first, external laterp. 215
Role of consultantsp. 215
Do you need a consultant?p. 216
Precisely Define the consultant's missionp. 217
Understand the interest of the consultantp. 217
Be actively involved in the missionp. 217
Engage external resources for diagnosisp. 218
Gradually transfer responsibilitiesp. 218
Be prepared to take overp. 218
Risk mitigationp. 218
Execution risk management: the traditional approachp. 219
Risk identificationp. 219
Risk quantificationp. 220
Risk response developmentp. 220
Risk response controlp. 220
Fighting white space risk through rapid-result initiativesp. 221
Result-orientedp. 222
Verticalp. 222
Fastp. 223
Independentp. 223
White space in the Grids sectorp. 223
Focus on selected elements of SOAp. 224
Run the complete system for a short whilep. 224
Build complete microscale systemp. 225
Agile developmentp. 225
Anticipate shift of requirementsp. 227
Refactor rather than design in advancep. 228
Engage developers in decision makingp. 228
Code is the documentationp. 229
Pair programmingp. 230
Test-driven programmingp. 231
Institutionalize the processp. 232
The Globus Campaign Systemp. 232
Treat customers as partnersp. 233
Treat developers as partnersp. 234
Summaryp. 235
Afterwordp. 237
Indexp. 239