pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

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

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

Line 1

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

<head>

http-equiv="Content-Type">

<style>

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

</style>

Line 963

Line 964

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>

<body lang="EN-US" link="blue" vlink="blue"><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags"

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

<o:smarttagtype

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

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

<span

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

style="font-size: 13.5pt; color: black;">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>

<span

style="color: black;">

PEP #: 364

Title: Release

Notes for OpenPegasus version 2.12.0

Notes for OpenPegasus version 2.12.1

Created: 10

September 2012

Authors: Karl

Schopmeyer

Schopmeyer, Marek Szermutzky

Status:  draft

Version History:

Version

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

History:

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

<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; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

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

height="27">

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

<span

-moz-background-origin: initial;

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

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

</td>

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

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

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

height="27">

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

<span

</td>

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

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

</td>

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

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

-moz-background-origin: initial;

height="27">

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

<span

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

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

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

</td>

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

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

</td>

height="27">

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

<span

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

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

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

<span

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

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

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

</td>

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

</td>

<font

size="2">10 September 2012

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

align="center"> <span

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

</td>

<span

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

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

align="center"> <font

size="2">Karl Schopmeyer

</td>

<font

<span style="font-family: Arial;

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

color: black;">Initial Submission <span

style="color: red;"><o:p><font

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

</td>

</tr>

<tr>

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

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

2012

September 2012

</td>

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

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

Schopmeyer

</td>

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

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

complete links to PEPs

and complete links to PEPs

</td>

</tr>

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

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

2012

September 2012

</td>

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

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

Schopmeyer

</td>

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

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

comments from first review

all comments from first review

</td>

</tr>

<tr>

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

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

2012

September 2012

</td>

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

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

Schopmeyer

</td>

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

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

8830 (compatibility considerations) and bug 9172(repupgrade)

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>

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

style="color: black;">

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

Abstract: This document defines the release notes for the 2.12.0

width="100%"></div>

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

Abstract: This document defines the release notes for

summarize the characteristics of this release, point to other

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

documentation that defines the release in more detail, and provide

this PEP is to summarize the characteristics of this release,

additional information about this release that is not available in the

point to other documentation that defines the release in more

other Pegasus documentation.

detail, and provide additional information about this release

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

that is not available in the other Pegasus documentation.

style="color: black;">

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

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

Release</a></li>

this Release</a></li>

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

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

of This Release</a></li>

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

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

Considerations</a></li>

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

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

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

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

Platforms</a></li>

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

with DMTF Specifications</a></li>

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

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

<li> <a

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

Release

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

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

</ol>

<h2>Availability of this Release</h2>

NOTE: This document

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

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

These can be downloaded from the OpenPegasus

formats. These can be downloaded from the <span

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

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

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

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

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

<li>OpenPegasus source RPMs on the OpenPegasus web

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

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

distributions and versions.</li>

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

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

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

release and subsequent snapshots that are made available in the

<li>The OpenPegasus CVS repository. The CVS tags

Pegasus CVS are defined on the OpenPegasus CVS repository web page

representing this release and subsequent snapshots that are

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

made available in the Pegasus CVS are defined on the

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

</ul>

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

The instructions for acquiring the released code are on the <a

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

WEB

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

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 for This Release</h2>

<h2>OpenPegasus Functionality in 2.12

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

Release</h2>

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

OpenPegasus overall status by release is defined by  a <a

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

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

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

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

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

site .  That web page shows the Pegasus users and developers

OpenPegasus 2.12.0 is a major release, extending the previous Pegasus

the status of the various features found in OpenPegasus using a

release in selected areas as described in the Pegasus  PEP defining

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

this release .

description of each feature.

OpenPegasus 2.12.1 is a Revision release.

NOTE: OpenPegasus releases are categorized as follows:

<ul>

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

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

release includes major functionality change and  incompatible

Major release includes major functionality change and 

behavior changes and/or incompatible public API changes,

incompatible behavior changes and/or incompatible public API

changes,

</li>

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

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

includes new functionality but maintains behavior and public API

Release and includes new functionality but maintains behavior

compatibility,

and public API compatibility,

</li>

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

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

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

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

</ul>

ALL changes for each release are documented in the

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

The major areas of development including both enhancements and bug

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

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

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

bugs listed represent only those features incorporated in bugs

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

without PEPS that are considered enhancements, not all bugs

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

incorporated in the release. For more information access the

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

PEP/BUG for each change defined below:

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

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

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

through corresponding Bugzilla tags for each revisions (ex

2.12.1_APPROVED).

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:

<font

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

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

Changes for this Release

of Major Changes for this Release

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

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

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

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

width="82%">

<tbody>

Line 1194

Line 1271

<td>Provider Lifecycle Indications

</td>

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

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

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

1.2</a>

</td>

</tr>

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

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

instances

</td>

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

<td width="128"><a

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

1.1</a>

</td>

</tr>

<tr>

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

</td>

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

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

namespace

interop namespace

</td>

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

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

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

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

1.5</a>

</td>

</tr>

Line 1222

Line 1312

</td>

<td>WSMan indication handling and subscription support

</td>

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

<td align="center"><a

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

<td><a

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

8891</a>

</td>

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

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

and subscriptions

destinations and subscriptions

</td>

<td>

</td>

</tr>

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

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

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

5667</a>

</td>

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

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

and filter functions in CIMInstance class

buildInstance and filter functions in CIMInstance class

</td>

</td>

</tr>

<tr>

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

<td><a

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

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

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

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

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

9008</a></td>

<td>Add new Indication runtime configuration variables:

maxIndicaitonDeliveryRetry Attempts  and

Line 1270

Line 1384

</td>

</tr>

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

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

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

9013</a>

</td>

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

<td align="left" width="75%"><span style="color:

style="">Enable ordered indication delivery from

windowtext;">Enable ordered

provider through CIMServer when

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

<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

<td> Guaranteed provider

indication delivery during CIMServer shutdonw </td>

lifecycle indication delivery during CIMServer shutdown </td>

</td>

</tr>

<tr>

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

<td><a

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

9112</a>

</td>

<td>Advertise IndicationService conformance to Indications Profileby

<td>Advertise IndicationService conformance to Indications

imlementing CIM_ElementConformsToProfile when

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

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

9114</a>

</td>

<td>Advertise DMTF Indications Profile (DSP1054) 1.1.0 conformance </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

<td><a

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

9118</a>

</td>

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

<td>Add support for CIM_IndicationFilter.SourceNamespaces[]

property

</td>

<td>

</td>

</tr>

<tr>

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

<td><a

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

9136</a></td>

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

<td>Runtime configuration option to restrict cimserver to

selected network interfaces</td>

listen on selected network interfaces</td>

<td>

</td>

</tr>

<tr>

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

<td><a

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

9155</a>

</td>

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

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

default schema

</td>

<td>

</td>

</tr>

<tr>

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

<td><a

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

9159</a></td>

<td>

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

<table style="font-family: Arial;"

bordercolordark="#666666" bordercolorlight="#CCCCCC"

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

<tbody>

<tr>

Line 1350

Line 1501

</td>

</tr>

<tr>

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

<td><a

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

9172</a>

</td>

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

<td>Add capability for administrator to override hostname

providers. This adds  new runtime configuration variable

used by providers. This adds  new runtime

hostname and fullyQualifiedHostName. It is necessary to upgrade

configuration variable hostname and

existing repositories using repupgrade utility when upgrading from

fullyQualifiedHostName. It is necessary to upgrade

OpenPegasus less that 2.12.0 and reusing an existing repository.

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

<td><a

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

9215</a>

</td>

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

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

general. When the server receives  ExecQuery it executes

in general. When the server receives  ExecQuery it

enumerate instance for providers that do not support ExecQuery and

executes enumerate instance for providers that do not

filters result.

support ExecQuery and filters result.

</td>

<td>

</td>

</tr>

<tr>

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

<td><a

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

9209 </a>

</td>

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

<td>Add operations for display class tree and counting

cimcli

instances to cimcli

</td>

<td>

</td>

</tr>

<tr>

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

<td><a

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

9227</a>

</td>

<td>Enhance cimsub for batches of subscription oriented operations

<td>Enhance cimsub for batches of subscription oriented

operations

</td>

<td>

</td>

</tr>

<tr>

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

<td><a

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

9229</a>

</td>

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

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

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

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

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

9236</a></td>

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

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

supports only X86 and X86_64 and requires clang version 3 or

version supports only X86 and X86_64 and requires clang

greater.

version 3 or greater.

</td>

<td>

</td>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality change status

The status of several components of Pegasus functionality

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

change status between Pegasus versions. <a

that

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

have

identified by a change in color from the previous release to

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

