pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.16 and 1.18.2.1

version 1.16, 2009/01/28 16:20:14

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

Line 1

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

<style>

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

</style>

Line 961

Line 963

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

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

<o:DocumentProperties>

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

Line 990

Line 992

</w:Compatibility>

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

</w:WordDocument>

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

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

Pegasus

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

PEP #: 359

PEP #: 345

Title: Release

Notes for OpenPegasus 2.9.0

Notes for OpenPegasus version 2.11.0 and version 2.11.1

Created: 23

Created: 05 January 2009

March 2011

Authors: Karl

Authors: Karl Schopmeyer

Schopmeyer

Status:  draft

Version History:

<tbody>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

</tr>

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

</td>

23 March 2011

05 January 2009

</td>

Karl Schopmeyer

Karl Schopmeyer

</td>

Initial

Submission <o:p>

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

</o:p>

</td>

</tr>

<tr>

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

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

<td style="padding: 0.75pt;" align="center" height="21">16 Jananuary 2008</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>

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

<td style="padding: 0.75pt;" height="21">Update with comments from 1.0 incorporated.</td>

</tr>

</tr>

<tr>

</tr>

</tr>

</tbody>

</table>

Abstract: This document defines the release notes for the

2.9.0 release of the OpenPegasus CIM Server. The purpose of this PEP is

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

to summarize the characteristics of this release, point to other

documentation that defines the release in more detail, and provide

additional information about this release that is not available in the

other Pegasus documentation.

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

and is also available directly in the OpenPegasus source tree root

library as ReleaseNotes.htm

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

<ol>

Line 1154

Line 1093

Release</a></li>

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

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

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

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

Considerations</a></li>

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

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

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

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

with DMTF Specifications</a></li>

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

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

</a></li>

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

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

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

Line 1168

Line 1109

</ol>

<h2>Availability

of this Release</h2>

NOTE: This document defines

the OpenPegasus 2.11.0 version release with comments added to define

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

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

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>

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

OpenPegasus tries to execute only bug fixes for revision releases and

not include enhancements but in exceptional cases including 2.11.1 some

extensions are included (See the Functionality of this Release

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

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

9014. Note that in OpenPegasus ALL changes including enhancements are

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

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

2.11.1.

This release is available in a number of forms including:

<ul>

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

These can be

downloaded from the OpenPegasus Web

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

<li>OpenPegasus source RPMs on the OpenPegasus web site.. A source RPM is  available on the

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

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

A source RPM is  available on the

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

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

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

release and

subsequent snapshots that are made available in the Pegasus CVS are

Line 1190

Line 1150

tree.

</div>

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

<h2>OpenPegasus Functionality for This

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

Pegasus overall status by release is defined by  a

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

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

WEB Page</a>

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

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

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

shows the

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

Pegasus users and developers the status of the various features found

each feature.Pegasus 2.9.0

in Pegasus

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

description of

each feature.

Pegasus 2.11.0

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

areas as described in the Pegasus  PEP defining this release

.

The major areas of development for this release  were as

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

follows. Note that the bugs listed represent only those features

more information access the PEP for each change defined:

incorporated in bugs without PEPS that are considered enhancements, not

all bugs incorporated in the release. For

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

Table of Major Changes for this Release

Table of Major

Changes for this Release

<tbody>

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

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

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

Version</th>

</tr>

<tr>

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

</tr>

<td align="left" width="75%">WS-Management Support in CIM Server - Phase II</td>

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

</td>

</tr>

<tr>

<td align="left" width="75%">SQLite Repository</td>

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

Indication Handler</td>

</tr>

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

<td align="left" width="75%">In-Memory-Tracing</td>

</td>

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

Implementation, stage 2

</td>

</tr>

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

<td align="left" width="75%">Solaris 11 (Nevada) support for CC compiler and IX86</td>

</td>

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

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

</tr>

<tr>

<tr><td style="text-align: center;">Bug 7902</td><td>Allow modifyClass on non-leaf class</td><td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=7902">7902</a></td></tr><tr><td style="text-align: center;">Bug 7996</td><td>64 bit platform support for z;/OS</td><td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=7996">7996</a></td></tr><tr align="center">

</td>

<td style="text-align: center;" width="7%">Bug 8074 </td><td align="left" width="75%">Significant performance enhancement in out-of-process providers (~ 300%) through binary protocol</td>

<td>Add External SLP support to release builds

</td>

</a>

</td>

</tr>

<tr>

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

</a></td>

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

PEGASUS_USE_RELEASE_CONFIG_OPTIONS build option to have true/false

values

</td>

</td>

</tr>

<tr>

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

8806</a></td>

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

</tr>

<tr>

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

8825</a></td>

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

</tr>

<tr>

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

8839</a></td>

<td>OOP Provider recovery enhancement</td>

</tr>

<tr>

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

8845</a></td>

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

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

</td>

</tr>

<td style="text-align: center;" width="7%">Bug 8171</td><td align="left" width="75%">Access to binary protocol for clients </td>

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

</a> </td>

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

to include enumeration association filters</td>

</td>

</tr>

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

</td>

</a></td>

</tr><tr>

</td>

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

backward compatibility due to a new virtual function that was

introduced in Pegasus 2.11.0 (2.11.1 release)

</td>

</td>

</tr>

<tr>

</td>

</td>

</td>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality change status

The status of several components of Pegasus functionality change

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

status

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

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

that

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

<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

Finally, a significant number of internal changes and corrections

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

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

NOTE: This functionality was incorporated in OpenPegasus

was felt that the information below was worth repeating in subsequent Release

2.7.0 but it

was felt that the information below was worth repeating in subsequent

Release

Notes

IPv6 is short for "Internet

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

Line 1272

Line 1321

PEP

291</a>.

The IPv6 support in OpenPegasus is

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this

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.

Line 1303

Line 1353

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>

<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

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

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

Line 1344

Line 1397

described in

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

bug 6586</a>

and

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

and manifests itself as an intermittent IPv6 socket failure. You should be aware

should be aware

that OpenPegasus with IPv6 enabled may be significantly impacted in these

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

On Windows XP, you can use the ipv6.exe

tool to install, uninstall, and

query

your IPv6 configuration. For example:

Line 1372

Line 1426

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

IPv6

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

<h4>Testing your OpenPegasus IPv6

Line 1388

Line 1441

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:

osinfo -h ::1</big></div>

<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

Support for forward-compatibility is a fundamental design principle

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

for the

Providers or Clients, using only the externally defined OpenPegasus interface,

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

to continue to work with a minor version upgrade of OpenPegasus. However, there

OpenPegasus

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

Providers or Clients, using only the externally defined OpenPegasus

significantly affects interoperability) that may require the Community to make

interface,

potentially incompatible changes. The following table contains a list of defect

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

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

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>

<tr><td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8229">8229</a></td><td>The Common Information Model (CIM) Infrastructure Specification (DSP0004)

version 2.3 contains this statement in section 3.2: "If the specification

references a class without defining it first, the server must reject it as

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

invalid if it does not already have a definition of that class."

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

Previously, this check was only performed for derived classes. In

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

Pegasus 2.9, the check is also done for base classes. This may cause a

on performance the CIMInstance::filter() and

MOF file that previously loaded without problem to generate an error if it

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

contains a forward reference. Note that the CIM 2.13.1 schema in the

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

Pegasus source repository contained such an error in Pegasus 2.8, which is

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

also corrected in Pegasus 2.9.</td></tr><tr align="center">

allow users to actually filter properties from an instance, new

function CIMInstance::filterInstance() will actually filter properties

<td align="left">In Pegasus 2.8, the behavior of the setName() method was

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

changed in the Pegasus C++ interface for the CIM data type model. For

versions of Pegasus.</td>

data types that use a shared representation model, the setName() method

now throws an Exception when the object is "contained" by another CIM

data object.

Specifically, setName() may throw the new exception in these cases:

