SlideShare a Scribd company logo
S-Cube Learning Package

Chemical Modeling: Workflow Enactment
   based on the Chemical Metaphor



           INRIA, CNR, SZTAKI


          Zsolt Németh, SZTAKI


             www.s-cube-network.eu
Learning Package Categorization


                        S-Cube




                  Service Infrastructure




             Multi-level and self-adaptation



               Supporting adaptation of
              service-based applications
Learning Package Overview


 Workflow, workflow management
 Problem and requirement analysis
   – enactment in large-scale heterogeneous environments

 A chemical metaphor for workflow enactment
 A coordination model for workflow enactment formalized in
  the -calculus
 Further challenges
This talk is about workflow but…

 Workflow is just an example
   – It is a common programming model for grids
   – Features many coordination problems

 Focus: coordination
   – Large-scale distributed, dynamic, error prone environment and
     applications
   – Some degree of autonomy, adaptability, self-* must be provided
Workflow




  “The computerized facilitation or automation of a
   business process in whole or in part” – The Workflow Management
   Coalition

  a collection of activities that are processed in some order
   and where both data-flow and control-flow relationships
   may be present
The workflow Management Reference
Model (Workflow Management Coalition)


 Process Design                  Process Analysis, Modeling
                                 & Definition Tools
 & Definition
                                     Process Definition
 Build time
 Run time


 Process Instantiation          Workflow Enactment Service
 & Control

 Interaction with            User (human)
                                                   Applications &
 Users & Application Tools                         Tools
Scope of enactment



                          Abstract workflow
       Problem               standalone application components
                             the order in which they are executed
                             names, references, etc. are logical
   Abstract workflow
                          Represented by a graph
                             typically: DAG
   Concrete workflow



  Physical environment
Scope of enactment



                          Concrete workflow
       Problem               standalone application components
                             the order in which they are executed
                             selected resources, services
   Abstract workflow
                             additional activities (e.g. file transfer,
                              staging, etc.)
                             all names, references, etc. are physical
   Concrete workflow



  Physical environment
Learning Package Overview


 Workflow, workflow management
 Problem and requirement analysis
   – enactment in large-scale heterogeneous environments

 A chemical metaphor for workflow enactment
 A coordination model for workflow enactment formalized in
  the -calculus
 Further challenges
A common scenario
(e.g. grid workflow)



  Abstract workflow




                       Workflow engine

                                         Resources
A common scenario
(e.g. grid workflow)




 Abstract workflow
                                         Information system




                       Workflow engine

                                             Resources
A common scenario
(e.g. grid workflow)




 Abstract workflow
                                       Information system




                     Workflow engine
                                           Resources
A common scenario
(e.g. grid workflow)




  Abstract workflow
                                        Information system




                      Workflow engine

Concrete workflow                           Resources
A common scenario
(e.g. grid workflow)




  Abstract workflow
                                        Information system




                      Workflow engine
Concrete workflow                           Resources
Problem analysis (current approaches)



 The abstract workflow is static
 (Typically) no advanced control structures
 A priori mapping/ partly a priori mapping
 Mapping based on stored information
 A priori simulation/ a priori test/ a priori optimisation
 Centralised engine
 Human interaction
 Limited autonomy, limited ability for adaptation
 Overall lack of any high level model
Requirement analysis




  Workflow enactment in large-scale heterogeneous
   environments
    – should provide a higher level of autonomy
    – should be able to adapt to changing conditions
    – should be distributed
    – should be able to make decisions on partial and actual
      information
    – should support arbitrarily complex control structures
  Often a complex problem can be solved in a more simple
   way using nature inspired models
Learning Package Overview


 Workflow, workflow management
 Problem and requirement analysis
   – enactment in large-scale heterogeneous environments

 A chemical metaphor for workflow enactment
 A coordination model for workflow enactment formalized in
  the -calculus
 Further challenges
This talk is about a chemical
metaphor but…


  It is just an example
    – Chemical reactions are reasonably similar to workflow enactment
    – It has a well established formalism

  Generally: nature inspiration for solving complex problems
    – Simple, primitive parts behave “intelligently” as a whole
    – Ants, termites, cells, molecules, etc.
A chemical metaphor

 Reactions are
   – autonomous
   – distributed
   – concurrent
   – depending on local conditions
   – depending on actual conditions
   – not following any a priori pattern
   – evolving in time
