IMarine Data E-Infrastructure Deployment and Operation: Resources
The iMarine Data e-InfrastructureAn operational combination of digital technologies (hardware and software), resources (data and services), communications (protocols, access rights and networks), and the people and organizational structures needed to support research efforts and collaboration in the large. is composed by 2 groups of resources:
- resources provided by the sites managed by 4 different iMarine project partners (CNR, FAO, FIN, NKUA) or provided by external partners sites having an established collaboration with iMarine ( ASGC Taiwan )
- resources belonging to the iMarine CoPCommunity of Practice. wich are planned to be accessible using the Federated approach.
The project partners and the external partners provide hosting resources:
- Hosting Resources: the physical and virtualized resources supporting the infrastructure
where to deploy gLite/EMI, gCube, Hadoop software and other needed software:
- gCube Resources : the gCube software resources
- gLite/EMI Resources : the gLite and EMI middleware resources
- Hadoop Resources: the Hadoop software resources
- Runtime Resources: other type of Resources exploited at runtime by the gCube Services.
As said, besides the resources hosted in iMarine Data e-InfrastructureAn operational combination of digital technologies (hardware and software), resources (data and services), communications (protocols, access rights and networks), and the people and organizational structures needed to support research efforts and collaboration in the large. itself, iMarine is establishing close interoperability links with other infrastructures, many of them already available in the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem. These collaborations are based on a Research Collaboration Model where resources of one infrastructure can be consumed or accessed by another infrastructure and vice-versa through an agreement community-based approach under the control of the infrastructure’s middleware:
The Federated Resources providers can be grouped in 3 categories:
