© 2008 Open Grid Forum Grid Standards Realizing Basic Grid Use Cases Using Existing Standards and Profiles

© 2008 Open Grid Forum 2 OGF IPR Policies Apply “ I acknowledge that participation in this meeting is subject to the OGF Intellectual Property Policy. ” Intellectual Property Notices Note Well: All statements related to the activities of the OGF and addressed to the OGF are subject to all provisions of Appendix B of GFD-C.1, which grants to the OGF and its participants certain licenses and rights in such statements. Such statements include verbal statements in OGF meetings, as well as written and electronic communications made at any time or place, which are addressed to: the OGF plenary session, any OGF working group or portion thereof, the OGF Board of Directors, the GFSG, or any member thereof on behalf of the OGF, the ADCOM, or any member thereof on behalf of the ADCOM, any OGF mailing list, including any group list, or any other list functioning under OGF auspices, the OGF Editor or the document authoring and review process Statements made outside of a OGF meeting, mailing list or other function, that are clearly not intended to be input to an OGF activity, group or function, are not subject to these provisions. Excerpt from Appendix B of GFD-C.1: ” Where the OGF knows of rights, or claimed rights, the OGF secretariat shall attempt to obtain from the claimant of such rights, a written assurance that upon approval by the GFSG of the relevant OGF document(s), any party will be able to obtain the right to implement, use and distribute the technology or works when implementing, using or distributing technology based upon the specific specification(s) under openly specified, reasonable, non- discriminatory terms. The working group or research group proposing the use of the technology with respect to which the proprietary rights are claimed may assist the OGF secretariat in this effort. The results of this procedure shall not affect advancement of document, except that the GFSG may defer approval where a delay may facilitate the obtaining of such assurances. The results will, however, be recorded by the OGF Secretariat, and made available. The GFSG may also direct that a summary of the results be included in any GFD published containing the specification. ” OGF Intellectual Property Policies are adapted from the IETF Intellectual Property Policies that support the Internet Standards Process.

© 2008 Open Grid Forum 3 Agenda Why Standardize? Where are we now? Base use-cases Standards Realizing the use cases

© 2008 Open Grid Forum 4 Why Standardize? What is the value of implementing standards? For vendors meet customer demand for interoperability For developers leverage the expertise of other developers offer a choice of tools and platforms in order to speed implementations only need to support one integration interface For end-users reduce the costs and risks of adopting grid technology get insight into the best practices of the industry at large

© 2008 Open Grid Forum 5 Why Not Standardize? Standards are not always appropriate A technology might be “too new” you stifle innovation with standardization, which focuses on commonality A technology might be very niched defacto standards will emerge in this case

© 2008 Open Grid Forum 6 Where are we now? We have a sufficient corpus of specifications and profiles to realize (implement) identified use cases in computing and data. Customer (user) value of standards is increased when they permit interoperability between packages/systems/vendors and when concepts can be transferred from one system to another.

© 2008 Open Grid Forum 7 Use case driven High-throughput computing Within an organization with shared file system – HPC-BP Multi-site/organization Data federation/data grids Flat file data Structured (relational)

© 2008 Open Grid Forum 8 Classic three layer view API’s & interfaces, e.g. NFS, CIFS Standard portypes Resources Layer Grid Services Layer Access Layer

© 2008 Open Grid Forum 9 Standard APIs vs Protocols Workload Manager Client Workload Manager Native API Native Protocol Engine proprietary API proprietary protocol Native Protocol Engine DRMAA/SAGA Native API proprietary protocol standard API OGSA-BES WS-I compliant SOAP toolkit standard protocol OGSA-BES WS-I compliant SOAP toolkit DRMAA/SAGA standard protocol standard API OGSA-BES WS-I compliant SOAP toolkit standard protocol proprietary API Native API

© 2008 Open Grid Forum 10 Standards Security WSI-BSP, WS-Security, WS-Trust, WS-Federation, WS- SecurityPolicy, WS-SecureNaming, WS-Secure Communication, others Infrastructure WS-Addressing, Resource Namespace Services (RNS), WS-Naming Compute JSDL, OGSA-BES, HPC-BP Data RNS, OGSA-Byte-IO, gridFTP, WS-DAI APIs SAGA, DRMAA, GridRPC

© 2008 Open Grid Forum 11 Simple HPC use case run myjob BES resource 0 BES resource 1 BES resource 2 A simple “run” command (not defined by OGSA) generates a JSDL document describing the application to be run, its resource requirements, file inputs and outputs, etc. It interacts securely with a set of predefined BES resources using the OGSA Basic Security Profile 2.0, authenticating the client to the BES resources and the BES resources to the client. Data publisher Windows JSDL can specify data staging Or use RNS/GFS file system WSI-BSP, X.509, etc BES/ Queue

© 2008 Open Grid Forum 12 Data publisher Mapping data into the Grid Data clients Linux Windows Links directories and files from source location to data grid directory and user-specified name Presents unified view of the data across platforms, locations, domains, etc. Data publisher controls authorization policy. Data publisher

© 2008 Open Grid Forum 13 Relational data Can be proxied and accessed using WS-DAI with EPRs and RNS paths Results of queries also have EPR’s

© 2008 Open Grid Forum 14 Data federation use-case User certificate Grid-proxy RNS name space with references to OGSA- ByteIO and WS-DAI resources Legacy application Grid aware shim Grid name space can be mapped into local file system, e.g., /uva-genii

© 2008 Open Grid Forum 15 Data federation use-case - Windows User certificate Grid-FS proxy RNS name space with references to OGSA- ByteIO and WS-DAI resources Windows FS Windows IFS Grid name space can be mapped into local file system, e.g., /uva-genii

© 2008 Open Grid Forum 16 Interop – it takes two Not only must the service present the right porttype – e.g., BES It must also understand and use the same security infrastructure – and not choke on the XML

© 2008 Open Grid Forum 17 Interop – it takes two One group or implementation inter-operating with itself is not interesting Why should two different infrastructures interoperate? maybe there is a need for interoperability within the infrastructure if multiple vendors solutions are deployed Why should grid middleware vendors bother to interoperate?

© 2008 Open Grid Forum 18 Spec Adoption

© 2008 Open Grid Forum 19 Full Copyright Notice Copyright (C) Open Grid Forum (2008). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors or assignees.