A Development to Grid Resource Management using Grid Broker

Sonchaya Rojanavipat

, Sivadon Chaisiri

, and Putchong Uthayopas

High Performance Computing and Networking Center,Faculty of Engineering, Kasetsart University50 Phahoyothin Rd., Chatuchak, Bangkok 10900 ThailandEmail: {g4765412, g4665304, pu}@ku.ac.th

Abstract

Grid computing is a technology that allows the possibility of sharing distributedresources among multiple organizations. Therefore, not only a middleware and its services areneeded, but also a resource management component that hides the complexity of accessingand discovering of Grid resources from users. In this paper, we present the design andimplementation of a Globus tool kit Version 4.0 compatible Grid resource broker. This brokerallows users to easily discover the resource and helps management the resource usage tomaximize users and system benefits. This paper also presents the experimental results todemonstrate the resource broker performance and the performance of a proof of conceptapplication. This works helps simplify the usage of Grid system for programmer whiledelivering a better performance out of a Grid system. The prototype system has beenimplemented and a drug design application is used to evaluate the system. The experimentalresults show that this system can function well in a heterogeneous distributed system.

Keywords:

Grid resource broker, Grid computing, Globus tool kit, Resource Management,Grid Service.

1. Introduction

Grid Computing [1] is a technology that enable the sharing and accessing of geographically dispersed resources. One approach of using the Grid System is to submit the job into the system using grid aware job scheduler [1]. The Grid scheduler accepts a jobsubmission from users, select the appropriate computing resources and send the job to beexecuted on those computing resources. After the computation finished, scheduler also collectthe results and deliver them to users. Grid Resource Allocation Management (GRAM) [1] is aservice that Grid provides for the access and management of resources. Fig. 1 (a) illustratesthe step involved. The efficiency of this system is depends on the suitability of the jobs andresources capability.With in the past few years, grid computing system is moving towards the approach of Service Oriented Architecture (SOA) Grid. In this approach, Grid system is viewed a offeringa rich set of services. Application can be developed by creating a workflow that invokes theseservices accordingly. In this kind of system, a new component called Grid Broker becomes animportant component. Grid Broker [13] is system component that manage the searching andselecting of the suitable resources and provides a location and access information for theapplications. Grid Broker can rely on resources discovery [6] service of the system to selectsdata, network, locations of resources, and other services. When Grid Broker received the datafrom Resources Discovery, it will match the resources with user’s demands and select themost suitable one. Then, Grid Broker sends the locations of the suitable resources to theapplication. Finally, the application can invoke the selected resources to accomplish the task.These steps are as shown in Fig. 1(b)This paper presents the design and development of a Grid Broker that work underGlobus 4.0 grid system. The organization of this paper is as follows. Section 1 is theintroduction followed by the related works in Section 2. Section 3 describes the proposedwork which is applied and evaluate in Section 4. Finally, Section 5 gives a conclusion andfuture works.

This work has been supported in part by Thai National Grid Project and Kasetsart University SRUfunding.

Fig. 1.

The operation of Grid Scheduler and Grid Broker

2. Related Works

In 1991, Common Object Request Broker Architecture (CORBA) [15] was developedto be the architecture and regulations for the building and distributing of object under network environment. The main concepts of CORBA are Object Request Broker (ORB) and ORBsupports network of clients and servers on heterogeneous computers. Thus, a client programcan request for the service from server located practically anywhere on the network. Anyway,COBRA require a tightly couple interaction and complex protocol which lead to somelimitation in term of scalability.In 2001, Tordson [11] proposed a system of resource brokering for Grid environmentthat can choose resources by considering the work load and efficiency of the resources. Then,broker selects a suitable resource for the application program. The goal is to reduce theexecution time of the application programs. The algorithm used are called Total Time toDelivery (TTTD), with consider the characteristics of the application, the order of work, andthe input and output of work. In [18], Chapman presents another project called EZ-GridProject. The goal of this project is to build a broker that increases the efficiency of theexecution and control resources sharing of under the organization. The work proposes thedesign of an automatic resource discovery system and prepared resources according to thepolicy used. Cavatieri and Monforte[14] also proposed another resource broker architectureand APIs .In 2002, Abramson et al. proposed a system called Nimrod/G [16] which consists of abroker that control and manage the parametric execution of jobs under Grid environment. Anarchitecture called GRACE (Grid Architecture for Computational Economy) has beenproposed. This GRACE architecture composes of global scheduler, bid-manager, anddirectory server. One of the major parts in broker system is the resources discovery systemthat works with the scheduling policy. These system helps user to optimize the budget anddeadline. Within the same year, Frey proposed Condor-G [17], which was developed fromCondor [19] but extended to work with Globus [3]. The users can control and manageresources by creating a Condor resources pool from Globus. The mechanism called Glide-inis built to allow a user to access and execute their job on any resource that belongs to thatpool. Condor-G uses Condor matching service to match the resources and job together.In the previous year, Kim proposed a design and implementation of an OGSI-Compliant Grid Broker Service [12]. This service tries to give the retrieval suitable resourcesfor the users.

3. Proposed Work

In this paper, a design of a Grid broker called GustoFarms Grid Broker (GGB) isdiscussed. The detail of this Grid Broker system and architecture are explained in thefollowing sections.

APPLICATIONGUSTOFarmJXTAPC FarmsAPI

RSS RMS JSS JMSCORE SERVICES

Resource DiscoverySCMSWeb

Fig. 2

. The architecture of GGB

In Fig. 2, shows the architecture of GGB. The system has been divided into 5 layers asfollows:1) PC Farms Layer is the lowest level; This layer consists of computing nodes that areconnected together using a network. To support cross platform capability, Java RuntimeEnvironment (JRE) is chosen to be an operating environment.2) Resource Discovery Layer is a layer that collects and registers all services provided bysystem and users. Currently, a previously developed system called GUSTOFarm has beenused .3) Core Service Layer that provides various services for the system and applications. Thefollowing the services are planned;· Query Service (QS) is the resource query service that receives the requirement fromapplication and then forwards to RDS.· Resource Selection Service (RSS) selects the suitable resource to the user’srequirement.· Resource Monitor Service (RMS) monitor resource status such as speed and loadingof processor, size of memory space left.· Job Submission Service (JSS) is the service that sends the job to computingresources for the processing.· Job Monitor Service (JMS) is the service that shows the progress of job execution.4) Application Programming Interface Layer (API) provides a set of API that users can use todevelop applications and tools for this system.5) Application Layer is consists of users’s application that perform various works accordingto users demands.The processing steps required to initiate any services is as illustrated in Fig. 3. This steps areas explained below.1) A client requests the URL of Grid service on any compute nodes from the broker.2) The Grid broker runs the resource selection algorithm and returns the URL of the chosencompute node to requested client.3) Client invokes Grid service on selected a compute resource.4) The compute resource executes the service using inputs from the incoming request. Then,results of the computing are returned to client.The following section presents the realistic application of this system and shows theperformance attainable from the real application.