this release</a> on the <a

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

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

Status WEB Page</a>.

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

OpenPegasus 2.12

</h3>

Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable

Prior to version 2.12 OpenPegasus used an OpenPegasus internal

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

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

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

OpenPegasus namespace with no defined way to change this

unsupported method involving editing one file and rebuilding OpenPegasus

variable.  Note that an unsupported method involving

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

editing one file and rebuilding OpenPegasus was defined as a

workaround in the <a

href="%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus

wiki faq</a>s.

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

However, since the definition of a standard name for this

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

namespace in DMTF and SNIA specifications ("interop" or

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

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

become an issue.

the use of  "root/PG_InterOp" has become an issue.

Effective OpenPegasus 2.12.0 a new build variable has been

defined  (PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus

defined  (PEGASUS_INTEROP_NAMESPACE) which allows an

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

OpenPegasus builder to define an alternate name for the Interop

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

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

interop).  Once this build variable is defined and OpenPegasus

PEGASUS_INTEROP_NAMESPACE = interop).  Once this build

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

variable is defined and OpenPegasus compiled, the actual name of

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

the interop namespace is what was defined in this variable and

interop namespace name include the complete OpenPegasus test

all components of OpenPegasus use this as the interop namespace

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

name include the complete OpenPegasus test suite.  The only

defined through this build variable.

name for the interop namespace will be the name defined through

this build variable.

However, today OpenPegasus is committed to the single namespace defined

However, today OpenPegasus is committed to the single namespace

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

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

number of OpenPegasus  installations are committed to the

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

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

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

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

must maintain their repositories through updates of OpenPegasus.

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

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

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

running version of OpenPegasus must accept both the and new

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

names and not confuse clients, listeners or providers that would

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

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

for more information about possible solutions and our progress on a

for this release. See bug <a

solution.

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

for more information about possible solutions and our progress

on a solution.

NOTE: If you redefine the interop namespace name with

PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp" namespace

PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp"

will not connect with the updated version of OpenPegasus.

namespace will not connect with the updated version of

OpenPegasus.

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

<h3>Information on  IPv6 Support (PEP

NOTE: This functionality was incorporated in OpenPegasus 2.7.0

291)</h3>

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

NOTE: This functionality was incorporated in OpenPegasus

subsequent Release Notes

2.7.0 but it was felt that the information below was worth

IPv6 is short

repeating in subsequent Release Notes

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

IPv6 is

protocol designed by the IETF to replace the current version Internet

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

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

generation" protocol designed by the IETF to replace the

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

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

Support for OpenPegasus is documented in <a

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

PEP 291</a>.

The IPv6 support in OpenPegasus is controlled by the

PEGASUS_ENABLE_IPV6 build variable. The default for this variable is

PEGASUS_ENABLE_IPV6 build variable. The default for this

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

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

the IPv6 support.

OpenPegasus will disable the IPv6 support.

The following subsections provide some information on IPv6 support for

The following subsections provide some information on IPv6

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

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

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

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

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

support on a platform by OpenPegasus. If you build with

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

PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you

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

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

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

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

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

both the CIM Server and Listener components. For more

documentation for that platform.

information on IPv6 support for your specific platform, refer to

the documentation for that platform.

All OpenPegasus externals that support either a hostname or an IP

All OpenPegasus externals that support either a hostname or an

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

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

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

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

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

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

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

must be specified without brackets. For example, the OpenPegasus

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

