CHAPTER: 06 Anatomy of the Grid

Key Components

Portal/user interface

Grid Computing

Key Components

Security
Grid Security Infrastructure (GSI)

Grid Computing

Key Components

Broker
Monitoring and Discovery Service (MDS)

Grid Computing

Key Components

Scheduler

Grid Computing

Key Components

Data management
Grid Access to Secondary Storage (GASS)

Grid Computing

Key Components

Job and resource management

Grid Resource Allocation Manager (GRAM)

Grid Computing

Virtual Organization

Virtual organization A set of individuals and/or institutions defined by such sharing rules. In other words, VOs are dynamic federations of heterogeneous organizational entities sharing data, metadata, processing and security infrastructure

VOs vary tremendously, but underlying technology requirements leads us to identify a broad set of common concerns and requirements.

Continued

highly flexible sharing relationships sophisticated and precise levels of control over how shared resources are used sharing of varied resources diverse usage modes current technology either does not accommodate the range of resource types or does not provide the flexibility and control on sharing relationships needed to establish VOs.

Continued

Resource sharing properties

Resource sharing is conditional Sharing relationships can vary dynamically over time

Sharing relationships may be combined to coordinate use across many resources

The same resource may be used in different ways

The nature of Grid Architecture

Interoperability is the central issue

Protocol Architecture & services

API and SDK

Grid Architecture

Hourglass Model In our architecture, the neck of the hourglass consists of Resource and Connectivity protocols which facilitate the sharing of individual resources Protocols are designed so that they can be implemented on top of a diverse range of resource types, defined at the Fabric layer can in turn be used to construct a wide range of global services and application-specific behaviors at the Collective layer

Five layered Grid Architecture

Layers

Fabric Layer Interface to local control

Abstraction of underlying systems, data, resources

Fabric components implement the local, resourcespecific operations that occur on specific resources (whether physical or logical) as a result of sharing operations at higher levels If we place few demands on Fabric elements, then deployment of Grid infrastructure is simplified

Fabric Layer continued Resource mechanisms

Minimum : Inquiry & resource management

mechanism

Computational resources- start/end/monitor & control Storage resources- putting and getting files Network resources-managing network transfer Code repositories-managing versioned codes Catalogs- Query and Update

Globus Toolkit

designed to use existing fabric components if a vendor does not provide the necessary Fabriclevel behavior, the Globus Toolkit includes the missing functionality

Connectivity Layer communicating easily/securely

This is where the security comes in. defines core communication and authentication protocols required for Grid-specific network transactions Communication: transport, routing, and naming: based on TCP/IP stack Authentication: Single sign on, Delegation, Integration with various local security solutions, Userbased trust relationships

Globus Toolkit

The Internet protocols are used for communication (GSI) protocols are used for authentication, communication protection, and authorization GSI builds on and extends the Transport Layer Security (TLS) protocols to address delegation, integration with various local security solutions and user-based trust relationships.

Resource Layer sharing single resources

these protocols call Fabric layer functions to access and control local resources. secure negotiation, initiation, monitoring, control, accounting & payment of sharing operations on individual resources. Manages and provides APIs & SDKs to each available grid resources. concerned entirely with individual resources Two primary classes of Resource layer protocols

Information protocols

Management protocols

Globus Toolkit

GRIP GRRP

GRAM
GridFTP LDAP as a catalog access protocol.

Resource and Connectivity protocol layers form the neck of our hourglass model, and as such should be limited to a small and focused set. These protocols must be chosen so as to capture the fundamental mechanisms of sharing across many different resource types (for example, different local resource management systems)

Collective Layer coordinating multiple resources

Components that deal with the coordination and cooperation of many grid resources global in nature and capture interactions across collections of resources.

Collective layer protocols span the spectrum from general purpose to highly application or domain specific
Collective functions can be implemented as persistent services, with associated protocols, or as SDKs (with associated APIs) designed to be linked with applications.

Continued

Continued

Directory services Co-allocation, scheduling, and brokering services Monitoring and diagnostics services Data replication services Grid-enabled programming systems Workload management systems and collaboration frameworks Software discovery services Community accounting and payment services Collaboratory services

Globus Toolkit

In addition to other services, Meta Directory Service which introduces Grid Information Index Servers (GIISs) to support arbitrary views on resource subsets replica catalog and replica management services to support the management of dataset replicas online credential repository service (MyProxy) for secure storage for proxy credentials DUROC co-allocation library provides an SDK and API for resource co allocation

Application Layer

This is where you use publicly available APIs to interface with underlying infrastructure architecture comprises the user applications that operate within a VO environment

Application programmers view

Grid Architecture in practice

Relationships with Other Technologies

Current distributed computing approaches do not provide a general resource-sharing framework that addresses VO requirements Because of their focus on dynamic, crossorganizational sharing, Grid technologies complement rather than compete with existing distributed computing technologies
WWW Application and Storage Service Providers Enterprise Computing Systems Internet and Peer-to-Peer Computing

WWW

lack features required for the richer interaction models that occur in VOs.

Example: use TLS for authentication, but do not support single sign-on or delegation. the single sign-on capabilities provided in the GSI extensions to TLS would allow for single sign-on to multiple Web servers

Application & storage service providers

VPNs and static configurations make many VO sharing modalities hard to achieve The integration of Grid technologies into ASPs and SSPs can enable a much richer range of possibilities.

Enterprise Computing Systems

Sharing arrangements are typically relatively static and restricted to occur within a single organization. Example: in the case of CORBA, we could construct an object request broker (ORB) that uses GSI mechanisms to address cross-organizational security issues.

Internet & peer-to-peer computing

Lacking common protocols that would allow for shared infrastructure & interoperability sharing targeted by various applications are quite limited

Other Perspectives

The Grid is a next-generation Internet. The Grid is a source of free cycles.

The Grid requires a distributed operating system.

The Grid requires new programming models. The Grid makes high-performance computers superfluous.

Strength & Weakness

Perfect paper for Grid & VO fundamentals Defines what to be done and not how to be done Emphasis on Globus Toolkit, not on other technologies

Questions???