Difference between revisions of "Virtual Research Environments Deployment and Operation: Plan"

From D4Science Wiki
Jump to: navigation, search
m
m (Analysis Phase)
Line 9: Line 9:
 
== Analysis Phase ==
 
== Analysis Phase ==
  
The analysis phase is expected to be continuous, i.e. VRE "managers" (both users playing the role of [[Role_VRE_Designer|VRE Designer]] or [[Role_VRE_Manager|VRE Manager]]), have to deal with novel scenario specifications with no planned schedule as well as with revised versions of existing scenario specifications resulting from the exploitation of the released services with no fixed schedule.  
+
The analysis phase is expected to be continuous, i.e. VRE "managers" (both users playing the role of [[Role_VRE_Designer|VRE Designer]] or [[Role_VRE_Manager|VRE Manager]]), have to deal with novel scenario specifications with no planned schedule as well as with revised versions of existing scenario specifications resulting from the exploitation of the released services with no fixed schedule.
The result of the analysis phase is documented in a per scenario analysis report and leads to the identification of Virtual Research Environments to be deployed as well as actions governing the evolution of the deployed VREs, e.g. deploy a new function, add a new data source.  
+
 
+
The result of the analysis phase is documented in a per scenario analysis report and leads to the identification of Virtual Research Environments to be deployed as well as actions governing the evolution of the deployed VREs, e.g. deploy a new function, add a new data source. In some cases, namely data source integration and vertical applications (i.e. applications specifically conceived to combine community specific applications and tools with gCube facilities offered through the APIs), this lead to development tasks.
<!--
+
 
+
{| align="center" border="1" cellpadding="4" cellspacing="0"
+
!| Scenario Description (*)
+
!!| Analysis State
+
!!| Current Analysis Report
+
!!| Assigned VO
+
|-
+
!! bgcolor="yellow" colspan="4"| D4Science-II Scenarios
+
|-
+
|| '''[https://networking.wiki.d4science-ii.research-infrastructures.eu/networking/index.php/AquaMaps_Scenario AquaMaps]'''
+
|| Ongoing
+
|| [[AquaMaps Scenario Analysis]]
+
|| [[FARM VO]]
+
|-
+
|| '''[https://networking.wiki.d4science-ii.research-infrastructures.eu/networking/index.php/FCPPS_Scenario FCPPS]'''
+
|| Ongoing
+
|| [[FCPPS Scenario Analysis]]
+
|| [[FARM VO]]
+
|-
+
|| '''[https://networking.wiki.d4science-ii.research-infrastructures.eu/networking/index.php/ICIS_Scenario ICIS]'''
+
|| Ongoing
+
|| [[ICIS Scenario Analysis]]
+
|| [[FARM VO]]
+
|-
+
|| '''[https://networking.wiki.d4science-ii.research-infrastructures.eu/networking/index.php/INSPIRE_Scenario INSPIRE]'''
+
|| Ongoing
+
|| [[INSPIRE Scenario Analysis]]
+
|| [[INSPIRE VO]]
+
|-
+
|| '''[https://networking.wiki.d4science-ii.research-infrastructures.eu/networking/index.php/DRIVER_Scenario DRIVER]'''
+
|| Ongoing
+
|| [[DRIVER Scenario Analysis]]
+
|| [[Ecosystem VO]]
+
|-
+
!! bgcolor="yellow" colspan="4"| Other Scenarios
+
|-
+
|| '''[https://networking.wiki.d4science-ii.research-infrastructures.eu/networking/index.php/Vessel_Transponded_Information_Scenario VTI]'''
+
|| Ongoing
+
|| [[VTI Scenario Analysis]]
+
|| [[FARM VO]]
+
|-
+
|| '''[https://networking.wiki.d4science-ii.research-infrastructures.eu/networking/index.php/GMan_Scenario gMan]'''
+
|| Ongoing
+
|| [[gMan Scenario Analysis]]
+
|| [[Ecosystem VO]] (***)
+
|-
+
|| '''EM'''
+
|| N/A
+
|| N/A
+
|| [[Ecosystem VO]] (**)
+
|}
+
 
