pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.19.2.1, 2013/03/18 14:15:54

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

Line 1

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

<head>

http-equiv="Content-Type">

<style>

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

</style>

Line 964

Line 965

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso">

</head>

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

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

style="color: black;">

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

OpenPegasus Enhancement

width="100%"></div>

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

<p class="MsoNormal" style="margin-bottom: 12pt; text-align:

center;" align="center"><span style="font-size: 13.5pt;

color: black;">OpenPegasus Enhancement Proposal (PEP)<o:p></o:p>

PEP #: 366

<span

style="color: black;">

PEP #: 364

Title: Release

Notes for OpenPegasus version 2.13.0

Created: 18 July

2013

Notes for OpenPegasus version 2.12.1

Created: 10

September 2012

Authors: Karl

Schopmeyer

Schopmeyer, Marek Szermutzky

Status:  draft

Version

Version History:

History:

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

border="1" cellpadding="0" cellspacing="1" height="155"

width="100%">

<tbody>

<td style="padding: 0.75pt; background: rgb(202, 230, 202)

none repeat scroll 0% 50%; -moz-background-clip: initial;

<o:p> </o:p>

-moz-background-origin: initial;

</td>

-moz-background-inline-policy: initial;" height="27">

<p class="MsoNormal" style="text-align: center;"

<o:p> </o:p>

align="center"><span style="font-family: Arial;

</td>

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

</td>

<o:p> </o:p>

<td style="padding: 0.75pt; background: rgb(202, 230, 202)

</td>

none repeat scroll 0% 50%; -moz-background-clip: initial;

-moz-background-origin: initial;

<o:p> </o:p>

-moz-background-inline-policy: initial;" height="27">

<p class="MsoNormal" style="text-align: center;"

align="center"><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">

<p class="MsoNormal" style="text-align: center;"

align="center"><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">

<p class="MsoNormal" style="text-align: center;"

align="center"><span style="font-family: Arial;

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

</td>

</tr>

<p class="MsoNormal" style="text-align: center;"

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

align="center"><span style="font-family: Arial; color:

black;"> 1.0<o:p></o:p>

</td>

<p class="MsoNormal" style="text-align: center;"

11 July 2013

align="center"> <span

style="font-family: Arial;">10 September 2012

</td>

<p class="MsoNormal" style="text-align: center;"

Karl Schopmeyer

align="center"> <font

size="2">Karl Schopmeyer

</td>

<span style="font-family: Arial;

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

color: black;">Initial Submission <span

style="color: red;"><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;" align="center" height="21">10

</td>

September 2012

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

</td>

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

Schopmeyer

</td>

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

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

and complete links to PEPs

before review

</td>

</tr>

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

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

</td>

September 2012

<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

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

all 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;" align="center" height="21">18

September 2012

</td>

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

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

Schopmeyer

</td>

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

</td>

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

<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

on bug 8830 (compatibility considerations) and bug

9172(repupgrade)

</td>

</tr>

1.3

</td>

<td style="padding: 0.75pt;" align="center" height="23">14

March 2013

</td>

<td style="padding: 0.75pt;" align="center" height="23">Marek

Szermutzky

</td>

<td style="padding: 0.75pt;" height="23">Update for 2.12.1

Release

</td>

</tr>

</tbody>

</table>

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

width="100%"></div>

Abstract: This document defines the release notes for the 2.13.0

Abstract: This document defines the release notes for

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

the 2.12.1 release of the OpenPegasus CIM Server. The purpose of

summarize the characteristics of this release, point to other

this PEP is to summarize the characteristics of this release,

documentation that defines the release in more detail, and provide

point to other documentation that defines the release in more

additional information about this release that is not available in the

detail, and provide additional information about this release

other Pegasus documentation.

that is not available in the other Pegasus documentation.

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

width="100%"></div>

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

<ol>

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

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

this Release</a></li>

Release</a></li>

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

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

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

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

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

Platforms</a></li>

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

with DMTF Specifications</a></li>

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

<li> <a

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

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

Release

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

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

</ol>

<h2>Availability of this Release</h2>

NOTE: This document

This release is available in a number of forms including:

defines the OpenPegasus 2.12.0 minor version release with

comments added to define the 2.12.1 revision to that minor

release.  OpenPegasus 2.12.1 is a bug fix revision to

OpenPegasus 2.12.0. The complete list of changes (total of 12

bugs fixed)  is defined in OpenPegasus bugzilla with the <a

href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.1_APPROVED">2.12.1_APPROVED

bugs</a> query.  We recommend that all users of 2.12.0

review this list. OpenPegasus tries to execute only bug fixes

for revision releases and not include enhancements. The

OpenPegasus team recommends that users of Pegasus 2.12.0 update

to Pegasus 2.12.1. Note that in OpenPegasus ALL changes

including enhancements are defined as bugs and committed only

when the APPROVED keyword is set so that the list in the query

above defines ALL changes between 2.11.0 and 2.11.1.

This release is available in a number of forms including:

<ul>

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

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

formats. These can be downloaded from the <span

These can be downloaded from the OpenPegasus

class="SpellE">OpenPegasus Web site at <a

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

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

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

<li>OpenPegasus source RPMs on the OpenPegasus web

source RPM is  available on the OpenPegasus web site that can be

site.. A source RPM is  available on the OpenPegasus web

used to build binaries for most LSB-compliant RPM-based Linux

site that can be used to build binaries for most LSB-compliant

distributions and versions.</li>

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

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

<li>The OpenPegasus CVS repository. The CVS tags

