GridScape Ding Choon Hoong Grid Computing and Distributed Systems (GRIDS) Lab. The University of Melbourne Melbourne, Australia WW Grid.

GridScape

Ding Choon HoongGrid Computing and Distributed Systems

(GRIDS) Lab. The University of MelbourneMelbourne, Australiawww.gridbus.org

WW Grid

2

Introduction: Why GridScape?

Grid Computing is gaining popularity Grid testbeds are set up Need a tool to view and monitor testbed

status GridScape assists creation and

administration of web-based portals

3

Why GridScape? (cont’)

Aims of GridScape:- Allow for rapid creation of grid testbed portals Allow for simple portal management &

administration Provide an interactive and dynamic portal Provide a clear and user-friendly overall view of

grid testbed resources Have a flexible design and implementation such

that core components can be leveraged, it provides a high level of portability, and a high level of accessibility

4

Related Work

Application Specific:- GRIDView (static HTML) NorduGrid (Dynamic HTML)

Application Independent (toolkits):- GridPort GPDK Legion Portal

5

GridScape Architecture

GridScape consists of 3 components:- Web Application

- interactive graphical view of resource locations and ability to monitor its status and details

Administration Tool- allow users to customise and update their personal testbed portal

6

GridScape Architecture (cont’)

Interface to Grid Information Service- access MDS to obtain individual grid resource information- low level details (e.g. LDAP protocols) are hidden from users- information obtained are cached to avoid costly continuous querying of distributed resources

7

GridScape Architecture (cont’)

Testbed

AdminTool

Interface to MDS/LDAP

Gridscape

Aggregates Resource Information

WebBrowser

How many CPUs does resource A have?

Which resources have > 4 processors?

WebBrowser

WebBrowser

WebBrowser

Globus GRIS

Grid Node A

IP IP

Grid Node B

IP

Grid Node C

IP IPIP

Globus GRIS Globus GRIS

Web App.

Testbed

AdminTool

Interface to MDS/LDAP

Gridscape

Aggregates Resource Information

WebBrowser

How many CPUs does resource A have?

Which resources have > 4 processors?

WebBrowser

WebBrowser

WebBrowser

Globus GRIS

Grid Node A

IP IP

Grid Node B

IP

Grid Node C

IP IPIP

Globus GRIS Globus GRIS

Web App.

8

Design & Implementation

GridScape web app. Was designed following the MVC (Model-View-Controller) based, Model-2 type

Reason:- To ensure cleaner separation of

presentation from content To ensure that GridScape can be easily

extended to be a large scale project

9

Design & Implementation (cont’)

Web

Browser

Grid

Testbed

Resources

Gridscape Controller

(Framework provided

by STRUTS. manages the flow

of control for the web app.)

View

(JSP – The presentation

layer providing the

interactive web portal)

Model

(Containing

the core

functionality

of Gridscape )

WebBrowser

Grid Testbed

Resources

Gridscape Controller

(Servlet - Framework provided by STRUTS. Manages the flow of

Contol for the web app.)

View

(JSP – The presentation layerproviding the interactive web

Portal)

Model

(Beans – Containing the

Core functionalityOf GridScape))

Web Server running the Gridscape web application

10

Design & Implementation (cont’)

The Model consists of all the core classes that are shared between the web app. and also the admin. Tool

Main class is TestbedManager GridScape maintains only a singleton

instance of the data.

11

Design & Implementation (cont’)

Misc. Gridscape Tool

Gridscape

Web App.

Gridscape

Admin. Tool

SwingComponents

JSP andServlets

Presentation/Application

Layers

Model(core classes)

12

GridScape in Practice

How to create a portal for your own Grid testbed using GridScape:-

1. Deploy the GridScape web app.2. Creating your portal3. Customising your portal

- Changing testbed name, logo and other details- Managing testbed resources

- Adding a new resource- Editing resource details- Deleting an unwanted resource

- Querying testbed resources4. Browsing the testbed portal

13

GridScape in Practice (cont’)

Deploy the GridScape web app. Deploy web app. within Jakarta Tomcat

installation Install the admin. tool

Creating your portal Usage of GridScape is fairly intuitive Need to provide:-

- testbed logo- map (for displaying physical location of resources)- details of resources (e.g. nodes)

14

GridScape in Practice (cont’)

Customising your portal Changing testbed name, logo and other

details:-- customisable from the ‘Options’ menu

15

GridScape in Practice (cont’)

16

GridScape in Practice (cont’)

17

GridScape in Practice (cont’)

Customising your portal (cont’) Managing testbed resources

- GAT provides two modes:-- Editing mode allows user to edit info regarding resources

- Viewing mode allows user to simply browse & query

existing resources

18

GridScape in Practice (cont’)

Customising your portal (cont’) Managing testbed resources

- Adding a new resource:-- simply click the mouse in a vacant

area on the map - a new resource will be created

automatically on the map- click & drag resource to desired

location- supply country name & address of

resource

19

GridScape in Practice (cont’)

20

GridScape in Practice (cont’)

Customising your portal (cont’) Managing testbed resources

- Editing resource details:-- select the resource by clicking

on it- edit details such as name,

address & port- click ‘Update’ button to store

the changes

21

GridScape in Practice (cont’)

Customising your portal (cont’) Managing testbed resources

- Deleting an unwanted resource:-- select unwanted resource- click the ‘Delete Record’

button- Querying testbed resources:-

- select ‘View’ mode- click on the resource

22

GridScape in Practice (cont’)

Customising your portal (cont’) Managing testbed resources

- Browsing the testbed portal:-- testbed details are saved into

a config file and deployed on a web server

- a browser is used to browse and monitor the status of the testbed

23

GridScape in Practice (cont’)

Snapshot of WWG:Global Data Intensive Grid Collaboration Network

24

GridScape in Practice (cont’)

Details of a selected resource appears in a pop-up window

25

GridScape in Practice (cont’)

Only resources running in Linux OS

26

GridScape in Practice (cont’)

Extension to GridScape:- Monitoring status of jobs sent from a

specified broker to the testbed Queries the protocol engine to obtain job

location and execution status

27

GridScape in Practice (cont’)

Admin

Tool

Interface to MDS/LDAP

Web

Browser

How many CPUs

does resource A

have?

Which resources

have > 4

processors?

Web

Browser

Web

Browser

Web

Browser

Globus GRIS

Grid Node A

IP IP

Grid Node B

IP

Grid Node C

IP IPIP

Globus GRIS Globus GRIS

Web App.

Testbed

Admin

Tool

Interface to MDS/LDAP

Aggregates Resource Information

Web

Browser

How many CPUs

does resource A

have?

Which resources

have > 4

processors?

Web

Browser

Web

Browser

Web

Browser

Globus GRIS

Grid Node A

IP IP

Grid Node B

IP

Grid Node C

IP IPIP

Globus GRIS Globus GRIS

Web App.

Interface to Protocol Engine

Aggregates Job Status Information

Gridbus Broker

Protocol Engine

Gridscape

28

GridScape in Practice (cont’)

ProtocolEngine

Farming Engine

GridScape extension

Broker

query

response

29

GridScape in Practice (cont’)

Specify broker and port number to monitor

30

GridScape in Practice (cont’)

Status of jobs are shown on each resource

31

The End

Questions anyone??