iMarine and our contribution
1Presentation methodology: PechaKucha 20x20
Andrea Manzi (CERN)Nick Drakopoulos (CERN)
ITGT
Outline
• What iMarine is• Main objectives• Our contribution– WP5– WP9 & 11– Future Activities
• Links
2
What is iMarine?
• iMarine is an open and collaborative initiative that will establish a data infrastructure to support the Ecosystem Approach to fisheries management and conservation of marine living resources.
3
Finance and administration • ERCIM
Technology• CNR• NKUA• CERN• ENG• FORTH• TERRA2 Community of Practice
• FAO• FIN • UNESCO• CRIA• IRD
• SP2000• VLIZ• NEAFC
Dissemination• Trust-IT
4
The Consortium
Objectives
• Policy development • Establishment of an iMarine EA Community of
Practice Board•Policies for data sharing and Governance of the
infrastructure
5
Policy development
•Data infrastructure management and operation• Resource provision and monitoring• Operation of concrete EA business cases
6
management and operation
Objectives
extension, adaptation and deployment
• Service enrichment and deployment• Implementation of the iMarine CoPBoard defined
policies• Focus on articulating the management and life-cycle
of biological and socio-economical data• Extend the gCube Framework which enables the
building and operation of a Service Oriented Infrastructure
7
Objectives
Syst
em
Bound
ary
Application Platform
ResourceManagement
ResourceDiscovery
Process Execution
Security
En
ab
ling
WorkspaceTime SeriesEcologicalNiche
Modelling
Business DocumentWorkflow
Applica
tion
VesselActivityAnalyser Internal interactions
Externalinteractions
SearchMining
Storage
AccessD
ata
Man
ag
em
ent
Transformation Transfer
EGI CF 2012 8
Platforms:
- gCore : JAVA WS-Core extension
- Tomcat
gCube Architecture
CERN Role
• Organization of work to reach objectives :– iMarine Project consists of 11 work packages. – Our contribution for iMarine is in WP5( Leader),
WP9, WP11 (Deputy technical director).
• Data e-Infrastructure Operation• Data Transfer Facilities and Data Management API’s
9
WP5
WP9 & 11
• Data e-Infrastructure Operation :– Operational procedures definition– Infrastructure incidents management– Infrastructure deployment and upgrade
• Data Infrastructure Availability, Monitoring and Accounting :– monitor the status of the infrastructure– account of the infrastructure exploitation – verify the availability of the core functionality provided
by the infrastructure
10
CERN Role : WP5
Managed Resources
• ~ 150 GHNs• ~ 60 TB disk space • ~ 6800 CPUs
Applications
• 15 Virtual Research Environments (Data Mining, Data Curation and Analysis, Niche Modeling, …)
Linking
• Computing Infrastructures (EGI, MS Azure, …)
• Data Infrastructures (MyOcean, GBIF, OBIS, ..)
Geographic Coverage
• Europe (Italy, Spain, Greece, France, …)• America (Brazil)• Asia (Taiwan, Philippines)
Data Infrastructure
12
Taxonomies• Catalogue of Life ( Col)• Integrated Taxonomic Information System ( ITIS)• World Register of Marine Species (WoRMS)
Marine Species Data• Ocean Biogeographic Information System (OBIS)• Global Biodiversity Information Facility (GBIF)
Reports• Fisheries Global Information System (FIGIS)
Environmental data• MyOcean
Earth Observation Data• GENESI– Digital Earth Community (GENESI-DEC)
Statistical Data• FAO SDMX Registry• IRD UMR EME
Species Maps• AquaMaps
Data Resources
13
• Migration to NAGIOS the “De facto” standard for distributed infrastructure monitoring
• Deployed on each infrastructure node • GHNs and Third Party components monitoring• Most of Site Managers already skilled• GUI Interface for free
Standard Monitoring Solution
CERN Role: WP9 & 11
• Data Transfer Facilities :– Develop a gCube service to integrate existing
services and technologies to deliver an efficient, secure, and reliable data transfer commodity;
– Support the transfer of multiple data formats over different transfer protocols
14
• Data Transfer Facilities :– The set of the Data Transfer Scheduler & Agent
components provides data transfer among Data Sources and Data Storages. It can be exploited by VO/VRE Administrators and by any client or web services.
VO: Virtual Organization (The group hosting VRE’s)VRE: Virtual Research Environment (The gCube applications)
15
CERN Role: WP9 & 11
• Data Transfer Scheduler :– The Data Transfer Scheduler Service is responsible
for the transfer scheduling activity delegating the transfer logic to the series of gDT Agent deployed on the infrastructure.
16
CERN Role: WP9 & 11
• Data Transfer Agent :– The Data Transfer Agent Service has been
implemented with the aim of facilitating the transfer of data ( both structured and unstructured ) for the following use cases:• Transfer local files to a remote GHN• Transfer from DataSource to a remote GHN• Transfer from DataSource to a DataStorage
17
CERN Role: WP9 & 11
• Data Transfer Portlet:– The scheduler portlet is an interface implemented
for the client with the general purpose of scheduling transfers. The Scheduler Portlet provides as well statistics about the agent nodes so that the user can choose the most beneficial agent.
18
CERN Role: WP9 & 11
Near Future Activities
• Data Transfer Facilities :– To integrate all data transfer components with
messaging.– Extensions related to requirements coming from
EA CoP• Data Infrastructure Operation:– Evaluation of Puppet– Development/Integration of tools for
infrastructure topology.
19
More information...
• iMarine site:– http://www.i-marine.eu
• CERN IT Project Page :– https://twiki.cern.ch/twiki/bin/view/IT/
IMarineProject• Project wiki :– http://wiki.i-marine.eu
20
THANKS!
Top Related