1 / 48

OGSA and CrossGrid

OGSA and CrossGrid. Maciej Malawski Institute of Computer Science & ACC CYFRONET AGH, Kraków, Poland www.eu-crossgrid.org. Overview. OGSA and OGSI Grid Service Hosting Environments and Implementations What will be in GT3 Collaboration with Globus Team CrossGrid Services.

pereznancy
Download Presentation

OGSA and CrossGrid

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. OGSA and CrossGrid Maciej Malawski Institute of Computer Science & ACC CYFRONET AGH, Kraków, Poland www.eu-crossgrid.org

  2. Overview • OGSA and OGSI • Grid Service • Hosting Environments and Implementations • What will be in GT3 • Collaboration with Globus Team • CrossGrid Services

  3. Globus, Web Services and OGSA • Globus Tolkit • Protocols and services: GRAM, GridFTP, MDS • Grid Security Infrastructure (GSI) • Web Services • System integration • Service orientation • XML based – SOAP, WSDL

  4. OGSA - Motivation • Need for basic infrastructure for distributed state management • Interoperability in heterogeneous environment • Can be used as a basis for building Globus Services

  5. Grid Service • Transient, stateful WebService (created dynamically) • Described by WSDL • Located by Grid Service Handle (GSH) in a form of URI • Can be queried for configuration and state in standard way

  6. Grid Service Examples • Job Manager Service • Data Transfer Service • Database Query Service • Monitoring Data Producer • Everything...?

  7. Grid Service PortType • RequestTerminationAfter • RequestTerminationBefore • Destroy • FindServiceData • queryByServiceDataName • queryByXPath • queryByXQuery

  8. Service Data • XML element containing information about service • Identified by Name and Type • May contain any XML information • May be queried or subscribed

  9. Non Mandatory Port Types • HandleResolver • NotificationSource • NotificationSubscription • NotificationSink • Factory • Registration

  10. BioDB 1 BioDB n Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service Compute Service Provider User Application . . . . . . “I want to create a personal database containing data on e.coli metabolism” Database Service Database Factory Storage Service Provider

  11. BioDB 1 BioDB n Example:Data Mining for Bioinformatics “Find me a data mining service, and somewhere to store data” Community Registry Mining Factory Database Service Compute Service Provider User Application . . . . . . Database Service Database Factory Storage Service Provider

  12. BioDB 1 BioDB n Example:Data Mining for Bioinformatics Community Registry Mining Factory GSHs for Mining and Database factories Database Service Compute Service Provider User Application . . . . . . Database Service Database Factory Storage Service Provider

  13. BioDB 1 BioDB n Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service “Create a data mining service with initial lifetime 10” Compute Service Provider User Application . . . . . . “Create a database with initial lifetime 1000” Database Service Database Factory Storage Service Provider

  14. BioDB 1 BioDB n Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service “Create a data mining service with initial lifetime 10” Miner Compute Service Provider User Application . . . . . . “Create a database with initial lifetime 1000” Database Service Database Factory Database Storage Service Provider

  15. BioDB 1 BioDB n Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service Query Miner Compute Service Provider User Application . . . . . . Query Database Service Database Factory Database Storage Service Provider

  16. BioDB 1 BioDB n Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service Query Miner Keepalive Compute Service Provider User Application . . . . . . Query Database Service Database Factory Keepalive Database Storage Service Provider

  17. BioDB 1 BioDB n Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service Miner Keepalive Compute Service Provider User Application . . . . . . Results Database Service Database Factory Keepalive Results Database Storage Service Provider

  18. BioDB 1 BioDB n Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service Miner Compute Service Provider User Application . . . . . . Database Service Database Factory Keepalive Database Storage Service Provider

  19. BioDB 1 BioDB n Example:Data Mining for Bioinformatics Community Registry Mining Factory Database Service Compute Service Provider User Application . . . . . . Database Service Database Factory Keepalive Database Storage Service Provider

  20. Terminology • OGSI – Open Grid Services Infrastructure • OGSA – Open Grid Services Architecture • OGSI-compliant – service conformant to Grid Service Specification, with WSDL interface

  21. OGSI GGF-WG • Review and refine the Grid Service Specification • GGF7 (March 3-7, 2003) • Review: Grid Service Specification v1.0 • Planning for: Grid Service Specification v1.1

  22. OGSA WG • Integrated approach to future OGSA service development • Documentation of requirements, functionalities, priorities, and interrelationships for OGSA services • Common Resource Model

  23. Hosting Environments • Embedded (Java Application) • Standalone J2SE Container • J2EE Web Container (Tomcat) • J2EE EJB Container • C/C++ - plans for 2003 • Python • Other

  24. Java Container • Java object  Grid Service • SOAP engine – based on Apache Axis • Tools to generate code • APIs for service management

  25. Enterprise Java Beans (EJB) • Entity Beans, Session Beans  Grid Services • J2EE Application Server  delegation from OGSA Hosting Environment • Home Interface  OGSA Factory • Remote Interface  Web Service Interface • EJB Environment Entries  Service Data • JMS interface to OGSA Notification • Automatic Code Generation • Support for IBM WebSphere and JBoss

  26. JINI • http://www.sc2002.org/paperpdfs/pap.pap253.pdf • ICENI: An Open Grid Service Architecture Implemented with Jini

  27. Unicore • Unicore OGSA Demonstrator • http://www.fz-juelich.de//unicore-dist/data/packages/server/ogsa_readme.pdf/returnDoc

  28. Common Component Architecture • Components  Grid Services • Ports  WebService PortTypes • Application Factory, Events, Service Data • http://www.extreme.indiana.edu/xgws/

  29. Globus Toolkit 2.x schedule • Globus Toolkit 2.x • GT 2.2 released • Bug fixes, some performance improvements • GT 2.4 • not confirmed yet • GT3 security supported • GT 2.x supported during 2003

  30. What is GT3? • GT3 = GT2 + OGSA • Implementation of GT services so that they are OGSI-compliant • Some extended functionality • Much of GT2 code will remain

  31. Globus Toolkit 3.0 Schedule • OGSA Technology Previews • TechPrev.5 in 2 weeks • GT 3.0 Alpha release – January 2003 at GlobusWorld conference • GT3 Beta release – April 2003 • GT 3.0 – June 2003

  32. GT3 Core • GT3 security • Change in proxy certificate format • http://www.gridforum.org/2_SEC/GSI.htm • Java – implementation of OGSI specification • Client and server infrastructure • SDK, hosting environment • C/C++ • Only client-side • Next year server-side support based most probably on gSOAP

  33. GT3 Base – GRAM • Java wrapper over existing code • RSL  XML • Future: • Redesigning of RSL • Moving to Web Services model

  34. GT3 Base - GridFTP • No changes to protocol • Server from GT2 with GT3 security • GT3 security compatible client tools • Future: • Control channel available as OGSI-compliant interface

  35. GT3 Base - MDS • Major changes: LDAP (LDIF)  XML • Information providers  OGSA Service Data mechanisms • Using Netscape LDAP JDK and DSMLTools ( http://www.dsmltools.org/ ) • GIIS – higher level service with OGSI-compliant interface • Adaptation of Common Information Model (CIM) http://www.dmtf.org/standards/standard_cim.php standards and GLUE project agreements

  36. GT3 Base – Database Services • OGSI-compliant interfaces to XML databases • Developed by UK eScience program • http://umbriel.dcs.gla.ac.uk/nesc/general/projects/OGSA_DAI/

  37. GT3 Collective Layer Services • Reliable File Transfer • Tolerant to network, source and destination faults • Uses database for persistent state management • Replica Location Service • Done in collaboration with EU DataGrid • Community Authorization Service • Authorization to groups of users • Available for GridFTP

  38. Benefits of using OGSA • Standards conformance • Interoperability • Infrastructure for information management (Service Data, Notification) • Software quality of OGSA implementation • http://www.globus.org/toolkit/gt3-faq.html

  39. Problems • Performance • Development process – easy? • Stability of specifications • Interoperability of Web Services

  40. Collaboration Areas between X# and Globus • Requirements for Globus Toolkit software • We are the „customers” and „users” • Our feedback is welcome • E.g. Do we need C/C++ based framework? • What performance is required? • Globus „contrib” directory • External reviews

  41. Roaming Access - design

  42. Roaming Access – OGSA possibilities • Components in Roaming Access Server can have OGSA interfaces • Where applicable OGSA services can act as gateways to external components • User session managers • Other...?

  43. Scheduling Agents

  44. Scheduling Agents – OGSA possibilities • OGSI-compliant interface • XML-based protocol • Usage of OGSA mechanisms to exchange information with external components (monitoring, etc.) • Problems to solve: • Dependency on DataGrid and Condor

  45. Grid Monitoring – OGSA possibilities • Monitoring systems = Information providers • Should use OGSA Service Data model • LDAP  XML • Two applications • Use OGSA/XML for internal purposes • Use OGSA/XML to publish data to external consumers

  46. Data Access

  47. Data Access - OGSA • External components  OGSA services • Coordination with Globus GridFTP server development • More service-oriented approach: • Transfer session as a service • File as a service

  48. Summary • OGSA as a standard • OGSA can be useful and usable • OGSA developers need our feedback • Discussion is welcome

More Related