- Global Grid Example One
- Overview of a Global Compute Grid
- Brief Description or the Globus Toolkit 2.0
- Distributed Resource Managers
- Portal Software and Authentication
- Global Grid Example One
- Global Grid Example Two
- About the Authors
- About the Authors
- Ordering Sun Documents
- Accessing Sun Documentation Online
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Global Grid Example Two
Introduction
The Poznan supercomputer project PROGRESS (Polish Research on Grid Environment for Sun Servers) involves two academic sites in Poland, Cracow and Poznan. The project was founded by the State Committee for Scientific Research. Project partners are: Poznan Supercomputing and Networking Center; Academic Supercomputing Center of University of Mining and Metallurgy, Cracow; Technical University, Lodz, and Sun Microsystems Poland.
Currently, there are two cluster grids accessible through the PROGRESS portal: one Sun Fire 6800 (24 CPUs) in Cyfronet Cracow and two Sun Fire 6800s (24 CPUs) connected using Sun Fire™ Link sited at Poznan Supercomputing and Networking Center. The distance between the locations is about 400 km. Both locations also use Sun Fire V880s and Sun StorEdge™ 3910s as the hardware supporting the Distributed Data Management System discussed below. At the development stage, only large Sun SMP machines are used, but the architecture of the developed system allows the existing computing resources to be augmented by hardware from other vendors.
As in the White Rose implementation, Globus Toolkit 2.x has been implemented to provide the middleware functionality. Also, as in the White Rose case, Sun ONE Grid Engine, Enterprise Edition is installed to control each of the cluster grids. In this case, however, the portal interface has been built using Webservices elements based upon J2EE.
The main task of this project is to give a unified access to distributed computing recourses for the Polish scientific community.
Other aims are the following:
Development of novel tools supporting grid-portal architecture (grid service broker, security, migrating desktop, and portal access to grid)
Development and integration of data management and visualization modules
Testing of tools and infrastructure using a set of bio-informatical applications (DNA assembling and prediction of protein secondary structure using Logical Analisys of Data)
Enabling the grid-portal environment for other advanced applications (PIONIER program)
)
FIGURE 4
Overview of PROGRESS Project
System Modules
The PROGRESS architecture can be described in terms of its constituent modules. As well as using the Globus Toolkit, each of these modules provides a major piece of functionality for the PROGRESS grid. The four main modules are:
Portal Environment
Grid Service Provider
Grid Infrastructure
Data Management System.
FIGURE 5 shows how these modules interact in the PROGRESS architecture and shows the main communication protocols used between the modules.
)
FIGURE 5 PROGRESS
Architecture
Portal Environment
The main module of the Progress Portal Environment is the Grid Service Provider (GSP). It is a new layer introduced into the Grid Portal architecture by the PROGRESS research team. The GSP provides users with three main services: a job submission service (JS), an application management service (AM), and a provider management service (PM).
The JS is responsible for managing creation of user jobs, their submission to the grid, and monitoring of their execution.
The AM provides functions for storing information about applications available for running in the grid. One of its main features is the possibility of assisting application developers in adding new applications to the application factory.
The PM allows the GSP administrator to keep up-to-date information on the services available within the provider.
The PROGRESS GSP services are accessible through two client interfaces: Web Portal (WP) and Migrating Desktop (MD). The Web Portal, which is deployed on the Sun ONE Portal Server 7.0, performs three functions:
Grid job management: creating, building, submitting, monitoring execution, and analyzing results
Application management
Provider management
FIGURE 6 shows a typical user's view of the portal interface.
)
FIGURE 6 PROGRESS
Portal
The MD, which is a separate Java client application, provides user interface for grid job management and DMS file system management. Both user interfaces are installed on a Sun Fire 280R machine, which serves as the PROGRESS system front-end.
Additionally PROGRESS Portal gives access to services such as news services, calendar server, and messaging server (deployed on a Sun ONE calendar and messaging server).
Grid Infrastructure
The Grid Resource Broker (GRB) is developed in the Poznan Supercomputing and Networking Center and enables execution of PROGRESS grid jobs in grid clusters. Clusters are managed by Sun ONE Grid Engine, Enterprise Edition software with Globus deployed on it. The GRB provides two interfaces: a CORBA interface and a web services interface. Grid job definitions are passed to the GRB in the form of an XRSL document and the GRB informs the JS about events connected with the execution of a job (start, failure, or success).
Sun ONE Grid Engine, Enterprise Edition is implemented at both sites as the local distributed resource manager. Sun ONE Grid Engine, Enterprise Edition provides policy driven resource management at the node level. The Share Tree policy is used to manage the resource share allocation at each node.
Two types of users can have access to resources:
Local users, accessing compute resources through the grid engine GUI
Portal users, accessing nodes using the PROGRESS portal or Migrating Desktop.
In the event of extensions to the PROGRESS grid, grid engine would also be used.
Each cluster grid also hosts Globus Gatekeeper.
Data Management System (DMS)
PROGRESS grid jobs use the DMS to store the input and output files. The DMS provides a web services based data broker that handles all requests. The DMS is equipped with three data containers: the file system, the database system, and the tape storage system containers. A data file is referenced within the DMS with a universal object identifier, which allows for obtaining information on the location of the file.
Users can download or upload files using one of three possible protocols: FTP, GASS, or GridFTP.