release and subsequent snapshots that are made available in the

representing this release and subsequent snapshots that are

Pegasus CVS are defined on the OpenPegasus CVS repository web page

made available in the Pegasus CVS are defined on the

(see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

OpenPegasus CVS repository web page (see the <a

href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

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

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

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

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

of the Pegasus source tree.

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

the root of the Pegasus source tree.

</div>

<h2>OpenPegasus Functionality in 2.12

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

Release</h2>

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

OpenPegasus overall status by release is defined by  a <a

Status WEB Page</a> that is available on the OpenPegasus web site

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

.  That web page shows the Pegasus users and developers the status of

Status WEB Page</a> that is available on the OpenPegasus web

the various features found in OpenPegasus using a simple color coded key

site .  That web page shows the Pegasus users and developers

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

the status of the various features found in OpenPegasus using a

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

OpenPegasus 2.13.0 is a major release, extending the previous Pegasus

description of each feature.

release in selected areas as described in the Pegasus  PEP defining

OpenPegasus 2.12.1 is a Revision release.

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

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

Major release includes major functionality change and 

release includes major functionality change and  incompatible

incompatible behavior changes and/or incompatible public API

behavior changes and/or incompatible public API changes,

changes,

</li>

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

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

Release and includes new functionality but maintains behavior

includes new functionality but maintains behavior and public API

and public API compatibility,

compatibility,

</li>

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

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

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

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

</ul>

The major areas of development including both enhancements and bug

ALL changes for each release are documented in the

fixes for the minor release 2.12 were as follows. Note that the

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

bugs listed represent only those features incorporated in bugs

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

without PEPS that are considered enhancements, not all bugs

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

incorporated in the release. For more information access the

this minor release can be viewed through  this link to the

PEP/BUG for each change defined below:

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

<font

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

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

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

of Major Changes for this Release

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

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

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

bordercolorlight="#CCCCCC" border="1" cellspacing="1"

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

width="82%">

The major areas of development including both enhancements and bug fixes

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:

Table of Major

Changes for this Release. Please review  Bugzilla 2.13.0

Enhancements and approved(above) for a complete list

<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

</tr>

href="https://collaboration.opengroup.org/pegasus/pp/documents/25003/PEP360_PLI_Ver1_2.html">Ver

<tr>

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

</td>

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

1.2</a>

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 width="128"><a

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

href="https://collaboration.opengroup.org/pegasus/pp/origrevdocuments/3195/PEP361_CIMCLIEmbeddedInstanceSupport.htm">Ver

primarily a development and debug extension.

</td>

<td>

</td>

1.1</a>

</tr>

<tr>

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

<td>

</td>

</tr>

<tr>

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

</td>

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

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

interop namespace

note below)

</td>

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

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

href="http://www.openpegasus.org/pp/uploads/40/23237/PEP_357_-_SNMP_v3_trap_generation_in_Pegasus_.htm"></a><a

304, Version 1.6</a>

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

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

<td>

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

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,

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

destinations and subscriptions

and sets runtime parameters

</td>

<td>

</td>

</tr>

<tr>

<td style="text-align: center;" align="left" width="7%"><a

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

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=5667">Bug

</a>and others

5667</a>

</td>

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

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

buildInstance 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

</td>

<td>Clean up  issues with building with static libraries

</td>

8952</a></td>

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

<td>

</td>

</tr>

<tr>

<td><a

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

</td>

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

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

</td>

8984</a></td>

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

<td>

</td>

</tr>

<tr>

<td><a

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

</td>

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

below for more info)

</td>

9008</a></td>

<td>Add new Indication runtime configuration variables:

maxIndicaitonDeliveryRetry Attempts  and

minIndicationdeliveryRetryInterval</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 style="color:

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

windowtext;">Enable ordered

PEGASUS_CLIENT_TRACE_ENABLE (now always compiles) </td>

indication delivery from provider through CIMServer when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE compile flag is set</td>

<td width="128"> <a

href="http://www.openpegasus.org/pp/uploads/40/22386/PEP_349_-_Improve_the_availability_of_the_CIMOM_by_better_isolation_from_faulty_providers.htm"></a>

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

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

</td>

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

9114</a>

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

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

property

some build defaults

</td>

<td>

</td>

</tr>

<tr>

<td><a

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

<td>Modify environment variable definition that controls client

tracing (See below)</td>

9136</a></td>

<td>Runtime configuration option to restrict cimserver to

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

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

default schema

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

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

<td>

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

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

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

9172</a>

</td>

<td>Add capability for administrator to override hostname

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

used by providers. This adds  new runtime

OpenSLP 2.0 (See OpenSLP 2.0 issues documented below)

configuration variable hostname and

fullyQualifiedHostName. It is necessary to upgrade

existing repositories using repupgrade utility when

upgrading from OpenPegasus less than 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

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

in general. When the server receives  ExecQuery it

(Experimental because of limited testing)

executes 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

<td>Fix connection between indication handlers and IndicationService

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

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

operations

</td>

<td>

</td>

</tr>

<tr>

<td><a

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

</td>

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

based authentication

9229</a>

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

</td>

<td>Role-based authorization extension for CMPI providers

9236</a></td>

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

version 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 between Pegasus versions. <a

The status of several components of Pegasus functionality change status

name="comtag_116">Features that have changed status can be

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

identified by a change in color from the previous release to

that

this release</a> on the <a

have

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

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

Status WEB Page</a>.

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

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

Status WEB Page</a>.

OpenPegasus 2.12

</h3>

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

Prior to version 2.12 OpenPegasus used an OpenPegasus internal

OpenPegasus Functionality Changes</h2>

variable to define "root/PG_InterOp" as the name for the

This section documents specific issues that the OpenPegasus team feels are

OpenPegasus namespace with no defined way to change this

important to OpenPegasus users with the current release (and possibly

variable.  Note that an unsupported method involving

older releases).

editing one file and rebuilding OpenPegasus was defined as a

workaround in the <a

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

href="%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">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

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

namespace in DMTF and SNIA specifications ("interop" or

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

"root/interop" with "interop" being the preferred alternative)

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

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

defined OpenPegasus interface, to continue to work with each version

OpenPegasus builder to define an alternate name for the Interop

upgrade of OpenPegasus.

namespace to either "interop" or "root/interop" (ex.

PEGASUS_INTEROP_NAMESPACE = interop).  Once this build

Effective OpenPegasus 2.12.0 a new build variable was defined 

variable is defined and OpenPegasus compiled, the actual name of

(PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus builder to define

the interop namespace is what was defined in this variable and

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

all components of OpenPegasus use this as the interop namespace

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

name include the complete OpenPegasus test suite.  The only

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

name for the interop namespace will be the name defined through

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

this build variable.

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

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

However, today OpenPegasus is committed to the single namespace

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

defined at build "(root/PG_InterOp", "interop", or

approach for implementations starting a new repository.

"root/interop"). However, a number of OpenPegasus 

installations are committed to the "root/PG_InterOp" name and

In order to supexport PEGASUS_CLIENT_TRACE=keyword:keywordport users with

must maintain their repositories through updates of OpenPegasus.

existing repositories, in 2.13.0,  migration of existing repositories

While we are working on this issue today (which means that a

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

running version of OpenPegasus must accept both the and new

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

names and not confuse clients, listeners or providers that would

for the interop namespace "root/PG_InterOp" to 

use either name) the OpenPegasus team did not complete that work

the prefered name "interop".

for this release. See bug <a

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

NOTE: If the interop namespace

for more information about possible solutions and our progress

name is redefined with PEGASUS_INTEROP_NAMESPACE clients using the

on a solution.

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

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

NOTE: If you redefine the interop namespace name with

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

PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp"

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

namespace will not connect with the updated version of

<h3>Configure Script to Control OpenPegasus Builds (OpenPegasus

OpenPegasus.

2.13.0)(Bug 9592)</h3>

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

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

<h3>Information on  IPv6 Support (PEP

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

291)</h3>

standard build environment.  However, because OpenPegasus must build

NOTE: This functionality was incorporated in OpenPegasus

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

2.7.0 but it was felt that the information below was worth

configuration tool set, this is an OpenPegasus defined configure

repeating in subsequent Release Notes

script.  The first very experimental version is part of OpenPegasu

IPv6 is

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

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

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

generation" protocol designed by the IETF to replace the

current version Internet Protocol, IP Version 4 ("IPv4"). IPv6

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

Support for OpenPegasus is documented in <a

environment variable with options in the pegasus/configure script where

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

those options are comatible with the Linux standard for defining configure

PEP 291</a>.

options and those options control the entire build process including placement

The IPv6 support in OpenPegasus is controlled by the

of output and choice of build options.

PEGASUS_ENABLE_IPV6 build variable. The default for this

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

variable is "true"; setting this to 'false' before building

OpenPegasus will disable the IPv6 support.

OpenPegasus has

long contained a hidden build controlled function to allow tracing at

The following subsections provide some information on IPv6

the client through an environment variable

support for the Linux and Windows platforms. Note that in the

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

2.6.1 release there is no automatic run-time detection of IPv6

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

support on a platform by OpenPegasus. If you build with

slightly changed

PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you

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

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

environment variable was:

bind() failure, or possibly some other failure. This applies to

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

both the CIM Server and Listener components. For more

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

information on IPv6 support for your specific platform, refer to

<pre> export PEGASUS_CLIENT_TRACE=con</pre>

the documentation for that platform.

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

2.7.0)</h3>

All OpenPegasus externals that support either a hostname or an

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but

IP address as input have been updated to allow an IPv6 address

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

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

Release Notes

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

must be specified without brackets. For example, the OpenPegasus

IPv6 Support for OpenPegasus is documented in

