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

From D4Science Wiki
Jump to: navigation, search
 
(36 intermediate revisions by the same user not shown)
Line 1: Line 1:
The '''D4Science Ecosystem''' is composed by 3 groups of resources:
+
The '''D4Science Infrastructure''' is composed by 2 groups of resources:
  
* resources provided by the site managed by 4 different project partners: CNR, FAO, FIN, NKUA
+
* resources provided by the sites managed by different EU project partners (iMarine, EUBrazilOpenBio, etc) or provided by external partners sites having an established collaboration with some of the EU Projects.
* resources provided by external partners having an established collaboration with the iMarine project  : ASGC Taiwan
+
* resources accessible using a federated approach.
* resources belonging to the CoP 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:
+
In particular the iMarine project partners ( CNR, NKUA, FAO, FIN)  and its external partner ( ASGC)  provide hosting resources:
  
 
* '''[[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 resources running gCube software
 
* '''[[gLite Resources|gLite/EMI Resources ]]:''' the resources running gLite and EMI middlewares
 
* '''[[Hadoop Resources |Hadoop Resources]]:''' the resources running Hadoop software
 
* '''[[Other Resources |Other Resources]]:''' the resoruces running Other type of Services like GeoServer, ActiveMQ etc.
 
  
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:
+
where to deploy EMI/UMD,  gCube, Hadoop and other needed software:
 +
 
 +
* '''[[gCube Resources|gCube Resources ]]:''' the gCube software resources
 +
* '''[[EMI/UMD Resources|EMI/UMD Resources ]]:''' the EMI and UMD middleware resources
 +
* '''[[Hadoop Resources |Hadoop Resources]]:''' the Hadoop software resources
 +
* '''[[Runtime Resources |Runtime Resources]]:''' other type of  Resources exploited  at runtime by  the gCube Services.
 +
 
 +
As said, besides the resources iMarine hosts in the D4Science Infrastructure, iMarine is establishing close interoperability links with other infrastructures, many of them already available in the D4Science Infrastructure. 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:
 
The Federated Resources can be grouped in 3 categories:
  
* '''[[WP5 Computing and Storage Resources Providers | Computing and Storage Resources Providers ]]'''
+
* '''[[Computing and Storage Resources Providers | Computing and Storage Resources ]]'''
* '''[[WP5 Community Resources Providers | Community Resources Providers]]'''
+
* '''[[Community Resources | Community Resources]]'''
* '''[[WP5 Other Resources Providers | Other Resources Providers]]'''
+
* '''[[Ecosystem Components| Ecosystem Components]]'''
 +
 
 +
A subset of the resources part of  the production infrastructure are  dedicated to the Quality Assurance tasks:
 +
 
 +
* '''[[Pre-Production Resources|Pre-Production Resources ]]:''' the resources dedicated to the Quality Assurance tasks
 +
 
 +
The development infrastructure instead is composed by the following resources:
 +
 
 +
* '''[[Development Resources|Development Resources ]]'''

Latest revision as of 14:46, 22 October 2013

The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Infrastructure is composed by 2 groups of resources:

  • resources provided by the sites managed by different EU project partners (iMarine, EUBrazilOpenBio, etc) or provided by external partners sites having an established collaboration with some of the EU Projects.
  • resources accessible using a federated approach.

In particular the iMarine project partners ( CNR, NKUA, FAO, FIN) and its external partner ( ASGC) provide hosting resources:

  • Hosting Resources: the physical and virtualized resources supporting the infrastructure

where to deploy EMI/UMD, gCube, Hadoop and other needed software:

As said, besides the resources iMarine hosts in the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Infrastructure, 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. Infrastructure. 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:

A subset of the resources part of the production infrastructure are dedicated to the Quality Assurance tasks:

The development infrastructure instead is composed by the following resources: