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

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

version 1.18.2.1, 2011/09/05 14:23:46

Line 1

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

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

<head>

<style>

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

</style>

Line 448

Line 449

margin:1.0in 1.25in 1.0in 1.25in;

mso-header-margin:.5in;

mso-footer-margin:.5in;

mso-paper-source:0;}

div.Section1

{page:Section1;}

Line 569

Line 571

text-indent:-.25in;}

@list l4:level7

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

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level8

Line 598

Line 601

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

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 963

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

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

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

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

name="City"/>

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

name="place"/>

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

name="date"/>

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

<o:DocumentProperties>

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

<o:LastAuthor> </o:LastAuthor>

Line 995

Line 992

</w:Compatibility>

<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>

</w:WordDocument>

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

</xml><![endif]--></head><body lang="EN-US" link="blue" vlink="blue">

Pegasus

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

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

PEP #: 359

Title: Release Notes Pegasus 2.3.2

Title: Release

Notes for OpenPegasus version 2.11.0 and version 2.11.1

Version: 1.5

Created: 23

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

March 2011

Authors: Karl

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

Schopmeyer

class=SpellE>Grunbok

                Karl

Status:  draft

Schopmeyer

Version History:

Status:  draft

<tbody>

Version History:

<o:p> </o:p>

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

</td>

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

<o:p> </o:p>

</td>

<span

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

<o:p> </o:p>

</td>

<span

<o:p> </o:p>

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

</td>

</tr>

<span

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

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

</td>

<span

23 March 2011

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

</td>

</tr>

Karl Schopmeyer

</td>

<span

Initial

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

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

</td>

</tr>

<st1:date

<tr>

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

23

<td style="padding: 0.75pt;" align="center" height="21">30 August 2011 </td>

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

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

</td>

<td style="padding: 0.75pt;" height="21">Updated to reflect Pegasus 2.11.1 release. Added covered properties to list of exceptions to DMTF specs.

</td>

<span

</tr>

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

</td>

Initial

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

</td>

</tr>

<tr>

<span

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

</td>

</tr>

<st1:date

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

4

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

</td>

<span

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>

Incorporate comments

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

</td>

</tr>

<o:p>

1.2/3</o:p>

</td>

<o:p>

15

April 2004</o:p>

</td>

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

<o:p>

Incorporate

comments from Second review</o:p>

</td>

</tr>

<span style='font-family:Arial;

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

1.4</o:p>

</td>

<span style='font-family:Arial;

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

April 2004</o:p>

</td>

<span style='font-family:Arial;

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

Schopmeyer</o:p>

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

Abstract: This document defines the release notes for the

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

2.11.0 release of the OpenPegasus CIM Server with notes to reflect the 2.11.1 revision. The purpose of this PEP

style='color:black'>

to summarize the characteristics of this release, point to other

documentation that defines the release in more detail, and provide

additional information about this release that is not available in the

</div>

other Pegasus documentation.

Abstract: This document defines the release notes that support

NOTE: This PEP is maintained both as a PEP on the Pegasus website

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

and is also available directly in the OpenPegasus source tree root

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

library as ReleaseNotes.htm

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>

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

<ol>

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

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

style='color:black'>

Release</a></li>

<li><a href="#Functionality_of_This_Release">OpenPegasus

Functionality of This Release</a></li>

<li><a href="#Compatibility_Considerations_">Compatibility

</div>

Considerations</a></li>

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

<o:p> </o:p>

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

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

<h2>Availability of the Release</h2>

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

with DMTF Specifications</a></li>

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

<li><a href="#PEGASUS%20Bugs">OpenPegasus Bug Fixes and Changes for this Release

The release can be downloaded from the OpenPegsaus Web

</a></li>

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

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

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

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

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

snapshot representing this release is RELEASE_2_3_2-snapshot_1 and the

Documentation</a></li>

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>

The overall level of functionality in the Pegasus environment effective with

this release is as follows:

CIM Server

CIM Operations over HTTP support

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

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

class=SpellE>deleteClass, modifyClass, <span

class=SpellE>enumerateClass, enumerateClassNames)

- Operational<a

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

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

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

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

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

<span

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

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

target="_self">

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

Indications

Process indications are operational in the Server.  This includes support

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

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

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

but the interfaces are marked experimental for version 2.3 because

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

available.

Query Language

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

filters.  However, the executeQuery operation

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

language.

Class Repository

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

access this repository.

Instance Repository

XML based file/directory Instance repository.  The instance repository

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

repository for client operations.

Security

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

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

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

<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

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

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