osinfo client (which returns information about the OS running on

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

PEP 291</a>.

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

specified as:

The IPv6 support in OpenPegasus is controlled by the PEGASUS_ENABLE_IPV6

build variable. The default for this variable is "true"; setting this to

<div style="margin-left: 40px; color: rgb(153, 51, 153);

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

font-family: monospace;"><big>osinfo -h

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

The following subsections provide some information on IPv6 support for the

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

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

option including an optional port number, requires the IPv6

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

address to be delimited with brackets, for example:

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

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

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.

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

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 or

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

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

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

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

interface would be specified as:

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

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

including an optional port number, requires the IPv6 address to be

delimited with brackets, for example:

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

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

or

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

<div style="margin-left: 40px;"><big>cimcli

monospace;">cimcli ns -l [3ffe:1:2:1]:5989</big>

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

</div>

For more information on specifying IPv6 addresses, refer to <a

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

href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP

RFC

Version 6 Addressing Architecture</a> and <a

2373 - IP Version 6 Addressing Architecture</a> and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF

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

RFC 2732 - Format for Literal IPv6 Addresses in URL's</a>.

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

<h4>IPv6 on Linux</h4>

Modern Linux distributions already contain IPv6-ready kernels,

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

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

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

possible that this module is not loaded automatically on

module is not loaded automatically on startup.

startup.

Note: you

Note: you shouldn't use

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

kernel series 2.2.x, because it's not IPv6-up-to-date anymore. Also the

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

IPv6 support in series 2.4.x is no longer improved according to

is no longer improved according to definitions in latest RFCs.

definitions in latest RFCs. It's recommend to use series 2.6.x now.

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,

into your /proc filesystem. The entry /proc/net/if_inet6 must exist. A

take a look into your /proc filesystem. The entry

short automated test looks like:

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

like:

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

kernel is IPv6 ready"</big></div>

<div style="margin-left: 40px; color: rgb(153, 51, 153);

font-family: monospace;"><big>test -f

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

/proc/net/if_inet6 && echo "Running kernel is IPv6

IPv6 in the Linux kernel and configuring network interfaces, refer to <a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux

ready"</big></div>

Documentation Project's IPv6 HOWTO</a>.

For more information on enabling IPv6 in the Linux kernel and

configuring network interfaces, refer to <a

Warning: There is currently an

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

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

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

RHEL5 and SLES10 systems. This problem is described in

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

Warning: There is

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

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

seen intermittently on RHEL5 and SLES10 systems. This problem is

described in <a

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

bug

6586</a> and

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

bug

248052</a>, and manifests itself as an intermittent IPv6

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

be significantly impacted in these environments.

248052</a>, and manifests itself as an intermittent

IPv6 socket failure. You should be aware that OpenPegasus with

IPv6 enabled may be significantly impacted in these

environments.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6 implementations for Windows

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

Microsoft provides supported IPv6 implementations for Windows Server 2003,

with Service Pack 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);

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

font-family: monospace;"><big>ipv6 install

ipv6 if</big></div>

Windows Vista and Windows Server 2008 support an integrated

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

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

stack. Note that the OpenPegasus IPv6 support has not yet been

implementation known as the Next Generation TCP/IP stack. Note that the

tested on Windows Vista or Windows Server 2008.

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

Windows Server 2008.

For more information on installing, configuring, and using IPv6

on Windows platforms, refer to the document <a

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

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,

As part of the OpenPegasus automated tests, the TestClient, g11ntest, and

g11ntest, and IndicationStressTest test clients were modified to

IndicationStressTest test clients were modified to run tests using the

run tests using the IPv6 loopback address (::1) if

IPv6 loopback address (::1) if PEGASUS_ENABLE_IPV6=true.

PEGASUS_ENABLE_IPV6=true.

You can also perform manual tests using the IPv6 loopback or a real

You can also perform manual tests using the IPv6 loopback or a

IPv6-configured network interface. For example, using the IPv6 loopback on

real IPv6-configured network interface. For example, using the

a system with OpenPegasus running on the WBEM standard http port of 5988:

IPv6 loopback on a system with OpenPegasus running on the WBEM

standard http port of 5988:

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

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

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

Considerations</a></h2>

Support for forward-compatibility is a fundamental design

Support for forward-compatibility is a fundamental design principle for

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

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

is for well-behaved OpenPegasus providers or clients, using only

OpenPegasus providers or clients, using only the externally defined

the externally defined OpenPegasus interface, to continue to

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

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

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

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

non-compliance with a standard that significantly affects

standard that significantly affects interoperability) that may

interoperability) that may require the community to make potentially

require the community to make potentially incompatible changes.

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

The following table contains a list of defects/fixes that MAY

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

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

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>

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

</tr>

<td><a

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

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

8830</a></td>

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

<td align="left">Starting

requirement for providers (CMPI and C++) to filter

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

properties from instances has been relieved. The server

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

will do the filtering at the protocol adapter level. To

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

avoid a negative impact on performance the

on performance the CIMInstance::filter() and

CIMInstance::filter() and

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

CMPIInstanceFT.setPropertyFilter() functions have been

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

changed to a NOP. This may be a change in behavior for

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

provider relying in some unknown way on the instance being

allow users to actually filter properties from an instance in a

filtered through these functions. To allow users to

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

actually filter properties from an instance, new function

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

CIMInstance::filterInstance() will actually filter

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

properties from an instance exactly as the

CIMServer will do the filtering but allows the provider to prefilter

CIMInstance::filter() did in previous versions of Pegasus.</td>

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

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

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

9369</a>

</td>

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

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

requires that the  cimserver be restarted to send the

fixed in OpenPegasus 2.13.0. Reregistering of an

enableIndication request to the providers. This issue has

indication provider requires that the  cimserver be restarted

existed starting with OpenPegasus 2.10 to the current

to send the enableIndication request to the providers. This issue

version. If the cimserver is not restarted the indication

has existed starting with OpenPegasus 2.10 to  version 2.12.

will not be enabled for the reregistered 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

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

CIM/WBEM specifications The following table defines the level of

specifications The following table defines the level of the DMTF

the DMTF specifications to which this version of Pegasus aims to

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

conform today.

<tbody>

<tr>

Line 1887

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 1908

Line 1753

</tr>

</tbody>

</table>

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

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

SMI Profiles Supported</h2>

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

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

as the SNIA SMI Indication profile it also supports this

SNIA SMI Indication profile it also supports this profile. This

profile. This profile is enabled by compiling OpenPegasus with

profile is enabled by compiling OpenPegasus with the buld variable

the build variable PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

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

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

Exceptions to DMTF Specifications</a></h2>

to DMTF Specifications</a></h2>

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

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