osinfo client (which returns information about the OS running on

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

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

IPv6-configured network interface would be specified as:

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

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

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

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

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

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

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

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

delimited with brackets, for example:

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

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

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

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

or

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

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

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

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

</div>

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

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

RFC

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

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

Version 6 Addressing Architecture</a> and <a

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

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

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

<h4>IPv6 on Linux</h4>

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

Modern Linux distributions already contain IPv6-ready kernels,

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

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

this module is not loaded automatically on startup.

possible that this module is not loaded automatically on

Note: you shouldn't use

startup.

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

Note: you

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

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

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

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

is no longer improved according to definitions in latest RFCs.

It's recommend to use series 2.6.x now.

To check whether your current running kernel supports IPv6, take a look

To check whether your current running kernel supports IPv6,

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

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

color="#000000">test -f /proc/net/if_inet6 && echo "Running

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

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

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

ready"</big></div>

For more information on enabling IPv6 in the Linux kernel and

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

configuring network interfaces, refer to <a

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

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

Warning: There is currently an

Warning: There is

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

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

on RHEL5 and SLES10 systems. This problem is described in

seen intermittently on RHEL5 and SLES10 systems. This problem is

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

described in <a

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

bug

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

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

Microsoft provides supported IPv6 implementations for Windows

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

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

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

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

On Windows XP, you can use the ipv6.exe

tool to install, uninstall, and query your IPv6 configuration. For

example:

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

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

color="#000000">ipv6 install

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

ipv6 if</big></div>

Windows Vista and Windows Server 2008 support an integrated IPv4 and

Windows Vista and Windows Server 2008 support an integrated

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

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

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

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

Windows Server 2008.

tested on Windows Vista or Windows Server 2008.

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

For more information on installing, configuring, and using IPv6

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

on Windows platforms, refer to the document <a

href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"><font

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

Questions</a>.

<h4>Testing  OpenPegasus IPv6 support</h4>

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

As part of the OpenPegasus automated tests, the TestClient,

IndicationStressTest test clients were modified to run tests using the

g11ntest, and IndicationStressTest test clients were modified to

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

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

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 Considerations</a></h2>

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

Support for forward-compatibility is a fundamental design principle for

Considerations</a></h2>

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

Support for forward-compatibility is a fundamental design

OpenPegasus providers or clients, using only the externally defined

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

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

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

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

the externally defined OpenPegasus interface, to continue to

non-compliance with a standard that significantly affects

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

interoperability) that may require the community to make potentially

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

incompatible changes. The following table contains a list of

standard that significantly affects interoperability) that may

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

require the community to make potentially incompatible changes.

or clients when upgrading to this OpenPegasus release.

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

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

upgrading to this OpenPegasus release.

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

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

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

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

width="80%">

<tbody>

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

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

</tr>

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

<td><a

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

8830</a></td>

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

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

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

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

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

properties from instances has been relieved. The server

protocol adapter level. To avoid a negative impact on performance

will do the filtering at the protocol adapter level. To

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

avoid a negative impact on performance the

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

CIMInstance::filter() and

behavior for provider relying in some unknown way on the instance

CMPIInstanceFT.setPropertyFilter() functions have been

being filtered through these functions. To allow users to actually

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

filter properties from an instance, new function

provider relying in some unknown way on the instance being

CIMInstance::filterInstance() will actually filter properties from

filtered through these functions. To allow users to

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

actually filter properties from an instance, new function

versions of Pegasus.</td>

CIMInstance::filterInstance() will actually filter

properties from an instance exactly as the

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

</tr>

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

<td><a

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

9369</a>

</td>

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

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

that the  cimserver be restarted to send the enableIndication

requires that the  cimserver be restarted to send the

request to the providers. This issue has existed starting with

enableIndication request to the providers. This issue has

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

existed starting with OpenPegasus 2.10 to the current

restarted the indication will not be enabled for the reregistered

version. If the cimserver is not restarted the indication

provider. </td>

will not be enabled for the reregistered provider. </td>

</tr>

</tbody>

</table>

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

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

Pegasus was designed and implemented to comply with the DMTF

specifications The following table defines the level of the DMTF

CIM/WBEM specifications The following table defines the level of

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

the DMTF specifications to which this version of Pegasus aims to

conform today.

<tbody>

<tr>

Line 1681

Line 1908

</tr>

</tbody>

</table>

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

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

Profiles Supported</h2>

SMI Profiles Supported</h2>

Today OpenPegasus includes support for several DMTF profiles including

Today OpenPegasus includes support for several DMTF profiles

the ones defined below:

including the ones defined below:

<ol>

<li>DMTF ProfileRegistration Version 1.0.0</li>

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

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

SNIA SMI Indication profile it also supports this profile. This

as the SNIA SMI Indication profile it also supports this

profile is enabled by compiling OpenPegasus with the buld variable

profile. This profile is enabled by compiling OpenPegasus with

PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

the build variable PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

</li>

<li>SNIA Profile Registration 1.0.0</li>

<li>SNIA Server 1.1.0 & 1.2.0

</li>

</ol>

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

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

to DMTF Specifications</a></h2>

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

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

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

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

utilize the DMTF CIM/WBEM specifications.  However, today

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

there are a number of known differences.  As of this

differences include the following:

release, some of the differences include the following:

<ol>

<li>Provider Registration - Pegasus supports registration through