supported by OpenSSL.  Minimum level known

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

with 0.9.6k.  See <a

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

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

</ol>

Platform Management Functions

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

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

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

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

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

</ol>

<h2>Availability

SLP Discovery<a name="comtag_61">

of this Release</h2>

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

NOTE: This document defines

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

the OpenPegasus 2.11.0 version release with comments added to define

environment variable PEGASUS_ENABLE_SLP. Note that this release differs from

the 2.11.1 revision to that release.  OpenPegasus 2.11.1 is a bug

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

fix revision to Pegasus 2.11.0. The complete list of changes (total of

interoperable environment.� Also, the

32 bugs fixed)  is defined in OpenPegasus bugzilla with the <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.11.1_APPROVED">2.11.1_APPROVED bugs</a>

provider for the interop classes (CIM_ObjectManager,

query.  We recommend that all uses of 2.11.0 review this list.

CIM_Namespace,

OpenPegasus tries to execute only bug fixes for revision releases and

etc.) is enabled along with the SLP discovery.

not include enhancements but in exceptional cases including 2.11.1 some

If the SLP discovery is not enabled, these interop

extensions are included (See the Functionality of this Release

classes are also not available.

section). The OpenPegasus team recommends that users of Pegasus 2.11.0

update to Pegasus 2.11.1 because of of issues defined in a couple of

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

the bugs below, in particular an api incompatibility defined in bug

9014. Note that in OpenPegasus ALL changes including enhancements are

Pegasus 2.3.2 includes as a compilable option a

defined as bugs and committed only when the APPROVED keyword is set so

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

that the list in the query above defines ALL changes between 2.11.0 and

provider manager for the CMPI C interfaces.

2.11.1.

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

class=GramE>see� <a

This release is available in a number of forms including:

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

<ul>

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

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

which is in review now within the WBEMSource

These can be

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

downloaded from the OpenPegasus Web

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

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

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

<li>OpenPegasus source RPMs on the OpenPegasus web site..

providers.

A source RPM is  available on the

OpenPegasus web site that can be used to build binaries for most

Today, the CMPI provider manager and interfaces are considered experimental

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

and are subject to change in future versions of Pegasus.

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

release and

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

subsequent snapshots that are made available in the Pegasus CVS are

all conditionally compiled with the environment variables ENABLE_CMPI_PROVIDER_MANAGER

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

and ENABLE_PROVIDERMANAGER_2. See PEP 144 for details.

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>

</blockquote>

Providers

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

This includes providers in the following categories:

Internal (control) Providers

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

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

manipulation of namespaces.<a

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

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

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

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>

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

Generic Providers

WEB site</a>.

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

Generic OperatingSystem provider. See the

Pegasus source

directory src/Providers/generic.

tree.

</div>

Test/Sample Providers

<h2>OpenPegasus Functionality for This

See the directories src/Providers/TestProviders

Release</h2>Pegasus overall status by release is defined by  a

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

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

sample providers.

WEB Page</a>

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

Managed System Providers

shows the

Pegasus users and developers the status of the various features found

ComputerSystem, DNSAdmin,

in Pegasus

DNSService, Operating System, Process, Processor. For

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

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

description of

the directory src/Providers/ManagedSystem

each feature.

Pegasus 2.11.0

CIMOM Statistics Providers

is a major release, extending the previous Pegasus release in selected

areas as described in the Pegasus  PEP defining this release

IBMStatisticalData - This is an early version of

.

the work that became CIM_StatisticalData. It is

The major areas of development for this release  were as

similar to CIM_StatisticalData and provides the same

follows. Note that the bugs listed represent only those features

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

incorporated in bugs without PEPS that are considered enhancements, not

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

all bugs incorporated in the release. For

more information access the PEP/BUG for each change defined below:

</blockquote>

Table of Major

Changes for this Release

CIM_Schema

The default CIM_Schema loaded with this release is

<tbody>

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

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

directory.   CIM 2.8� schema is

<th bgcolor="#00ffff">Description of Change</th>

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

<th bgcolor="#00ffff" width="128">Posted PEP

The mechanism to switch to the the 2.8 schema is via

Version</th>

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

</tr>

<tr>

export PEGASUS_CIM_SCHEMA=CIM28

<td>Run 32 bit providers in 64 bit OpenPegasus</td>

NOTE: the CIM 2.5 schema is maintained in the

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

</tr>

environment.

Pegasus MOF Compiler

<td align="left" width="75%">Provider Module Grouping</td>

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

</td>

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

</tr>

repository (cimmofl).

