RE: [wsdm] Terminology in the requirements

["Mark Potts" <mark.potts@talkingblocks.com>]

Andrea...


Capabilities does not infer a distinction between information and action
The manageability capabilities are all exposed through a manageability
interface 
that can include actions that affects the management of the resource and
information 
made available by the resource to a manager for management.

> <arw> No, not restricted to configuration of manageability 
> but about the resource AND the interface.  I was referring to 
> the fact that some interfaces cannot support all aspects of 
> getting/setting/invoking the information/actions from the 
> resource.  We found this in the DMTF work - for example, 
> using the CIM/WBEM interface, we could do xyz, but using the 
> Acme interface, you could only do a subset (x and y only).  

Hmmm... Whether the interface is "complete" or "restricted" due to 
the resources own capabilities is simply the scope of the manageability 
capabilities.

> <arw> I would like to see more specific definitions with 
> examples, including capability :-).  When you say that we 
> should distinguish between mgmt info and manageability do you 
> mean - manageability is the information exposed, and 
> operational and provisional actions that are supported, via 
> one or more interfaces??  If so, I agree that mgmt info and 
> manageability are not the same - but that manageability needs 
> some level of mgmt info.

No .. I'm making a distinction that is critical to management especially
in 
Web and Grid environments where management resources are very loosely
coupled 
and discovery and self description are key facets in the architecture. 
There are two sets of information  - there is information about 
the resource specific to manageability  - e.g. current state, last
transition, 
and then there is meta information about the manageability - what are
the 
supported states and what is the state model for the resource.

> 
> Thoughts?
> 
> Mark/
> 
> 
> > -----Original Message-----
> > From: Andrea Westerinen [mailto:andreaw@cisco.com]
> > Sent: Wednesday, August 13, 2003 6:07 PM
> > To: Mark Potts; 'Ellen Stokes'; homayoun@hp.com
> > Cc: 'Sedukhin, Igor S'; wsdm@lists.oasis-open.org
> > Subject: RE: [wsdm] Terminology in the requirements
> > 
> > 
> > Mark, I agree in general with the definitions, except for one.... 
> > "manageability capabilities".  We have found in the DMTF that 
> > capabilities and current choices/configuration are 
> different things. 
> > For example, your manageability information may have the 
> capability to 
> > be input or output in 4 different languages, but your current 
> > configuration is to use English.
> > I would rather use the term "manageability information" to 
> > convey properties, operations and events that can be exposed 
> > - and then change the definitions as follows:
> > 
> > Manageable implies that a resource can effectively be managed by a 
> > Manager (no change)
> > 
> > Manageability implies the existence of a sufficient set of 
> > manageability INTERFACES and INFORMATION such that a resource is 
> > manageable (removed the word, capabilities)
> > 
> > Manager is the consumer of manageability INFORMATION offered by 
> > resources, THROUGH ONE OR MORE MANAGEABILITY INTERFACES 
> (removed the 
> > word, capabilities, and added the phrase regarding interfaces)
> > 
> > Manageability INFORMATION INCLUDES properties, operations 
> and events 
> > exposed for the management of a resource (removed the words, 
> > capabilities include)
> > 
> > Management is the utilization of the manageability INTERFACES TO 
> > OBTAIN MANAGEABILITY INFORMATION by a Manager (removed the word, 
> > capabilities)
> > 
> > Managed implies that a resource's manageability INFORMATION IS 
> > actively being utilised by a Manager (removed the words, 
> capabilities 
> > are)
> > 
> > Manageability interface is the interface through which 
> manageability 
> > INFORMATION IS exposed (removed the words, capabilities are)
> > 
> > Manageability endpoint is the address at which the manageability 
> > interface can be accessed (no change)
> > 
> > MANAGEABILITY CAPABILITIES DESCRIBE THE POSSIBLE MANAGEABILITY 
> > INTERFACES, THEIR CONFIGURATION AND INFORMATION THAT CAN BE EXPOSED 
> > THROUGH THESE INTERFACES (new)
> > 
> > Andrea
> > 
> > -----Original Message-----
> > From: Mark Potts [mailto:mark.potts@talkingblocks.com]
> > Sent: Thursday, August 07, 2003 10:18 PM
> > To: Mark Potts; Ellen Stokes; homayoun@hp.com
> > Cc: Sedukhin, Igor S; wsdm@lists.oasis-open.org
> > Subject: RE: [wsdm] Terminology in the requirements
> > 
> > 
> > Sorry... The terminology doesnt read as well with the HTML 
> formatting 
> > stripped from the mail - so attached is the same mail in HTML.
> > 
> > 	-----Original Message----- 
> > 	From: Mark Potts 
> > 	Sent: Thu 8/7/2003 10:10 PM 
> > 	To: Ellen Stokes; homayoun@hp.com 
> > 	Cc: Sedukhin, Igor S; wsdm@lists.oasis-open.org 
> > 	Subject: RE: [wsdm] Terminology in the requirements
> > 	
> > 	
> > 	 
> > 
> > 
> > 
> 
> You may leave a Technical Committee at any time by visiting 
http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgrou
p.php