pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.19 and 1.20

version 1.19, 2012/09/20 05:48:51

version 1.20, 2013/07/18 13:41:36

Line 1

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

<head>

<style>

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

</style>

Line 963

Line 965

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

</head>

<body lang="EN-US" link="blue" vlink="blue"><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> <o:LastAuthor> </o:LastAuthor> <o:Revision>4</o:Revision> <o:TotalTime>211</o:TotalTime> <o:Created>2004-04-05T14:13:00Z</o:Created> <o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>5026</o:Words> <o:Characters>28651</o:Characters> <o:Company>IBM</o:Company> <o:Lines>238</o:Lines> <o:Paragraphs>67</o:Paragraphs> <o:CharactersWithSpaces>33610</o:CharactersWithSpaces> <o:Version>10.4219</o:Version> </o:DocumentProperties></xml><![endif]--><!--[if gte mso 9]><xml>

<w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:Compatibility> <w:ApplyBreakingRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument></xml><![endif]-->

<span

OpenPegasus Enhancement

style="font-size: 13.5pt; color: black;">OpenPegasus Enhancement

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

PEP #: 364

PEP #: 366

Title: Release

Notes for OpenPegasus version 2.12.0

Notes for OpenPegasus version 2.13.0

Created: 10

Created: 18 July

September 2012

2013

Authors: Karl

Schopmeyer

Status:  draft

Version History:

<table class="MsoNormalTable" style="width: 100%;" id="table1" height="155"

border="1" cellpadding="0" cellspacing="1" width="100%">

<tbody>

<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

height="27">

<o:p> </o:p>

<span

</td>

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

</td>

<o:p> </o:p>

<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

</td>

height="27">

<span

<o:p> </o:p>

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

</td>

<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

<o:p> </o:p>

height="27">

<span

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

</td>

<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

height="27">

<span

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

</td>

</tr>

<span

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

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

</td>

<font

11 July 2013

size="2">10 September 2012

</td>

<span

Karl Schopmeyer

style="font-family: Arial;">Karl Schopmeyer

</td>

<font

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

size="2">Initial Submission <o:p><font

size="2"> </o:p>

</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center" height="21">1.01

<td style="padding: 0.75pt;" height="21" align="center">10 September

</td>

2012

<td style="padding: 0.75pt;" align="center" height="21">11 July 2013

</td>

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

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

Schopmeyer

</td>

<td style="padding: 0.75pt;" height="21"> Minor fixes and

<td style="padding: 0.75pt;" height="21">Minor editorial updates

complete links to PEPs

before review

</td>

</tr>

<td style="padding: 0.75pt;" align="center" height="21">1.02

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

2012

</td>

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

<td style="padding: 0.75pt;" align="center" height="21">16 July 2013

</td>

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

Schopmeyer

</td>

<td style="padding: 0.75pt;" height="21"> Incorporate all

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

comments from first review

1.01. See bug 9611. Add new section"Notes on SpecificOpenPegasus

Functionality"

</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center" height="21">1.03

<td style="padding: 0.75pt;" height="21" align="center">18 September

2012

</td>

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

<td style="padding: 0.75pt;" align="center" height="21">18 July 2013

Schopmeyer

</td>

<td style="padding: 0.75pt;" height="21"> Fix comments on bug

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

8830 (compatibility considerations) and bug 9172(repupgrade)

</td>

<td style="padding: 0.75pt;" height="21">Respond to HP comment about some confusion with the comment to bug 8830 in the compatibility Considerations section

</td>

</tr>

</tr>

</tbody>

</table>

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

style="color: black;">

Abstract: This document defines the release notes for the 2.12.0

Abstract: This document defines the release notes for the 2.13.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

other Pegasus documentation.

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

style="color: black;">

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

<ol>

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

Line 1101

Line 1080

of This Release</a></li>

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

Considerations</a></li>

<li><a href="#Notes_on_Specific_OpenPegasus">Notes on Specific

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

Line 1113

Line 1095

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

</ol>

<h2>Availability of this Release</h2>

This release is available in a number of forms including:

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

Line 1129

Line 1111

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>

page</a> and the <a title="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus">OpenPegasus

WIKI Release Status Page</a>.</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

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

WEB

site</a>. Installation instructions are part of the README in the root

site</a> and the <a title="OpenPegasus WIKI" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">OpenPegasus

of the Pegasus source tree.

WIKI</a>. Installation instructions are part of the README in the root

of the Pegasus source tree.

</div>

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

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

OpenPegasus overall status by release is defined by  a <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature

Status WEB Page</a> 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 OpenPegasus using a simple color coded key

(white, red, yellow, green) and a description of each feature.

(white, red, yellow, green) and a description of each feature.

OpenPegasus 2.12.0 is a major release, extending the previous Pegasus

OpenPegasus 2.13.0 is a major release, extending the previous Pegasus

release in selected areas as described in the Pegasus  PEP defining

this release .

NOTE: OpenPegasus releases are categorized as follows:

NOTE: OpenPegasus releases are categorized as follows:

<ul>

<li>First number of version changes (ex. 2.x.x to 3.0.0) -  Major

release includes major functionality change and  incompatible

behavior changes and/or incompatible public API changes,

</li>

<li>Second number changes (ex 2.11.0 2.12.0) -  Minor Release and

<li>Second number changes (ex 2.12.0 2.13.0) -  Minor Release and

includes new functionality but maintains behavior and public API

compatibility,

</li>