<tr>

The direct interface compiler is used primarily to provide an initial

<td align="left" width="75%">SNMP V3 Trap Generation in Pegasus

class/instance repository. WARNING:

Indication Handler</td>

the use of cimmofl

to manipulate instances in the repository bypasses any provider that is

</tr>

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

<td style="text-align: center;" width="7%">PEP 324

are registered providers, 2) corruption of the repository if the CIM Server is

</td>

running or, 3) MOF data that is loaded but not available until the server is

<td align="left" width="75%">DMTF Indications Profile (DSP 1054)

stopped and restarted in some cases.  Use of cimmofl in

Implementation, stage 2

general is discouraged and particularly  to manipulate

</td>

instances served by a registered providers (ex.

Provider registration). Use of <span

</tr>

class=SpellE>cimmof rather that cimmofl

wherever possible.

<td style="text-align: center;" width="7%">PEP 349

</td>

Client Tools

<td align="left" width="75%">Improve the

availability of the CIMOM by better isolation from faulty providers</td>

Pegasus CIM Server Adminstration

</tr>

<tr>

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

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

</td>

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

<td>Add External SLP support to release builds

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

</td>

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

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

</a>

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

</td>

list .5in'>cimauth - Manage the CIM Server

</tr>

authorization characteristics. Today this is authorizing users to

<tr>

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

<td style="text-align: center;"> <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8800">Bug 8800

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

</a></td>

list .5in'>cimprovider - Manage information

<td> <a name="comtag_90"></a>enable

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

PEGASUS_USE_RELEASE_CONFIG_OPTIONS build option to have true/false

</ol>

values

</td>

Information client tools

</td>

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

</tr>

<tr>

<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8806">Bug

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

8806</a></td>

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

<td>Diagnose data for BAD UTF8 exception</td>

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

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

</tr>

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

<tr>

information on the Dmain Name System (DNS)

<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8825">Bug

configuration from CIM Classes. Note that the information generated is dependent

8825</a></td>

on the information available from providers and differs from system to

<td>Option to specify multiple provider dirs for release builds</td>

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

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

</tr>

list .5in'>ipinfo - Generates a set of standard

<tr>

information from the Network Schema.  Information generated varies by

<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8839">Bug

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

8839</a></td>

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

<td>OOP Provider recovery enhancement</td>

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

information on the Operating System from CIM Classes. Note that the

</tr>

information generated is dependent on the information available from

<tr>

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

<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8845">Bug

</ol>

8845</a></td>

<td><big><big>Enhance SSL Certificate info to

Test support Tools

expose the whole certificate</big></big>

</td>

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

</tr>

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

option on the Pegasus make files       

<td style="text-align: center;" width="7%"> <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8871">Bug 8871

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

</a> </td>

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

<td align="left" width="75%">Enhance WSMan Server Adpater

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

to include enumeration association filters</td>

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

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

</td>

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

</tr>

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

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

list .5in'>wbemexec - Test tool that

<td align="left" width="75%"> New runtime configuration options for Indication Service (2.11.1 Release)

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

</td>

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

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

</a></td>

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

</tr><tr>

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

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

</td>

See src/clients/benchmarkTest for more

<td style="vertical-align: top;">Correct issue with Provider

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

backward compatibility due to a new virtual function that was

</ol>

introduced in Pegasus 2.11.0 (2.11.1 release)

</td>

Pegasus Interface APIs

</td>

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

</tr>