CIMProperty contained by CIMClass, CIMInstance, and CIMObject

CIMQualifier contained by CIMClass, CIMInstance, CIMObject,

CIMProperty, CIMParameter, and CIMMethod

CIMMethod contained by CIMClass

CIMParameter contained by CIMMethod</td>

</tr>

<td>

<td>

</td>

In Pegasus 2.8, the C++ CMPI IndicationMI function

<td>

signatures were changed to fit the CMPIIndicationMIFT definitions.

</td>

The CmpiResult parameter in CmpiIndicationMI authorizeFilter, mustPoll,

activateFilter and deActivateFilter have been removed cause it does not

exist in the CMPIIndicationMIFT definitions.

The missing CmpiContext parameter and CMPIStatus have been added to

enableIndications and disableIndications.</td>

</tr>

<td>

<td>

</td>

In Pegasus 2.8, the CMPI property filter handling performance was improved.

<td>

Two things have changed in the behaviour of the property filter

</td>

handling:

* Repeated applying of property filters onto the same instance will now

only leave the properties which build the most common dominator on the

instance.

* It is not possible anymore to add properties not defined for the

corresponding class to an instance.</td>

</tr>

<td>

<td>

</td>

In Pegasus 2.8, the algorithm used by the MessageLoader

<td>

to search the accept language list to determine which message file to

open was changed. Before Pegasus 2.8, the Message Loader used the

following algorithm:

1.) The Message Loader will search the accept

language list for an exact match. The first exact match found will

be returned.

2.) If an exact match does not exist, the Message Loader will return

an ICU "fallback" match for the first entry in accept language list.

3.) If an ICU "fallback" match does not exist for the first entry,

it will return the ROOT resource bundle.

</blockquote>

With the release of Pegasus 2.8, the Message Loader no longer returns ICU "fallback" matches. In addition, it gives

preference to the default process locale over the ROOT resource bundle.

In Pegasus 2.8, the Message Loader was modified to use the

following algorithm:

<ul>

1.) The Message Loader will search the accept

language list for an exact match. The first exact match found will

be returned.

2.) If an exact match does not exist, the Message Loader will return

an exact match for the default process locale.

3.) If an exact match for the default process locale is not found,

it will return the ROOT resource bundle.

</ul>

</td>

</tr>

<td>

7501</a></td>

</td>

<td>

<td>

Since OpenPegasus 2.7.2 the way CMPI_chars are added to

</td>

arrays was corrected to follow the CMPI specification. Following the

CMPI specification means that CMPI_chars are not to be dereferenced,

contrary to all other subtypes of CMPIValues.

If you experience an error since switching over to OpenPegasus 2.8

saying "The byte sequence starting at offset xx is not valid UTF-8

encoding", this is an indication for a missing update in the provider

code.

The update for a C CMPI provider using arrays of CMPI_chars is to use a

char* now as input parameter instead of a char**.

CMPI Example:

char* role = "Unknown";

array = CMNewArray(_broker,1,CMPI_chars,rc);

from:

CMSetArrayElementAt(array,0,(CMPIValue*)&role,CMPI_chars);

to:

CMSetArrayElementAt(array,0,(CMPIValue*)role,CMPI_chars);</td>

</tr>

</tbody>

</table>

Line 1547

Line 1546

</tr>

<tr>

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

<td width="33%">2.17.1 Final,  14 Dec 2007( default) </td>

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

</tr>

</tbody>

</table>

Line 1571

Line 1570

indications and lifecycle indications when defined specifically by

providers. Pegasus does not support lifecycle indications if they are

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

more information see the Pegasus CVS file:<a name="comtag_137">

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

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. 

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

Line 1591

Line 1592

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.

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

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

Line 1604

Line 1608

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

specification for more information.</li>

<li>

MultiRequest Operations - Pegasus

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOF Compiler namespace pragma - The

MOF Compiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

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

based on the DSP0200 1.2.0 preliminary spec. including the operation

defined in that specification Refer to bug

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

<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> for more details.

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

