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

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

version 1.17, 2010/03/26 13:20:35

Line 1002

PEP #: 345

PEP #: 355

Title: Release

Notes for OpenPegasus 2.9.0

Notes for OpenPegasus version 2.10.0

Created: 05 January 2009

Created: 21 January 2010

Authors: Karl Schopmeyer

Line 1063

05 January 2009

21 January 2010

</td>

Line 1086

<tr>

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

<td style="padding: 0.75pt;" height="21"> Remove PEP 353 and 354 from

list and point to repository.Clean up PEP list</td>

</tr>

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

Line 1110

Line 1111

<tr>

<td style="padding: 0.75pt;" align="center" height="21">25 March 2010</td>

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

<td style="padding: 0.75pt;" height="21">Incorporate comments from Vote on

this PEP - This version approved</td>

</tr>

Line 1140

Line 1142

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.10.0 release of the OpenPegasus CIM Server. The purpose of this PEP is

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

Line 1197

Line 1199

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

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

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

each feature.Pegasus 2.9.0

each feature.Pegasus 2.10.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 follows. For

more information access the PEP for each change defined:

Table of Major Changes for this Release

Line 1218

Line 1219

</tr>

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

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

NOTE: This is an update of the same PEP number that incorporated

WS_Management changes to Pegasus 2.9.0 to incorporate more WS_Management

functionality.</td>

2.2</a> </td>

</tr>

<tr>

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

<td align="left" width="75%">Extend CIMCLI to create/modify instances with other features</td>

</tr>

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

<td align="left" width="75%">Single-Memory-Object for CMPI structure</td>

</tr>

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

<td align="left" width="75%">Separate Internal Modules from Common Library</td>

1.1</a></td>

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

<tr><td style="text-align: center;">PEP 350</td><td>Multi CIMOM support on

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

same OS </td><td style="text-align: center;">

1.0</a></td></tr><tr><td style="text-align: center;">

<a name="comtag_90">repupgrade utility enhancement to

update SystemName property in indication filter/handler and

ObjectManager instances</a> </td><td style="text-align: center;"> </td></tr><tr align="center">

<a name="comtag_95">Indication service can be

disabled/enabled dynamically</a> </td>

</tr>

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

</tr>

</tbody>

</table>

Line 1399

Line 1417

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.

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

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

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

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

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

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

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

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

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

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

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>

In Pegasus 2.8, the C++ CMPI IndicationMI function

signatures were changed to fit the CMPIIndicationMIFT definitions.

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>

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

Two things have changed in the behaviour of the property filter

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>

In Pegasus 2.8, the algorithm used by the MessageLoader

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>

7501</a></td>

<td>

Since OpenPegasus 2.7.2 the way CMPI_chars are added to

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 1484

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

Line 1515

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 1531

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,

</li>

the normalizer does apply qualifiers to returned instances if the

<li>LocalOnly option on instance

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

Line 1651

Line 1591

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

Line 1627

Linux IA-32</td>

gcc

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

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

</tr>

Line 1694

Line 1635

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

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>

Line 1769

Line 1683

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

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

Line 1740

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. 

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.10.0_APPROVED). The link is <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.10.0_APPROVED">

Pegasus 2.9.0_APPROVED bug list.</a>

Pegasus 2.10.0_APPROVED bug list.</a>

<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 a set of documents

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.The following documentation defines the characteristics of this

Pegasus release. These PEPs are available at

Pegasus release. The PEPs are available at

OpenPegasus Approved PEPs.</a><ol>

<li>

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

OpenPegasus Release Definition/Status -  </li>No PEP (See Wiki Section <a href="http://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_9_x">OpenPegasus 2.10.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

represent the Pegasus  functionality changes for this version of Pegasus.

represent the Pegasus  functionality changes for this version of Pegasus.

<li>

OpenPegasus  Build and Configuration

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 -

<a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/*checkout*/pegasus/doc/BuildAndReleaseOptions.html?rev=1.18">CVS Respository Build And Release Options Document</a> -

In previous versions of Pegasus this

information was  releases as a Pegasus PEP. Starting with Pegasus 2.9.0

the information is located in the OpenPegasus CVS repository as <big>

pegasus/doc/BuildAndReleaseOptions.html</big>.</li>

<li>

OpenPegasus External Interfaces -

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

interfaces for clients and providers that are considered external and

CVS Repository External Interfaces Document</a>- THE list of the

therefore "frozen".

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 repository as  pegasus/doc/EnternalInterface.html.

<li>

OpenPegasus  SDK Packaging Definition - </li>

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

PEP 352</a> - Defines the

recommended set of files for inclusion in the OpenPegasus SDK

<li>

Pegasus  Runtime Packaging Definition -

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

PEP 351</a> - </li>Defines the

recommended set of files for inclusion in this OpenPegasus release.

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

<li>Pegasus Release Notes -  PEP 355

- (This document is located in the

approved PEP

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

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

</li>

Legend:

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

No CVS admin address has been configured