1. Universal Dynamic Activity Package - Concepts
A. Anjomshoaa, H. Mersch, A. Memon, M. Memon, Ph. Wieder
JSDL Session #3
October 17, 2007
Seattle, WA, USA
(C) The NextGRID Consortium

2. (C) 2007 The NextGRID Consortium
Outline
Status Quo
Problem Domain
Universal Dynamic Activity Package
Concept
Model
Use cases
Lessons Learned
(C) The NextGRID Consortium

3. Activity - Status Quo Focus is on “Compute Activities”
Client defines Activity using JSDL
Activity is executed on a compute resource
Related OGF specifications
OGSA-BES
JSDL
(GLUE)

4. Problem Domain - the Activity view
Activity concept is broader than just compute
Think about business scenarios using SLAs
Modelling SLA lifecycle
Creation and Monitoring of SLAs
Evaluation
SLA = “Business Activity”
Comprises compute, but also ...
... data, accounting info, provenance, lifecycle, etc.
This information has to be captured and related to an activity
(C) The NextGRID Consortium

5. Problem Domain - the JSDL view
JSDL comprises a core Resource Request Language and
exists within an environment of other languages like
Scheduling Description Language, Job Policy Language, etc.
--> more requirements, dependencies, etc. wrt to an Activity
(C) The NextGRID Consortium

6. UDAP - Activity Definition
A unit of work
A job
A task
A data processing operation
A data access operation
An application execution
A Web Service invocation
A “thing” you need to do/take care of/execute!
…etc.
From the OGSA-BES specification:
“…computational entities such as UNIX or Windows processes, Web Services, or parallel programs—what we call activities…”
(C) The NextGRID Consortium

7. UDAP - Activity Definition
We take a holistic view of an activity
We, therefore, consider ALL that there is to know about an activity:
ALL of its requirements
ALL of its dependencies (on data and other activities)
ALL of its contextual information
Topical domain (financial markets, weather forecasting, etc.)
Security (who owns the activity, who is allowed to run it, etc.)
SLAs, QoS and other related policies
ALL of its monitoring information
Status, history, resource information, accounting, policy conformation etc.
(C) The NextGRID Consortium

8. UDAP - Activity Definition
An activity is a resource!
It MUST be managed as a resource
It MAY be depended on and used by other activities and resources
Since an activity is a resource, all the knowledge (information) about the activity can be captured and presented as a set of resource properties
(C) The NextGRID Consortium

9. (C) 2007 The NextGRID Consortium
UDAP Concept
The UDAP package can contain any information about an activity, regardless of the schema used to present that information
The values of the activity information can be updated or appended to reflect the past, present, and future state of the activity
All of the information associated with each activity is contained in a single package
The information in a UDAP package is kept up-to-date for its activity, once it is submitted to and managed within a Grid
(C) The NextGRID Consortium

10. (C) 2007 The NextGRID Consortium
UDAP Model - Overview
ID and Description
The Record is the core of an Activity
Result is xsd:any
(C) The NextGRID Consortium

11. (C) 2007 The NextGRID Consortium
UDAP Model - Record
(C) The NextGRID Consortium

12. (C) 2007 The NextGRID Consortium
UDAP Model & JSDL
<UDAP ...>
<ActivityID>ID1</ActivityID>
<ActivityDescription Dialect=”JSDL">Example using JSDL</ActivityDescription>
<Record>
<Entry Category="original">
<TimeStamp> T18:13:51.0Z</TimeStamp>
<State>pending</State>
<Resource>
<jsdl:jobDocument> ... </jsdl:jobDocument>
</Resource>
<Context>
<sdl:schedulingPolicy> ... </jsdl:schedulingPolicy>
<jpl:somePolicy> ... </jpl:somePolicy>
</Context>
<Dependency>
<wf:someWorkflowDependencies> ... </wf:someWorkflowDependencies>
</Dependency>
</Entry>
</Record>
<Result> </Result>
</UDAP>
(C) The NextGRID Consortium

13. (C) 2007 The NextGRID Consortium
UDAP Use Cases
Potentially unlimited number
Job submission (BES!)
Monitor and control state
Accounting
....
Current NextGRID usage covers
Service/resource discovery
SLA agreement creation (results in Activity instance)
SLA ranking
Uses JSDL, CIM, WS-Resource, ...
Execution not yet integrated (BES?)
(C) The NextGRID Consortium

14. (C) 2007 The NextGRID Consortium
Lessons Learned
Different definitions of the term “Activity” (co-)exist
JSDL/BES --> compute activity
UDAP --> potentially every activity
Lifecycle of an Activity pretty much determines components needed
Is service discovery part of an Activity?
SLA lifecycle = Activity lifecycle?
“Activity is a WS-Resource” seems to work pretty well
(C) The NextGRID Consortium

15. (C) 2007 The NextGRID Consortium
Proposal
Follow JSDL approach: clear scope, focus on the schema
Identify components used during activity lifecycle
Make the Activity work a separate group (or design team within JSDL)
(C) The NextGRID Consortium