<li>3rd number changes (2.12.0 to 2.12.1) - Revision(also called point

<li>3rd number changes (2.13.0 to 2.13.1) - Revision(also called point

release) release and only includes bug fixes.</li>

</ul>

ALL changes for each release are documented in the

OpenPegasus bug data base by tagging each bug(keyword field of

ALL changes for each release are documented in the

bug).  No change to Pegasus is committed with out this tag on the

OpenPegasus bug data base by tagging each bug(keyword field of bug). 

bug. Changes for this minor release are  tagged 2.12.0_APPROVED.

No change to Pegasus is committed with out this tag on the bug. Changes

All changes for this minor release can be viewed through  this link

for this minor release are  tagged 2.13.0_APPROVED. All changes for

to the OpenPegasus bugzilla <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.0_APPROVED">

this minor release can be viewed through  this link to the

Pegasus 2.12.0_APPROVED bug list. Bugs.  </a>Bugs marked as

OpenPegasus bugzilla <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.13.0_APPROVED">

enhancements can be reviewed through the this <a href="http://bugzilla.openpegasus.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=CIM+Server+Core&product=CIMClient+Application&product=CIMClient+DefaultCPlusPlus&product=CIMClient+Java-SNIA&product=CIMConsumer+DefaultCPlusPlus&product=CIMIndicationHandler&product=CIMListener+Dynamic&product=CIMListener+Standalone&product=CIMProvider+CMPI&product=CIMProvider+CMPIRemote&product=CIMProvider+DefaultCPlusPlus&product=CIMProvider+Instrumentation&product=CIMProvider+JMPI&product=CIMSchema&product=CIMServer+Administration&product=CIMServer+Administration+Command&product=CIMServer+Administration+Profiles&product=CIMServer+ProviderManagement&product=CIMServer+Repository&product=CIMServer+SLP&product=OpenPegasus+Build+System&product=OpenPegasus+Documentation&product=OpenPegasus+Security+Defects&product=OpenPegasusProject+Bugzilla&product=OpenPegasusProject+CVS&product=OpenPegasusProject+Website&product=PegasusCIMOM&product=PegasusGeneral&product=RPM+CIMServer&product=TestProduct&product=Unsupported&product=WMI+Mapper&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.12.0_APPROVED&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfield=[Bug+creation]&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_severity&type0-0-0=equals&value0-0-0=enhancement">link

Pegasus 2.13.0_APPROVED bug list. Bugs.  </a>Bugs marked as

to OpenPegasus bugzilla 2.12.0 enhancement bugs</a> .  Bugs fixed

enhancements can be reviewed through the this <a href="http://bugzilla.openpegasus.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=CIM+Server+Core&product=CIMClient+Application&product=CIMClient+DefaultCPlusPlus&product=CIMClient+Java-SNIA&product=CIMConsumer+DefaultCPlusPlus&product=CIMIndicationHandler&product=CIMListener+Dynamic&product=CIMListener+Standalone&product=CIMProvider+CMPI&product=CIMProvider+CMPIRemote&product=CIMProvider+DefaultCPlusPlus&product=CIMProvider+Instrumentation&product=CIMProvider+JMPI&product=CIMSchema&product=CIMServer+Administration&product=CIMServer+Administration+Command&product=CIMServer+Administration+Profiles&product=CIMServer+ProviderManagement&product=CIMServer+Repository&product=CIMServer+SLP&product=OpenPegasus+Build+System&product=OpenPegasus+Documentation&product=OpenPegasus+Security+Defects&product=OpenPegasusProject+Bugzilla&product=OpenPegasusProject+CVS&product=OpenPegasusProject+Website&product=PegasusCIMOM&product=PegasusGeneral&product=RPM+CIMServer&product=TestProduct&product=Unsupported&product=WMI+Mapper&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.13.0_APPROVED&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_severity&type0-0-0=equals&value0-0-0=enhancement">link

for subsequent revision releases (ex. 2.12.1) would also be viewed

to OpenPegasus bugzilla 2.13.0 enhancement bugs</a> .  Bugs fixed

through corresponding Bugzilla tags for each revisions (ex

for subsequent revision releases (ex. 2.13.1) would also be viewed through

2.12.1_APPROVED).

corresponding Bugzilla tags for each revisions (ex 2.13.1_APPROVED).

The major areas of development including both enhancements and bug

The major areas of development including both enhancements and bug fixes

fixes for this release  were as follows. Note that the bugs listed

for this release  were as follows. Note that the bugs listed

represent only those features 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:

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

<font

style="font-weight: bold;" size="4">    Table of Major

Table of Major

Changes for this Release

Changes for this Release. Please review  Bugzilla 2.13.0

<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC"

Enhancements and approved(above) for a complete list

border="1" cellspacing="1" width="82%">

<tbody>

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

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

Version</th>

</tr>

<tr>

<td>Provider Lifecycle Indications

<td>Fixed issues where Pegasus compiler converted Schema Qualifer

decl to CLASS</td>

<td>

</td>

<td style="text-align: center;"><a href="https://collaboration.opengroup.org/pegasus/pp/documents/25003/PEP360_PLI_Ver1_2.html">Ver

</tr>

1.2</a>

<tr>

<td style="text-align: center;"> 5904

</td>

<td>Fixed issue that could cause server error if providers

return  associator or ref responses with no keys in path</td>

<td>

</td>

</tr>

<tr>

<td align="left" width="75%">cimcli support for embedded instances

</td>

<td>Support Writing indications to local file. Note that this is

primarily a development and debug extension.

</td>

<td width="128"><a href="https://collaboration.opengroup.org/pegasus/pp/origrevdocuments/3195/PEP361_CIMCLIEmbeddedInstanceSupport.htm">Ver

<td>

1.1</a>

</td>

</tr>

<tr>

<td align="left" width="7%">PEP 304

<td>Remove the PEGASUS_VENDOR_HP build variable</td>

<td>

</td>

<td align="left" width="75%">Allow modification of name of interop

</tr>

namespace

<tr>

</td>

<td style="text-align: center;" width="128"><a href="http://www.openpegasus.org/pp/uploads/40/23237/PEP_357_-_SNMP_v3_trap_generation_in_Pegasus_.htm"></a><a

<td>Enhance repupgrade utility to support "interop" namespace (see

href="https://collaboration.opengroup.org/pegasus/pp/documents/24686/PEP304_NamespaceRenaming.htm">Ver

note below)

1.5</a>

</td>

<td><a href="https://collaboration.opengroup.org/pegasus/pp/documents/24686/PEP304.htm">PEP

304, Version 1.6</a>

</td>

</tr>

<tr>

<td align="left">PEP 358

</td>

<td>WSMan indication handling and subscription support

<td>Support clang compiler in Production Build

</td>

<td align="center"><a href="https://collaboration.opengroup.org/pegasus/pp/documents/26240/PEP_358_-_WSMAN_Eventing_support_in_Pegasus_.htm">Ver

<td>

1.1</a>

</td>

</tr>

<tr>

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

8891</a>

</td>

<td>Enhance cimsub to add operations to create filters, destinations

<td>Add more supplemental help info to cimconfig CLI tool that views

and subscriptions

and sets runtime parameters

</td>

<td>

</td>

</tr>

<tr>

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

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

5667</a>

</a>and others

</td>

<td align="left" width="75%">Remove experimental form buildInstance

<td style="vertical-align: top;">Fixed issues involving compiled

and filter functions in CIMInstance class

unused variable warnings and set compiler defaults to make these

warnings a build error.

</td>

</td>

</tr>

<tr>

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

8952</a></td>

</td>

<td> Support Configurable cipher suites in OpenPegasus</td>

<td>Clean up  issues with building with static libraries

</td>

<td>

</td>

</tr>

<tr>

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

8984</a></td>

</td>

<td>Add support for indication deliver connection pooling</td>

<td>Reduce static code size (Note: several bug fixes contributed to

this reduction) (see 9555, 9560, 9557, 9558, 9580)

</td>

<td>

</td>

</tr>

<tr>

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

9008</a></td>

</td>

<td>Add new Indication runtime configuration variables:

<td>Log rotation configuration variable to set max file size (see

maxIndicaitonDeliveryRetry Attempts  and

below for more info)

minIndicationdeliveryRetryInterval</td>

</td>

<td>

</td>

</tr>

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

9013</a>

</td>

<td align="left" width="75%"><span

<td align="left" width="75%">Remove compile option

style="">Enable ordered indication delivery from

PEGASUS_CLIENT_TRACE_ENABLE (now always compiles) </td>

provider through CIMServer when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE compile flag is set</td>

</td>

</tr>

<tr>

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

9080 </a></td>

<td> Guaranteed provider lifecycle

indication delivery during CIMServer shutdonw </td>

</td>

</tr>

<td>Fix issues requiring restart of cimserver  if indication

<tr>

provider reregistered

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

9112</a>

</td>

<td>Advertise IndicationService conformance to Indications Profileby

imlementing CIM_ElementConformsToProfile when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td>

<td>

</td>

</tr>

<tr>

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

9114</a>

</td>

<td>Initial configure script for OpenPegasus (Experimental, see below)

</td>

<td>Advertise DMTF Indications Profile (DSP1054) 1.1.0 conformance </td>

<td>

</td>

</tr>

<tr>

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

9118</a>

</td>

<td>Add support for CIM_IndicationFilter.SourceNamespaces[] property

<td>Update env_var_LINUX.status and env_var_HPUX.status to change

some build defaults

</td>

<td>

</td>

</tr>

<tr>

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

9136</a></td>

<td>Modify environment variable definition that controls client

<td>Runtime configuration option to restrict cimserver to listen on

tracing (See below)</td>

selected network interfaces</td>

<td>

</td>

</tr>

<tr>

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

9155</a>

</td>

<td>Update to include CIM 2.31 Schema and set this as default schema

<td align="left" width="75%">Add support for PUSH_WITH_ACK delivery

mode for WSMAN indications

</td>

<td>

<td style="text-align: center;" width="128">PEP 365

</td>

</tr>

<tr>

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

9159</a></td>

<td>Change default Schema version to use CIM Schema 2.36</td>

<td>

<td>

<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC"

border="1" cellspacing="1" width="82%">

<tbody>

<tr>

<td>Add SSL Support to Dynamic Listener

</td>

</tr>

</tbody>

<tr>

</table>

</td>

<td>Replace custom atomic operations with GCC built-in atomic

operations(see below for more comments)

</td>

<td>

</td>

</tr>

<tr>

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

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

9172</a>

</td>

<td>Add capability for administrator to override hostname used by

<td align="left" width="75%">IPV6 support for OpenPegasus slp using

providers. This adds  new runtime configuration variable

OpenSLP 2.0 (See OpenSLP 2.0 issues documented below)

hostname and fullyQualifiedHostName. It is necessary to upgrade

existing repositories using repupgrade utility when upgrading from

OpenPegasus less that 2.12.0 and reusing an existing repository.

</td>

<td>

</td>

</tr>

<tr>

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

9215</a>

</td>

<td>Add support of CQL query language to ExecQuery operation in

<td>Support for ARM 64 CPU by adding platform definition

general. When the server receives  ExecQuery it executes

(Experimental because of limited testing)

enumerate instance for providers that do not support ExecQuery and

filters result.

</td>

<td>

</td>

</tr>

<tr>

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

9209 </a>

</td>

<td>Add operations for display class tree and counting instances to

<td>Fix connection between indication handlers and IndicationService

cimcli

so that OnFatalErrorPolicy works

</td>

<td>

</td>

</tr>

<tr>

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

9227</a>

</td>

<td>Enhance cimsub for batches of subscription oriented operations

<td>Expand reporting of errors from PAM so detailed PAM errors reported.

</td>

<td>

</td>

</tr>

<tr>

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

9229</a>

</td>

<td>Allow remote update of expired user password for PAM session

based authentication

</td>

<td><a name="comtag_197">Add gcc build support on hp-ux for the

Common, Client and General libraries.</a></td>

<td>

</td>

</tr>

<tr>

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

9236</a></td>

</td>

<td>Support for clang/clang++ compiler on Linux. This version

<td>Role-based authorization extension for CMPI providers

supports only X86 and X86_64 and requires clang version 3 or

greater.

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

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

that

have

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

previous release to this release</a> on the <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature

Status WEB Page</a>.

Status WEB Page</a>.

<h3>Information on Interop namespace name (root/PG_InterOp) for

OpenPegasus 2.12

<h2><a name="Notes_on_Specific_OpenPegasus"></a>Notes on Specific

</h3>

OpenPegasus Functionality Changes</h2>

Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable

This section documents specific issues that the OpenPegasus team feels are

to define "root/PG_InterOp" as the name for the OpenPegasus namespace

important to OpenPegasus users with the current release (and possibly

with no defined way to change this variable.  Note that an

older releases).

unsupported method involving editing one file and rebuilding OpenPegasus

was defined as a workaround in the <a href="%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus

<h3>Add new RunTime Variables to control trace file size and Rotation(OpenPegasus

2.13.0)(bug 9550)</h3>

As of OpenPegasus 2.13.0, two new runtime variables have been added:

   * traceFileSizeKBytes -  Defines the size of the

tracefile in kilobytes. The trace file will be rolled once its size

exceeds the specified size.

   * numberOfTraceFiles - Specifies the number of the tracefiles

for rolling where the default is 3.

<h3>Using GCC 4.7 Compiler on Linux OS (OpenPegasus 2.13.0)

</h3>

As of 2.13.0, OpenPegasus has been updated to replace the custom atomic

operations with GCC built-in atomic operations if GCC version 4.7 or

greater is used as the compiler.  It is recommended that if possible

this version of the GCC compiler be used since the change provides

significant performance improvements.

<h3>OpenPegasus and OpenSLP V 2.0 (OpenPegasus 2.13.0)</h3>

As of 2.13.0, OpenPegasus slp fully supports IPV6  and has been

tested with OpenSLP 2.0 (Recently released by <a href="http://openslp.org">OpenSlp.org</a>)

While testing OpenPegasus with OpenSLP 2.0 the OpenPegasus team found two

issues with this version of OpenSLP.  The patches documented below

allow this version of OpenSLP to work with OpenPegasus

1) SLPReg used TCP connection previously, but it now uses UDP. Therefore,

a BUFFER_OVERFLOW exception occurs.  This is because UDP cannot

handle attribute size greater than network MTU size. In such cases,

according to the specification, OpenSLP should automatically switch to

TCP.  Since this has not been implemented in OpenSlp 2.0, the

workaround used by OpenPegasus to force use of TCP may be found at <a title="http://sourceforge.net/p/openslp/bugs/139/" href="http://sourceforge.net/p/openslp/bugs/139/">http://sourceforge.net/p/openslp/bugs/139/</a>.

2) On Windows, slpd service fails to start when IPV6 is enabled and throws

the error message "Error 1067: the process terminated unexpectedly". More

details and the fix for this issue are in the bug <a href="http://sourceforge.net/p/openslp/bugs/140/">http://sourceforge.net/p/openslp/bugs/140/</a>.

<h3>Interop namespace name (OpenPegasus 2.13.0)</h3>

Effective with the release of OpenPegasus  2.13 the "interop"

namespace support for existing or

older repositories which used

"root/PG_InterOp" has been added via a new option in the "reupgrade"

utility. Users with existing repositories may use this option to migrate

the repository from "root/PG_InterOp" to

"interop" namespace.  See <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9414" title="RESOLVED FIXED - enhance repupgrade to support "interop" namespace">bug

9414</a> (PEP304) for

