An Experience in Accessing Grid Computing from Mobile Device with GridLab Mobile Services

Transcription

1 An Experience in Accessing Grid Computing from Mobile Device with GridLab Mobile Services Riri Fitri Sari, Rene Paulus Department of Electrical Engineering, Faculty of Engineering University of Indonesia Kampus Baru UI Depok 16424, Indonesia Abstract In this paper we discuss our experience in evaluating the GridLab Mobile service as a tool which supports the combination of two mainstream research area, Grid computing and mobile devices. We use GridLab Mobile services platform to conduct our experiment to enable the access of Grid computing power from Poznan supercomputing and networking Center in Poland through smart phones. Minimum interfaces required to use GridLab Mobile services include Mobile Client, Mobile Command Center and Grid application. We explore some GridLab Mobile services functionality such as GridLab Resource Management System (GRMS) Job submission and Control, message box browsing, visualization viewing, and auxiliary functionality (login for instance). From our experiment it was found that to Login we need to send the average of 635 Bytes of data and receive 467,6 of data in 14.6 seconds. For getting message box we had to send the average of 1389 Bytes of data and receive 1638,8 Bytes of data in 26.6 seconds. In addition to that, for visualization purposes we sent the average of 2701,8 Bytes of data and received the average of 46139,4 of data in 43.4 seconds. I. ITRODUCTIO In the last few years mobile devices has emerged as a common communication tools which extensively been developed jointly by academic and industry sectors. These devices benefited from the advancement in wireless technology, which has become more powerful. Mobile devices have grown rapidly in numbers due to their lower initial cost compared with the wired network. Grid computing is a group of computer, server, and storage that form a virtual computer system. With Grid computing we can optimize performance and reliability. In this paper we combine these two issues to enable us to get the benefit of Grid computing power from mobile devices. The technology used here is GridLab Mobile services, which is one of the workpackage of the GridLab project. The combination of Grid computing and mobile devices with other technology in detail is not within the scope of this paper. II. GRID COMPUTIG Grid computing concept has become more mature. Grid computing has a lot in common with the metacomputing, which was popular during 1990 s. One of project that develop metacomputing concept is /$ IEEE 1 Informational Wide Area Year (I-WAY) which was strongly influenced by the development of Globus project, the most prominent Grid computing standard currently [3]. Ian Foster and Carl Kesselman define Grid as hardware and software infrastructure that provides dependable, consistent, pervasive, and inexpensive access to high-end computational capabilities [9]. The other definition from Foster state that A Computational Grid is a collection of computers, on-line instruments, data archives and networks all tied together by a shared set of services that, when taken together, provides users with transparent access through interface devices to the entire set of resources. According to IBM s definition [6], Grid is a collection of distributed computing resources available over a local or wide area network that appears to an end user or application as one large virtual computing system. The vision is to create virtual dynamic organizations through secure, coordinated resource-sharing among individuals, institutions, and resources. Grid computing is an approach to distributed computing that spans not only over some locations but also organizations, machine architectures, and software boundaries to provide unlimited power, collaboration, and information access to everyone connected to a Grid. The Internet is the network of information, where as grid computing is the network of resources. Grid will help elevate the Internet to a true computing platform, combining the qualities of service of enterprise computing with the ability to share heterogeneous distributed resources (applications, data, storage, servers, etc). The Globus Alliance defined Grid as "an infrastructure that enables the integrated, collaborative use of high-end computers, networks, databases, and scientific instruments owned and managed by multiple organizations. Grid applications often involve large amounts of data and or computing and often require secure resource sharing across organizational boundaries, and thus not easily handled by today s Internet and Web infrastructures." Fig. 1 shows the architecture of Grid computing remote implementation in which Grid provides access to distributed resources. Computational Grid enables the sharing, selection, and aggregation of a wide

