1 / 19

INFN Research Roadmap for

EGEE’09 Conference, Barcelona 21-25 September 2009. INFN Research Roadmap for. www.g-ows.org Eric Frizziero (INFN) Marco Verlato (INFN) Luigi Zangrando (INFN). A little of history…. INFN started to work with geospatial web services in the context of CYCLOPS project

nate
Download Presentation

INFN Research Roadmap for

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EGEE’09 Conference, Barcelona 21-25 September 2009 INFN Research Roadmap for www.g-ows.org Eric Frizziero (INFN) Marco Verlato (INFN) Luigi Zangrando (INFN)

  2. A little of history… • INFN started to work with geospatial web services in the context of CYCLOPS project • FP6 SSA of EGEE –> June 2006 - November 2008 • Consortium: • Civil Protection Agencies: ANPC (PT),DDSC (FR), DPC (IT), Pr. Chania (GR) • Scientific and Technological Centres: CNR (IT), EMA (FR), INFN (IT), TEI (GR), UMINHO (PT) • Main Outcomes: • Grid-enabled CP applications proof-of-concept • Research Strategies and Innovation Guidelines for a European CP e-Infrastructure

  3. Architectural framework

  4. G-RISICO use-case • Application built on top of grid-enabled OWS: • OpenGIS WPS (Web Processing Service): standard description of GIS calculation (the process), here the wild fire risk assessment model • OpenGIS WCS (Web Coverage Service): standard access to geospatial information data

  5. GRID WCS Grid-enabled WCS example Grid-WCS Traditional WCS

  6. CYCLOPS VO support • Continued after the end of CYCLOPS project • 14 EGEE production grid sites in total (in France, Italy, Portugal) • Potentially > 600 CPU-cores and > 10 TB of storage available • Central grid services (WMS, LB, VOMS, LFC) at INFN • G-OWS services (WCS and WPS) at INFN • >14k test & demo jobs >100 CPU.days

  7. CYCLOPS follow up • From CYCLOPS final review (Dec. 08) • Draft work plan (from G-OWS charter) • VO-OWS package • OWS implementation on WMProxy • Security aspects: basic security support • Site-OWS package • OWS implementation on CREAM • SOS implementation on Instrument Element

  8. CREAM • CREAM (Computing Resource Execution And Management) service: • general purpose framework for building grid services • functionalities/operations are pluggable • for example, the functionality for accessing a database can be easily added and plugged to CREAM • main functionalities provided: job management operations at the Computing Element (CE) level • allow the grid user to submit, cancel, monitor, … computational jobs • Computing Element: grid component acts as interface to computational resources • single pc • cluster of pc handled by a LRMS (e.g. LSF, PBS/Torque, Condor)‏ • supercomputer for High Performance Computing (HPC)‏ • CREAM describes and exposes its functionality through a Web Service interface

  9. ??? Executor High level CREAM architecture • In the current architecture, it is possible to plug different interfaces to CREAM (e.g. one for job management, one for database access, etc.). • The different commands (that is the operations defined on the WS interfaces) are then managed by different command executors (pluggable). Multiple Web service interfaces can coexist Basic Execution Service (BES) an OGF specification Web service interfaces for job management Possible extension of CREAM capabilities: OGC interfaces? CREAM job manag. OGSA-BES ??? WS CREAM core Job management functionalities Job Exec BLAH Job management functionalities implementation LRMS

  10. High level CREAM architecture • Persistency, fault tolerance • Support for both synchronous and asynchronous commands is provided • Asynchronous commands execution is implemented by a priority queue • A command can be also executed in a serial/parallel way WS interface ??? WS asynchronous commands cmd cmd priority cmd queue cmd synchronous command cmd CREAM core ??? Executor Executor implementation

  11. “Simplified” view of CREAM architecture • Web service interface‏ • WS-I compliance • WSDL 1.1 • document/literal • SOA (Service Oriented Architecture) paradigm adopted • Fully implemented in Java • developed with Apache Axis (version 1.4) framework for Java • http://ws.apache.org/axis/ • CREAM runs as Java-Axis servlet on Tomcat 5.5 application server • To get access to the CREAM it is needed to cross the AuthN and AuthZ layers; • The DN and VOMS attributes are extracted from the user's proxy certificate; • The AuthZ is based on VOMS attributes and on the gridmap file; Security layer X.509 + VOMS Web service interface • SOAP engine (servlet)‏ AXIS • servlet engine Tomcat

  12. “Generic” CREAM WS interface • CREAM provides also a “generic” WS interface for executing commands • The main operation is the execute() one which allows a client to execute synchronously/asynchronously the specified command implemented by CREAM through the associated command executor. • CommandResult execute(Command) • Within the Command argument the client provides input parameters, execution category, specific executor name, etc • the CommandResult returns the outputs produced (if executed synchronously) or the commandId (if executed asynchronously)

  13. CREAM usage scenarios • CREAM can be used: • through the gLite components (Web Services) • directly by the users • they can build their own clients using a Web Service framework Submission through gLite WMS Direct Job Submission gLite WMS CREAM CREAM CREAM

  14. G-RISICO and gLite GUI WCS WCS WCS WPS RISICO Business Logic RISICO WCS gLite WMS CE CE CE

  15. CREAM as coverage provider CREAM could become a coverage provider by adding the WCS interface GUI WCS WCS RISICO Business Logic WCS WPS RISICO WCS WMS gLite JM WCS WCS JM WCS JM CREAM CREAM CREAM

  16. OGC-WPS vs CREAM interface • The WPS interface presents strong analogies with respect to the CREAM “generic” one. • execute() operation • This encourages a possible integration of WPS in CREAM • advantages: • If (almost) all resources (e.g. geospatial data) are locally distributed and provided by a single site which must provided an adequate local cluster of pc handled by a LRMS • this avoid the intrinsic grid overhead • Inheritance of the CREAM security level (X509, VOMS) which is gLite compliant • Sophisticate asynchronous execution of commands • priority command queue • serial/parallel command execution • Disadvantage: N/A

  17. G-RISICO and CREAM Remote WCS GUI WCS WCS WCS Security layer X.509 + VOMS OGC-WPS OGC WS interface CREAM RISICO exec RISICO Business Logic Local WCS WCS WN WN WN WN Local cluster

  18. WCS Exec BLAH WPS and WCS integration WPS WCS asynchronous commands cmd cmd cmd cmd Priority cmd queue cmd cmd synchronous command cmd cmd WCS WCS WPS Exec (RISICO WF) BLAH Direct access to the local WCS Remote WCS LRMS Geospatial data

  19. Conclusions • A first preliminary analysis has shown that the CREAM framework could provide OWS services at site level • A prototype could be developed in the context of future FP7 projects: • CYCLOPS-2 ? • Lifewatch related project? • …

More Related