pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.3, 2005/08/26 16:13:44

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

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 450

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 572

text-indent:-.25in;}

@list l4:level7

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

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level8

Line 598

Line 602

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

mso-level-number-position:left;

text-indent:-.25in;}

@list l5:level5

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

mso-level-number-position:left;

Line 888

Line 891

text-indent:-.25in;}

@list l19

{mso-list-id:1902863286;

mso-list-template-ids:740079056;}

@list l19:level1

{mso-level-number-format:bullet;

Line 960

Line 964

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 997

Line 995

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

PEP #: 150<o:p></o:p>

Title: Release Notes Pegasus 2.3.2

Version: 1.5

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

Authors: <st1:City><st1:place>Warren</st1:place></st1:City> <span

class=SpellE>Grunbok

                Karl

Schopmeyer

Status:  draft

Version History:

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

Pegasus

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

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

<span

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

Title: Release

</td>

Notes for OpenPegasus 2.5.1 and Subsequent 2.5 minor releases

Version: 1.7

<span

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

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

Authors: Karl Schopmeyer

</td>

Status:  draft

<span

Version History:

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

</td>

<tbody>

<span

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

<o:p> </o:p>

</td>

</tr>

<o:p> </o:p>

</td>

<span

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

<o:p> </o:p>

</td>

<st1:date

<o:p> </o:p>

Year="2004" Day="23" Month="3">

</td>

23

</tr>

March 2004</st1:date><o:p></o:p>

</td>

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

<span

</td>

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

</td>

<o:p>  1 March

2006</o:p>

Initial

</td>

Submission<o:p></o:p>

</td>

</tr>

Karl Schopmeyer

</td>

<span

Initial

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

Submission<o:p>

</td>

</o:p>

</td>

<st1:date

</tr>

Year="2004" Day="4" Month="4">

<tr>

4

April 2004</st1:date><o:p></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>

<span

</tr>

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

mso-fareast-font-family:"Times New Roman";color:black'><o:p>K

Schopmeyer</o:p>

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

</td>

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

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

Incorporate comments

Review week of 12 March 2006</td>

from� review<o:p></o:p>

</tr>

</td>

<tr>

</tr>

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

2006</td>

<o:p>

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

1.2/3</o:p>

Schopmeyer</td>

</td>

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

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

<o:p>

</tr>

15

<tr>

April 2004</o:p>

</td>

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

2006</td>

<o:p>

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

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

Schopmeyer</td>

mso-fareast-font-family:"Times New Roman";color:black'><o:p>K

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

Schopmeyer</o:p>

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

</td>

</tr>

<tr>

<o:p>

Incorporate

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

comments from Second review</o:p>

2006</td>

</td>

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

</tr>

Schopmeyer</td>

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

status "experimental" for certain features</td>

</tr>

<span style='font-family:Arial;

<tr>

mso-fareast-font-family:"Times New Roman";color:black'><o:p>

1.4</o:p>

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

</td>

2006</td>

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

Schopmeyer</td>

<span style='font-family:Arial;

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

mso-fareast-font-family:"Times New Roman";color:black'><o:p> 20

architecture group</td>

April 2004</o:p>

</tr>

</td>

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

<span style='font-family:Arial;

2006</td>

mso-fareast-font-family:"Times New Roman";color:black'><o:p> K

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

Schopmeyer</o:p>

Schopmeyer</td>

</td>

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

2.5.2 release</td>

<span style='font-family:Arial;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> Incorporate

review comments from third Review</o:p>

</td>

</tr>

<span style='font-size:9.0pt;font-family:Verdana;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> 1.5</o:p>

</td>

<span style='font-size:9.0pt;font-family:Verdana;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> 28 April

2004</o:p>

</td>

<span style='font-size:9.0pt;font-family:Verdana;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> K.

Schopmeyer</o:p>

</td>

<span style='font-size:9.0pt;font-family:Verdana;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> Add

Bug 1400 to bug list.</o:p>

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

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

</div>

Abstract: This document defines the release notes that support

release 2.3.2 of the Pegasus platform.  This release notes document incorporates

the Pegasus version 2.3.0 and 2.3.1 release notes plus a delta for 2.3.2.  Comments made

to these release notes have also been incorporated.<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'>

</div>

<o:p> </o:p>

<h2>Availability of the Release</h2>

This release is available as a source release in both ZIP and TAR formats.

The release can be downloaded from the OpenPegsaus Web

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

In addition, this release is available through Pegasus CVS. The CVS tag for the

snapshot representing this release is RELEASE_2_3_2-snapshot_1 and the

branch tag representing the current state of version 2_3_2 is

RELEASE_2_3_2-branch.  This branch defines the current released version of

the Pegasus major

release 2.3.  RELEASE_2_3_2-root defines the initial release point

where Pegasus 2.3 branched from the trunk..  This snapshot release and any

subsequent updates to version 2.3.2 will be announced on the web site and

the Pegasus mailing list.� Specific

additinal snapshots to this release will be marked in the CVS as

RELEASE_2_3_2-snapshot_x, where x is the number of the snapshot and these will correspond to equivalent

zip and tar files made available on the web site.

The instructions for acquiring the released code are on the WEB site.

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

tree.

The OpenPegasus project is currently not providing binary releases.

There may be additional point releases to the Pegasus 2.3 release and these

will be announced on the <a href="http://www.openpegasus.org">Pegasus web site</a>. <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=47"

target="_self">

</a>

<h2>Functionality of This Release</h2>

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

The overall level of functionality in the Pegasus environment effective with

</o:p></h2>

this release is as follows:

<ol>

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

CIM Server

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

This Release</a></li>

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

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

CIM Operations over HTTP support

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

Platforms</a></li>

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

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

with DMTF Specifications</a></li>

list .5in'>Class Operations (getClass, <span

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

class=SpellE>deleteClass, modifyClass, <span

in This Release</a></li>

class=SpellE>enumerateClass, enumerateClassNames)

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

- Operational<a

Bugs</a></li>

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=40"

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

target="_self"></a><o:p></o:p></li>

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

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

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

list .5in'>Qualifier Operations getQualifier, setQualifier, deleteQualifier)

Documentation</a></li>

- Operational</li>

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

list .5in'>Instance Operations (getInstance, <span

class=SpellE>deleteInstance, modifyInstance,

enumerateInstance, enumerateInstanceNames,

getProperty, setProperty)

-   Operational<o:p></o:p></li>

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

list .5in'>Association Operations (references, referencenames,

associators, associatornames)

- Operational <a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=43"

target="_self"></a><o:p></o:p></li>

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

list .5in'>Methods- Operational<span

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

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=44"

target="_self"></a><o:p></o:p></li>

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

list .5in'>Query operation (Not Operational) <o:p></o:p></li>

</ol>

<h2>Availability

<span

of this Release</h2>

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

This release is available in a number of forms including:

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=45"

<ul>

target="_self">

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

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

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>

Indications

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

Process indications are operational in the Server.  This includes support

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

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

also available that can be used to build binaries for most

indications and the CIMXML indication handler. The Pegasus server can be used as

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

an Indication client.  The Client indication  API support is complete,

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

but the interfaces are marked experimental for version 2.3 because

subsequent snapshots that are made available in the Pegasus CVS are

this is the first major release version of Pegasus in which these APIs were

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

available.

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>

Query Language

</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 query language today is based on WQL and is implemented and used for

WEB site</a>.

filters.  However, the executeQuery operation

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

has not been implemented pending the availability of a standard DMTF Query

Pegasus source

language.

tree.</div>

Class Repository

<h2>Functionality of This Release</h2>

Pegasus overall status by release is defined by  a

XML based file/directory Class repository. All class and qualifier operations

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

access this repository.

that is available on the OpenPegasus web site .  That

web page shows the Pegasus users and developers

Instance Repository

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

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

XML based file/directory Instance repository.  The instance repository

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

is used as the default repository unless a flag is set disabling this

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

repository for client operations.

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

Security

are conditionally compiled with special environment variables.

provides more detailed information on how to enable

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

functionality that is conditionally compiled in this release.

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

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

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

please access the

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

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

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

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

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

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

of the features listed below are production ready.

supported by OpenSSL.  Minimum level known

<h3>CIM Server Functionality</h3>

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

with 0.9.6k.  See <a

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

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

<ol>

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

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

enumerateClass, enumerateClassNames)</li>

<li>Qualifier Operations (getQualifier, setQualifier,

deleteQualifier) </li>

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

enumerateInstance, enumerateInstanceNames, getProperty,

setProperty)</li>