This trailer was completely removed from the DSP0200 1.2 final specification

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

as a non-compatible change so that if chunking is used Pegasus is returning

is used Pegasus is returning a noncompliant response to enumerate type

a noncompliant response to enumerate type requests.

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>

</ol>

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

Platforms</a></h2>

Each OpenPegasus release lists as 'active' platforms those

Each OpenPegasus release lists as 'active' platforms

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

those

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

hardware/software platforms that have recognized ports for the Pegasus

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

code base

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

including a maintainer for the platform that will be willing to

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

regularly

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

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

responsibility of the entity that packages and/or compiles OpenPegasus for

changed. 

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

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

database for a list of relevant defects that affect their platform.  

a group

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

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

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

Pegasus

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

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

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

it is the

of the release are reported in the second table.Actively Supported Platforms (Nightly Tests Reported for this release)

responsibility of the entity that packages and/or compiles OpenPegasus

for

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

bugzilla

database for a list of relevant defects that affect their

platform.  

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

below. 

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

regular

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

platforms

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

the time

of the release are reported in the second table.

Actively Supported Platforms (Nightly Tests Reported for this

release)

<tbody>

Platform and

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

</td>

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

</td>

</tr>

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

HP-UX<o:p>

PA_RISC and Itanium</o:p>

</td>

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

Line 1682

Line 1723

</td>

</tr>

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

Linux IA-32</td>

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

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

gcc

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

</tr>

Line 1694

Line 1733

</td>

gcc

(versions 2.9x, 3.xx, 4.xx)

(versions 3.xx, 4.xx)

</td>

</tr>

Windows 2000

</td>

Microsoft Visual C++ Ver.  6 and Microsoft .Net compiler version. Works on VC .NET 2003 v7.1).

NOTE: Visual C++ Ver. 6 no longer being regularly tested.</td>

</tr>

<tr>

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

</td>

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

Note: Visual C++ Ver. 6 no longer being regular tested.

</td>

</tr>

<tr>

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

<td style="vertical-align: top;"> <big>HP C++ V7.3-009 or later required for OpenVMS

Alpha</big></td>

</tr>

<tr>

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

<td style="vertical-align: top;"><big>HP C++ V7.3-023 or

later required on OpenVMS IA64</big></td>

</tr>

<tr>

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

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

1.7 and up</td>

z/OS Version 1.7 and up</td>

</tr>

</tbody>

</table>

Platforms no Actively supported for this release (No

Platforms not Actively supported for this release

(No

current Nightly Build Test Results

<tbody>

Platform and

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

</td>

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

</td>

</tr>

<tr>

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

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

</td>

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

Note: Visual C++ Ver. 6 no longer being regular tested.

</td>

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

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

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

</tr>

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

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

and higher</td>

</tr>

<tr>

Line 1769

Line 1783

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

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

</td>

</tr><tr><td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td><td><big>CC Compiler Sun Studio 5.11</big></td></tr>

</tr>

<tr>

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

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

OpenVMS

Alpha</big></td>

</tr>

<tr>

<td><big> HP OpenVMS 8.3 or

later IA64</big></td>

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

</tr>

<tr>

Windows 2000

</td>

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

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

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

tested.</td>

</tr>

<tr>

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

</td>

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

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

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

</tr>

<tr>

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

IX86)</big></td>

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

</tr>

</tbody>

</table>

Platform patches

Line 1779

Line 1826

<ol>

<li>

RHAS

RHAS

2.1 needs the update to fix Red Hat Bugzilla 98815.

2.1 needs the update to fix Red Hat Bugzilla 98815.</li>

</li>

<li>

RHEL 4.4 multithreading bug in

RHEL 4.4

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

multithreading bug in

RHEL 4.5</li>

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

fixed in

RHEL 4.5

</li>

<li>

Red Hat and SUSE Linux

Red Hat and SUSE

multiple versions -

Linux multiple versions -

multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla

multithreaded client intermittently fails connecting to IPv6 (Pegasus

6586) (Red Hat bug 248052) </li>

Bugzilla

6586) (Red Hat bug 248052)

