Sharing Workflows - PowerPoint PPT Presentation

1 / 19
About This Presentation
Title:

Sharing Workflows

Description:

User Portals/ Science Portals. Launch, configure. And control. Orchestration Service ... Portal DLR Application. Portal Management. Provenance Analysis Tool ... – PowerPoint PPT presentation

Number of Views:34
Avg rating:3.0/5.0
Slides: 20
Provided by: omer9
Category:

less

Transcript and Presenter's Notes

Title: Sharing Workflows


1
Sharing Workflows
  • Omer Rana
  • Cardiff University
  • o.f.rana_at_cs.cardiff.ac.uk

2
Workflow ( Enactment)
From Aleksander Slominski
Description
Launch, configure And control
Orchestration Service
Workflow Engine
Workflow Instance
Workflow Instance
Workflow Instance
Resource layer 1000s of PCs -gtmassive
supercomputers and data sources
Network
3
Incentives
  • Semantic annotations of services
  • UDDI too limited (TModel and CategoryBag)
  • Seek alternative service
  • Sharing of common interfaces
  • Composition S1 x S2 x S3 x Sn
  • x (sequence, parallel, map, etc)
  • Sharing ? Alternative Decompositions
  • C1 S1 x S2 x S3 (workflow re-writing)
  • C1 S1 x (S4 x S5) x S3
  • Eg. Look for a service tan(x)
  • Look for a services sin(x) and cos(x)

4
What can be shared?
  • Abstract (design time) workflow
  • Task graph encoding data flow or control flow
    dependencies
  • Concrete (run time) workflow
  • Service bindings to an abstract workflow graph
  • Sharing of graph structures, rather than just
    services
  • Limited case composite services

5
KNOOGLE (OMII UK)
  • Matchmaker shell that can support
  • Match plug-ins
  • Selection policy
  • Registry service (GRIMOIRES)
  • Matchmaker based
  • Syntax or context-based
  • Can identify match modes/scores
  • Selection Policy
  • Choice between returned services (policy)
  • Available from
  • OMII UK
  • Command line based
  • Or with Taverna 1.4.1

6
(No Transcript)
7
(No Transcript)
8
(No Transcript)
9
Re-enacting workflow
  • Run-time concrete workflow sharing
  • Understand
  • What happened when workflow was executed
  • What services were used and the type of I/O
    (interactions) involved
  • Use recorded provenance (history) information
    as a means to reconstruct workflow

The provenance of a piece of data is the process
that led to that piece of data
10
Provenance architecture (EU Provenance)
Service A (actor 2)
Application
Client (actor 1)
Service B (actor 3)
User
Provenance Store
11
p-assertion
  • A given element of process documentation referred
    to as a p-assertion
  • p-assertion is an assertion that is made by an
    actor and pertains to a process.
  • Types
  • Interaction p-assertion
  • relates to content of received/sent message
  • Actor State p-assertion
  • State of an actor
  • Relationship p-assertion
  • Relationships between interaction
  • p-assertions

From Luc Moreau (U Southampton)
12
Implementation Diagram
From Luc Moreau (U Southampton)
13
Portal OTM Application
14
Portal OTM Application
15
Portal EHCR Application
16
Portal DLR Application
17
Portal Management
18
Provenance Analysis Tool (JESS Rule Engine)
19
Thanks to
  • Julian Padget and Bill Naylor, Bath University
    Knoogle team
  • Subodh Vaid, Neil Chapman and Tom Goodale,
    Cardiff Knoogle team
  • Arnaud Contes, Vikas Deora, and the EU Provenance
    team (http//www.gridprovenance.org/)
Write a Comment
User Comments (0)
About PowerShow.com