pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.12 and 1.13

version 1.12, 2007/10/16 17:27:28

version 1.13, 2008/07/30 16:39:55

Line 1011

PEP #: 306

PEP #: 332

Title: Release

Notes for OpenPegasus 2.7.0

Notes for OpenPegasus 2.8.0

Created: 3 October 2007

Created: 21 June 2008

Authors: Karl Schopmeyer

Line 1071

<o:p> </o:p>3

October 2007

21 June 2008

</td>

Line 1097

<td style="padding: 0.75pt;" align="center" height="21">8 October 2007</td>

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

<td style="padding: 0.75pt;" height="21">Incorporate data from 2.6.1

<td style="padding: 0.75pt;" height="21">Incorporate initial comments</td>

release notes. Fix per comments in 1.0</td>

</tr>

Line 1110

Line 1109

<td style="padding: 0.75pt;" align="center" height="21">11 October 2007</td>

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

<td style="padding: 0.75pt;" height="21">Comments from V 1.1 and add

<td style="padding: 0.75pt;" height="21">Incorporate All Comments to date

existing document links. Add pep 302 to enhancements</td>

(See discussion for list of changes)</td>

</tr>

Line 1123

Line 1122

<td style="padding: 0.75pt;" align="center" height="21">15 October 2007</td>

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

<td style="padding: 0.75pt;" height="21">Add final links</td>

<td style="padding: 0.75pt;" height="21">Add bug 7501 to compatibility

issues table. Remove temp change list section</td>

</tr>

Line 1153

<hr align="center" color="#009900" noshade="noshade" size="2"

width="100%"></div>

Abstract: This document defines the release notes for the

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

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

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

each feature.Pegasus 2.8.0

is a major release, extending Pegasus 2.6 in selected

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

areas as described in the Pegasus  PEP defining this release

.

Line 1238

<TH bgColor=#00FFFF width="128">Posted PEP Version</TH>

</TR>

<TD align="left" width="75%">Add Platform support IBM i5/PASE - Portable Application

<TD align="left" width="75%">Memory Resident Repository</TD>

Solutions Environment (PASE)</TD>

1.6</a></TD>

1.3.1</a></TD>

</TR>

<tr>

<TD align="left" width="75%">Reduce the Amount of CIM Server code that runs Privileged

311</TD>

(Privilege Separation)</TD>

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

1.8</a></TD>

</TR>

1.4</a></TD>

</tr>

<TD align="left" width="75%">Add Support for IPv6 - Stage 1 (Note: This functionality

<TD align="left" width="75%">Pluggable Provider Managers - Enhancement</TD>

was made available but normally disabled

Pegasus 2.6.1)</TD>

1.2</a></TD>

</TR>

<TD align="left" width="75%">Add IPV6 Support for SNMP Indication Handler

<TD align="left" width="75%">Tracing in OpenPegasus - Enhancement</TD>

and include NET-SNMP indication handler in Linux RPM </TD>

1.1</a></TD>

1.0</a></TD>

</TR>

<TD align="left" width="75%">Enable Remote CMPI for Windows</TD>

<TD align="left" width="75%">Profile Registration Profile Support</TD>

1.2</a></TD>

1.3</a></TD>

</TR>

<TD align="left" width="75%">Enhanced Log File Support</TD>

<TD align="left" width="75%">Track Generated Indications Data</TD>

1.0</a></TD>

1.2</a></TD>

</TR>

<TD align="left" width="75%">Add support for certificate-based authentication audit

<TD align="left" width="75%">DMTf Indication Profile Implementation, Stage

logging</TD>

1 (DMTF DSP 1054)</TD>

1.5</a></TD>

1.0</a></TD>

</TR>

<TD width="7%">Bugzilla 6466</TD>

<TD align="left" width="75%">Add two new trace components to facilitate

<TD align="left" width="75%">Track Generated Indications Data</TD>

triage of indication delivery issues</TD>

Bug 6466</a></TD>

1.2</a></TD>

</TR>

</TBODY>

</TABLE>

Line 1314

Line 1310

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 the 2.8.0 Release

Notes

IPv6 is short for "Internet

Protocol

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

Line 1459

Line 1458

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

upgrading to OpenPegasus 2.8.0.

<TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666

borderColorLight=#CCCCCC border=1 width="80%">

<TBODY>

Line 1468

Line 1467

<TH bgColor=#00FFFF>Description</TH>

</TR>

<TD align="left">HP-UX only: Introduction of the "explicit" keyword in CIMClass.h and CIMInstance.h may introduce

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

a compile error in some code. Specifically, a compiler-supplied automatic conversion from CIMObject

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

type to CIMClass or CIMInstance has been removed. The cast operation must be explicitly specified.

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

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

