anatomy of grid,advance computing

8/13/2019 Anatomy of Grid,advance computing

1/38

CHAPTER: 06

Anatomy of the Grid


2/38

Grid Computing 2

Key Components

Portal/user interface


3/38

Grid Computing 3

Key Components

Security Grid Security Infrastructure (GSI)


4/38

Grid Computing 4

Key Components

Broker Monitoring and Discovery Service (MDS)


5/38

Grid Computing 5

Key Components

Scheduler


6/38

Grid Computing 6

Key Components

Data management Grid Access to Secondary Storage (GASS)


7/38

Grid Computing 7

Key Components

Job and resource management Grid Resource Allocation Manager (GRAM)


8/38

Virtual Organization Virtual organization

A set of individuals and/or institutions defined by such

sharing rules.

In other words, VOs are dynamic federations ofheterogeneous organizational entities sharing data,metadata, processing and security infrastructure

VOs vary tremendously, but underlying technologyrequirements leads us to identify a broad set ofcommon concerns and requirements.


9/38

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 theflexibility and control on sharing relationships neededto establish VOs.


10/38

Continued


11/38

Resource sharing properties Resource sharing is conditional

Sharing relationships can vary dynamically over time

Sharing relationships may be combined to coordinateuse across many resources

The same resource may be used in different ways


12/38

The nature of Grid Architecture

Interoperability is the central issue

Protocol Architecture & services

API and SDK


13/38

Grid Architecture Hourglass Model

In our architecture, the neck of the hourglass

consists of Resource and Connectivity protocolswhich facilitate the sharing of individual resources

Protocols are designed so that they can beimplemented on top of a diverse range of resourcetypes, defined at the Fabric layer

can in turn be used to construct a wide range ofglobal services and application-specific behaviors atthe Collective layer


14/38

Five layered Grid Architecture


15/38

Layers


16/38

Fabric LayerInterface to local control

Abstraction of underlying systems, data, resources

Fabric components implement the local, resource-specific operations that occur on specific resources(whether physical or logical) as a result of sharingoperations at higher levels

If we place few demands on Fabric elements, thendeployment of Grid infrastructure is simplified


17/38

Fabric Layer continuedResource 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


18/38

Globus Toolkit

designed to use existing fabric components

if a vendor does not provide the necessary Fabric-level behavior, the Globus Toolkit includes themissing functionality


19/38

Connectivity Layercommunicating easily/securely

This is where the securitycomes in. defines corecommunication and authentication protocols requiredfor 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, User-based trust relationships


20/38

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 anduser-based trust relationships.


21/38

Resource Layersharing single resources

these protocols call Fabric layer functions to access andcontrol local resources. secure negotiation, initiation,monitoring, control, accounting & payment of sharing

operations on individual resources.

Manages and provides APIs & SDKs to each availablegrid resources.

concerned entirely with individual resources

Two primary classes of Resource layer protocolsInformation protocols Management protocols


22/38

Globus Toolkit

GRIP

GRRP

GRAM

GridFTP

LDAP as a catalog access protocol.


23/38

Resource and Connectivity protocol layers form theneck of our hourglass model, and as such should belimited to a small and focused set.

These protocols must be chosen so as to capture thefundamental mechanisms of sharing across manydifferent resource types (for example, different localresource management systems)


24/38

Collective Layercoordinating multiple resources

Components that deal with the coordination and cooperation ofmany grid resources

global in nature and capture interactions across collections of

resources.

Collective layer protocols span the spectrum from generalpurpose 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.


25/38

Continued


26/38

Continued

Directory services

Co-allocation, scheduling, and brokering services

Monitoring and diagnostics services

Data replication services

Grid-enabled programming systems

Workload management systems and collaborationframeworks

Software discovery services

Community accounting and payment services

Collaboratory services


27/38

Globus Toolkit

In addition to other services, Meta Directory Servicewhich 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) forsecure storage for proxy credentials

DUROC co-allocation library provides an SDK and APIfor resource co allocation


28/38

Application Layer

This is where you use publicly available APIs tointerface with underlying infrastructure

architecture comprises the user applications thatoperate within a VO environment


29/38

Application programmers view


30/38

Grid Architecture in practice


31/38

Relationships with OtherTechnologies

Current distributed computing approaches do notprovide a general resource-sharing framework thataddresses VO requirements

Because of their focus on dynamic, cross-organizational sharing, Grid technologies complementrather than compete with existing distributedcomputing technologies

WWWApplication and Storage Service ProvidersEnterprise Computing SystemsInternet and Peer-to-Peer Computing


32/38

WWW

lack features required for the richer interactionmodels 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 tomultiple Web servers


33/38

Application & storage service providers

VPNs and static configurations make many VOsharing modalities hard to achieve

The integration of Grid technologies into ASPs andSSPs can enable a much richer range of possibilities.


34/38

Enterprise Computing Systems

Sharing arrangements are typically relativelystatic and restricted to occur within a single

organization.Example:

in the case of CORBA, we could construct anobject request broker (ORB) that uses GSImechanisms to address cross-organizationalsecurity issues.


35/38

Internet & peer-to-peercomputing

Lacking common protocols that wouldallow for shared infrastructure &

interoperability

sharing targeted by various applications

are quite limited


36/38

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 computerssuperfluous.


37/38

Strength & Weakness

Perfect paper for Grid & VOfundamentals

Defines what to be done and not howto be done

Emphasis on Globus Toolkit, not on

other technologies


38/38

Questions???

anatomy of grid,advance computing

Documents