1. © 2006 Open Grid Forum Joint Session on Information Modeling for Computing Resources OGF 21, Seattle, Tuesday 16 October 2007

2. © 2006 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.

3. © 2006 Open Grid Forum 3 Outline Introduction and scope of the session (10 min) Summary on OGF Information Modeling activities (OGSA Res.Mgt Design Team - 10 min) - Ellen Stokes GLUE-WG summary status on computing resource modeling (GLUE WG - 10 min) Integration with other OGF specifications: Status of Reference Model and GLUE Integration (RM WG – 10 min) - Paul Strong JSDL and GLUE Integration (JSDL WG - 10 min) Status of JSDL extension to support XQuery How it is possible to express requirements in JSDL doc about GLUE representation of resources Proposal for GLUE 2 and BES integration (GLUE WG - 30 min) Open discussion

4. © 2006 Open Grid Forum OGF Information Modeling Activities E. Stokes

5. © 2006 Open Grid Forum GLUE WG - Status S. Andreozzi

6. © 2006 Open Grid Forum 6 Problem Statement How do we describe resources shared in Grid systems in order to enable: Resource awareness Resource discoverability Resource requirements expression Resource basic monitoring

7. © 2006 Open Grid Forum 7 GLUE 2: A Super GLUE GLUE 1.X is an important experience in the context of information modeling of Grid resources De-facto standard Other approaches exist e.g.: NorduGrid Schema, NAREGI Schema Can we create a Super GLUE that unifies all the modeling efforts? that is accepted as an open standard?

8. © 2006 Open Grid Forum 8 OGF GLUE WG New OGF Working Group approved at OGF 19 (Jan 2007) http://forge.ogf.org/sf/projects/glue-wg Focus: facilitate interoperability between Grid infrastructures via common information models and reference implementation for describing Grid resources in response to use cases Goal: define a use case document collecting use cases from different Grid projects/infrastructures define a conceptual model defining the abstract schema GLUE 2.0 satisfying the collected use cases. develop reference implementations

9. © 2006 Open Grid Forum 9 Relationship to other OGF WGs JSDL GLUE Reference Model SAGA GSM OGSA Res.Mgt. Used to express requirements in Common service descripton for discovery API Used to describe exposed resources Should fit into the picture BES Used to describe exposed resources SAGA:Simple Access Grid API GSM:Grid Storage ManagementBES: Basic Execution Service JSDL: Job Submission Description Language

10. © 2006 Open Grid Forum 10 Tentative Timeline for the GLUE WG http://forge.ogf.org/sf/docman/do/listDocuments/projects.glue-wg/docman.root.drafts Latest Draft Versions available:

11. © 2006 Open Grid Forum 11 Main Entities

12. © 2006 Open Grid Forum 12 Computing Entities

13. © 2006 Open Grid Forum 13 OGF GLUE WG sessions GLUE 2 Specification - part 1 (90 mins) Wed 17 Oct 2007 11-12.30 AM http://www.ogf.org/gf/event_schedule/index.php?id=901 GLUE 2 Specification – part 2 (90 mins) Wed 17 Oct 2007 1.30-3.00 PM http://www.ogf.org/gf/event_schedule/index.php?id=902

14. © 2006 Open Grid Forum GLUE and Reference Model Paul Strong

15. © 2006 Open Grid Forum GLUE and JSDL

16. © 2006 Open Grid Forum GLUE and BES S. Andreozzi

17. © 2006 Open Grid Forum 17 BES Operations Where GLUE Can Be Used BES-Factory Port-type GetActivityStatuses GetActivityDocuments GetFactoryAttributesDocument BES-Management Port-type No hooks BES-Activity Port-type Undefined

18. © 2006 Open Grid Forum 18 BES-Factory::GetActivityStatuses Hook to add fragment of GLUE about job

19. © 2006 Open Grid Forum 19 GLUE Integration in GetActivityStatuses

20. © 2006 Open Grid Forum 20 BES-Factory::GetActivityDocuments “The ActivityDocument element is used to describe either the desired or the actual representation of a single activity and has the following structure” ? At the moment, we don’t add any GLUE info in this message; when we will define how JSDL can contain requirements on GLUE attributes, then we can discuss it again

21. © 2006 Open Grid Forum 21 BES-Factory::GetFactoryAttributesDocument GetFactoryAttributesDocument no input parameter, while the output is an XML document compliant to the XSD complex type: bes-factory:BESResourceAttributeDocumentType Hook to add fragments of XML documents under different namespace

22. © 2006 Open Grid Forum 22 GLUE Integration in GetFactoryAttributesDocument

23. © 2006 Open Grid Forum 23 BES-Factory::GetFactoryAttributesDocument Mandatory attributes

24. © 2006 Open Grid Forum 24 How to Query Information Exposed by BES? At the moment, you can ask for Activity status by job ID (EPR) Complete resouce description There is no way to specify query to be executed on the BES side How can we extend BES in order to provide query capabilities on the server side? There is a way to extend BES in a compatible way? It seems no; e.g. no input parameter for GetFactoryAttributesDocument If not, should we add a new operation? e.g.: GetDocument (Namespace,QueryLanguage,QueryExpression,DataFormat) rely on WSRF/WSRT?

25. © 2006 Open Grid Forum 25 How to Select a Certain Share from BES? GLUE defines the concept of share In a cluster, many shares where Grid users can be mapped can be configured A single BES instance can place jobs on any of the available shares How does the BES client specify to which it wants to place the job? Should this be specified it in the JSDL? What does happen if the JSDL does not specify any share? What does happen if the JSDL cannot be satisfied in terms of requirements?

26. © 2006 Open Grid Forum 26 References OGF GLUE WG Website http://forge.ogf.org/sf/projects/glue-wg Documents GLUE 2 - Specification (draft) GLUE 2 - Use Cases (draft) http://forge.ogf.org/sf/docman/do/listDocuments/projects.glue-wg/docman.root.drafts

27. © 2006 Open Grid Forum 27 Full Copyright Notice Copyright (C) Open Grid Forum (2007). 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.