wsdm message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [wsdm] OASIS WSDM [OMod] call
- From: "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>
- To: <wsdm@lists.oasis-open.org>
- Date: Tue, 7 Oct 2003 14:13:08 -0400
Title: OASIS WSDM [OMod] call
10/07/2003
Present: Igor, Fred, JohnDC, BrianC,
GeoffB.
A&B.
Igor:
presented the diagram and its intention
No
significant objections about the conceptual diagram.
BrianC: said that versioning is an important enough element that may have
to be included on the diagram.
Igor:
yes, but that would be a detail of this "root" diagram and may be represented as
a separate diagram or possibly as a representation of one of
the manageabity capability information models.
We
didn't find any voluteers for the work items 1-3 for now :).
JohnDC: in addition to 1, overview has to include another scoping
statement of a similar content: about the endpoint implementation management.
Just say that it is someone's responsibility to aggregate that information up to
the endpoint manageability level. For example, management of loadbalanced
endpoint in a web server farm.
GeoffB: expressed concern how to make sure that instances of managability
representations expressed in MOWS and MUWS stich together properly. That is it
should be possible to do root cause analysis using that infromation. For
example, relationship to hosting environment, etc.
Igor:
yes, that is a concern for internal resources management which, to certain
extent, generally works today, but we have more concern for external,
federated management of WSs which is not generally possible today. That is a
valid concern and we should not break or preclude proper information stitching,
but focus on the later. For example, URL where SOAP messages are sent can
be used today as a basis for the root cause analysys, and relationships can
be used to express any kind of lower-level relationships using MUWS (defining
that is already on our agenda).
C.
Igor:
proposed to use the UML notation that WS-Manageability used to express the
atomic manageability capability models. That is representation
of properties, data models, events and operations. We can then
dicuss what goes in or out of the models on the calls.
Dind't
hear pushback on that.
Igor:
proposed to edit UMLs and send them with updates for now.
That
was ok with the group.
ACTION: Igor to send out an example representation of one atomic
capability model before the next call.
-- Igor
Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza,
Islandia, NY 11788
Agenda for [OMod] call tomorrow.
A.
Review attached UML diagram intended for MOWS spec overview section. Attached.
This was a product of our discussion during the [OMod] ad-hoc meeting
on Wed after the F2F. Me, Mark, Fred and Zulah were
present.
B.
Find volunteers for the following (coming from the discussion about the diagram
in A.)
1. Text in the
overview of the MOWS spec must elaborate on the manageability at the service
level. Essentially "how to use manageabilty of endpoints to infer (aggregate)
manageability of a service".
2. The diagram will show a shade on the nexus points of MUWS and MOWS
(manageable resource and manageable endpoint respectively). Only nexus points
will be singled out on this diagram. There will be abother diagram that shows
relationships of MUWS and MOWS concepts (possibly aggregation/composition of
manageability capabilities).
3. There is a need for another diagram to display
the "locus of implementation" concepts.
C.
Discuss the UML framework in which to express manageability
capabilities following the MOWS contents outline discussed during the
F2F.
-- Igor
Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza,
Islandia, NY 11788
Every TUE, 1-2
EST.
Reservationless-Plus Toll Free Dial-In Number: (888) 827-2241
Reservationless-Plus International Dial-In Number: (706) 679-8701
Conference Code:
6313424325
<<OASIS WSDM [OMod]
call>>
-- 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]