+
(*) The Scenario Description pages are hosted by the [https://networking.wiki.d4science-ii.research-infrastructures.eu/networking/index.php/NA5_Home NA5 Wiki].
+
 
+
(**) This VRE results from the union of two VREs ([[GCM VRE]] and [[GVM VRE]]) hosted by the [[EM VO]] until March 2010.
+
 
+
(***) This VRE has been hosted by the [[Arts-Humanities VO]] until October 2011. In October 2011 it was decided to move the VRE in the [[Ecosystem VO]]. -->
+
  
 
== Deployment Phase ==
 
== Deployment Phase ==

Revision as of 20:26, 29 February 2012

The iMarine project is expected to deploy and operate a number of Virtual Research Environments (VREs) to satisfy the needs of its community.

The set of Virtual Research Environments (VREs) iMarine operates as well as their evolution in terms of resources involved and services offered is a consequence of the analysis of the requirements captured by the Ecosystem Approach Community of Practice. In addition to that, others scenarios are expected to spring up and be analysed during the project lifetime as a consequence of the expression of interests coming from external communities, i.e. communities that are not part of the iMarine consortium. The analysis phase is followed by a deployment phase, i.e. the activity leading to the development and evolution of the identified VOs and VREs.

Analysis Phase

The analysis phase is expected to be continuous, i.e. VREVirtual Research Environment. "managers" (both users playing the role of VRE Designer or VRE Manager), have to deal with novel scenario specifications with no planned schedule as well as with revised versions of existing scenario specifications resulting from the exploitation of the released services with no fixed schedule.

The result of the analysis phase is documented in a per scenario analysis report and leads to the identification of Virtual Research Environments to be deployed as well as actions governing the evolution of the deployed VREs, e.g. deploy a new function, add a new data source. In some cases, namely data source integration and vertical applications (i.e. applications specifically conceived to combine community specific applications and tools with gCube facilities offered through the APIs), this lead to development tasks.

Deployment Phase

To meet the expectations of the above scenarios, the iMarine supports the operation of the following Virtual Research Environments (VREs operated in the context of a number of Virtual Organisations). For each of them the current state is reported as well as the plans governing the evolution from the following points of view:

  • data, i.e. the data sources made available through them;
  • functional, i.e. the functionality supported by them;
  • software, i.e. the version of the gCube technology supporting their operation.

Ecosystem VOVirtual Organization; Development Plan and State

This Virtual Organisation has been deployed to serve the needs of any community that need to use the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. resources.

Name Type Description Evolution Plan State (*)
Overall Data Functionality Software
Ecosystem VOVirtual Organization; N/A Data Functionality Software Operational N/A N/A N/A
TryIt VREVirtual Research Environment. N/A Data Functionality Software Operational N/A N/A N/A
EM VREVirtual Research Environment. N/A Data Functionality Software Operational N/A N/A N/A
DRIVER VREVirtual Research Environment. N/A Data Functionality Software Operational N/A N/A N/A
gMan VREVirtual Research Environment. N/A Data Functionality Software Operational N/A N/A N/A
(*) These numbers corresponds to the number of actions done w.r.t. the number of actions planned.

FARM VOVirtual Organization; Development Plan and State

This Virtual Organisation has been deployed to serve the Fisheries and Aquaculture Resources Management community.

Name Type Description Evolution Plan State (*)
Overall Data Functionality Software
FARM VOVirtual Organization; N/A Data Functionality Software Operational N/A N/A N/A
AquaMaps VREVirtual Research Environment. N/A Data Functionality Software Operational N/A N/A N/A
FCPPS VREVirtual Research Environment. N/A Data Functionality Software Operational N/A N/A N/A
ICIS VREVirtual Research Environment. N/A Data Functionality Software Operational N/A N/A N/A
VTI VREVirtual Research Environment. N/A Data Functionality Software Operational N/A N/A N/A
(*) These numbers corresponds to the number of actions done w.r.t. the number of actions planned.

gCubeApps VOVirtual Organization; Development Plan and State

This Virtual Organisation has been created to serve the needs of the any community willing to experience with specific applications supported by the gCube technology.

Name Type Description Evolution Plan State (*)
Overall Data Functionality Software
gCubeApps VOVirtual Organization; N/A N/A N/A N/A Operational N/A N/A N/A
DocumentsWorkflow VREVirtual Research Environment. N/A N/A N/A N/A Operational N/A N/A N/A
EcologicalModelling VREVirtual Research Environment. N/A N/A N/A N/A Operational N/A N/A N/A
TimeSeries VREVirtual Research Environment. N/A N/A N/A N/A Operational N/A N/A N/A
VesselActivitiesAnalyzer VREVirtual Research Environment. N/A N/A N/A N/A Operational N/A N/A N/A
(*) These numbers corresponds to the number of actions done w.r.t. the number of actions planned.