3 rd RDA Plenary Dublin, 26 -28 March 2014 Brokering IG Session S. NATIVI, J. PEARLMAN AND M. CRAGLIA
Agenda Introduction (All) - 15 minutes; Brokering framework (Chairs) – 15 minutes; ◦ The Earth Cube experience (Jay Pearlman) – 10 minutes; ◦ The GEOSS Experience (Stefano Nativi) – 10 minutes; ◦ The INSPIRE Experience (Max Craglia) – 10 minutes Break – 15 minutes Discussion on “Governance of Brokering middleware” – 30 minutes Lunch – 60 minutes Designing a new WG (All) – 40 minutes Wrap-up (Chairs) – 5 minutes nativi@iia.cnr.it nativi@iia.cnr.it
WHY BROKERING? WHAT IS BROKERING?
Discipline A .. . Discipline B Discipline N
Developing Interoperbility • Federation approach : a Common (lingua franca) solution for all Standardization Federation Common Technological and Semantic baseline Common interoperability for all the domains and organizations
Developing Interoperbility • Complement Fedarion with Brokering Standardization Federation Common Brokering Technological /interconnection Domain and Semantic interoperability Multi-domain (and baseline multi-organizational ) standards mediation Cohese for a given infrastructures domain Global infrastructures (e.g. SoS, NoN)
Brokering Framework (Intermediation & Transformation) .. .
Brokering Framework (Intermediation & Transformation) .. .
Brokering Benefits Lowers barriers to participation in distributed systems for both users and resource providers ◦ minimal burden or cost impact on existing systems; Accelerates interconnection of disparate systems; Facilitates sustainability, reusability, extensibility, and flexibility of the infrastructure Enhances multi-disciplinary interoperability via introduction of new capabilities across multiple domains; Removes need to impose common (e.g. federal, “top - down”) specifications and software components enabling a more adaptive “bottom - up” evolution of the infrastructure nativi@iia.cnr.it
Several Projects and Programmes are adopting or testing a Brokering approach BROKERING COMMUNITY
The GEOSS Experience STEFANO NATIVI (CNR-IIA)
GEO (Group on Earth Observations) • launched in response to calls for action by the 2002 World Summit on Sustainable Development, Earth Observation Summits, and by the G8 (Group of Eight) leading industrialized countries • voluntary partnership of 90 governments and 67 international organizations • provides a framework within which these partners can develop new projects and coordinate their strategies and investments • charged with developing GEOSS
Global Earth Observation System of Systems (GEOSS)
Rationale GEOSS Portal GEOSS Common Discovery and Access Broker Infrastructure Resource Registration Earth observations data, information and services
An ecosystem of multiple “Galaxies” nativi@iia.cnr.it nativi@iia.cnr.it
Data & Information Capacities «Traditional» Data/Information Systems Crowd-sourcing capacities Big Data capacities nativi@iia.cnr.it nativi@iia.cnr.it
The GEO Brokering Approach SeaDataNet SAEOS INPE OneGeology CWIC GENESI-DEC EEA-SDI EuroGEOSS EnviroGRIDS/ WaterML PANGAEA Clearinghouse WIS NASA GCMD/IDN GBIF Big Data NASA Platform GSFC- DAAC IODE Big Data Analitycs Citizen Oservatory nativi@iia.cnr.it
Enabling Community Applications Community & Citizen Apps GEOSS Portal GEONETcast apps nativi@iia.cnr.it nativi@iia.cnr.it
Current Assets GEO Home Page GEOSS Portal nativi@iia.cnr.it
Current Assets More than 20 brokered data providers – capacities, systems, Communities .. . Publish More than 7 Million (1.2 Million GEOSS Data Core) Discoverable and potentially Accessible .. . aggregated resources (mix of data collections, datasets and individual images) .. . Contain [source: data providers] More than 65 Million (50 Million GEOSS Data Core) Discoverable and potentially Accessible individual resources (e.g. satellite scenes, rain gauge records) nativi@iia.cnr.it
DAB Cloud-based Capabilities Load Balancing ◦ Each DAB component is replicated on multiple machines Elastic Load ◦ Amazon Load Balancers take care of routing requests to machines with lighter loads Balancing ◦ New machine can be added on-the-fly as needed Tiles and Data Caches ◦ DAB makes use of Hadoop-based solutions for storing and retrieving maps and data. Monitoring system usage and resource consuming (number of queries, use of CPU, memory, etc.) Instance with CloudWatch Store user’s queries and selections to improve ranking of results (under development) nativi@iia.cnr.it nativi@iia.cnr.it
GEO DAB typical Configuration nativi@iia.cnr.it
Recommend
More recommend
