pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.17.4.3, 2013/07/20 18:32:34

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 965

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>

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

OpenPegasus Enhancement

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

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

width="100%"></div>

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

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

PEP #: 366

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

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

Version

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)

<o:p> </o:p>

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

</td>

-moz-background-origin: initial;

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

<o:p> </o:p>

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

</td>

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

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

<o:p> </o:p>

</td>

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

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

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

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

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

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

</td>

11 July 2013

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

align="center"> <span

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

</td>

Karl Schopmeyer

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

align="center"> <font

size="2">Karl Schopmeyer

</td>

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

<span style="font-family: Arial;

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>

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

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

September 2012

</td>

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

Schopmeyer

</td>

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

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

before review

and complete links to PEPs

</td>

</tr>

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

</td>

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

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

September 2012

</td>

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

Schopmeyer

</td>

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

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

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

all comments from first review

Functionality"

</td>

</tr>

<tr>

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

</td>

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

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

September 2012

</td>

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

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

Schopmeyer

</td>

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

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

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"

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

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 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="#Notes_on_Specific_OpenPegasus">Notes on Specific

OpenPegasus Functionality</a>

</li>

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

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

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

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

This release is available in a number of forms including:

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

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

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

the status of the various features found in OpenPegasus using a

OpenPegasus 2.13.0 is a major release, extending the previous Pegasus

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

release in selected areas as described in the Pegasus  PEP defining

description of each feature.

this release .

OpenPegasus 2.12.1 is a Revision release.

NOTE: OpenPegasus releases are categorized as follows:

NOTE: OpenPegasus releases are categorized as follows:

<ul>

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

<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.12.0 2.13.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.13.0 to 2.13.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

The major areas of development including both enhancements and bug

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

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

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

bugs listed represent only those features incorporated in bugs

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

without PEPS that are considered enhancements, not all bugs

this minor release can be viewed through  this link to the

incorporated in the release. For more information access the

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

PEP/BUG for each change defined below:

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

<font

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

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

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

of Major Changes for this Release

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

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

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

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

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>Fixed issues where Pegasus compiler converted Schema Qualifer

<td>Provider Lifecycle Indications

decl to CLASS</td>

<td>

</td>

</tr>

<tr>

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

</td>

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

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

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

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

<td>

1.2</a>

</td>

</tr>

<tr>

</td>

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

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

instances

primarily a development and debug extension.

</td>

<td>

</td>

</tr>

<td width="128"><a

<tr>

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

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

<td>

1.1</a>

</td>

</tr>

<tr>

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

</td>

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

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

note below)

interop namespace

</td>

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

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

304, Version 1.6</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>

<tr>

<td align="left">PEP 358

</td>

<td>Support clang compiler in Production Build

<td>WSMan indication handling and subscription support

</td>

<td>

<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

8891</a>

</td>

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

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

and sets runtime parameters

destinations and subscriptions

</td>

<td>

</td>

</tr>

<tr>

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

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

</a>and others

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

5667</a>

</td>

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

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

unused variable warnings and set compiler defaults to make these

buildInstance and filter functions in CIMInstance class

warnings a build error.

</td>

</td>

</tr>

<tr>

<td><a

</td>

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

<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

</td>

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

<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

</td>

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

<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%">Remove compile option

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

PEGASUS_CLIENT_TRACE_ENABLE (now always compiles) </td>

windowtext;">Enable ordered

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>

<td>Fix issues requiring restart of cimserver  if indication

</tr>

provider reregistered

<tr>

<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

</td>

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

<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>Update env_var_LINUX.status and env_var_HPUX.status to change

<td>Add support for CIM_IndicationFilter.SourceNamespaces[]

some build defaults

property

</td>

<td>

</td>

</tr>

<tr>

<td><a

<td>Modify environment variable definition that controls client

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

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

</td>

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

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

mode for WSMAN indications

9155</a>

</td>

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

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

default schema

</td>

</tr>

<tr>

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

<td>

</td>

</tr>

<tr>

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

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

<tbody>

<tr>

<td>Add SSL Support to Dynamic Listener

</td>

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

</tr>

operations(see below for more comments)

</tbody>

</table>

</td>

<td>

</td>

</tr>

<tr>

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

<td><a

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

9172</a>

</td>

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

<td>Add capability for administrator to override hostname

OpenSLP 2.0 (See OpenSLP 2.0 issues documented below)

used by providers. This adds  new runtime

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>Support for ARM 64 CPU by adding platform definition

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