available from the web site(<a

<tr>

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

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

extensions and new interfaces added for release 2.3 and these are shown as

experimental.   The Pegasus public

interfaces includes the following major functions

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

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

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

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>

<o:p> </o:p>

The APIs are documented in

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

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

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

WMI Mapper

The WBEM to WMI Mapper provides a way to access

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

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

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

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

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

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

authenticates these credentials, verifying if the provided credentials have

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

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

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

WMI Mapper impersonates the user credentials provided

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

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

contain user credentials.

<a

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

target="_self">

</a>Supported Platforms

<a

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>

</tbody>

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

</table>

</td>

The status of several components of Pegasus functionality change

status

HP aC++

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

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

that

</td>

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

release to this release</a> on the

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

WEB Page</a>.

Finally, a significant number of internal changes and corrections

were made

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

section below

for more information.

<h3>Information on  IPv6 Support (PEP 291)</h3>

NOTE: This functionality was incorporated in OpenPegasus

2.7.0 but it

was felt that the information below was worth repeating in subsequent

Release

Notes

IPv6 is

short for "Internet

Protocol

Version 6". IPv6 is the "next generation" protocol designed by the IETF

to replace the current version Internet Protocol, IP Version 4

("IPv4"). IPv6 Support for OpenPegasus is documented in <a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">

PEP

291</a>.

The IPv6 support in OpenPegasus is

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for

this

variable is "true"; setting this to

'false' before building OpenPegasus will disable the IPv6 support.

The following subsections provide

some information on IPv6 support for the Linux and Windows platforms.

Note that in the 2.6.1 release there is no automatic run-time detection

of IPv6 support on a platform by OpenPegasus. If you build with

PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you will

get a build failure (missing header files), a run-time bind() failure,

or possibly some other failure. This applies to both the CIM Server and

Listener components. For more information on IPv6 support for your

specific platform, refer to the documentation for that platform.

All OpenPegasus externals that

support either a hostname or an IP address as input have been updated

to allow an IPv6 address to be specified. If the required input is just

an IP address (eg. no optional or required port number), then the IPv6

address must be specified without brackets. For example, the

OpenPegasus osinfo client (which returns information about the OS

running on a host system) takes separate host and port options. In this

case a host with an IPv6-configured network interface would be

specified as:

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>osinfo -h

3ffe:1:2:1 -p 5988</big></div>

But the cimcli command, which

takes

an optional "location" option including an optional port number,

requires the IPv6 address to be delimited with brackets, for example:

<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns

-l [3ffe:1:2:1]</big></div>

or

<div style="margin-left: 40px;"><big>cimcli ns -l [3ffe:1:2:1]:5989</big>

</div>

For more information on

specifying

IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF

RFC 2373 - IP Version

6 Addressing Architecture</a>

and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 -

Format for

Literal IPv6 Addresses in URL's</a>.

<h4>IPv6 on Linux</h4>

Modern Linux distributions already

contain IPv6-ready kernels, the

IPv6 capability is generally compiled as a module, but it's possible

that this module is not loaded automatically on startup.

Note:

you shouldn't use kernel series 2.2.x, because it's not

IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no

longer improved according to definitions in latest RFCs. It's recommend

to use series 2.6.x now.

To check whether your current

running

kernel supports IPv6, take a look into your /proc filesystem. The entry

/proc/net/if_inet6 must exist. A short automated test looks like:

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>test -f

/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"</big></div>

For more information on

enabling

IPv6 in the Linux kernel and configuring network interfaces, refer to

<a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux

Documentation Project's IPv6 HOWTO</a>.

Warning:

There is currently an open issue with RedHat to address a problem that

is seen intermittently on RHEL5 and SLES10 systems. This problem is

described in

<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus

bug 6586</a>

and

<a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat

bug 248052</a>,

and manifests itself as an intermittent IPv6 socket failure. You

should be aware

that OpenPegasus with IPv6 enabled may be significantly impacted in

these

environments.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6

implementations for Windows Server

2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service

Pack 2 (SP2), and Windows CE .NET 4.1 and later.

On Windows XP, you can use the ipv6.exe

tool to install, uninstall, and

query

your IPv6 configuration. For example:

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>ipv6 install

ipv6 if</big></div>

Windows Vista

and Windows Server 2008 support an integrated

IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack.

Note that the OpenPegasus IPv6 support has not yet been tested

on Windows Vista or Windows Server 2008.

For more information on

installing, configuring, and using IPv6 on Windows platforms, refer to

the document

<a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx">IPv6

for Microsoft Windows: Frequently Asked Questions</a>.

<h4>Testing your OpenPegasus IPv6

support</h4>

As part of the OpenPegasus

automated tests, the TestClient, g11ntest, and IndicationStressTest

test clients were modified to run tests using the IPv6 loopback address

(::1) if PEGASUS_ENABLE_IPV6=true.

You can also perform manual

tests

using the IPv6 loopback or a real IPv6-configured network interface.

For example, using the IPv6 loopback on a system with OpenPegasus

running on the WBEM standard http port of 5988:

<big style="font-family: monospace;"> osinfo -h ::1</big></div>

<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2>

Support for forward-compatibility is a fundamental design principle

for the

OpenPegasus project. As a Community, our goal is for well-behaved

OpenPegasus

Providers or Clients, using only the externally defined OpenPegasus

interface,

to continue to work with a minor version upgrade of OpenPegasus.

However, there

are certain classes of errors (e.g., non-compliance with a standard

that

significantly affects interoperability) that may require the Community

to make

potentially incompatible changes. The following table contains a list

of defect

fixes that MAY impact, even well-behaved, OpenPegasus Providers or

Clients when

upgrading to this OpenPegasus release.

<tbody>

<th bgcolor="#00ffff" width="10%">Bugzilla #</th>

<th bgcolor="#00ffff">Description</th>

</tr>

PowerLinux<span

<td align="left">The requirement for providers (CMPI and C++) to

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

filter properties from instances has been relieved. The server will do

</td>

the filtering at the protocol adapter level. To avoid a negative impact

on performance the CIMInstance::filter() and

gcc<span

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

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

NOP. This may be a change in behavior for provider relying in some

</td>

unknown way on the instance being filtered through these functions. To

allow users to actually filter properties from an instance, new

function CIMInstance::filterInstance() will actually filter properties

from an instance exactly as the CIMInstance::filter() did in previous

versions of Pegasus.</td>

</tr>

<td>

zLinux<span

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

</td>

<td>

gcc<span

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

</td>

</tr>

<td>

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

</td>

<td>

gcc<span

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

</td>

</tr>

<td>

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

</td>

<td>

gcc<span

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

</td>

</tr>

<td>

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

</td>

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

</tbody>

</table>

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

<h2>OpenPegasus Relationship to

</td>

CIM/WBEM Standards</h2>

Pegasus was designed and implemented to comply with the DMTF

Microsoft

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

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

DMTF specifications to which this version of Pegasus aims to conform

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

today.

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

</td>

<tbody>

<tr>

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

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

</tr>

<tr>

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

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

</tr>

<tr>

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

<td width="33%">Version 1.2, Final, January 09, 2007</td>

</tr>

<tr>

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

<td width="33%">Version 2.2 Final, January 09, 2007</td>

</tr>

<tr>

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

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

</tr>

<tr>

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

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

</tr>

<tr>

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

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

</tr>

<tr>

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

<td width="33%">2.22.1 Final,  22 Oct 2009( default) </td>

</tr>

</tbody>

</table>

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

Exceptions to

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

DMTF Specifications</a></h2>

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>

It is a major goal

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. 

specifications.  However, today there are a number of known

As of Pegasus 2.3.2, some of the differences include the following:

differences. 

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

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

<ol>

Provider registration classes and does not support the DMTF defined Provider

<li>Provider Registration - Pegasus supports registration

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

through a set of Pegasus Provider registration classes rather than

support the DMTF defined Provider Qualifier. Pegasus will not support

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

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

include any specific support for lifecycle indications.

provider registration.  This is not a deviation from the

specifications but is a different method of registration than many CIM

3. Interop Schema implementation differences.

Servers and means that the the provider qualifier is unused in Pegasus.</li>

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

<li>Indications -Today Pegasus supports process

class=SpellE>Interop Schema including CIM_StatisticalData.

indications and lifecycle indications when defined specifically by

Note that the CIM_ObjectManager and other similar

providers. Pegasus does not support lifecycle indications if they are

classes are only compiled with the SLP option.

not defined by the provider or for changes to CIM Classes.  For

more information see the Pegasus CVS file:<a name="comtag_137">  pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

<li>

IncludeQualifiers

option on Instance Operations

The DMTF specifications have deprecated the use of qualifiers on

instance operations with the 1.2 CIM Operations Specification and

stated specifically that the client should NOT depend on the

includeQualifiers parameter of the CIM/XML instance operations

returning qualifiers. 

Some CIM Client implementations expect instances

returned

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

definition (such as KEY qualifiers on properties).   Pegasus

today expects the provider to complete the qualifiers on instances in

accordance with the specification and generally the interpretation is

that Pegasus applies class level qualifiers when the includeInstance

parameter is supplied on instance operations.  However, Pegasus

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

should NOT depend on Pegasus accurately honoring the includeQualifier

parameter for instance operations.  In the future it is expected

that Pegasus will deprecate the use of qualifiers on instance

operations completely.  When Pegasus uses object normalization,

the normalizer does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.

</li>

<li>LocalOnly option on instance

Operations - With the 1.1 version of Specification for CIM

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

GetInstance and Enumerate Instances operations was modified. This

change

was incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

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

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

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

specification for more information.</li>

<li>

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOF Compiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

</li>

<li>CIMOperation Trailer - Pegasus implements

chunking

based on the DSP0200 1.2.0 preliminary spec. including the operation

trailer defined in that specification Refer to bug <a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a>

for more details. This trailer was completely removed from the DSP0200

1.2 final specification as a non-compatible change so that if chunking

is used Pegasus is returning a noncompliant response to enumerate type

requests. </li>

<li>Whitespace in XML value Element

- Pegasus trims the leading and trailing whitespace from XML value

elements that are of the Type String.  This behavior is documented

in Pegasus bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8773">8773</a>

and there is a patch available for users.  However, since the

change is considered a change to behavior this will not be patched

until pegasus does a major version update. NOTE: There are some

documented bugs in Pegasus such as this that the OpenPegasus team feels

cannot be modified until a major version update.  These bugs are

documented with the Bugzilla tag <big style="font-weight: bold;"><samp>"3.0_TARGET".</samp></big></li>

<li>modifyInstance operation

behavior in the Pegasus repository does not match the DMTF specification.

Under some conditions (ex. if no propertyList is supplied) it modifies

all properties rather than just the properties supplied with the

request thereby Nulling out existing values. See bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8752">8752</a>

for more information.</li>

<li>Covered Properties (multiple properties with the same name but different class origin)

- The DMTF Spec DSP0004 now defines the requirement for covered

properties. However, OpenPegasus does not support this capability (see <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">bug 3571</a>)

</li>

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>

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

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

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

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

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>

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

list .5in'>Pluggable

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

were extensive and released very late in the development

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

</ol>

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

The set of PEPs defined for release 2.3 is below

Platforms</a></h2>

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

Each OpenPegasus release lists as 'active' platforms

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

those

available on the OpenPegasus web site.

hardware/software platforms that have recognized ports for the Pegasus

code base

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

including a maintainer for the platform that will be willing to

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

regularly

document issues and/or fix defects as the Pegasus code base is

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

changed. 

height:13.5pt'>

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

PEP #<span

a group

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

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

</td>

Pegasus

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

cannot be assured.  In all cases, including the active platforms,

height:13.5pt'>

it is the

PEP Description<span

responsibility of the entity that packages and/or compiles OpenPegasus

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

for

</td>

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

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

bugzilla

height:13.5pt'>

database for a list of relevant defects that affect their

Status<span

platform.  

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

The platforms that are considered ported are shown in the two tables

</td>

below. 

</tr>

The first table represents platform sofr which testing is done on a

regular

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

basis and reported to the Pegasus Nightly Build Test WEB Page. Those

height:13.5pt'>

platforms

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

which have been ported but do not have test results that are current at

</td>

the time

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

of the release are reported in the second table.

height:13.5pt'>

Actively Supported Platforms (Nightly Tests Reported for this

Unicode Support in

release)

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

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

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

height:13.5pt'>

</td>

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

</tr>

</td>

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

height:13.5pt'>

HP-UX<o:p>

Unicode Support in

PA_RISC and Itanium</o:p>

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

</td>

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

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

height:13.5pt'>

</td>

<a

</tr>

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>

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

</td>

</tr>

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

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

</td>

height:13.5pt'>

</tr>

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

</td>

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

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

height:13.5pt'>

</td>

Provider Manager Interface -

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

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

</td>

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

</tr>

height:13.5pt'>

Implemented - but requires

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

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

</td>

</tr>

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

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

</td>

height:13.5pt'>

</tr>

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

</td>

<td style="padding: 0.75pt;"> Linux IA-32</td>

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

<td style="padding: 0.75pt;"> gcc

height:13.5pt'>

(versions 3.xx, 4.xx)<o:p></o:p></td>

Provider Manager Interface,

</tr>

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

</td>

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

Linux X86_64<o:p></o:p>

height:13.5pt'>

</td>

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

</td>

gcc

</tr>

(versions 3.xx, 4.xx)

</td>

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

</tr>

height:13.5pt'>

<tr>

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

</td>

<td style="vertical-align: top;">XL C/C++ from

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

z/OS Version 1.7 and up</td>

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>

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

height:13.5pt'>

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

</td>

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

height:13.5pt'>

SNMP Mapper

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

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

height:13.5pt'>

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

</td>

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

height:13.5pt'>

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

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

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

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

</td>

</tr>

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

height:10.5pt'>

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

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

</td>

</tr>

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

height:10.5pt'>

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

</td>

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

height:10.5pt'>

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

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

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

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

</td>

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

height:10.5pt'>

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

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

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

</td>

</tr>

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

height:10.5pt'>

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

</td>

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

height:10.5pt'>

Support CIM Schema 2.8

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

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

</td>

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

height:10.5pt'>

WMI Mapper

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

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>

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

height:10.5pt'>

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

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

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

height:10.5pt'>

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>

<td width="20%" style='width:20.26%;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=306"

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

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>

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

</td>

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>

Platforms not Actively supported for this release

(No

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

current Nightly Build Test Results

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

<tbody>

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,

patches, etc. for particular bugs.

Platform and

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

<o:p> </o:p>

</td>

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

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

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

</td>

</tr>

<tr>

<span

<td style="padding: 0.75pt;"> Windows XP

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

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

</td>

<o:p></o:p>

<td style="padding: 0.75pt;"> Microsoft Visual

</td>

C++ Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++

Ver. 6 no longer being regular tested. </td>

<span

</tr>

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

<td style="padding: 0.75pt;"> MacOS version 10.3

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

and higher</td>

</td>

</tr>

<span

<tr>

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

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

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

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

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

</td>

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

</td>

<span

</tr>

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

<tr>

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

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

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

</td>

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

</td>

<span

</tr>

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

<tr>

<td><big>HP OpenVMS 8.3 or later Alpha</big></td>

<o:p></o:p>

<td><big>HP C++ V7.3-009 or later required for

</td>

OpenVMS

</tr>

Alpha</big></td>

</tr>

<tr>

<a

<td><big> HP OpenVMS 8.3 or

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

later IA64</big></td>

</td>

<td><big>HP C++ V7.3-023 or later required on OpenVMS IA64</big></td>

</tr>

nor

<tr>

<o:p></o:p>

</td>

Windows 2000

</td>

P2

<td style="padding: 0.75pt;"> Microsoft Visual

<o:p></o:p>

C++ Ver.  6 and Microsoft .Net compiler version. Works on VC

</td>

.NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being regularly

tested.</td>

All

</tr>

<o:p></o:p>

<tr>

</td>

<td style="padding: 0.75pt;"> Windows 2003

MOF

</td>

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

<td style="padding: 0.75pt;"> Microsoft Visual

</td>

C++ Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++

</tr>

Ver. 6 no longer being regular tested. </td>

</tr>

<tr>

<a

<td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and

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

IX86)</big></td>

</td>

<td><big>CC Compiler Sun Studio 5.11</big></td>

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

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

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

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

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

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

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

</td>

</tr>

<a

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

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

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

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

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

</td>

</tr>

<a

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

</td>

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

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

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

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

Absence

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

</td>

</tr>

<a

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

MOF

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

</td>

</tr>

<a

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

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

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

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

"Times New Roman"'> enumerateinstances <span

class=SpellE>deepInheritance, etc. procesing

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1054">1054</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"'>cimserver<span style='mso-fareast-font-family:

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

</td>

</tr>

<a

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

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

Sample

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

</td>

</tr>

<a

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

</td>

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

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

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

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

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

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

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

them

</td>

</tr>

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

</tbody>

</table>

Platform patches

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

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

The following is a list known of platform

patches Pegasus requires.

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

<ol>

<li>

RHAS

<a

2.1 needs the update to fix Red Hat Bugzilla 98815.

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

</li>

</td>

<li>

RHEL 4.4

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

multithreading bug in

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

getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is

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

fixed in

</td>

RHEL 4.5

</li>

P2

<li>

<o:p></o:p>

Red Hat and SUSE

</td>

Linux multiple versions -

multithreaded client intermittently fails connecting to IPv6 (Pegasus

All

Bugzilla

<o:p></o:p>

6586) (Red Hat bug 248052)

</td>

</li>

Functionality on errors with Enumerate Functions. Should we

</ol>

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

</div>

</td>

Further information regarding Pegasus support on IBM platforms can

</tr>

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>

<a

Further information regarding Pegasus support on HP platforms can

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

</td>

found at:

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

nor

<h2><a name="PEGASUS Bugs">Pegasus Defects Fixed and Changes for this Release

<o:p></o:p>

</a></h2>

</td>

The Pegasus bugzilla database documents any defects found in Pegasus

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

P2

database</a>.

<o:p></o:p>

Effective with the start of the Pegasus 2.6 work, all changes to the

</td>

CVS tree are documented through bugs.  Bugs reports are filed not

only for bugs and

PC

their corresponding fixes but also as part of the process of committing

<o:p></o:p>

new code

</td>

representing the work on PEPs done for Pegasus 2.6 and all subsequent

versions.  Therefore, a search of

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

the Open Pegasus bugzilla base for bugs with the tag for a particular

</td>

version

</tr>

(ex. 

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

2.6.1_APPROVED</a>,

1400</a></td>

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

etc) will yield all changes to

maj</td>

the Pegasus CVS tree for that Pegasus release.

P1</td>

     - Changes for this release (bugs Tagged

2.11.0_APPROVED). The link is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.11.0_APPROVED">

All</td>

Pegasus 2.11.0_APPROVED bug list.</a>

     - (2.11. 1) Changes between the 2.11.0 release

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

and 2.11.1 revision are defined in bugs tagged (2.11.1.APPROVED). The

</tr>

complete list of 32 bugs is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.11.1_APPROVED">2.11.1_APPROVED bugs</a>.

</table>

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

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

<o:p></o:p>

The Pegasus project is controlled largely through the CVS repository

and a set of documents

<h2>List of Bugs Corrected in Pegasus 2.3

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

</h2>

and

modified Pegasus functionality and for the definition and documentation

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

of releases.

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

The following documentation defines the characteristics of this Pegasus

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

release. The documents are available in the OpenPegasus CVS

repository.

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

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

style='color:black'>

</div>

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

Permission is hereby granted, free of

<ul>

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

<li> OpenPegasus Release Definition/Status -No PEP (See Wiki

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

Section <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_11_x">OpenPegasus

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

2.11.x Release Status</a>) - A

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

section in the Pegasus wiki is used

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

throughout the development of this version as the control point for

following conditions:

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

PEPs that represent the Pegasus  functionality changes for this

THE ABOVE COPYRIGHT NOTICE AND THIS

version of Pegasus. </li>

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

OpenPegasus

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

Build and Configuration

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

Options  for Selected

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

Platforms -  In previous

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

versions of Pegasus this information was  released as a Pegasus

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

PEP. Starting with Pegasus 2.9.0 the information is located in the

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

OpenPegasus CVS repository as <big style="font-weight: bold;"> pegasus/doc/BuildAndReleaseOptions.html</big>.

THE USE OR OTHER DEALINGS IN THE SOFTWARE.

<li> OpenPegasus External Interfaces -The list of the OpenPegasus interfaces

that are considered external and therefore "frozen". Unless an

exception is explicitly approved by the Steering Committee all

subsequent releases of Pegasus MUST continue to support these

interfaces. Interfaces not explicitly listed in this document, should

be considered as internal and subject to change.In previous Pegasus

releases this information was available as a separate PEP. Starting

with Pegasus 2.9.0 this information is integrated into the Pegasus

repositoryas  pegasus/doc/EnternalInterface.html.</li>

<li> OpenPegasus  SDK Packaging Definition - Defines the recommended set of files for

inclusion in the OpenPegasus

SDK. Starting with Pegasus release 2.11.0, this document is available

in the Pegasus CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>.

previous Pegasus releases this document was made available as s

separate Pegasus PEP document rather than in the CVS repository.

</li>

<li> Pegasus  Runtime Packaging Definition

- Defines the recommended set

of files for inclusion in this OpenPegasus

release. Starting with Pegasus release 2.11.0, this idocument contained

in the CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/RuntimePackaging.html</samp></big>.

In previous

releases this was made available as a seperate Pegasus PEP document

rather than in the CVS repository.  </li>

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

approved PEP repository and the OpenPegasus source tree root directory (<big style="font-weight: bold;">pegasus/ReleaseNotes.htm</big>)</li>

</ul>

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

The following documentation is available for the this Pegasus

release:

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

A

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

command and HTML documentation for most of the tools.<o:p></o:p> <li class="MsoNormal" style="color: black;">API and  usage

documentation - </li>

See the header files and the HTML  API

documentation that is on the web site. 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 class="MsoNormal" style="color: black;">Building and Debugging

Providers - </li>

Readme.html in the Pegasus source tree Root Directory, API

documentation, and documentation from the Pegasus Technical Workshop

which is available on the Pegasus web site. <li class="MsoNormal" style="color: black;">Building and Debugging

Clients - </li>

API documentation and the documentation on the Pegasus

Technical Workshop which is available on the Pegasus web site. <li class="MsoNormal" style="color: black;">PEPs - </li>

The

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

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

OpenPegasus web site.  While these are the original design

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

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

the design and implementation of these features.

</ul>

<hr>Licensed to The Open Group (TOG) under one or more contributor

license

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with

this work for additional information regarding copyright ownership.

Each contributor licenses this file to you under the OpenPegasus Open

Source License; you may not use this file except in compliance with the

License.

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

obtaining a

copy of this software and associated documentation files (the

"Software"),

to deal in the Software without restriction, including without

limitation

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

sublicense,

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

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

The above copyright notice and this permission notice shall be

included

in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,

EXPRESS

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY

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

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

SOFTWARE OR 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.18.2.1

No CVS admin address has been configured