MOBILE AGENT BASED AUTOMATED DEPLOYMENT OF RESOURCE MONITORING SERVICE IN GRID

Transcription

1 Ubiquitous Computing and Communication Journal (ISSN ) MOBILE AGENT BASED AUTOMATED DEPLOYMENT OF RESOURCE MONITORING SERVICE IN GRID Valliyammai.C, Thamarai Selvi.S Department of Computer Technology, MIT, Anna University, Chennai {cva, ABSTRACT This paper discusses a novel approach for automated deployment of resource monitoring service for job submission in grid environment. Grid computing is used for solving large scale problems which are complex. Monitoring becomes a crucial model in Grid which is used for scheduling, fault detection, accounting, etc. Job monitoring is required because user has no direct control over the job when it is submitted to a remote. Monitoring requires services to be deployed on all the s in a grid environment to predict the resource availability. It is difficult to deploy the monitoring service manually in geographically distributed s. Hence a need for automated deployment arises. Our approach takes less time to deploy when compared to the manual deployment. The mobile agents do the automated deployment with minimum deployment time which utilizes minimum bandwidth in turn reduces the network load. Keywords: mobile agents, resource monitoring, job monitoring 1 INTRODUCTION A grid is a collection of heterogeneous, widely distributed resources to create a virtual organization. Grid computing helps in coordinating the resource sharing and also problem solving in dynamic, multi institutional organizations [2], [14], [16]. Grid monitoring involves collection of resource status information and providing this information which serves for system management, faults detection and performance optimization [1]. Grid monitoring is essential for efficient management and for locating failed s thereby ensuring that the system can run smoothly [11]. Due to dynamicity of grid environment, resources join and leave dynamically, hence monitoring becomes an essential task [3]. The available grid environment still does not support all functionalities and services like resource brokering, fault management, automatic software installation and configuration, and trust based access control [10]. A mobile agent can be viewed as an object that is capable of migrating in a network and performing task in s. Since logic moves near data, network load is reduced and less bandwidth is used [1]. Mobile agents are used in a variety of applications like resource monitoring, network monitoring, and copying files from remote machines, etc. In addition to the characteristics of a simple agent [12], a mobile agent has some additional characteristics like: mobility, durative, off line computing, etc. The advantages [15] of using mobile agents such as since computational unit is closer to the data, network traffic is reduced; Mobile agents reduce the usage of network bandwidth; Mobile agents can migrate themselves according to the environment; Rule based migration policy prevents blindness of resource access. Resource monitoring involves collecting information pertaining to the system resource usage which is needed for improving the performance of the system. Network monitoring which involves monitoring the bandwidth, latency, etc is needed for better utilization of the resources [22]. Job monitoring enables to monitor the progress of the jobs submitted. Whenever a job is submitted to a, it undergoes the following states, submitted (job that entered the Grid), waiting (while resource discovery), ready (when job transferred to the selected ), scheduled (when waiting in a local queue), running (when job is actually running), and done (when completed successfully) or aborted (when terminated abnormally) [1], [7]. System configuration is a major source of error in deployment and its management dominates system administration costs. Automation of deployment for monitoring system enables improved correctness and speed [4].The dynamicity of grid environment raises a need for monitoring the grid. As new s join the grid, the resources should be monitored for efficient usage of resources. Our proposed mobile agent based automated deployment avoids the maintenance costs and human errors occurring during deployment. The well known tool Globus [17] is used o set up the grid environment, but still it focus on low-level protocols. Due to the complex and large scale grid environment with different types of resources, there UbiCC Journal, Volume 6: Issue 2 786

2 is a need of adapting the technique for code and data mobility which is knows as Mobile Agent Technology to support the features of dynamic work load balancing, reconfiguration, reliability, monitoring and management [10], [23]. 2 RELATED WORK Monitoring and Discovery Services (MDS) is used to describe and monitor services, resources, etc [18]. It is based on Lightweight Directory Access Protocol (LDAP) which does not support complex querying. In MDS, the data is not exactly latest one. Hence maintaining the resource information in a database along with a timestamp facilitates for obtaining the latest data. The Ganglia [9] presents a distributed monitoring system which has a hierarchical design. It uses a multicast-based listen/announce protocol within clusters. It maintains a tree of point-to-point connections to federate clusters and aggregate their state. Also it satisfies the requirement of monitoring in multi-clusters. When a new cluster needs to be monitored, Ganglia should be manually installed, s should be configured, source codes should be compiled and make command should be executed. The effort required for manual deployment becomes considerable in case of large-scale clusters [6], [13].The present information and monitoring systems are scaled to Grid level to support the necessary checkpoints and migration. Mobile agent technology is very much flexible to support the rum-time mobility through push and pull interaction models. The MA-GMA [5] is based on GMA with a mobile agent-based collecting module and a cache mechanism. GMA facilitates development of high performance monitoring middleware [8]. It is designed in accordance with OGSA standard with mobile agent s characteristics. The mobile agents are generated in the mobile agent factory and the mobile agent manager manages the agents. The infrastructure needed for agents' transferring and receiving in the Grid is provided by the mobile agent manager. MAGDA is a mobile agent based platform for grid environment to support the dynamic load balancing in distributed applications [10]. And the characteristics persistence, cloning and migration of the mobile agents improve the reliability through replication. In present scenario, many researchers focus on agent based model [20] and importance of basic services such as load balancing [23], fault management [24] and service discovery [21]. Monitoring System capable of Rapid and Automated Deployment (MSRAD) utilizes peer to peer protocols for automated deployment [4].In this paper we have proposed a method which uses mobile agents for automated deployment. Since mobile agents are capable of operating even without active connections between s, they are not affected by network failures. Further mobile agents reduces network load. 3 THE PROPOSED ARCHITECTURE The proposed architecture for an agent based and Automated Deployment of job monitoring service is shown in the Figure 1.The main components of the architecture are as follows: IP address of new is stored in database New Registration Agent migrates and invokes deployment Service is deployed IP address of head is given to new Job file is submitted Head User invokes monitoring service User IP address of suitable is returned Job status is returned Scheduler Delegation Schedule Authenticate Job manager Job state monitor Figure 1. Architecture of agent based automated deployment UbiCC Journal, Volume 6: Issue 2 787

3 Deployment Agent: an agent which contains code for deployment of the services. It resides in the head. On request from a newly arrived, it migrates to the and executes. Registration Node: A which maintains a database of the s that arrive and also it sends the IP address of the head to the newly arrived Probe: A script is deployed in the s. On invoking the script it collects the resource metrics of the s periodically and stores in the head in the form of XML. Collector Service: The collector service collects the resource metric from the head and stores it in a database in the head along with a time stamp. Database: A database that stores the resource information gathered from every which will be used for monitoring and scheduling. Selector Service: The selector service searches the database for a that best suits the user's job requirements. Job monitor: This module performs credential delegations and submits the job to the selected for execution. It also updates the status of the job periodically. A mobile agent is composed of code and data which migrates to other s and executes there in the to which it migrates. The mobile agents exploit the basic communication protocols defined within IBM Aglets Workbench [19] for agent migration and to dispatch messages from one to another. The head contains the services to be deployed and the deployment agent. The registration maintains a repository of IP addresses of the s in which the monitoring service is deployed and also the IP address of the head. Mobile agents are used by the user for getting the IP address of the head from the registration and for deploying the services. For automated deployment of service, mobile agents are used to send request to the registration on its arrival and retrieve the IP address of the head to the newly arrived. A mobile agent from the new migrates to the registration, collects the IP address of the head and migrates back to the sender. Using the IP address of the head, the newly arrived requests the head for deployment of the services. The deployment agent migrates to the head containing the services and executes thereby deploying the services. 4 IMPLEMENTATION The implementation of the proposed approach for an automated deployment of the services to monitor the job has two phases. The first phase involves creating services that are used for automated deployment. One service called collector service is created for collecting the resource metrics from the system and another service called selector service is used to select a suitable for the submission of job. The collector service includes collecting resource metrics like CPU speed, free memory, bandwidth and latency from the s in the cluster. The collected data is then stored in the database along with a timestamp. Timestamp helps in validating the monitored data. The selector service selects a suitable by searching the database based on some constraint. The constraint used here is, select a set of s having high free memory, from this set a having more CPU speed, low latency and high bandwidth is chosen for job submission. Figure2. Automated deployment using mobile agents UbiCC Journal, Volume 6: Issue 2 788

4 The second phase involves automating the service deployment. The process of automated deployment of the service to a new is shown in Figure 2. Whenever a new joins the grid, it registers itself to the registration. The registration is done by sending the IP address. The registration maintains a database of the IP address. Now the registration sends the IP address of the where the service is located i.e. in the head. After getting the IP address of the head the newly joined invokes the deployment agent in the head. The agent deploys the service requested in the new. The deployment agent has the details of which files to be transferred and what commands to be run for the deployment. These services are used for selecting a to which a job can be submitted. GRAM services are used which helps in secure job submission to various types of schedulers. Job monitoring module periodically updates the job status and after completion of job the result is reported to the user. 5 RESULTS AND DISCUSSION The time taken for the mobile agents to deploy the service in a new is calculated as follows: Let t(dt) be the time taken for automated deployment. t(dt) = t(α)+ t(β) (1) Where t(α) is the time taken for the deployment agent to migrate to a. t(β) is the time taken for deployment. From the Figure 3, it is evident that mobile agent based automated deployment consumes less time than the script based approach in Automated Deployment of Monitoring Service (ADMS). If the dependency packages for Ganglia are downloaded, the time taken to install Ganglia is equal to running four commands which completes the installation. ADMS has to install Component Auto-deploy Proxy (CAP) and cluster and thereby it takes more time than the mobile based approach. Deployment time in secs D e p lo y m e n t T im e - M a n u a l V s A g e n ts N o. o f A g e n ts Figure 3. Manual vs. automated deployment time A g e n t s M a nu a l A simulation based test is adopted to verify the efficiency of the proposed method. It is seen that the time taken for manual deployment increases as the number of s increases. Since the response time of mobile agent is less, the time taken for automated deployment using mobile agent does not increase proportionately with the increase in the number of s. 6 CONCLUSION AND FUTURE WORK In this paper, we have specified the importance of monitoring and automated deployment of monitoring service in Grid environment. The proposed approach enables automated deployment in a grid environment with the help of mobile agents. Mobile agents are utilized in the automated deployment process to facilitate error free deployment since mobile agents are not affected by network failures and the time taken for deployment is also less when compared to manual deployment. The automated deployment of monitoring service exploits the plan of selecting suitable which ensures the efficient utilization of grid resources. Our future work includes extending the architecture which supports the resubmission of failed jobs and protection of mobile agents form malicious hosts to improve the reliability of the automated deployment using mobile agents. The monitoring service can be invoked to select another suitable for job submission and the failed job can be resubmitted in the selected, and also reporting the status of the job given to the user. 7 REFERENCES [1] Valliyammai C, Thamarai Selvi S, Hemarupa S, Kalai E, Ragul P(2008), Monitoring Remote jobs in Grid Using Mobile Agents, Icfai Journal of Information Technology,pp.57-63(2008). [2] Foster, C. Kesselman, and S. Tuecke, The anatomy of the Grid: Enabling scalable virtual organization, International Journal of Supercomputer Applications 15(3), pp (2001). [3] Serafeim Zanikolas and Rizos Sakellariou, A Taxonomy of Grid Monitoring Systems, Future Generation Computer Systems, Vol.21, No 1, pp [4] Mei Yiduo, Dong Xiaoshe, Li Junyang, Xu Jing, Xue Zhenghua, Rapid and Automated Deployment of Monitoring Services in Grid Environments, IEEE Asia-Pacific Services Computing Conference (2007). [5] Guoqing Dong, Weiqin Tong, MA-GMA: A Mobile Agent-based Grid Monitor Architecture, ACS International Conference on Computer Systems and Applications (AICCSA 2007), pp (2007). UbiCC Journal, Volume 6: Issue 2 789

5 [6] Dong Xiaoshe, Wang Yinfeng, Qin Zhongsheng, Zheng Fang, Research on an Automatic Deployment Mechanism of Monitor Service in Grid Environment, Proceedings of the Fifth International Conference on Grid and Cooperative Computing Workshops (2006). [7] Roger Curry and Rob Simmonds, Job Centric Cluster Monitoring, IEEE International Conference On Parallel and Distributed System, (2006). [8] Chenxi Huang, Peter R.Hobson, Gareth A. Taylor, Paul Kyberd, A Study of Publish/Subscribe Systems for Real-Time Grid Monitoring, IEEE, (2007). [9] Chao Tung Yang, Tsui-Ting Chen, Sung -Yi Chen, Implementation of Monitoring and Information Service Using Ganglia and NWS for Grid Resource Brokers, IEEE, (2007). [10] Rocco Aversa, Beniamino Di Matino, Nicola Mazzocca, Salvatore Veticinque, MAGDA: A Mobile Agent based Grid Architecture, Journal of Grid Computing, pp (2006). [11] Jianbo Shen, Bin Gong, Yi Hu, Sha Li, The Design and Implementation of a GMA based Grid Monitoring Service, Proceedings of the 11th International Conference on Computer Supported Cooperative Work in Design, (2007). [12] Todd Papaioannou, On the Structuring of Distributed Systems: The Argument for Mobility, Doctoral Thesis, Loughborough University, (2000). [13] Vanish Talwar, Dejan Milojicic, Qinyi Wu,Calton Pu, Wenchang Yan and Gueyoung Jung, Approaches for Service Deployment, IEEE Internet Computing, pp70-80 (2005). [14] I.Foster, C.Kesselman, Steven Tuecke, The Anatomy of the Grid, Enabling Scalable Virtual Organizations, Lecture Notes in Computer Science. [15] Danny B.Lange and Mitsuru oshima, Seven Good Reasons for Mobile agents, Communications of ACM, (1999). [16] I.Foster, C.Kesselman, Globus: A Metacomputing Infrastructure Toolkit, International journal of supercomputer applications, pp ( 1997). [17] Globus [Online] Available: [18] Jennifer M. Schopf, Ioan Raicu, Laura Pearlman, Neill Miller, Carl kesselman, Ian Foster, Mike D Arcy, Monitoring and Discovery in a Web Services Framework: Functionality and Performance of Globus Toolkit MDS4, dc06.pdf [19] Aglets, Online [available]: [20] Li, Z.Parshar, M.Rudder, An agent-based infrastructure for autonomic composition of grid applications, Multiagent and grid systems Journal, IOS Press1 (3), pp (2005) [21] Cao.J, kerbyson, D.J., Graham. R.N, High Performance services discovery in large-scale multi-agent and mobile-agent systems, International journal of software Engineering. 2(5), pp (2001). [22] C.Valliyammai, S.Thamarai Selvi (2008), Relational Network Monitoring System for Grid Performance Optimization, in the International Conference ADCOM 2008, Dec14-17, pp (2008). [23] Niranyan, S., Groth, P.T., Bradshaw, J.M.: While you re away: A system for loadbalancing and resource based on mobile agents. In: Buyya, R. (ed.) 1st IEEE International Conference on Cluster Computing and the Grid, Brisbane, Australia. IEEE Computer Society, (2001). [24] Jain, A., Shyamasundar, R.K.: Failure detection and membership management in Grid environments. Grid, pp , Fifth IEEE/ACM International Workshop on Grid Computing (GRID 04),(2004). UbiCC Journal, Volume 6: Issue 2 790