details.

For this to work, the build  option "PEGASUS_INTEROP_NAMESPACE" has

to be

set to "interop". Only then will the "-i" option in repupgrade be enabled.

Once the repository is upgraded with "-i" , the namespace

"root/PG_InterOp"

will cease to exsist. Clients using "root/PG_InterOp" must now use

"interop".

Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable to

define "root/PG_InterOp" as the name for the OpenPegasus namespace with no

defined way to change this variable.  Note that an unsupported method

involving editing one file and rebuilding OpenPegasus was defined as a

workaround in the <a href="file:///home/kschopmeyer/dev/pgogbug9611releasenotes/pegasus/%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus

wiki faq</a>s.

However, since the definition of a standard name for this namespace in

However, since the definition of a standard name for this namespace in

DMTF and SNIA specifications ("interop" or "root/interop" with "interop"

being the preferred alternative) the use of  "root/PG_InterOp" has

become an issue.

become an issue. Support for forward-compatibility is a fundamental design

principle for the OpenPegasus project. As a community, our goal is for

Effective OpenPegasus 2.12.0 a new build variable has been

well-behaved OpenPegasus providers or clients, using only the externally

defined  (PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus

defined OpenPegasus interface, to continue to work with each version

builder to define an alternate name for the Interop namespace to either

upgrade of OpenPegasus.

"interop" or "root/interop" (ex. PEGASUS_INTEROP_NAMESPACE =

interop).  Once this build variable is defined and OpenPegasus

Effective OpenPegasus 2.12.0 a new build variable was defined 

compiled, the actual name of the interop namespace is what was defined

(PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus builder to define

in this varaible and all components of OpenPegasus use this as the

an alternate name for the Interop namespace to either "interop" or

interop namespace name include the complete OpenPegasus test

"root/interop" (ex. PEGASUS_INTEROP_NAMESPACE = interop).  Once this

suite.  The only name for the interop namespace will be the name

build variable is defined and OpenPegasus compiled, the actual name of the

defined through this build variable.

interop namespace is what was defined in this varaible and all components

of OpenPegasus use this as the interop namespace name include the complete

However, today OpenPegasus is committed to the single namespace defined

OpenPegasus test suite.  The only name for the interop namespace will

at build "(root/PG_InterOp", "interop", or "root/interop"). However, a

be the name defined through this build variable.  This is the logical

number of OpenPegasus  installations are committed to the

approach for implementations starting a new repository.

"root/PG_InterOp" name and must maintain their repositories through

updates of OpenPegasus. While we are working on this issue today (which

In order to supexport PEGASUS_CLIENT_TRACE=keyword:keywordport users with

means that a running version of OpenPegasus must accept both the and new

existing repositories, in 2.13.0,  migration of existing repositories

names and not confuse clients, listeners or providers that would use

was integrated into the "repupgrade" utility to allow existing OpenPegasus

either name) the OpenPegasus team did not complete that work for this

environments to smoothly move the server from use of the old name 

release. See bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9250">9250</a>

for the interop namespace "root/PG_InterOp" to 

for more information about possible solutions and our progress on a

the prefered name "interop".

solution.

NOTE: If the interop namespace

NOTE: If you redefine the interop namespace name with

name is redefined with PEGASUS_INTEROP_NAMESPACE clients using the

PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp" namespace

"root/PG_InterOp" namespace will not connect with the updated version of

will not connect with the updated version of OpenPegasus.

OpenPegasus. The OpenPegasus team searched for a solution to the issue

supporting the old and new name at the same time and concluded that there

were so many issues that it could not effectively be done.

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

<h3>Configure Script to Control OpenPegasus Builds (OpenPegasus

NOTE: This functionality was incorporated in OpenPegasus 2.7.0

2.13.0)(Bug 9592)</h3>

but it was felt that the information below was worth repeating in

OpenPegasus is moving from the use of environment variables to a configure

subsequent Release Notes

script to control build.  This is both to make it easier to define

IPv6 is short

the build variables, etc. and to be more compatibile with the Linux/Unix

for "Internet Protocol Version 6". IPv6 is the "next generation"

standard build environment.  However, because OpenPegasus must build

protocol designed by the IETF to replace the current version Internet

on a number of platforms that do not support the full Linux/Unix

Protocol, IP Version 4 ("IPv4"). IPv6 Support for OpenPegasus is

configuration tool set, this is an OpenPegasus defined configure

documented in <a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">

script.  The first very experimental version is part of OpenPegasu

PEP 291</a>.

2.13.0 but this version has a number of limitations (see the OpenPegasus

The IPv6 support in OpenPegasus is controlled by the

Bugzilla) and will be expanded in the next versions of OpenPegasus.

PEGASUS_ENABLE_IPV6 build variable. The default for this variable is

"true"; setting this to 'false' before building OpenPegasus will disable

The goal is to replace the setting of most of the OpenPegasus build

the IPv6 support.

environment variable with options in the pegasus/configure script where

those options are comatible with the Linux standard for defining configure

The following subsections provide some information on IPv6 support for

options and those options control the entire build process including placement

the Linux and Windows platforms. Note that in the 2.6.1 release there is

of output and choice of build options.

no automatic run-time detection of IPv6 support on a platform by

<h3>Tracing Client Requests and Responses(OpenPegasus2.13.0)</h3>

OpenPegasus. If you build with PEGASUS_ENABLE_IPV6=true, your platform

must support IPv6 or you will get a build failure (missing header

OpenPegasus has

files), a run-time bind() failure, or possibly some other failure. This

long contained a hidden build controlled function to allow tracing at

applies to both the CIM Server and Listener components. For more

the client through an environment variable

information on IPv6 support for your specific platform, refer to the

(PEGASUS_CLIENT_TRACE_ON).  In 2.13.0 this was a) make a permanent