2 variety of geographically distributed computational resources (such as supercomputers, computing cluster, storage system, data source, instrument, and developers). Grid computing key components include the following: Resource management: the Grid must be aware of what resources are available for different tasks. Security management: the Grid needs to take care that only authorized user can access and use the available resources. Data management: data must be transported, cleansed, parceled, and processed. Service management: users and application must be able to query the Grid in an effective and efficient manner. To cover complex system of services and software required to integrate Grid resources, Grid community [1] has develop a layered model shown in Fig. 2. The bottom horizontal layer consists of hardware resources such as computers, networks, data archieves, etc. The next horizontal layer (common infrastructure) consists of software services and system which virtualize the Grid. The key concept at the common infrastructure layer is the community agreement on software, which represent Grid as a unified virtual platform and provide the target for more focused software and application. The next horizontal layer (user and application-focused Grid middleware, tools and services) contains software packages built on top of the common infrastructure. The top most horizontal layer (Grid application) represents application and user. The vertical layers represent the next step for Grid development. The left vertical layer represent the influence of new devices, such as sensors, PDA, wireless, and mobile devices. Over the next 10 years, these devices will need to be integrated with the Grid. At the same time, the increasing globalization of the Grid will require serious policies of sharing, globalarea networking and the development of Grid economies (the right vertical layer). III. MOBILE DEVICES Mobile devices have become more and more powerful as their size getting smaller. They are now capable of executing applications comparable with the power of the earlier desktop computer. By their high mobility, mobile devices become more popular and growing rapidly in numbers. Although mobile devices are powerful they have many limitations such as limited screen size, input capability, processing power, small amount of memory, and short battery life. Current wireless network connections of mobile devices are slow, the latency is high and the bandwidth is limited. The connection to the network is not permanent. Mobile client normally open its connection only when required to do so, and therefore the network connection may not always be available. Mobile services were developed for multiple platforms. Currently Palm and Symbian are among the most common Operating System (OS) for mobile devices, in addition to other Operating Systems. All of these platforms are different and not compatible with each other. Fortunately, most of these platforms are capable of running application written in Java. Java 2 Platform Micro Edition (J2ME) [8] is an application environment designated for small and limited devices. Program running in this environment are called middlet. J2ME defines two configuration which is Connected Limited Device Configuration (CLDC) the most lightweight configuration and Connected Device Configuration (CDC) used in device with larger memory and performance. On top of configuration layers, there is a profile layer which specifies a set of API fo a particular category of devices and minimum hardware, software, networking, and application requirements. Fig. 3 shows this configuration. Combining these two key trends (Grid computing and mobile devices) means that the users are able to command the power of supercomputers with mobile devices. In this work we use GridLab Mobile Service to combine these two key trends. GridLab Mobile services use J2ME technology at the mobile client which is a mobile device. IV. GRIDLAB PROJECT GridLab project researches currently develop application and middleware for Grid environment. GridLab project is a grid computing research organized by the Institute of the Bioorganic Chemistry of the Polish Academy of Sciences, Poznan Supercomputing and etworking Center (PSC), Poland, and co-funded by the European Commission under the Fifth Framework Programme. GridLab project consists of 12 core workpackages (WP), with additional workpackages covering exploitation, dissemination and project management. All GridLab technology fit into the GridLab architecture shown in Fig /$ IEEE 2

3 Fig. 1. Grid Computing (remote implementation) [7] Fig. 2. Layered architecture of the Community Grid Model [1] WP1 Grid Application Toolkit (GAT) objectives are to design and build a Grid Application Toolkit from the services developed in other GridLab workpackages. GAT is a set of coordinated, generic managements systems, together with working implementations provided by the tools developed in GridLab project. WP2 Cactus Grid Application Toolkit (CGAT) will provide a very general toolkit framework supporting different Grid applications, from astrophysics to chemical engineering. CGAT extended GAT interface to Cactus [2]. WP3 Work- Flow Application Toolkit (TGAT) based on Triana [5] packages developed for gravitational wave data analysis. WP4 Grid Portal goal is to design, build and support the GridLab Portal. WP5 Testbed Management takes care of all the activities necessary for deploying and running a large-scale Grid testbed and to establishment of an actual prototype. WP6 Security aims at building solid and consistent testbed security management tools and policies, as well as inter-testbed interoperability security policies. WP7 Adaptive Grid Component goal is to provide adaptive components to other modules of the Grid application toolkit (GAT). WP8 Data Handling and Visualization creates a framework that enables application to stream data for visualization purpose. WP9 Resource Management aim is to describe GridLab Resource Management System (GRMS). WP10 Information Services goal is to design and build igrid, the GridLab Information Services to supplies information about a specific resource. WP11 Monitoring objectives are to design and develop a general Grid monitoring infrastructure, compliant to the Grid Monitoring Architecture proposal of the Global Grid Forum Performance Working Group. WP12 Access to Mobile Users objective is to develop implementation for mobile device so user can use it to access Grid computing environment. V. GRIDLAB MOBILE SERVICES Fig. 3. Java 2 Platform, Micro Edition (J2ME) [8] Fig. 4. GridLab Architecture [4] WP12 GridLab Mobile Services provide the Grid user possibility to access Grid application and resource from any place using their mobile devices. Mobile device acts as a mobile client and tightly coupled with the gateway. Minimum Grid interface required for GridLab Mobile Service are GridLab Mobile Client, Mobile Command Center as gateway, and Grid service. Fig. 5 shows the minimum requirement for Grid interface. Mobile Command Center (MCC) is a portlet that serves as the gateway between mobile devices and Grid services. MCC required Java 1.4.2, Jakarta Ant 1.6, Jakarta Tomcat 4 or 5, GridSphere [5] portal (WP4) installed and deployed, and GridPortlets installed and deployed in the same GridSphere container. Portlets are reusable Web components that display relevant information to portal users. GridLab 3

