pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.6.12.2 and 1.9

version 1.6.12.2, 2006/07/12 19:53:48

version 1.9, 2007/01/09 01:58:56

Line 1

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<head>

<style>

st1\:*{behavior:url(#ieooui) }

</style>

<style>

<!--

/* Font Definitions */

Line 949

Line 953

{margin-bottom:0in;}

-->

</style>

<style>

/* Style Definitions */

table.MsoNormalTable

Line 964

Line 969

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype>

<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml>

Line 1002

Line 1010

</head>

Pegasus

Enhancement Proposal (PEP)<o:p></o:p>

PEP #: 287

Title: Release

Notes for OpenPegasus 2.5.1 and Subsequent 2.5 minor releases

Notes for OpenPegasus 2.6.0

Version: 1.7

Created: <st1:date year="2004" day="23" month="3">1 March 2006</st1:date>

Created: <st1:date year="2004" day="23" month="3">19 December 2006</st1:date>

Authors: Karl Schopmeyer

Status:  draft

Version History:

<tbody>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

</tr>

1.0<o:p></o:p>

</td>

<o:p>  1 March

<o:p>  19 December

2006</o:p>

</td>

Karl Schopmeyer

</td>

Initial

Submission<o:p>

</o:p>

</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center">2 March 2006</td>

<td style="padding: 0.75pt;" align="center">Karl Schopmeyer</td>

<td style="padding: 0.75pt;">Fix editorial errors</td>

<td style="padding: 0.75pt;" align="center" height="21">20 December 2006</td>

<td style="padding: 0.75pt;" height="21">Remove functionality description section</td>

</tr>

<td style="padding: 0.75pt;" align="center">20 March 2006</td>

<td style="padding: 0.75pt;" align="center">Karl Schopmeyer</td>

<td style="padding: 0.75pt;">Incorporate comments from

<td style="padding: 0.75pt;" align="center" height="21">2 January 2007</td>

Review week of 12 March 2006</td>

</tr>

<tr>

<td style="padding: 0.75pt;" height="21">Fix comments from 1.1. Note comments are in

<td style="padding: 0.75pt;" align="center">22 March

Red in text for now.</td>

2006</td>

<td style="padding: 0.75pt;" align="center">Karl

Schopmeyer</td>

<td style="padding: 0.75pt;">Incorporate comments form

Review 21 March 06 and bring into line with Feature status page</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center">28 March

2006</td>

<td style="padding: 0.75pt;" align="center">Karl

Schopmeyer</td>

<td style="padding: 0.75pt;">Remove all statements

concerning status and point to the Feature Status Page.</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center">28 March

2006</td>

<td style="padding: 0.75pt;" align="center">Karl

Schopmeyer</td>

<td style="padding: 0.75pt;">Remove references to

status "experimental" for certain features</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center">28 March

2006</td>

<td style="padding: 0.75pt;" align="center">Karl

<td style="padding: 0.75pt;" align="center" height="21">3 January 2007</td>

Schopmeyer</td>

<td style="padding: 0.75pt;">Typos - Approved by

architecture group</td>

<td style="padding: 0.75pt;" height="21">Clean up remaining comments and remove

comment markers.</td>

</tr>

<td style="padding: 0.75pt;" align="center">12 July

2006</td>

<td style="padding: 0.75pt;" align="center">Karl

<td style="padding: 0.75pt;" align="center" height="23">8 January</td>

Schopmeyer</td>

<td style="padding: 0.75pt;">Update to reflect Pegasus

<td style="padding: 0.75pt;" align="center" height="23">Karl Schopmeyer</td>

2.5.2 release</td>

<td style="padding: 0.75pt;" height="23">Move approved PEP, reflecting

changes to 1.3 for approval</td>

</tr>

</tbody>

</table>

<o:p> </o:p>

Abstract: This document defines the release notes for the 2.5.1

and subsequent 2.5 minor releases of the Pegasus CIM Server. <a href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35" target="_self">

Abstract: This document defines the release notes for the 2.6.0 release of the Pegasus CIM Server.

The purpose of this PEP is simply to summarize the characteristics of this

release, point to other documentation that defines the release in more detail,

and provide additional information about this release that is not available in

the other Pegasus documentation. <a href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35" target="_self">

</a>

<h2 style="margin-bottom: 1px;"><o:p> Contents

</o:p></h2>

<ol>

<li><a href="#Availability_of_this_Release_">Availability of this Release</a></li>

<li><a href="#Functionality_of_This_Release">Functionality of

This Release</a></li>

<li><a href="#Functionality_of_This_Release">OpenPegasus Functionality of This

Release</a></li>

<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship

to CIM/WBEM Standards</a></li>

<li><a href="#Supported%20Platforms">Supported

Platforms</a></li>

<li><a href="#Supported Platforms">OpenPegasus Supported Platforms</a></li>

<li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance

with DMTF Specifications</a></li>

<li><a href="#Changes%20in%20This%20Release">Changes

in This Release</a></li>

<li><a href="#PEGASUS Bugs">OpenPegasus Bugs</a></li>

<li><a href="#PEGASUS%20Bugs">PEGASUS

Bugs</a></li>

<li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">Pegasus

OpenPegasus Release Control and Version Definition Documentation</a></li>

Release Control and Version Definition Documentation</a></li>

<li><a href="#General%20Documentation">General

Documentation</a></li>

</ol>

<h2>Availability

of this Release</h2>

This release is available in a number of forms including:

<ul>

<li>Source release in both ZIP and TAR formats. These can be

<li>Source release in both ZIP (and ZIP EXE) and TAR formats. These can be

downloaded from the OpenPegasus Web

site at <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a></li>

site at <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li>

<li>OpenPegasus 2.5.x binaries are available for Red Hat Enterprise

Linux 3.0 and 4.2 and SUSE LINUX Enterprise Server 9.0. A Source RPM is

<li>OpenPegasus  binary and source RPMs on the OpenPegasus web

also available that can be used to build binaries for most

site.. The source RPM is  available on the OpenPegasus web site that can be used to build binaries for most LSB-compliant RPM-based Linux distributions and versions.</li>

LSB-compliant RPM-based Linux distributions and versions.</li>

<li>The Pegasus CVS. The CVS tags representing this release and

<li>The Pegasus CVS repository. The CVS tags representing this release and

subsequent snapshots that are made available in the Pegasus CVS are

defined on the OpenPegasus CVS repository web page (see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

CVS page</a> for information) using the tags defined on the <a href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release

snapshots page</a>.</li>

</ul>

The instructions for acquiring the released code are on the <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus

WEB site</a>.

Installation instructions are part of the README in the root of the

Pegasus source

tree.</div>

tree.

</div>

<h2>Functionality of This Release</h2>

<h2>OpenPegasus Functionality for This Release</h2>

Pegasus overall status by release is defined by  a

<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>

that is available on the OpenPegasus web site .  That

that is available on the OpenPegasus web site .  That web page shows the

web page shows the Pegasus users and developers

Pegasus users and developers the status of the various features found in Pegasus

the status of the various features found in Pegasus using a simple color coded

using a simple color coded key (white, red, yellow, green) and a description of

key (white, red, yellow, green).  Pegasus 2.5.1 is a minor release, extending Pegasus 2.5.0 in selected

each feature.Pegasus 2.6.0

areas primarily for bug fixes.  However, there were some signification

is a major release, extending Pegasus 2.5 in selected

changes in the feature status for selected functions in 2.5.1 (moving selected

areas as described in the Pegasus  PEP defining this release (see PEP 218)

functions closer to production-capable status). Pegasus 2.5.2 is a minor release

.

providing changes that have been defined through pegasus bugs.The following paragraphs list the functionality in this release.   In many cases these features  and interfaces

are conditionally compiled with special environment variables.

The major areas of development for this release  were as follows. For

more information access the documented PEP:

provides more detailed information on how to enable

functionality that is conditionally compiled in this release.

NOTE: For current information and history on the status of each feature,

Table of Major Changes for this Release

please access the

OpenPegasus Feature Status WEB Page</a>.  Please see

<TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666

the Feature status page for the quality/status of each feature because not all

borderColorLight=#cccccc border=1>

of the features listed below are production ready.

<TBODY>

<h3>CIM Server Functionality</h3>

<h4>CIM Operations over HTTP support</h4>

<TH bgColor=#E0E8EF>Description</TH>

<ol>

<TH bgColor=#E0E8EF>Posted PEP Version</TH>

<li>Class Operations (getClass, deleteClass, modifyClass,

</TR>

enumerateClass, enumerateClassNames)</li>

<li>Qualifier Operations (getQualifier, setQualifier,

deleteQualifier) </li>

<TD align="left">Embedded Instance Support in Pegasus</TD>

<li>Instance Operations (getInstance, deleteInstance, modifyInstance,

<TD>

enumerateInstance, enumerateInstanceNames, getProperty,

setProperty)</li>

1.3</a>

<li>Association Operations (references, referencenames,

</TD>

associators, associatornames)</li>

</TR>

<li>Methods Operations (invokeMethod)</li>

<li>Query operation - Support for ExecQuery was added in 2.4 with

WQL as query language and is defined in PEP 119. This feature is

<TD align="left">Providing SMI-Server Profile through OpenPegasus</TD>

considered at alpha quality because it has only been contributor

<TD>

tested.  Additional tests have been added in 2.5 for ExecQuery. Pegasus

today does not support the ExecuteQuery operation defined as the Query

1.5.1</a></TD>

operation for CQL.

</TR>

</li>

</ol>

</blockquote>

<TD align="left">Incorporation of CIM_Error into OpenPegasus Infrastructure</TD>

</div>

<TD>

<h4>Indication Processing</h4>

1.4</a>

<ol>

</TD>

<li>Process indications - Process indications are operational in

</TR>

the

Server.  This includes support

for subscriptions, filters, and indication handlers, the provider API

<TD align="left">Language Interfaces</TD>

for

<TD>

indications and the CIMXML indication handler.</li>

<li>Lifecycle indications - With the support for embedded objects,

1.0</a>

lifecycle indications (ie. those

</TD>

classes of indications derived from CIM_ClassIndication and

</TR>

CIM_InstIndication) can now be created. Pegasus 2.5 provides some

enablement for the generation of lifecycle indications. For more

details, refer to

<TD align="left">Reducing Pegasus Code size and static memory usage</TD>

<TD>

</ol>

<h4>Query Language</h4>

1.3.1</a>

Pegasus includes the  WQL  query language which is implemented and

</TD>

used for filters and in version 2.4 for execQuery.

</TR>

CQL Stage 1 has been added for Pegasus 2.5.  PEPs 138, 193, 205

combine to describe the CQL  functionality supported.

<TD align="left">Indication Subscription Management</TD>

<h4>Object Normalization</h4>

<TD>

The Object Normalizer is an entity introduced in Pegasus 2.4 that

ensures

1.2</a>

objects delivered from providers are complete and accurate. Two major

</TD>

issues were identified with the initial implementation: 1) the Object

</TR>

Normalizer droped instances it considered bad, and 2) the Object

Normalizer code slowed performance. These issues are now addressed by

moving the Object Normalizer from the Dispatcher to the Response

<TD align="left">Audit Logging</TD>

Handler (or equivalent) and optimizing the existing implementation. The

<TD>

move allows errors to be reported to the provider at the point of

delivery and ensures that only a single copy is made to preserve the

1.4</a></TD>

CIMOM/provider boundary.

</TR>

<h4>Embedded Object Support</h4>

Pegasus 2.5 provides embedded object support. The proposed solution

is restricted to the following:<ul>

<TD align="left">SSL Certificate Management Command Interfaces</TD>

<li>The only representation for embedded objects supported by this

<TD>

PEP is CIM-XML (i.e. id does not support MOF encoded objects). </li>

<li>CIMObject is implemented as a new CIMValue type. This type will be used

1.2</a></TD>

internally to represent embedded objects. When externalized (via

</TR>

CIM-XML) these objects will be converted to strings representing valid

INSTANCE or CLASS elements, in accordance with the CIM Infrastructure

Specification.  Embedded instances will also carry the

<TD align="left">CMPI 2.0 Currency</TD>

EmbeddedObject attribute with

<TD>

the value "object", as specified by CR Interop-00217.001.

</li>

1.1</a>

</ul>

</TD>

<h3>Pegasus Repositories

</TR>

</h3>

</blockquote>

<TD align="left">SLP enhancements for Pegasus 2.6</TD>

<TD>

<h4>Schema Repository</h4>

1.5</a></TD>

By default, Pegasus uses an XML-based

</TR>

schema repository. A binary encoding option is also available for the repository.

<TD align="left">Repository Archive</TD>

Note: Users may experience an incompatibility moving a binary repository from

<TD>

Pegasus 2.4 to 2.5. In Pegasus 2.5, measures have been taken to improve

the ability to maintain compatibility with subsequent releases. (See bugzilla 3642 for details.)</div>

1.1</a>

Further information on the use of the binary repository is in the

</TD>

readme.binaryrepository file in the Pegasus source root directory.

</TR>

<h4>Instance Repository</h4>

</TBODY>

The

</TABLE>

Pegasus schema repository may also be configured to hold instance

</UL>

data.  Although instances may be place in the

</html>

repository

The status of several components of Pegasus functionality change status

it was not designed as a

between Pegasus versions. <a name="comtag_116">Features that

high volume data store.

have changed status can be identified by a change in color from the previous

<h4>Compressed Repository Feature</h4>

release to this release</a> on the

A compressed repository

<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>.

feature has been added for

pegasus 2.5 that compresses the repository written to disk. This allows

Finally, a significant number of internal changes and corrections were made

the

under the control of the Pegasus bugzilla bug system. See the bug section below

repository to be as much as 50% smaller on disk. It uses an external

for more information.

compression library (zlib) and has been tested with zlib 1.2.2. This

feature is

documented in PEP 214 and also in a Readme

(readme.compressed_repository). Note

that the tests for this feature are in the test suite but not

activated for

automatic tests.Further information on the use of the compressed

repository is in the readme.compressedrepository file in the Pegasus source

root directory.

<h4>Pegasus MOF Compilers</h4>

Pegasus implements a MOF compiler that can operate either at the

client

interface to the Pegasus CIM Server (cimmof)

or directly interfacing with a CIM

repository (cimmofl).

The direct interface compiler is used primarily to provide an

initial

class/instance repository. WARNING:

The use of cimmofl

to manipulate instances in the repository bypasses any provider that is

registered to serve these  instances and simply installs the

instances in the

instance repository; this may result in 1) bad data in the repository

if there are registered providers, 2) corruption of the repository if

the CIM Server is running or, 3) MOF data that is loaded but not

available until the server is stopped and restarted in some

cases.  Use of cimmofl in general is

discouraged and particularly  to manipulate

instances served by a registered providers (ex. Provider registration).

<h3>Security Considerations</h3>

OpenPegasus 2.5 (and

prior versions) contains several mechanisms to perform authorization, but none

of these authorization checks are performed by default.

By registering any provider which fails to do appropriate authorization

checks, the consequences may include information leakage, data

corruption, or unintended elevation of privilege. Please ensure that

one of the following mechanisms is used to ensure appropriate access to

your systems and data:

1. Only install/register providers which perform authorization

appropriate for your environment.

<div style="margin-left: 40px;">a. For providers, this may include registering to

'Run-as-requestor' (not available prior to Pegasus 2.5) and/or

performing authorization checks within the provider.

b. For administrators, ensure that the providers you have registered in

your environment have performed sufficient authorization checks. Also,

monitor announcements of security defects in those providers and follow

the recommendations in those announcements as soon as possible.

c. For distributors of Pegasus or providers, ensure that the providers

you are shipping have performed appropriate authorization checks, and

relay announcements of discovered security defects to your users.

</div>

2. Restrict users with

access to Pegasus to a specific authorized user group of trusted

individuals.

3. Namespace authorization is also available.

For administration issues please refer to

the SSL Admin Guide found in the source repository at:   pegasus/doc/PegasusSSLGuidelines.htm

<h4>Server Security</h4>

<li class="MsoNormal" style="color: black;">Basic Authentication

(Note that Digest based security is not implemented in Pegasus)</li>

<li class="MsoNormal" style="color: black;">PAM authentication <o:p></o:p></li>

<li class="MsoNormal" style="color: black;">SSL support - SSL is

implemented in Pegasus using the OpenSSL

libraries. Pegasus does not provide the OpenSSL

libraries but SSL can be used on any platform supported by OpenSSL. .   This release of Pegasus was tested

with multiple versions of  OpenSSL versions

0.9.7 and 0.9.8.   Effective with Pegasus 2.5.1 the Open SSL version

0.9.6 is no longer supported. See <a href="http://www.openpegasus.org/pp/uploads/40/Application%20Data/Microsoft/Word/www.openssl.org">openssl.org</a>

for OpenSSL release information<o:p>.</o:p></li>

<li class="MsoNormal" style="color: black;">SSL levels - SSLv3

and TLSv1 by default. SSLv2 is

disabled by default and only enabled by a compile time option.

See<a href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502">

PEP 237</a> for details on

configuration.

</li>

</ol>

<h4>Client Security</h4>

Certificate management

and User-based certificate authentication . A new control provider and CLI for certificate management tasks. It expands upon the existing SSL

client verification support by providing a robust solution to managing

client certificates and certificate revocation lists via standard CIM

operations. It allows certificates to be associated with particular

system users for enhanced authorization capabilities.

CN/ Host

name checks are not performed as a function of SSL or client libraries

and are the responsibility of the client to implement on their

own.  See the SSL guide found in the /pegasus/doc directory for

more details on client security.

Note: WBEM clients are responsible for SSL

certificate verification using Pegasus and/or SSL libraries as

appropriate. Consequences of not doing so include leakage of

authentication credentials to unauthorized parties.

<h4>Platform Management Functions</h4>

<li class="MsoNormal" style="color: black;">Configuration through

the defined configuration parameters (cimconfig) and server command

line options.  NOTE: When installed

as a service on Windows, setting the run-time config option

enableAuthentication to true can result in improper operation of the

SLP

provider and other providers. In order to circumvent this defect, an

Administrator should change the user that the service runs under from

the Local

System user to a local, privileged user (e.g. Administrator).

See bugzilla 4142 for details. <o:p></o:p></li>

<li class="MsoNormal" style="color: black;">Daemon/service

operation of the Pegasus CIM Server on all supported platforms<o:p>

with the exception of HP OpenVMS.</o:p></li>

<li class="MsoNormal" style="color: black;">Operation statistics

capture using the CIM_StatisticalData classes in

the DMTF Interop model. This

function is considered alpha quality and conditionally compiled.

</li>

<li class="MsoNormal" style="color: black;">Multiple

pluggable provider managers.  Provider managers are provided for

the Pegasus C++ provider interface, the CMPI C provider interface and

an alpha quality Java provider interface (JMPI).</li>

<li class="MsoNormal" style="color: black;">Platform Globalization

- Pegasus includes support for unicode data transfers and includes a

mechanism for message support in multiple languages using the open

source ICU libraries (<a href="http://oss.software.ibm.com/icu/">http://oss.software.ibm.com/icu/</a>).</li>

<li class="MsoNormal" style="color: black;">Out-of-process providers - See PEP 072 for more information on use of

this feature </li>

<li class="MsoNormal" style="color: black;">Shared class namespaces - See PEP 129 for more information on use of this feature.</li>

<li class="MsoNormal" style="color: black;">Remote providers for

the CMPI provider interface - See PEP 130 for more

information on use of this feature.</li>

</ol>

<h4>SLP Discovery</h4>

SLP support is included but is conditionally compiled in or out on

a platform basis. <a href="http://www.openpegasus.org/pp/uploads/40/8502/PEP200_RecommendedReleaseOptions.htm">

PEP 237</a> describes the  environment variable (PEGASUS_ENABLE_SLP) to

enable or disable this code.  Effective with Pegasus 2.5.1, support has

been added for the use of OpenSLP as the Service Agent (SA) in addition to the

internal to the Service Agent.  This is controlled through an additional

environment variable (PEGASUS_HAS_OPENSLP)  Once compiled, SLP

support is enabled with the slp configuration parameter (slp=true). SLP

support includes an SLP service agent in the Pegasus CIM sever (either the

internal agent or OpenSLP)  and

generates SLP advertisements compatible with the DMTF slp template

specification. The SLP support also includes  extensions to the

CIM Client libraries to execute SLP User Agent requests and analyze the

results (note that these interfaces are not yet part of the Pegasus

public SDK).

Note: Pegasus on Windows is built with SLP support on by default.

<h4>Indication Handlers</h4>

<h5>System Log Indication Handler

</h5>

The SysLog Indication Handler is a new

for 2.5

type of Indication Handler which allows CIM Indications to be delivered

to the system syslog file. It has following features:

Each syslog file entry has a tag 'CIM Indication' to distinguish

an entry made by Syslog Indication Handler.

If a subscriber includes PerceivedSeverity property in the SELECT

list of the filter condition for the indication, the PerceivedSeverity

will be mapped to syslog error severity. Otherwise, syslog error

severity 'LOG_INFO' is used.

See

<a href="http://www.openpegasus.org/pp/uploads/40/7165/PEP206-SystemLogIndicationHandler.htm" style="color: blue; text-decoration: underline;">PEP

206</a> for details.

<h5>Email Indication Handler

</h5>

The Email Indication Handler is a new

for 2.5

type of Indication Handler that allows CIM Indications to be delivered

to a specified e-mail address.   See

<a href="http://www.openpegasus.org/pp/uploads/40/7166/PEP207-EmailIndicationHandler.htm" style="color: blue; text-decoration: underline;">PEP

207</a>  for details.

</blockquote>

<h4>Pegasus Provider Interfaces</h4>

Pegasus is designed to support multiple Provider Managers to allow

multiple provider interfaces to the CIMOM.  The two default

provider managers are the Pegasus C++ Interface and Common

Manageability Programming Interface (CMPI) Interface.

<h5>C++ Provider Interface</h5>

This is the original

interface defined for OpenPegasus Providers.  It provides an interface

for both operations and indications. Many of the sample and test providers are

written to this interface.  This interface includes a callback into the

CIMOM (CIMOMHandle).

<h5>CMPI C interface Provider Manager<o:p></o:p></h5>

Pegasus 2.5 includes

a provider manager for the CMPI C interfaces. This C interface is the

result of a project by the IBM SBLIM team (see 

http://sblim.sourceforge.net) and is written to the Common

Manageability Programming Interface, which is an OpenGroup standard.

The CMPI

specification is available at:

http://www.opengroup.org/bookstore/catalog/c051.htm. This provides a

standardized C level interface for creating providers that can be

registered with the Pegasus CIM Server in the same manner as the

current C++ providers.  The

ability for CMPI providers to do user authorization is now available in

Pegasus 2.5.1.

Information on writing providers with the CMPI interface is available

in the specification today (see above) and in the following documents

(http://sblim.sourceforge.net/whitepaper.html and

http://sblim.sourceforge.net/presentations.html) and readme.cmpi in the

Pegasus source root directory.

NOTE: See the Feature status page

for exact status of the CMPI provider manager for different Pegasus

platforms.

<h5>JMPI Java Interface Provider Manager</h5>

Pegasus

includes a provider manager for Java

provider interfaces based on the SNIA provider interface

definitions.  This provider manager is  considered alpha

quality and is not compiled in the default build.   See

readme.jmpi in the Pegasus source root directory for more information.

</blockquote>

<h3>    Providers</h3>

<div style="margin-left: 40px;">New for 2.5 is the ability of Providers

to run out of process at

request user- level and running CMPI providers remotely or out of

process space.

Administrators should check the providers to

ensure that the provider vendor

has made use of available authorization capability.

</div>

There are a number of providers available

in the Pegasus release.

This includes providers in the following categories:

<h4>Pegasus Internal Providers</h4>

Pegasus provides a set of "internal" providers that have direct

access to the CIMOM for information and provide information and

services to support the CIMOM and its administration.    The

providers in this category are mostly defined in the directory

src/pegasus/controlproviders and include support for the following

classes:

<ul>

<li>DMTF Interop classes including __Namespace,  CIM_Namespace, CIM_ObjectManager,

CIM_CommunicationMechanism, and

CIMOMStatistics.</li>

</ul>

<h4>CMPI Remote Providers</h4>

Pegasus includes an support for

running CMPI providers to be run on remote systems without the need for

an extra CIMOM. It uses a special proxying provider to relay requests

to a remote location using so-called communication layers. The remote

side has to start a CMPIRDaemon process, which accepts remote requests

and passes them on to CMPI style providers.<h3>

Generic Providers</h3>

These are providers that support multiple pegauss platforms and include the Generic OperatingSystem provider. See

the

directory src/Providers/generic.

<h4>Test/Sample Providers</h4>

See the directories src/Providers/TestProviders

and src/Providers/sample for more

information about test and

sample providers.

<h4>Managed System Providers</h4>

ComputerSystem, DNSAdmin,

DNSService, Operating System, Process,

Processor. For

more information on these providers see the documentation for each

provider in

the directory src/Providers/ManagedSystem

<h4>Server Statistics Provider

</h4>

CIM Server statistics, based on the DMTF 'CIM_StatisticalData' class,

are implemented in this release. The statistics gathering is compiled

by default but it is disabled through a property in the singleton

CIM_ObjectManager class. It may be enabled or disabled by performing a

ModifyInstance operation on the 'CIM_ObjectManager instance

in the 'PG_InterOp' namespace to set the GatherStatisticalData property

to 'true' or 'false'. This property setting is persistent across CIM

Server restarts. A statistics display test tool, cimperf, is available

from the Pegasus CVS repository. <h4>SLP Provider</h4>

This provider acts as the definer of

SLP information for SLP registration and also controls the Pegasus SLP

Service Agent. It is treated as a normal provider rather than a control

provider because it does not use internal functions of the CIMOM to

generate any of its information today. (conditionally compiled today)

</blockquote>

<h2>Pegasus Indication Listeners</h2>

The generic components for a CIM Listener and a

listener API are operational.  This includes the functions for

HTTP, XML indication input and response, and consumers of indications.

This code can be used to define a separate listener package and is used

as an indication listener in the Pegasus server.

Pegasus includes 3 separate Indication Listeners.

<h3>Embedded CIMListener</h3>

This listener is embedded in the CIMServer and allows the

server to accept indications and route them.

<h3>Standalone Static CIMListener</h3>

This is a standalone listener that combines the functions

of listener and consumer into a single element.

<h3>Standalone Dynamic Listener</h3>

Pegasus 2.5

includes a new standalone dynamic listener that is separate

from the current standalone CIMListener and the ExportServer listener

in the CIM server.

The use model that this listener fits is the following:

<ul>

<li> The listener may be packaged as

part of the CIMOM or it may be packaged independently as part of

another application. </li>

<li> Consumers

are developed independently of the listener and may be shipped with the

listener or added to an installed listener at a future time. </li>

</ul>

This

dynamic listener provides a solution for the above use model. It

is essentially a lightweight, pluggable listener that

provides a small set of management features. The DynamicListener can be

run inside a daemon or a service. It is easily configurable and

bypasses traditional registration procedures.  See

<a href="http://www.openpegasus.org/pp/protected/upreviews/20/1303/PEP195_CIMListenerEnhancementsv1_6.htm" style="color: blue; text-decoration: underline;">PEP 195</a>  for

details.

</blockquote>

<h3>CIM_Schema</h3>

The default CIM_Schema loaded with this

release is

the DMTF CIM 2.9, final release.  In addition, Pegasus includes

a number of

local classes defined for Pegasus.  These are defined in the pegasus/Schemas

directory.   There are also a

number of older schema available in the CVS.  Further, the CIM 2.10 and CIM

2.11 schemas are available in the CVS repository and the Pegasus is compatible

with these Schemas.

The mechanism to install other schemas than the default is defined

in the mak/config.mak

NOTE: The CIM 2.5 schema is

maintained in the

CVS repository because it remains the basis for parts of the Pegasus

test

environment.

</blockquote>

<h3>Pegasus CIM Server Administration</h3>

<li class="MsoNormal" style="color: black;">cimuser

- Manage Pegasus CIM Server Users.<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">cimconfig

- Manage the Pegasus CIM Server configuration parameters.<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">cimauth

- Manage the CIM Server authorization characteristics. Today this is

authorizing users to namespaces.<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">cimprovider

- Manage information about the providers .</li>

</ol>

Server admin

note:

<div style="margin-left: 40px;">The default behavior for determining

the CIM server's HTTP and HTTPS ports has changed.  In previous

releases, any value in /etc/services would override a port explicitly

specified in the configuration.  The new order for determining the

CIM server's HTTP and HTTPS ports is as follows:

1) An explicitly specified port value takes precedence over any other

values.

</div>

<div style="margin-left: 40px;">2) If no port is specified, the value

in /etc/services is used.

3) If no value is specified in /etc/services, the default WBEM port is

used.

</div>

<h3>Information client tools</h3>

These tools provide information on the objects managed by the server.

<li class="MsoNormal" style="color: black;">tomof

- output classes and/or instance information from the Pegasus

repository in MOF or XML format.<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">dnsinfo

- Generate a set of standard information on the Domain

Name System (DNS) configuration from CIM Classes. Note that the

information generated is dependent on the information available from

providers and differs from system to system.<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">ipinfo

- Generates a set of standard information from the Network

Schema.  Information generated varies by system because of the

level of provider support.<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">osinfo

- Generate a set of standard information on the Operating System from

CIM Classes. Note that the information generated is dependent on the

information available from providers and differs from system to system<o:p></o:p></li>

</ol>

<h3>Test support Tools</h3>

<li class="MsoNormal" style="color: black;">Pegasus unit tests

(available through the "tests" option on the Pegasus make files) these

tests are defined throughout the Pegasus source tree typically in

"tests" directories.        <o:p></o:p></li>

<li class="MsoNormal" style="color: black;">The Pegasus test suite

(see the pegasus/tests directory)<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">TestClient

- Basic client for overall platform operation testing. <o:p></o:p></li>

<li class="MsoNormal" style="color: black;">wbemexec

- Test tool that sends/receives XML from XML input.<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">CLI - Command line

interface for Client commands.<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">Benchmark Test - A

benchmark test environment is provided which includes both a client and

provider component. See src/clients/benchmarkTest

for more information.</li>

<li class="MsoNormal" style="color: black;">cimperf  - Lightweight statistics are implemented for

the

client. The client statistics surfaces the elapsed time spent in the

client,

and the

elapsed time spent on the network between client and server.</li>

</ol>

<h3>Pegasus Interface APIs</h3>

Details of the Pegasus public interfaces for this release are listed

in PEP 209

available from the web site(<a href="http://www.openpegasus.org/pp/uploads/40/Administrator/My%20Documents/processes/www.openpegasus.org">www.openpegasus.org</a>).

That document is the authorative source for the list

of publicly supported Pegasus APIs.   The Client and Provider API were

originally frozen at the Pegasus version 2.1 release. The interfaces in the

release of Pegasus 2.1 are forward compatible to this release. Well-behaved

clients and providers compiled to the Pegasus 2.1 or 2.2 interfaces should be

compatible with this release without compilation.  There have been

extensions and new interfaces added for this release.

  The Pegasus public

interfaces includes the following major functions

<li class="MsoNormal" style="color: black;">Client APIs<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">Provider APIs<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">CIM Object and System

function APIs</li>

</ol>

In addition, there are other client interfaces which are not today

in the public SDK including:

<li class="MsoNormal" style="color: rgb(0, 0, 0);">CIM Listener APIs</li>

<li class="MsoNormal">CIM Listener

is a component that can be used to consume indications without a

dependency on the Pegasus CIMOM. In environments where no CIMOM is

running or a physical separation between the indication listener and

the CIMOM is desired, CIM Listener fits the bill. Still, there are

several enhancements that are necessary to make CIM Listener scalable. Enhancements were deemed significant

enough to propose a new listener that builds off CIMListener's

basic capabilities, yet allows the existing CIMListener to remain the

same.</li>

<ul>

<li>New CIM Listener now provides selective

indication delivery.

</li>

<li>New CIM Listener

keeps all consumer libraries in memory for the duration of its

execution.

</li>

<li>New CIM Listener

is now pluggable.</li>

<li>New CIM Listener

now provides reliable indication delivery.</li>

</ul>

<li class="MsoNormal" style="color: black;">SLP

Client (User Agent) APIs which are extensions to the Client APIs</li>

</ol>

<o:p> </o:p>

The APIs are

documented in

their respective header files and  in HTML documentation based on

the information

in the header files extracted with the doc++ tool will be available on

the

OpenPegasus web site.

WMI Mapper

The WBEM to WMI Mapper provides a way

to access

WMI data from Windows platform systems. It converts incoming XML/CIM

requests

to Microsoft WMI requests, executes the requests, converts the results

XML/CIM and returns the results to the client. WMI Mapper

receives an HTTP message containing the XML/CIM request. It decodes the

XML

message and extracts from the HTTP message header the user credentials

provided

on the connection (username and password). The WMI Mapper

authenticates these credentials, verifying if the provided credentials

have

access to the desired WMI data. This is done because the WMI Mapper runs as a service, logged on using an

account with

administrative rights (which has all access to WMI data). Because of

this, the

WMI Mapper impersonates the user

credentials provided

on the HTTP message to ensure that the calling user has rights to

browse WMI

data. Hence, ALL requests made to the WMI Mapper

MUST

contain user credentials.

<ol>

</ol>

<h2>Relationship to

<h2>OpenPegasus Relationship to

CIM/WBEM Standards</h2>

Pegasus was designed and implemented to comply with the DMTF

specifications The following table defines the level of the DMTF specifications

CIM/WBEM specifications The following table defines the level of the DMTF specifications

to which this version of Pegasus conforms today.

to which this version of Pegasus aims to conform today.

<tbody>

<tr>

<td bgcolor="#00ffff" width="33%">DMTF Specification</td>

<td bgcolor="#00ffff" width="33%">Specification Version</td>

</tr>

<tr>

<td width="33%">DSP 0004 CIM Specification</td>

<td width="33%">Version 2.2 with Addendum</td>

<td width="33%">DSP 0004 - CIM Infrastructure Specification</td>

<td width="33%">Version 2.3 Final, 4 October 2005</td>

</tr>

<tr>

<td width="33%">DSP 0200 - CIM Operations over HTTP</td>

<td width="33%">1.1, final, 6  January 2002</td>

<td width="33%">1.2.0, preliminary, 9 December 2004</td>

</tr>

<tr>

<td width="33%">DSP 0201 - Representation of CIM in XML</td>

<td width="33%">2.1, preliminary, May 2, 2002</td>

<td width="33%">2.2.0, preliminary, December 2004</td>

</tr>

<tr>

<td width="33%">DSP 0202 - CIM Query Language Specification</td>

<td width="33%">1.0.0, preliminary, 9 December 2004</td>

</tr>

<tr>

<td width="33%">DSP 0205 - WBEM Discovery using SLP</td>

<td width="33%">1.0, preliminary, 27 January 2004</td>

</tr>

<tr>

<td width="33%">WBEM SLP Template</td>

<td width="33%">DSP 0206 - WBEM SLP Template</td>

<td width="33%">1.0.0, Preliminary, January 2004</td>

</tr>

<tr>

<td width="33%">CIM Schema </td>

<td width="33%">2.9 Final, Jan. 2005</td>

<td width="33%">2.9 Final, Jan. 2005 ( default) 2.13.1 (available in

pegasus CVS)</td>

</tr>

</tbody>

</table>

<h2><a name="Supported Platforms">Supported

<h2><a name="Conformance with DMTF Specifications">Conformance Exceptions to

DMTF Specifications</a></h2>

It is a major goal

of the OpenPegasus project to both drive and utilize the DMTF CIM/WBEM

specifications.  However, today there are a number of known

differences. 

As of this release, some of the differences include the following:

<ol>

<li>Provider Registration - Pegasus supports registration

through a set of Pegasus Provider registration classes rather than

support the DMTF defined Provider Qualifier. Pegasus will not support

this qualifier in the future. See the readme for more information on

provider registration.  This is not a deviation from the specifications but

is a different method of registration than many CIM Servers and means that the

the provider qualifier is unused in Pegasus.</li>

<li> Indications -Today Pegasus supports process indications and

lifecycle indications when defined specifically by providers. Pegasus does not

support lifecycle indications if they are not defined by the provider or for

changes to CIM Classes.

For more information see the Pegasus CVS

file  <a name="comtag_137"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

<li>

IncludeQualifiers

option on Instance Operations

The DMTF specifications have deprecated the use of qualifiers on instance

operations with the 1.2 CIM Operations Specification.  Some CIM Client implementations expect instances

returned

from the CIM Server to include the qualifiers defined in the class

definition (such as KEY qualifiers on properties).   Pegasus

today expects the provider to complete the qualifiers on instances in

accordance with the specification and generally the interpretation is

that Pegasus applies class level qualifiers when the includeInstance

parameter is supplied on instance operations.  However, Pegasus

today is inconsistent in the return of qualifiers so that the user

should NOT depend on Pegasus accurately honoring the includeQualifier

parameter for instance operations.  In the future it is expected

that Pegasus will deprecate the use of qualifiers on instance

operations completely.

</li>

<li>LocalOnly option on instance

Operations - With the 1.1 version of Specification for CIM

Operations over HTTP, the definition of the LocalOnly parameter for the

GetInstance and EnumerateInstances operations was modified. This change

was incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

introduced by this change, we strongly recommend that CIM Clients set

LocalOnly = false and do not rely on the use of this parameter to

filter the set of set of properties returned. See Appendix C of this

specification for more information.</li>

<li>

MultiRequest Oprations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOFCompiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

</li>

</ol>

<h2>OpenPegasus <a name="Supported Platforms">Supported

Platforms</a></h2>

Each Pegasus release lists as 'active' platforms those

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus

code

base including a maintainer for the platform that will be willing to

Line 1856

Line 1556

Pegasus cannot be

assured.  In all cases, including the active platforms, it is the

responsibility of the entity that packages and/or compiles OpenPegasus

for shipment or deployment, to read, and actively monitor the Pegasus

for shipment or deployment, to read, and actively monitor the Pegasus bugzilla database for a list of relevant defects that affect their

bugzilla database for a list of relevant defects that affect their

platform.   The platforms that are considered 'active' for this

Pegasus release are:

<tbody>

Platform and

OS<o:p></o:p>

</td>

Compilers<o:p></o:p>

</td>

</tr>

HP-UX<o:p></o:p>

</td>

HP aC++ B3910B<o:p></o:p>

</td>

</tr>

Linux on Power<o:p></o:p>

</td>

gcc<o:p></o:p>

</td>

</tr>

zLinux<o:p></o:p>

</td>

gcc<o:p></o:p>

</td>

</tr>

Linux Itanium<o:p></o:p>

</td>

gcc<o:p></o:p>

</td>

</tr>

Linux IA-32<o:p></o:p>

</td>

gcc

(versions 2.9x and 3.xx)<o:p></o:p>

</td>

</tr>

Windows 2000<o:p></o:p>

</td>

Microsoft

Visual C++ Ver 6 and Microsoft .Net compiler Version.   Works on VC .NET 2003 (aka

v7.1)<o:p></o:p>

</td>

</tr>

<tr>

Windows XP<o:p>, Windows

2003</o:p>

</td>

Microsoft

Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1<o:p></o:p>

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="43" width="211"> MacOS version 10.2 and higher</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="43" width="289"> gcc 3.3,

gcc 4.01</td>

</tr>

<tr>

<td style="vertical-align: top;"><big>HP OpenVMS Alpha

</big></td>

<td style="vertical-align: top;"> <big>HP C++ V6.5-042 for OpenVMS

Alpha and above</big> </td>

</tr>

<tr>

<td style="vertical-align: top;"><big> HP OpenVMS IA64</big></td>

<td style="vertical-align: top;"><big>HP C++ V7.1-011 on OpenVMS IA64 and above</big>

</td>

</tr>

<tr>

<td style="vertical-align: top;"><big>Solaris 8

</big></td>

<td style="vertical-align: top;"><big>GNU  2.95.3,  Sun CC

compiler V 5.8. Note that the latest thread patch (108993) may be

required. (see Pegasus bug 4632)</big>

</td>

</tr>

<tr>

<td style="vertical-align: top;"><big>Solaris 9

</big></td>

<td style="vertical-align: top;"><big>GNU  2.95.3, Sun WorkShop 6

update 2 C++ 5.3, patch 111685-22 2005/04/09</big>

</td>

</tr>

</tbody>

</table>

Platform patches

Platform patches

The following is a list of platform

patches Pegasus requires.

RHAS

2.1 needs the update to fix Red Hat Bugzilla 98815.

</div>

</div>

Further information regarding Pegasus support on IBM platforms can

found at: <a href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</a>

Further information regarding Pegasus support on HP platforms can be

Further information regarding Pegasus support on HP platforms can be

found at:

<a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.

<h2><a name="Conformance with DMTF Specifications">Conformance with

DMTF Specifications</a></h2>

<h2><a name="PEGASUS Bugs">Pegasus Defects</a></h2>

It is a major goal

of the OpenPegasus project to both drive and utilize the DMTF CIM/WBEM

specifications.  However, today there are a number of known

differences. 

As of this release, some of the differences include the following:

<ol>

<li>Provider Registration - Pegasus supports registration

through a set of Pegasus Provider registration classes rather than

support the DMTF defined Provider Qualifier. Pegasus will not support

this qualifier in the future. See the readme for more information on

provider registration.</li>

<li> Indications -Today Pegasus supports process

indications but does not

include any specific support for lifecycle indications.</li>

<li>

IncludeQualifiers

option on Instance Operations

The DMTF specifications are unclear regarding the inclusion of

qualifiers on

CIM instances.  Some CIM Client implementations expect instances