(Experimental because of limited testing)

in general. When the server receives  ExecQuery it

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>Fix connection between indication handlers and IndicationService

<td>Add operations for display class tree and counting

so that OnFatalErrorPolicy works

instances to cimcli

</td>

<td>

</td>

</tr>

<tr>

<td><a

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

9227</a>

</td>

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

<td>Enhance cimsub for batches of subscription oriented

operations

</td>

<td>

</td>

</tr>

<tr>

<td><a

</td>

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

<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

</td>

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

<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

The status of several components of Pegasus functionality change status

change status between Pegasus versions. <a

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

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

that

identified by a change in color from the previous release to

have

this release</a> on the <a

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

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

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

Status WEB Page</a>.

Status WEB Page</a>.

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

OpenPegasus 2.12

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

</h3>

OpenPegasus Functionality Changes</h2>

Prior to version 2.12 OpenPegasus used an OpenPegasus internal

This section documents specific issues that the OpenPegasus team feels are

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

important to OpenPegasus users with the current release (and possibly

OpenPegasus namespace with no defined way to change this

older releases).

variable.  Note that an unsupported method involving

editing one file and rebuilding OpenPegasus was defined as a

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

workaround in the <a

2.13.0)(bug 9550)</h3>

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

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

   * traceFileSizeKBytes -  Defines the size of the

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

exceeds the specified size.

   * numberOfTraceFiles - Specifies the number of the tracefiles

for rolling where the default is 3.

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

</h3>

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

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

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

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

significant performance improvements.

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

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

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

While testing OpenPegasus with OpenSLP 2.0 the OpenPegasus team found two

issues with this version of OpenSLP.  The patches documented below

allow this version of OpenSLP to work with OpenPegasus

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

a BUFFER_OVERFLOW exception occurs.  This is because UDP cannot

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

according to the specification, OpenSLP should automatically switch to

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

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

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

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

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

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

Effective with the release of OpenPegasus  2.13 the "interop"

namespace support for existing or

older repositories which used

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

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

the repository from "root/PG_InterOp" to

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

9414</a> (PEP304) for

details.

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

to be

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

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

"root/PG_InterOp"

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

"interop".

Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable to

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

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

involving editing one file and rebuilding OpenPegasus was defined as a

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

wiki faq</a>s.

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

However, since the definition of a standard name for this

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. Support for forward-compatibility is a fundamental design

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

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

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

Effective OpenPegasus 2.12.0 a new build variable has been

defined OpenPegasus interface, to continue to work with each version

defined  (PEGASUS_INTEROP_NAMESPACE) which allows an

upgrade of OpenPegasus.

OpenPegasus builder to define an alternate name for the Interop

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

Effective OpenPegasus 2.12.0 a new build variable was defined 

PEGASUS_INTEROP_NAMESPACE = interop).  Once this build

(PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus builder to define

variable is defined and OpenPegasus compiled, the actual name of

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

the interop namespace is what was defined in this variable and

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

all components of OpenPegasus use this as the interop namespace

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

name include the complete OpenPegasus test suite.  The only

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

name for the interop namespace will be the name defined through

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

this build variable.

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

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

However, today OpenPegasus is committed to the single namespace

approach for implementations starting a new repository.

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

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

In order to supexport PEGASUS_CLIENT_TRACE=keyword:keywordport users with

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

existing repositories, in 2.13.0,  migration of existing repositories

must maintain their repositories through updates of OpenPegasus.

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

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

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

running version of OpenPegasus must accept both the and new

for the interop namespace "root/PG_InterOp" to 

names and not confuse clients, listeners or providers that would

the prefered name "interop".

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

for this release. See bug <a

NOTE: If the interop namespace

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

name is redefined with PEGASUS_INTEROP_NAMESPACE clients using the

for more information about possible solutions and our progress

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

on a solution.

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

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

NOTE: If you redefine the interop namespace name with

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

PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp"

<h3>Configure Script to Control OpenPegasus Builds (OpenPegasus

namespace will not connect with the updated version of

2.13.0)(Bug 9592)</h3>

OpenPegasus.

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

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

<h3>Information on  IPv6 Support (PEP

standard build environment.  However, because OpenPegasus must build

291)</h3>

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

NOTE: This functionality was incorporated in OpenPegasus

configuration tool set, this is an OpenPegasus defined configure

2.7.0 but it was felt that the information below was worth

script.  The first very experimental version is part of OpenPegasu

repeating in subsequent Release Notes

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

IPv6 is

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

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

generation" protocol designed by the IETF to replace the

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

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

environment variable with options in the pegasus/configure script where

Support for OpenPegasus is documented in <a

those options are comatible with the Linux standard for defining configure

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

options and those options control the entire build process including placement

PEP 291</a>.

of output and choice of build options.

The IPv6 support in OpenPegasus is controlled by the

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

PEGASUS_ENABLE_IPV6 build variable. The default for this

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

OpenPegasus has

OpenPegasus will disable the IPv6 support.

long contained a hidden build controlled function to allow tracing at

the client through an environment variable

The following subsections provide some information on IPv6

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

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

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

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

slightly changed

support on a platform by OpenPegasus. If you build with

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

PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you

environment variable was:

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

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

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

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

both the CIM Server and Listener components. For more

<pre> export PEGASUS_CLIENT_TRACE=con</pre>

information on IPv6 support for your specific platform, refer to

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

the documentation for that platform.

2.7.0)</h3>

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but

All OpenPegasus externals that support either a hostname or an

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

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

Release Notes

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

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

IPv6 Support for OpenPegasus is documented in

must be specified without brackets. For example, the OpenPegasus

osinfo client (which returns information about the OS running on

PEP 291</a>.

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

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

The IPv6 support in OpenPegasus is controlled by the PEGASUS_ENABLE_IPV6

specified as:

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

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

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

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

The following subsections provide some information on IPv6 support for the

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

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

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

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

option including an optional port number, requires the IPv6

If you build with PEGASUS_ENABLE_IPV6=true, your platform must support

address to be delimited with brackets, for example:

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

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

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

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

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

module is not loaded automatically on startup.

possible that this module is not loaded automatically on

startup.

Note: you shouldn't use

Note: you

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

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

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

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

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

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

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

To check whether your current running kernel supports IPv6,

short automated test looks like:

take a look into your /proc filesystem. The entry

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

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

like:

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

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

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

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

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

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

Documentation Project's IPv6 HOWTO</a>.

ready"</big></div>

For more information on enabling IPv6 in the Linux kernel and

Warning: There is currently an

configuring network interfaces, refer to <a

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

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

RHEL5 and SLES10 systems. This problem is described in

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

<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

Warning: There is

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

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.

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.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6 implementations for Windows

Microsoft provides supported IPv6 implementations for Windows Server 2003,

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

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

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

(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>ipv6 install

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

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

ipv6 if</big></div>

Windows Vista and Windows Server 2008 support an integrated

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

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

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

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

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

tested on Windows Vista or Windows Server 2008.

Windows Server 2008.

For more information on installing, configuring, and using IPv6

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

on Windows platforms, refer to the document <a

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

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

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

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

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

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_">OpenPegasus Compatibility

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

Considerations</a></h2>

Support for forward-compatibility is a fundamental design principle for

Support for forward-compatibility is a fundamental design

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

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

OpenPegasus providers or clients, using only the externally defined

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

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

the externally defined OpenPegasus interface, to continue to

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

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

non-compliance with a standard that significantly affects

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

interoperability) that may require the community to make potentially

standard that significantly affects interoperability) that may

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

require the community to make potentially incompatible changes.

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

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

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

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

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

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

properties from instances has been relieved. The server

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

will do the filtering at the protocol adapter level. To

on performance the CIMInstance::filter() and

avoid a negative impact on performance the

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

CIMInstance::filter() and

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

CMPIInstanceFT.setPropertyFilter() functions have been

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

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

allow users to actually filter properties from an instance in a

provider relying in some unknown way on the instance being

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

filtered through these functions. To allow users to

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

actually filter properties from an instance, new function

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

CIMInstance::filterInstance() will actually filter

CIMServer will do the filtering but allows the provider to prefilter

properties from an instance exactly as the

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

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

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

</td>

</tr>

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

<td><a

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

9369</a>

</td>

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

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

fixed in OpenPegasus 2.13.0. Reregistering of an

requires that the  cimserver be restarted to send the

indication provider requires that the  cimserver be restarted

enableIndication request to the providers. This issue has

to send the enableIndication request to the providers. This issue

existed starting with OpenPegasus 2.10 to the current

has existed starting with OpenPegasus 2.10 to  version 2.12.

version. If the cimserver is not restarted the indication

If the cimserver is not restarted the indication will not be

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

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 1732

Line 1887

</tr>

<tr>

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

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

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

</tr>

<tr>