<li>Association Operations (references, referencenames,

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 alpha quality because it has only been contributor

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>

Platform Management Functions

<h4>Indication Processing</h4>

<ol>

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

<li>Process indications - Process indications are operational in

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

the

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

Server.  This includes support

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

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

list .5in'>Daemon operation on all supported platforms<o:p>.</o:p></li>

for

indications and the CIMXML indication handler.</li>

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

lifecycle indications (ie. those

classes of indications derived from CIM_ClassIndication and

CIM_InstIndication) can now be created. Pegasus 2.5 provides some

enablement for the generation of lifecycle indications. For more

details, refer to

</ol>

<h4>Query Language</h4>

SLP Discovery<a name="comtag_61">

Pegasus includes the  WQL  query language which is implemented and

</a>SLP support is included but is conditionally compiled with the default to

used for filters and in version 2.4 for execQuery.

not compile it.  This code can be enabled by setting the compile

environment variable PEGASUS_ENABLE_SLP. Note that this release differs from

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

2.3.1 in that the SLP functions have been completed and tested in an

combine to describe the CQL  functionality supported.

interoperable environment.� Also, the

<h4>Object Normalization</h4>

provider for the interop classes (CIM_ObjectManager,

The Object Normalizer is an entity introduced in Pegasus 2.4 that

CIM_Namespace,

ensures

etc.) is enabled along with the SLP discovery.

objects delivered from providers are complete and accurate. Two major

If the SLP discovery is not enabled, these interop

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

classes are also not available.

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

Normalizer code slowed performance. These issues are now addressed by

CMPI Provider Manager<o:p></o:p>

moving the Object Normalizer from the Dispatcher to the Response

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

Pegasus 2.3.2 includes as a compilable option a

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

new set of code that allows multiple provider managers and also a second

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

provider manager for the CMPI C interfaces.

CIMOM/provider boundary.

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

<h4>Embedded Object Support</h4>

class=GramE>see� <a

Pegasus 2.5 provides embedded object support. The proposed solution

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

is restricted to the following:<ul>

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

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

which is in review now within the WBEMSource

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

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

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

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

internally to represent embedded objects. When externalized (via

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

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

providers.

INSTANCE or CLASS elements, in accordance with the CIM Infrastructure

Specification.  Embedded instances will also carry the

Today, the CMPI provider manager and interfaces are considered experimental

EmbeddedObject attribute with

and are subject to change in future versions of Pegasus.

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

</li>

The CMPI provider manager, sample providers and the hooks into Pegasus are

</ul>

all conditionally compiled with the environment variables ENABLE_CMPI_PROVIDER_MANAGER

<h3>Pegasus Repositories

and ENABLE_PROVIDERMANAGER_2. See PEP 144 for details.

</h3>

</blockquote>

Providers

<h4>Schema Repository</h4>

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

By default, Pegasus uses an XML-based

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

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

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

readme.binaryrepository file in the Pegasus source root directory.

<h4>Instance Repository</h4>

The

Pegasus schema repository may also be configured to hold instance

data.  Although instances may be place in the

repository

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

(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

Internal (control) Providers

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

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

src/pegasus/controlproviders and include support for the following

list .5in'>__Namespace provider - Serves the __Namespace class to allow

classes:

manipulation of namespaces.<a

<ul>

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=65"

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

target="_self"></a><o:p></o:p></li>

CIM_CommunicationMechanism, and

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

CIMOMStatistics.</li>

list .5in'>Subscription Classes Providers - These provide subscription,

filter, and indication handler processing.<o:p></o:p></li>

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

list .5in'>Provider registration Providers - This provide registration of

providers using the PG_Provider classes.<o:p></o:p></li>

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

list .5in'>ConfigProvider - Manages Pegasus <span

class=SpellE>configuraton information.<o:p></o:p></li>

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

list .5in'>UserAuthProvider - Manages password,

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

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

list .5in'>ShutdownProvider - Provides support

for Pegasus shutdown.<o:p></o:p></li>

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

list .5in'>Interop Provider - Supports many of

the DMTF Interop Schema Classes including <span

class=SpellE>CIM_Namespace, CIM_ObjectManager,

CIM_CommunicationMechanism, etc.. (Note that

this provider is part of the SLP work package so is not compiled as part

of the default compile. The environment variable PEGASUS_ENABLE_SLP must

be set to enable this option.)<o:p></o:p></li>

</ul>

<h4>CMPI Remote Providers</h4>

Generic Providers

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

Test/Sample Providers

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

Generic Providers</h3>

See the directories src/Providers/TestProviders

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

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

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>

Managed System Providers

ComputerSystem, DNSAdmin,

DNSService, Operating System, Process,

ComputerSystem, DNSAdmin,

Processor. For

DNSService, Operating System, Process, Processor. For

more information on these providers see the documentation for each

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

provider in

the directory src/Providers/ManagedSystem

the directory src/Providers/ManagedSystem

<h4>Server Statistics Provider

CIMOM Statistics Providers

</h4>

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

IBMStatisticalData - This is an early version of

are implemented in this release. The statistics gathering is compiled

the work that became CIM_StatisticalData. It is

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

similar to CIM_StatisticalData and provides the same

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

data but the structure of the Classes is slightly different. This will be

ModifyInstance operation on the 'CIM_ObjectManager instance

standardized to the DMTF definition in a future version of Pegasus.

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>

CIM_Schema

The default CIM_Schema loaded with this release is

The generic components for a CIM Listener and a

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

listener API are operational.  This includes the functions for

local classes defined for Pegasus.  These are visible in the Schemas

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

directory.   CIM 2.8� schema is

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

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

as an indication listener in the Pegasus server.

The mechanism to switch to the the 2.8 schema is via

environment variable: PEGASUS_CIM_SCHEMA = (See Config.mak).

Pegasus includes 3 separate Indication Listeners.

<h3>Embedded CIMListener</h3>

export PEGASUS_CIM_SCHEMA=CIM28

This listener is embedded in the CIMServer and allows the

server to accept indications and route them.

NOTE: the CIM 2.5 schema is maintained in the

<h3>Standalone Static CIMListener</h3>

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

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>

Pegasus MOF Compiler

<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

wherever possible.

Client Tools

Pegasus CIM Server Adminstration

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

Information client tools

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

Test support Tools

<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       

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

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

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

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

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

list .5in'>The Pegasus Test Suite (see the tests directory and the

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

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

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

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

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

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

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

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

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

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

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

list .5in'>wbemexec - Test tool that

benchmark test environment is provided which includes both a client and

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

provider component. See src/clients/benchmarkTest

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

for more information.</li>

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

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

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

the

list .5in'>Benchmark Test - Introduced with Pegasus 2.3, a benchmark test

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

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

client,

See src/clients/benchmarkTest for more

and the

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

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

</ol>

<h3>Pegasus Interface APIs</h3>

Pegasus Interface APIs

Details of the Pegasus public interfaces for this release are listed

in PEP 209

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

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

This 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 release 2.3 Well-behaved

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 Pegasus 2.3 without compilation.  There have been

compatible with this release without compilation.  There have been

extensions and new interfaces added for release 2.3 and these are shown 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>

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

list .5in'>CIM Listener

(experimental for Pegasus 2.3.2)<o:p></o:p></li>

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

list .5in'>SLP Client (experimental for Pegasus 2.3.2)<o:p></o:p></li>

</ol>

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

<o:p> </o:p>

in the public SDK including:

The APIs are documented in

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

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

<li class="MsoNormal">CIM Listener

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

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

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

WMI Mapper

running or a physical separation between the indication listener and

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

The WBEM to WMI Mapper provides a way to access

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

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

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

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

basic capabilities, yet allows the existing CIMListener to remain the

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

same.</li>

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

<ul>

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

<li>New CIM Listener now provides selective

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

indication delivery.

authenticates these credentials, verifying if the provided credentials have

</li>

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

<li>New CIM Listener

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

keeps all consumer libraries in memory for the duration of its

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

execution.

WMI Mapper impersonates the user credentials provided

</li>

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

<li>New CIM Listener

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

is now pluggable.</li>

contain user credentials.

<li>New CIM Listener

<a

now provides reliable indication delivery.</li>

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

</ul>

target="_self">

</ul>

</a>Supported Platforms

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

<a

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

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

target="_self">

</a>Each Pegasus release lists as supported 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 regularly

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

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

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

operation. The supported platforms for Pegasus release 2.3.2 are:

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

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

Platform and OS<span

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

</td>

Compilers<span

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

</td>

</tr>

AIX 5.2<o:p></o:p>

</td>

VisualAge<span

style='color:black'> C++ Version 5.0.2.3<o:p></o:p>

</td>

</tr>

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

</td>

HP aC++

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

</td>

</tr>

PowerLinux<span

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

</td>

gcc<span

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

</td>

</tr>

zLinux<span

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

</td>

gcc<span

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

</td>

</tr>

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

</td>

gcc<span

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

</td>

</tr>

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

</td>

gcc<span

style='color:black'> (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.   <span

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

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

</td>

</tr>

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

</td>

Microsoft

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

style='color:red'>7.1<span lang=NL style='color:black;mso-ansi-language:

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

</td>

</tr>

</table>

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

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>

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

href="http://www.hp.com/large/infrastructure/management/wbem" target="_">http://www.hp.com/large/infrastructure/management/wbem</a>/.

<o:p> </o:p>

<h2>Conformance with DMTF Specifications</h2>

Pegasus tries to conform to the CIM specifications.  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 Pegasus 2.3.2, some of the differences include the following:

1. Provider Registration - Pegasus supports registration through a set of

Provider registration classes and does not support the DMTF defined Provider

Qualifier. See the readme for more information on provider registration.

2. Indications. Today Pegasus supports process indications but does not

include any specific support for lifecycle indications.

3. Interop Schema implementation differences.

Today Pegasus provides alternatives to some of the classes in the <span

class=SpellE>Interop Schema including CIM_StatisticalData.

Note that the CIM_ObjectManager and other similar

classes are only compiled with the SLP option.

4. Today Pegasus does not support the execQuery pending the availability of

a standard for the query language.  Pegasus is expected to support

execQuery in a future release with the new CQL query language and possibly WQL.

5. Instance qualifiers and class

qualifiers on some Operations -

The DMTF specifications are unclear regarding the inclusion of qualifiers on

CIM instances.  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 is based on the

interpretation that class-defined qualifiers are not included in instances, so

incompatibilities may exist with clients that rely on these qualifiers.<o:p></o:p>

<o:p> </o:p>

6. HTTP Chunking � Today the Pegasus

implementation defines itself as supporting HTTP 1.1 but does NOT support

chunking. This is a high priority for a future version.

7. CIM MOF compiler functions for instance aliasing - The

Pegasus compiler does not today support thi functions.  This function is

planned for a future version.

8. MultiRequest Oprations - Pegasus does not support the DMTF defined MultiRequest

Operation option.

9. LocalOnly option on some instance Operations - Because of

incompatible changes made between CIM Operation specification versions, the DMTF

has determined that there is confusion in the use of the LocalOnly parameter on

instance operations and the

results it will return.  The definition changed between version 1.0 and

version 1.1 of the CIM Operations

over HTTP Specification  so that the information provided to

the requestor may be different between a CIM Operations version 1.0 specification

implementation and a version 1.1 implementation.  Therefore, the Pegasus

community discourages the use of this parameter on any operations. NOTE:

We recommend that client users always set localOnly to False (remember that the

default is true) on instance

operations to avoid the confusion of different information from different CIM

Server implementations.

NOTE: This problem does not apply to the class

operations such as getClass, etc.

<h2>Changes in Release 2.3</h2>

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

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

this release and lists 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 changes implemented for this release were:

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

list .5in'>

Introduction of platform globalization.</li>

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

list .5in'>

Introduction of a listener API.</li>

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

list .5in'>

Introduction of SLP (still experimental and by default not

compiled in the 2.3.2 release).</li>

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

list .5in'>

Introduction of a new pluggable Provider Manager (still

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

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

list .5in'>

Introduction of extensive changes to the HTTP monitor (still

experimental and not compiled in the 2.3.2 release).</li>

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

list .5in'>

Inclusion of Pluggable

CMPI provider manager.  Note: This makes use of the PPM item

described below.  This is an optional compile.</li>

</ol>

<o:p> </o:p>

The APIs are

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

documented in

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

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

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

the

list .5in'>SLP integration - This code is in place but is compiled only

OpenPegasus web site.

with a conditional compile flag. This code can be enabled by setting the

environment variable PEGASUS_SLP_ENABLE and recompiling Pegasus.<o:p></o:p></li>

WMI Mapper

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

The WBEM to WMI Mapper provides a way

list .5in'>Pluggable

to access

provider manager - This was a major objective but because the code changes

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

were extensive and released very late in the development

requests

cycle of 2.3, both the old and the new provider managers are maintained in

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

the release AND the old provider manager is defined as the default

compile.  To compile and run with the new pluggable provider manager

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

functions the user must set a compile flag (TBD).  NOTE: It is the

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

intention of the Pegasus project to move to the new provider manager as

XML

soon as possible.<o:p></o:p></li>

message and extracts from the HTTP message header the user credentials

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

provided

list .5in'>HTTP Monitor enhancements - As with the Pluggable Provider

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

Manager, it was the intention to incorporate a number of enhancements to

authenticates these credentials, verifying if the provided credentials

the HTTP monitor.  Again because the time in the development phase

have

when they were submitted, the project team elected to release 2.3.2 with

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

the existing monitor as the default compile but with the code for both

account with

monitors. It is the intention to move to the new monitor as soon as

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

possible and users are free to work with either implementation.  To

this, the

compile and run with the new monitor use the flag PEGASUS_MONITOR2.<o:p></o:p></li>

WMI Mapper impersonates the user

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

credentials provided

list .5in'>CMPI Pluggable Provider Mgr - The CMPI Provider manager was

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

added as a PEP to release 2.3.2 and uses the same flag as the Pluggable

browse WMI

provider manager to control its compilation. Without setting this flag before

data. Hence, ALL requests made to the WMI Mapper

the build process this provider manager and its sample providers are NOT

MUST

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

contain user credentials.

<ol>

</ol>

<h2>Relationship to

The set of PEPs defined for release 2.3 is below

CIM/WBEM Standards</h2>

along with the final implementation status. Note that release 2.3.2 introduced no new <span

Pegasus was designed and implemented to comply with the DMTF

class=SpellE>PEPs beyond what was in release 2.3.0. All of these PEPS are

specifications The following table defines the level of the DMTF specifications

available on the OpenPegasus web site.

to which this version of Pegasus conforms today.

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

<tbody>

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

<tr>

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

<td width="20%" style='width:20.26%;background:#00CC99;padding:.75pt .75pt .75pt .75pt;

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

height:13.5pt'>

</tr>

PEP #<span

<tr>

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

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

</td>

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

<td width="46%" style='width:46.22%;background:#00CC99;padding:.75pt .75pt .75pt .75pt;

</tr>

height:13.5pt'>

<tr>

PEP Description<span

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

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

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

</td>

</tr>

<td width="33%" style='width:33.2%;background:#00CC99;padding:.75pt .75pt .75pt .75pt;

<tr>

height:13.5pt'>

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

Status<span

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

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

</tr>

</td>

<tr>

</tr>

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

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

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

</tr>

height:13.5pt'>

<tr>

56<o:p></o:p>

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

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

</tr>

height:13.5pt'>

<tr>

Unicode Support in

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

Infrastructure<o:p></o:p>

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

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

<o:p> </o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

58<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Unicode Support in

Infrastructure<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

<a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=168"

target="_self">

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

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

68<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Provider Manager Interface -

Multiple provider support<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Implemented - but requires

compile flag to integrate.<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

84<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Provider Manager Interface,

Pluggable provider manager configuration<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Implemented - see above.<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

86<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Provider Manager Interface,

pluggable provider manager.<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Implemented - see above.<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

60<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Secure connections between CIM

Listener and CIM server<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

</tbody>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

</table>

height:13.5pt'>

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

62<o:p></o:p>

Platforms</a></h2>

</td>

Each Pegasus release lists as 'active' platforms those

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

hardware/software platforms that have recognized ports for the Pegasus

height:13.5pt'>

code

SNMP Mapper

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

Indication Handler<o:p></o:p>

regularly document issues and/or fix defects as the Pegasus

</td>

code base is changed. 

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

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

height:13.5pt'>

a group

Implemented<o:p></o:p>

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

</td>

Pegasus cannot be

</tr>

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

responsibility of the entity that packages and/or compiles OpenPegasus

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

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

height:13.5pt'>

bugzilla database for a list of relevant defects that affect their

67<o:p></o:p>

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

</td>

Pegasus release are:

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Indication Consumer registration<o:p></o:p>

</td>

<tbody>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

<o:p> </o:p>

Platform and

</td>

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

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

76<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

CIM Listener Client API,

Libraries, SDK<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Implemented - Experimental<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

75<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Indication Subscription

Performance Enhancements<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

30<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

SLP support<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

Implemented - Optional compile<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

52<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Interop<span

style='color:black'> Schema provider support<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

Implemented - Optional compile<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

88<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

Polling design socket change.<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

<o:p> </o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

64<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Java implementation of CIM

Client and Listener Interface<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

Included in Pegasus based SNIA <span

class=SpellE>OpenCimom Java Classes.<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

65<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

Benchmark test utility<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

74<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

SSL certificate verification

callback enhancement<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

gcc

Implemented<o:p></o:p>

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

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

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

73<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Microsoft

Support CIM Schema 2.8

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

preliminary<o:p></o:p>

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

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

<o:p> </o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Windows XP<o:p>, Windows

79<o:p></o:p>

2003</o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Microsoft

WMI Mapper

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

- local connection enhancements<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

<o:p> </o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

77<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Default instance provider<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

</big></td>

85<o:p></o:p>

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

</td>

Alpha and above</big> </td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Configuration Property Table

Enhancement<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

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

90<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Add

IO trace diagnostics to CIMClient<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

89<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

SLP Client Integration<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Implemented but not compiled by

default<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

</big></td>

<a

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

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=306"

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

target="_self">99</a><span

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

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

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

<a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=307"

target="_self">Restructure of CIMRequest

Message</a> <o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

<a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=308"

target="_self">Implemented but not compiled by

default</a> <o:p></o:p>

</td>

</tr>

<tr>

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

102<o:p></o:p>

</big></td>

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

CMPI Pluggable Provider <o:p></o:p>

</td>

Implemented but not compiled by

default <o:p></o:p>

</td>

</tr>

</tbody>

</table>

<h2>PEGASUS Bugs</h2>

Platform patches

The following is a list of platform

The current bug list for Pegasus is openly available on the OpenPegasus web

patches Pegasus requires.

site.  As of the release of 2.3.2 release date, the following list

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

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

RHAS

patches, etc. for particular bugs.

2.1 needs the update to fix Red Hat Bugzilla 98815.

</div>

<o:p> </o:p>

Further information regarding Pegasus support on IBM platforms can

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

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>

<span

Further information regarding Pegasus support on HP platforms can be

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

found at:

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>

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

<o:p></o:p>

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

</td>

DMTF Specifications</a></h2>

It is a major goal

<span

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

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

specifications.  However, today there are a number of known

differences. 

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

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

</td>

<ol>

<li>Provider Registration - Pegasus supports registration

<span

through a set of Pegasus Provider registration classes rather than

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

support the DMTF defined Provider Qualifier. Pegasus will not support

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

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

provider registration.</li>

</td>

<li> Indications -Today Pegasus supports process

indications but does not

<span

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

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

<li>

IncludeQualifiers

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

option on Instance Operations

</td>

The DMTF specifications are unclear regarding the inclusion of

<span

qualifiers on

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

CIM instances.  Some CIM Client implementations expect instances

returned

<o:p></o:p>

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

</td>

definition (such as KEY qualifiers on properties).   Pegasus

</tr>

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

<a

parameter is supplied on instance operations.  However, Pegasus

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

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

</td>

should NOT depend on Pegasus accurately honoring the includeQualifier

parameter for instance operations.  In the future it is expected

nor

that Pegasus will deprecate the use of qualifiers on instance

<o:p></o:p>

operations completely.

</td>

</li>

<li>LocalOnly option on instance

P2

Operations - With the 1.1 version of Specification for CIM

<o:p></o:p>

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

</td>

GetInstance and EnumerateInstances operations was modified. This change

was incorrect, resulted in reduced functionality and introduced a

All

number of backward compatibility issues. As a result of issues

<o:p></o:p>

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

</td>

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

filter the set of set of properties returned.</li>

MOF

<li>

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

CIM MOF compiler function for

</td>

instance aliasing - The Pegasus MOF compiler does not today support

</tr>

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

</li>

<li>

<a

MultiRequest Oprations - Pegasus

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

does not support the DMTF defined MultiRequest Operation option.

</td>

</li>

<li>

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

MOFCompiler namespace pragma - The

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

Pegasus compiler does not support the namespace pragma.

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

</li>

</td>

</ol>

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

P2

The development and release of each version of Pegasus is defined

<o:p></o:p>

and

</td>

controlled through Pegasus PEP documents.  PEP 180 is the

controlling document  for Pegasus 2.5.0 and PEP 239 is the controlling

PC

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

<o:p></o:p>

status of

</td>

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

functionality was completed for this release.

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

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

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

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

</td>

Addition of CQL

</tr>

stage 1 support

</li>

<a

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

Refactoring of

</td>

Object Normalizer function to improve performance.

</li>

nor

<o:p></o:p>

Out of Process

</td>

Provider user level request.

P2

</li>

<o:p></o:p>

</td>

Embedded Object

support.

All

</li>

<o:p></o:p>

</td>

Command Line

Utilities

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

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

</li>

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

</td>

CIMDateTime

</tr>

enhancements

</li>

<a

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

Completion of

</td>

AutoPtr enhancements.

</li>

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

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

Certificate

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

management and user-based certificate authentication

</td>

</li>

P2

<o:p></o:p>

Completion of HTTP

</td>

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

PC

PEP 140</a> describes the implementation details.

<o:p></o:p>

</li>

</td>

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

statistics</li>

Absence

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

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

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

</td>

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

</tr>

</ol>

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

more details) Note: there was no PEP controlling Pegasus 2.5.2 changes, simply

<a

approved bugs:.

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

</td>

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

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

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

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

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

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

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

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

</td>

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

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

P2

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

<o:p></o:p>

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

</td>

value representes the state.</li>

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

All

strings (bug 4624).</li>

<o:p></o:p>

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

</td>

the Pegasus internal SA.</li>

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

MOF

options.</li>

compiler does not convert escape characters <o:p></o:p>

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

</td>

</ol>

</tr>

Specifically the status of several components of Pegasus functionality were

moved in status on the Feature Status Page as follows:

<ol>

<a

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

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

<li>Out of Process providers</li>

</td>

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

</ol>

nor

<o:p></o:p>

The complete set of changes defined for this release

</td>

is defined in PEP 239

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

P2

</a></h2>

<o:p></o:p>

The Pegasus bugzilla database documents any defects found in Pegasus

</td>

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

PC

with the keyword 2.5.1_APPROVED so that

<o:p></o:p>

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

</td>

changes between Pegasus 2.5.1 and 2.5.2 are documented in bugs with the keyword

2.5.2_APPROVED. These are a minor release all of the fixes were documented as

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

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

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

The following links provide a list of the bugs for each version

"Times New Roman"'> enumerateinstances <span

class=SpellE>deepInheritance, etc. procesing

    - Changes for Pegasus 2.5.1 release (bugs Tagged

</td>

2.5.1_APPROVED) 

</tr>

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

<a

    - Changes for Pegasus 2.5.2 release (bugs Tagged

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

2.5.2_APPROVED)<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&">

</td>

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

nor

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

<o:p></o:p>

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

</td>

The Pegasus project is controlled largely through a set of documents

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

P2

modified Pegasus functionality and for the definition and documentation

<o:p></o:p>

of releases.

</td>

Specifically the following PEPs define the characteristics of this

Pegasus release.

PC

<ol>

<o:p></o:p>

<li>

</td>

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

</li>

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

<li>

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

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

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

Option  for Selected

</td>

Platforms</li>

</tr>

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

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

<li>

<a

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

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

</li>

</td>

<li>

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

nor

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

<o:p></o:p>

and also in the Pegasus

</td>

source

tree root directory).</li>

P2

<li>

<o:p></o:p>

<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

</td>

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

All

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

<o:p></o:p>

</ol>

</td>

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

The following documentation is available for the this Pegasus

Sample

release:

providers should not be declared in Pegasus namespace <o:p></o:p>

</td>

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

</tr>

combination of help generally available with the -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

<a

documentation - See the header files and the HTML  API

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

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

</td>

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

documentation.  In particular the Common/tests unit tests contain

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

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

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

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

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

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

</td>

documentation, and documentation from the Pegasus Technical Workshop

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

P2

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

<o:p></o:p>

Clients - API documentation and the documentation on the Pegasus

</td>

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

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

All

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

<o:p></o:p>

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

</td>

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

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

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

OpenPegasus web site.  While these are the original design

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

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

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

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

them

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

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1285">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>

</table>

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

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

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

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

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1307">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>

<a

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

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

MOF compiler does not handle "/* ... */" comments.

</td>

</tr>

1400</a></td>

maj</td>

P1</td>

All</td>

Disabling https prevents indication delivery through http.</td>

</tr>

</table>

<o:p></o:p>

<h2>List of Bugs Corrected in Pegasus 2.3

</h2>

The current bug list for Pegasus is openly available on the OpenPegasus web

site bug database.  This site defines the mechanism so that the user can list the bugs

that have been fixed between the release of Pegasus 2.2 and the current release.

<h2>Documentation</h2>

The following documentation is available for the this Pegasus release:

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

list .5in'>Pegasus Build and Installation - Readme in

the Pegasus Root Directory<o:p></o:p></li>

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

list .5in'>Pegasus Operation - Readme in the Pegasus

Root Directory<o:p></o:p></li>

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

list .5in'>APIs - See the header files and the HTML  API documentation that is

on the web site. <o:p></o:p></li>

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

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

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

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

list .5in'>API usage documentation - The best API usage documentation is

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

documentation.  In particular the

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

Common APIs.</li>

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

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

Directory, API documentation, and documentation from the Pegasus Technical

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

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

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

documentation on the Pegasus Technical Workshop which is available on the

Pegasus web site.</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>

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

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.3
changed lines
	Added in v.1.6.12.2

No CVS admin address has been configured