OOI CyberInfrastructure: Data Management Architecture Specification Workshop

1. OOI CyberInfrastructure:Data Management Architecture Specification Workshop June 30-July 1, 2008 Matthew Arrott, Ingolf Krueger, Claudiu Farcas, Emilia Farcas, Michael Meisinger, Igor Klacansky OOI CI Architecture & Design Team UCSD/Calit2

2. Overview • OOI CI Implementing Organization Goals • Workshop goals • OOI Cyber-Infrastructure • Data Management Subsystem

3. Goal of the OOI CI Implementing Organization • To build • The next generation community cyber-infrastructure for an integrated ocean observatory system • Funded by NSF’s MREFC program • Serving scientists, educators and the general public • Integrating the resources of 3 co-funded marine observatories under construction: coastal/global, and cabled regional • Providing cyber-infrastructure support for sensor access, instrument data acquisition, processing and distribution, data analysis and visualization, mission planning and control • Guaranteeing security, data integrity and quality of service • With operational scope of 30 years • Designed and constructed in a time frame from 6/2007 to 2014

4. Goals of this workshop • Focus on enriching the current understanding of the DM subsystem from the scientific data management point of view • Identify • capabilities provided by current technologies • gaps to be covered, and possible solutions for integrating these tech. • best fit of the current technologies in the overall DM architecture • Refine high level architecture • Clarify technology mappings • Three aspects will be discussed: • Data flow from instruments (direct access, data streaming or other means) to preservation repositories • Data discovery and access (including basic presentation means), metadata handling, cataloging • Data distribution between facilities, replication, federation capabilities • models for data and metadata • publication and subscription • interaction protocols

5. OOI-CI Services Architectural Pattern

6. Relationship with the other subsystems • Data management subsystem implements a subset of the capabilities of the Data Services Network (from the overall CI arch) • Additional capabilities result from the interplay of the other subsystems (e.g., policy, governance, routing, etc.) • Note: Education and Public Engagement was intentionally omitted as it requires the same capabilities as the Modeling Subsystem

7. Basic capabilities expected from other subsystems • Common Operating Infrastructure • Message based communication interchange mechanism • Inside and inter-facility data distribution backbone • Support for policy/governance • Common Execution Infrastructure • Platform abstraction through VM encapsulation • Computation provisioning/scheduling • Instrument Services Network • Instrument abstractions through proxies • Basic data marshaling • Interfaces for data acquisition, control, monitoring • Modeling Services Network • Analysis and assimilation of data • Basic presentation mechanisms • Models and additional data streams

8. DSN High level architecture (simplified) • Simplified view of the Data Services Network focusing on Data Management capabilities • Note: Colors depict expected relationships with other subsystems, but do not cover all possible aspects of their interactions.

9. DSN High level architecture (one level deeper) • Basic capabilities expected from each constituent of the DSN • Note: Colors depict expected relationships with other subsystems, but do not cover all possible aspects of their interactions. • Not all expected capabilities are illustrated.

10. Technology mappings (tentative) • Exchange: OPeNDAP over a messaging system • Ingestion: design based on SSDS • Preservation: iRODS • Presentation: mix of OPeNDAP, THREDDS, VSTO • Mediation: VSTO Ontology, GEON Mediation Framework • Metadata: mix of SSDS Data Model, VSTO Ontology, and a spatial indexing strategy

11. Thanks! Thanks a lot for your important contributions and your time and efforts!