pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.18.2.1, 2011/09/05 14:23:46

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

Line 1

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

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

<head>

http-equiv="Content-Type">

<style>

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

</style>

Line 963

Line 964

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

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

</head>

<o:DocumentProperties>

<o:Author>IBM_User</o:Author>

<o:smarttagtype

<o:LastAuthor> </o:LastAuthor>

namespaceuri="urn:schemas-microsoft-com:office:smarttags"

<o:Revision>4</o:Revision>

name="City"></o:smarttagtype> <o:smarttagtype

<o:TotalTime>211</o:TotalTime>

namespaceuri="urn:schemas-microsoft-com:office:smarttags"

<o:Created>2004-04-05T14:13:00Z</o:Created>

name="place"></o:smarttagtype><o:smarttagtype

<o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved>

namespaceuri="urn:schemas-microsoft-com:office:smarttags"

<o:Pages>1</o:Pages>

name="date"></o:smarttagtype><!--[if gte mso 9]><xml>

<o:Words>5026</o:Words>

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

<o:Characters>28651</o:Characters>

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

<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]--></head><body lang="EN-US" link="blue" vlink="blue">

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

style="color: black;">

Pegasus

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

Enhancement 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 #: 359

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

<span

style="color: black;">

PEP #: 364

Title: Release

Notes for OpenPegasus version 2.11.0 and version 2.11.1

Notes for OpenPegasus version 2.12.1

Created: 10

September 2012

Created: 23

March 2011

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>

23 March 2011

<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

<span style="font-family: Arial;

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

color: black;">Initial Submission <span

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

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

</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center" height="21">30 August 2011 </td>

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

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

September 2012

<td style="padding: 0.75pt;" height="21">Updated to reflect Pegasus 2.11.1 release. Added covered properties to list of exceptions to DMTF specs.

</td>

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

Schopmeyer

</td>

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

and complete links to PEPs

</td>

</tr>

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

September 2012

</td>

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

Schopmeyer

</td>

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

all comments from first review

</td>

</tr>

<tr>

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

September 2012

</td>

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

Schopmeyer

</td>

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

Abstract: This document defines the release notes for the

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

2.11.0 release of the OpenPegasus CIM Server with notes to reflect the 2.11.1 revision. The purpose of this PEP

width="100%"></div>

Abstract: This document defines the release notes for

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

NOTE: This PEP is maintained both as a PEP on the Pegasus website

and is also available directly in the OpenPegasus source tree root

library as ReleaseNotes.htm

<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 of This Release</a></li>

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

Considerations</a></li>

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

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

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

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 Bug Fixes and Changes for this Release

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

</a></li>

<li> <a

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

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

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

Release

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

Documentation</a></li>

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

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

</ol>

<h2>Availability

<h2>Availability of this Release</h2>

of this Release</h2>

NOTE: This document

NOTE: This document defines

defines the OpenPegasus 2.12.0 minor version release with

the OpenPegasus 2.11.0 version release with comments added to define

comments added to define the 2.12.1 revision to that minor

the 2.11.1 revision to that release.  OpenPegasus 2.11.1 is a bug

release.  OpenPegasus 2.12.1 is a bug fix revision to

fix revision to Pegasus 2.11.0. The complete list of changes (total of

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

32 bugs fixed)  is defined in OpenPegasus bugzilla with the <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.11.1_APPROVED">2.11.1_APPROVED bugs</a>

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

query.  We recommend that all uses of 2.11.0 review this list.

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

OpenPegasus tries to execute only bug fixes for revision releases and

not include enhancements but in exceptional cases including 2.11.1 some

extensions are included (See the Functionality of this Release

section). The OpenPegasus team recommends that users of Pegasus 2.11.0

update to Pegasus 2.11.1 because of of issues defined in a couple of

the bugs below, in particular an api incompatibility defined in bug

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

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

formats. These can be downloaded from the <span

downloaded from the OpenPegasus Web

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

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

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

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

<li>OpenPegasus source RPMs on the OpenPegasus web

A source RPM is  available on the

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

OpenPegasus web site that can be used to build binaries for most

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

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

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

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

<li>The OpenPegasus CVS repository. The CVS tags

release and

representing this release and subsequent snapshots that are

subsequent snapshots that are made available in the Pegasus CVS are

made available in the Pegasus CVS are defined on the

