pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.9, 2007/01/09 01:58:56

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>

<style>

<!--

/* Font Definitions */

Line 953

Line 949

{margin-bottom:0in;}

-->

</style>

<style>

/* Style Definitions */

table.MsoNormalTable

Line 969

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

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

width="100%"></div>

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

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

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

<span

style="color: black;">

PEP #: 364

Title: Release

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

Notes for OpenPegasus version 2.12.1

Created: 10

September 2012

Authors: Karl

Schopmeyer, Marek Szermutzky

Status:  draft

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)

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>

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

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

-moz-background-origin: initial;

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

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

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

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

</td>

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

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

-moz-background-origin: initial;

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

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

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

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

</td>

</tr>

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

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

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

</td>

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

align="center"> <span

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

</td>

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

align="center"> <font

size="2">Karl Schopmeyer

</td>

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

September 2012

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

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

width="100%"></div>

Abstract: This document defines the release notes for

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

this PEP is to summarize the characteristics of this release,

point to other documentation that defines the release in more

detail, and provide additional information about this release

that is not available in the other Pegasus documentation.

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

CIM/WBEM Standards</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

Release

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

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

</ol>

<h2>Availability of this Release</h2>

NOTE: This document

defines the OpenPegasus 2.12.0 minor version release with

comments added to define the 2.12.1 revision to that minor

release.  OpenPegasus 2.12.1 is a bug fix revision to

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

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

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

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

review this list. OpenPegasus tries to execute only bug fixes

for revision releases and not include enhancements. The

OpenPegasus team recommends that users of Pegasus 2.12.0 update

to Pegasus 2.12.1. Note that in OpenPegasus ALL changes

including enhancements are defined as bugs and committed only

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

above defines ALL changes between 2.11.0 and 2.11.1.

This release is available in a number of forms including:

<ul>

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

formats. These can be downloaded from the <span

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

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

<li>OpenPegasus source RPMs on the OpenPegasus web

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

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

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

<li>The OpenPegasus CVS repository. The CVS tags

representing this release and subsequent snapshots that are

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

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

WEB

</head>

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

the root of the Pegasus source tree.

</div>

<h2>OpenPegasus Functionality in 2.12

Release</h2>

OpenPegasus overall status by release is defined by  a <a

Pegasus

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

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

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

site .  That web page shows the Pegasus users and developers

the status of the various features found in OpenPegasus using a

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

description of each feature.

OpenPegasus 2.12.1 is a Revision release.

NOTE: OpenPegasus releases are categorized as follows:

<ul>

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

Major release includes major functionality change and 

incompatible behavior changes and/or incompatible public API

changes,

</li>

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

Release and includes new functionality but maintains behavior

and public API compatibility,

</li>

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

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

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

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

Version</th>

</tr>

<tr>

<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

PEP #: 287

Title: Release

1.2</a>

Notes for OpenPegasus 2.6.0

</td>

</tr>

<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

Created: <st1:date year="2004" day="23" month="3">19 December 2006</st1:date>

Authors: Karl Schopmeyer

1.1</a>

</td>

</tr>

<tr>

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

</td>

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

interop 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

Status:  draft

Version History:

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

<tbody>

1.1</a>

</td>

</tr>

<tr>

<td><a

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

<o:p> </o:p>

8891</a>

</td>

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

destinations and subscriptions

</td>

<td>

</td>

</tr>

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

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

<o:p> </o:p>

5667</a>

</td>

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

buildInstance and filter functions in CIMInstance class

</td>

</td>

</tr>

<tr>

<td><a

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

<o:p> </o:p>

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

<o:p> </o:p>

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

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

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

<o:p>  19 December

2006</o:p>

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>

</tr>

<tr>

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

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

Karl Schopmeyer

9080 </a></td>

<td> Guaranteed provider

lifecycle indication delivery during CIMServer shutdown </td>

</td>

</tr>

<tr>

<td><a

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

Initial

Submission<o:p>

</o:p>

9112</a>

</td>

<td>Advertise IndicationService conformance to Indications

Profile by imlementing CIM_ElementConformsToProfile when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td>

<td>

</td>

</tr>

<tr>

<td><a

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

<td style="padding: 0.75pt;" align="center" height="21">20 December 2006</td>

<td style="padding: 0.75pt;" height="21">Remove functionality description section</td>

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

<td style="padding: 0.75pt;" align="center" height="21">2 January 2007</td>

9118</a>

</td>

<td>Add support for CIM_IndicationFilter.SourceNamespaces[]

property

</td>

<td>

</td>

</tr>

<tr>

<td><a

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

<td style="padding: 0.75pt;" height="21">Fix comments from 1.1. Note comments are in

Red in text for now.</td>

9136</a></td>

<td>Runtime configuration option to restrict cimserver to

listen on selected network interfaces</td>

<td>

</td>

</tr>

<tr>

<td><a

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

<td style="padding: 0.75pt;" align="center" height="21">3 January 2007</td>

<td style="padding: 0.75pt;" height="21">Clean up remaining comments and remove

comment markers.</td>

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

<td style="padding: 0.75pt;" align="center" height="23">8 January</td>

9159</a></td>

<td>

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

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

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

<tbody>

<tr>

<td>Add SSL Support to Dynamic Listener

</td>

</tr>

</tbody>

</table>

</td>

<td>

</td>

</tr>

<tr>

<td><a

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

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

<td style="padding: 0.75pt;" height="23">Move approved PEP, reflecting

changes to 1.3 for approval</td>

9172</a>

</td>

<td>Add capability for administrator to override hostname

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

</tbody>

</table>

<o:p> </o:p>

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

Abstract: This document defines the release notes for the 2.6.0 release of the Pegasus CIM Server.

The purpose of this PEP is simply to summarize the characteristics of this

release, point to other documentation that defines the release in more detail,

and provide additional information about this release that is not available in

the other Pegasus documentation. <a href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35" target="_self">

</a>

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

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

</o:p></h2>

<ol>

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

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

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

Release</a></li>

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

9229</a>

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

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

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

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

with DMTF Specifications</a></li>

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

9236</a></td>

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

version supports only X86 and X86_64 and requires clang

version 3 or greater.

</td>

<td>

</td>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality

change status between Pegasus versions. <a

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

identified by a change in color from the previous release to

this release</a> on the <a

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

Status WEB Page</a>.

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

OpenPegasus 2.12

</h3>

Prior to version 2.12 OpenPegasus used an OpenPegasus internal

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

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

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

Documentation</a></li>

</ol>

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 was felt that the information below was worth

repeating in subsequent Release Notes

IPv6 is

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

generation" protocol designed by the IETF to replace the

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

Support for OpenPegasus is documented in <a

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

PEP 291</a>.

The IPv6 support in OpenPegasus is controlled by the

PEGASUS_ENABLE_IPV6 build variable. The default for this

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

OpenPegasus will disable the IPv6 support.

The following subsections provide some information on IPv6

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

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

support on a platform by OpenPegasus. If you build with

PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you

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

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

both the CIM Server and Listener components. For more

information on IPv6 support for your specific platform, refer to

the documentation for that platform.

All OpenPegasus externals that support either 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

<h2>Availability

of this Release</h2>

This release is available in a number of forms including:

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

or

<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 specifying IPv6 addresses, refer to <a

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

Version 6 Addressing Architecture</a> and <a

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

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

<h4>IPv6 on Linux</h4>

Modern Linux distributions already contain IPv6-ready kernels,

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

possible that this module is not loaded automatically on

startup.

Note: you

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

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

is no longer improved according to definitions in latest RFCs.

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

To check whether your current running kernel supports IPv6,

take a look into your /proc filesystem. The entry

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

like:

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

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

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

ready"</big></div>

For more information on enabling IPv6 in the Linux kernel and

configuring network interfaces, refer to <a

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

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

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

<ul>

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

downloaded from the OpenPegasus Web

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

<li>OpenPegasus  binary and source RPMs on the OpenPegasus web

site.. The source RPM is  available on the OpenPegasus web site that can be used to build binaries for most LSB-compliant RPM-based Linux distributions and versions.</li>

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

subsequent snapshots that are 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

snapshots page</a>.</li>

</ul>

6586</a> and

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

bug

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

WEB site</a>.

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

Pegasus source

tree.

</div>

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

Pegasus overall status by release is defined by  a

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

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

IPv6 socket failure. You should be aware that OpenPegasus with

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

IPv6 enabled may be significantly impacted in these

Pegasus users and developers the status of the various features found in Pegasus

environments.

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

<h4>IPv6 on Windows</h4>

each feature.Pegasus 2.6.0

Microsoft provides supported IPv6 implementations for Windows

is a major release, extending Pegasus 2.5 in selected

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

areas as described in the Pegasus  PEP defining this release (see PEP 218)

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

.

On Windows XP, you can use the ipv6.exe

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

The major areas of development for this release  were as follows. For

example:

more information access the documented PEP:

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

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

Table of Major Changes for this Release

ipv6 if</big></div>

Windows Vista and Windows Server 2008 support an integrated

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

<TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666

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

borderColorLight=#cccccc border=1>

tested on Windows Vista or Windows Server 2008.

<TBODY>

For more information on installing, configuring, and using IPv6

on Windows platforms, refer to the document <a

<TH bgColor=#E0E8EF>Description</TH>

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

<TH bgColor=#E0E8EF>Posted PEP Version</TH>

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

</TR>

Questions</a>.

<h4>Testing  OpenPegasus IPv6 support</h4>

<TD align="left">Embedded Instance Support in Pegasus</TD>

As part of the OpenPegasus automated tests, the TestClient,

<TD>

g11ntest, and IndicationStressTest test clients were modified to

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

1.3</a>

PEGASUS_ENABLE_IPV6=true.

</TD>

</TR>

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

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

IPv6 loopback on a system with OpenPegasus running on the WBEM

<TD align="left">Providing SMI-Server Profile through OpenPegasus</TD>

standard http port of 5988:

<TD>

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

1.5.1</a></TD>

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

</TR>

Considerations</a></h2>

Support for forward-compatibility is a fundamental design

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

<TD align="left">Incorporation of CIM_Error into OpenPegasus Infrastructure</TD>

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

<TD>

the externally defined OpenPegasus interface, to continue to

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

1.4</a>

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

</TD>

standard that significantly affects interoperability) that may

</TR>

require the community to make potentially incompatible changes.

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

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

<TD align="left">Language Interfaces</TD>

upgrading to this OpenPegasus release.

<TD>

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

1.0</a>

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

</TD>

width="80%">

</TR>

<tbody>

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

<TD align="left">Reducing Pegasus Code size and static memory usage</TD>

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

<TD>

</tr>

1.3.1</a>

<td><a

</TD>

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

</TR>

<TD align="left">Indication Subscription Management</TD>

<TD>

1.2</a>

</TD>

</TR>

<TD align="left">Audit Logging</TD>

<TD>

1.4</a></TD>

</TR>

<TD align="left">SSL Certificate Management Command Interfaces</TD>

<TD>

1.2</a></TD>

</TR>

<TD align="left">CMPI 2.0 Currency</TD>

<TD>

1.1</a>

</TD>

</TR>

<TD align="left">SLP enhancements for Pegasus 2.6</TD>

<TD>

1.5</a></TD>

</TR>

<TD align="left">Repository Archive</TD>

<TD>

1.1</a>

</TD>

</TR>

</TBODY>

</TABLE>

</UL>

</html>

The status of several components of Pegasus functionality change status

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

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

release to this release</a> on the

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

Finally, a significant number of internal changes and corrections were made

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

for more information.

<ol>

</ol>

<h2>OpenPegasus Relationship to

8830</a></td>

CIM/WBEM Standards</h2>

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

requirement for providers (CMPI and C++) to 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 NOP. This may be a change in behavior for

provider relying in some unknown way on the instance being

filtered through these functions. To allow users to

actually filter properties from an instance, new function

CIMInstance::filterInstance() will actually filter

properties from an instance exactly as the

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

</tr>

<td><a

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

Pegasus was designed and implemented to comply with the DMTF

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

to which this version of Pegasus aims to conform today.

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 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 DMTF specifications to which this version of Pegasus aims to

conform today.

<tbody>

<tr>

<td bgcolor="#00ffff" width="33%">DMTF Specification</td>

<td bgcolor="#00ffff" width="33%">Specification Version</td>

</tr>

<tr>

<td width="33%">DSP 0004 - CIM Infrastructure Specification</td>

<td width="33%">Version 2.3 Final, 4 October 2005</td>

</tr>

<tr>

<td width="33%">DSP 0200 - CIM Operations over HTTP</td>

<td width="33%">Version 1.2, Final, January 09, 2007</td>

<td width="33%">1.2.0, preliminary, 9 December 2004</td>

</tr>

<tr>

<td width="33%">DSP 0201 - Representation of CIM in XML</td>

<td width="33%">Version 2.2 Final, January 09, 2007</td>

<td width="33%">2.2.0, preliminary, December 2004</td>

</tr>

<tr>

<td width="33%">DSP 0202 - CIM Query Language Specification</td>

<td width="33%">1.0.0, preliminary, 9 December 2004</td>

</tr>

<tr>

<td width="33%">DSP 0205 - WBEM Discovery using SLP</td>

<td width="33%">1.0, preliminary, 27 January 2004</td>

</tr>

<tr>

<td width="33%">DSP 0206 - WBEM SLP Template</td>

<td width="33%">1.0.0, Preliminary, January 2004</td>

</tr>

<tr>

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

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

<td width="33%">2.9 Final, Jan. 2005 ( default) 2.13.1 (available in

</tr>

pegasus CVS)</td>

<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

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

SMI Profiles Supported</h2>

DMTF Specifications</a></h2>

Today OpenPegasus includes support for several DMTF profiles

including the ones defined below:

It is a major goal

<ol>

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

<li>DMTF ProfileRegistration Version 1.0.0</li>

specifications.  However, today there are a number of known

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

differences. 

as the SNIA SMI Indication profile it also supports this

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

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 DMTF Specifications</a></h2>

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

utilize the DMTF CIM/WBEM specifications.  However, today

there are a number of known 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 specifications but

more information on provider registration.  This is not a

is a different method of registration than many CIM Servers and means that the

deviation from the specifications but is a different method of

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

registration than many CIM Servers and means that the the

provider qualifier is unused in Pegasus.</li>

<li> Indications -Today Pegasus supports process indications and

<li>Lifecycle Indications -Today Pegasus supports

lifecycle indications when defined specifically by providers. Pegasus does not

process indications and lifecycle indications when defined

support lifecycle indications if they are not defined by the provider or for

specifically by providers. Pegasus does not support lifecycle

changes to CIM Classes.

indications if they are not defined by the provider or for

For more information see the Pegasus CVS

changes to CIM Classes. <span

file  <a name="comtag_137"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

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>

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

IncludeQualifiers

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

option on Instance Operations

Operations

- The DMTF specifications have deprecated the use of

The DMTF specifications have deprecated the use of qualifiers on instance

qualifiers on instance operations with the 1.2 CIM

operations with the 1.2 CIM Operations Specification.  Some CIM Client implementations expect instances

Operations Specification and stated specifically that the

returned

client should NOT depend on the includeQualifiers

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

parameter of the CIM/XML instance operations returning

definition (such as KEY qualifiers on properties).   Pegasus

qualifiers.  Some CIM Client implementations expect

today expects the provider to complete the qualifiers on instances in

instances returned from the CIM Server to include the

accordance with the specification and generally the interpretation is

qualifiers defined in the class definition (such as KEY

that Pegasus applies class level qualifiers when the includeInstance

qualifiers on properties).   Pegasus

parameter is supplied on instance operations.  However, Pegasus

today expects the provider to complete the qualifiers on

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

instances in accordance with the specification and generally

should NOT depend on Pegasus accurately honoring the includeQualifier

the interpretation is that Pegasus applies class level

parameter for instance operations.  In the future it is expected

qualifiers when the includeInstance parameter is supplied on

that Pegasus will deprecate the use of qualifiers on instance

instance operations.  However, Pegasus today is

operations completely.

inconsistent in the return of qualifiers so that the user

should NOT depend on Pegasus accurately honoring the

includeQualifier parameter for instance operations.  In

the future it is expected that Pegasus will deprecate the

use of qualifiers on instance operations completely.

 When Pegasus uses object normalization, the normalizer

does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.

</li>

<li>LocalOnly option on instance Operations - With the

<li>LocalOnly option on instance

1.1 version of Specification for CIM Operations over HTTP, the

Operations - With the 1.1 version of Specification for CIM

definition of the LocalOnly parameter for the GetInstance and

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

Enumerate Instances operations was modified. This change was

GetInstance and EnumerateInstances operations was modified. This 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 Oprations - Pegasus

does not support the DMTF defined MultiRequest Operation

does not support the DMTF defined MultiRequest Operation option.

option.

</li>

<li>

MOF Compiler namespace pragma -

MOFCompiler namespace pragma - The

The Pegasus compiler does not support the namespace pragma.

Pegasus compiler does not support the namespace pragma.

</li>

<li>CIMOperation Trailer - Pegasus implements chunking

based on the DSP0200 1.2.0 preliminary spec. including the

operation trailer defined in that specification Refer to bug <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 1.2 final specification as a non-compatible change so

that if chunking is used Pegasus is returning a noncompliant

response to enumerate type requests. </li>

<li>Whitespace in XML value

Element - Pegasus trims the leading and trailing

whitespace from XML value elements that are of the Type

String.  This behavior is documented in Pegasus bug <a

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

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

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

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

are some documented bugs in Pegasus such as this that the

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. 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 name in OpenPegasus is "root/PG_Interop".  In

versions of OpenPegasus prior to 2.12.0 this could be changed

during build by modifying a string definition in the code.

Effective version 2.12 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>).

</ol>

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

Platforms</a></h2>

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus

code

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

regularly document issues and/or fix defects as the Pegasus

code base is changed. 

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

a group

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

Pegasus cannot be

assured.  In all cases, including the active platforms, it is the

responsibility of the entity that packages and/or compiles OpenPegasus

for shipment or deployment, to read, and actively monitor the Pegasus bugzilla database for a list of relevant defects that affect their

platform.   The platforms that are considered 'active' for this

Pegasus release are:

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

Each OpenPegasus release lists as 'active'

platforms those hardware/software platforms that have recognized

ports for the Pegasus code base including a maintainer for the

platform that will be willing to regularly document issues

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

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

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

correct operation of  Pegasus cannot be assured.  In

all cases, including the active platforms, it is the

responsibility of the entity that packages and/or compiles

OpenPegasus for shipment or deployment, to read, and actively

monitor the Pegasus Bugzilla 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 for 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)

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

-moz-background-origin: initial;

Platform and

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

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

height="26">

Platform

</td>

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

</td>

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

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

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

-moz-background-origin: initial;

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

height="26">

Compilers<span

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

</td>

</tr>

HP-UX<o:p>

PA_RISC and Itanium</o:p>

HP-UX<o:p></o:p>

</td>

</td>

HP <span

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

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

</td>

</tr>

<span

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

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

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

</td>

<span

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

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

</td>

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

</td>

</tr>

<span

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

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

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

</td>

<span

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

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

</td>

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

</td>

</tr>

Linux

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

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

</td>

</td>

<span

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

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

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

</td>

</tr>

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

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

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

Linux IA-32<o:p></o:p>

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

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

</td>

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

experimental and is not part of the nightly tests

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

gcc

(versions 2.9x and 3.xx)<o:p></o:p>

</td>

</tr>

Linux

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

Windows 2000<o:p></o:p>

</td>

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

Microsoft

Visual C++ Ver 6 and Microsoft .Net compiler Version.   Works on VC .NET 2003 (aka

v7.1)<o:p></o:p>

</td>

</tr>

<tr>

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

and up</td>

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

Windows XP<o:p>, Windows

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

2003</o:p>

</td>

Microsoft

Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1<o:p></o:p>

</td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this

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)

<td style="padding: 0.75pt; width: 126.75pt;" height="43" width="211"> MacOS version 10.2 and higher</td>

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

-moz-background-origin: initial;

<td style="padding: 0.75pt; width: 173.25pt;" height="43" width="289"> gcc 3.3,

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

gcc 4.01</td>

height="26">

Platform

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

</td>

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

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

-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="vertical-align: top;"><big>HP OpenVMS Alpha

Windows Vista, Windows 7, Windows Server 2008

</big></td>

</td>

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

<td style="vertical-align: top;"> <big>HP C++ V6.5-042 for OpenVMS

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

Alpha and above</big> </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 and higher</td>

</tr>

<tr>

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

<td style="vertical-align: top;"><big> HP OpenVMS IA64</big></td>

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

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

<td style="vertical-align: top;"><big>HP C++ V7.1-011 on OpenVMS IA64 and above</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><font

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

color="RED">Solaris

9</big></td>

</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 style="vertical-align: top;"><big>GNU  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><big>HP OpenVMS 8.3 or later Alpha</big></td>

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

<td><big>HP

C++ V7.3-009

</big></td>

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

</tr>

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

<tr>

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

<td><big> HP OpenVMS 8.3

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

</td>

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

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

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

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

</tr>

<tr>

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

</td>

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

Visual C++ 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>CC Compiler Sun Studio 5.11</big></td>

</tr>

</tbody>

</table>

Platform patches

<font

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

Platform patches

platform patches Pegasus requires.

The following is a list of platform

patches Pegasus requires.

RHAS

2.1 needs the update to fix Red Hat Bugzilla 98815.

</div>

Further information regarding Pegasus support on IBM platforms can

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

Further information regarding Pegasus support on HP platforms can be

found at:

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

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

The Pegasus bugzilla database documents any defects found in Pegasus

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

database</a>.  Note that all changes  committed for this release have been marked

with the keyword 2.6.0_APPROVED so that

all changes for this release can be found with the following bug search.

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

were documented through bugs.  Thus bugs were filed not only for bugs and

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

representing the work on PEPs done for Pegasus 2.6.  Therefore, a search of

the bugzilla base for bugs with the tag 2.6.0_Approved will yield all changes to

the Pegasus CVS tree for Pegasus 2.6.0.

    - Changes for Pegasus 2.6.0 release (bugs Tagged

2.6.0_APPROVED) 

Pegasus 2.6.0_APPROVED bug list</a>

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

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

The Pegasus project is controlled largely through a set of documents

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

modified Pegasus functionality and for the definition and documentation

of releases.

Specifically the following PEPs define the characteristics of this

Pegasus release. These PEPs are available on as

OpenPegasus Approved PEPs.</a>

<ol>

<li>

PEP 218 - OpenPegasus Release Definition - This PEP is used

<font

throughout the development of this version as the control point for

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

functionality that will go into the release and points to all of the PEPs that