documentation for that platform.

part of of the environment (Bug 9564) and the calling convention

slightly changed

All OpenPegasus externals that support either a hostname or an IP

to make it simpler to use. The original format for the

environment variable was:

<pre class="bz_comment_text" id="comment_text_1">export PEGASUS_CLIENT_TRACE=keyword:keyword where the keyword was "con" | "log" | "both" This was changed to: keyword:keyword separately define Client input and output keyword: Client Input only :keyword Client Output Only keyword Client Input and output defined by keyword</pre>

so that the normal setup for a console output trace would be

<pre> export PEGASUS_CLIENT_TRACE=con</pre>

<h3>Information on IPV6 Support and OpenPegasus(PEP 291)(OpenPegasus

2.7.0)</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 Support for OpenPegasus is documented in

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

specified. If the required input is just an IP address (eg. no optional or

or required port number), then the IPv6 address must be specified

required port number), then the IPv6 address must be specified without

without brackets. For example, the OpenPegasus osinfo client (which

brackets. For example, the OpenPegasus osinfo client (which returns

returns information about the OS running on a host system) takes

information about the OS running on a host system) takes separate host and

separate host and port options. In this case a host with an

port options. In this case a host with an IPv6-configured network

IPv6-configured network interface would be specified as:

interface would be specified as:

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

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>osinfo -h 3ffe:1:2:1 -p 5988</big></div>

color="#000000">osinfo -h 3ffe:1:2:1 -p 5988</big></div>

But the cimcli command, which takes an optional "location" option

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

Line 1516

Line 1582

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

Modern Linux distributions already contain IPv6-ready kernels, the IPv6

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

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

this module is not loaded automatically on startup.

module is not loaded automatically on startup.

Note: you shouldn't use

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

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

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>test -f /proc/net/if_inet6 && echo "Running

color="#000000">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

For more iSchema version default update to CIM 2.36nformation on enabling

Linux Documentation Project's IPv6 HOWTO</a>.

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

open issue with RedHat to address a problem that is seen intermittently on

on RHEL5 and SLES10 systems. This problem is described in

RHEL5 and SLES10 systems. This problem is described in

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

bug

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

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

socket failure. You should be aware that OpenPegasus with IPv6 enabled may

may be significantly impacted in these environments.

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

Microsoft provides supported IPv6 implementations for Windows Server 2003,

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

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

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

color="#000000">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

Windows Vista and Windows Server 2008 support an integrated IPv4 and IPv6

the OpenPegasus IPv6 support has not yet been tested on Windows Vista or

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

For more information on installing, configuring, and using IPv6 on Windows

Windows platforms, refer to the document <a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"><font

platforms, refer to the document <a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx">IPv6 for Microsoft Windows: Frequently Asked Questions</a>.

color="#000000">IPv6 for Microsoft Windows: Frequently Asked

Questions</a>.

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

Line 1576

Line 1642

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>

<h2><a name="Compatibility_Considerations_">OpenPegasus Compatibility

Support for forward-compatibility is a fundamental design principle for

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

OpenPegasus interface, to continue to work with a minor version upgrade of

of OpenPegasus. However, there are certain classes of errors (e.g.,

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

incompatible changes. The following table contains a list of defects/fixes

defects/fixes that MAY impact, even well-behaved, OpenPegasus providers

that MAY impact, even well-behaved, OpenPegasus providers or clients when

or clients when upgrading to this OpenPegasus release.

upgrading to this OpenPegasus release.

<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC"

border="1" cellspacing="1" width="80%">

<tbody>

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

Line 1598

Line 1664

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

8830</a></td>

<td align="left">Starting with OpenPegasus 2.11.0 the requirement

<td align="left">Starting

for providers (CMPI and C++) to filter properties from instances

with OpenPegasus 2.11.0 the requirement for providers (CMPI and C++) to

has been relieved. The server will do the filtering at the

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

protocol adapter level. To avoid a negative impact on performance

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

the CIMInstance::filter() and CMPIInstanceFT.setPropertyFilter()

on performance the CIMInstance::filter() and

functions have been changed to a NOP. This may be a change in

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

behavior for provider relying in some unknown way on the instance

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

being filtered through these functions. To allow users to actually

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

filter properties from an instance, new function

allow users to actually filter properties from an instance in a

CIMInstance::filterInstance() will actually filter properties from

provider, a new function (CIMInstance::filterInstance()) will actually

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

filter properties from an instance exactly as the CIMInstance::filter()

versions of Pegasus.</td>

did in previous versions of Pegasus. This is not required since the

CIMServer will do the filtering but allows the provider to prefilter

properties if it so desires, in particular where properties might be

very large or there would be a significant number of properties.

</td>

</tr>

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

9369</a>

</td>

<td align="left">Reregistering of an indication provider requires

<td align="left">NOTE: This bug

that the  cimserver be restarted to send the enableIndication

fixed in OpenPegasus 2.13.0. Reregistering of an

request to the providers. This issue has existed starting with

indication provider requires that the  cimserver be restarted

OpenPegasus 2.10 to the current version. If the cimserver is not

to send the enableIndication request to the providers. This issue

restarted the indication will not be enabled for the reregistered

has existed starting with OpenPegasus 2.10 to  version 2.12.

provider. </td>

If the cimserver is not restarted the indication will not be

enabled for the reregistered provider. </td>

</tr>

</tbody>

</table>

<h2>OpenPegasus Relationship to CIM/WBEM Standards</h2>

Pegasus was designed and implemented to comply with the DMTF CIM/WBEM

Pegasus was designed and implemented to comply with the DMTF CIM/WBEM

specifications The following table defines the level of the DMTF

specifications to which this version of Pegasus aims to conform today.

specifications to which this version of Pegasus aims to conform today.

<tbody>

<tr>

Line 1660

Line 1732

</tr>

<tr>

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

<td width="33%">2.31.0 Final ( default) </td>

<td width="33%">2.36.0 Final ( default build Schema) </td>

</tr>

<tr>

<td>DSP0226 - Web Services for Management

Line 1681

Line 1753

</tr>

</tbody>

</table>

<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIS SMI

<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIA SMI

Profiles Supported</h2>

Today OpenPegasus includes support for several DMTF profiles including

the ones defined below:

Today OpenPegasus includes support for several DMTF profiles including:

<ol>

<li>DMTF ProfileRegistration Version 1.0.0</li>

<li>DMTF ProfileRegistration Version DSP 1033, Version 1.0.0</li>

<li>DMTF Indications 1.1.0. Since this is effectively the same as the

<li>DMTF Indications DSP 1054, Version 1.1.0. Since this is effectively the same as the

SNIA SMI Indication profile it also supports this profile. This

profile is enabled by compiling OpenPegasus with the buld variable

PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

</li>

<li>SNIA Profile Registration 1.0.0</li>

<li>SNIA Profile Registration 1.0.0

</li>

<li>SNIA Server 1.1.0 & 1.2.0

</li>

</ol>

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

to DMTF Specifications</a></h2>

It is a major goal of the OpenPegasus project to both drive and utilize

It is a major goal of the OpenPegasus project to both drive and utilize

the DMTF CIM/WBEM specifications.  However, today there are a

the DMTF CIM/WBEM specifications.  However, today there are a number

number of known differences.  As of this release, some of the

of known differences.  As of this release, some of the differences

differences include the following:

include the following:

<ol>

<li>Provider Registration - Pegasus supports registration through

<li>Provider Registration

a set of Pegasus Provider registration classes rather than support the

- Pegasus supports registration through a set of Pegasus Provider

DMTF defined Provider Qualifier. Pegasus will not support this

registration classes rather than support the DMTF defined Provider

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

Qualifier. Pegasus will not support this qualifier in the future. See

provider registration.  This is not a deviation from the

the readme for more information on provider registration.  This is

specifications but is a different method of registration than many CIM

not really a deviation from the specifications since there is no

Servers and means that the the provider qualifier is unused in

specification or profile for provider registration today but is a

Pegasus.</li>

different method of registration than many CIM Servers and means that

the the provider qualifier is unused in Pegasus.</li>

<li>Lifecycle Indications -Today Pegasus supports process

indications and lifecycle indications when defined specifically by

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

pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a><font

pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

size="2">.</li>

<li> IncludeQualifiers

<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

instance operations with the 1.2 CIM Operations Over HTTP Specification (DSP0200) 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

properties).   Pegasus today expects the provider to

