Difference between revisions of "IMarine Data E-Infrastructure Deployment and Operation: Resources"

From D4Science Wiki
Jump to: navigation, search
Line 10: Line 10:
 
* '''[[gCube Resources|gCube Resources ]]:''' the resources running gCube software
 
* '''[[gCube Resources|gCube Resources ]]:''' the resources running gCube software
 
* '''[[gLite Resources|gLite/EMI Resources ]]:''' the resources running gLite and EMI middlewares
 
* '''[[gLite Resources|gLite/EMI Resources ]]:''' the resources running gLite and EMI middlewares
* '''[[Hadoop Resource |Hadoop Resources]]:''' the resources running Hadoop software
+
* '''[[Hadoop Resources |Hadoop Resources]]:''' the resources running Hadoop software
 
* '''[[Other Resources |Other Resources]]:''' the resoruces running Other type of Services like GeoServer, ActiveMQ etc.
 
* '''[[Other Resources |Other Resources]]:''' the resoruces running Other type of Services like GeoServer, ActiveMQ etc.
  

Revision as of 18:39, 7 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 EMI, gCube and Hadoop software:

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: