pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.4 and 1.6.12.1

version 1.4, 2005/08/26 16:15:07

version 1.6.12.1, 2006/03/28 20:30:22

Line 1

<html xmlns:v="urn:schemas-microsoft-com:vml"

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

<head>

<style>

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

</style>

Line 448

Line 449

margin:1.0in 1.25in 1.0in 1.25in;

mso-header-margin:.5in;

mso-footer-margin:.5in;

mso-paper-source:0;}

div.Section1

{page:Section1;}

Line 569

Line 571

text-indent:-.25in;}

@list l4:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level8

Line 887

Line 890

text-indent:-.25in;}

@list l19

{mso-list-id:1902863286;

mso-list-template-ids:740079056;}

@list l19:level1

{mso-level-number-format:bullet;

Line 959

Line 963

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

href="PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso">

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

<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"

<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>

name="City"/>

<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"

name="place"/>

<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"

name="date"/>

<!--[if gte mso 9]><xml>

<o:DocumentProperties>

<o:Author>IBM_User</o:Author>

<o:LastAuthor> </o:LastAuthor>

Line 996

Line 994

</w:WordDocument>

</xml><![endif]-->

<div class=MsoNormal align=center style='text-align:center'><span

style='color:black'>

</div>

<span

style='font-size:13.5pt;color:black'>Pegasus Enhancement Proposal (PEP)<o:p></o:p>

Pegasus

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

PEP #: 185

PEP #: 249

Title: Release Notes for OpenPegasus 2.4

Title: Release

Notes for OpenPegasus 2.5.1

Version: 1.4

Version: 1.0

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

Created: <st1:date Year="2004" Day="23" Month="3">23 July 2004</st1:date>

Authors: Karl Schopmeyer

Authors: Karl

Status:  draft

Schopmeyer

Version History:

Status:  draft

<tbody>

Version History:

<o:p> </o:p>

<table class=MsoNormalTable border=1 cellspacing=1 cellpadding=0 width="100%"

</td>

style='width:100.0%;mso-cellspacing:.6pt;mso-padding-alt:0in 5.4pt 0in 5.4pt'>

<o:p> </o:p>

</td>

<span

style='font-family:Arial;color:black'><o:p> </o:p>

<o:p> </o:p>

</td>

<span

<o:p> </o:p>

style='font-family:Arial;color:black'><o:p> </o:p>

</td>

</tr>

<span

style='font-family:Arial;color:black'><o:p> </o:p>

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

</td>

<span

<o:p>  1 March

style='font-family:Arial;color:black'><o:p> </o:p>

2006</o:p>

</td>

</tr>

Karl Schopmeyer

<span

</td>

style='font-family:Arial;color:black'> 1.0<o:p></o:p>

</td>

Initial

Submission<o:p>

<o:p>

</o:p>

23 July 3004</o:p>

</td>

</tr>

<tr>

<span

style='font-family:Arial;color:black'><o:p> KS</o:p>

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

</td>

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

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

Initial

</tr>

Submission<o:p> (Incomplete)</o:p>

</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

1.1</td>

Review week of 12 March 2006</td>

</tr>

26 August 2004</td>

<tr>

KS</td>

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

2006</td>

Incorporate comments from 1.0</td>

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

</tr>

Schopmeyer</td>

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

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

1.2</td>

</tr>

<tr>

6  October 2004</td>

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

KS</td>

2006</td>

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

Incorporate comments from Review of 1.1</td>

Schopmeyer</td>

</tr>

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

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

1.3</td>

24 October 2004</td>

KS</td>

Update with comments from Version 1.2</td>

</tr>

1.4</td>

1 November 2004</td>

KS</td>

Comments from 1.3</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>

<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;">Typos</td>

</tr>

</tbody>

</table>

<o:p> </o:p>

<div class=MsoNormal align=center style='text-align:center'><span

style='color:black'>

Abstract: This document defines the release notes for the 2.5.1

version 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">

</div>

Abstract: This document defines the release notes that support

release 2.4 of the Pegasus platform. <span

style='font-size:9.0pt'><a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35"

target="_self">

</a>

<div class=MsoNormal align=center style='text-align:center'><span

style='color:black'>

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

</o:p></h2>

</div>

<o:p> Contents</o:p>

<ol>

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

<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">Functionality of

<li><a href="#Relationship to CIM/WBEM Standards">Relationship to CIM/WBEM

This Release</a></li>

Standards</a></li>

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

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

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

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

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

Specifications</a></li>

Platforms</a></li>

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

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

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

with DMTF Specifications</a></li>

<li>

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

in This Release</a></li>

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

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

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

Bugs</a></li>

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

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

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

Documentation</a></li>

</ol>

<h2>Availability

<h2><a name="Availability of this Release">Availability of this Release</a></h2>

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 downloaded from the OpenPegasus Web

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

site at <a href="../Application%20Data/Microsoft/Word/www.openpegasus.org">www.openpegasus.org.</a></li>

downloaded from the OpenPegasus Web

<li>OpenPegasus 2.4 binaries are available for Red Hat Enterprise Linux 3.0 and

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

SUSE LINUX Enterprise Server 9.0. A Source RPM is also available that can be

<li>OpenPegasus 2.5.1 binaries are available for Red Hat Enterprise

used to build binaries for most LSB-compliant RPM-based Linux distributions and

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

versions.</li>

also available that can be used to build binaries for most

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

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

release and subsequent snapshots that are made available in the Pegasus CVS are

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

defined on the

subsequent snapshots that are made available in the Pegasus CVS are

OpenPegasus CVS repository web page (see the

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

<a href="http://www.openpegasus.org/cvs.tpl?CALLER=page.tpl">OpenPegasus CVS

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

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

The instructions for acquiring the released code are on the

WEB site</a>.

<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

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

Pegasus source

tree.

tree.</div>

<h2>Functionality of This Release</h2>

<a name="comtag_59">Instructions for building the Linux

Pegasus overall status by release is defined by  a

RPMs: </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

<ol>

web page shows the Pegasus users and developers

<li><a name="comtag_59">Download tog-pegasus-2.4.0-1.src.rpm.

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

</a></li>

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

<li><a name="comtag_59">rpm -ih tog-pegasus-2.4.0-1.src.rpm

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

</a></li>

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

<li>

functions closer to production-capable status).The following paragraphs list the functionality in this release.   In many cases these features  and interfaces

<a name="comtag_59">Build the rpms</a>:

are conditionally compiled with special environment variables.

<a name="comtag_59">For RHEL3 - rpmbuild -bb /usr/src/redhat/SPECS/tog-pegasus- 2.4.0-1.spec </a>

provides more detailed information on how to enable

functionality that is conditionally compiled in this release.

<a name="comtag_59">For SLES9 - rpmbuild -bb /usr/src/packages/SPECS/tog-pegasus- 2.4.0-1.spec </a></li>

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

<li><a name="comtag_59">After the build the rpms will be in

please access the

the following locations: </a>

<a name="comtag_59">For RHEL3 - /usr/src/redhat/RPMS/[arch]/tog-pegasus-

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

2.4.0-1.[arch].rpm /usr/src/redhat/RPMS/[arch]/tog-pegasus-sdk- 2.4.0-1.[arch].rpm. </a>

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

of the features listed below are production ready.

<a name="comtag_59">For SLES9 - /usr/src/packages/RPMS/[arch]/tog-pegasus- 2.4.0-1.[arch].rpm /usr/src/packages/RPMS/[arch]/tog-pegasus-sdk-

2.4.01-.[arch].rpm</a>.</li>

</ol>

<h2><a name="Functionality of This Release">Functionality of This Release</a></h2>

The overall level of functionality in the Pegasus environment effective with

this release is as follows:

<h3>CIM Server Functionality</h3>

The following paragraphs list the functions in this release.  All

functions are considered community tested and operational unless specifically

noted below. Features that are marked alpha or beta are not generally of the

quality or completeness for production usage.  Interfaces that are

part of the Pegasus public interface definitions but that the Pegasus team feels

may change are marked experimental. In many cases these features  and

interfaces are conditionally compiled with special environment variables. PEP

174 provides more detailed information on how to enable functionality that is

conditionally compiled in this release.

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

<ol>

<li>Class Operations (getClass, <span

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

class=SpellE>deleteClass, modifyClass, <span

enumerateClass, enumerateClassNames)</li>

class=SpellE>enumerateClass, enumerateClassNames)</li>

<li>Qualifier Operations (getQualifier, setQualifier,

<li>Qualifier Operations (getQualifier, setQualifier, deleteQualifier) </li>

deleteQualifier) </li>

<li>Instance Operations (getInstance, <span

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

class=SpellE>deleteInstance, modifyInstance,

enumerateInstance, enumerateInstanceNames, getProperty,

enumerateInstance, enumerateInstanceNames,

setProperty)</li>

getProperty, setProperty)</li>

<li>Association Operations (references, referencenames,

<li>Association Operations (references, referencenames,

associators, associatornames)</li>

associators, associatornames)</li>

<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 considered at

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

alpha quality because it has only been contributor tested and there is no test

considered at alpha quality because it has only been contributor

in the test suite to confirm the functionality.</li>

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

today does not support the ExecuteQuery operation defined as the Query

operation for CQL.

</li>

</ol>

</blockquote>

</div>

<h4>Indication Processing</h4>

<h4>Indications</h4>

<ol>

<li>Process indications - Process indications are operational in

Process indications are operational in the Server.  This includes support

the

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

Server.  This includes support

indications and the CIMXML indication handler.

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

for

<h4>Indication Listener</h4>

indications and the CIMXML indication handler.</li>

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

The generic components for a CIM

lifecycle indications (ie. those

Listener and a listener API are operational.  This includes the functions

classes of indications derived from CIM_ClassIndication and

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

CIM_InstIndication) can now be created. Pegasus 2.5 provides some

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

enablement for the generation of lifecycle indications. For more

indication listener in the Pegasus server.

details, refer to

</ol>

<h4>Query Language</h4>

Pegasus includes the  WQL  query language which is implemented and

used for filters and in version 2.4 for execQuery.

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

combine to describe the CQL  functionality supported.

<h4>Object Normalization</h4>

The Object Normalizer is an entity introduced in Pegasus 2.4 that

ensures

objects delivered from providers are complete and accurate. Two major

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

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

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

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

CIMOM/provider boundary.

<h4>Embedded Object Support</h4>

Pegasus 2.5 provides embedded object support. The proposed solution

is restricted to the following:<ul>

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

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

internally to represent embedded objects. When externalized (via

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

EmbeddedObject attribute with

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

</li>

</ul>

<h3>Pegasus Repositories

</h3>

</blockquote>

<h4>Schema Repository</h4>

<h4>Query Language</h4>

By default, Pegasus uses an XML-based

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

The query language today is based on WQL and is implemented and used for

filters and in 2.4 for execQuery.  The execQuery support  for WQL has

been implemented in Pegasus 2.4 but is considered alpha quality.

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

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

<h4>Class Repository</h4>

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

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

Pegasus uses an XML based file/directory class repository. All class and qualifier operations

readme.binaryrepository file in the Pegasus source root directory.

access this repository. The repository was modified to improve efficiency in 2.4

by adding a binary repository option to reduce repository size. The binary

repository functions are considered alpha level because they have only been

contributor tested and there is no test function in the automated Pegasus test

suite.

<h4>Instance Repository</h4>

The

Pegasus uses an XML based file/directory Instance repository.  The

Pegasus schema repository may also be configured to hold instance

instance  repository may be conditionally used as the default repository

data.  Although instances may be place in the

with a Pegasus configuration flag ( As defined in PEP 174, it is normally set 

repository

to NOT use the instance repository as default).

it was not designed as a

high volume data store.

<h4>Compressed Repository Feature</h4>

A compressed repository

feature has been added for

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

the

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

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

<li class=MsoNormal style='color:black;mso-list:l14 level1 lfo6;tab-stops:

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

list .5in'>Basic Authentication (Note that Digest based security is not

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

implemented) <o:p></o:p></li>

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

<li class=MsoNormal style='color:black;mso-list:l14 level1 lfo6;tab-stops:

implemented in Pegasus using the OpenSSL

list .5in'>SSL support - SSL is implemented in Pegasus using the <span

libraries. Pegasus does not provide the OpenSSL

class=SpellE>OpenSSL libraries. Pegasus does not provide the <span

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

class=SpellE>OpenSSL libraries but SSL can be used on any platform

with multiple versions of  OpenSSL versions

supported by OpenSSL.  Minimum level known

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

to work is  0.9.6c .   This release of Pegasus was tested

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>

with 0.9.6k.  See <a

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

href="../Application%20Data/Microsoft/Word/www.openssl.org">openssl.org</a>

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

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

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>

<h4> Platform Management Functions</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

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

client certificates and certificate revocation lists via standard CIM

list .5in'>Configuration through the defined configuration parameters (cimconfig)

operations. It allows certificates to be associated with particular

and server command line options. <o:p></o:p></li>

system users for enhanced authorization capabilities.

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

CN/ Host

list .5in'>Daemon/service operation of the Pegasus CIM Server on all supported platforms<o:p>.</o:p></li>

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

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

and are the responsibility of the client to implement on their

list .5in'>Operation statistics capture using the CIMStatistics classes in

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

the DMTF Interop model. This function is considered alpha quality and conditionally compiled.  The

more details on client security.

default is that this function is not compiled.</li>

Note: WBEM clients are responsible for SSL

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

certificate verification using Pegasus and/or SSL libraries as

list .5in'>Multiple pluggable provider managers.  Provider managers are provided for the Pegasus C++ provider interface, the CMPI C provider interface

appropriate. Consequences of not doing so include leakage of

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

authentication credentials to unauthorized parties.

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

<h4>Platform Management Functions</h4>

list .5in'>Platform Globalization - Pegasus includes support for unicode

data transfers and includes a mechanism for message support in mulitple

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

languages using the open source ICU libraries (<a href="http://oss.software.ibm.com/icu/">http://oss.software.ibm.com/icu/</a>). Note that this is still marked

the defined configuration parameters (cimconfig) and server command

experimental.</li>

line options.  NOTE: When installed

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

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

list .5in'>Out-of-process providers (Experimental) - See PEP 072 for more information on

enableAuthentication to true can result in improper operation of the

use of this feature </li>

SLP

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

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

list .5in'>Shared class namespaces (Experimental) - See PEP 129 for more information on

Administrator should change the user that the service runs under from

use of this feature</li>

the Local

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

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

list .5in'>Remote providers for the CMPI provider interface (Experimental)

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

- See PEP 130

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

for more information on use of this feature</li>

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

SLP support is included but is conditionally compiled with the default.  This code can be enabled by setting the compile

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

environment variable PEGASUS_ENABLE_SLP.   Once compiled, SLP support

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

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

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

an SLP service agent in the Pegasus CIM severas and generates SLP advertisements compatible with the DMTF

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

slp template specification. The SLP support also includes  extensions to the CIM

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

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

environment variable (PEGASUS_HAS_OPENSLP)  Once compiled, SLP

(note that these interfaces are not yet part of the Pegasus public SDK).

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

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

<h4>Provider Managers</h4>

internal agent or OpenSLP)  and

generates SLP advertisements compatible with the DMTF slp template

Pegasus is designed to support multiple Provider Managers to allow multiple

specification. The SLP support also includes  extensions to the

provider interfaces to the CIMOM.  The default provider manager is the C++

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

Interface.  This section defines the additional provider managers available

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

with Pegasus 2.4.

public SDK).

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

<h4>Indication Handlers</h4>

<h5>System Log Indication Handler

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

</h5>

The SysLog Indication Handler is a new

Pegasus 2.4 includes a provider manager for the CMPI C interfaces.

for 2.5

This C interface is the result of a project by the IBM SBLIM team (<span

type of Indication Handler which allows CIM Indications to be delivered

class=GramE>see� <a

to the system syslog file. It has following features:

href="http://www-124.ibm.com/sblim/)">http://www-124.ibm.com/sblim/)</a> and

also the working draft of the Open Group specification for these interfaces

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

which is in review now within the WBEMSource

an entry made by Syslog Indication Handler.

Initiative (<a href="http://www.wbemsource.org/">http://www.wbemsource.org</a>).

If a subscriber includes PerceivedSeverity property in the SELECT

This provides a standardized C level interface for creating providers that can

list of the filter condition for the indication, the PerceivedSeverity

be registered with the Pegasus CIM Server in the same manner as the current C++

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

providers.

severity 'LOG_INFO' is used.

See

Today, the CMPI provider manager and interfaces are considered experimental

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

and are subject to change in future versions of Pegasus  until the CMPI

206</a> for details.

specification is released. Information on writing providers with the CMPI

<h5>Email Indication Handler

interface is available in the draft version of the specification today (see

</h5>

above) and in the following documents (<a href="http://www-124.ibm.com/sblim/doc/CMPIandC++.pdf">http://www-124.ibm.com/sblim/doc/ProviderArchitecture.pdf

The Email Indication Handler is a new

</a>and <a href="http://www-124.ibm.com/sblim/doc/CMPIandC++.pdf">

for 2.5

http://www-124.ibm.com/sblim/doc/CMPIandC++.pdf</a>) and readme.cmpi in the

type of Indication Handler that allows CIM Indications to be delivered

Pegasus source root directory.

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

Pegasus includes an experimental provider manager for Java provider

includes a provider manager for Java

interfaces based on the SNIA provider interface definitions.  This provider

provider interfaces based on the SNIA provider interface

manager is  considered alpha quality and is not compiled in the default build.  

definitions.  This provider manager is  considered alpha

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

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>

<h3>Providers</h3>

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

to run out of process at

There are a number of providers available in the Pegasus release.

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

Pegasus provides a set of "internal" providers that have direct access to the

access to the CIMOM for information and provide information and

CIMOM for information and provide information and services to support the CIMOM

services to support the CIMOM and its administration.    The

and its administration.    The providers in this category are mostly defined in the directory src/pegasus/controlproviders

providers in this category are mostly defined in the directory

and include support for the following classes:

src/pegasus/controlproviders and include support for the following

classes:

<ul>

<li>DMTF Interop classes including __Namespace,  <span

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

class=SpellE>CIM_Namespace, CIM_ObjectManager,

CIM_CommunicationMechanism, and

CIM_CommunicationMechanism, and CIMOMStatistics.</li>

CIMOMStatistics.</li>

</ul>

<h4>CMPI Remote Providers</h4>

<h4>Generic Providers</h4>

Pegasus includes an support for

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

Generic OperatingSystem provider. See the

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

directory src/Providers/generic.

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

See the directories src/Providers/TestProviders

and src/Providers/sample for more

and src/Providers/Sample for more information about test and

information about test and

sample providers.

<h4>Managed System Providers</h4>

ComputerSystem, DNSAdmin,

ComputerSystem, DNSAdmin,

DNSService, Operating System, Process,

DNSService, Operating System, Process, Processor. For

Processor. For

more information on these providers see the documentation for each provider in

more information on these providers see the documentation for each

the directory src/Providers/ManagedSystem

provider in

the directory src/Providers/ManagedSystem

<h4>SLP Provider</h4>

<h4>Server Statistics Provider

</h4>

This provider acts as the definer of  SLP

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

information for SLP registration and also controls the Pegasus SLP Service

are implemented in this release. The statistics gathering is compiled

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

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

it does not use internal functions of the CIMOM to generate any of its

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

information today. (conditionally compiled today)

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>

<h3>CIM_Schema</h3>

The generic components for a CIM Listener and a

The default CIM_Schema loaded with this release is

listener API are operational.  This includes the functions for

the DMTF CIM 2.8, Final release.  In addition, Pegasus includes a number of

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.   CIM 2.9 preliminary

directory.   There are also a

schema is also available in the CVS but is not the default schema for compile. 

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

There are also a number of older schema available in the CVS.

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

The mechanism to install other schemas than the default is defined

defined in the mak/config.mak

in the mak/config.mak

NOTE: The CIM 2.5 schema is

NOTE: The CIM 2.5 schema is maintained in the

maintained in the

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

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

test

environment.

</blockquote>

<h3>Pegasus MOF Compilers</h3>

<h3>Pegasus CIM Server Administration</h3>

Pegasus implements a MOF compiler that can operate either at the client

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

interface to the Pegasus CIM Server (cimmof) or directly interfacing with a CIM

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

repository (cimmofl).

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

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

The direct interface compiler is used primarily to provide an initial

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

class/instance repository. WARNING:

- Manage the CIM Server authorization characteristics. Today this is

the use of cimmofl

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

to manipulate instances in the repository bypasses any provider that is

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

registered to serve these  instances and simply installs the instances in the

- Manage information about the providers .</li>

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). Use of <span

class=SpellE>cimmof rather that cimmofl is encouraged

wherever possible.

<h3>Client Tools</h3>

<h4>   Pegasus CIM Server Adminstration</h4>

<li class=MsoNormal style='color:black;mso-list:l8 level1 lfo15;tab-stops:

list .5in'>cimuser - Manage Pegasus CIM Server

Users.<o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l8 level1 lfo15;tab-stops:

list .5in'>cimconfig - Manage the Pegasus CIM

Server configuration parameters.<o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l8 level1 lfo15;tab-stops:

list .5in'>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;mso-list:l8 level1 lfo15;tab-stops:

list .5in'>cimprovider - Manage information

about the providers .<o:p></o:p></li>

</ol>

<h4>Information client tools</h4>

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

<li class=MsoNormal style='color:black;mso-list:l4 level1 lfo18;tab-stops:

- output classes and/or instance information from the Pegasus

list .5in'>tomof - output classes and/or

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

instance information from the Pegasus repository in MOF or XML format.<o:p></o:p></li>

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

<li class=MsoNormal style='color:black;mso-list:l4 level1 lfo18;tab-stops:

- Generate a set of standard information on the Domain

list .5in'>dnsinfo - Generate a set of standard

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

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;mso-list:l4 level1 lfo18;tab-stops:

list .5in'>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;mso-list:l4 level1 lfo18;tab-stops:

list .5in'>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>

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>

<h4>Test support Tools</h4>

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

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

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

tests are defined throughout the Pegasus source tree typically in

list .5in'>Pegasus unit tests (available through the "tests"

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

option on the Pegasus make files) these tests are defined throughout the

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

Pegasus source tree typically in "tests" directories.       

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

<o:p></o:p></li>

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

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

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

list .5in'>The Pegasus test suite (see the pegasus/tests directory and the

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

Pegasus/TestBuildMakeFile)<o:p></o:p></li>

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

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

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

list .5in'>TestClient - Basic client for overall

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

platform operation testing. <o:p></o:p></li>

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

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

benchmark test environment is provided which includes both a client and

list .5in'>wbemexec - Test tool that

provider component. See src/clients/benchmarkTest

sends/receives XML from XML input.<o:p></o:p></li>

for more information.</li>

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

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

list .5in'>CLI - Command line interface for Client commands.<o:p></o:p></li>

the

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

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

list .5in'>Benchmark Test - A benchmark test

client,

environment is provided which includes both a client and provider component.

and the

See src/clients/benchmarkTest for more

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

information.<o:p></o:p></li>

</ol>

<h3>Pegasus Interface APIs</h3>

Details of the Pegasus public interfaces for this release are listed

Details of the Pegasus public interfaces for this release are listed in PEP

in PEP 209

189

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>).

