pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.10.2.1 and 1.17.4.2

version 1.10.2.1, 2007/10/05 18:19:26

version 1.17.4.2, 2013/06/03 22:34:01

Line 1

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

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

<head>

<style>

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

</style>

Line 962

Line 963

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>

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

</head>

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

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

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"

<span

width="100%"></div>

style="font-size: 13.5pt; color: black;">OpenPegasus Enhancement

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

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

align="center">Pegasus

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

<span

style="color: black;">

PEP #: 305

PEP #: 364

Title: Release

Notes for OpenPegasus 2.6.1

Notes for OpenPegasus version 2.12.0

Created: <st1:date

Created: 10

year="2004" day="23" month="3">3 August 2007

September 2012

</st1:date>

Authors: Dave

Sudlik

Status:  approved

Authors: Karl

Schopmeyer

Status:  draft

Version History:

<table class="MsoNormalTable" style="width: 868px; height: 54px;"

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

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

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

<tbody>

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

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

<span

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

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

</td>

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

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

<span

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

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

</td>

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

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

<span

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

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

</td>

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

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

<span

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

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

</o:p>

</td>

</tr>

Line 1056

Line 1022

<span

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

</td>

<span

<font

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

size="2">10 September 2012

August 2007

</o:p>

</td>

<span

style="font-family: Arial;">Dave Sudlik

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

</td>

<span

<font

style="font-family: Arial; color: black;">Initial

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

Submission. Updates for 2.6.1 (from 2.6) are highlighted <span

style="color: rgb(255, 0, 0);">in

this color. <o:p><font

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

</td>

</tr>

<tr>

<td style="vertical-align: top; text-align: center;">1.1

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

2012

</td>

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

Schopmeyer

</td>

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

complete links to PEPs

</td>

</tr>

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

2012

</td>

<td style="vertical-align: top; text-align: center;">8 August 2007

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

Schopmeyer

</td>

<td style="vertical-align: top; text-align: center;">Dave Sudlik

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

comments from first review

</td>

<td style="vertical-align: top;">Updates from review <span

</tr>

style="color: rgb(255, 0, 0);">

<tr>

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

2012

</td>

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

Schopmeyer

</td>

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

8830 (compatibility considerations) and bug 9172(repupgrade)

</td>

</tr>

</tr>

</tbody>

</table>

<o:p> </o:p>

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

Abstract: This document defines the release notes for the 2.12.0

Abstract: This document defines the release notes for the

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

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

summarize the characteristics of this release, point to other

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

other Pegasus documentation.

style="font-size: 9pt;"><a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35"

target="_self">

</a>

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

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

<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

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

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

of This Release</a></li>

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

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

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

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

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

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

Release

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

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

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

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

Documentation</a></li>

</ol>

<h2>Availability

<h2>Availability of this Release</h2>

of this Release</h2>

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

These can be downloaded from the OpenPegasus

downloaded from the OpenPegasus Web

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

site at <a

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

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

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

<li>OpenPegasus  binary and source RPMs on the

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

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

distributions and versions.</li>

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

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

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

release and subsequent snapshots that are made available in the

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

Pegasus CVS are defined on the OpenPegasus CVS repository web page

release and

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

subsequent snapshots that are made available in the Pegasus CVS are

CVS

defined on the OpenPegasus CVS repository web page (see the <a

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

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

page</a>.</li>

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

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

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

WEB

WEB site</a>.

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

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

of the Pegasus source tree.

Pegasus source

tree.

</div>

<h2>OpenPegasus Functionality for This

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

Release</h2>

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

Pegasus overall status by release is defined by  a <a

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

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

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

Page</a> that is available on the OpenPegasus web site .  That web

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

page shows the Pegasus users and developers the status of the various

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

features found in Pegasus using a simple color coded key (white, red,

OpenPegasus 2.12.0 is a major release, extending the previous Pegasus

yellow, green) and a description of each feature.

release in selected areas as described in the Pegasus  PEP defining

Pegasus 2.6.1 is a "point"

this release .

release, extending Pegasus 2.6 in

selected areas. Normally an OpenPegasus "point" release does not

NOTE: OpenPegasus releases are categorized as follows:

contain major new pieces of functionality, but in this case one new PEP

<ul>

was added for IPv6 support, the description of which has been added to

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

these Release Notes.

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>

ALL changes for each release are documented in the

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

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

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

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

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

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

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

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

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

through corresponding Bugzilla tags for each revisions (ex

2.12.1_APPROVED).

The major areas of development for this release  were as

The major areas of development including both enhancements and bug

follows. For more information access the documented PEP:

fixes for this release  were as follows. Note that the bugs listed

represent only those features incorporated in bugs without PEPS that are

Table of Major Changes for this Release

considered enhancements, not all bugs incorporated in the release. For

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

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

bordercolorlight="#cccccc" border="1" cellspacing="1">

<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="#e0e8ef">Description</th>

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

<th bgcolor="#e0e8ef">Posted PEP

<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

1.2</a>

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

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

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;" align="left" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=5667">Bug

5667</a>

</td>

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

and filter functions in CIMInstance class

</td>

</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;" align="left" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9013">Bug

<td style="color: rgb(153, 51, 153);" align="left">OpenPegasus

9013</a>

Support for IPv6: Stage 1

</td>

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

style="">Enable ordered indication delivery from

provider through CIMServer when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE compile flag is set</td>

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

</td>

</tr>

<tr>

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

9112</a>

</td>

<td>Advertise IndicationService conformance to Indications Profileby

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

9114</a>

</td>

<td>Advertise DMTF Indications Profile (DSP1054) 1.1.0 conformance </td>

<td>

</td>

</tr>

<tr>

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

9118</a>

</td>

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

</td>

<td>

</td>

</tr>

<tr>

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

9136</a></td>

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

selected network interfaces</td>

<td>

</td>

</tr>

<tr>

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

9155</a>

</td>

<td>Update to include CIM 2.31 Schema and set this as 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>

<tr>

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

9172</a>

</td>

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

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

<td style="color: rgb(0, 153, 0);"> <a

</tr>

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

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

status between Pegasus versions. <a

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

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

that

by a change in color from the previous release to this release</a>

have

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

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

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

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

OpenPegasus 2.12

bug section below for more information.

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

wiki faq</a>s.

<h3 style="color: rgb(153, 51, 153);">IPv6 Support

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

</h3>

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

IPv6 is short for "Internet

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

Protocol

become an issue.

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

Effective OpenPegasus 2.12.0 a new build variable has been

controlled by the PEGASUS_ENABLE_IPV6 build variable. Setting this to

defined  (PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus

'true' before building OpenPegasus will enable the IPv6 support. In

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

2.6.1 this variable will default to 'false' to omit the IPv6 support.

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

The following subsections provide

However, today OpenPegasus is committed to the single namespace defined

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

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

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

number of OpenPegasus  installations are committed to the

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

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

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

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

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

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

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

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

Listener components. For more information on IPv6 support for your

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

specific platform, refer to the documentation for that platform.

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.

All OpenPegasus externals that

NOTE: If you redefine the interop namespace name with

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

PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp" namespace

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

will not connect with the updated version of OpenPegasus.

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);">osinfo -h

3ffe:1:2:1 -p 5988

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

</div>

NOTE: This functionality was incorporated in OpenPegasus 2.7.0

But the cimcli command, which

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

takes

subsequent Release Notes

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

IPv6 is short

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

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.

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

The following subsections provide some information on IPv6 support for

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

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

or

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.

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

All OpenPegasus externals that support either a hostname or an IP

[3ffe:1:2:1]:5989

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

</div>

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

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

For more information on

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

specifying

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

IPv6 addresses, refer to <a style="color: rgb(153, 51, 153);"

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

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

IPv6-configured network interface would be specified as:

6 Addressing Architecture</a>

and <a style="color: rgb(153, 51, 153);"

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

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

style="color: rgb(153, 51, 153);">.<br

style="color: rgb(153, 51, 153);">

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

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

running

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

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

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

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

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

delimited with brackets, for example:

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

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

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

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

or

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

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

</div>

For more information on

enabling

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

style="color: rgb(153, 51, 153);"

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

Documentation Project's IPv6 HOWTO</a><span

style="color: rgb(153, 51, 153);">.

Warning:

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

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

RFC

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

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

described in <a style="color: rgb(153, 51, 153);"

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

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

<h4>IPv6 on Linux</h4>

bug 6586</a> and <a

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

style="color: rgb(153, 51, 153);"

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

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

this module is not loaded automatically on startup.

bug 248052</a>, and manifests

Note: you shouldn't use

itself as an intermittent IPv6 socket failure. You should be aware that

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

OpenPegasus with IPv6 enabled may be

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

significantly impacted in these environments.<br

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

style="color: rgb(153, 51, 153);">

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

<h4 style="color: rgb(153, 51, 153);">IPv6 on Windows</h4>

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

Microsoft provides supported IPv6

short automated test looks like:

implementations for Windows Server

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

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

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

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

On Windows XP, you can use the <span

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

style="font-weight: bold; color: rgb(153, 51, 153);">ipv6.exe<span

For more information on enabling IPv6 in the Linux kernel and

style="color: rgb(153, 51, 153);"> tool to install, uninstall, and

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

query

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

your IPv6 configuration. For example:<br

style="color: rgb(153, 51, 153);">

Warning: There is currently an

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

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

on RHEL5 and SLES10 systems. This problem is described in

ipv6 if

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

</div>

bug

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

Windows Vista

bug

and Windows Server 2008 support an integrated

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

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

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

Note that the OpenPegasus IPv6 support in 2.6.1 has not yet been tested

may be significantly impacted in these environments.

on Windows Vista or Windows Server 2008.<br

<h4>IPv6 on Windows</h4>

style="color: rgb(153, 51, 153);">

Microsoft provides supported IPv6 implementations for Windows Server

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

For more information on

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

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

On Windows XP, you can use the ipv6.exe

the document <a style="color: rgb(153, 51, 153);"

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

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

example:

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

style="color: rgb(153, 51, 153);">.<br

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

style="color: rgb(153, 51, 153);">

color="#000000">ipv6 install

<h4 style="color: rgb(153, 51, 153);">Testing your OpenPegasus IPv6

ipv6 if</big></div>

support</h4>

Windows Vista and Windows Server 2008 support an integrated IPv4 and

As part of the OpenPegasus

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

automated tests, the TestClient, g11ntest, and IndicationStressTest

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

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

Windows Server 2008.

(::1) if PEGASUS_ENABLE_IPV6=true.<br

style="color: rgb(153, 51, 153);">

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

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

You can also perform manual

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

tests

Questions</a>.

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

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

<h4>Testing  OpenPegasus IPv6 support</h4>

running on the wbem standard http port of 5988:<br

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

style="color: rgb(153, 51, 153);">

IndicationStressTest test clients were modified to run tests using the

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

osinfo -h ::1

</div>

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

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

<ol>

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

</ol>

<h2>OpenPegasus Relationship to

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

CIM/WBEM Standards</h2>

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

Pegasus was designed and implemented to comply with the DMTF

Support for forward-compatibility is a fundamental design principle for

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

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

DMTF specifications to which this version of Pegasus aims to conform

OpenPegasus providers or clients, using only the externally defined

today.

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

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

non-compliance with a standard that significantly affects

interoperability) that may 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 upgrading to this OpenPegasus release.

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

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

<tbody>

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

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

</tr>

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

8830</a></td>

<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

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>

Line 1378

Line 1640

</tr>

<tr>

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

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

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

</tr>

<tr>

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

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

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

</tr>

<tr>

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

Line 1398

Line 1660

</tr>

<tr>

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

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

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

in pegasus CVS)</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">Conformance

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

Exceptions to

Profiles Supported</h2>

DMTF Specifications</a></h2>

Today OpenPegasus includes support for several DMTF profiles including

It is a major goal

the ones defined below:

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

<li>DMTF ProfileRegistration Version 1.0.0</li>

through a set of Pegasus Provider registration classes rather than

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

support the DMTF defined Provider Qualifier. Pegasus will not support

SNIA SMI Indication profile it also supports this profile. This

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

profile is enabled by compiling OpenPegasus with the buld 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 support the

DMTF defined Provider Qualifier. Pegasus will not support this

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

provider registration.  This is not a deviation from the

specifications but is a different method of registration than many CIM

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

Servers and means that the the provider qualifier is unused in

<li> Indications -Today Pegasus supports process

Pegasus.</li>

<li>Lifecycle Indications -Today Pegasus supports process

indications and lifecycle indications when defined specifically by

providers. Pegasus does not support lifecycle indications if they are

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

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

color="#ff0000">  For

For more

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

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

face="Courier New">pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

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

size="2">.</li>

<li>

<font

IncludeQualifiers

style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers

option

option on Instance Operations

on Instance Operations

- The DMTF specifications have deprecated the use of qualifiers on

The DMTF specifications have deprecated the use of qualifiers on

instance operations with the 1.2 CIM Operations Specification and

instance operations with the 1.2 CIM Operations Specification. 

stated specifically that the client should NOT depend on the

Some CIM Client implementations expect instances

includeQualifiers parameter of the CIM/XML instance operations

returned

returning qualifiers.  Some CIM Client implementations expect

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

instances returned from the CIM Server to include the qualifiers

definition (such as KEY qualifiers on properties).   Pegasus

defined in the class definition (such as KEY qualifiers on

today expects the provider to complete the qualifiers on instances in

properties).   Pegasus today expects the

accordance with the specification and generally the interpretation is

provider to complete the qualifiers on instances in accordance with

that Pegasus applies class level qualifiers when the includeInstance

the specification and generally the interpretation is that Pegasus

parameter is supplied on instance operations.  However, Pegasus

applies class level qualifiers when the includeInstance parameter is

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

supplied on 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 should NOT

parameter for instance operations.  In the future it is expected

depend on Pegasus accurately honoring the includeQualifier parameter

that Pegasus will deprecate the use of qualifiers on instance

for instance operations.  In the future it is expected that

operations completely.

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

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

Operations - With the 1.1 version of Specification for CIM

version of Specification for CIM Operations over HTTP, the definition

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

of the LocalOnly parameter for the GetInstance and Enumerate Instances

GetInstance and EnumerateInstances operations was modified. This change

operations was modified. This change was incorrect, resulted in

was incorrect, resulted in reduced functionality and introduced a

reduced functionality and introduced a number of backward

number of backward compatibility issues. As a result of issues

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

introduced by this change, we strongly recommend that CIM Clients set

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

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

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

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

properties returned. See Appendix C of this specification for more

specification for more information.</li>

information.</li>

<li>

MultiRequest Oprations - Pegasus

MultiRequest Operations - Pegasus does not

does not support the DMTF defined MultiRequest Operation option.

support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOFCompiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

</li>

<li>Pegasus implements

<li>CIMOperation Trailer - Pegasus implements chunking based on

chunking

the DSP0200 1.2.0 preliminary spec. including the operation trailer

based on the DSP0200 1.2.0 preliminary spec. Refer to bug <a

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

style="color: rgb(153, 51, 153);"

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

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

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

style="color: rgb(153, 51, 153);"> for more details.

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 configuraton

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

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

name="Supported Platforms">Supported

Platforms</a></h2>

Each OpenPegasus release lists as 'active' platforms those

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus

code

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

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

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

regularly document issues and/or fix defects as the Pegasus

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

code base is changed. 

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

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

maintenance, correct operation of  Pegasus cannot be assured. 

a group

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

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

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

Pegasus cannot be

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

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

for a list of relevant defects that affect their platform.  

responsibility of the entity that packages and/or compiles OpenPegasus

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

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

below.  The first table represents platform for which testing is

bugzilla database for a list of relevant defects that affect their

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

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

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

Pegasus release are:

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

second table.

<table class="MsoNormalTable" style="width: 302.25pt;" border="1"

Actively Supported Platforms (Nightly Tests Reported for this release)

cellpadding="0" cellspacing="1" height="409" width="504">

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

cellspacing="1">

<tbody>

<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: 240px;"

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

height="26">

height="26" width="211">

Platform and

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

</td>

<td

height="26">

height="26" width="289">

Compilers<span

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

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

width="211">

HP-UX<o:p>

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

PA_RISC and Itanium</o:p>

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

HP aC++

HP <span

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

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

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

width="211">

Linux

<span

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

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

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

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

gcc<span

<span

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

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

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

width="211">

zLinux<span

<span

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

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

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

gcc<span

width="289">

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

<span

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

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

width="211">

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

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

gcc<span

<span

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

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

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

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

width="211">

IA-32</td>

Linux IA-32, <span

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

style="color: rgb(153, 51, 153);">X86_64<o:p></o:p>

size="3">gcc<font

</td>

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

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

is considered experimental and is not part of the nightly

width="289">

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

<span

</tr>

style="color: black;">gcc

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

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

</td>

gcc<span

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

size="3">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;">XL C/C++ from z/OS

Version 1.7 and up</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; width: 126.75pt;" height="91"

width="211">

height="26">

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

Platform and

</td>

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

<td style="padding: 0.75pt; width: 173.25pt;" height="91"

</td>

width="289">

Microsoft

height="26">

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

Compilers<span

style="color: black;">Works on VC .NET 2003 (aka

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

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

</td>

</tr>

<tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="69"

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

width="211">

Vista, Windows 7, Windows Server 2008

Windows XP<o:p>,

Windows 2003</o:p>

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="69"

width="289">

Microsoft

Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1<span

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

</td>

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

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

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

the Windows. </td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="43"

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

width="211"> MacOS version 10.2 and higher</td>

higher</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="43"

width="289"> gcc 3.3, gcc 4.01</td>

</tr>

<tr>

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

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

8</big></td>

</big></td>

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

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

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

style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span

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

style="color: rgb(153, 51, 153);">7.3-009 for OpenVMS

</td>

Alpha and above</big> </td>

</tr>

<tr>

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

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

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

style="color: rgb(0, 0, 0);">HP C++ V7.<span

color="RED">Solaris 9</big></td>

style="color: rgb(153, 51, 153);">2-021 on OpenVMS IA64 and

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

above</big> </td>

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

</td>

</tr>

<tr>

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

<td><big>HP C++ V<span

style="color: rgb(153, 51, 153);">7.3-009 or later required

for OpenVMS Alpha</big></td>

</tr>

<tr>

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

<td><big> HP OpenVMS 8.3 or later

style="color: rgb(0, 0, 0);">Solaris 8

IA64</big></td>

</big></td>

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

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

or later required on

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

OpenVMS IA64</big></td>

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

</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="vertical-align: top;"><big><font

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

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>

<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

Platform patches

The

<font

following is a list known of platform patches Pegasus requires.

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

patches Pegasus requires.

<font

<ol>

style="color: rgb(0, 0, 0);">RHAS

<li>

2.1 needs the update to fix Red Hat Bugzilla 98815.

RHAS

2.1

needs the update to fix Red Hat Bugzilla 98815.

</li>

<li>

RHEL 4.4

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

(Bugzilla 6232). This is fixed in RHEL 4.5

</li>

<li>

Red Hat and SUSE

Linux multiple versions - multithreaded client intermittently

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

248052)

</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can

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

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

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:

<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

The OpenPegasus Bugzilla database documents any defects found in

and  is available through the following link:  <a

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

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

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

database</a>.  Note that all changes  committed for this

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

release have been marked with the keyword 2.6.<span

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

style="color: rgb(153, 51, 153);">1_APPROVED

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

so that all changes for this release can be found with the following

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

bug search. Effective with the start of the Pegasus 2.6 work, all

subsequent versions.  Therefore, a search of the OpenPegasus

changes to the CVS tree were documented through bugs.  Thus bugs

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

were filed not only for bugs and their corresponding fixes but also as

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

part of the process of committing new code representing the work on

PEPs done for Pegasus 2.6.  Therefore, a search of the bugzilla

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

base for bugs with the tag 2.6.<span

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

style="color: rgb(153, 51, 153);">1_APPROVED will

release.

yield

- Changes for this release (bugs Tagged

all changes to the

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

Pegasus RELEASE_2_6-branch

Pegasus 2.12.0_APPROVED bug list.</a>

CVS branch since

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

Pegasus 2.6.0.

Control

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

- Changes for Pegasus 2.6.<span

The OpenPegasus project is controlled largely through the CVS

style="color: rgb(153, 51, 153);">1 point release (bugs Tagged <font

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

face="Courier New">2.6.1_APPROVED)

definition and review mechanism for new and modified Pegasus

functionality and for the definition and documentation of releases.

href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.6.1_APPROVED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Pegasus

The following documentation defines the characteristics of this Pegasus

2.6.1_APPROVED bug list</a>

release. The documents are available in the OpenPegasus CVS

repository.

<h4>2.6.1 bugs of special interest:

</h4>

<ul>

<li><a style="color: rgb(153, 51, 153);"

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

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

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

style="color: rgb(153, 51, 153);"> changed the way OpenPegasus loads

2.12.x

libraries (such as providers) in a POSIX environment. The dlopen() call

Release Status</a>) - A

was changed to include the RTLD_GLOBAL option for all POSIX platforms

section in the Pegasus wiki is used throughout the development of

except VMS.

this version as the control point for functionality that will go

</li>

into the release and points to all of the PEPs that represent the

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

OpenPegasus

Build and Configuration Options  for Selected Platforms -  <span

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

information was  released as a Pegasus PEP. Starting with

Pegasus 2.9.0 the information is located in the OpenPegasus CVS

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

<li> OpenPegasus External Interfaces -The

list of the OpenPegasus interfaces that are considered external

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

by the Steering Committee all subsequent releases of Pegasus MUST

continue to support these interfaces. Interfaces not explicitly

listed in this document, should be considered as internal and

subject to change.In previous Pegasus releases this information

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

information is integrated into the Pegasus repositoryas  <small

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

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

<li> OpenPegasus  SDK Packaging Definition - Defines

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

Starting with Pegasus release 2.11.0, this document is available

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

In previous Pegasus releases this document was made available as s

separate Pegasus PEP document rather than in the CVS repository.

</li>

<li> Pegasus  Runtime Packaging Definition - Defines

the recommended set of files for inclusion in this OpenPegasus

release. Starting with Pegasus release 2.11.0, this idocument

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

In previous releases this was made available as a seperate Pegasus

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

<li>Pegasus Release Notes -  PEP

364 - (This document is located

in the approved PEP repository and the OpenPegasus source tree

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

</ul>

<h2><a

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

name="Pegasus Release Control and Version Definition Documentation">Pegasus

The following documentation is available for the this Pegasus

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

release:

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 the

Pegasus 2.6 release. These PEPs are available as

href="http://www.openpegasus.org/pp/protected/documents.tpl?CALLER=index.tpl&gdc_docage=0&S=gdc_title&R=desc">OpenPegasus

Approved PEPs.</a>

For this 2.6.1 point release,

only

this document, the 2.6.1 Release Notes, was updated. All other

references should be back to the 2.6 release PEPs.

<ol>

<li> PEP 218 - OpenPegasus 2.6 Release Definition - This PEP

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>

<li> PEP 277 -  OpenPegasus 2.6 Build and Configuration

Options  for Selected

Platforms</li>

<li> PEP 278 OpenPegaus 2.6 External Interfaces - Lists the

public interfaces for clients and providers that are considered

external and therefore "frozen".

</li>

<li> PEP 279 - OpenPegasus 2.6 SDK Packaging Definition - Defines

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

<li>PEP 280 - Pegasus  2.6 Runtime Packaging Definition -

Defines the recommended set of files for inclusion in this OpenPegasus

release.</li>

<li>PEP 305 - Pegasus 2.6.1

Release

Notes (This document located in

the approved PEP repository and the OpenPegasus source tree root

directory)

</li>

<li>PEP 289  - Pegasus 2.6 readme.txt (Located in PEP

repository and also in the OpenPegasus

source

tree root directory).</li>

</ol>

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

The following documentation is available for the this Pegasus

release:

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

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

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

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

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

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

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

documentation - See the header files and the HTML  API

documentation - </li>

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

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

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

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

documentation.  In particular the Common/tests unit tests contain

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

extensive examples of the use of the Common APIs.</li>

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

use of the Common APIs.

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

Providers - Readme.html in the Pegasus Root Directory, API

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

which is available on the Pegasus web site.

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

Clients - API documentation and the documentation on the Pegasus

Clients - </li>

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

API documentation and the documentation on the Pegasus Technical

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

Workshop which is available on the Pegasus web site.

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

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

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

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

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

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

the OpenPegasus web site.  While these are the original design

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>

the design and implementation of these features.

</ul>

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

<span

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

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

work for additional information regarding copyright ownership. Each

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

contributor licenses this file to you under the OpenPegasus Open Source

style="color: black;">

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

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

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

width="100%">

copy of this software and associated documentation files (the

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

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

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

Open Group; VERITAS Software Corporation; Intel Corp.

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

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

Permission is hereby granted, free of charge, to any

the following conditions:

person obtaining a copy  of this software and associated

The above copyright notice and this permission notice shall be included

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

in all copies or substantial portions of the Software.

restriction, including without limitation the rights to use, copy,

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

modify, merge, publish, distribute, sublicense, and/or sell copies of

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

the Software, and to permit persons to whom the Software is furnished

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

to do so, subject to the following conditions:

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

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

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION

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

NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

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>

</div>

</body>

</html>

Legend:

Removed from v.1.10.2.1
changed lines
	Added in v.1.17.4.2

No CVS admin address has been configured