4 Mobile Client (GMC) run on the mobile device which support J2ME technology. GridLab Mobile Service functionality are GridLab Resource Management System (GRMS) Job submission and control, visualization viewing, message Box browsing, and auxiliary functionality. The GridLab Resource Management System (GRMS) is an open source meta-scheduling system, based on dynamic resource selection, mapping and advanced scheduling methodology. The main goal is to directly manage the whole process of remote job submissions to various batch queuing system, cluster or resources. The most important part is the part which enable the system to submit job to the best resources according to the job resource requirement. GRMS functionality which can be use from mobile device are submitjob, migratejob, canceljob. Message Box Service (Fig. 7) main purpose is to store users notification messages in the structured repositories folder. Grid Mobile Client can access user folders and messages stored in Message Box. Auxiliary functionality is a part of GridSphere framework for user login and profile which is user login, user logout, user credential usage (for authorization), dan user data checking. Fig. 8 represents the login service. CC Fig. 7. Message Box browsing Fig. 8. Login Form Fig. 5. Minimal Grid Interface [4] Visualization viewing (Fig. 6) works together with WP8 so the WP12 user can display scaled-down visualization (mainly picture) on mobile device many times. The picture are sent to mobile device according to the limitation of that device, such as the low resolution screen and color depth, small bandwidth network, etc. We performed some experiment using the following equipment specification: Sony Ericsson K508i device, 128x160 pixel screen, 65,536 color depth. The connection used to connect to through Indosat M3 GPRS service. From our experiments, we performed performance evaluation. We gather and analys data for each service. The average of those data have been calculated and presented in Table I, II, III and IV. Login to Mobile Command Center from GridLab Mobile Client required 635 Bytes of data to be send and 467,6 data received in 14,6 seconds. For Message box viewing, the average of data sent is 1389 Bytes and 1638,8 Byetes receivedin 26,6 seconds. Visualization service from mobile client need 2701,8 Bytes data to be send and 46139,4 Byetes received in 43,4 seconds. Fig. 6. Visualization Viewing 4

5 TABLE I LOGI TABLE II MESSAGE BOX Currently we are woking on integrating some distributed grid nodes at the University of Indonesia and set the environment to be able to be accessed from mobile nodes. Our work on implementing virtual reality over grid computing will also take advantage from this grid computing platform. REFERECE [1] Berman, F., Hey, A.J.G., Fox G.C., Grid Computing Making the Global Infrastucture a Reality, John Wiley & Sons, Ltd, England, [2] Cactus, last accessed June [3] Globus Alliance, last accessed June [4] GridLab, last accessed June [5] GridSphere, last accessed June [6] IBM, last accessed June [7] Minoli, Daniel, A etworking Approach to Grid Computing, John Wiley & Sons, Inc, [8] Sun Microsystem, last accessed June [9] Foster, I., Kesselman, C., The Grid, Blueprint for a new Computing Infrastructure, San Fransisco, TABLE III VISUALIZATIO TABLE IV AVERAGE Service Send Login ,6 14,6 Message box ,8 26,6 Visualization 2701, ,4 43,4 VI. COCLUSIO The development of mobile device in the last few years enables us to access Grid computing environment in mobile. GridLab Mobile Service can be used to access Grid application and resources from mobile devices. GridLab Mobile Service required minimum Grid interface such as GridLab mobile client running on J2ME enabled mobile devices, Mobile Command Center as gateway, and the Grid services. From our experiments with GridLab services for mobile client, we plan to perform future work which include building some services on top of the mobile command center testbed. 5