available from the web site(<a

That document is the authorative source for the list

href="../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 and these are marked as

extensions and new interfaces added for this release.

experimental.   The Pegasus public

  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;mso-list:l5 level1 lfo24;tab-stops:

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

list .5in'>Client APIs<o:p></o:p></li>

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

<li class=MsoNormal style='color:black;mso-list:l5 level1 lfo24;tab-stops:

function APIs</li>

list .5in'>Provider APIs<o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l5 level1 lfo24;tab-stops:

list .5in'>CIM Object and System function APIs</li>

</ol>

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

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

in the public SDK including:

public SDK including:

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

<li class=MsoNormal style='color:black;mso-list:l5 level1 lfo24;tab-stops:

<li class="MsoNormal">CIM Listener

list .5in'>CIM Listener APIs</li>

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

<li class=MsoNormal style='color:black;mso-list:l5 level1 lfo24;tab-stops:

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

list .5in'>SLP Client (User Agent) APIs which are

running or a physical separation between the indication listener and

extensions to the Client APIs</li>

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>

<o:p> </o:p>

The APIs are

documented in

The APIs are documented in

their respective header files and  in HTML documentation based on

their respective header files and  in HTML documentation based on the information

the information

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

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

OpenPegasus web site. <o:p></o:p>

the

OpenPegasus web site.

<h3>WMI Mapper</h3>

WMI Mapper

The WBEM to WMI Mapper provides a way to access

The WBEM to WMI Mapper provides a way

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

to access

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

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

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

requests

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

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

message and extracts from the HTTP message header the user credentials provided

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

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

authenticates these credentials, verifying if the provided credentials have

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

access to the desired WMI data. This is done because the WMI <span

XML

class=SpellE>Mapper runs as a service, logged on using an account with

message and extracts from the HTTP message header the user credentials

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

provided

WMI Mapper impersonates the user credentials provided

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

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

authenticates these credentials, verifying if the provided credentials

data. Hence, ALL requests made to the WMI Mapper MUST

have

contain user credentials.

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

account with

<h2><a name="Relationship to CIM/WBEM Standards">Relationship to CIM/WBEM

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

Standards</a></h2>

this, the

WMI Mapper impersonates the user

Pegasus was designed and implemented to comply with the DMTF specifications The following table defines the

credentials provided

level of the DMTF specifications which which Pegasus conforms today.

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

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

to which this version of Pegasus conforms today.

<tbody>

<tr>

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

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

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

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

</tr>

<tr>

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

Line 1634

Line 1819

</tr>

<tr>

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

<td width="33%">2.8 Final, June 2004</td>

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

</tr>

</tbody>

</table>

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

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

Platforms</a></h2>

Each Pegasus release lists as 'active' platforms those

Each Pegasus release lists as supported platforms those

hardware/software platforms that have recognized ports for the Pegasus

hardware/software platforms that have recognized ports for the Pegasus code

code

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

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

assure that the port is maintained as the Pegasus code base is changed. 

regularly document issues and/or fix defects as the Pegasus

Pegasus may be operable on other platforms (ex. Windows 98) but without a group

code base is changed. 

to provide the role of test and maintenance, the Pegasus project cannot assure

Pegasus may be operable on other platforms (ex. Windows 98) but without

operation. The supported platforms for this Pegasus release are:

a group

to provide the role of test and maintenance, correct operation of 

<table class=MsoNormalTable border=1 cellspacing=1 cellpadding=0 width=504

Pegasus cannot be

style='width:302.25pt;mso-cellspacing:.6pt;mso-padding-alt:0in 5.4pt 0in 5.4pt' height="409">

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

Platform and OS<span

bugzilla database for a list of relevant defects that affect their

style='color:black'><o:p></o:p>

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

Pegasus release are:

<tbody>

Platform and

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

</td>

Compilers<span

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

style='color:black'><o:p></o:p>

</td>

</tr>

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

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

</td>

HP aC++

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

B3910B<o:p></o:p>

</td>

</tr>

PowerLinux<span

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

style='color:black'><o:p></o:p>

</td>

gcc<span

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

style='color:black'><o:p></o:p>

</td>

</tr>

zLinux<span

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

style='color:black'><o:p></o:p>

</td>

gcc<span

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

style='color:black'><o:p></o:p>

</td>

</tr>

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

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

</td>

gcc<span

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

style='color:black'><o:p></o:p>

</td>

</tr>

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

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

</td>

gcc<span

gcc

style='color:black'> (versions 2.9x and 3.xx)<o:p></o:p>

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

</td>

</tr>

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

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

</td>

Microsoft

Microsoft

Visual C++ Ver 6 and Microsoft .Net compiler Version.   <span

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

style='color:black'>Works on VC .NET 2003 (aka

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

</td>

</tr>

<tr>

Windows XP<o:p></o:p>

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>

</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>

Microsoft

Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1<span lang=NL style='color:black;mso-ansi-language:

NL'><o:p></o:p>

</td>

</tr>

Sun Solaris 9</td>

Sun workshop 6, update 2</td>

</tr>

MacOS version 10.2 and higher</td>

gcc 3.3</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

Further information regarding Pegasus support on IBM platforms can be found at:<a

The following is a list of platform

href="http://publib.boulder.ibm.com/eserver/v1r1/en_US/index.html" target="_"> http://publib.boulder.ibm.com/eserver/v1r1/en_US/index.html.</a>

patches Pegasus requires.

RHAS

2.1 needs the update to fix Red Hat Bugzilla 98815.

</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 found at:

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

<o:p> </o:p>

DMTF Specifications</a></h2>

<h2><a name="Conformance with DMTF Specifications">Conformance with 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. 

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

<li>Provider Registration - Pegasus supports registration

Pegasus Provider registration classes rather than support the DMTF defined Provider

through a set of Pegasus Provider registration classes rather than

Qualifier. Pegasus will not support this qualifier in the future. See the readme for more information on provider registration.</li>

support the DMTF defined Provider Qualifier. Pegasus will not support

<li> Indications -Today Pegasus supports process indications but does not

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

Instance qualifiers and class

option on Instance Operations

qualifiers on some Operations -

The DMTF specifications are unclear regarding the inclusion of qualifiers on

The DMTF specifications are unclear regarding the inclusion of

CIM instances.  Some CIM Client implementations expect instances returned

qualifiers on

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

CIM instances.  Some CIM Client implementations expect instances

(such as KEY qualifiers on properties).   Pegasus today expects the provider to complete the qualifiers on instances in

returned

accordance with the specification and generally the interpretation is that

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

Pegasus applies class level qualifiers when the includeInstance parameter is

definition (such as KEY qualifiers on properties).   Pegasus

supplied on instance operations.  However, Pegasus today is inconsistent in

today expects the provider to complete the qualifiers on instances in

the return of qualifiers so that the user should NOT depend on Pegasus

accordance with the specification and generally the interpretation is

accurately honoring the includeQualifier parameter for instance operations. 

that Pegasus applies class level qualifiers when the includeInstance

In the future it is expected that Pegasus will deprecate the use of qualifiers

parameter is supplied on instance operations.  However, Pegasus

on instance operations completely.

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.</li>

<li>

CIM MOF compiler function for

CIM MOF compiler function for instance aliasing - The

instance aliasing - The Pegasus MOF compiler does not today support

Pegasus MOF compiler does not today support this function.  This function is

this function.  This function is planned for a future version.

planned for a future version.

</li>

<li>

MultiRequest Oprations - Pegasus does not support the DMTF defined MultiRequest

Operation option.

</li>

<li>

MultiRequest Oprations - Pegasus

LocalOnly option on some instance Operations -

does not support the DMTF defined MultiRequest Operation option.

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.

</li>

<li>

MOFCompiler namespace pragma - The

MOFCompiler namespace pragma - The Pegasus compiler does not support the namespace pragma.

Pegasus compiler does not support the namespace pragma.

</li>

</ol>

<h2><a name="Changes in This Release">Changes in This Release</a></h2>

The development and release of each version of Pegasus is defined

The development and release of each version of Pegasus is defined and

and

controlled through Pegasus PEP documents.  PEP 97 is the controlling document

controlled through Pegasus PEP documents.  PEP 180 is the

this release and lists the original set of changes proposed and the status of

controlling document  for Pegasus 2.5.0 and PEP 239 is the controlling

document for this release. These PEPs list the original set of changes proposed and the

status of

each of those changes. Note that not all of the originally defined

functionality was completed for this release.

In general, the areas of development for release 2.5.0 were:

In general, the areas of development for this release were:

Addition of CQL

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

stage 1 support

list .5in'>

Expansion of platform globalization.</li>

</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Refactoring of

Expansion of SLP support (still

Object Normalizer function to improve performance.

experimental and by default not compiled in the 2.4 release).</li>

</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Out of Process

Inclusion of the Pluggable Provider   manager

Provider user level request.

(Providermanager2)as the default provider manager. Note that the original

provider manager will NOT be supported in the future.</li>

</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Embedded Object

Inclusion of Pluggable

support.

CMPI provider manager and the JMPI provider.  </li>

</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Command Line

Inclusion of the out-of-process

Utilities

provider mechanism and the remote provider mechanism for CMPI. (Experimental)</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

</li>

list .5in'>

Addition of the binary repository

CIMDateTime

option. (Experimental)</li>

enhancements

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

</li>

Addition of the shared namespace

concept so that class and qualifier definitions can be shared between multiple

Completion of

namespaces. (Experimental)</li>

AutoPtr enhancements.

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

</li>

list .5in'>

Refactoring of the HTTP monitor.</li>

Certificate

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

management and user-based certificate authentication

list .5in'>

Addition of HTTP chunking.

</li>

Note that the internal segmenentation of operation responses allowing better control of memory within

the cimom is planned for the future.</li>

Completion of HTTP

chunking. Pegasus

now supports HTTP V1.1 transfer encoding otherwise known as chunking .<a href="http://www.openpegasus.org/pp/uploads/40/5097/PEP140_ChunkedEncoding_4.3.html">

PEP 140</a> describes the implementation details.

</li>

<li class="MsoNormal" style="color: black;">Client side performance

statistics</li>

<li class="MsoNormal" style="color: black;">Syslog Indication handler.</li>

<li class="MsoNormal" style="color: black;">Email Indication handler.</li>

<li class="MsoNormal" style="color: black;">Port to OpenVMS.</li>

</ol>

For release 2.5.1, a number of additional changes were made( See PEP 239 for

more details):.

Note that there were a number of objectives that were not completely achieved

<li>Significant performance improvements ( better than 10 to 1 for operations

including: <o:p></o:p>

and 3 to 1 for indications). (bug 4225)</li>

<li>Improved support for the several platforms (Solaris, MacOS, HardHat Linux)</li>

<li>Modified Makefile targets for easier usage.</li>

<li class=MsoNormal style='color:black;mso-list:l10 level1 lfo30;tab-stops:

<li>Extended and reorganized unit and end-end tests.</li>

list .5in'>Complete move to segmented operation responses and positive control of memory

<li>Completed implementation of statistics gathering for operations.</li>

for operations.   The chunking code has been incorporated and the

<li>Further integrated CMPI and added additional tests.</li>

Pegasus client and the Server HTTP components handle chunking.  The

<li>Consolidate some of the compile-time variables. Largely this meant moving

components necessary to segment operation responses from the providers was not

from separate variables for DISABLE and ENABLE to a single variable where the

completed and will be included in a future version.</li>

value representes the state.</li>

<li>Corrected error where Pegasus could not maintain general whitespace in

strings (bug 4624).</li>

<li>SLP extended to allow optional use of OpenSLP as the Service Agent (SA) in place of

the Pegasus internal SA.</li>

<li>Changes to align OpenPegasus and Red Hat RPM packaging and configuration

options.</li>

<li>Additonal testing and integration of the  JMPI provider manager.</li>

</ol>

Specifically the status of several components of Pegasus functionality were

The complete set of PEPs defined for this release is

moved in status on the Feature Status Page as follows:

defined in PEP 97.

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

The current bug list for Pegasus is openly available on the

<a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus web

site</a>.  As of the release of 2.4 release date, the following list represents

what the Pegasus community feels are a subset of  open bugs with

OpenPegasus 2.4 that may be of particular interest to users. Please see the bug reports

(the number is a link to the report) to determine if there are any workarounds,

patches, etc. for particular bugs.

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=730

style='width:437.95pt;mso-cellspacing:0in;mso-padding-alt:2.4pt 2.4pt 2.4pt 2.4pt'>

<span

style='mso-fareast-font-family:"Times New Roman"'><a

href="buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Pegasus+CLI+Commands&product=PegasusCIMOM&product=PegasusClient&product=PegasusCompiler&product=PegasusGeneral&product=PegasusJavaCIMClient&product=PegasusProvider&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&newqueryname=&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id">ID</a>

<o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'><a

class=SpellE>Sev</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'><a

class=SpellE>Pri</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'><a

class=SpellE>Plt</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'><a

<o:p></o:p>

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=14">14</a> <o:p></o:p>

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

MOF

Compiler does not support aliasing <o:p></o:p>

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=377">377</a> <o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>enh<span style='mso-fareast-font-family:

"Times New Roman"'> <o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>Multirequest operations<span style='mso-fareast-font-family:

"Times New Roman"'> not supported <o:p></o:p>

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=424">424</a> <o:p></o:p>

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>XMLParser<span style='mso-fareast-font-family:

"Times New Roman"'> removes whitespace <o:p></o:p>

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=482">482</a> <o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>maj<span style='mso-fareast-font-family:

"Times New Roman"'> <o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

Absence

of REFERENCECLASSNAME in XML causes error <o:p></o:p>

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=786">786</a> <o:p></o:p>

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>CIMRepository<span style='mso-fareast-font-family:

"Times New Roman"'> enumerateinstances <span

class=SpellE>deepInheritance, etc. procesing

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1195">1195</a> <o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>maj<span style='mso-fareast-font-family:

"Times New Roman"'> <o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>ResponseHandler<span style='mso-fareast-font-family:

"Times New Roman"'> should clone CIM* objects before modifying

them

</td>

</tr>

<tr>

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1285" style="color: blue; text-decoration: underline; text-underline: single">1285</a> <o:p></o:p>

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>EnumerateInstanceNames<span

style='mso-fareast-font-family:"Times New Roman"'> generates namespace error <span

class=SpellE>CIMException

</td>

</tr>

<tr>

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1307" style="color: blue; text-decoration: underline; text-underline: single">1307</a> <o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>maj<span style='mso-fareast-font-family:

"Times New Roman"'> <o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

Functionality on errors with Enumerate Functions. Should we

generate error or send existing data. Today we pass data.

</td>

</tr>

</td>

</td>

</td>

</td>

</td>

</tr>

</table>

<span style='mso-fareast-font-family:"Times New Roman";

display:none;mso-hide:all'><o:p> </o:p>

<h2><a name="Bugs Corrected in This Release">Bugs

Corrected in This Release</a>

</h2>

The current bug list for Pegasus is openly available on the

<a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus web site bug

database</a>.  The database can be searched for bugs fixed based on date

and Pegasus version.

Specifically the following Bugs which were listed in the release notes for

Pegasus 2.3.2 have been fixed.

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=730

style='width:437.95pt;mso-cellspacing:0in;mso-padding-alt:2.4pt 2.4pt 2.4pt 2.4pt'>

<span

style='mso-fareast-font-family:"Times New Roman"'>

<o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'>

class=SpellE>Sev</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'>

class=SpellE>Pri</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'>

class=SpellE>Plt</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'>

<o:p></o:p>

</td>

</tr>

544</a>

</td>

maj

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

MOF compiler does not convert escape characters

</td>

</tr>

1054</a> <o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>enh<span style='mso-fareast-font-family:

"Times New Roman"'> <o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>cimserver stop responding after stress query of repository <o:p></o:p>

</td>

</tr>

nor</td>

P2</td>

All</td>

Sample providers should not be declared in Pegasus namespace</td>

</tr>

nor</td>

nor</td>

PC</td>

MOF compiler does not handle "/* ... */" comments.</td>

</tr>

</td>

maj

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>Disabling https prevents indication delivery through http. <o:p></o:p>

</td>

</tr>

</table>

Pegasus Release Control and Version Definition Documentation</a></h2>

The Pegasus project is controlled largely through a set of documents (PEPs)

that serve as the definition and review mechanism for new and modified Pegasus

functionality and for the definition and documentation of releases.

Specifically the following PEPs define the characteristics of this Pegasus

release.

<ol>

<li>PEP 189 - OpenPegaus 2.4 External Interfaces</li>

<li>Binary Repository move to green (production capable). (see bug 4388)</li>

<li>PEP 188 - OpenPegaus 2.4 Packaging Definition for Selected Platforms</li>

<li>Out of Process providers</li>

<li>PEP 185 - Pegasus 2.4 Release Notes (This document)</li>

<li>Pegasus Provider Interfaces, User Context for Linux and Unix</li>

<li>PEP 181 - OpenPegasus 2.4 SDK Packaging Definition</li>

</ol>

<li>PEP 175 - Pegasus readme.txt for 2.4 (also in the Pegasus source tree root

directory).</li>

The complete set of changes defined for this release

<li>PEP 97 - OpenPegasus Release Definition - This PEP is used throughout the

is defined in PEP 239

development of this version as the control point for functionality that will

<h2><a name="PEGASUS Bugs">Pegasus defects

go into the release and points to all of the PEPs that represent the Pegasus

</a></h2>

2.4 functionality changes.</li>

The Pegasus bugzilla database documents any defects found in Pegasus

and  is available through the following link:  <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla

database</a>.  Note that bugs committed for Pegasus 2.5.1 have been marked

with the keyword 2.5.1_APPROVED so that

all bug fixes for this release can be found with the following bug search. 

Note that since this was a minor release all of the fixes were documented as

bugs so that even the changes listed in the previous section are listed as bugs.

http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVED</a>

<h2><a name="Pegasus Release Control and Version Definition Documentation">Pegasus

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

The Pegasus project is controlled largely through a set of documents

(PEPs) that serve as the definition and review mechanism for new and

modified Pegasus functionality and for the definition and documentation

of releases.

Specifically the following PEPs define the characteristics of this

Pegasus release.

<ol>

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/8568/PEP209_ExternalInterface2.5.htm">PEP 209</a> - OpenPegaus 2.5 External Interfaces.

</li>

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/10083/PEP237_RecommendedReleaseOptions.htm">PEP  237</a> - OpenPegaus 2.5.1 Build and Configuration

Option  for Selected

Platforms</li>

<li>PEP 249 - Pegasus 2.5.1 Release Notes (This document located in the PEP

repository and the Pegasus source tree root directory)</li>

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/9825/PEP242_RuntimePackaging2.5.1.htm">PEP 242</a> -  Pegasus 2.5.1 Runtime Packaging Definition

</li>

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/9820/PEP243_SDKFile2.5.1.htm">PEP 243</a>  - OpenPegasus 2.5.1 SDK Packaging Definition</li>

<li>PEP 251  - Pegasus readme.txt for 2.5.1 (Located in PEP repository

and also in the Pegasus

source

tree root directory).</li>

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/10067/PEP239_2_5_1ReleaseDefinition.htm">PEP 239</a> - OpenPegasus Release Definition - This PEP is used

throughout the development of this version as the control point for

functionality that will go into the release and points to all of the

PEPs that represent the Pegasus 2.5 functionality changes.  (as of

this document verion of PEP 230, PEP 180 is listed as draft status)</li>

</ol>

<h2><a name="General Documentation">General Documentation</a></h2>

The following documentation is available for the this Pegasus

The following documentation is available for the this Pegasus release:

release:

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

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

combination of help generally available with the -h option for each

list .5in'>Utilities - A combination of help generally available with the

command and HTML documentation for most of the tools.<o:p></o:p></li>

-h option for each command and HTML documentation for most of the tools.<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">API and  usage

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

documentation - See the header files and the HTML  API

list .5in'>API and  usage documentation - See the header files and the

documentation that is on the web site. The best API usage documentation

HTML  API documentation that is on the web site. The best API usage documentation is

is the existing utilities and test programs and the examples in the API

the existing utilities and test programs and the examples in the API

documentation.  In particular the Common/tests unit tests contain

documentation.  In particular the

extensive examples of the use of the Common APIs.</li>

Common/tests unit tests contain extensive examples of the use of the

<li class="MsoNormal" style="color: black;">Building and Debugging

Common APIs.</li>

Providers - Readme.html in the Pegasus Root Directory, API

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

documentation, and documentation from the Pegasus Technical Workshop

list .5in'>Building and Debugging Providers - Readme.html in the Pegasus Root

which is available on the Pegasus web site.</li>

Directory, API documentation, and documentation from the Pegasus Technical

<li class="MsoNormal" style="color: black;">Building and Debugging

Workshop which is available on the Pegasus web site.</li>

Clients - API documentation and the documentation on the Pegasus

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

Technical Workshop which is available on the Pegasus web site.</li>

list .5in'>Building and Debugging Clients - API documentation and the

<li class="MsoNormal" style="color: black;">Compiler operation and

documentation on the Pegasus Technical Workshop which is available on the

commands - compiler help (cimmofl -h)</li>

Pegasus web site.</li>

<li class="MsoNormal" style="color: black;">PEPs - The

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

features of Pegasus that have been installed in this and the previous

list .5in'>Compiler operation and commands - compiler help (cimmofl

few versions are defined by Pegasus PEPs that are available on the

-h)</li>

OpenPegasus web site.  While these are the original design

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

documents largely and use in the process of defining and approving the

list .5in'>PEPs - The features of Pegasus that have been installed

overall characteristics of new functionality, they serve as a guide to

in this and the previous few versions are defined by Pegasus PEPs that are

the design and implementation of these features.</li>

available on the OpenPegasus web site.  While these are the original

design documents largely and use in the process of defining and approving the

overall characteristics of new functionality, they serve as a guide to the

design and implementation of these features.</li>

</ul>

<o:p></o:p>

<o:p></o:p>

<div class=MsoNormal align=center style='text-align:center'><span

style='color:black'>

Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open

Group; VERITAS Software Corporation; Intel Corp.

</div>

Development Company, L.P.; IBM Corp.; The Open Group; VERITAS Software

Corporation

Permission is hereby granted, free of

Permission is hereby granted, free of charge, to any person

charge, to any person obtaining a copy  of this software and associated

obtaining a copy  of this software and associated documentation files (the

documentation files (the "Software"), to deal in the Software without

"Software"), to deal in the Software without restriction, including without

restriction, including without limitation the rights to use, copy, modify,

limitation the rights to use, copy, modify, merge, publish, distribute,

merge, publish, distribute, sublicense, and/or sell copies of the Software, and

sublicense, and/or sell copies of the Software, and to permit persons to whom

to permit persons to whom the Software is furnished to do so, subject to the

the Software is furnished to do so, subject to the following conditions:

following conditions:

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE

THE ABOVE COPYRIGHT NOTICE AND THIS

SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE

PERMISSION NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF

SOFTWARE IS PROVIDED  "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

THE SOFTWARE. THE SOFTWARE IS PROVIDED  "AS IS", WITHOUT

IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE

LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,

FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,

OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR

SOFTWARE.</div>

THE USE OR OTHER DEALINGS IN THE SOFTWARE.

</div>

</body>

</html>

</body></html>

Legend:

Removed from v.1.4
changed lines
	Added in v.1.6.12.1

No CVS admin address has been configured