provider to complete the qualifiers on instances in accordance with

complete the qualifiers on instances in accordance with the

the specification and generally the interpretation is that Pegasus

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

Line 1741

Line 1813

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.

includeQualifiers operation parameter is set.</li>

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

Line 1753

Line 1824

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>

<li>MultiRequest CIM/XML Option

MultiRequest Operations - Pegasus does not

-  Pegasus does not support the DMTF defined MultiRequest

support the DMTF defined MultiRequest Operation option.

Operation option (See DSP0200).

</li>

<li>

<li>MOF Namespace Pragma -The

MOF Compiler namespace pragma - The

Pegasus compiler does not support the namespace pragma defined in DSP

Pegasus compiler does not support the namespace pragma.

0004. Namespaces for the OpenPegasus repository are defined through

arguments for the MOF Compiler

</li>

<li>CIMOperation Trailer - Pegasus implements chunking based on

the DSP0200 1.2.0 preliminary spec. including the operation trailer

Line 1787

Line 1859

<li>OpenPegasus Interop Namespace - The default interop namespace

name in OpenPegasus is "root/PG_Interop".  In versions of

OpenPegasus prior to 2.12.0 this could be changed during build by

modifying a string definition in the code. Effective version 2.12

modifying a string definition in the code. Effective version 2.12.0

this  has become a build option with the build configuraton

environment variable PEGASUS_INTEROP_NAMESPACE = <name for this

namespace> however, the default if built without this change is

still "root/PG_InterOp"

still "root/PG_InterOp". Effective with OpenPegasus 2.13.0 the reupgrade utility has been extended to allow existing repositories to be converted from the use of "root/PG_Interop" to "interop" (See discussion above).  The default in the CVS source code is still "root/PG_InterOp".

</li>

<li>OpenPegasus WSMAN protocol on windows does not handle NaN, INF,

or -INF (bug  <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>)

or -INFHowever, t (bug  <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>)

- If requests or responses include properties or parameters with

floating point property types (Real32 or Real64) with the special

states NaN, INF, or -INF on a Windows platform, the input is not

Line 1821

Line 1893

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

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

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

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

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

is changed.  Pegasus may be operable on other platforms (ex.

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

Windows 98) but without a group to provide the role of test and

but without a group to provide the role of test and maintenance, correct

maintenance, correct operation of  Pegasus cannot be assured. 

operation of  Pegasus cannot be assured.  In all cases,

In all cases, including the active platforms, it is the responsibility

including the active platforms, it is the responsibility of the entity

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

that packages and/or compiles OpenPegasus for shipment or deployment, to

deployment, to read, and actively monitor the Pegasus Bugzilla database

read, and actively monitor the Pegasus Bugzilla database for a list of

for a list of relevant defects that affect their platform.  

relevant defects that affect their platform.   The platforms

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

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

below.  The first table represents platform for which testing is

first table represents platform for which testing is done on a regular

done on a regular basis and reported to the Pegasus Nightly Build Test

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

WEB Page. Those platforms which have been ported but do not have test

platforms which have been ported but do not have test results that are

results that are current at the time of the release are reported in the

current at the time of the release are reported in the second table.

second table.

Actively Supported Platforms (Nightly Tests Reported for this release)

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

cellspacing="1">

<tbody>

<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 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>

height="26">

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

Compilers<span

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

</td>

</tr>

Line 1870

Line 1938

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

</td>

gcc<span

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

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

</td>

</tr>

zLinux<span

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

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

</td>

gcc<span

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

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

</td>

</tr>

Line 1889

Line 1954

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

</td>

gcc<span

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

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

</td>

</tr>

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

IA-32</td>

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

<td style="padding: 0.75pt;"> gcc (versions 3.xx, 4.7) clang(The clang compiler usage

size="3">gcc<font

is considered production effective OpenPegasus 2.13.0)<o:p></o:p></td>

size="3"> (versions 3.xx, 4.xx) clang(The clang compiler usage

is considered experimental and is not part of the nightly

tests today)<o:p></o:p></td>

</tr>

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

</td>

gcc<span

gcc (versions 3.xx, 4.7) clang(The clang compiler usage is considered production effective OpenPegasus 2.13.0)

style="color: black;"> (versions 3.xx, 4.xx) <font

size="3">clang(The clang compiler usage is considered

experimental and is not part of the nightly tests today)

</td>

</tr>

<tr>

Line 1922

Line 1980

</table>

Platforms not Actively supported for this release (No

current Nightly Build Test Results

current Nightly Build Test Results)

<table class="MsoNormalTable" style="width: 90%;" id="table2" border="1" cellpadding="0"

cellspacing="1">

<tbody>

height="26">

Platform and

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

</td>

height="26">

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

Compilers<span

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

</td>

</tr>

<tr>

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

Vista, Windows 7, Windows Server 2008

Vista, Windows 7, Windows Server 2008 </td>

</td>

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

Compilers 2003 - 2010.. Note: Visual C++ Ver. 6 no longer being

regular tested.Note that today there are some open issues with

Line 1962

Line 2014

</td>

</tr>

<tr>

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

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

color="RED">Solaris 9</big></td>

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

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

</td>

</tr>

<tr>

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

<td><big>HP C++ V<span

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

style="color: rgb(153, 51, 153);">7.3-009 or later required

for OpenVMS Alpha</big></td>

</tr>

<tr>

Line 1991

Line 2041

regularly tested.</td>

</tr>

<tr>

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

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

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

Line 2004