<td>DSP0226 - Web Services for Management

Line 1753

Line 1908

</tr>

</tbody>

</table>

<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIA 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

Today OpenPegasus includes support for several DMTF profiles including:

including the ones defined below:

<ol>

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

<li>DMTF ProfileRegistration Version 1.0.0</li>

<li>DMTF Indications DSP 1054, Version 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 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 number

utilize the DMTF CIM/WBEM specifications.  However, today

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

there are a number of known differences.  As of this

include the following:

release, some of the differences include the following:

<ol>

<li>Provider Registration

<li>Provider Registration - Pegasus supports registration

- Pegasus supports registration through a set of Pegasus Provider

through a set of Pegasus Provider registration classes rather

registration classes rather than support the DMTF defined Provider

than support the DMTF defined Provider Qualifier. Pegasus will

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

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

the readme for more information on provider registration.  This is

more information on provider registration.  This is not a

not really a deviation from the specifications since there is no

deviation from the specifications but is a different method of

specification or profile for provider registration today but is a

registration than many CIM Servers and means that the the

different method of registration than many CIM Servers and means that

provider qualifier is unused in Pegasus.</li>

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

<li>Lifecycle Indications -Today Pegasus supports

<li>Lifecycle Indications -Today Pegasus supports process

process indications and lifecycle indications when defined

iPegasusndications and lifecycle indications when defined specifically by

specifically by providers. Pegasus does not support lifecycle

providers. Pegasus does not support lifecycle indications if they are

indications if they are not defined by the provider or for

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

changes to CIM Classes. <span

For more

class="norm"> For more

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

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

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

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

<li> IncludeQualifiers

size="2">.</li>

option

<li>

on Instance Operations

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

- The DMTF specifications have deprecated the use of qualifiers on

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

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

Operations

stated specifically that the client should NOT depend on the

- The DMTF specifications have deprecated the use of

includeQualifiers parameter of the CIM/XML instance operations

qualifiers on instance operations with the 1.2 CIM

returning qualifiers.  Some CIM Client implementations expect

Operations Specification and stated specifically that the

instances returned from the CIM Server to include the qualifiers

client should NOT depend on the includeQualifiers

defined in the class definition (such as KEY qualifiers on

parameter of the CIM/XML instance operations returning

properties).   Pegasus today expects the provider to

qualifiers.  Some CIM Client implementations expect

complete the qualifiers on instances in accordance with the

instances returned from the CIM Server to include the

specification and generally the interpretation is that Pegasus

qualifiers defined in the class definition (such as KEY

applies class level qualifiers when the includeInstance parameter is

qualifiers on properties).   Pegasus

supplied on instance operations.  However, Pegasus today is

today expects the provider to complete the qualifiers on

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

instances in accordance with the specification and generally

depend on Pegasus accurately honoring the includeQualifier parameter

the interpretation is that Pegasus applies class level

for instance operations.  In the future it is expected that

qualifiers when the includeInstance parameter is supplied on

Pegasus will deprecate the use of qualifiers on instance operations

instance operations.  However, Pegasus today is

completely.  When Pegasus uses object normalization, the

inconsistent in the return of qualifiers so that the user

normalizer does apply qualifiers to returned instances if the

should NOT depend on Pegasus accurately honoring the

includeQualifiers operation parameter is set.</li>

includeQualifier parameter for instance operations.  In

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

the future it is expected that Pegasus will deprecate the

version of Specification for CIM Operations over HTTP, the definition

use of qualifiers on instance operations completely.

of the LocalOnly parameter for the GetInstance and Enumerate Instances

 When Pegasus uses object normalization, the normalizer

operations was modified. This change was incorrect, resulted in

does apply qualifiers to returned instances if the

reduced functionality and introduced a number of backward

includeQualifiers operation parameter is set.

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

</li>

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

<li>LocalOnly option on instance Operations - With the

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

1.1 version of Specification for CIM Operations over HTTP, the

properties returned. See Appendix C of this specification for more

definition of the LocalOnly parameter for the GetInstance and

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>MultiRequest CIM/XML Option

<li>

-  Pegasus does not support the DMTF defined MultiRequest

MultiRequest Operations - Pegasus

Operation option (See DSP0200).

does not support the DMTF defined MultiRequest Operation

option.

</li>

<li>MOF Namespace Pragma -The

<li>

Pegasus compiler does not support the namespace pragma defined in DSP

MOF Compiler namespace pragma -

0004. Namespaces for the OpenPegasus repository are defined through

The Pegasus compiler does not support the namespace pragma.

arguments for the MOF Compiler

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

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

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 -INFHowever, t (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 to

ports for the Pegasus code base including a maintainer for the

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

platform that will be willing to regularly document issues

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

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

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

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

operation of  Pegasus cannot be assured.  In all cases,

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

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

correct operation of  Pegasus cannot be assured.  In

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

all cases, including the active platforms, it is the

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

responsibility of the entity that packages and/or compiles

relevant defects that affect their platform.   The platforms

OpenPegasus for shipment or deployment, to read, and actively

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

monitor the Pegasus Bugzilla database for a list of relevant

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

defects that affect their platform.   The platforms

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

that are considered ported are shown in the two tables

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

below.  The first table represents platform for which

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

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

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

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)

Platform and

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

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

-moz-background-origin: initial;

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

height="26">

Platform

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

</td>

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

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

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>

Line 1928

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<o:p></o:p>

<span

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

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

</td>

</tr>

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

<span

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

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

</td>

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

<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<o:p></o:p>

<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;"> gcc (versions 3.xx, 4.7) clang(The clang compiler usage

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

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

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

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 X86_64<o:p></o:p>

Linux

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

</td>

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

<span

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

<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" cellspacing="1">

<tbody>

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

Platform and

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

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

-moz-background-origin: initial;

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

height="26">

Platform

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

</td>

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

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

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

Windows Vista, Windows 7, Windows Server 2008

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

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

</td>

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

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

the Windows. </td>

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

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 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>Solaris 9</big></td>

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

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

color="RED">Solaris

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

9</big></td>

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

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

</td>

</tr>

<tr>

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

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

<td><big>HP

for OpenVMS Alpha</big></td>

C++ V7.3-009

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

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

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

</td>

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

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

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

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

tested. </td>

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

<h3>Platform patches </h3>

Platform patches

<font

The following is a list known of

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

platform patches Pegasus requires.

platform patches Pegasus requires.

<ol>

<li> RHAS 2.1 needs the update to

<li>

fix Red Hat Bugzilla 98815.

<font

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

to fix Red Hat Bugzilla 98815.

</li>

<li> RHEL 4.4 multithreading bug in getpwuid-r could cause a CIM

<li>

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

RHEL 4.4

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

Further information regarding Pegasus support on IBM platforms can be

can be found at: <a

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

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 found

Further information regarding Pegasus support on HP platforms

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 defects found in Pegasus

Defects</a></h2>

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 OpenPegasus CVS tree are

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

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

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

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

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

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

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

documented through bugs.  Bugs reports are filed not only

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

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

process of committing new code representing the work on PEPs

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

done for OpenPegasus 2.6 and all subsequent versions. 

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

Therefore, a search of the OpenPegasus Bugzilla base for bugs

release.

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

     - Changes for this release (bugs Tagged

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

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

Pegasus 2.13.0_APPROVED bug list.</a>

2.6.1_APPROVED</a>, <a

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

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

Control

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

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

OpenPegasus release.

The OpenPegasus project is controlled largely through the CVS repository

- Changes between the 2.12.0 release

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

and 2.12.1 revision are defined in bugs tagged

mechanism for new and modified Pegasus functionality and for the

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

definition and documentation of releases.

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

The following documentation defines the characteristics of this Pegasus

release. The documents are available in the OpenPegasus CVS

bugs</a>

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 - (See Wiki Section <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_12_x">OpenPegasus

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

2.13.x

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 -  In previous versions of Pegasus this

information was  released as a Pegasus PEP. Starting with

Pegasus 2.9.0 the information is located in the OpenPegasus CVS

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

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 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 OpenPegasus Documentation</a></h2>

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

The following documentation is available for the this

The following documentation is available for the this Pegasus release:

Pegasus release:

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

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

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>

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

A combination of help generally available with the --help

Clients -API documentation and the documentation on the

option for each command and HTML documentation for most of the

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

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

</li>

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

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

usage documentation - </li>

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

See the header files and the HTML  API documentation

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

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

OpenPegasus web site.  While these are the original design

existing utilities and test programs and the examples in the API

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

documentation.  In particular the Common/tests unit tests

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

contain extensive examples of the use of the Common APIs.

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

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

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

Debugging Providers - </li>

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

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

development team and as a user information resource.  The wiki

documentation, and documentation from the Pegasus Technical

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>

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

</body>

</html>

Legend:

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

No CVS admin address has been configured