Embed Size (px)
Citation preview
®
Copyright © 2009, Open Geospatial Consortium, Inc., All Copyright © 2009, Open Geospatial Consortium, Inc., All Rights Reserved.Rights Reserved.
OWS-6 Grid Computing OWS-6 Grid Computing ActivitiesActivities
Bastian BaranskiInstitute for Geoinformatics (IfGI)
University of Münster
OGC®
Agenda
• Introduction– Open Geospatial Consortium (OGC)– OGC Web Processing Service (WPS)– Memorandum of Understanding (MoU)
• OWS-6 Grid Computing Activities– OGC Web Services, Phase 6 (OWS-6)– Geo Processing Workflow (GPW)– Airport Scenario– Debris Flow Scenario
• Outlook
OGC®
Introduction
OGC®
Open Geospatial Consortium (OGC)
• Open Geospatial Consortium (OGC)– Founded in 1994, OGC is a non-profit, international, voluntary consensus
standards organization that is leading the development of standards for geospatial and location based services
– “Helping the World to Communicate Geographically”• ~80% of all data collected or produced by humans is geospatially referenced
– Consortium of 376 companies, government agencies and universitiesAfrica (1) Asia Pacific (43) Europe (168)
Middle East (4) North America (159)South America (1)
– Works with other standards bodies including ISO, W3C, OASIS, IETF, etc.
• A few current OGC standards– Web Map Server (WMS)
– Web Feature Server (WFS)
– Catalog Service for Web (CSW)
– Web Processing Service (WPS)
OGC®
OGC Web Processing Service (WPS)
Data WPS Information
OGC®
OGC Web Processing Service (WPS)
• OGC Web Processing Service (WPS) Version 1.0.0 (2007)• interface to publish and perform processes over the web• synchronous and asynchronous execution• wrapped XML payload and raw data payload• referencing data (HTTP-GET & HTTP-POST)
OGC®
OGC Web Processing Service (WPS)
OGC®
OGC Web Processing Service (WPS)
WPS
Buffer
Process
Process
Process
20
OGC®
Memorandum of Understanding (MoU)
OGC and OGF signed a formal Memorandum of Understanding that defines particular areas for collaboration (2007).
• Potential joint projects– Integrate OGC WPS with a range of "back-end" processing environments to
enable large-scale processing– Integration of WPS with workflow management tools– Integration of OGC Federated Catalogues with grid data movement tools– WPS is just a starting point for the collaboration
• A few collaboration activities– The OGC-OGF Collaboration Workshop, OGF-22 (02-2008)– OGC-OGF Grid Ad Hoc, OGC Meeting (06-2008)– The OGC-OGF Collaboration Workshop, OGF-23 (06-2008)– OGC Web Services, Phase 6 (OWS-6) Interoperability Initiative– OGC-OGF Collaboration Workshop Ad-hoc, OGC Meeting (12-2008)– Grid Computing & Geospatial Technologies, OGF-25 (03-2009)
OGC®
OGC Web Services, Phase 6 (OWS-6)
OGC®
OGC Web Services, Phase 6 (OWS-6)
• OGC Web Services, Phase 6 (OWS-6)– A global, hands-on and collaborative prototyping program designed to
rapidly develop, test and deliver proven candidate specifications– Overall schedule of events and milestones
• 07-21-2008, The Request for Quotation / Call for Participation was released• 10-14-2008, OWS-6 Kickoff at George Mason University, Fairfax • 12-12-2008, Interim Milestone: Draft Engineering Reports • 01-16-2009, Draft component implementations• 03-13-2009, Final component implementations• 04-17-2009, Final drafts of all Engineering Reports and Change Requests
– Organized around the following threads• Sensor Web Enablement (SWE)• Geo Processing Workflow (GPW)• Aeronautical Information Management (AIM)• Decision Support Services (DSS)• Compliance Testing (CITE)
OGC®
OWS-6, Geo Processing Workflow (GPW)
• Main topics in the OWS-6 GPW thread– Web Services Security and Asynchronous Workflow– Operational Security Environments– Web Services Security Environments and Solutions– Asynchronous Workflows Within and Across Security Domains– Open Grid Forum (OGF) Enabled Web Processing Services (WPS)– Web Processing Service (WPS) Grid Processing Profiles– GML Application Schema Development– GML ShapeChange Enhancements– Data Accessibility for DCS-enabled WFS
OGC®
OWS-6, Geo Processing Workflow (GPW)
• OGF Enabled WPS (Implementation)– WPS should be able to benefit from and integrate with distributed
computing resources and technologies– Two potential ways to make use of OGF specifications, concepts
and their implementations where identified• encapsulating other resources
• integration alongside other services
OGC®
OWS-6, Geo Processing Workflow (GPW)
OGC®
OWS-6, Geo Processing Workflow (GPW)
OGC®
OWS-6, Geo Processing Workflow (GPW)
• WPS Grid Processing Profile(s) (Specification)– Investigate, define and implement a WPS Grid Processing Profile
which is integrated with a grid computing infrastructure using• High Performance Computing (HPC) Basic Profile (HPC-BP)
• Simple API for Grid Applications (SAGA)
• Data Access and Integration set of specifications (WS-DAI-*)
• Web Services Resource Framework (WSRF)
• (…)
OGC®
OWS-6 GPW, Deliverables
• Implementations– Airport Scenario
• Trajectory Service (WPS JSDL Profile)– Science and Technology Facilities Council (STFC), UK
• Plume Rendering Service (WPS JSDL Profile)– Institute for Geoinformatics (IfGI), University of Münster, Germany
– Debris Flow Scenario• Rainfall Data Interpolation (WPS HPC Basic Profile)
– Institute for Geoinformatics (IfGI), University of Münster, Germany
– Geographic Information Systems (GIS) Research Center, Feng Chia University (FCU), Taiwan
• Geophone Data Analysis (WPS HPC Basic Profile)– Institute for Geoinformatics (IfGI), University of Münster, Germany
– Geographic Information Systems (GIS) Research Center, Feng Chia University (FCU), Taiwan
• Engineering Report– Institute for Geoinformatics (IfGI), University of Münster, Germany
OGC®
OWS-6 GPW, Airport Scenario
• WPS JSDL Profile– Science and Technology Facilities Council (STFC), UK– WPS as interface to Grid Computing resources– passed-through’ by WPS from user to Grid environment (“Full”)– generated by WPS on basis of resource/staging parameters (“Lite”)
http://foo.bar.1/wps?version=1.0.0&request=Execute&service=WPS&Identifier=WeatherGenerator&DataInput=JSDL=http://www.domain.com/jsdl.xml@Format=text/xml@Encoding=utf-8@Schema=http://www.domain.com/jsdl.xsd&storeExecuteResponse=true&status=true
Full
http://foo.bar.1/wps?version=1.0.0&request=Execute&service=WPS&Identifier=WeatherGenerator&DataInput=other_inputs=xxx;JSDL=[TotalDiskSpace=5@uom=GB;TotalCPUCount=1;
DataStaging=target@url=ftp://domain.com/file]&storeExecuteRepose=true&status=true
Lite
OGC®
OWS-6 GPW, Airport Scenario
• WPS JSDL Profile– Trajectory Service (WPS)
• uses atmospheric model forecast to trace particle trajectories
• provides advection of particles, but not dispersion
– Deployment on UK National Grid Service– Use GridSAM as NGS JSDL interface– MyProxy for authentication, no sophisticated authorisation
• standardised username / password parameters to WPS
– Configuration file for• mapping WPS ‘Process’ to NGS executable
• (…)
OGC®
OWS-6 GPW, Debris Flow Scenario
• Debris Flow Scenario– Participants
• Geographic Information Systems (GIS) Research Center, Feng Chia University (FCU), Taiwan
• Institute for Geoinformatics (IfGI), University of Münster, Germany
• 52° North Initiative for Geospatial Open Source Software GmbH, Münster, Germany
– Scenario• A Debris flow is a fast moving mass of unconsolidated, saturated debris
that looks like flowing concrete
• Based on existing Debris Flow monitoring system (proprietary and monolithic software infrastructure) in Taiwan (running since 2003)
• Develop and implement open standards (OGC-) based service oriented architecture (SOA) for Debris Flow monitoring
OGC®
OWS-6 GPW, Debris Flow Scenario
OGC®
OWS-6 GPW, Debris Flow Scenario
OGC®
OWS-6 GPW, Debris Flow Scenario
OGC®
OWS-6 GPW, Debris Flow Scenario
OGC®
OWS-6 GPW, Debris Flow Scenario
OGC®
OWS-6 GPW, Debris Flow Scenario
OGC®
OWS-6 GPW, Debris Flow Scenario
• Geophone Sensor (Example)– 500 Hz sampling rate = 500 records / sec / sensor– 1.2 MB / min / sensor = 1.7 GB / day / sensor– 3 sensors per station, 15 stations– 1.7 GB * 3 * 15 = 76.5 GB / day– Wavelet Transform Algorithm– ~2 hour calculation time
OGC®
OWS-6 GPW, Debris Flow Scenario
OGC®
Outlook
OGC®
Outlook
• Some areas for future work include– Web Service Resource Framework (WSRF)– Service Level Agreements (SLA)– (…)
• Any questions, suggestions or annotations?