<li>Provider Registration - Pegasus supports registration

a set of Pegasus Provider registration classes rather than support the

through a set of Pegasus Provider registration classes rather

DMTF defined Provider Qualifier. Pegasus will not support this

than support the DMTF defined Provider Qualifier. Pegasus will

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

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

provider registration.  This is not a deviation from the

more information on provider registration.  This is not a

specifications but is a different method of registration than many CIM

deviation from the specifications but is a different method of

Servers and means that the the provider qualifier is unused in

registration than many CIM Servers and means that the the

Pegasus.</li>

provider qualifier is unused in Pegasus.</li>

<li>Lifecycle Indications -Today Pegasus supports process

<li>Lifecycle Indications -Today Pegasus supports

indications and lifecycle indications when defined specifically by

process indications and lifecycle indications when defined

providers. Pegasus does not support lifecycle indications if they are

specifically by providers. Pegasus does not support lifecycle

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

indications if they are not defined by the provider or for

For more

changes to CIM Classes. <span

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

class="norm"> For more

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

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

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

size="2">.</li>

<li>

IncludeQualifiers

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

option

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

on Instance Operations

Operations

- The DMTF specifications have deprecated the use of qualifiers on

- The DMTF specifications have deprecated the use of

instance operations with the 1.2 CIM Operations Specification and

qualifiers on instance operations with the 1.2 CIM

stated specifically that the client should NOT depend on the

Operations Specification and stated specifically that the

includeQualifiers parameter of the CIM/XML instance operations

client should NOT depend on the includeQualifiers

returning qualifiers.  Some CIM Client implementations expect

parameter of the CIM/XML instance operations returning

instances returned from the CIM Server to include the qualifiers

qualifiers.  Some CIM Client implementations expect

defined in the class definition (such as KEY qualifiers on

instances returned from the CIM Server to include the

properties).   Pegasus today expects the

qualifiers defined in the class definition (such as KEY

provider to complete the qualifiers on instances in accordance with

qualifiers on properties).   Pegasus

the specification and generally the interpretation is that Pegasus

today expects the provider to complete the qualifiers on

applies class level qualifiers when the includeInstance parameter is

instances in accordance with the specification and generally

supplied on instance operations.  However, Pegasus today is

the interpretation is that Pegasus applies class level

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

qualifiers when the includeInstance parameter is supplied on

depend on Pegasus accurately honoring the includeQualifier parameter

instance operations.  However, Pegasus today is

for instance operations.  In the future it is expected that

inconsistent in the return of qualifiers so that the user

Pegasus will deprecate the use of qualifiers on instance operations

should NOT depend on Pegasus accurately honoring the

completely.  When Pegasus uses object normalization, the

includeQualifier parameter for instance operations.  In

normalizer does apply qualifiers to returned instances if the

the future it is expected that Pegasus will deprecate the

use of qualifiers on instance operations completely.

 When Pegasus uses object normalization, the normalizer

does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.

</li>

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

<li>LocalOnly option on instance Operations - With the

version of Specification for CIM Operations over HTTP, the definition

1.1 version of Specification for CIM Operations over HTTP, the

of the LocalOnly parameter for the GetInstance and Enumerate Instances

definition of the LocalOnly parameter for the GetInstance and

operations was modified. This change was incorrect, resulted in

Enumerate Instances operations was modified. This change was

reduced functionality and introduced a number of backward

incorrect, resulted in reduced functionality and introduced a

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

number of backward compatibility issues. As a result of issues

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

introduced by this change, we strongly recommend that CIM

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

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

properties returned. See Appendix C of this specification for more

this parameter to filter the set of set of properties

returned. See Appendix C of this specification for more

information.</li>

<li>

MultiRequest Operations - Pegasus does not

MultiRequest Operations - Pegasus

support the DMTF defined MultiRequest Operation option.

does not support the DMTF defined MultiRequest Operation

option.

</li>

<li>

MOF Compiler namespace pragma - The

MOF Compiler namespace pragma -

Pegasus compiler does not support the namespace pragma.

The Pegasus compiler does not support the namespace pragma.

</li>

<li>CIMOperation Trailer - Pegasus implements chunking based on

<li>CIMOperation Trailer - Pegasus implements chunking

the DSP0200 1.2.0 preliminary spec. including the operation trailer

based on the DSP0200 1.2.0 preliminary spec. including the

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

operation trailer defined in that specification Refer to bug <a

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

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

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

for more details. This trailer was completely removed from the

is used Pegasus is returning a noncompliant response to enumerate type

DSP0200 1.2 final specification as a non-compatible change so

requests. </li>

that if chunking is used Pegasus is returning a noncompliant

<li>Whitespace in XML value Element

response to enumerate type requests. </li>

- Pegasus trims the leading and trailing whitespace from XML value

<li>Whitespace in XML value

elements that are of the Type String.  This behavior is

Element - Pegasus trims the leading and trailing

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

whitespace from XML value elements that are of the Type

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

String.  This behavior is documented in Pegasus bug <a

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

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

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

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

documented bugs in Pegasus such as this that the OpenPegasus team

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

feels cannot be incorporated into the code until a major version

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

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

are some documented bugs in Pegasus such as this that the

<li>modifyInstance operation behavior

OpenPegasus team feels cannot be incorporated into the code

in the Pegasus repository does not match the DMTF specification.

until a major version update.  These bugs are documented

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

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

all properties rather than just the properties supplied with the

<li>modifyInstance operation

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

behavior in the Pegasus repository does not match the DMTF

specification. Under some conditions (ex. if no

propertyList is supplied) it modifies all properties rather

than just the properties supplied with the request thereby

Nulling out existing values. See bug <a

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

for more information.</li>

<li>OpenPegasus Interop Namespace - The default interop namespace

<li>OpenPegasus Interop Namespace - The default interop

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

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

OpenPegasus prior to 2.12.0 this could be changed during build by

versions of OpenPegasus prior to 2.12.0 this could be changed

modifying a string definition in the code. Effective version 2.12

during build by modifying a string definition in the code.

this  has become a build option with the build configuraton

Effective version 2.12 this  has become a build option

environment variable PEGASUS_INTEROP_NAMESPACE = <name for this

with the build configuration environment variable

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

PEGASUS_INTEROP_NAMESPACE = <name for this namespace>

still "root/PG_InterOp"

however, the default if built without this change is still

"root/PG_InterOp"

</li>

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

<li>OpenPegasus WSMAN protocol on windows does not handle

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

NaN, INF, or -INF (bug  <a

- If requests or responses include properties or parameters with

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

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

- If requests or responses include properties or parameters

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

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

accepted because these special strings are not understood by the

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

decoder on Windows.</li>

input is not accepted because these special strings are not

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

understood by the decoder on Windows.</li>

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

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

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

Real32 and Real64 property and Parameter types for the

Today the DMTF Specification DSP0201 allows only numeric information

CIM/XML protocol - (bug <a

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

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

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

Today the DMTF Specification DSP0201 allows only numeric

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 the

superclass and subclass without overridding the property in

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

the superclass) are not allowed in OpenPegasus. While the

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

requirement for this functionality was added to DSP0004

general agreement is that the requirement itself is not supportable

subsequent to version 2.4, the general agreement is that the

and particularly not with the existing OpenPegasus APIs. 

requirement itself is not supportable and particularly not

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

with the existing OpenPegasus APIs.  Further, the

CIM 3.0).

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

3.0).

</li>

</ol>

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

<h2>OpenPegasus <a

Platforms</a></h2>

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

Each OpenPegasus release lists as 'active' platforms those

Each OpenPegasus release lists as 'active'

hardware/software platforms that have recognized ports for the Pegasus

platforms those hardware/software platforms that have recognized

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

ports for the Pegasus code base including a maintainer for the

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

platform that will be willing to regularly document issues

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

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

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

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

maintenance, correct operation of  Pegasus cannot be assured. 

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

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

correct operation of  Pegasus cannot be assured.  In

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

all cases, including the active platforms, it is the

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

responsibility of the entity that packages and/or compiles

for a list of relevant defects that affect their platform.  

OpenPegasus for shipment or deployment, to read, and actively

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

monitor the Pegasus Bugzilla database for a list of relevant

below.  The first table represents platform for which testing is

defects that affect their platform.   The platforms

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

that are considered ported are shown in the two tables

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

below.  The first table represents platform for which

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

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

second table.

Nightly Build Test WEB Page. Those platforms which have been

Actively Supported Platforms (Nightly Tests Reported for this release)

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

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

of the release are reported in the second table.

cellspacing="1">

Actively Supported Platforms (Nightly Tests Reported for this

release)

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

cellpadding="0" cellspacing="1">

<tbody>

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

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

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

-moz-background-origin: initial;

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

height="26">

Platform and

Platform

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

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;

-moz-background-origin: initial;

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

height="26">

Compilers<span

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

Line 1860

Line 2118

PA_RISC and Itanium</o:p>

</td>

HP aC++

HP <span

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

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

</td>

</tr>

Linux

<span

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

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

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

</td>

gcc<span

<span

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

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

</td>

</tr>

zLinux<span

<span

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

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

</td>

gcc<span

<span

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

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

</td>

</tr>

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

Linux

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

</td>

gcc<span

<span

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

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

</td>

</tr>

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

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

IA-32</td>

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

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

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

size="3">gcc<font

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

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

style="color: black;"> (versions 3.xx,

is considered experimental and is not part of the nightly

4.xx) clang(The clang compiler usage is considered

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

experimental and is not part of the nightly tests

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

</tr>

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

Linux

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

</td>

gcc<span

<span

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

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

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

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

experimental and is not part of the nightly tests today)

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

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

and up</td>

Version 1.7 and up</td>

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

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

</tr>

</tbody>

</table>

Platforms not Actively supported for this release (No

Platforms not Actively supported for this

current Nightly Build Test Results

release (No current Nightly Build Test Results

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

<table class="MsoNormalTable" style="width: 90%;" id="table2"

cellspacing="1">

border="1" cellpadding="0" cellspacing="1">

<tbody>

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

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

-moz-background-origin: initial;

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

height="26">

Platform and

Platform

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

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;

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

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

Vista, Windows 7, Windows Server 2008

Windows Vista, Windows 7, Windows Server 2008

</td>

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

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

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

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

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

6 no longer being regular tested.Note that today there

the Windows. </td>

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

</tr>

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

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

higher</td>

10.3 and higher</td>

</tr>

<tr>

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

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

8</big></td>

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

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

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

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

2.95.3,  Sun CC compiler V 5.8. Note that the

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

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

Pegasus bug 4632)</big>

</td>

</tr>

<tr>

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

color="RED">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 C++ V<span

<td><big>HP

style="color: rgb(153, 51, 153);">7.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 or later

<td><big> HP OpenVMS 8.3

IA64</big></td>

or later IA64</big></td>

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

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

or later required on

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

OpenVMS IA64</big></td>

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

</tr>

<tr>

Windows 2000

Windows

2000

</td>

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

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

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

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

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

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

regularly tested.</td>

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

</tr>

<tr>

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

</td>

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

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

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

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

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

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

tested. </td>

</tr>

<tr>

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

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

and IX86)</big></td>

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

</tr>

</tbody>

</table>

Platform patches

The

<font

following is a list known of platform patches Pegasus requires.

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

platform patches Pegasus requires.

<ol>

<li>

RHAS

<font

2.1

style="color: rgb(0, 0, 0);">RHAS 2.1 needs the update

needs the update to fix Red Hat Bugzilla 98815.

to fix Red Hat Bugzilla 98815.

</li>

<li>

RHEL 4.4

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

multithreading bug in getpwuid-r could cause a CIM Server

(Bugzilla 6232). This is fixed in RHEL 4.5

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

</li>

<li>

Red Hat and SUSE

Red Hat and

Linux multiple versions - multithreaded client intermittently

SUSE Linux multiple versions - multithreaded client

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

intermittently fails connecting to IPv6 (Pegasus Bugzilla

248052)

6586) (Red Hat bug 248052)

</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can be

Further information regarding Pegasus support on IBM platforms

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

can be found at: <a

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

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

Further information regarding Pegasus support on HP platforms

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

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

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

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

The OpenPegasus Bugzilla database documents any defects found in

Defects</a></h2>

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

The OpenPegasus Bugzilla database documents any defects found

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

in Pegasus and  is available through the following

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

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

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

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

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

subsequent versions.  Therefore, a search of the OpenPegasus

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

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

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

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

documented through bugs.  Bugs reports are filed not only

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

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

process of committing new code representing the work on PEPs

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

done for OpenPegasus 2.6 and all subsequent versions. 

release.

Therefore, a search of the OpenPegasus Bugzilla base for bugs