defined on the OpenPegasus CVS repository web page (see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

OpenPegasus CVS repository web page (see the <a

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

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

snapshots page</a>.</li>

CVS

page</a> for information) using the tags defined on the <a

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

snapshots

page</a>.</li>

</ul>

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

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

WEB site</a>.

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

Installation instructions are part of the README in the root of the

WEB

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

<h2>OpenPegasus Functionality in 2.12

Release</h2>Pegasus overall status by release is defined by  a

Release</h2>

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

OpenPegasus overall status by release is defined by  a <a

WEB Page</a>

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

that is available on the OpenPegasus web site .  That web page

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

shows the

site .  That web page shows the Pegasus users and developers

Pegasus users and developers the status of the various features found

the status of the various features found in OpenPegasus using a

in Pegasus

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

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

description of each feature.

description of

OpenPegasus 2.12.1 is a Revision release.

each feature.

Pegasus 2.11.0

NOTE: OpenPegasus releases are categorized as follows:

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

<ul>

areas as described in the Pegasus  PEP defining this release

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

.

Major release includes major functionality change and 

The major areas of development for this release  were as

incompatible behavior changes and/or incompatible public API

follows. Note that the bugs listed represent only those features

changes,

incorporated in bugs without PEPS that are considered enhancements, not

</li>

all bugs incorporated in the release. For

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

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

Release and includes new functionality but maintains behavior

Table of Major

and public API compatibility,

Changes for this Release

</li>

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

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

</ul>

The major areas of development including both enhancements and bug

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

bugs listed represent only those features incorporated in bugs

without PEPS that are considered enhancements, not all bugs

incorporated in the release. For more information access the

PEP/BUG for each change defined below:

<font

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

of Major Changes for this Release

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

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

width="82%">

<tbody>

Line 1181

Line 1268

Version</th>

</tr>

<tr>

<td>Run 32 bit providers in 64 bit OpenPegasus</td>

<td>Provider Lifecycle Indications

</td>

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

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

1.2</a>

</td>

</tr>

<td align="left" width="75%">Provider Module Grouping</td>

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

instances

</td>

<td width="128"><a

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

1.1</a>

</td>

</tr>

<tr>

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

<td align="left" width="75%">SNMP V3 Trap Generation in Pegasus

</td>

Indication Handler</td>

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

interop namespace

</td>

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

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

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

1.5</a>

</td>

</tr>

<tr>

<td align="left">PEP 358

</td>

<td>WSMan indication handling and subscription support

</td>

<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>Enhance cimsub to add operations to create filters,

destinations and subscriptions

</td>

<td>

</td>

</tr>

<td style="text-align: center;" width="7%">PEP 324

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

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

5667</a>

</td>

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

buildInstance and filter functions in CIMInstance class

</td>

<td align="left" width="75%">DMTF Indications Profile (DSP 1054)

Implementation, stage 2

</td>

</tr>

<tr>

<td><a

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

8952</a></td>

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

<td>

</td>

</tr>

<tr>

<td><a

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

8984</a></td>

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

<td>

</td>

</tr>

<tr>

<td><a

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

9008</a></td>

<td>Add new Indication runtime configuration variables:

maxIndicaitonDeliveryRetry Attempts  and

minIndicationdeliveryRetryInterval</td>

<td>

</td>

</tr>

<td style="text-align: center;" width="7%">PEP 349

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

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

9013</a>

</td>

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

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>

<td align="left" width="75%">Improve the

availability of the CIMOM by better isolation from faulty providers</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>Add External SLP support to release builds

</tr>

<tr>

<td><a

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

9112</a>

</td>

<td>Advertise IndicationService conformance to Indications

</a>

Profile by imlementing CIM_ElementConformsToProfile when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td>

<td>

</td>

</tr>

<tr>

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

<td><a

</a></td>

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

<td> <a name="comtag_90"></a>enable

PEGASUS_USE_RELEASE_CONFIG_OPTIONS build option to have true/false

values

9114</a>

</td>

<td>Advertise DMTF Indications Profile (DSP1054) 1.1.0

conformance </td>

<td>

</td>

</tr>

<tr>

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

<td><a

8806</a></td>

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

<td>Diagnose data for BAD UTF8 exception</td>

</tr>

<tr>

9118</a>

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

</td>

8825</a></td>

<td>Add support for CIM_IndicationFilter.SourceNamespaces[]

<td>Option to specify multiple provider dirs for release builds</td>

property

</td>

</tr>

<td>

<tr>

</td>

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

8839</a></td>

<td>OOP Provider recovery enhancement</td>

</tr>

<tr>

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

8845</a></td>

<td><big><big>Enhance SSL Certificate info to

expose the whole certificate</big></big>

</td>

</tr>

<tr>

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

<td><a

</a> </td>

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

<td align="left" width="75%">Enhance WSMan Server Adpater

to include enumeration association filters</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 align="left" width="75%"> New runtime configuration options for Indication Service (2.11.1 Release)

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

9155</a>

</td>

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

default schema

</td>

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

</tr>

</tbody>

</table>

</td>

<td>

</td>

</tr>

</a></td>

<tr>

</tr><tr>

<td><a

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

9172</a>

</td>

<td style="vertical-align: top;">Correct issue with Provider

<td>Add capability for administrator to override hostname

backward compatibility due to a new virtual function that was

used by providers. This adds  new runtime

introduced in Pegasus 2.11.0 (2.11.1 release)

configuration variable hostname and

fullyQualifiedHostName. It is necessary to upgrade

existing repositories using repupgrade utility when

upgrading from OpenPegasus less than 2.12.0 and reusing an

existing repository.

</td>

<td>

</td>

</tr>

<tr>

<td><a

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

9215</a>

</td>

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

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>Add operations for display class tree and counting

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>Enhance cimsub for batches of subscription oriented

operations

</td>

<td>

</td>

</tr>

<tr>

<td><a

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

9229</a>

</td>

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

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

<td>

</td>

</tr>

<tr>

<td><a

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

9236</a></td>

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

version supports only X86 and X86_64 and requires clang

version 3 or greater.

</td>

<td>

</td>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality change

The status of several components of Pegasus functionality

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 changed status can be identified by a change in color from the

this release</a> on the <a

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

release to this release</a> on the

Status WEB Page</a>.

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

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

WEB Page</a>.

OpenPegasus 2.12

Finally, a significant number of internal changes and corrections

</h3>

were made

Prior to version 2.12 OpenPegasus used an OpenPegasus internal

under the control of the Pegasus bugzilla bug system. See the bug

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

section below

OpenPegasus namespace with no defined way to change this

for more information.

variable.  Note that an unsupported method involving

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

editing one file and rebuilding OpenPegasus was defined as a

workaround in the <a

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

wiki faq</a>s.

However, since the definition of a standard name for this

namespace in DMTF and SNIA specifications ("interop" or

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

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

Effective OpenPegasus 2.12.0 a new build variable has been

defined  (PEGASUS_INTEROP_NAMESPACE) which allows an

OpenPegasus builder to define an alternate name for the Interop

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

PEGASUS_INTEROP_NAMESPACE = interop).  Once this build

variable is defined and OpenPegasus compiled, the actual name of

the interop namespace is what was defined in this variable and

all components of OpenPegasus use this as the interop namespace

name include the complete OpenPegasus test suite.  The only

name for the interop namespace will be the name defined through

this build variable.

However, today OpenPegasus is committed to the single namespace

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

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

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

must maintain their repositories through updates of OpenPegasus.

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

running version of OpenPegasus must accept both the and new

names and not confuse clients, listeners or providers that would

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

for this release. See bug <a

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

for more information about possible solutions and our progress

on a solution.

NOTE: If you redefine the interop namespace name with

PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp"

namespace will not connect with the updated version of

OpenPegasus.

<h3>Information on  IPv6 Support (PEP

291)</h3>

NOTE: This functionality was incorporated in OpenPegasus

2.7.0 but it

2.7.0 but it was felt that the information below was worth

was felt that the information below was worth repeating in subsequent

repeating in subsequent Release Notes

Release

Notes

IPv6 is

short for "Internet

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

Protocol

generation" protocol designed by the IETF to replace the

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

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

to replace the current version Internet Protocol, IP Version 4

Support for OpenPegasus is documented in <a

("IPv4"). IPv6 Support for OpenPegasus is documented in <a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">

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

PEP

PEP 291</a>.

291</a>.

The IPv6 support in OpenPegasus is controlled by the

The IPv6 support in OpenPegasus is

PEGASUS_ENABLE_IPV6 build variable. The default for this

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for

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

this

OpenPegasus will disable the IPv6 support.

variable is "true"; setting this to

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

The following subsections provide

The following subsections provide some information on IPv6

some information on IPv6 support for the Linux and Windows platforms.

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

Note that in the 2.6.1 release there is no automatic run-time detection

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

of IPv6 support on a platform by OpenPegasus. If you build with

support on a platform by OpenPegasus. If you build with

PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you will

PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you

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

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

or possibly some other failure. This applies to both the CIM Server and

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

Listener components. For more information on IPv6 support for your

both the CIM Server and Listener components. For more

specific platform, refer to the documentation for that platform.

information on IPv6 support for your specific platform, refer to

the documentation for that platform.

All OpenPegasus externals that

All OpenPegasus externals that support either a hostname or an

support either a hostname or an IP address as input have been updated

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

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

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

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

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

address must be specified without brackets. For example, the

must be specified without brackets. For example, the OpenPegasus

OpenPegasus osinfo client (which returns information about the OS

osinfo client (which returns information about the OS running on

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

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

<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

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

takes

option including an optional port number, requires the IPv6

an optional "location" option including an optional port number,

address to be delimited with brackets, for example:

requires the IPv6 address to be delimited with brackets, for example:

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

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

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

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

or

<div style="margin-left: 40px;"><big>cimcli ns -l [3ffe:1:2:1]:5989</big>

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

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

</div>

For more information on

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

specifying

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

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

Version 6 Addressing Architecture</a> and <a

RFC 2373 - IP Version

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

6 Addressing Architecture</a>

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

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

Format for

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

<h4>IPv6 on Linux</h4>

Modern Linux distributions already

Modern Linux distributions already contain IPv6-ready kernels,

contain IPv6-ready kernels, the

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

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

possible that this module is not loaded automatically on

that this module is not loaded automatically on startup.

startup.

Note:

Note: you

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

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

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

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

longer improved according to definitions in latest RFCs. It's recommend

is no longer improved according to definitions in latest RFCs.

to use series 2.6.x now.

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

To check whether your current

To check whether your current running kernel supports IPv6,

running

take a look into your /proc filesystem. The entry

kernel supports IPv6, take a look into your /proc filesystem. The entry

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

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

like:

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

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

/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"</big></div>

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

For more information on

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

enabling

ready"</big></div>

IPv6 in the Linux kernel and configuring network interfaces, refer to

For more information on enabling IPv6 in the Linux kernel and

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

configuring network interfaces, refer to <a

Documentation Project's IPv6 HOWTO</a>.

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

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

Warning:

Warning: There is

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

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

is seen intermittently on RHEL5 and SLES10 systems. This problem is

seen intermittently on RHEL5 and SLES10 systems. This problem is

described in

described in <a

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

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

bug 6586</a>

bug

and

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

bug 248052</a>,

and manifests itself as an intermittent IPv6 socket failure. You

6586</a> and

should be aware

that OpenPegasus with IPv6 enabled may be significantly impacted in

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

these

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

Microsoft provides supported IPv6 implementations for Windows

implementations for Windows Server

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

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

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

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

On Windows XP, you can use the ipv6.exe

tool to install, uninstall, and

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

query

example:

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

Windows Vista and Windows Server 2008 support an integrated

and Windows Server 2008 support an integrated

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

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

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

Note that the OpenPegasus IPv6 support has not yet been tested

tested on Windows Vista or Windows Server 2008.

on Windows Vista or Windows Server 2008.

For more information on

For more information on installing, configuring, and using IPv6

installing, configuring, and using IPv6 on Windows platforms, refer to

on Windows platforms, refer to the document <a

the document

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

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

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

for Microsoft Windows: Frequently Asked Questions</a>.

Questions</a>.

<h4>Testing your OpenPegasus IPv6

<h4>Testing  OpenPegasus IPv6 support</h4>

support</h4>

As part of the OpenPegasus automated tests, the TestClient,

As part of the OpenPegasus

g11ntest, and IndicationStressTest test clients were modified to

automated tests, the TestClient, g11ntest, and IndicationStressTest

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

test clients were modified to run tests using the IPv6 loopback address

PEGASUS_ENABLE_IPV6=true.

(::1) if PEGASUS_ENABLE_IPV6=true.

You can also perform manual

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

tests

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

using the IPv6 loopback or a real IPv6-configured network interface.

IPv6 loopback on a system with OpenPegasus running on the WBEM

For example, using the IPv6 loopback on a system with OpenPegasus

standard http port of 5988:

running on the WBEM standard http port of 5988:

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

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

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

Support for forward-compatibility is a fundamental design principle

Considerations</a></h2>

for the

Support for forward-compatibility is a fundamental design

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

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

OpenPegasus

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

Providers or Clients, using only the externally defined OpenPegasus

the externally defined OpenPegasus interface, to continue to

interface,

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

to continue to work with a minor version upgrade of OpenPegasus.

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

However, there

standard that significantly affects interoperability) that may

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

require the community to make potentially incompatible changes.

that

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

significantly affects interoperability) that may require the Community

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

to make

upgrading to this OpenPegasus release.

potentially incompatible changes. The following table contains a list

of defect

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

fixes that MAY impact, even well-behaved, OpenPegasus Providers or

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

Clients when

width="80%">

upgrading to this OpenPegasus release.

<tbody>

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

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

</tr>

<td><a

<td align="left">The requirement for providers (CMPI and C++) to

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

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

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

on performance the CIMInstance::filter() and

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

8830</a></td>

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

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

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

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

allow users to actually filter properties from an instance, new

properties from instances has been relieved. The server

function CIMInstance::filterInstance() will actually filter properties

will do the filtering at the protocol adapter level. To

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

avoid a negative impact on performance the

versions of Pegasus.</td>

CIMInstance::filter() and

</tr>

CMPIInstanceFT.setPropertyFilter() functions have been

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

<td>

provider relying in some unknown way on the instance being

</td>

filtered through these functions. To allow users to

<td>

actually filter properties from an instance, new function

</td>

CIMInstance::filterInstance() will actually filter

</tr>

properties from an instance exactly as the

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

<td>

</td>

<td>

</td>

</tr>

<td>

</td>

<td>

</td>

</tr>

<td>

<td><a

</td>

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

<td>

9369</a>

</td>

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

requires that the  cimserver be restarted to send the

enableIndication request to the providers. This issue has

existed starting with OpenPegasus 2.10 to the current

version. If the cimserver is not restarted the indication

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

</tr>

</tbody>

</table>

<h2>OpenPegasus Relationship to

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

CIM/WBEM Standards</h2>

Pegasus was designed and implemented to comply with the DMTF

CIM/WBEM specifications The following table defines the level of the

CIM/WBEM specifications The following table defines the level of

DMTF specifications to which this version of Pegasus aims to conform

the DMTF specifications to which this version of Pegasus aims to

today.

conform today.

<tbody>

<tr>

Line 1546

Line 1887

</tr>

<tr>

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

<td width="33%">2.22.1 Final,  22 Oct 2009( default) </td>

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

</tr>

<tr>

<td>DSP0226 - Web Services for Management

</td>

<td>Version 1.1.1

</td>

</tr>

<tr>

<td>DSP0227 - WS-Management CIM Binding Specification

</td>

<td>Version 1.2.0

</td>

</tr>

<tr>

<td>DSP0230 - WS-CIM Mapping Specification </td>

<td>Version 1.1.0

</td>

</tr>

</tbody>

</table>

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

SMI Profiles Supported</h2>

Today OpenPegasus includes support for several DMTF profiles

including the ones defined below:

<ol>

<li>DMTF ProfileRegistration Version 1.0.0</li>

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

as the SNIA SMI Indication profile it also supports this

profile. This profile is enabled by compiling OpenPegasus with

the build variable PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

</li>

<li>SNIA Profile Registration 1.0.0</li>

<li>SNIA Server 1.1.0 & 1.2.0

</li>

</ol>

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

Exceptions to

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

DMTF Specifications</a></h2>

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

It is a major goal

utilize the DMTF CIM/WBEM specifications.  However, today

of the OpenPegasus project to both drive and utilize the DMTF CIM/WBEM

there are a number of known differences.  As of this

specifications.  However, today there are a number of known

release, some of the differences include the following:

differences. 

As of this release, some of the differences include the following:

<ol>

<li>Provider Registration - Pegasus supports registration

through a set of Pegasus Provider registration classes rather than

through a set of Pegasus Provider registration classes rather

support the DMTF defined Provider Qualifier. Pegasus will not support

than support the DMTF defined Provider Qualifier. Pegasus will

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

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

provider registration.  This is not a deviation from the

more information on provider registration.  This is not a

specifications but is a different method of registration than many CIM

deviation from the specifications but is a different method of

Servers and means that the the provider qualifier is unused in Pegasus.</li>

registration than many CIM Servers and means that the the

<li>Indications -Today Pegasus supports process

provider qualifier is unused in Pegasus.</li>

indications and lifecycle indications when defined specifically by

<li>Lifecycle Indications -Today Pegasus supports

providers. Pegasus does not support lifecycle indications if they are

process indications and lifecycle indications when defined

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

specifically by providers. Pegasus does not support lifecycle

more information see the Pegasus CVS file:<a name="comtag_137">  pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

indications if they are not defined by the provider or for

changes to CIM Classes. <span

class="norm"> For more

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

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

size="2">.</li>

<li>

IncludeQualifiers

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

option on Instance Operations

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

Operations

The DMTF specifications have deprecated the use of qualifiers on

- The DMTF specifications have deprecated the use of

instance operations with the 1.2 CIM Operations Specification and

qualifiers on instance operations with the 1.2 CIM

stated specifically that the client should NOT depend on the

Operations Specification and stated specifically that the

includeQualifiers parameter of the CIM/XML instance operations

client should NOT depend on the includeQualifiers

returning qualifiers. 

parameter of the CIM/XML instance operations returning

Some CIM Client implementations expect instances

qualifiers.  Some CIM Client implementations expect

returned

instances returned from the CIM Server to include the

from the CIM Server to include the qualifiers defined in the class

qualifiers defined in the class definition (such as KEY

definition (such as KEY qualifiers on properties).   Pegasus

qualifiers on properties).   Pegasus

today expects the provider to complete the qualifiers on instances in

today expects the provider to complete the qualifiers on

accordance with the specification and generally the interpretation is

instances in accordance with the specification and generally

that Pegasus applies class level qualifiers when the includeInstance

the interpretation is that Pegasus applies class level

parameter is supplied on instance operations.  However, Pegasus

qualifiers when the includeInstance parameter is supplied on

today is inconsistent in the return of qualifiers so that the user

instance operations.  However, Pegasus today is

should NOT depend on Pegasus accurately honoring the includeQualifier

inconsistent in the return of qualifiers so that the user

parameter for instance operations.  In the future it is expected

should NOT depend on Pegasus accurately honoring the

that Pegasus will deprecate the use of qualifiers on instance

includeQualifier parameter for instance operations.  In

operations completely.  When Pegasus uses object normalization,

the future it is expected that Pegasus will deprecate the

the normalizer does apply qualifiers to returned instances if the

use of qualifiers on instance operations completely.

 When Pegasus uses object normalization, the normalizer

does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.

</li>

<li>LocalOnly option on instance

<li>LocalOnly option on instance Operations - With the

Operations - With the 1.1 version of Specification for CIM

1.1 version of Specification for CIM Operations over HTTP, the

Operations over HTTP, the definition of the LocalOnly parameter for the

definition of the LocalOnly parameter for the GetInstance and

GetInstance and Enumerate Instances operations was modified. This

Enumerate Instances operations was modified. This change was

change

incorrect, resulted in reduced functionality and introduced a

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

introduced by this change, we strongly recommend that CIM

LocalOnly = false and do not rely on the use of this parameter to

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

filter the set of set of properties returned. See Appendix C of this

this parameter to filter the set of set of properties

specification for more information.</li>

returned. See Appendix C of this specification for more

information.</li>

<li>

MultiRequest Operations - Pegasus

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

does not support the DMTF defined MultiRequest Operation

option.

</li>

<li>

MOF Compiler namespace pragma - The

MOF Compiler namespace pragma -

Pegasus compiler does not support the namespace pragma.

The Pegasus compiler does not support the namespace pragma.

</li>

<li>CIMOperation Trailer - Pegasus implements

<li>CIMOperation Trailer - Pegasus implements chunking

chunking

based on the DSP0200 1.2.0 preliminary spec. including the

based on the DSP0200 1.2.0 preliminary spec. including the operation

operation trailer defined in that specification Refer to bug <a

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

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

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

for more details. This trailer was completely removed from the

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

DSP0200 1.2 final specification as a non-compatible change so

is used Pegasus is returning a noncompliant response to enumerate type

that if chunking is used Pegasus is returning a noncompliant

requests. </li>

response to enumerate type requests. </li>

<li>Whitespace in XML value Element

<li>Whitespace in XML value

- Pegasus trims the leading and trailing whitespace from XML value

Element - Pegasus trims the leading and trailing

elements that are of the Type String.  This behavior is documented

whitespace from XML value elements that are of the Type

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

String.  This behavior is documented in Pegasus bug <a

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

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

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

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

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

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

documented bugs in Pegasus such as this that the OpenPegasus team feels

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

cannot be modified until a major version update.  These bugs are

are some documented bugs in Pegasus such as this that the

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

OpenPegasus team feels cannot be incorporated into the code

until a major version update.  These bugs are documented

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

<li>modifyInstance operation

behavior in the Pegasus repository does not match the DMTF specification.

behavior in the Pegasus repository does not match the DMTF

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

specification. Under some conditions (ex. if no

all properties rather than just the properties supplied with the

propertyList is supplied) it modifies all properties rather

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

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>Covered Properties (multiple properties with the same name but different class origin)

<li>OpenPegasus Interop Namespace - The default interop

- The DMTF Spec DSP0004 now defines the requirement for covered

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

properties. However, OpenPegasus does not support this capability (see <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">bug 3571</a>)

versions of OpenPegasus prior to 2.12.0 this could be changed

during build by modifying a string definition in the code.

Effective version 2.12 this  has become a build option

with the build configuration environment variable

PEGASUS_INTEROP_NAMESPACE = <name for this namespace>

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, or -INF (bug  <a

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

- If requests or responses include properties or parameters

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

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

input is not accepted because these special strings are not

understood by the decoder on Windows.</li>

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

Real32 and Real64 property and Parameter types for the

CIM/XML protocol - (bug <a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9392">9392</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) are not allowed in OpenPegasus. While the

requirement for this functionality was added to DSP0004

subsequent to version 2.4, the general agreement is that the

requirement itself is not supportable and particularly not

with the existing OpenPegasus APIs.  Further, the

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

Each OpenPegasus release lists as 'active'

those

platforms those hardware/software platforms that have recognized

hardware/software platforms that have recognized ports for the Pegasus

ports for the Pegasus code base including a maintainer for the

code base

platform that will be willing to regularly document issues

including a maintainer for the platform that will be willing to

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

regularly

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

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

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

changed. 

correct operation of  Pegasus cannot be assured.  In

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

all cases, including the active platforms, it is the

a group

responsibility of the entity that packages and/or compiles

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

OpenPegasus for shipment or deployment, to read, and actively

Pegasus

monitor the Pegasus Bugzilla database for a list of relevant

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

defects that affect their platform.   The platforms

it is the

that are considered ported are shown in the two tables

responsibility of the entity that packages and/or compiles OpenPegasus

below.  The first table represents platform for which

for

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

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

Nightly Build Test WEB Page. Those platforms which have been

bugzilla

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

database for a list of relevant defects that affect their

platform.  

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

below. 

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

regular

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

platforms

which have been 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 1695

Line 2118

PA_RISC and Itanium</o:p>

</td>

HP aC++ B3910B<o:p></o:p>

HP <span

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

</td>

</tr>

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

<span

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

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

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

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

(versions 3.xx, 4.xx)<o:p></o:p></td>

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

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

<span

(versions 3.xx, 4.xx)

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

and up</td>

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

Platforms not Actively supported for this

(No

release (No current Nightly Build Test Results

current Nightly Build Test Results

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

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

<tbody>

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

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

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

Windows Vista, Windows 7, Windows Server 2008

</td>

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

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

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

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

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

6 no longer being regular tested.Note that today there

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

</tr>

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

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

and higher</td>

10.3 and higher</td>

</tr>

<tr>

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

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

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

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

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

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

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

2.95.3,  Sun CC compiler V 5.8. Note that the

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

color="RED">Solaris

9</big></td>

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

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

</td>

</tr>

<tr>

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

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

<td><big>HP

OpenVMS

C++ V7.3-009

Alpha</big></td>

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

</tr>

<tr>

<td><big> HP OpenVMS 8.3 or

<td><big> HP OpenVMS 8.3

later IA64</big></td>

or later IA64</big></td>

<td><big>HP C++ V7.3-023 or later required on OpenVMS IA64</big></td>

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

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

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

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

C++ Ver.  6 and Microsoft .Net compiler version. Works on VC

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

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

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

tested.</td>

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

</tr>

<tr>

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

</td>

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

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

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

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

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

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

tested. </td>

</tr>

<tr>

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

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

IX86)</big></td>

and IX86)</big></td>

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

</tr>

</tbody>

</table>

Platform patches

Platform patches

<font

The following is a list known of platform

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

patches Pegasus requires.

platform patches Pegasus requires.

<ol>

<li>

RHAS

<font

2.1 needs the update to fix Red Hat Bugzilla 98815.

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

to fix Red Hat Bugzilla 98815.

</li>

<li>

RHEL 4.4

multithreading bug in

multithreading bug in getpwuid-r could cause a CIM Server

getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is

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

fixed in

RHEL 4.5

</li>

<li>

Red Hat and SUSE

Red Hat and

Linux multiple versions -

SUSE Linux multiple versions - multithreaded client

multithreaded client intermittently fails connecting to IPv6 (Pegasus

intermittently fails connecting to IPv6 (Pegasus Bugzilla

Bugzilla

6586) (Red Hat bug 248052)

</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can

Further information regarding Pegasus support on IBM platforms

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

Further information regarding Pegasus support on HP platforms

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

found at:

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

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

Defects</a></h2>

<h2><a name="PEGASUS Bugs">Pegasus Defects Fixed and Changes for this Release

The OpenPegasus Bugzilla database documents any defects found

</a></h2>

in Pegasus and  is available through the following

The Pegasus bugzilla database documents any defects found in Pegasus

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

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

database</a>.

Effective with the start of the Pegasus 2.6 work, all changes to the

CVS tree are documented through bugs.  Bugs reports are filed not

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

only for bugs and

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

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

documented through bugs.  Bugs reports are filed not only

new code

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

representing the work on PEPs done for Pegasus 2.6 and all subsequent

process of committing new code representing the work on PEPs

versions.  Therefore, a search of

done for OpenPegasus 2.6 and all subsequent versions. 

the Open Pegasus bugzilla base for bugs with the tag for a particular

Therefore, a search of the OpenPegasus Bugzilla base for bugs

version

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

(ex. 

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

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

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

2.6.1_APPROVED</a>,

2.6.1_APPROVED</a>, <a

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

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

etc) will yield all changes to

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

the Pegasus CVS tree for that Pegasus release.

OpenPegasus release.

- Changes between the 2.12.0 release

     - Changes for this release (bugs Tagged

and 2.12.1 revision are defined in bugs tagged

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

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

Pegasus 2.11.0_APPROVED bug list.</a>

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

     - (2.11. 1) Changes between the 2.11.0 release

and 2.11.1 revision are defined in bugs tagged (2.11.1.APPROVED). The

complete list of 32 bugs is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.11.1_APPROVED">2.11.1_APPROVED bugs</a>.

bugs</a>

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

- Changes that were made in the minor

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

release 2.12 are in bugs Tagged 2.12.0_APPROVED. The link

The Pegasus project is controlled largely through the CVS repository

is <a

and a set of documents

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

(PEPs) that serve both as the definition and review mechanism for new

Pegasus 2.12.0_APPROVED bug list.</a>

and

modified Pegasus functionality and for the definition and documentation

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

of releases.

Documentation">Release Control and Version Definition

The following documentation defines the characteristics of this Pegasus

Documentation</a></h2>

release. The documents are available in the OpenPegasus CVS

The OpenPegasus project is controlled largely through the CVS

repository.

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

definition and review mechanism for new and modified Pegasus

functionality and for the definition and documentation of

releases.

The following documentation defines the characteristics of this

Pegasus release. The documents are available in the

OpenPegasus CVS repository.

<ul>

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

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

Section <a

2.11.x Release Status</a>) - A

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

section in the Pegasus wiki is used

2.12.x

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>

Release Status</a>) - A

section in the Pegasus wiki is used throughout the

development of this version as the control point for

functionality that will go into the release and points to

all of the PEPs that represent the Pegasus 

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

OpenPegasus

Build and Configuration

Options  for Selected

Platforms -  In previous

versions of Pegasus this information was  released as a Pegasus

Build and Configuration Options  for Selected Platforms

PEP. Starting with Pegasus 2.9.0 the information is located in the

-  In previous

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

versions of Pegasus this information was  released as a

<li> OpenPegasus External Interfaces -The list of the OpenPegasus interfaces

Pegasus PEP. Starting with Pegasus 2.9.0 the information is

that are considered external and therefore "frozen". Unless an

located in the OpenPegasus CVS repository as <big

exception is explicitly approved by the Steering Committee all

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

subsequent releases of Pegasus MUST continue to support these

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

interfaces. Interfaces not explicitly listed in this document, should

<li> OpenPegasus External Interfaces -<span

be considered as internal and subject to change.In previous Pegasus

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

releases this information was available as a separate PEP. Starting

interfaces that are considered external and therefore

with Pegasus 2.9.0 this information is integrated into the Pegasus

"frozen". Unless an exception is explicitly approved by

repositoryas  pegasus/doc/EnternalInterface.html.</li>

the Steering Committee all subsequent releases of Pegasus

<li> OpenPegasus  SDK Packaging Definition - Defines the recommended set of files for

MUST continue to support these interfaces. Interfaces not

inclusion in the OpenPegasus

explicitly listed in this document, should be considered

SDK. Starting with Pegasus release 2.11.0, this document is available

as internal and subject to change.In previous Pegasus

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

releases this information was available as a separate PEP.

Starting with Pegasus 2.9.0 this information is integrated

previous Pegasus releases this document was made available as s

into the Pegasus repositoryas  <small

separate Pegasus PEP document rather than in the CVS repository.

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

</li>

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

<li> Pegasus  Runtime Packaging Definition

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

- Defines the recommended set

of files for inclusion in this OpenPegasus

<li> OpenPegasus  SDK Packaging Definition - <span

release. Starting with Pegasus release 2.11.0, this idocument contained

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

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

of files for inclusion in the OpenPegasus SDK. Starting

In previous

with Pegasus release 2.11.0, this document is available in

releases this was made available as a seperate Pegasus PEP document

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

rather than in the CVS repository.  </li>

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

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

In previous Pegasus releases this document was made

approved PEP repository and the OpenPegasus source tree root directory (<big style="font-weight: bold;">pegasus/ReleaseNotes.htm</big>)</li>

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>

</ul>

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

The following documentation is available for the this Pegasus

The following documentation is available for the this

release:

Pegasus release:

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

A

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

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

</li>

command and HTML documentation for most of the tools.<o:p></o:p> <li class="MsoNormal" style="color: black;">API and  usage

A combination of help generally available with the --help

documentation - </li>

option for each command and HTML documentation for most of the

See the header files and the HTML  API

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

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

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

is the existing utilities and test programs and the examples in the API

usage documentation - </li>

documentation.  In particular the Common/tests unit tests contain

See the header files and the HTML  API documentation

extensive examples of the use of the Common APIs. <li class="MsoNormal" style="color: black;">Building and Debugging

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

Providers - </li>

existing utilities and test programs and the examples in the API

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

documentation.  In particular the Common/tests unit tests

documentation, and documentation from the Pegasus Technical Workshop

contain extensive examples of the use of the Common APIs.

which is available on the Pegasus web site. <li class="MsoNormal" style="color: black;">Building and Debugging

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

Clients - </li>

Debugging Providers - </li>

API documentation and the documentation on the Pegasus

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

Technical Workshop which is available on the Pegasus web site. <li class="MsoNormal" style="color: black;">PEPs - </li>

documentation, and documentation from the Pegasus Technical

The

Workshop which is available on the Pegasus web site.

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

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

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

Debugging Clients - </li>

OpenPegasus web site.  While these are the original design

API documentation and the documentation on the Pegasus

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

Technical Workshop which is available on the Pegasus web site.

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

the design and implementation of these features.

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

license agreements. Refer to the OpenPegasusNOTICE.txt file

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with

distributed with this work for additional information regarding

this work for additional information regarding copyright ownership.

Each contributor licenses this file to you under the OpenPegasus Open

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

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

file except in compliance with the License.

License.

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

obtaining a

obtaining a copy of this software and associated documentation

copy of this software and associated documentation files (the

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

"Software"),

restriction, including without limitation the rights to use,

to deal in the Software without restriction, including without

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

limitation

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

the rights to use, copy, modify, merge, publish, distribute,

Software is furnished to do so, subject to the following

sublicense,

conditions:

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

Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be

included

included in all copies or substantial portions of the Software.

in all copies or substantial portions of the Software.

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

EXPRESS

EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT

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

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

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

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

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

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

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

OTHER DEALINGS IN THE SOFTWARE.

</div>

</body></html>

</body>

</html>

Legend:

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

No CVS admin address has been configured