Automatic deployment of interoperable legacy code services

The Grid Execution Management for Legacy Code Architecture (GEMLCA) enables exposing legacy applications as Grid services without re-engineering the code, or even requiring access to the source files. The integration of current GT3 and GT4 based GEMLCA implementations with the P-GRADE Grid portal allows the creation, execution and visualisation of complex Grid workflows composed of legacy and nonlegacy components. However, the deployment of legacy codes and mapping their execution to Grid resources is currently done manually. This paper outlines how GEMLCA can be extended with automatic service deployment, brokering, and information system support. A conceptual architecture for an Automatic Deployment Service (ADS) and for an x-Service Interoperability Layer (XSILA) are introduced explaining how these mechanisms support desired features in future releases of GEMLCA

Service-oriented production grids and user support

Currently several production Grids offer their resources for academic communities. These Grids are resource-oriented Grids with minimal user support. The existing user support incorporates Grid portals without workflow editing and execution capabilities, brokering with no QoS and SLA management, security solutions without privacy and trust management, etc. They do not provide any kind of support for running legacy code applications on Grids. Production Grids started the migration from resource-oriented Grids to service-oriented ones. The migration defines additional requirements towards the user support. These requirements include solving interoperability among Grids, automatic service deployment, dynamic user management, legacy code support, QoA and SLA-based brokering, etc. This paper discusses some aspects of the user support needed for service-oriented production Grids

Workflow level interoperation of grid data resources

The lack of widely accepted standards and the use of different middleware solutions divide today’s Grid resources into non-interoperable production Grid islands. On the other hand, more and more experiments require such a large number of resources that the interoperation of existing production Grids becomes inevitable. This paper, based on the current results of grid interoperation studies, defines generic requirements towards the workflow level interoperation of grid solutions. It concentrates on intra-workflow interoperation of grid data resources, as one of the key areas of generic interoperation, and describes through an example how existing tools can be extended to achieve the required level of interoperation