Chapter 1: Introduction
Chapter 2: The Basics
Chapter 3: Grid Computing Enters Business
Chapter 4: Joining the Grid
Chapter 5: Technical Issues
Chapter 6: Management Issues

Preface

i. Preface

Chapter 1: Introduction

1.1. Problems of today and promise of Grid computing
1.2. A vision of the Grid
1.2.1. Example 1: Techman runs simulations using on-demand CPU-hours
1.2.2. Example 2: HydroTech offers secure, remote processing of sensitive data
1.2.3. Example 3: InvestIT automatically acquires information on foreign markets for niche customers
1.3. The feel of the Grid today
1.3.1. Google and the World Wide Web
1.3.2. Travelocity, Sabre, and Global Distribution System
1.4. Summary

Chapter 2: The Basics

2.1. This chapter in two paragraphs
2.2. Scientific roots
2.2.1. Early proto-grids (meta-computers)
2.2.2. Noncomputational resources
2.2.3. Virtualization
2.2.3.1. Note on the term virtualization
2.2.4. Scientific Roots: Summary
2.3. Business perspective
2.3.1. Standing on the shoulders of giants
2.3.2. Web services
2.3.3. Service-oriented architecture
2.3.4. Today’s Web services are not enough
2.3.5. The prospect of utility computing
2.4. Business meets academia
2.4.1. WS-Resource Framework
2.4.1.1. Note on the term Grid service
2.4.2. The meaning of WSRF
2.4.2.1. Note: OGSI, the predecessor to WSRF
2.4.3. Virtual organization
2.4.4. Security for virtual organizations
2.4.5. The case for Open Grid Service Architecture
2.4.6. OGSA services—overview
2.4.6.1. Virtual Organization
2.4.6.2. Composition, grouping, orchestration, workflow
2.4.6.3. Transactions
2.4.6.4. Metering, accounting, and billing
2.4.6.5. Installation, deployment, provisioning
2.4.6.6. Application contents
2.4.6.7. Information and monitoring
2.4.6.8. Logging
2.4.6.9. Messaging
2.4.6.10. Security
2.4.6.11. Policy
2.4.6.12. Data
2.4.6.13. Program execution
2.4.7. Grid Computing defined, and redefined
2.4.7.1. Note on spelling of “grids”, “Grid” and “Grid computing”
2.4.8. Disagreement on the definitions
2.4.8.1. Cluster of clusters
2.4.8.2. Cycle scavenging
2.4.8.3. Grid versus Distributed Computing
2.4.8.4. Grid versus Web services
2.4.8.5. Grid versus peer-to-peer (P2P)
2.4.8.6. Other definitions of Grid computing
2.5. Will there be The Grid?

Chapter 3: Grid computing enters business

3.1. How the market understands grids
3.1.1. Departmental grids
3.1.2. Enterprise grids
3.1.3. Partner grids
3.1.4. Open grids and The Grid
3.1.5. Taxonomy summary
3.2. What is the market?
3.2.1. The educational and public research market
3.2.2. Engineering and manufacturing
3.2.3. Life sciences
3.2.4. Financial sector
3.2.5. The future market
3.2.6. How can market segmentation hamper open grids?
3.2.6.1. Case study: The MCNC Enterprise Grid
3.2.7. Service
3.2.8. Customers
3.2.9. Financials
3.2.10. Resources
3.2.11. Location
3.3. Who is who: The ecosystem of the Grid
3.3.1. Standard bodies and consortia
3.3.2. Academic projects and groups of interest
3.3.3. Large vendors
3.3.4. Grid-specializing vendors and niche vendors
3.3.5. Application vendors
3.3.6. Vendor taxonomy according to The 451
3.3.7. Grid resource providers
3.3.8. Consultants
3.3.9. Media and other information providers
3.4. The panorama of today’s products
3.4.1. Distributed Resource Management
3.4.1.1. SUN N1 Grid Engine family
3.4.1.2. LSF Suite from Platform Computing
3.4.2. Service Containers and Hosting Environments
3.4.2.1. Note on service containers, server containers and service provisioning systems
3.4.2.2. Globus Toolkit 4 Grid Service Container
3.4.3. Portals and end-user interfaces to the Grid
3.4.4. Security Solutions
3.4.5. Data Solutions
3.4.5.1. Avaki
3.4.6. Applications
3.5. Case Study: The NEEDS grid cyberinfrastructure
3.5.1. Technical overview
3.5.2. Hardware
3.5.3. Software
3.5.4. Planning the communication w/ users
3.5.5. Testing and quality management
3.5.6. Accomplishments
3.5.7. Summary

Chapter 4: Joining the Grid

