Difference between revisions of "Data Transfer Facilities"
From Gcube Wiki
Andrea.manzi (Talk | contribs) (→Overview) |
Andrea.manzi (Talk | contribs) |
||
| Line 1: | Line 1: | ||
'''THIS PAGE IS UNDER CONSTRUCTION''' | '''THIS PAGE IS UNDER CONSTRUCTION''' | ||
| + | |||
| + | == Overview == | ||
The implementation of a reliable data transfer mechanisms between the nodes of the iMarine Data e-Infrastructure is one of the main objectives when dealing with large set of multi-type datasets distributed across different repositories, like the one made available by the iMarine EA Community of Practice. | The implementation of a reliable data transfer mechanisms between the nodes of the iMarine Data e-Infrastructure is one of the main objectives when dealing with large set of multi-type datasets distributed across different repositories, like the one made available by the iMarine EA Community of Practice. | ||
| Line 7: | Line 9: | ||
This document outlines the design rationale and high-level architecture of such components. | This document outlines the design rationale and high-level architecture of such components. | ||
| − | == | + | == Key Features == |
The components part of the subsystem provide the following main key features: | The components part of the subsystem provide the following main key features: | ||
| Line 15: | Line 17: | ||
* | * | ||
| − | + | ||
Revision as of 15:17, 26 April 2012
THIS PAGE IS UNDER CONSTRUCTION
Overview
The implementation of a reliable data transfer mechanisms between the nodes of the iMarine Data e-Infrastructure is one of the main objectives when dealing with large set of multi-type datasets distributed across different repositories, like the one made available by the iMarine EA Community of Practice.
To promote an efficient and optimized consumption of these data resources, a number of components have been designed to meet the data transfer requirements.
This document outlines the design rationale and high-level architecture of such components.
Key Features
The components part of the subsystem provide the following main key features:
Main Components
- the Data Scheduler & Agent components
- this family of components guarantees VO/VRE Administrators the possibility to transfer data among Data Sources and Data Storages. It can be exploited as well by any client or web services to implements data movement between infrastructure nodes by relying as well on the facilities offered by the Result Set components
- the Result Set components
