How to do a minimal 'smoke test' of Openwsman

About Openwsman

Openwsman is an open-source implementation of the WS-Management stack.

About the WS-Management stack

WS-Management is a resource management protocol, allowing operations like

• create
• delete
• search (enumerate)
• read (get)
• write (put)

on resources.

A resource is anything that has

• a type (class, identified by a resource path)
• a unique id (called "end point reference")
• properties (set of key, value pairs)

Primary use case

The primary use case for WS-Management is to transport Common Information Model (CIM) data.

CIM is used to represent and manage elements in an IT environment. Think of physical elements like Computers, Storage Media, Routers, or logical elements like Operating Systems, Processes, etc.

Putting the pieces together

Openwsman only provides WS-Management protocol capabilities. In order to serve CIM resources, it must talk to a cim-server (like sfcb or Pegasus)

A standard SUSE Linux Enterprise Server setup would look like this:

Providers for sfcb is any *-cmpi-* or cmpi-* package from here

Testing the pieces

Required packages

• openwsman-server - provides the openwsmand daemon
• sblim-sfcb - provides the sfcbd daemon
• sblim-cmpi-* packages, i.e. sblim-cmpi-base

In theory, openwsmand and sfcbd could run on different systems. However, this has no practical relevance.

For command line testing of both daemons, these packages should be installed

• wsmancli - command line client to 'talk' WS-Management to openwsmand
• wbemcli - command line client to 'talk' wbem-http (aka cimxml)

Configurations