</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can

Line 1801

Line 1854

found at:

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

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

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

</a></h2>

The Pegasus bugzilla database documents any defects found in Pegasus

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

database</a>.

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

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

were documented through bugs.  Bugs reports were filed not only for bugs and

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

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

only for bugs and

representing the work on PEPs done for Pegasus 2.6 and all subsequent versions.  Therefore, a search of

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

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

new code

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

versions.  Therefore, a search of

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

version

(ex. 

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

2.6.0_APPROVED</a>,

2.6.1_APPROVED</a>,

<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>) will yield all changes to

<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

the Pegasus CVS tree for that Pegasus release.

     - Changes for Pegasus 2.9.0 release (bugs Tagged

     - Changes for this release (bugs Tagged

2.9.0_APPROVED). The link is <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.9.0_APPROVED">

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

Pegasus 2.9.0_APPROVED bug list.</a>

Pegasus 2.11.0_APPROVED bug list.</a>

     - (2.11. 1) Changes between the 2.11.0 release

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

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

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

The Pegasus project is controlled largely through a set of documents

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

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

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

The Pegasus project is controlled largely through the CVS repository

and a set of documents

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

and

modified Pegasus functionality and for the definition and documentation

of releases.The following PEPs define the characteristics of this

of releases.

Pegasus release. These PEPs are available at

The following documentation defines the characteristics of this Pegasus

release. The documents are available in the OpenPegasus CVS

OpenPegasus Approved PEPs.</a><ol>

repository.

<li>

<ul>

No PEP (See Wiki Section <a href="http://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_9_x">OpenPegasus 2.9.x Release Status</a>) - OpenPegasus Release Definition/Status -  </li>A

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

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

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

section in the Pegasus wiki is used

throughout the development of this version as the control point for

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

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

represent the Pegasus  functionality changes for this version of Pegasus.

PEPs that represent the Pegasus  functionality changes for this

version of Pegasus. </li>

OpenPegasus

Build and Configuration

<li>

PEP 343</a> -  OpenPegasus  Build and Configuration

Options  for Selected

Platforms - Also located in the OpenPegasus CVS repository as <big>pegasus/doc/BuildAndReleaseOptions.html</big>.</li>

Platforms -  In previous

versions of Pegasus this information was  released as a Pegasus

<li>

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

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

PEP 344</a> - OpenPegasus 2.8 External Interfaces - </li>Lists the public

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

interfaces for clients and providers that are considered external and

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

therefore "frozen".

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

<li>

releases this information was available as a separate PEP. Starting

with Pegasus 2.9.0 this information is integrated into the Pegasus

PEP 342</a> - OpenPegasus  SDK Packaging Definition - </li>Defines the

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

recommended set of files for inclusion in the OpenPegasus SDK

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

<li>

previous Pegasus releases this document was made available as s

PEP 341</a> - Pegasus  Runtime Packaging Definition - </li>Defines the

separate Pegasus PEP document rather than in the CVS repository.

recommended set of files for inclusion in this OpenPegasus release.

</li>

<li> Pegasus  Runtime Packaging Definition

- Defines the recommended set

of files for inclusion in this OpenPegasus

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

release. Starting with Pegasus release 2.11.0, this idocument contained

approved PEP

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

repository and the OpenPegasus source tree root directory (<big>pegasus/ReleaseNotes.html</big>)

In previous

releases this was made available as a seperate Pegasus PEP document

</li>

rather than in the CVS repository.  </li>

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

</ol>

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

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

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

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

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

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

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>

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

The

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

Line 1918

Line 1969

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

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

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

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

copy of this software and associated documentation files (the "Software"),

obtaining a

to deal in the Software without restriction, including without limitation

copy of this software and associated documentation files (the

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

"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

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

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

Line 1941

Line 1998

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>

Legend:

Removed from v.1.16
changed lines
	Added in v.1.18.2.1

No CVS admin address has been configured