- Changes for this release (bugs Tagged

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

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

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

Pegasus 2.12.0_APPROVED bug list.</a>

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

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

Control

2.6.1_APPROVED</a>, <a

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

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

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

OpenPegasus release.

- Changes between the 2.12.0 release

and 2.12.1 revision are defined in bugs tagged

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

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

bugs</a>

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

functionality and for the definition and documentation of

The following documentation defines the characteristics of this Pegasus

releases.

release. The documents are available in the OpenPegasus CVS

The following documentation defines the characteristics of this

repository.

Pegasus release. The documents are available in the

OpenPegasus CVS repository.

<ul>

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

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

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

Section <a

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

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

section in the Pegasus wiki is used throughout the

development of this version as the control point for

functionality that will go into the release and points to

all of the PEPs that represent the Pegasus 

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

OpenPegasus

Build and Configuration Options  for Selected Platforms -  <span

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

information was  released as a Pegasus PEP. Starting with

Pegasus 2.9.0 the information is located in the OpenPegasus CVS

Build and Configuration Options  for Selected Platforms

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

-  In previous

<li> OpenPegasus External Interfaces -The

versions of Pegasus this information was  released as a

list of the OpenPegasus interfaces that are considered external

Pegasus PEP. Starting with Pegasus 2.9.0 the information is

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

located in the OpenPegasus CVS repository as <big

by the Steering Committee all subsequent releases of Pegasus MUST

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

continue to support these interfaces. Interfaces not explicitly

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

listed in this document, should be considered as internal and

<li> OpenPegasus External Interfaces -<span

subject to change.In previous Pegasus releases this information

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

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

interfaces that are considered external and therefore

information is integrated into the Pegasus repositoryas  <small

"frozen". Unless an exception is explicitly approved by

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

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

<li> OpenPegasus  SDK Packaging Definition - <span

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

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

Starting with Pegasus release 2.11.0, this document is available

of files for inclusion in the OpenPegasus SDK. Starting

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

with Pegasus release 2.11.0, this document is available in

In previous Pegasus releases this document was made available as s

the Pegasus CVS repository as <big style="font-weight:

separate Pegasus PEP document rather than in the CVS repository.

bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>.

</li>

In previous Pegasus releases this document was made

<li> Pegasus  Runtime Packaging Definition - Defines

available as s separate Pegasus PEP document rather than

the recommended set of files for inclusion in this OpenPegasus

in the CVS repository.  </li>

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

<li> Pegasus  Runtime Packaging Definition - <span

In previous releases this was made available as a seperate Pegasus

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

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

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

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

364 - (This document is located

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

in the approved PEP repository and the OpenPegasus source tree

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

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

repository and the OpenPegasus source tree root directory

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

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

</ul>

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

The following documentation is available for the this Pegasus

The following documentation is available for the this

release:

Pegasus release:

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

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

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

</li>

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

A combination of help generally available with the --help

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

option for each command and HTML documentation for most of the

documentation - </li>

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

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

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

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

usage documentation - </li>

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

See the header files and the HTML  API documentation

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

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

use of the Common APIs.

existing utilities and test programs and the examples in the API

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

documentation.  In particular the Common/tests unit tests

Providers - </li>

contain extensive examples of the use of the Common APIs.

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

Debugging Providers - </li>

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

documentation, and documentation from the Pegasus Technical Workshop

documentation, and documentation from the Pegasus Technical

which is available on the Pegasus web site.

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

Clients - </li>

API documentation and the documentation on the Pegasus Technical

Workshop which is available on the Pegasus web site.

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

The features of Pegasus that have been installed in this and

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

the previous few versions are defined by Pegasus PEPs that are

the OpenPegasus web site.  While these are the original design

available on the OpenPegasus web site.  While these are the

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

original design documents largely and use in the process of

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

defining and approving the overall characteristics of new

the design and implementation of these features.

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 license

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

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

license agreements. Refer to the OpenPegasusNOTICE.txt file

work for additional information regarding copyright ownership. Each

distributed with this work for additional information regarding

contributor licenses this file to you under the OpenPegasus Open Source

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

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

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

file except in compliance with the License.

copy of this software and associated documentation files (the

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

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

obtaining a copy of this software and associated documentation

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

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

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

restriction, including without limitation the rights to use,

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

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

the following conditions:

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

The above copyright notice and this permission notice shall be included

Software is furnished to do so, subject to the following

in all copies or substantial portions of the Software.

conditions:

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

The above copyright notice and this permission notice shall be

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

included in all copies or substantial portions of the Software.

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

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

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

EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES

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

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

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

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

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

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>

Legend:

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

No CVS admin address has been configured