utilize the DMTF CIM/WBEM specifications.  However, today

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

there are a number of known differences.  As of this

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

release, some of the differences include the following:

include the following:

<ol>

<li>Provider Registration - Pegasus supports registration

<li>Provider Registration

through a set of Pegasus Provider registration classes rather

- Pegasus supports registration through a set of Pegasus Provider

than support the DMTF defined Provider Qualifier. Pegasus will

registration classes rather than support the DMTF defined Provider

not support this qualifier in the future. See the readme for

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

more information on provider registration.  This is not a

the readme for more information on provider registration.  This is

deviation from the specifications but is a different method of

not really a deviation from the specifications since there is no

registration than many CIM Servers and means that the the

specification or profile for provider registration today but is a

provider qualifier is unused in Pegasus.</li>

different method of registration than many CIM Servers and means that

<li>Lifecycle Indications -Today Pegasus supports

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

process indications and lifecycle indications when defined

<li>Lifecycle Indications -Today Pegasus supports process

specifically by providers. Pegasus does not support lifecycle

iPegasusndications and lifecycle indications when defined specifically by

indications if they are not defined by the provider or for

providers. Pegasus does not support lifecycle indications if they are

changes to CIM Classes. <span

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

class="norm"> For more

For more

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

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

size="2">  pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a><font

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

size="2">.</li>

<li> IncludeQualifiers

<li>

option

<font style="color: rgb(0, 0, 0);

on Instance Operations

font-weight: bold;">IncludeQualifiers option on Instance

- The DMTF specifications have deprecated the use of qualifiers on

Operations

instance operations with the 1.2 CIM Operations Over HTTP Specification (DSP0200) and

- The DMTF specifications have deprecated the use of

stated specifically that the client should NOT depend on the

qualifiers on instance operations with the 1.2 CIM

includeQualifiers parameter of the CIM/XML instance operations

Operations Specification and stated specifically that the

returning qualifiers.  Some CIM Client implementations expect

client should NOT depend on the includeQualifiers

instances returned from the CIM Server to include the qualifiers

parameter of the CIM/XML instance operations returning

defined in the class definition (such as KEY qualifiers on

qualifiers.  Some CIM Client implementations expect

properties).   Pegasus today expects the provider to

instances returned from the CIM Server to include the

complete the qualifiers on instances in accordance with the

qualifiers defined in the class definition (such as KEY

specification and generally the interpretation is that Pegasus

qualifiers on properties).   Pegasus

applies class level qualifiers when the includeInstance parameter is

today expects the provider to complete the qualifiers on

supplied on instance operations.  However, Pegasus today is

instances in accordance with the specification and generally

inconsistent in the return of qualifiers so that the user should NOT

the interpretation is that Pegasus applies class level

depend on Pegasus accurately honoring the includeQualifier parameter

qualifiers when the includeInstance parameter is supplied on

for instance operations.  In the future it is expected that

instance operations.  However, Pegasus today is

Pegasus will deprecate the use of qualifiers on instance operations

inconsistent in the return of qualifiers so that the user

completely.  When Pegasus uses object normalization, the

should NOT depend on Pegasus accurately honoring the

normalizer does apply qualifiers to returned instances if the

includeQualifier parameter for instance operations.  In

includeQualifiers operation parameter is set.</li>

the future it is expected that Pegasus will deprecate the

<li>LocalOnly option on instance Operations - With the 1.1

use of qualifiers on instance operations completely.

version of Specification for CIM Operations over HTTP, the definition

 When Pegasus uses object normalization, the normalizer

of the LocalOnly parameter for the GetInstance and Enumerate Instances

does apply qualifiers to returned instances if the

operations was modified. This change was incorrect, resulted in

includeQualifiers operation parameter is set.

reduced functionality and introduced a number of backward

</li>

compatibility issues. As a result of issues introduced by this change,

<li>LocalOnly option on instance Operations - With the

we strongly recommend that CIM Clients set LocalOnly = false and do

1.1 version of Specification for CIM Operations over HTTP, the

not rely on the use of this parameter to filter the set of set of

definition of the LocalOnly parameter for the GetInstance and

properties returned. See Appendix C of this specification for more

Enumerate Instances operations was modified. This change was

incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

introduced by this change, we strongly recommend that CIM

Clients set LocalOnly = false and do not rely on the use of

this parameter to filter the set of set of properties

returned. See Appendix C of this specification for more

information.</li>

<li>

<li>MultiRequest CIM/XML Option

MultiRequest Operations - Pegasus

-  Pegasus does not support the DMTF defined MultiRequest

does not support the DMTF defined MultiRequest Operation

Operation option (See DSP0200).

option.

</li>

<li>

<li>MOF Namespace Pragma -The

MOF Compiler namespace pragma -

Pegasus compiler does not support the namespace pragma defined in DSP

The 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

<li>CIMOperation Trailer - Pegasus implements chunking based on

based on the DSP0200 1.2.0 preliminary spec. including the

the DSP0200 1.2.0 preliminary spec. including the operation trailer

operation trailer defined in that specification Refer to bug <a

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

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

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

for more details. This trailer was completely removed from the

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

DSP0200 1.2 final specification as a non-compatible change so

is used Pegasus is returning a noncompliant response to enumerate type

that if chunking is used Pegasus is returning a noncompliant

requests. </li>

response to enumerate type requests. </li>

<li>Whitespace in XML value Element

<li>Whitespace in XML value

- Pegasus trims the leading and trailing whitespace from XML value

Element - Pegasus trims the leading and trailing

