wishing a shared terminology bis n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Wishing a shared terminology bis PowerPoint Presentation
Download Presentation
Wishing a shared terminology bis

Loading in 2 Seconds...

play fullscreen
1 / 18

Wishing a shared terminology bis - PowerPoint PPT Presentation


  • 104 Views
  • Uploaded on

Wishing a shared terminology bis. WS-Diamond meeting 29-11-2005. To discuss. Architecture (model of execution for WS-Diamond) Fault classifications Repair actions Terms & glossay & questions. Tasks.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Wishing a shared terminology bis' - jerica


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
wishing a shared terminology bis

Wishing a shared terminologybis

WS-Diamond meeting

29-11-2005

to discuss
To discuss
  • Architecture (model of execution for WS-Diamond)
  • Fault classifications
  • Repair actions
  • Terms & glossay & questions

WP3 meeting - Milan November 29th, 2005

tasks
Tasks
  • 1 models of execution mechanisms and composition strategies, dynamic architectures, workflow and interaction management (3-9, 12-18)
  • 2 execution models for repair actions (9-27)
  • 3 Prototyping 15-30 (first 18, final 30)

WP3 meeting - Milan November 29th, 2005

slide4

Self-healing platform architecture

One node

WP3 meeting - Milan November 29th, 2005

slide5

WS-DIAMOND -enabled node

WS

Mgmt intf

Non WS-Diamond node

BPEL orchestration engine

WS

Repair action selector

Non WS-Diamond node

WS

Diagnosis infrastructure

network

Diagnosis infrastructure

Failure detection

Failure detection

WS

Mgmt intf

Conversation mgr

Conversation client

WSDM?

BPEL orchestration engine

WS

Mgmt intf

BPEL orchestration engine

Mgmt intf

WS

Repair action selector

Repair action selector

Diagnosis infrastructure

Failure detection

Diagnosis infrastructure

Failure detection

WS-DIAMOND -enabled node

Failure detection

WS-DIAMOND -enabled node

WS-DIAMOND -enabled node

WP3 meeting - Milan November 29th, 2005

slide6

4. Fault classification

Fault classification

WP3 meeting - Milan November 29th, 2005

other classifications of faults
Other classifications of faults
  • Toulouse
    • Functional
    • QoS (e.g. WSOL)
      • Generic
      • Temporal
      • Domain
      • Data
    • Semantic

Model

    • Qos request, provisioning, contract
    • Mismatch and handling
    • “errors” in invocation

WP3 meeting - Milan November 29th, 2005

failure events fault types mourao antunes 04
Failure events (Fault types (Mourao, Antunes 04))
  • Data event
  • Temporal event
  • Wf events
  • System/appls events
  • External (human, …) ?
  • Noncompliance events

WP3 meeting - Milan November 29th, 2005

wf modification
WF modification
  • WF schema modification run time?
  • Human actions (modification of process)
  • Other types of external “compensations” (or external compensations)?

WP3 meeting - Milan November 29th, 2005

failure error and fault ieee tc ftd ifip wg10 4 definitions
Failure error and faultIEEE TC FTD/IFIP WG10.4 definitions
  • A system failure occurs when the delivered service deviates from fulfilling the system function, the latter being what the system is aimed at
  • An error is that part of the system state which is liable to lead to subsequent failure: an error affecting the service is an indication that a failure occurs or has occurred. The adjudged or hypothesised cause of an error is a fault
  • (Note: errors do not necessarily lead to failures; component failures are not necessarily faults to the surrounding system)

WP3 meeting - Milan November 29th, 2005

the failure fault error chain
The Failure Fault Error “Chain”
  • A failure occurs when an error “passes through” the system-user interface and affects the service delivered by the system – a system of course being composed of components which are themselves systems.
  • Thus the manifestation of failures, faults and errors follows a “fundamental chain”:
    • failure  fault  error  failure  fault . . .
    • event  cause  state  event  cause  . . .

WP3 meeting - Milan November 29th, 2005

a simple question
A simple (?) question
  • What are we doing in WS-Diamond? (please check)
    • Failure detection (input to diagnosis)
    • Fault identification (result of diagnosis)
    • Error recovery and repair

WP3 meeting - Milan November 29th, 2005

terms 1 3
Terms 1/3
  • Exceptions = mean of notifying failures to diagnosers (some failures are not detected)
    • Known
    • Unknown (cfr middleware RMI, CORBA , propagation of exception)

WP3 meeting - Milan November 29th, 2005

terms
Terms
  • Diagnosis
    • Fault + context (note: tradeoff with detail of model)
  • Orchestration (Peltz’s paper IEEE Computer Oct. 2003)
  • Choreography
  • Web service (model)
  • Process model
  • Exceptions, Handlers, compensations

WP3 meeting - Milan November 29th, 2005

list minute addendum
List minute addendum
  • Symptom = exception
  • On line recovery (reactive)
  • Off line repair (proactive)
  • Recovery includes repair

WP3 meeting - Milan November 29th, 2005

questions
Questions
  • Domain dependent and/or domain independent?
  • patterns

WP3 meeting - Milan November 29th, 2005

tasks1
Tasks
  • 1 models of execution mechanisms and composition strategies, dynamic architectures, workflow and interaction management (3-9, 12-18)
    • Glossary
      • Failures, etc terms, recovery, repair (TO)
      • Unknown exception (Toulouse)
      • Mismatch (Toulouse)
    • Fault taxonomy (MI-Toulouse) (also for glossary PoliMi)
    • WF modification
      • Klagenfurt
      • polimi
    • Architecture (TO) (Vienna)
    • Models
      • Ws invocation
      • Business process (PoliMI)
        • Orchestrated
          • Exceptions, Handlers, compensations
        • Choreographed (TO)
    • Taxonomy of repair action
  • 2 execution models for repair actions (9-27)
    • E.g. ECA
    • Wf dynamic modification?? (Mecella)
  • 3 Prototyping 15-30 (first 18, final 30)
    • Proof of concept
    • working

WP3 meeting - Milan November 29th, 2005