This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.scrm-wg/wiki/DSP0226 at Thu, 03 Nov 2022 00:16:55 GMT SourceForge : View Wiki Page: DSP0226

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Wiki Pages Project: scrm-wg     Wiki > DSP0226 > View Wiki Page
wiki1496: DSP0226

Standard

1. The name of the specification

Web Services for Management (WS-Management)

2. A short statement (<100 words) of the purpose and function of the specification

This specification describes a general SOAP-based protocol for managing systems such as PCs, servers, devices, Web services and other applications, and other manageable entities.

3. The version number (or other distinct identifier) and date of the most recently approved version of the specification.

Version 1.0 Preliminary April 5, 2006

4. If the specification is part of a group of explicitly related specifications from the same source, the name of the group of specifications.

The Web services architecture is based on a suite of specifications that define rich functions and that may be composed to meet varied service requirements. A crucial application for these services is in the area of systems management. To promote interoperability between management applications and managed resources, this specification identifies a core set of Web service specifications and usage requirements that expose a common set of operations central to all systems management. This comprises the abilities to

• Get, put (update), create, and delete individual resource instances, such as settings and dynamic values,

• Enumerate the contents of containers and collections, such as large tables and logs,

• Subscribe to events emitted by managed resources, and

• Execute specific management methods with strongly typed input and output parameters.

In each of these areas of scope, this specification defines minimal implementation requirements for conformant Web service implementations. An implementation is free to extend beyond this set of operations, and may also choose not to support one or more areas of functionality listed above if that functionality is not appropriate to the target device or system.

5. URI for the normative text of the specification

http://www.dmtf.org/standards/published_documents/DSP0226.pdf

SOURCE

6. The name of the SDO that generated/authored/hosted the specification.

Distributed Management Task Force (DMTF)

7. URI for the SDO

http://www.dmtf.org

8. The level of approval that the SDO has conferred on the specification as described by the SDO's process.

Preliminary

9. The language or languages in which the specification is available.

US English

SUBJECT

10. Which of the ITU-T TMN FCAPS model layers does the specification's functionality address?

(http://en.wikipedia.org/wiki/FCAPS, http://www.futsoft.com/pdf/fcapswp.pdf) Fault Management: Fixing broken resources. Configuration Management: Controlling a resource's operational parameters. Accounting Management: Recording and analyzing resource use. Performance Management: Controlling speed and efficiency of resource use. Security Management: Controlling access to resources.

12. Where does the specification directly operate, as among the layers defined in the ISO Open System Interconnect (OSI) model?

(http://www.looselycoupled.com/opinion/2003/saruk-osi-infr0905.html ) Physical layer Data link layer Network layer Transport layer Session layer Presentation layer Application layer.

13. Which of the following (CIM based) functional areas does the model of the specification address?

(http://www.dmtf.org/standards/cim/)

Policy Management Infrastructure Physical Networks Logical Networks Physical Systems Logical Systems Physical Devices Logical Devices Physical Storage Logical Storage Operating Systems Databases Application Servers Applications Users Security Support


OPTIONAL

14. The level of approval of the specification in this generic lifecycle taxonomy:

Proposed work Contributions received Preliminary SDO draft Initial public review Final approval Product availability End-of-life (superseded, withdrawn, etc.)

15. URI for the applicable SDO's patent and copyright rules, if any, applicable to development and use of the specification.

http://www.dmtf.org/about/policies/

16. URI for the SDO's posting location, (if any) for notices from participants or individuals regarding claims under the rules stated under number 15.

http://www.dmtf.org/about/policies/disclosures/

17. Interoperability, conformance, or certification test activity for the specification (by owner name or URI).

18. Known implementations of the specification (by owner name or URI).

http://www.dmtf.org/about/marketplace/

19. A list (or URI pointer to same) of the other specifications* that are normatively referenced in the specification.

20. A list (or URI pointer to same) of the other specifications* that are referenced in the specification (except the ones listed under number 19).

21. A list (or URI pointer to same) of other specifications* with which the specification may (speculatively) interoperate or act in complementary, compatible fashion.

22. A list (or URI pointer to same) of other specifications* similar to this specification. (Whether or not substitutable.)

  • : Please identify where reference specification is within SDO member organizations or not and current level of approval as the level of question.
 




The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.scrm-wg/wiki/DSP0226 at Thu, 03 Nov 2022 00:16:55 GMT