A chemical metaphor



   Reactions are             Workflow enactment should
      autonomous               provide a higher level of
      distributed               autonomy

      concurrent               be able to adapt to changing
                                 conditions
      depending on local
       conditions               be distributed

      depending on actual      be able to make decisions on
       conditions                partial and actual information

      not following any a priori support arbitrarily complex
                               
       pattern                    control structures

      evolving in time
A vision of chemical enactment



  Resources
A vision of chemical enactment



  Resources
  Activities
A vision of chemical enactment



  Resources
  Activities
  Control
A vision of chemical enactment



  React
Learning Package Overview


 Workflow, workflow management
 Problem and requirement analysis
   – enactment in large-scale heterogeneous environments

 A chemical metaphor for workflow enactment
 A coordination model for workflow enactment formalized
  in the -calculus
 Further challenges
From a vision to a model



  Materialize information: resource quantums
  Define an abstract chemical coordination model
    – independent from actual technical realizations
    – provide a high-level abstract framework for refinement
    – formalism: -calculus
  Advance, refine: find chemical examples for
    – Complex control
    – Fault tolerance
    – Resource management
    – Optimization
    – etc
Resource quantums



  The usual solutions




                                              P4 P6
                                      P1P2

                                   P5 P3


 • stored information may be time sensitive
Resource quantums



  The usual solutions




                    P4
                    P2
                    P1
                      P6
                    P3
                    P5
Resource quantums
(« materialization of information »)


 resources are represented as tickets




                                                  P4 P6
                                           P1P2

                                         P5 P3


• tickets represent a guaranteed service
Resource quantums
(« materialization of information »)




                                 P2

  P6                             P5


  P4
                                 P1

                                 P3
The -calculus



 a declarative, functional formalism
 inherently concurrent model of computation
 basic data structure: multiset (chemical solution)
   – passive molecules: booleans, integers, tuples, naming molecules
   – active molecules: -abstraction

 reaction: active molecules capture other molecules
   – x.M, N → M[x:=N]

 execution: perform reactions until a stable (inert) chemical
  solution is resulted
The -calculus: -abstraction




 Active molecules: -abstraction: PC.M
   – P is a pattern that selects elements for the reaction
   – C is a condition; the reaction takes place if C is true
   – M is the action

 Example:  i:x, j:y i≤j, x>y. (j+1):x, j:y
 Semantics: capture i:x and j:y and replace them by (j+1):x,
  j:y if i≤j, x>y
 -abstraction is one-shot
 Universal matching symbol: 
The -calculus


 -terms are
   – Commutative: M1,M2≡M2,M1
   – Associative: (M1,M2),M3≡M1,(M2,M3)
   – Realize Brownian motion

 Reactions
   – Locality: if M1→M2, then M,M1→M,M2
   – Solution: if M1→M2, then <M1>→<M2>

 Conditional reactions
   –  xC.M

 Atomic capture
   –  x1,x2,…xn.M
Resources




 a resource quantum is modeled as a sub-solution
   – recall: chemical solutions can be nested

 elements in the solution are inert attribute:value pairs
 there are mandatory attributes otherwise, the format is felxible
 <id:R1, type:comp, proc:16, OS:Linux, …>
 <id:N1, type:net, bandwidth:23, …>
 <id:R3, type:comp, proc:1, installed:equsolver, network:N1 …>
Elementary activities


 the chemical model does not execute an activity, just enacts
  it – execution is external
 exit from the chemical world:
   – execute activity on resource using parameter
   – a symbolic notation that can be realised in many ways
 return to the chemical world
   – the execution produces some result or error put back in form of a
     solution (control molecule)
   – <ActivityID:result>
   – <ActivityID:result, error:errorcode, …>
   – <ActivityID:result, executed:R1, …>
 execute A on R→ <A:result…>,<id:R,…>
Resource dependency

 activity A needs a resource
 <id:r, type:comp, proc:1, >. execute A on r



                        < id:R2, type:comp, proc:1,…>
< id:R1, type:comp,
proc:16, OS:Linux, …>
                                                 < id:R3, type:comp,
                                                 proc:1, OS:SunOS, …>

                <id:r, type:comp, proc:1, >.
                     execute A on r
  < id:R4, type:comp,
                                      < id:R5, type:comp,
  proc:1, memory:23, …>
                                      proc:1, disk:12, …>
Resource dependency

 <id:r, type:comp, proc:1, >. execute A on r
 Captured a matching resource



                    < id:R2, type:comp, proc:1,…>
 < id:R1, type:comp,
 proc:16, OS:Linux, …>


                               execute A on R3



  < id:R4, type:comp,              < id:R5, type:comp,
  proc:1, memory:23, …>            proc:1, disk:12, …>
Resource dependency

 Both the resource and the activity are replaced by a control
  molecule




                    < id:R2, type:comp, proc:1,…>
 < id:R1, type:comp,
 proc:16, OS:Linux, …>
                                                < id:R3, type:comp,
                                                proc:1, OS:SunOS, …>


                          <A:12, error:0, executed:R3>

  < id:R4, type:comp,                 < id:R5, type:comp,
  proc:1, memory:23, …>               proc:1, disk:12, …>
Data and control dependency

 activity A waits a result from activity B
 <B:x, >. execute A using x




                   <C:0, error:5>


  <B:18>        <B:x, >. execute A using x


                                               <D:42>
                 <H:apple>
Data and control dependency

 <B:x, >. execute A using x
 Captured a corresponding control molecule




                 <C:0, error:5>


      execute A using 18


                                              <D:42>
               <H:apple>
Data and control dependency

 Replaced by the result




                     <C:0, error:5>


       <A:2, error:0,...>


                                      <D:42>
                  <H:apple>
Complex dependencies




 An activity needs both input from another activity and
  resources
   – <id:r, 1>, <B:x, 2>. execute A on r using x

 Dependencies can be arbitrarily combined
   – find a resource r1 for activity A and a resource r2 for B so that r1 and r2
     have the same operating system
   – <id:r1, OS:x, 1>, <id:r2, OS:x, 2> .
                          execute A on r1, execute B on r2

 Conditions can be added as well
   – <id:r, disk:x, memory:y, > x>30, y>12.
                               execute A on r
Workflow patterns



    Sequence
    Conditional
    Split
    Synchronizing merge
    P-split
      – p-out-of-n activities follow A

    P-merge
      – p-out-of-n results trigger activity A

    Loop
Learning Package Overview


 Workflow, workflow management
 Problem and requirement analysis
   – enactment in large-scale heterogeneous environments

 A chemical metaphor for workflow enactment
 A coordination model for workflow enactment formalized in
  the -calculus
 Further challenges
Challenges



  What we have so far is a framework
    – Principles of a chemical coordination model
    – It is just the beginning!

  Let’s explore and advance
    – Solve further aspects of workflow enactment: fault tolerance,
      optimization, resource control, complex workflow structures,
      constraints, co-allocation, compensation, etc.
    – Find further nature analogon within the chemical model:
      temperature, weight, magnetic properties, size, gravity, catalysts,
      membranes, etc.
Challenges (examples)



 Resource control by chemical agents
   – withdraw, modify, block, accept, reject, group, etc.

 Assert a neutralization agent: <id:r1, >.
 Replace a molecule:
  <id:r1, proc:1, OS:x, >.<id:r1, proc:1, OS:Linux, >
 Combine two molecules:
  (<id:r1, proc:1, >, <id:r1, proc:1, >).
  <id:r1, proc:2, >
Challenges (examples)



 Fault-tolerance by chemical agents
   – error molecules, retry, rollback, redundancy, compensation, etc.

 Assert an error handling molecule that reactivates in case of
  error
 (<Ai:x, >, <Aj:y, >, <id:r, R, >).
  (execute A on r using x y,
  (<A:errork, >,<id:r’, R, >).execute A on r’ using x y))
Challenges (examples)



 Complex resource allocation and co-llocation scenarios by
  molecules
   – e.g. reserve r1 and r2 so that there is a network link between them
   – (<id:r1, proc:1, network:n, >,
      <id:r2, proc:4, network:n, >,
      <id:n, type:net, >).
     (execute A on r1, (<A:x, >.execute B on r2 using x))
Conclusion



 The chemical metaphor: autonomous, adapting, distributed,
  actual
 The nature inspired coordination model
   – activities, resources and control are modeled using the same
     formalism
   – -calculus is not just description but defines execution semantics as
     well
   – workflow structure, resources and control can be
     added/withdrawn/modified in a fully dynamic and adaptive way
Connections to other teaching units



 Foundations
   – The Chemical Computing model and HOCL Programming

 Applications
   – Dynamic Adaptation with the Chemical Model




                                                   © S-Cube – 50/<Max>
References




 Zsolt Németh, Christian Pérez, Thierry Priol: Distributed workflow coordination: molecules and reactions.
 IPDPS 2006



 Zsolt Németh, Christian Pérez, Thierry Priol: Workflow Enactment Based on a Chemical Metaphor. SEFM
 2005: 127-136



 Manuel Caeiro, Zsolt Németh, Thierry Priol: A Chemical Model for Dynamic Workflow Coordination. PDP 2011:
 215-222
Acknowledgements




      The research leading to these results has
      received funding from the European
      Community’s Seventh Framework
      Programme [FP7/2007-2013] under grant
      agreement 215483 (S-Cube).

More Related Content

PDF
Online Chemical Modeling Environment: Models
PPTX
Distimo G Star Presentation
PPT
PHYSICO-CHEMICAL CHARACTERIZATION AND PRODUCT DEVELOPMENT FROM BANANA GERMPLA...
PDF
4th International Conference on Process Analytical Technologies in Organic Pr...
PDF
Chemical Spaces: Modeling, Exploration & Understanding
PPT
Is there a future for conventional abstracting and indexing services?
PDF
Online Workflow Management and Performance Analysis with Stampede
PDF
Adam shiwa summerschool 2012
Online Chemical Modeling Environment: Models
Distimo G Star Presentation
PHYSICO-CHEMICAL CHARACTERIZATION AND PRODUCT DEVELOPMENT FROM BANANA GERMPLA...
4th International Conference on Process Analytical Technologies in Organic Pr...
Chemical Spaces: Modeling, Exploration & Understanding
Is there a future for conventional abstracting and indexing services?
Online Workflow Management and Performance Analysis with Stampede
Adam shiwa summerschool 2012

Similar to S-CUBE LP: Chemical Modeling: Workflow Enactment based on the Chemical Metaphor (20)

PPTX
Workflow User Interfaces Patterns
PPT
Session 46 - Principles of workflow management and execution
PPTX
Cloud computing_Applications and paradigams.pptx
PPTX
Cloud computing_Applications and paradigams.pptx
PDF
Overview of Scientific Workflows - Why Use Them?
PDF
Climbing the tree of unreachable fruits, reusing processes
PPTX
Advances in Scientific Workflow Environments
PDF
Discovering Concurrency: Learning (Business) Process Models from Examples
PDF
Nephele pegasus
PPT
Requirements engineering vii
PDF
Workflows and Plone
 - Case supervisiondoc
PDF
Workflows via Event driven architecture
PDF
2001 09 ma,ma b2 b process integration tutorial
PPTX
WORKS 11 Presentation
PPTX
FAIR Computational Workflows
PDF
Business Process Modeling
PDF
Petri Net
PDF
A Chemistry-Inspired Workflow Management System for Scientific Applications o...
PPTX
Wengines, Workflows, and 2 years of advanced data processing in Apache OODT
PPTX
Getting Stuff Done! Managing Tasks with SharePoint Designer Workflows by Chri...
Workflow User Interfaces Patterns
Session 46 - Principles of workflow management and execution
Cloud computing_Applications and paradigams.pptx
Cloud computing_Applications and paradigams.pptx
Overview of Scientific Workflows - Why Use Them?
Climbing the tree of unreachable fruits, reusing processes
Advances in Scientific Workflow Environments
Discovering Concurrency: Learning (Business) Process Models from Examples
Nephele pegasus
Requirements engineering vii
Workflows and Plone
 - Case supervisiondoc
Workflows via Event driven architecture
2001 09 ma,ma b2 b process integration tutorial
WORKS 11 Presentation
FAIR Computational Workflows
Business Process Modeling
Petri Net
A Chemistry-Inspired Workflow Management System for Scientific Applications o...
Wengines, Workflows, and 2 years of advanced data processing in Apache OODT
Getting Stuff Done! Managing Tasks with SharePoint Designer Workflows by Chri...
Ad

More from virtual-campus (20)

PDF
S-CUBE LP: Analysis Operations on SLAs: Detecting and Explaining Conflicting ...
PDF
S-CUBE LP: Quality of Service-Aware Service Composition: QoS optimization in ...
PDF
S-CUBE LP: The Chemical Computing model and HOCL Programming
PDF
S-CUBE LP: Executing the HOCL: Concept of a Chemical Interpreter
PDF
S-CUBE LP: SLA-based Service Virtualization in distributed, heterogenious env...
PDF
S-CUBE LP: Service Discovery and Task Models
PDF
S-CUBE LP: Impact of SBA design on Global Software Development
PDF
S-CUBE LP: Techniques for design for adaptation
PDF
S-CUBE LP: Self-healing in Mixed Service-oriented Systems
PDF
S-CUBE LP: Analyzing and Adapting Business Processes based on Ecologically-aw...
PDF
S-CUBE LP: Preventing SLA Violations in Service Compositions Using Aspect-Bas...
PDF
S-CUBE LP: Analyzing Business Process Performance Using KPI Dependency Analysis
PDF
S-CUBE LP: Process Performance Monitoring in Service Compositions
PDF
S-CUBE LP: Service Level Agreement based Service infrastructures in the conte...
PDF
S-CUBE LP: Runtime Prediction of SLA Violations Based on Service Event Logs
PDF
S-CUBE LP: Proactive SLA Negotiation
PDF
S-CUBE LP: A Soft-Constraint Based Approach to QoS-Aware Service Selection
PDF
S-CUBE LP: Variability Modeling and QoS Analysis of Web Services Orchestrations
PDF
S-CUBE LP: Run-time Verification for Preventive Adaptation
PDF
S-CUBE LP: Online Testing for Proactive Adaptation
S-CUBE LP: Analysis Operations on SLAs: Detecting and Explaining Conflicting ...
S-CUBE LP: Quality of Service-Aware Service Composition: QoS optimization in ...
S-CUBE LP: The Chemical Computing model and HOCL Programming
S-CUBE LP: Executing the HOCL: Concept of a Chemical Interpreter
S-CUBE LP: SLA-based Service Virtualization in distributed, heterogenious env...
S-CUBE LP: Service Discovery and Task Models
S-CUBE LP: Impact of SBA design on Global Software Development
S-CUBE LP: Techniques for design for adaptation
S-CUBE LP: Self-healing in Mixed Service-oriented Systems
S-CUBE LP: Analyzing and Adapting Business Processes based on Ecologically-aw...
S-CUBE LP: Preventing SLA Violations in Service Compositions Using Aspect-Bas...
S-CUBE LP: Analyzing Business Process Performance Using KPI Dependency Analysis
S-CUBE LP: Process Performance Monitoring in Service Compositions
S-CUBE LP: Service Level Agreement based Service infrastructures in the conte...
S-CUBE LP: Runtime Prediction of SLA Violations Based on Service Event Logs
S-CUBE LP: Proactive SLA Negotiation
S-CUBE LP: A Soft-Constraint Based Approach to QoS-Aware Service Selection
S-CUBE LP: Variability Modeling and QoS Analysis of Web Services Orchestrations
S-CUBE LP: Run-time Verification for Preventive Adaptation
S-CUBE LP: Online Testing for Proactive Adaptation
Ad

Recently uploaded (20)

PPTX
Understanding_Digital_Forensics_Presentation.pptx
PDF
Advanced methodologies resolving dimensionality complications for autism neur...
PDF
Machine learning based COVID-19 study performance prediction
PDF
Electronic commerce courselecture one. Pdf
PDF
GamePlan Trading System Review: Professional Trader's Honest Take
PPTX
Big Data Technologies - Introduction.pptx
PDF
Approach and Philosophy of On baking technology
PDF
NewMind AI Monthly Chronicles - July 2025
PDF
NewMind AI Weekly Chronicles - August'25 Week I
PDF
GDG Cloud Iasi [PUBLIC] Florian Blaga - Unveiling the Evolution of Cybersecur...
PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
PDF
Diabetes mellitus diagnosis method based random forest with bat algorithm
PDF
[발표본] 너의 과제는 클라우드에 있어_KTDS_김동현_20250524.pdf
PPT
“AI and Expert System Decision Support & Business Intelligence Systems”
PDF
Modernizing your data center with Dell and AMD
PDF
Advanced Soft Computing BINUS July 2025.pdf
PDF
solutions_manual_-_materials___processing_in_manufacturing__demargo_.pdf
PDF
Chapter 3 Spatial Domain Image Processing.pdf
PDF
Network Security Unit 5.pdf for BCA BBA.
PDF
Dropbox Q2 2025 Financial Results & Investor Presentation
Understanding_Digital_Forensics_Presentation.pptx
Advanced methodologies resolving dimensionality complications for autism neur...
Machine learning based COVID-19 study performance prediction
Electronic commerce courselecture one. Pdf
GamePlan Trading System Review: Professional Trader's Honest Take
Big Data Technologies - Introduction.pptx
Approach and Philosophy of On baking technology
NewMind AI Monthly Chronicles - July 2025
NewMind AI Weekly Chronicles - August'25 Week I
GDG Cloud Iasi [PUBLIC] Florian Blaga - Unveiling the Evolution of Cybersecur...
Reach Out and Touch Someone: Haptics and Empathic Computing
Diabetes mellitus diagnosis method based random forest with bat algorithm
[발표본] 너의 과제는 클라우드에 있어_KTDS_김동현_20250524.pdf
“AI and Expert System Decision Support & Business Intelligence Systems”
Modernizing your data center with Dell and AMD
Advanced Soft Computing BINUS July 2025.pdf
solutions_manual_-_materials___processing_in_manufacturing__demargo_.pdf
Chapter 3 Spatial Domain Image Processing.pdf
Network Security Unit 5.pdf for BCA BBA.
Dropbox Q2 2025 Financial Results & Investor Presentation

