TWiki> EGEE Web>Interoperability (revision 7)EditAttachPDF

Strategy And Plans For Interoperability With Other Grid Infrastructures

Overview

This document outlines the strategy and plans for Interoperability between EGEE and other Grid infrastructures. This work builds upon previous experiences most notability the interoperations activity with OSG and the interoperations activity with ARC. This experience has been used to create the Interoperations Cookbook which describes what is required to achieve interoperation between infrastructures. The strategy follows a simple five point plan, each point is described in more details below.

  1. Identify requirement
  2. Analysis of the problem
  3. Develop solutions
  4. Operational Support
  5. Standards

Requirement

Experience has shown that an interoperations activity can not successfully get underway without first identifying the infrastructures which need to interoperate and the user community for which this is required. Therefore the first step is for EGEE to actively engaging with its user community to help identify with which infrastructure interoperation is required. The demand from the user community is key in driving the activity. If a VO has resources provided by an infrastructure project other than EGEE and requires that EGEE interoperates with that infrastructure, this requirement should be brought to the TMB for discussion and the task will be prioritized.

Analysis

The second step is to understand the similarities and differences between the infrastructures. This can be achieved by investigating the main functions provided by the infrastructures and producing an interoperability matrix. The typically areas covered include security, information systems, job management and data management. Once the scale of the problem is understood a decision can be made on the most pragmatic way to achieve interoperability. The most common techniques to use are described in the Interoperations Cookbook. This task will be carried in collaboration between technical representatives of EGEE, the VO and the other infrastructure. The final plan should be brought back to the TMB for discussion and the various tasks required to be carried out by EGEE members will be prioritized.

Development

Components need to be developed which implement the proposed solutions which were identified in the analysis phase. The development work should be carried out by the relevant developers to minimize the overhead of a new developer requiring to understand a component in order to make a small change.

Support

Once the components have been developed, the information required to provide a production quality service needs to be disseminated to the operations teams. On going support needs to be given and the situation needs to be continuously monitored to ensure that interoperability is maintained.

Standards

The long term goal is to achieve interoperability via the use of standards

EGEE is actively involved in a number of standardization efforts. The interoperability activity is particularly focused on identifying areas for standardization and following up on standardization efforts. The following is a list of standards that are considered to be important for interoperability and their current status. This is a continuation of the EGEE II EGEE Standards Survey and provides the current status of the relevant standard that were identified in the report. The KnowARC project has produced a similar report .

Security

XACML

Standards Body
Open Grid Forum (OGF)
Document
Description
OGSA-AUTHZ XACML
Relevance to EGEE
Status
Work in progress

Information Systems

GLUE Schema v2.0

Standards Body
Open Grid Forum (OGF)
Document
GLUE Specification v. 2.0
Description
The GLUE-WG provides a recommendation for an abstract information model which is expressed via a set of attributes and attribute semantics, the relationship between the attributes and the syntax for attribute values where applicable. The main purpose of the model is to facilitate interoperation between grid infrastructures via enabling the development of interoperating grid middleware components and as such the model was designed in response to existing use cases. The focus is on use cases which span multiple grid infrastructures that may rely on different middleware. The collected use cases are published as a information document. The existing version 1.3 of the Glue Schema document and Nordugrid Schema was used as a starting point for the work. The abstract information model enables a concrete data models to be rendered in various formats. These renderings are not seen as an output of the group but are the ultimate result of the work.
Relevance to EGEE
A common information model for the description of Grid resources is an essential requirement for interoperating Grid infrastructures and its implementation interacts with every Grid component being modeled.
Status
Work in progress

Job Management

Job Submission Description Language

Standards Body
Open Grid Forum (OGF)
Document
Job Submission Description Language v1.0
Description
The JSDL-WG has provided a specification for an abstract standard Job Submission Description Language (JSDL) that is independent of language bindings. A normative XML Schema corresponding to the JSDL specification has been included in the JSDL specification document.
Relevance to EGEE
The Job Submission Description Language specification is useful as a standard notation for job description. By making the gLite infrastructure JSDL-compliant, it will be able to accept jobs produced for other JSDL-compliant Grid systems without any modifications.
Status
The JSDL-WG is working on improving and extending this language to address a wider class of jobs, including Web service invocations, and issues raised by the Grid community. Further, the JSDL-WG plans to work with Grid projects and DRM vendors to produce a document of translation tables to and from the scheduling languages of a set of popular batch systems for both the job requirements and resource description attributes of those languages, which are relevant to the JSDL.

Basic Execution Service

Standards Body
Open Grid Forum (OGF)
Document
OGSA Basic Execution Service v1.0
Description
The aim of the OGSA-BES-WG (OGSA Basic Execution Services) working group is to define a Web Services-based interface for creating, monitoring, and controlling computational entities such as UNIX or Windows processes, Web Services, or parallel programs. These entities are called activities and they are defined by the Job Submission Description Language (JSDL). A BES implementation executes each activity that it accepts on an appropriate computational resource, which - depending on the BES implementation and the type(s) of activities supported - may be a single computer; a cluster managed through a local resource manager (e.g. LSF, PBS, etc); a Web Service hosting environment; or even another BES implementation.
Relevance to EGEE
The Basic Execution Service specification is very important because it provides a standard interface to Job Management components. For EGEE, this would mean that the gLite WMS and CREAM CE can be made BES-compliant so that they could be used as standard components also outside the gLite infrastructure.
Status
The base specifcation document is now in the final version.

Execution Environment

Standards Body
Open Grid Forum (OGF)
Document
Description
Relevance to EGEE
Status
Work in progress

Data Management

Storage Resource Manager

Standards Body
Open Grid Forum (OGF)
Document
Description
[http://sdm.lbl.gov/srm-wg/][SRM]]
Relevance to EGEE
Status
Work in progress

GridFTP

Standards Body
Open Grid Forum (OGF)
Document
Description
GridFTP v2 Protocol Description
Relevance to EGEE
Status
Work in progress

Operations

Usage Record

Standards Body
Open Grid Forum (OGF)
Document
Description
Relevance to EGEE
Status
Work in progress

Resource Usage Service

Standards Body
Open Grid Forum (OGF)
Document
Description
Relevance to EGEE
Status
Work in progress
Edit | Attach | Watch | Print version | History: r11 | r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r7 - 2008-11-10 - LaurenceField
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback