The GridLab project consists of 12 core workpackages, with
additional workpackages covering exploitation, dissemination and
project management.
|
TB
|
Technical
Board (TB)
|
The Technical Board is responsible for the general
architecture of the GridLab project and has to coordinate
and ensure the interoperability between the individual
Work Packages.
|
|
WP1
|
Grid Application Toolkit (GAT)
|
The objectives of this workpackage are to design and build a Grid Application Toolkit (GAT)
from the services developed in other GridLab workpackages. The GAT is a set of coordinated,
generic and flexible APIs for accessing Grid services from e.g. generic application codes,
portals, data managements systems, together with working implementations provided by the
tools developed in the Grid Lab project (See the figure below). The GAT is designed
in a modular plug-and-play manner, such that tools developed anywhere which conform
to the GAT API will be inter-opera
|
| |
|
|
WP2
|
Cactus Grid Application Toolkit (CGAT)
|
The Cactus Grid Application Toolkit will provide an extended GAT interface for Cactus
(http://www.cactuscode.org), a very general toolkit framework supporting different
Grid applications, from astrophysics to chemical engineering. Cactus is one of the
primary application drivers for the GAT.
|
| |
|
|
WP3
|
Work-Flow Application Toolkit (TGAT)
|
The Work-Flow Application Toolkit, based on the Triana package developed originally
for gravitational wave (GW) data analysis, will provide a second example application
toolkit for GridLab. GW data analysis has a large community of users that will benefit
significantly from the developments of this WP. However, the class of applications
covered by TGAT is much larger than GW data analysis. Complimenting the CGAT,
which is aimed primarily at supporting large scale simulation applications,
the TGAT will be developed to exploit Grids for many different work-flow applications,
through extensions to the Triana data-flow programming environment.
|
| |
|
|
WP4
|
Grid Portals
|
The goal of this work package is to design, build and support the GridLab Portal.
In this project, we combine the lessons learned in the development
of the Astrophysics Simulation Collaboratory (ASC), a precursor to the GridLab Project,
and the Grid Portal Development Kit, one of the earliest and most widely used research projects
in the Grid portal community.
|
| |
|
|
WP5
|
Testbed Management
|
One of the most challenging tasks of the Grid research is the establishment of actual prototype
or even production Grids, requiring creation and maintenance of both the technological and political
infrastructure. This WP takes care of all the activities necessary for deploying and running
a large-scale Grid testbed, providing a prototype of future production Grids.
The GridLab testbed is available to all other work packages for development, testing, evaluation,
and deployment of new components. While the core resources of the testbed are provided by GridLab
partners, we actively encourage other EU and US sites and testbeds to join and expand the GridLab
testbed and to enable inter-grid experiments. Results of testbed experiences are published in series
of documents disseminated through the Global Grid and other forums.
|
| |
|
|
WP6
|
Security
|
This work package aims at building solid and consistent testbed security management
tools and policies, as well as inter-testbed interoperability security policies.
The work package will provide various security mechanisms that will fulfill Grid security
requirements. The following issues will be addressed by the WP: Grid requirements for authentication,
for communication protection, authorization. Grid security solutions that will be provided by the WP
will be based on existing standards wherever possible.
|
| |
|
|
WP7
|
Adaptive Grid Components
|
The goal of this work package is to provide adaptive components to other modules of the grid
application toolkit (GAT). Common to these adaptive components is that they take
(possibly dynamic) information about Grid resources (network status, CPU availability, memory
footprint, etc.) as input to performance-prediction models and implement adaptive strategies
that let applications use the given resources more efficiently. For grid-aware applications,
this general mechanism is used for numerous purposes like data access, task scheduling,
and dynamic application reconfiguration. Although use-case specific APIs and event models
are necessary, the basic techniques are similar.
|
| |
|
|
WP8
|
Data Handling and Visualization
|
The GridLab Data Management and Visualization Workpackage provides the services
that are needed by the GridLab Grid to manage public and user-private files and
creates a framework that enables applications to stream data for visualization purposes.
|
| |
|
|
WP9
|
Resource Management
|
The aim of this webpage is to describe the GridLab Resource Management System (GRMS),
consisting of a set of technical specifications, along with clarifications and examples
that help end users, administrators and developers to deal with this software.
|
| |
|
|
WP10
|
Information Services
|
The goal of this work package is to design and build iGrid, the GridLab Information Services.
The iGrid distributed architecture is based on two kind of Information Services,
the iServe and the iStore GSI enabled web services. The iServe supplies information
about a specific resource, while the iStore aggregates information coming from registered iServe.
|
| |
|
|
WP11
|
Monitoring
|
The objectives of this workpackage 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.
The aim is to support the advanced scenarios foreseen in the GridLab project,
such as application steering, self-tuning applications and performance analysis and prediction.
To achieve this the general GGF GMA architecture is extended with actuators and controls.
|
| |
|
|
WP12
|
Access for Mobile Users
|
The main objectives of this Workpackage is to develop novel theoretical scenarios and their implementation
for using mobile devices to enhance the working environment and efficiency of application users,
especially in relation to applications making large scale use of the grid.
Interact with other WPs to ensure the developed infrastructure (Portal, web interface, remote steering
and visualization) is supported on a wide range of mobile devices as possible
(eg. PDAs, Windows CE, PalmOS, laptops, mobile phones).
|
| |
|
|
WP13
|
Exploitation and Dissemination
|
Ensure the active dissemination of the project results
through a variety of channels, including active
participation in international organizations (eg GGF), co-development with other
Grid projects in the USA and EU, participation in
international conferences, training programs, instruction of
GridLab technologies into various communities, and
introduction into the commercial vendor world.
|
| |
|
|
WP14
|
Project Management
|
Ensure the project's professional management, including
careful orchestration and monitoring of work across groups,
major project decisions, liaisons with external projects and
with the international advisory board, etc.
|
| |
| Del. No. |
Deliverable Title |
Lead Participant |
Del. Type |
Security |
Delivery (proj. month) |
State |
Review |
| D14.1 |
Quality Assurance Plan |
PSNC |
Report |
Int. |
3 |
delivered |
|
| D14.4-D14.15 |
Quarterly reports (D14.4,
D14.5,
D14.6,
D14.7,
D14.8,
D14.9,
D14.10,
D14.11,
D14.12,
D14.13,
D14.14,
D14.15) |
PSNC |
Report |
IST |
3,6,9,12,15,18,21,24,27,30,33,36 |
D14.4-15 delivered |
|
| D14.2 |
Methodology for quality assurance |
PSNC |
Spec. |
Int. |
6 |
delivered |
|
| D14.3 |
Architecture requirements document |
PSNC |
Spec. |
Int. |
12 |
delivered |
|
| D14.16-D14.18 |
Yearly reports (D14.16,
D14.17,
D14.18) |
PSNC |
Report |
IST |
12, 24, 36 |
all delivered |
|
|