S-CUBE LP: Chemical Modeling: Workflow Enactment based on the Chemical Metaphor

  • 1. S-Cube Learning Package Chemical Modeling: Workflow Enactment based on the Chemical Metaphor INRIA, CNR, SZTAKI Zsolt Németh, SZTAKI www.s-cube-network.eu
  • 2. Learning Package Categorization S-Cube Service Infrastructure Multi-level and self-adaptation Supporting adaptation of service-based applications
  • 3. Learning Package Overview  Workflow, workflow management  Problem and requirement analysis – enactment in large-scale heterogeneous environments  A chemical metaphor for workflow enactment  A coordination model for workflow enactment formalized in the -calculus  Further challenges
  • 4. This talk is about workflow but…  Workflow is just an example – It is a common programming model for grids – Features many coordination problems  Focus: coordination – Large-scale distributed, dynamic, error prone environment and applications – Some degree of autonomy, adaptability, self-* must be provided
  • 5. Workflow  “The computerized facilitation or automation of a business process in whole or in part” – The Workflow Management Coalition  a collection of activities that are processed in some order and where both data-flow and control-flow relationships may be present
  • 6. The workflow Management Reference Model (Workflow Management Coalition) Process Design Process Analysis, Modeling & Definition Tools & Definition Process Definition Build time Run time Process Instantiation Workflow Enactment Service & Control Interaction with User (human) Applications & Users & Application Tools Tools
  • 7. Scope of enactment  Abstract workflow Problem  standalone application components  the order in which they are executed  names, references, etc. are logical Abstract workflow  Represented by a graph  typically: DAG Concrete workflow Physical environment
  • 8. Scope of enactment  Concrete workflow Problem  standalone application components  the order in which they are executed  selected resources, services Abstract workflow  additional activities (e.g. file transfer, staging, etc.)  all names, references, etc. are physical Concrete workflow Physical environment
  • 9. Learning Package Overview  Workflow, workflow management  Problem and requirement analysis – enactment in large-scale heterogeneous environments  A chemical metaphor for workflow enactment  A coordination model for workflow enactment formalized in the -calculus  Further challenges
  • 10. A common scenario (e.g. grid workflow) Abstract workflow Workflow engine Resources
  • 11. A common scenario (e.g. grid workflow) Abstract workflow Information system Workflow engine Resources
  • 12. A common scenario (e.g. grid workflow) Abstract workflow Information system Workflow engine Resources
  • 13. A common scenario (e.g. grid workflow) Abstract workflow Information system Workflow engine Concrete workflow Resources
  • 14. A common scenario (e.g. grid workflow) Abstract workflow Information system Workflow engine Concrete workflow Resources
  • 15. Problem analysis (current approaches)  The abstract workflow is static  (Typically) no advanced control structures  A priori mapping/ partly a priori mapping  Mapping based on stored information  A priori simulation/ a priori test/ a priori optimisation  Centralised engine  Human interaction  Limited autonomy, limited ability for adaptation  Overall lack of any high level model
  • 16. Requirement analysis  Workflow enactment in large-scale heterogeneous environments – should provide a higher level of autonomy – should be able to adapt to changing conditions – should be distributed – should be able to make decisions on partial and actual information – should support arbitrarily complex control structures  Often a complex problem can be solved in a more simple way using nature inspired models
  • 17. Learning Package Overview  Workflow, workflow management  Problem and requirement analysis – enactment in large-scale heterogeneous environments  A chemical metaphor for workflow enactment  A coordination model for workflow enactment formalized in the -calculus  Further challenges
  • 18. This talk is about a chemical metaphor but…  It is just an example – Chemical reactions are reasonably similar to workflow enactment – It has a well established formalism  Generally: nature inspiration for solving complex problems – Simple, primitive parts behave “intelligently” as a whole – Ants, termites, cells, molecules, etc.
  • 19. A chemical metaphor  Reactions are – autonomous – distributed – concurrent – depending on local conditions – depending on actual conditions – not following any a priori pattern – evolving in time
  • 20. A chemical metaphor  Reactions are  Workflow enactment should  autonomous  provide a higher level of  distributed autonomy  concurrent  be able to adapt to changing conditions  depending on local conditions  be distributed  depending on actual  be able to make decisions on conditions partial and actual information  not following any a priori support arbitrarily complex  pattern control structures  evolving in time
  • 21. A vision of chemical enactment  Resources
  • 22. A vision of chemical enactment  Resources  Activities
  • 23. A vision of chemical enactment  Resources  Activities  Control
  • 24. A vision of chemical enactment  React
  • 25. Learning Package Overview  Workflow, workflow management  Problem and requirement analysis – enactment in large-scale heterogeneous environments  A chemical metaphor for workflow enactment  A coordination model for workflow enactment formalized in the -calculus  Further challenges
  • 26. From a vision to a model  Materialize information: resource quantums  Define an abstract chemical coordination model – independent from actual technical realizations – provide a high-level abstract framework for refinement – formalism: -calculus  Advance, refine: find chemical examples for – Complex control – Fault tolerance – Resource management – Optimization – etc
  • 27. Resource quantums  The usual solutions P4 P6 P1P2 P5 P3 • stored information may be time sensitive
  • 28. Resource quantums  The usual solutions P4 P2 P1 P6 P3 P5
  • 29. Resource quantums (« materialization of information »)  resources are represented as tickets P4 P6 P1P2 P5 P3 • tickets represent a guaranteed service
  • 30. Resource quantums (« materialization of information ») P2 P6 P5 P4 P1 P3
  • 31. The -calculus  a declarative, functional formalism  inherently concurrent model of computation  basic data structure: multiset (chemical solution) – passive molecules: booleans, integers, tuples, naming molecules – active molecules: -abstraction  reaction: active molecules capture other molecules – x.M, N → M[x:=N]  execution: perform reactions until a stable (inert) chemical solution is resulted
  • 32. The -calculus: -abstraction  Active molecules: -abstraction: PC.M – P is a pattern that selects elements for the reaction – C is a condition; the reaction takes place if C is true – M is the action  Example:  i:x, j:y i≤j, x>y. (j+1):x, j:y  Semantics: capture i:x and j:y and replace them by (j+1):x, j:y if i≤j, x>y  -abstraction is one-shot  Universal matching symbol: 
  • 33. The -calculus  -terms are – Commutative: M1,M2≡M2,M1 – Associative: (M1,M2),M3≡M1,(M2,M3) – Realize Brownian motion  Reactions – Locality: if M1→M2, then M,M1→M,M2 – Solution: if M1→M2, then <M1>→<M2>  Conditional reactions –  xC.M  Atomic capture –  x1,x2,…xn.M
  • 34. Resources  a resource quantum is modeled as a sub-solution – recall: chemical solutions can be nested  elements in the solution are inert attribute:value pairs  there are mandatory attributes otherwise, the format is felxible  <id:R1, type:comp, proc:16, OS:Linux, …>  <id:N1, type:net, bandwidth:23, …>  <id:R3, type:comp, proc:1, installed:equsolver, network:N1 …>
  • 35. Elementary activities  the chemical model does not execute an activity, just enacts it – execution is external  exit from the chemical world: – execute activity on resource using parameter – a symbolic notation that can be realised in many ways  return to the chemical world – the execution produces some result or error put back in form of a solution (control molecule) – <ActivityID:result> – <ActivityID:result, error:errorcode, …> – <ActivityID:result, executed:R1, …>  execute A on R→ <A:result…>,<id:R,…>
  • 36. Resource dependency  activity A needs a resource  <id:r, type:comp, proc:1, >. execute A on r < id:R2, type:comp, proc:1,…> < id:R1, type:comp, proc:16, OS:Linux, …> < id:R3, type:comp, proc:1, OS:SunOS, …> <id:r, type:comp, proc:1, >. execute A on r < id:R4, type:comp, < id:R5, type:comp, proc:1, memory:23, …> proc:1, disk:12, …>
  • 37. Resource dependency  <id:r, type:comp, proc:1, >. execute A on r  Captured a matching resource < id:R2, type:comp, proc:1,…> < id:R1, type:comp, proc:16, OS:Linux, …> execute A on R3 < id:R4, type:comp, < id:R5, type:comp, proc:1, memory:23, …> proc:1, disk:12, …>
  • 38. Resource dependency  Both the resource and the activity are replaced by a control molecule < id:R2, type:comp, proc:1,…> < id:R1, type:comp, proc:16, OS:Linux, …> < id:R3, type:comp, proc:1, OS:SunOS, …> <A:12, error:0, executed:R3> < id:R4, type:comp, < id:R5, type:comp, proc:1, memory:23, …> proc:1, disk:12, …>
  • 39. Data and control dependency  activity A waits a result from activity B  <B:x, >. execute A using x <C:0, error:5> <B:18>  <B:x, >. execute A using x <D:42> <H:apple>
  • 40. Data and control dependency  <B:x, >. execute A using x  Captured a corresponding control molecule <C:0, error:5> execute A using 18 <D:42> <H:apple>
  • 41. Data and control dependency  Replaced by the result <C:0, error:5> <A:2, error:0,...> <D:42> <H:apple>
  • 42. Complex dependencies  An activity needs both input from another activity and resources – <id:r, 1>, <B:x, 2>. execute A on r using x  Dependencies can be arbitrarily combined – find a resource r1 for activity A and a resource r2 for B so that r1 and r2 have the same operating system – <id:r1, OS:x, 1>, <id:r2, OS:x, 2> . execute A on r1, execute B on r2  Conditions can be added as well – <id:r, disk:x, memory:y, > x>30, y>12. execute A on r
  • 43. Workflow patterns  Sequence  Conditional  Split  Synchronizing merge  P-split – p-out-of-n activities follow A  P-merge – p-out-of-n results trigger activity A  Loop
  • 44. Learning Package Overview  Workflow, workflow management  Problem and requirement analysis – enactment in large-scale heterogeneous environments  A chemical metaphor for workflow enactment  A coordination model for workflow enactment formalized in the -calculus  Further challenges
  • 45. Challenges  What we have so far is a framework – Principles of a chemical coordination model – It is just the beginning!  Let’s explore and advance – Solve further aspects of workflow enactment: fault tolerance, optimization, resource control, complex workflow structures, constraints, co-allocation, compensation, etc. – Find further nature analogon within the chemical model: temperature, weight, magnetic properties, size, gravity, catalysts, membranes, etc.
  • 46. Challenges (examples)  Resource control by chemical agents – withdraw, modify, block, accept, reject, group, etc.  Assert a neutralization agent: <id:r1, >.  Replace a molecule: <id:r1, proc:1, OS:x, >.<id:r1, proc:1, OS:Linux, >  Combine two molecules: (<id:r1, proc:1, >, <id:r1, proc:1, >). <id:r1, proc:2, >
  • 47. Challenges (examples)  Fault-tolerance by chemical agents – error molecules, retry, rollback, redundancy, compensation, etc.  Assert an error handling molecule that reactivates in case of error  (<Ai:x, >, <Aj:y, >, <id:r, R, >). (execute A on r using x y, (<A:errork, >,<id:r’, R, >).execute A on r’ using x y))
  • 48. Challenges (examples)  Complex resource allocation and co-llocation scenarios by molecules – e.g. reserve r1 and r2 so that there is a network link between them – (<id:r1, proc:1, network:n, >, <id:r2, proc:4, network:n, >, <id:n, type:net, >). (execute A on r1, (<A:x, >.execute B on r2 using x))
  • 49. Conclusion  The chemical metaphor: autonomous, adapting, distributed, actual  The nature inspired coordination model – activities, resources and control are modeled using the same formalism – -calculus is not just description but defines execution semantics as well – workflow structure, resources and control can be added/withdrawn/modified in a fully dynamic and adaptive way
  • 50. Connections to other teaching units  Foundations – The Chemical Computing model and HOCL Programming  Applications – Dynamic Adaptation with the Chemical Model © S-Cube – 50/<Max>
  • 51. References Zsolt Németh, Christian Pérez, Thierry Priol: Distributed workflow coordination: molecules and reactions. IPDPS 2006 Zsolt Németh, Christian Pérez, Thierry Priol: Workflow Enactment Based on a Chemical Metaphor. SEFM 2005: 127-136 Manuel Caeiro, Zsolt Németh, Thierry Priol: A Chemical Model for Dynamic Workflow Coordination. PDP 2011: 215-222
  • 52. Acknowledgements The research leading to these results has received funding from the European Community’s Seventh Framework Programme [FP7/2007-2013] under grant agreement 215483 (S-Cube).