EGI-Engage:WP4.3-D4Science
Jump to navigation
Jump to search
Objective
Integration for gCube and the D4Science infrastructure (M1 - M12)
This activity will integrate D4Science resources at Engineering (commercial) and CNR (public) into the EGI Federated Clouds infrastructure. The gCube framework will be extended to use EGI Federated Cloud resources through implementing OCCI client capabilities.
Involved Partners
CNR - ISTI
Engineering
Roadmap
Two use cases were selected to start the integration:
- running a gCube WN in FedCloud. The gCube worker node (the name of the gCube service is Executor) is the service where the D4Science computations are executed. The Executor can perform several types of job depending on the way the job is assigned to it. Among those different policies it is worth noticing the following ones: as a scheduler, it executes local code at regular intervals as specified in the job activation, similar to a cron command; as a worker node It fetches job from an ActiveMQ. This last case is the most demanding one, The job to be executed, the data to be processed and the configuration to be applied are all downloaded from the gCube storage via the persistent identifiers collected in the job description.
- running a DataMiner in FedCloud. The gCube DataMiner is a service hosting a number of models. It adopts a plugin-based architecture where each model is implemented via a service plugin. New models can easily be added by simply deploying a new plugin in the service. The interface exposed is a WPS standard Interface.
These WNs/DataMiner would be deployed by human triggered action from the D4Science UI. Plan to use jOCCI to interact with resources.