Line 2052

</tr>

</tbody>

</table>

Platform patches

<h3>Platform patches </h3>

The

following is a list known of platform patches Pegasus requires.

The following is a list known of

platform patches Pegasus requires.

<ol>

<li>

<li> RHAS 2.1 needs the update to

RHAS

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 getpwuid-r could cause a CIM

RHEL 4.4

Server failure (Bugzilla 6232). This is fixed in RHEL 4.5

multithreading bug in getpwuid-r could cause a CIM Server failure

(Bugzilla 6232). This is fixed in RHEL 4.5

</li>

<li>

Red Hat and SUSE

Linux multiple versions - multithreaded client intermittently

fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red Hat bug

248052)

</li>

<li> Red Hat and SUSE Linux multiple versions - multithreaded client

intermittently fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red

Hat bug 248052)</li>

<li> OpenSLP Version 2.0 - This release of OpenSLP requires the

patches for OpenSLP version 2.0 documented above.</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can be

found at: <a href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span

Further information regarding Pegasus support on IBM platforms can be

style="text-decoration: underline; color: rgb(51, 51, 255);">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</a>

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>

Further information regarding Pegasus support on HP platforms can be

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

Further information regarding Pegasus support on HP platforms can be 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>

The OpenPegasus Bugzilla database documents any defects found in

The OpenPegasus Bugzilla database documents defects found in Pegasus

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

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

OpenPegasus 2.6 work, all changes to the CVS tree are documented through

OpenPegasus 2.6 work, ALL changes to the OpenPegasus CVS tree are

bugs.  Bugs reports are filed not only for bugs and their

documented through bugs. Therefore all source code changes to OpenPegasus

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

are documented through bugs providing a complete history of changes and

code representing the work on PEPs done for OpenPegasus 2.6 and all

the reasons for those changes.  Bugs reports are filed not only for

subsequent versions.  Therefore, a search of the OpenPegasus

bugs and their corresponding fixes but also as part of the process of

Bugzilla base for bugs with the tag for a particular version (ex. 

committing new code representing the work on PEPs done for OpenPegasus 2.6

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

and all subsequent versions.  Therefore, a search of the OpenPegasus

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.1_APPROVED</a>, <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 OpenPegasus

release.

release.

- Changes for this release (bugs Tagged

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

     - Changes for this release (bugs Tagged

Pegasus 2.12.0_APPROVED bug list.</a>

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

Pegasus 2.13.0_APPROVED bug list.</a>

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

Control

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

The OpenPegasus project is controlled largely through the CVS

The OpenPegasus project is controlled largely through the CVS repository

repository and a set of documents (PEPs) that serve both as the

and a set of documents (PEPs) that serve both as the definition and review

definition and review mechanism for new and modified Pegasus

mechanism for new and modified Pegasus functionality and for the

functionality and for the definition and documentation of releases.

definition and documentation of releases.

The following documentation defines the characteristics of this Pegasus

release. The documents are available in the OpenPegasus CVS

repository.

<ul>

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

<li> OpenPegasus Release Definition/Status - (See Wiki Section <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_12_x">OpenPegasus

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

2.13.x

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

OpenPegasus

Build and Configuration Options  for Selected Platforms -  <span

Build and Configuration Options  for Selected Platforms -  In previous versions of Pegasus this

style="font-weight: normal;">In previous versions of Pegasus this

information was  released as a Pegasus 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>.

<li> OpenPegasus External Interfaces -The

<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

Line 2085

Line 2131

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

information is integrated into the Pegasus repositoryas  pegasus/doc/EnternalInterface.html.</li>

style="font-weight: bold;">pegasus/doc/EnternalInterface.html<span

style="font-weight: normal;">.</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>.

In previous Pegasus releases this document was made available as s

separate Pegasus PEP document rather than in the CVS repository.

</li>

</li>

<li> Pegasus  Runtime Packaging Definition - Defines

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

PEP document rather than in the CVS repository.  </li>

<li>Pegasus Release Notes -  PEP

<li>Pegasus Release Notes -

364 - (This document is located

PEP 364 - (This document

in the approved PEP repository and the OpenPegasus source tree

is located in the approved PEP repository and the OpenPegasus

root directory (<big style="font-weight: bold;">pegasus/ReleaseNotes.htm</big>)</li>

source tree root directory (<big>pegasus/ReleaseNotes.htm</big>)</li>

</ul>

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

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

The following documentation is available for the this Pegasus

release:

The following documentation is available for the this Pegasus release:

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

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

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

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

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

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

<li class="MsoNormal" style="color: black;">API and  usage

</li>

documentation - </li>

<li class="MsoNormal" style="color: black;">API and  usage

See the header files and the HTML  API documentation that is on

documentation - See the header files and the HTML

the web site. The best API usage documentation is the existing utilities

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

and test programs and the examples in the API documentation.  In

documentation is the existing utilities and test programs and the

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

examples in the API documentation.  In particular the

use of the Common APIs.

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

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

Common APIs. </li>

Providers - </li>

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

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

Providers - Readme.html in the Pegasus source tree Root

documentation, and documentation from the Pegasus Technical Workshop

Directory, API documentation, and documentation from the Pegasus

which is available on the Pegasus web site.

Technical Workshop which is available on the Pegasus web site.

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

</li>

Clients - </li>

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

API documentation and the documentation on the Pegasus Technical

Clients -API documentation and the documentation on the

Workshop which is available on the Pegasus web site.

Pegasus Technical Workshop which is available on the Pegasus web site.

</li>

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

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

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

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

the OpenPegasus web site.  While these are the original design

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.

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

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

WIKI - This WIKI is maintained both for the use of the

development team and as a user information resource.  The wiki

can be accessed at <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start</a></li>

</ul>

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

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this

Line 2163

Line 2212

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.19
changed lines
	Added in v.1.20

No CVS admin address has been configured