DCI-Bridge is implemented as a set of Web services that bind together in flexible ways on demand to deliver user services in Grid and/or cluster and/or cloud and/or Web services environments.
DCI Bridge is a web application (sevice) that provides standard access to the distributed computing infrastructures (DCIs) like grids, desktop grids, clusters, clouds and service based computational resources by implementing the specification of the OGSA Basic Execution Service 1.0.
The DCI Bridge web application creates a transparent layer between the users (workflow systems) and the DCI systems. The user can submit jobs to the various DCI systems using the OGSA Basic Execution Service (BES) interface defined here. As a result, the users do not have to learn the access protocol of the various DCI systems since they are hidden behind the BES interface.
The DCI Bridge gives support to the use of the Meta Broker which is able to choose the most ideal environment for the job from the available execution resources. The DCI Bridge will do the task in this specified environment.
DCI Bridge structure
- Resource registry
- Online configuration interface
- ResourceConfiguration service
- Runtime system
- BESFactoryService service
- Job registry
- Proxy manager
- Executor layer handler
- Input queue
- Meta Broker client
- Middleware plugin and queue handler
- Output queue
- Status manager
- Application management
- BESManagement and online interface for its use
- Application monitor + online interface
- Plugin monitor + online interface
- Job monitor + online interface
The job of the Resource Registry subsystem is to provide an online configuration interface to be able to configure the resources which can be called by the DCI Bridge. Also it provides information about the configured resources to other external software components. For the configuration of the resources an online interface is available which is part of the web application. The access to this interface is controlled with container authentication. The available resource publishing goes through on the ResourceConfiguration service which is accessible with http/https protocol as a generic web service.
The job of the Application Management subsystem is the implementation of BES-Management Port-type from the fifth volume of the OGSA Basic Execution Service 1.0 specification which makes possible to supervise the software based access of the BES Factory service.
The Runtime System does the effective job running. The subsystem can be called with a service made by OGF which implements the BES WSDL and it makes the operations defined by the OGSA Basic Execution Service 1.0 specification on different grid/cloud/service based middlewares. The separate running systems can be handled with plugins and their numbers can be increased without any restriction.
The job of the Monitor subsystem is to handle and visualize the logs and messages of the DCI Bridge, the plugins and the running jobs.
|GT2, GT4, GT5||GT2 Documentation