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
Foreword | p. xiii |
Preface | p. xv |
1 Introduction | p. 1 |
Problems of today and promise of Grid computing | p. 5 |
A vision of the Grid | p. 6 |
Example 1 Techman runs simulations using on-demand CPU-hours | p. 6 |
Example 2 HydroTech offers secure, remote processing of sensitive data | p. 9 |
Example 3 InvestIT automatically acquires information on foreign markets for niche customers | p. 10 |
The feel of the Grid today | p. 12 |
Google and the World Wide Web | p. 13 |
Travelocity, Sabre, and Global Distribution Systems | p. 17 |
Summary | p. 23 |
2 The Basics | p. 25 |
This chapter in two paragraphs | p. 25 |
Scientific roots | p. 26 |
Early proto-grids (meta-computers) | p. 29 |
Noncomputational resources | p. 33 |
Virtualization | p. 35 |
Note on the term virtualization | p. 37 |
Scientific roots: Summary | p. 37 |
Business perspective | p. 38 |
Standing on the shoulders of giants | p. 38 |
Web services | p. 39 |
Service-oriented architecture | p. 39 |
Today's Web services are not enough | p. 40 |
The prospect of utility computing | p. 41 |
Business meets academia | p. 42 |
WS-Resource Framework | p. 44 |
Note on the term Grid service | p. 45 |
The meaning of WSRF | p. 45 |
Note: OGSI, the predecessor to WSRF | p. 46 |
Virtual organization | p. 47 |
Security for virtual organizations | p. 48 |
The case for Open Grid Service Architecture | p. 50 |
OGSA services: Overview | p. 53 |
Virtual organization | p. 53 |
Composition, grouping, orchestration, workflow | p. 53 |
Transactions | p. 54 |
Metering, accounting, and billing | p. 54 |
Installation, deployment, provisioning | p. 54 |
Application contents | p. 54 |
Information and monitoring | p. 55 |
Logging | p. 55 |
Messaging | p. 55 |
Security | p. 55 |
Policy | p. 56 |
Data | p. 56 |
Program execution | p. 56 |
Grid computing defined and redefined | p. 57 |
Note on spelling of "grids," "Grid," and "Grid computing" | p. 60 |
Disagreement on the definitions | p. 60 |
Cluster of clusters | p. 61 |
Cycle scavenging | p. 61 |
Grid versus distributed computing | p. 61 |
Grid versus Web services | p. 62 |
Grid versus peer-to-peer (P2P) | p. 62 |
Other definitions of Grid computing | p. 63 |
Will there be the Grid? | p. 63 |
3 Grid Computing Enters Business | p. 65 |
How the market understands grids | p. 66 |
Departmental grids | p. 66 |
Enterprise grids | p. 68 |
Partner grids | p. 69 |
Open grids and the Grid | p. 70 |
Taxonomy summary | p. 71 |
What is the market? | p. 72 |
The educational and public research market | p. 72 |
Engineering and manufacturing | p. 73 |
Life sciences | p. 73 |
Financial sector | p. 74 |
The future market | p. 74 |
How can market segmentation hamper open grids? | p. 74 |
Case study: The MCNC Enterprise Grid | p. 76 |
Service | p. 77 |
Customers | p. 78 |
Financials | p. 79 |
Resources | p. 80 |
Location | p. 81 |
Who is who: The ecosystem of the Grid | p. 82 |
Standard bodies and consortia | p. 83 |
Academic projects and groups of interest | p. 84 |
Large vendors | p. 85 |
Grid-specializing vendors and niche vendors | p. 86 |
Application vendors | p. 87 |
Vendor taxonomy according to the 451 | p. 88 |
Grid resource providers | p. 88 |
Consultants | p. 89 |
Media and other information providers | p. 90 |
The panorama of today's products | p. 90 |
Distributed resource management | p. 91 |
SUN N1 Grid Engine family | p. 91 |
LSF Suite from Platform Computing | p. 92 |
Service containers and hosting environments | p. 94 |
Note on service containers, server containers, and service provisioning systems | p. 95 |
Globus Toolkit 4 Grid service container | p. 95 |
Portals and end-user interfaces to the Grid | p. 97 |
Security solutions | p. 98 |
Data solutions | p. 99 |
Avaki | p. 99 |
Applications | p. 101 |
Case Study: The NEESgrid cyberinfrastructure | p. 101 |
Technical overview | p. 103 |
Hardware | p. 105 |
Software | p. 106 |
Planning the communication with users | p. 106 |
Testing and quality management | p. 108 |
Accomplishments | p. 109 |
Summary | p. 109 |
4 Joining the Grid | p. 111 |
Strategies for participating | p. 113 |
What does it mean to "plug in"? | p. 114 |
Build an enterprise grid | p. 114 |
Case study: Wachovia's Grid-powered trade floor | p. 116 |
Business case | p. 117 |
Transition | p. 117 |
Applications | p. 118 |
Standards | p. 119 |
Summary | p. 119 |
Participate in a partner grid | p. 120 |
Join the industry-wide Grid as end-user | p. 123 |
Case study: Synopsys: Software release engineering on the Grid | p. 125 |
Deploy monitoring before transition | p. 127 |
The transition | p. 127 |
Technology | p. 129 |
Problems | p. 130 |
Summary | p. 131 |
What does it mean to provide a Grid-enabled solution? | p. 131 |
Become a Grid infrastructure provider | p. 131 |
Become a service provider on the Grid | p. 134 |
Provide a Grid-enabled product | p. 136 |
Refactor application for horizontal scalability and on-demand business model | p. 136 |
Refactor applications for Grid-compliant connectivity | p. 138 |
Become a middleware vendor | p. 140 |
Case study: Rolls-Royce and Data Systems & Solutions develop grid for Equipment Health Monitoring | p. 141 |
The support services model | p. 141 |
Data systems & solutions | p. 142 |
Equipment Health Monitoring (EHM) problem description | p. 143 |
DAME | p. 146 |
Generalization | p. 146 |
Analysis | p. 147 |
Summary | p. 149 |
5 Technical Issues | p. 151 |
High-level system design | p. 151 |
Organizational security requirements and firewalls | p. 152 |
Data sensitivity | p. 154 |
CPU peak requirements and duty cycles | p. 155 |
Data storage | p. 156 |
Internet bandwidth availability | p. 157 |
Existing resources | p. 159 |
Custom resources | p. 160 |
Potential for porting | p. 162 |
Side trip: Analogies | p. 163 |
The Web | p. 163 |
Peer to Peer | p. 164 |
CORBA, DCOM | p. 164 |
Technology Areas | p. 165 |
Data management and databases | p. 165 |
Secure remote access | p. 166 |
Taking advantage of clusters | p. 167 |
Secure delegation | p. 167 |
Federated databases | p. 167 |
Storage management | p. 169 |
Resource management | p. 173 |
Supercomputers | p. 174 |
Clusters and farms | p. 175 |
On-demand CPU resources | p. 175 |
Workflow management | p. 176 |
Guaranteed execution | p. 177 |
Security | p. 177 |
Internal versus external security | p. 178 |
Techman case revisited | p. 179 |
Feasibility study | p. 182 |
Authorization scalability and federations | p. 183 |
Other security concerns | p. 185 |
Pragmatic view | p. 185 |
Other Grid security solutions | p. 186 |
Where do the standards go? | p. 188 |
Security summary | p. 189 |
6 Management Issues | p. 191 |
Building and selling Grid business case | p. 191 |
Identify problems to solve | p. 193 |
Marketing mix | p. 196 |
Product and product differential advantage | p. 196 |
Price | p. 198 |
Promotion | p. 201 |
Place (channels) | p. 202 |
Press | p. 203 |
Events | p. 204 |
Partnering | p. 205 |
SWOT matrix | p. 206 |
Strengths | p. 206 |
Weakness | p. 206 |
Opportunities | p. 207 |
Risks | p. 207 |
Change and transition period management | p. 207 |
Change driven by technology | p. 208 |
Change driven by organization | p. 208 |
Change resulting from introduction of new products | p. 209 |
Change readiness | p. 209 |
Identify charismatic leaders | p. 209 |
Motivate people | p. 210 |
Minimize hierarchy | p. 210 |
Planning the change | p. 211 |
Engage team to identifying solutions | p. 211 |
Construct the vision shared by everyone | p. 212 |
Build a sensible deployment plan | p. 212 |
Start transition from peripheries and let it radiate | p. 213 |
Adjust strategy to the observed transition process | p. 213 |
Address human factor | p. 213 |
Single change versus constant change | p. 214 |
Migrate in three stages | p. 214 |
Scale up the pilot system | p. 215 |
Internal change first, external later | p. 215 |
Role of consultants | p. 215 |
Do you need a consultant? | p. 216 |
Precisely Define the consultant's mission | p. 217 |
Understand the interest of the consultant | p. 217 |
Be actively involved in the mission | p. 217 |
Engage external resources for diagnosis | p. 218 |
Gradually transfer responsibilities | p. 218 |
Be prepared to take over | p. 218 |
Risk mitigation | p. 218 |
Execution risk management: the traditional approach | p. 219 |
Risk identification | p. 219 |
Risk quantification | p. 220 |
Risk response development | p. 220 |
Risk response control | p. 220 |
Fighting white space risk through rapid-result initiatives | p. 221 |
Result-oriented | p. 222 |
Vertical | p. 222 |
Fast | p. 223 |
Independent | p. 223 |
White space in the Grids sector | p. 223 |
Focus on selected elements of SOA | p. 224 |
Run the complete system for a short while | p. 224 |
Build complete microscale system | p. 225 |
Agile development | p. 225 |
Anticipate shift of requirements | p. 227 |
Refactor rather than design in advance | p. 228 |
Engage developers in decision making | p. 228 |
Code is the documentation | p. 229 |
Pair programming | p. 230 |
Test-driven programming | p. 231 |
Institutionalize the process | p. 232 |
The Globus Campaign System | p. 232 |
Treat customers as partners | p. 233 |
Treat developers as partners | p. 234 |
Summary | p. 235 |
Afterword | p. 237 |
Index | p. 239 |