4.1. Strategies for participating
4.1.1. What does it mean to “plug in”?
4.1.2. Build an enterprise grid
4.1.3. Case study: Wachovia’s Grid-powered trade floor
4.1.3.1. Business case
4.1.3.2. Transition
4.1.3.3. Applications
4.1.3.4. Standards
4.1.3.5. Summary
4.1.4. Participate in a partner grid
4.1.5. Join the industry-wide Grid as end-user
4.2. Case Study: Synopsys: Software Release Engineering on the Grid
4.2.1. Deploy monitoring before transition
4.2.2. The transition
4.2.3. Technology
4.2.4. Problems
4.2.5. Summary
4.3. What does it mean to provide a Grid-enabled solution?
4.3.1. Become a grid infrastructure provider
4.3.2. Become a service provider on the Grid
4.3.3. Provide a Grid-enabled product
4.3.3.1. Refactor application for horizontal scalability and on-demand business model
4.3.3.2. Refactor applications for Grid-compliant connectivity
4.3.4. Become a middleware vendor
4.4. Rolls-Royce and Data Systems & Solutions develop grid for Equipment Health Monitoring
4.4.1. The Support Services model
4.4.2. Data Systems & Solutions
4.4.3. Equipment Health Monitoring (EHM) Problem Description
4.4.4. DAME
4.4.5. Generalization
4.4.6. Analysis
4.5 Summary

Chapter 5: Technical Issues

5.1. High-level system design
5.1.1. Organizational security requirements and firewalls
5.1.2. Data sensitivity
5.1.3. CPU peak requirements and duty cycles
5.1.4. Data storage
5.1.5. Internet bandwidth availability
5.1.6. Existing resources
5.1.7. Custom resources
5.1.8. Potential for porting
5.2. Side trip: analogies
5.2.1. Web services
5.2.2. Peer to Peer
5.2.3. CORBA, DCOM
5.3. Technology Areas
5.4. Data Management (databases)
5.4.1. Secure remote access
5.4.2. Taking advantage of clusters
5.4.3. Secure delegation
5.4.4. Federated databases
5.4.5. Storage management in workflow management systems
5.5. Resource Management
5.5.1. Supercomputers
5.5.2. Clusters and farms
5.5.3. On-demand CPU resources
5.6. Workflow Management
5.7. Guaranteed Execution
5.7.1. Security
5.7.2. Internal versus External Security
5.7.3. Techman case revisited
5.7.4. Feasibility study
5.7.5. Authorization scalability and federations
5.7.6. Other security concerns
5.7.7. Pragmatic view
5.7.8. Other Grid security solutions
5.7.9. Where do the standards go?
5.7.10. Security summary

Chapter 6: Management issues

6.1. Building and selling Grid business case
6.1.1. Identify problems to solve
6.1.2. Marketing mix
6.1.2.1. Product and product differential advantage
6.1.2.2. Price
6.1.2.3. Promotion
6.1.2.4. Place (channels)
6.1.2.5. Press
6.1.2.5.1. Events
6.1.2.5.2. Partnering
6.1.3. SWOT matrix
6.1.3.1. Strengths
6.1.3.2. Weaknesses
6.1.3.3. Opportunities
6.1.3.4. Risks
6.2. Change and transition period management
6.2.1. Change driven by technology
6.2.2. Change driven by organization
6.2.3. Change resulting from introduction of new products
6.2.4. Change readiness
6.2.4.1. Identify charismatic leaders
6.2.4.2. Motivate people
6.2.4.3. Minimize hierarchy
6.2.5. Planning the change
6.2.5.1. Engage team to identifying solutions
6.2.5.2. Construct the vision shared by everyone
6.2.5.3. Build a sensible deployment plan
6.2.5.4. Start transition from peripheries and let it radiate
6.2.5.5. Adjust strategy to the observed transition process
6.2.5.6. Address human factor
6.2.6. Single change versus constant change
6.2.6.1. Migrate in three stages
6.2.6.2. Scale up the pilot
6.2.6.3. Internal change first, external later
6.3. Role of consultants
6.3.1. Do you need a consultant?
6.3.2. Precise the consultant’s mission
6.3.3. Understand the interest of the consultant
6.3.4. Be actively involved in the mission
6.3.5. Engage external resources for diagnosis
6.3.6. Gradually transfer responsibilities
6.3.7. Be prepared to take over
6.4. Risk Mitigation
6.4.1. Execution risk management: the traditional approach
6.4.1.1. Risk identification
6.4.1.2. Risk quantification
6.4.1.3. Risk response development
6.4.1.4. Risk response control
6.4.2. Fighting white space risk through rapid-result initiatives
6.4.2.1. Result-oriented
6.4.2.2. Vertical
6.4.2.3. Fast
6.4.2.4. Independent
6.4.3. White space in the grids sector
6.4.3.1. Focus on selected elements of SOA
6.4.3.2. Stand up the complete system for a short while
6.4.3.3. Build complete microscale system
6.4.4. Agile development
6.4.4.1. Anticipate shift of requirements
6.4.4.2. Refactor rather than design in advance
6.4.4.3. Engage developers in decision making
6.4.4.4. Code is the documentation
6.4.4.5. Pair programming
6.4.4.6. Test-driven programming
6.4.4.7. Institutionalize the process
6.4.4.8. The Globus Campaign System
6.4.4.9. Treat customers as partners
6.4.4.10. Treat developers as partners
6.5. Summary