# Presentation: 388208

## Resource Management:The Globus Approach

- Ian Foster
- Argonne National Laboratory
- University of Chicago

## What Should Middleware Look Like?

- Grid Fabric
- Layer
- (Underware)

- Grid Services
- Layer
- (Middleware)

- Application
- Adaptation Layer
- (Upperware)

- Applications

- ...

- _Dist. Computing_

- _Remote Instr._

- _Collaboration_

- PVM
- Condor    DSM
- Network solvers
- etc.   etc.   etc.

- Shared state
- CAVERNsoft
- Group security

- Information services         Policy negotiation
- Co-reservation/co-allocation     Grid Security Infrastructure
- Accounting       Event model      Checkpointing     Message Passing
- Remote data access     Fault detection     Monitors
- (Real-time) CORBA     Scheduling       Agent technology

- IP       Multicast protocols    Name servers    HTTP
- Bandwidth broker      CPU schedulers   PKI    Site accounting
- Directory service     OS bypass

- Microscopy

- Astronomy

- Medical

- ..

- ..

- ..

- Remote control
- Online archive
- Online reconstr.
- etc.   etc.   etc.

- Simulation

- Param study

- Data analysis

## Resource Management for Grids

- Goal: an integrated resource management infrastructure that supports
- End-to-end QoS for high-performance (grid) applications
- Application-level specification of QoS requirements
- Application-level monitoring and adaptation

## Challenges

- Advance reservation
- Because resources can be in high demand
- Co-allocation of sets of resources
- End-to-end QoS involves multiple resources
- Heterogeneous resource types
- Networks, computers, instruments, etc.
- Resources in multiple domains
- Reservation/allocation process can require understanding of local mechanisms, policy

## Example: Online Data Analysis

- MPP1

- MPP2

**Notes:**
This slide looks much better as a slide show!
It introduces the concept that the concept of “co-allocation” as found in GRAM now needs to apply both to “co-reservation” and “co-creation”.
The example shows how a user needing to connect a scientific instrument to a visualization device contacts a broker, which selects from among the two possible sets of resources, returning a set of reservations that will allow one of these to be used.
A reservation co-allocator is used to reserve the resources, returning a set of ResHandles.
An object creation co-allocator is used to create the network and process objects.
Finally, an online monitor watches performance, and may decide (as shown here) to increase a network reservation at a later time.

## Globus Architecture For Reservation and Allocation

## Example: Online Data Analysis

- MPP1

- MPP2

- G

- G

- G

- G

- G

- G

- G

- a

- b

- d

- c

- Information
- Service

**Notes:**
This slide looks much better as a slide show!
It introduces the concept that the concept of “co-allocation” as found in GRAM now needs to apply both to “co-reservation” and “co-creation”.
The example shows how a user needing to connect a scientific instrument to a visualization device contacts a broker, which selects from among the two possible sets of resources, returning a set of reservations that will allow one of these to be used.
A reservation co-allocator is used to reserve the resources, returning a set of ResHandles.
An object creation co-allocator is used to create the network and process objects.
Finally, an online monitor watches performance, and may decide (as shown here) to increase a network reservation at a later time.

## GARA Status

- Currently deployed system supports discovery and co-allocation of computers
- Prototype supports advance reservation of networks and computers
- Parallel computers (SMP)
- CPU fraction via Nahrstedt’s DSRT
- Networks via IntServ (SCRAPI)
- Application-driven deployment and evaluation will begin soon
- In context of DiffServ (see W. Johnston)