1. Introduction to OGF Standards
Use-Case: Job Submission and Management Using Meta-Schedulers

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.
IPR Notices Note Well for OGF meetings 2

3. Use-Case Overview
Client submits a job to a grid-aware scheduling system
Scheduling-system is responsible for detecting and selecting suitable resources, forwarding job to a Grid site
SLA/QoS constraints are supported for job allocation
Local resource management systems include local scheduling entites
Available standards:
OGSA-BES, GLUE, JSDL, WS-Agreement, UR 3

4. Use case overview Information System Grid-level Scheduler Accounting
Jobs (with QoS requirem.) described with JSDL
Service Consumer
Job submission
XQuery/ XPath/
proprietary
Resource information stored according to GLUE model
Information
System
Grid-level
Scheduler
Accounting
Resource Info
WS-Agreement
SLA format.
SLA includes JSDL job description
WS-Agreement
protocol
SLA
Usage
Records
Resource
Usage
Resource
Info
Usage & accounting info is stored as Usage Records (UR)
SLA
Management
BES
Factory
Job
execution
BES Factory takes JSDL description as input and executes the job on the resource
Service Provider 4

5. Communication Stages
1. Information gathering
2. Non-binding negotiation/ request for offers
3. Reservation/commitment
4. Job control/job monitoring
Information gathering about available remote Grid schedulers
Non-binding negotiation may end up with several possible agreement alternatives (possibly in parallel)
Agreement creation and commitment; may fail and require return to previous stages
Handing over job control to remote Grid scheduler (responsibility remains at initiator) 5

6. Example Process including Scheduling and Execution
EPS/CSG(?): OGSA-RSS
Client
Scheduler/Broker
Job/Activity/Workflow
JSDL ?
SDL
WS-A
Step 1: activity/job/workflow needs to be submitted 6

7. Example Process including Scheduling and Execution
Client
Scheduler/Broker
OGSA-BES
Adapter
Adapter
3a) Direct access to resources through BES or some other protocol 7

8. Job Submission
Job format: Job Submission Description Language (V 1.0; GFD.56; P.-Rec.)
No standard JSDL submission interface to be implemented by the Grid-level scheduler exists
Scheduler could provide a BES interface
Grid-level
Scheduler
Job (JSDL) 8

9. Example Process including Scheduling and Execution
In future: OGSA-EPS/ OGSA-CSG
Resource Discovery
Client
Scheduler/Broker
Discovery/registry
Need for Resource Model: GLUE ?
UDDI?
Static?
LDAP?
3b) Access resources through another broker/scheduler; 3b.1) identify available other scheduler/brokers through registry, statically, somehow… 9

10. Information System
Information model: GLUE (V 2.0; public comment for P-REC ended Aug. 13)
Rendering: most likely XML Schema
Information query: XQuery, XPath, proprietary
Grid-level
Scheduler
Information
System (GLUE)
Provider Info 10

11. Example Process including Scheduling and Execution
Resource Discovery
Client
Scheduler/Broker
WS-Agreement/ (in future plus Negotiation)
Scheduler/Broker
Job/Activity/Workflow
Use “job” description
or subset thereof
JSDL ?
SDL
WS-A
3b) Access resources through another broker/scheduler;
3b.2) communicate with remote scheduler about potential agreement 11

12. Service Level Agreements
Grid-level scheduler & Service Provider agree upon the service to be provided
SLA is negotiated (contains JSDL)
SLA format & protocol: WS-Agreement (V1.0; GFD.107; P-REC)
Current negotiation is “take-it-or-leave-it”, GRAAP working on enhancements
Grid-level
Scheduler
SLA (WS-Agr.)
SLA
Management 12

13. Example Process including Scheduling and Execution
Resource Discovery
Client
Scheduler/Broker
Scheduler/Broker
Use case depended who finally commits:
Client or Scheduler
responsibility of execution management:
Client or scheduler
4) Transition to execution management: OGSA-BES 13

14. Job execution Via Basic Execution Service (V1.0; GFD.108; P-REC)
BES-Factory receives JSDL job description
BES defines all interfaces to create & manage “activities” (i.e. jobs)
BES Factory
Job Execution
JSDL 14

15. Accounting
Service provider stores accounting and usage data using Usage Records (V1.0; GFD.98; P-REC)
Interface on how to retrieve URs is not defined
Accounting
Resource
Usage
Records (UR) 15

16. Full Copyright Notice
Copyright (C) Open Grid Forum (applicable years). 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.
OGF Full Copyright Notice if necessary 16