mows @ wsdm f2f

9
MOWS @ WSDM F2F 15 Apr 2004

Upload: ula

Post on 26-Jan-2016

28 views

Category:

Documents


1 download

DESCRIPTION

MOWS @ WSDM F2F. 15 Apr 2004. Agenda. Metrics Service Lifecycle State Request Processing State Managing Operations. Metrics. An important metric is ResponseTime (used in SLAs, etc.) No way to reliably calculate it from the current MOWS Metrics. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: MOWS @ WSDM F2F

MOWS @ WSDM F2F

15 Apr 2004

Page 2: MOWS @ WSDM F2F

Agenda

Metrics Service Lifecycle State Request Processing State Managing Operations

Page 3: MOWS @ WSDM F2F

Metrics

An important metric is ResponseTime (used in SLAs, etc.)

No way to reliably calculate it from the current MOWS Metrics.

No reason to monitor every request state change for this metric either

Suggestion is to add mows-xs:MaxResponseTime which is a gauge, interval mows-xs:LastResponseTime (Richard) May be more

Writeup

Page 4: MOWS @ WSDM F2F

Metrics deficiency

#R

#S

2

1

4

3

5

5

rateresponse

2 p/s<1s

2 p/s<1s or <2s

1 p/s<1s or <2s or <3s

Page 5: MOWS @ WSDM F2F

Service Lifecycle State

Need to complete mapping of the W3C Lifecycle State to the WSDM state model Pending MUWS state model representation Pending MUWS events against state model

Page 6: MOWS @ WSDM F2F

Request Processing State

Need to add a new capability to express the W3C Request Processing State

Define state representation (possibly following MUWS state model representation pattern)

Define events: names and information set Define “triggers”/”conditions” Define request data collection “filters” Actual implementation/rendition would rely on our

choice of notification mechanism Pending WSN, writeup

Page 7: MOWS @ WSDM F2F

Managing Operations Currently managing the endpoints irrespective of operations

metrics are aggregated In many cases it makes sense to manage performance of individual

operations (e.g. GetMapData vs. LogIn). Using Request Processing State with “triggers” is very expensive for just

the per-operation metrics Do we need to manage per operation?

YES Exact solution TBD

Separate capability Optionality is implied Alternatives

Property name based solution Manageable op resource solution (EPRs) Metadata on the metrics property solution Metrics complex type (container) solution

Page 8: MOWS @ WSDM F2F

Managing Operations A nicer solution is possible (a proposal)

Define manageable operation resource MOWS.OperationIdentification MOWS.OperationMetrics extends MOWS.EndpointMetrics MOWS.OperationRequestProcessingState extends

MOWS.EndpointRequetsProcessingState Use WS-Resource pattern to work with various

manageable operation resources via the endpoint resource’s manageability endpoint (same endpoint).

MOWS.EndpointManageableOperations capability lists EPRs of all manageable operations (this could also be done more generally via MUWS.Relationships at a later point)

Page 9: MOWS @ WSDM F2F

Managing Operations (discussion)

Manageability endpoint

Manageable endpoint resource

Manageable operation resource

WSDL or EPR

EPR

EPR

EPR

EPR