OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsdm] multiple sutiation categories in an event


I suggest we consider the multiple situation category scenario in V2.0. While it is an interesting idea there are two aspects about it I do not like.

Foremost, I haven't seen a case yet that justifies it.

Secondly, when we start to think about how events will get filtered, we will gain a huge benefit from the situationcategories. If we allow more than one category per event then it is conceiveable that a single event could get routed to two independent managers that are responsible for different event types. How do we handle the contention between these managers if they are both responding to the same resource on the same event? This takes far more study than an eleventh hour attempt to compromise.

Thomas W. Studwell
Senior Technical Staff Member, Autonomic Computing Architecture
IBM Software Group
C151/Bldg 500
4205 S Miami Blvd, Durham, NC 27703
(919) 254-7574 Fax: (919) 254-7628 Mobile: (919) 619-1038
studwell@us.ibm.com

"What marks the mind of the strategist is an intellectual elasticity or flexibility that enables him to come up with realistic responses to changing conditions... In strategic thinking, one first seeks a clear understanding of the particular character of each element of a situation and then makes the fullest possible use of human brainpower to restructure the elements in the most advantageous way." (Keniche Ohmae, The Mind of the Strategist)
Inactive hide details for "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>"Sedukhin, Igor S" <Igor.Sedukhin@ca.com>


          "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>

          11/17/2004 04:39 PM


To

<wsdm@lists.oasis-open.org>

cc


Subject

[wsdm] multiple sutiation categories in an event

It may be interesting to hear opinions of the TC members about what William has proposed as a way to move forward with the situation categories: allow multiple situation categories in an event.

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
--
(631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749




From: Sedukhin, Igor S
Sent:
Wednesday, November 17, 2004 2:47 PM
To:
Vambenepe, William N; wsdm@lists.oasis-open.org
Subject:
RE: [wsdm] cases on situation categories

Ok, if we accept what you propose I may let this go. It is not getting any better, it seems...

I suggest that we decice this on the call tomorrow.

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
--
(631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749




From: Vambenepe, William N [mailto:vbp@hp.com]
Sent:
Wednesday, November 17, 2004 1:39 PM
To:
Sedukhin, Igor S; wsdm@lists.oasis-open.org
Subject:
RE: [wsdm] cases on situation categories

Igor,

Do you think that allowing more than one situation category would cover your examples better? If events are related to more than one it can be expressed in the message...

William


From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com]
Sent:
Wednesday, November 17, 2004 8:40 AM
To:
wsdm@lists.oasis-open.org
Subject:
[wsdm] cases on situation categories

#1 there is a property which is mydevice:ConnectedTo which indicates the name of the network which the device is currently connected to e.g. Nothing, GSM900, GSM1900, GSM 1800, 802.11g, 802.11.b etc. Such property is writeable and could be set by the manager, so this is configuration. When a property change event has to be generated by an manageability implementation for this device, what would be the situation category to put in the event data: Configuration, Connection or Report? What part of the WSDM spec will be sufficient to describe the choice for an average developer?

#2 there is an OperationalState property and an event is generated for this property change when state transition from DOWN:CRASHED to DOWN:STOPPED. What does one put as a situation category: Availability, Stop or Report? In this case, availability did not change so it is just a report, but the operational state certainly defines the availability. DOWN:STOPPED is a state which indicates that resource is stopped, but its availability didn't really change in case of this transition. However this would not be true if transitioning from UP to DOWN:STOPPED, in that case the availability changes. A) What in the spec would lead one to be crystal clear on which situation category to pick in this case? B) What if the event generator has no knowwledge of the actual resource state model? How would it decide between UP->DOWN:STOPPED and DOWN:CRASHED->DOWN:STOPPED?

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
--
(631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749

GIF image



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]