elements that are of the Type String.  This behavior is

whitespace from XML value elements that are of the Type

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

String.  This behavior is documented in Pegasus bug <a

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

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

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

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

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

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

documented bugs in Pegasus such as this that the OpenPegasus team

patched until pegasus does a major version update. NOTE: There

feels cannot be incorporated into the code until a major version

are some documented bugs in Pegasus such as this that the

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

OpenPegasus team feels cannot be incorporated into the code

<li>modifyInstance operation behavior

until a major version update.  These bugs are documented

in the Pegasus repository does not match the DMTF specification.

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

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

<li>modifyInstance operation

all properties rather than just the properties supplied with the

behavior in the Pegasus repository does not match the DMTF

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

specification. Under some conditions (ex. if no

propertyList is supplied) it modifies all properties rather

than just the properties supplied with the request thereby

Nulling out existing values. See bug <a

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

for more information.</li>

<li>OpenPegasus Interop Namespace - The default interop

<li>OpenPegasus Interop Namespace - The default interop namespace

namespace name in OpenPegasus is "root/PG_Interop".  In

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

versions of OpenPegasus prior to 2.12.0 this could be changed

OpenPegasus prior to 2.12.0 this could be changed during build by

during build by modifying a string definition in the code.

modifying a string definition in the code. Effective version 2.12.0

Effective version 2.12 this  has become a build option

this  has become a build option with the build configuraton

with the build configuration environment variable

environment variable PEGASUS_INTEROP_NAMESPACE = <name for this

PEGASUS_INTEROP_NAMESPACE = <name for this namespace>

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

however, the default if built without this change is still

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

"root/PG_InterOp"

</li>

<li>OpenPegasus WSMAN protocol on windows does not handle

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

NaN, INF, or -INF (bug  <a

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

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>)

- If requests or responses include properties or parameters with

- If requests or responses include properties or parameters

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

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

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

special states NaN, INF, or -INF on a Windows platform, the

accepted because these special strings are not understood by the

input is not accepted because these special strings are not

decoder on Windows.</li>

understood by the decoder on Windows.</li>

<li>OpenPegasus outputs Nan, INF, -INF special values for Real32 and

<li>OpenPegasus outputs Nan, INF, -INF special values for

Real64 property and Parameter types for the CIM/XML protocol -

Real32 and Real64 property and Parameter types for the

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

CIM/XML protocol - (bug <a

Today the DMTF Specification DSP0201 allows only numeric information

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9392">9392</a>).

in the format definition for this type and does not all the special

strings Nan, etc. However, OpenPegasus actually outputs the special

strings if  that is what is defined in the internal values. 

OpenPegasus does not allow these special Strings on input however,</li>

Today the DMTF Specification DSP0201 allows only numeric

<li>OpenPegasus does not handle covered properties - (bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">3571</a>)

information in the format definition for this type and does

not all the special strings Nan, etc. However, OpenPegasus

actually outputs the special strings if  that is what is

defined in the internal values.  OpenPegasus does not

allow these special Strings on input however,</li>

<li>OpenPegasus does not handle covered properties - (bug

<a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">3571</a>)

Covered properties (properties which have the same name in a

superclass and subclass without overridding the property in

superclass and subclass without overridding the property in the

the superclass) are not allowed in OpenPegasus. While the

superclass) are not allowed in OpenPegasus. While the requirement for

requirement for this functionality was added to DSP0004

this functionality was added to DSP0004 subsequent to version 2.4, the

subsequent to version 2.4, the general agreement is that the

general agreement is that the requirement itself is not supportable

requirement itself is not supportable and particularly not

and particularly not with the existing OpenPegasus APIs. 

with the existing OpenPegasus APIs.  Further, the

Further, the requirement is expected to be removed in the future (i.e

requirement is expected to be removed in the future (i.e CIM

CIM 3.0).

3.0).

</li>

</ol>

<h2>OpenPegasus <a

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

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

Platforms</a></h2>

Each OpenPegasus release lists as 'active'

Each OpenPegasus release lists as 'active' platforms those

platforms those hardware/software platforms that have recognized

hardware/software platforms that have recognized ports for the Pegasus

ports for the Pegasus code base including a maintainer for the

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

platform that will be willing to regularly document issues

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

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

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

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

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

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

operation of  Pegasus cannot be assured.  In all cases,

correct operation of  Pegasus cannot be assured.  In

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

all cases, including the active platforms, it is the

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

responsibility of the entity that packages and/or compiles

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

OpenPegasus for shipment or deployment, to read, and actively

relevant defects that affect their platform.   The platforms

monitor the Pegasus Bugzilla database for a list of relevant

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

defects that affect their platform.   The platforms

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

that are considered ported are shown in the two tables

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

below.  The first table represents platform for which

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

testing is done on a regular basis and reported to the Pegasus

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

Nightly Build Test WEB Page. Those platforms which have been

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

Actively Supported Platforms (Nightly Tests Reported for this release)

of the release are reported in the 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;

Platform and

-moz-background-origin: initial;

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

-moz-background-inline-policy: initial; width: 240px;"

height="26">

Platform

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

</td>

<td style="padding: 0.75pt; background: rgb(0, 255, 255)

none repeat scroll 0% 50%; -moz-background-clip: initial;

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

-moz-background-origin: initial;

-moz-background-inline-policy: initial; width: 75%;"

height="26">

Compilers<span

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

</td>

</tr>

Line 2118

Line 1928

PA_RISC and Itanium</o:p>

</td>

HP <span

HP aC++

class="SpellE">aC++ B3910B<o:p></o:p>

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

</td>

</tr>

<span

Linux

style="color: black;">Linux on Power<span

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

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

</td>

<span

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

style="color: black;">gcc<span

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

</td>

</tr>

<span

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

style="color: black;">zLinux<span

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

</td>

<span

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

style="color: black;">gcc<span

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

</td>

</tr>

Linux

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

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

</td>

<span

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

style="color: black;">gcc<span

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

</td>

</tr>

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

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

size="3">Linux IA-32</td>

IA-32</td>

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

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

style="color: black;">gcc<span

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

style="color: black;"> (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

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

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

</td>

<span

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

style="color: black;">gcc<span

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

style="color: black;">clang(The clang

compiler usage is considered experimental and is not

part of the nightly tests today)

</td>

</tr>

<tr>

<td style="vertical-align: top;">z/OS V1.7

and up</td>

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

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

Version 1.7 and up</td>

from z/OS Version 1.7 and up</td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this

Platforms not Actively supported for this release (No

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>

<td style="padding: 0.75pt; background: rgb(0, 255, 255)

none repeat scroll 0% 50%; -moz-background-clip: initial;

Platform and

-moz-background-origin: initial;

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

-moz-background-inline-policy: initial; width: 240px;"

height="26">

Platform

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

</td>

<td style="padding: 0.75pt; background: rgb(0, 255, 255)

none repeat scroll 0% 50%; -moz-background-clip: initial;

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

-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 style="padding: 0.75pt;"> Windows XP, Windows

Windows Vista, Windows 7, Windows Server 2008

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

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

</td>

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

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

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

Visual C++ Compilers 2003 - 2010.. Note: Visual C++ Ver.

the Windows. </td>

6 no longer being regular tested.Note that today there

are some open issues with the Windows. </td>

</tr>

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

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

10.3 and higher</td>

higher</td>

</tr>

<tr>

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

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

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

8</big></td>

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

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

2.95.3,  Sun CC compiler V 5.8. Note that the

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

latest thread patch (108993) may be required. (see

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

Pegasus bug 4632)</big>

</td>

</tr>

<tr>

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

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

color="RED">Solaris

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

9</big></td>

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

<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

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

C++ V7.3-009

for OpenVMS Alpha</big></td>

or later required for OpenVMS Alpha</big></td>

</tr>

<tr>

<td><big> HP OpenVMS 8.3

<td><big> HP OpenVMS 8.3 or later

or later IA64</big></td>

IA64</big></td>

<td><big>HP C++ V7.<font

<td><big>HP C++ V7.3-023

color="#993399">3-023 or later required<font

or later required on

style="color: rgb(0, 0, 0);"> on OpenVMS IA64</big></td>

OpenVMS IA64</big></td>

</tr>

<tr>

Windows

Windows 2000

2000

</td>

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

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

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

Ver.  6 and Microsoft .Net compiler version. Works on

version. Works on VC .NET 2003 v7.1). NOTE: Visual

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

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

regularly tested.</td>

</tr>

<tr>

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

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

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

</td>

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

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

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

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

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

and IX86)</big></td>

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

</tr>

</tbody>

</table>

Platform patches

<h3>Platform patches </h3>

<font

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

The following is a list known of

platform patches Pegasus requires.

platform patches Pegasus requires.

<ol>

<li>

<li> RHAS 2.1 needs the update to

<font

fix Red Hat Bugzilla 98815.

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

Further information regarding Pegasus support on IBM platforms can be

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

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>

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>

Further information regarding Pegasus support on HP platforms

Further information regarding Pegasus support on HP platforms can be found

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

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

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

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

Defects</a></h2>

The OpenPegasus Bugzilla database documents defects found in Pegasus

The OpenPegasus Bugzilla database documents any defects found

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

in Pegasus and  is available through the following

bugzilla database</a>.   Effective with the start of the

link:  <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus

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

documented through bugs. Therefore all source code changes to OpenPegasus

are documented through bugs providing a complete history of changes and

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

bugzilla database</a>.   Effective with the start of

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

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

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

documented through bugs.  Bugs reports are filed not only

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

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

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

process of committing new code representing the work on PEPs

done for OpenPegasus 2.6 and all subsequent versions. 

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

Therefore, a search of the OpenPegasus Bugzilla base for bugs

etc) will yield all changes to the Pegasus CVS tree for that OpenPegasus

with the tag for a particular version (ex.  <a

release.

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

     - Changes for this release (bugs Tagged

href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED">

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

2.6.1_APPROVED</a>, <a

Pegasus 2.13.0_APPROVED bug list.</a>

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

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

etc) will yield all changes to the Pegasus CVS tree for that

Control

OpenPegasus release.

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

- Changes between the 2.12.0 release

The OpenPegasus project is controlled largely through the CVS repository

and 2.12.1 revision are defined in bugs tagged

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

(2.12.1.APPROVED). The complete list of 12 bugs is <a

mechanism for new and modified Pegasus functionality and for the

href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.1_APPROVED">2.12.1_APPROVED

definition and documentation of releases.

The following documentation defines the characteristics of this Pegasus

bugs</a>

release. The documents are available in the OpenPegasus CVS

repository.

- Changes that were made in the minor

release 2.12 are in bugs Tagged 2.12.0_APPROVED. The link

is <a

href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.0_APPROVED">

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

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

<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

Section <a

2.13.x

href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2.12_x">OpenPegasus

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

section in the Pegasus wiki is used throughout the

Pegasus  functionality changes for this version of Pegasus. </li>

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

Build and Configuration Options  for Selected Platforms

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

-  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;"> <span style="font-family:

monospace;">pegasus/doc/BuildAndReleaseOptions.html</big>.

<li> OpenPegasus External Interfaces -<span

style="font-weight: normal;">The list of the OpenPegasus

interfaces that are considered external and therefore

"frozen". Unless an exception is explicitly approved by

the Steering Committee all subsequent releases of Pegasus

MUST continue to support these interfaces. Interfaces not

explicitly listed in this document, should be considered

as internal and subject to change.In previous Pegasus

releases this information was available as a separate PEP.

Starting with Pegasus 2.9.0 this information is integrated

into the Pegasus repositoryas  <small

style="font-weight: bold;"><font face="Courier New"

size="4">pegasus/doc/EnternalInterface.html<span

style="font-weight: normal;">.</li>

<li> OpenPegasus  SDK Packaging Definition - <span

style="font-weight: normal;">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> Pegasus  Runtime Packaging Definition - <span

style="font-weight: normal;">Defines the recommended set

of files for inclusion in this OpenPegasus release.

Starting with Pegasus release 2.11.0, this document is

contained in the CVS repository as <big

style="font-weight: bold;"><samp>pegasus/doc/RuntimePackaging.html</samp></big>.

In previous releases this was made available as a seperate

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

<li>Pegasus Release Notes - <span style="font-weight:

normal;"> PEP 364 - <span style="font-weight:

normal;"> (This document is located in the approved PEP

repository and the OpenPegasus source tree root directory

(<big style="font-weight: bold;"><span style="font-family:

monospace;">pegasus/ReleaseNotes.htm</big>)</li>

<li> OpenPegasus External Interfaces -The

list of the OpenPegasus interfaces that are considered external

and therefore "frozen". Unless an exception is explicitly approved

by the Steering Committee all subsequent releases of Pegasus MUST

continue to support these interfaces. Interfaces not explicitly

listed in this document, should be considered as internal and

subject to change.In previous Pegasus releases this information

was available as a separate PEP. Starting with Pegasus 2.9.0 this

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

<li> OpenPegasus  SDK Packaging Definition - Defines

the recommended set of files for inclusion in the OpenPegasus SDK.

Starting with Pegasus release 2.11.0, this document is available

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

In previous Pegasus releases this document was made available as s

separate Pegasus PEP document rather than in the CVS repository.

</li>

<li> Pegasus  Runtime Packaging Definition - Defines

the recommended set of files for inclusion in this OpenPegasus

release. Starting with Pegasus release 2.11.0, this idocument

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

In previous releases this was made available as a seperate Pegasus

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

<li>Pegasus Release Notes -

PEP 364 - (This document

is located in the approved PEP repository and the OpenPegasus

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 class="MsoNormal" style="color: black;">Utilities - A

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

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

</li>

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

documentation - See the header files and the HTML

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

documentation is the existing utilities and test programs and the

examples in the API documentation.  In particular the

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

Common APIs. </li>

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

Providers - Readme.html in the Pegasus source tree Root

Directory, API documentation, and documentation from the Pegasus

Technical Workshop which is available on the Pegasus web site.

</li>

A combination of help generally available with the --help

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

option for each command and HTML documentation for most of the

Clients -API documentation and the documentation on the

tools.<o:p></o:p>

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

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

</li>

usage documentation - </li>

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

See the header files and the HTML  API documentation

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

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

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

existing utilities and test programs and the examples in the API

OpenPegasus web site.  While these are the original design

documentation.  In particular the Common/tests unit tests

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

contain extensive examples of the use of the Common APIs.

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

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

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

Debugging Providers - </li>

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

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

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

documentation, and documentation from the Pegasus Technical

development team and as a user information resource.  The wiki

Workshop which is available on the Pegasus web site.

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>

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

Debugging Clients - </li>

API documentation and the documentation on the Pegasus

Technical Workshop which is available on the Pegasus web site.

The features of Pegasus that have been installed in this and

the previous few versions are defined by Pegasus PEPs that are

available on the OpenPegasus web site.  While these are the

original design documents largely and use in the process of

defining and approving the overall characteristics of new

functionality, they serve as a guide to the design and

implementation of these features.

</ul>

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

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

license agreements. Refer to the OpenPegasusNOTICE.txt file

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

distributed with this work for additional information regarding

work for additional information regarding copyright ownership. Each

contributor licenses this file to you under the OpenPegasus Open Source

under the OpenPegasus Open Source License; you may not use this

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

file except in compliance with the License.

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

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

copy of this software and associated documentation files (the

obtaining a copy of this software and associated documentation

"Software"), to deal in the Software without restriction, including

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

without limitation the rights to use, copy, modify, merge, publish,

restriction, including without limitation the rights to use,

distribute, sublicense, and/or sell copies of the Software, and to

copy, modify, merge, publish, distribute, sublicense, and/or

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

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

the following conditions:

Software is furnished to do so, subject to the following

The above copyright notice and this permission notice shall be included

conditions:

in all copies or substantial portions of the Software.

The above copyright notice and this permission notice shall be

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

included in all copies or substantial portions of the Software.

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

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

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES

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

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

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

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT

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

HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING

FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR

OTHER DEALINGS IN THE SOFTWARE.

</div>

</body>

</html>

</body></html>

Legend:

Removed from v.1.19.2.1
changed lines
	Added in v.1.20

No CVS admin address has been configured