Difference between revisions of "IMarine Data E-Infrastructure Deployment and Operation: Resources"
Andrea.manzi (Talk | contribs) |
Andrea.manzi (Talk | contribs) |
||
| Line 8: | Line 8: | ||
* '''[[Hosting Resources|Hosting Resources]]:''' the physical and virtualized resources supporting the infrastructure | * '''[[Hosting Resources|Hosting Resources]]:''' the physical and virtualized resources supporting the infrastructure | ||
| − | * '''[[gCube Resources|gCube Resources ]]:''' the | + | * '''[[gCube Resources|gCube Resources ]]:''' the gCube software resources |
| − | * '''[[gLite Resources|gLite/EMI Resources ]]:''' the | + | * '''[[gLite Resources|gLite/EMI Resources ]]:''' the gLite and EMI middleware resources |
| − | * '''[[Hadoop Resources |Hadoop Resources]]:''' the | + | * '''[[Hadoop Resources |Hadoop Resources]]:''' the Hadoop software resources |
| − | * '''[[Other Resources | | + | * '''[[Other Resources |Runtime Resources]]:''' other type of Services deployed on the infrastructure and exploited at runtime by gCube Services. |
As said, besides the resources hosted in D4Science Ecosystem itself, iMarine is establishing close interoperability links with other infrastructures, many of them already available in the D4Science 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: | As said, besides the resources hosted in D4Science Ecosystem itself, iMarine is establishing close interoperability links with other infrastructures, many of them already available in the D4Science 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: | ||
Revision as of 12:24, 8 December 2011
The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem is composed by 3 groups of resources:
- resources provided by the site managed by 4 different project partners: CNR, FAO, FIN, NKUA
- resources provided by external partners having an established collaboration with the iMarine project : ASGC Taiwan
- resources belonging to the CoPCommunity of Practice. with are planned to be accessible trough the Ecosystem using the Federated approach.
The project partners and the external partners provide hosting resources used to deploy gLite/EMI, gCube and Hadoop software:
- Hosting Resources: the physical and virtualized resources supporting the infrastructure
- 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 Services deployed on the infrastructure and exploited at runtime by gCube Services.
As said, besides the resources hosted in D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem 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 can be grouped in 3 categories:
