The Anatomy of the Grid

1
The Anatomy of the Grid

• Mar 10, 2006
• MPI Seminar
• Distributed Computing Communication Laboratory
• Yun, Hyun jun

2
Outline

• Introduction
• Virtual Organization
• The Nature of Grid Architecture
• Grid Architecture Description
• Relationships with other Technologies
• Other Perspectives on Grids
• Conclusion

3
Introduction

• Motivation
• GRIDs issue is
• Coordinated resource sharing
• Problem solving in dynamic, multi-institutional
  VOs
• Current distributed environments
• Burdensome and inflexible
• Does not accommodate wide range of resource types
• GRID should
• Support Security, resource management, remote
  compute, information query, data locating
  transporting
• Role as a complementer

4
Introduction

• The object of this paper is
• Clarify the nature of VOs and Grid computing
• Defining an overall architectural framework
• Defining how Grid is related to other
  technologies
• So we believe
• VO has potentiality to change the way of problem
  solving around every field

5
Virtual Organization

• Sharing relationships
• Various participants, activities, duration, scale
• Various resources
• Constraints, Security, Dynamicity, Policy,
  Delegating, Coordinating
• Diverse usages

6
The Nature of Grid Architecture

• Issuies on Grid
• How can we increase interoperability
• Protocols, API, SDK Middleware
• In detail
• Interoperability standard protocols syntaxes
• Protocols
• Services
• API SDK

7
Grid Architecture Description

• Overview

8
Grid Architecture Description

• Fabric Layer
• Interfaces to local control
• Tight, subtle interdependence
• Should support enquiry for discovering,
  mornitoring
• Advance Reservation
• Examples
• Computational resources hw, sw info. State
  info.(load, queue state )
• Storage resources load, bandwidth, space
• Network resources network characteristics, load
• Code repositories version data, CVS
• Catalogs query, update operations, RDB

9
Grid Architecture Description

• Connectivity Layer
• Communicating easily and securely
• Transport, routing, naming
• Authentication should follow
• Single sign-on
• Delegation
• Intergration with various local security
  solutions
• User-based trust relationships

10
Grid Architecture Description

• Resource Layer
• Sharing single resources
• Negotiation, initiation, monitoring, control,
  accounting, payment on individual resources
• Ignores global state
• Information protocols obtain information-conf.,
  load, policy
• Management protocols should cover various
  resource types

11
Grid Architecture Description

• Collective Layer
• Coordinating multiple resources
• Highly app. Or domain specific rather than
  general purpose.
• Directory services discovering
• Co-allocation, scheduling, brokering services
• Monitoring and diagnostics services
• Data replication service
• Grid-enabled programming systems
• Workload management systems and collaboration
  framework
• Software discovery service
• Community authorization servers
• Community accounting and payment service
• Collaboratory services

12
Grid Architecture Description
13
Grid Architecture Description

• Application Layer

14
Relationships with other Technologies

• WWW
• TLS only, No single-sign on, delegation
• ASP/SSP
• Static configurations
• Enterprise Computing systems
• Static sharing, sharing in limited domain
• Client-Server interaction
• Internet and P2P Computing
• Vertically integrated
• Target is limited

15
Other Perspectives on Grids

• The Grid is a next-generation Internet
• The Grid is a source of free cycles
• The Grid require a distributed operating system
• The Grid requires new programming models
• The Grid makes high performance computers
  superfluous

16
Conclusion

• GRID issues
• Controlled, coordinated resource sharing
• Use in dynamic, scalable VO
• And we presented requirements/framework
• So, what are the appropriate choices for the
  Protocols?