to fix Red Hat Bugzilla 98815.

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

</li>

<li>

PEP 277 -  OpenPegasus  Build and Configuration

Options  for Selected

Platforms</li>

<li>

PEP 278 OpenPegaus 2.5 External Interfaces - Lists the public

RHEL 4.4

interfaces for clients and providers that are considered external and

multithreading bug in getpwuid-r could cause a CIM Server

therefore "frozen".

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

</li>

<li>

PEP 279 - OpenPegasus  SDK Packaging Definition - Defines the

Red Hat and

recommended set of files for inclusion in the OpenPegasus SDK</li>

SUSE Linux multiple versions - multithreaded client

intermittently fails connecting to IPv6 (Pegasus Bugzilla

<li>PEP 280 - Pegasus  Runtime Packaging Definition - Defines the

6586) (Red Hat bug 248052)

recommended set of files for inclusion in this OpenPegasus release.</li>

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

approved PEP

repository and the OpenPegasus source tree root directory)

</li>

<li>PEP 289  - Pegasus readme.txt for this release (Located in PEP repository

and also in the OpenPegasus

source

tree root directory).</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms

can be found at: <a

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

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 at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.

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

Defects</a></h2>

The OpenPegasus Bugzilla database documents any defects found

in Pegasus and  is available through the following

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

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

The following documentation is available for the this Pegasus

release:

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

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

documented through bugs.  Bugs reports are filed not only

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

process of committing new code representing the work on PEPs

done for OpenPegasus 2.6 and all subsequent versions. 

Therefore, a search of the OpenPegasus Bugzilla 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>,

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

2.6.1_APPROVED</a>, <a

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

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

OpenPegasus release.

- Changes between the 2.12.0 release

and 2.12.1 revision are defined in bugs tagged

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

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

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

combination of help generally available with the -h 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 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

Clients - API documentation and the documentation on the Pegasus

Technical Workshop which is available on the Pegasus web site.</li>

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

commands - compiler help (cimmofl -h)</li>

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

bugs</a>

- Changes that were made in the minor

release 2.12 are in bugs Tagged 2.12.0_APPROVED. The link

is <a

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

Pegasus 2.12.0_APPROVED bug list.</a>

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

Documentation">Release Control and Version Definition

Documentation</a></h2>

The OpenPegasus project is controlled largely through the CVS

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

definition and review mechanism for new and modified Pegasus

functionality and for the definition and documentation of

releases.

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

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

</ul>

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

The following documentation is available for the this

<o:p></o:p>

Pegasus release:

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

</li>

A combination of help generally available with the --help

Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open

option for each command and HTML documentation for most of the

Group; VERITAS Software Corporation; Intel Corp.

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

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

usage documentation - </li>

See the header files and the HTML  API documentation

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

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

obtaining a copy  of this software and associated documentation files (the

existing utilities and test programs and the examples in the API

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

documentation.  In particular the Common/tests unit tests

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

contain extensive examples of the use of the Common APIs.

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

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

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

Debugging Providers - </li>

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.

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE

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

SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE

Debugging Clients - </li>

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

API documentation and the documentation on the Pegasus

IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

Technical Workshop which is available on the Pegasus web site.

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE

AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

The features of Pegasus that have been installed in this and

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

the previous few versions are defined by Pegasus PEPs that are

OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

available on the OpenPegasus web site.  While these are the

SOFTWARE.

original design documents largely and use in the process of

</div>

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 agreements. Refer to the OpenPegasusNOTICE.txt file

distributed with this work for additional information regarding

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

file except in compliance with the License.

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

obtaining a copy of this software and associated documentation

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

restriction, including without limitation the rights to use,

copy, modify, merge, publish, distribute, sublicense, 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 in all copies or substantial portions of the Software.

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

EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT

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

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

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

OTHER DEALINGS IN THE SOFTWARE.

</div>

</body>

</html>

Legend:

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

No CVS admin address has been configured