</TD>

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>

WIPCR00430 recommends an unquoted charset parameter in Content-type header. See the writeup in this bug for a discussion of the validation of the charset parameter in various OpenPegasus releases. In 2.7 we perform "extended" validation that should ignore differences based on whitespace or quotes. The CR recommendation is to not use quotes on the charset parameter, but only at a time when it is expected that all CIMOMs have been updated to accept the charset parameter with or without quotes.</TD>

In Pegasus 2.8, the C++ CMPI IndicationMI function

signatures have been 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>

The MOF Compiler now rejects some property values that are invalid according to the DMTF specification that it previously accepted.</TD>

In Pegasus 2.8, the CMPI property filter handling has

been improved in performance.

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 will

not longer return ICU "fallback" matches. In addition, it will give

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

In Pegasus 2.8, the Message Loader has been 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 1508

Line 1583

</tr>

<tr>

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

<td width="33%">1.2.0, preliminary, 9 December 2004</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%">2.2.0, preliminary, December 2004</td>

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

</tr>

<tr>

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

Line 1528

Line 1603

</tr>

<tr>

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

<td width="33%">2.13.1 Final, Jan. 2005 ( default) </td>

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

</tr>

</tbody>

</table>

Line 1595

Line 1670

MOF Compiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

</li>

<li>Pegasus implements

<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

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

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>

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

hardware/software platforms that have recognized ports for the Pegasus

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

code

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

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

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

regularly document issues and/or fix defects as the Pegasus

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

code base is changed. 

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

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

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

a group

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

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

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

Pegasus cannot be

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

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

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

responsibility of the entity that packages and/or compiles OpenPegasus

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

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

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

bugzilla database for a list of relevant defects that affect their

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

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

of the release are reported in the second table

Pegasus release are:

Actively Supported Platforms (Nightly Tests Reported for this release

<table class="MsoNormalTable" style="width: 90%;" border="1"

cellpadding="0" cellspacing="1">

<tbody>

Line 1706

Line 1784

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

</tr>

<tr>

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

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

</td>

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

Line 1714

Line 1792

</td>

</tr>

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

</tr>

<tr>

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

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

Line 1734

Line 1808

style="color: rgb(0, 0, 0);"> 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

current Nightly Build Test Results

<table class="MsoNormalTable" style="width: 90%;" border="1"

cellpadding="0" cellspacing="1" id="table2">

<tbody>

<td

style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;"

height="26">

Platform and

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

</td>

<td

style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;"

height="26">

Compilers<span

style="color: black;"><o:p></o:p>

</td>

</tr>

<tr>

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

</tr>

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

</tr>

<tr>

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

style="color: rgb(0, 0, 0);">Solaris 8</big></td>

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

Line 1750

Line 1863

</tr>

</tbody>

</table>

Platform patches

Platform patches

<font

style="color: rgb(0, 0, 0);">The following is a list known of platform

patches Pegasus requires.

Line 1801

Line 1914

the Pegasus CVS tree for that Pegasus release.

     - Changes for Pegasus 2.7.0 release (bugs Tagged

     - Changes for Pegasus 2.8.0 release (bugs Tagged

2.7.0_APPROVED) 

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

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

Pegasus 2.8.0_APPROVED bug list</a>

<h2><a

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

Line 1823

Line 1936

<ol>

<li>

PEP 296 - OpenPegasus Release Definition - This PEP is used

PEP 333 - OpenPegasus Release Definition - This PEP ( and a corresponding

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

Line 1831

Line 1945

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/14873/PEP292_RecommendedReleaseOptions.htm">PEP 292</a> -  OpenPegasus  Build and Configuration

PEP 308</a> -  OpenPegasus  Build and Configuration

Options  for Selected

Platforms</li>

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/14874/PEP293_ExternalInterface2.7.htm">PEP 293</a> - OpenPegasus 2.7 External Interfaces - Lists the public

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

interfaces for clients and providers that are considered external and

therefore "frozen".

</li>

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/14875/PEP294_SDKFile2.7.0.htm">PEP 294</a> - OpenPegasus  SDK Packaging Definition - Defines the

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

recommended set of files for inclusion in the OpenPegasus SDK</li>

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/14877/PEP295_RuntimePackaging2.7.0.htm">PEP 295</a> - Pegasus  Runtime Packaging Definition - Defines the

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

recommended set of files for inclusion in this OpenPegasus release.</li>

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

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

approved PEP

repository and the OpenPegasus source tree root directory)

Line 1905

Line 2023

<span

style="color: black;">  <o:p></o:p>

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

Legend:

Removed from v.1.12
changed lines
	Added in v.1.13

No CVS admin address has been configured