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] Requirements for Management Using Web Services

Hi Sanjeev,

Great comments. Find my response below:

> -----Original Message-----
> From: Sanjeev Kumar [mailto:sakumar@attbi.com]
> Sent: Tuesday, April 22, 2003 10:22 PM
> To: KUMAR,PANKAJ (HP-Cupertino,ex1)
> Pankaj,
> This is an excellent start! 

Thanks. I also see this as only as a start.

> Here are some of my comments, alongwith
> the appropriate context from your write-up -
> Management Interface Requirements Section
> Requirements on Web Services (generic):
> >      3. Web Services Identification
> Actually, this is more general - "Managed Resource Identification",
> since management products compliant with WSDM will manage resources
> other than web services as well. This is the first issue we need to
> agree on as part of a building block for the rest of the spec, in my
> opinion.

Completely agree. In fact, going back to my write up, I found the following
statement --
3. It should be able to uniquely identify a managed Resource and
   allow a manager to access other identification information such
   as vendor, version, operator etc.
And the managed resource is any entity, not just a Web service.

> >      9. Support for events
> Aren't existing message mechanisms sufficient for what we need? Maybe
> you can elaborate on this during the conf call tomorrow.

While working on an internal project we found that the event mechanism needs
to support the notion of publishers, subscribers, subscriptions,
notifications etc. The same abstractions that JMS has. Of course one could
build these using one-way and two-way SOAP messages, but still the
abstractions need to be worked out.

I would really like to talk about this in a conf. call.

> >      12. Discovery mechanisms
> Scalability Requirements:
> > 1. It should be possible to off-load certain kinds of processing/
> >    filtering at Agent to reduce network traffic.
> I think we should be more specific here, since this aspect deals a
> lot with operational/implementation issues. Possible kinds of
> filtering or work to be offloaded to the Agent: a) computation of
> derived statistics b) event co-relation (sequence and time-based)
> c) local root-cause analysis (??!!), d) ...

Agree. This needs more work. We got to come up with a mechanism by which
Manager and Agents can agree based on ids. and leave the details on the

> > 3. A Manager should be able to support a large number of
> >    Managed Resources.
> This is also subjective and "close" to operational/implementation
> aspects. What is the scale here - ten's, hundred's, thousand's? I
> think the ability to multiplex across ten's of "children" at the
> Manager and Agent level might be more appropriate. Also, we are not
> saying anything regarding the levels of hierarchy a product could
> support amongst the Manager -> Agent -> Managed Resource layers.
> Other views are welcome if I am off-base here.

This requirement short of bubbled up from an implementation based on
stateful protocol, which inherently doesn't scale. Also, the ability to
address a large number of managed resources in a single request (vs. each
request for each resource).

Some of these are protocol related issues.
> Also, it might be useful to add a section on "Usability" as well.
> One aspect I can think of right away for this is -
> - It should be possible to configure an operation on more than one
>   Managed Resource, rather than having to go through a configuration
>   step for each Resource.

Completely agree.

Once again, thanks for your great comments.

Best Regards,
Pankaj Kumar.
> Thanks!
> Regards,
> Sanjeev K.
> "KUMAR,PANKAJ (HP-Cupertino,ex1)" wrote:
> > 
> > Hi WSDM-TC Members,
> > 
> > To continue the discussion initiated by last week's presentation,
> > we would like to submit the attached writeup as starting point for
> > further discussion on "Management Using Web Services"
> > requirements. A subsequent submission will include a writeup on
> > "Management Of Web Services" requirements.
> > 
> > Winston, Heather,
> > 
> > Please add these documents to the TC agenda.
> > 
> > Best Regards, <<MUWS-Req.txt>>
> > Pankaj Kumar
> > Web Services management Organization,
> > HP OpenView, HP.
> > Tel: 1-408-447-4571
> > 
> >   
> --------------------------------------------------------------
> ----------
> >                    Name: MUWS-Req.txt
> >    MUWS-Req.txt    Type: Plain Text (text/plain)
> >                Encoding: quoted-printable

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