wsdm message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [wsdm] [Uarch] MUWS logical model concepts
- From: "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>
- To: "ECKERT,ZULAH (HP-Cupertino,ex1)" <zulah_eckert@hp.com>,<wsdm@lists.oasis-open.org>
- Date: Thu, 13 Nov 2003 10:32:43 -0500
Title: Message
Hmm...
According to the diagram
One consumer interacts with many services. why can't many
consumers interact with one service as well? There are a few similar problems
with cardinality that I see on the diagram.
Using WSDL I can create a description of a service which
endpoints belong to different providers (owners). How would that work with the
expressed set of concepts?
As per our earlier definition manageability capabilities
are merely a set of distinct semantics which could be expressed in a model. I
can see how a capability could *represent* how to monitor/control along with
other things, but I don't understand how it would actually do that. This is like
saying that an interface monitors/controls something. That is never so, an
implementation of an interface could do that. So, IMO, manageable resource is
the one that offers monitoring/control of itself. Conceptually. Implementations
may vary e.g. a manageability service/endpoint implementation may internally be
able to control the *resource*. The resource + its controls (implementation) =
manageable resource.
-- Igor
Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza,
Islandia, NY 11788
Appologies for missing the last Uarch call.
Attached is a proposal for the roles and relationships model (or logical
concepts model) for the teams consideration. There are similarities to the
diagram that Igor proposed, but they differ in some aspects:
* the
manageability provider provides a manageability service, not the manageable
resource
* a
manageable resource has an associated manageability provider for it
manageability service
* the
diagram is service as opposed to endpoint centric
* the
manageability consumer manages a manageable resource by montoring and controling
using the manageability capabilities
Zulah
-----Original Message-----
From:
Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com]
Sent: Friday, November
07, 2003 9:04 AM
To: wsdm@lists.oasis-open.org
Subject:
[wsdm] [Uarch] MUWS logical model concepts
On the last Uarch call I promised
to send a logical model formalization in UML. The diagram is attached. The
words to PRECEDE the diagram are as follows (assuming the roles of
manageability provider and manageability consumer are roughly
defined).
"
The manageability provider may provide many
manageable resources, instances of which belong to one instance of the
provider. To do this, manageability provider maintains manageability endpoints
which provide access to manageable resources. Manageable resource is a
resource with a number of manageability capabilities composed into it.
Manageability capabilities are explicitly supported by the manageability
provider and are offered via manageability endpoints.
The manageability consumers deal
with manageable resources. To 'deal with' in this context means to exert
control and to obtain and interpret the information. In order to deal with the
manageable resource, consumers access manageability endpoints and exrecsise
offered manageability capabilities. To 'exercise' in this context means to
make use of the distinct semantics defined for a given manageability
capability. Technically, it translates into being able to use a distinct group
of properties, operations, events and metadata by exchanging messages with the
manageability endpoint.
"
<<MUWS Logical Model.png>>
-- Igor
Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza,
Islandia, NY 11788
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]