pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

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

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

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 963

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

</head>

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

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

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

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

<o:DocumentProperties>

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

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

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

<o:LastAuthor> </o:LastAuthor>

<o:DocumentProperties> <o:Author>IBM_User</o:Author> <o:LastAuthor> </o:LastAuthor> <o:Revision>4</o:Revision> <o:TotalTime>211</o:TotalTime> <o:Created>2004-04-05T14:13:00Z</o:Created> <o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>5026</o:Words> <o:Characters>28651</o:Characters> <o:Company>IBM</o:Company> <o:Lines>238</o:Lines> <o:Paragraphs>67</o:Paragraphs> <o:CharactersWithSpaces>33610</o:CharactersWithSpaces> <o:Version>10.4219</o:Version> </o:DocumentProperties></xml><![endif]--><!--[if gte mso 9]><xml>

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

<w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:Compatibility> <w:ApplyBreakingRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument></xml><![endif]-->

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

<span

Pegasus

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

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

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

PEP #: 364

PEP #: 359

Title: Release

Notes for OpenPegasus version 2.12.0

Notes for OpenPegasus version 2.11.0 and version 2.11.1

Created: 10

September 2012

Created: 23

March 2011

Authors: Karl

Schopmeyer

Status:  draft

Version History:

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

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

<o:p> </o:p>

<span

</td>

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

</td>

<o:p> </o:p>

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

</td>

height="27">

<span

<o:p> </o:p>

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

<o:p> </o:p>

height="27">

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

<span

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

</td>

</tr>

<span

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

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

</td>

<font

23 March 2011

size="2">10 September 2012

</td>

</td>

Karl Schopmeyer

<span

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

</td>

<font

Initial

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

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

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

</td>

</tr>

<tr>

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

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

2012

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

</td>

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

<td 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="padding: 0.75pt;" height="21" align="center">Karl

Schopmeyer

</td>

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

comments from first review

</td>

</tr>

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

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

style="color: black;">

Abstract: This document defines the release notes for the

Abstract: This document defines the release notes for the 2.12.0

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

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

summarize the characteristics of this release, point to other

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.

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

style="color: black;">

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

and is also available directly in the OpenPegasus source tree root

library as ReleaseNotes.htm

<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

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

of This Release</a></li>

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

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

Considerations</a></li>

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

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

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

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%20Bugs">OpenPegasus Bug Fixes and Changes for this Release

</a></li>

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

<h2>Availability

of this Release</h2>

NOTE: This document defines

the OpenPegasus 2.11.0 version release with comments added to define

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

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

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

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

OpenPegasus tries to execute only bug fixes for revision releases and

not include enhancements but in exceptional cases including 2.11.1 some

extensions are included (See the Functionality of this Release

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

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

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

9014. Note that in OpenPegasus ALL changes including enhancements are

defined as bugs and committed only when the APPROVED keyword is set so

that the list in the query above defines ALL changes between 2.11.0 and

2.11.1.

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 OpenPegasus

These can be

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

downloaded from the OpenPegasus Web

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

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

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

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

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

A 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 href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

page</a> for information) using the tags defined on the <a href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release

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

snapshots page</a>.</li>

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

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

<h2>OpenPegasus Functionality for This

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

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

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

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

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

WEB Page</a>

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

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

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

shows the

OpenPegasus 2.12.0 is a major release, extending the previous Pegasus

Pegasus users and developers the status of the various features found

release in selected areas as described in the Pegasus  PEP defining

in Pegasus

this release .

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

description of

NOTE: OpenPegasus releases are categorized as follows:

each feature.

<ul>

Pegasus 2.11.0

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

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

release includes major functionality change and  incompatible

areas as described in the Pegasus  PEP defining this release

behavior changes and/or incompatible public API changes,

.

</li>

The major areas of development for this release  were as

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

follows. Note that the bugs listed represent only those features

includes new functionality but maintains behavior and public API

incorporated in bugs without PEPS that are considered enhancements, not

compatibility,

all bugs incorporated in the release. For

</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 including both enhancements and bug

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

represent only those features incorporated in bugs without PEPS that are

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

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

<font

Table of Major

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

Changes for this Release

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

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

<tbody>

Line 1191

Line 1181

Version</th>

</tr>

<tr>

<td>Provider Lifecycle Indications

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

</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 align="left" width="75%">Provider Module Grouping</td>

</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 align="left" width="75%">SNMP V3 Trap Generation in Pegasus

<td>WSMan indication handling and subscription support

Indication Handler</td>

</td>

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

1.1</a>

</td>

</tr>

<tr>

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

8891</a>

</td>

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

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

5667</a>

</td>

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

and filter functions in CIMInstance class

</td>

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

</td>

Implementation, stage 2

</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="text-align: center;" width="7%">PEP 349

9013</a>

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

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

availability of the CIMOM by better isolation from faulty providers</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

<td>Add External SLP support to release builds

imlementing CIM_ElementConformsToProfile when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td>

<td>

</td>

</tr>

<tr>

</a>

<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

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

9118</a>

</a></td>

</td>

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

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

PEGASUS_USE_RELEASE_CONFIG_OPTIONS build option to have true/false

values

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

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

9172</a>

8806</a></td>

</td>

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

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

providers. This adds  new runtime configuration variable

</tr>

hostname and fullyQualifiedHostName. It is necessary to upgrade

<tr>

existing repositories using repupgrade utility when upgrading from

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

OpenPegasus less that 2.12.0 and reusing an existing repository.

8825</a></td>

</td>

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

<td>

</td>

</tr>

<tr>

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

8839</a></td>

<td>OOP Provider recovery enhancement</td>

</tr>

<tr>

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

8845</a></td>

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

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

</td>

</tr>

<tr>

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

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

9215</a>

</a> </td>

</td>

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

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

to include enumeration association filters</td>

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

</td>

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

cimcli

</td>

<td>

</td>

</tr>

<tr>

</a></td>

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

</tr><tr>

9227</a>

</td>

<td>Enhance cimsub for batches of subscription oriented operations

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

backward compatibility due to a new virtual function that was

introduced in Pegasus 2.11.0 (2.11.1 release)

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

The status of several components of Pegasus functionality change

status

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

that

have

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

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

release to this release</a> on the

Status WEB Page</a>.

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

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

WEB Page</a>.

OpenPegasus 2.12

Finally, a significant number of internal changes and corrections

</h3>

were made

Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable

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

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

section below

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

for more information.

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.

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

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

NOTE: This functionality was incorporated in OpenPegasus

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

2.7.0 but it

subsequent Release Notes

was felt that the information below was worth repeating in subsequent

IPv6 is short

Release

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

Notes

protocol designed by the IETF to replace the current version Internet

IPv6 is

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

short for "Internet

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

Protocol

PEP 291</a>.

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

The IPv6 support in OpenPegasus is controlled by the

to replace the current version Internet Protocol, IP Version 4

PEGASUS_ENABLE_IPV6 build variable. The default for this variable is

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

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

PEP

the IPv6 support.

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 following subsections provide

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

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

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

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

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

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

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

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

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

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

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

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

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

Listener components. For more information on IPv6 support for your

documentation for that platform.

specific platform, refer to the documentation for that platform.

All OpenPegasus externals that support either a hostname or an IP

All OpenPegasus externals that

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

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

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

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

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

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

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

address must be specified without brackets. For example, the

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

OpenPegasus osinfo client (which returns information about the OS

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

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

IPv6-configured network interface would be specified as:

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

specified as:

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

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

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

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

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

But the cimcli command, which

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

takes

delimited with brackets, for example:

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

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

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

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

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

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

or

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

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

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

</div>

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

For more information on

RFC

specifying

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

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

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

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

Modern Linux distributions already

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

contain IPv6-ready kernels, the

this module is not loaded automatically on startup.

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

Note: you shouldn't use

that this module is not loaded automatically on startup.

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

Note:

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

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

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

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

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

to use series 2.6.x now.

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

To check whether your current

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

running

short automated test looks like:

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

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

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

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

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

For more information on

For more information on enabling IPv6 in the Linux kernel and

enabling

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

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

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

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

Documentation Project's IPv6 HOWTO</a>.

Warning: There is currently an

Warning:

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

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

on RHEL5 and SLES10 systems. This problem is described in

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

bug 6586</a>

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

and

bug

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

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

bug 248052</a>,

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

and manifests itself as an intermittent IPv6 socket failure. You

may be significantly impacted in these environments.

should be aware

that OpenPegasus with IPv6 enabled may be significantly impacted in

these

environments.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6 implementations for Windows Server

Microsoft provides supported IPv6

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

implementations for Windows Server

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

2003, Windows XP with Service Pack 1 (SP1), Windows XP 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

tool to install, uninstall, and

example:

query

your IPv6 configuration. For example:

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

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

color="#000000">ipv6 install

ipv6 if</big></div>

Windows Vista and Windows Server 2008 support an integrated IPv4 and

Windows Vista

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

and Windows Server 2008 support an integrated

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

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

Windows Server 2008.

Note that the OpenPegasus IPv6 support has not yet been tested

on Windows Vista or Windows Server 2008.

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

For more information on

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

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

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

the document

Questions</a>.

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

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

<h4>Testing  OpenPegasus IPv6 support</h4>

<h4>Testing your OpenPegasus IPv6

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

support</h4>

IndicationStressTest test clients were modified to run tests using the

As part of the OpenPegasus

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

automated tests, the TestClient, g11ntest, and IndicationStressTest

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

(::1) if PEGASUS_ENABLE_IPV6=true.

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

You can also perform manual

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

tests

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

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 standard http port of 5988:

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

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

Support for forward-compatibility is a fundamental design principle for

Support for forward-compatibility is a fundamental design principle

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

for the

OpenPegasus providers or clients, using only the externally defined

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

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

OpenPegasus

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

Providers or Clients, using only the externally defined OpenPegasus

non-compliance with a standard that significantly affects

interface,

interoperability) that may require the community to make potentially

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

incompatible changes. The following table contains a list of

However, there

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

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

or clients when upgrading to this OpenPegasus release.

that

significantly affects interoperability) that may require the Community

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

to make

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

potentially incompatible changes. The following table contains a list

of defect

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

Clients when

upgrading to this OpenPegasus release.

<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">The requirement for providers (CMPI and C++) to

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

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

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

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

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

on performance the CIMInstance::filter() and

protocol adapter level. To avoid a negative impact on performance

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

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

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

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

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

behavior for provider relying in some unknown way on the instance

allow users to actually filter properties from an instance, new

being filtered through these functions. To allow users to actually

function CIMInstance::filterInstance() will actually filter properties

filter properties from an instance, new function

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

CIMInstance::filterInstance() will actually filter properties from

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

versions of Pegasus.</td>

</tr>

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

<td>

9369</a>

</td>

<td>

</td>

</tr>

<td>

</td>

<td>

</td>

</tr>

<td>

</td>

<td>

</td>

</tr>

<td>

</td>

<td>

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

<h2>OpenPegasus Relationship to

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

CIM/WBEM Standards</h2>

specifications The following table defines the level of the DMTF

Pegasus was designed and implemented to comply with the DMTF

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

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>

Line 1660

Line 1546

</tr>

<tr>

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

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

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

</tr>

<tr>

<td>DSP0226 - Web Services for Management

</td>

<td>Version 1.1.1

</td>

</tr>

<tr>

<td>DSP0227 - WS-Management CIM Binding Specification

</td>

<td>Version 1.2.0

</td>

</tr>

<tr>

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

<td>Version 1.1.0

</td>

</tr>

</tbody>

</table>

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

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

Profiles Supported</h2>

Exceptions to

Today OpenPegasus includes support for several DMTF profiles including

DMTF Specifications</a></h2>

the ones defined below:

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>DMTF ProfileRegistration Version 1.0.0</li>

<li>Provider Registration - Pegasus supports registration

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

through a set of Pegasus Provider registration classes rather than

SNIA SMI Indication profile it also supports this profile. This

support the DMTF defined Provider Qualifier. Pegasus will not support

profile is enabled by compiling OpenPegasus with the buld variable

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

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

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

Pegasus.</li>

<li>Indications -Today Pegasus supports process

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

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

For more

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

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

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

size="2">.</li>

<li>

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

stated specifically that the client should NOT depend on the

includeQualifiers parameter of the CIM/XML instance operations

returning qualifiers.  Some CIM Client implementations expect

returning qualifiers. 

instances returned from the CIM Server to include the qualifiers

Some CIM Client implementations expect instances

defined in the class definition (such as KEY qualifiers on

returned

properties).   Pegasus today expects the

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

provider to complete the qualifiers on instances in accordance with

definition (such as KEY qualifiers on properties).   Pegasus

the specification and generally the interpretation is that Pegasus

today expects the provider to complete the qualifiers on instances in

applies class level qualifiers when the includeInstance parameter is

accordance with the specification and generally the interpretation is

supplied on instance operations.  However, Pegasus today is

that Pegasus applies class level qualifiers when the includeInstance

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

parameter is supplied on instance operations.  However, Pegasus

depend on Pegasus accurately honoring the includeQualifier parameter

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

for instance operations.  In the future it is expected that

should NOT depend on Pegasus accurately honoring the includeQualifier

Pegasus will deprecate the use of qualifiers on instance operations

parameter for instance operations.  In the future it is expected

completely.  When Pegasus uses object normalization, the

that Pegasus will deprecate the use of qualifiers on instance

normalizer does apply qualifiers to returned instances if the

operations completely.  When Pegasus uses object normalization,

the normalizer does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.

</li>

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

<li>LocalOnly option on instance

version of Specification for CIM Operations over HTTP, the definition

Operations - With the 1.1 version of Specification for CIM

of the LocalOnly parameter for the GetInstance and Enumerate Instances

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

operations was modified. This change was incorrect, resulted in

GetInstance and Enumerate Instances operations was modified. This

reduced functionality and introduced a number of backward

change

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

was incorrect, resulted in reduced functionality and introduced a

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

number of backward compatibility issues. As a result of issues

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

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

properties returned. See Appendix C of this specification for more

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

information.</li>

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

specification for more information.</li>

<li>

MultiRequest Operations - Pegasus does not

MultiRequest Operations - Pegasus

support the DMTF defined MultiRequest Operation option.

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOF Compiler namespace pragma - The

MOF Compiler namespace pragma - 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

<li>CIMOperation Trailer - Pegasus implements

the DSP0200 1.2.0 preliminary spec. including the operation trailer

chunking

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

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

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

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

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

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

feels cannot be incorporated into the code until a major version

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

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

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

<li>modifyInstance operation behavior

<li>modifyInstance operation

in the Pegasus repository does not match the DMTF specification.

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

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

all properties rather than just the properties supplied with the

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

for more information.</li>

<li>OpenPegasus Interop Namespace - The default interop namespace

<li>Covered Properties (multiple properties with the same name but different class origin)

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

- The DMTF Spec DSP0004 now defines the requirement for covered

OpenPegasus prior to 2.12.0 this could be changed during build by

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

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 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 base including a maintainer for the platform that will be willing

code base

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

including a maintainer for the platform that will be willing to

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

regularly

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

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

maintenance, correct operation of  Pegasus cannot be assured. 

changed. 

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

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

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

a group

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

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

for a list of relevant defects that affect their platform.  

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

below. 

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

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

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

regular

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

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

second table.

platforms

Actively Supported Platforms (Nightly Tests Reported for this release)

which have been ported but do not have test results that are current at

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

the time

cellspacing="1">

of the release are reported in the second table.

Actively Supported Platforms (Nightly Tests Reported for this

release)

<tbody>

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

height="26">

Platform and

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

</td>

height="26">

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

Compilers<span

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

</td>

</tr>

Line 1860

Line 1695

PA_RISC and Itanium</o:p>

</td>

HP aC++

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

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

</td>

</tr>

Linux

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

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

</td>

gcc<span

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

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

</td>

</tr>

zLinux<span

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

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

</td>

gcc<span

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

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

</td>

</tr>

Line 1889

Line 1719

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

</td>

gcc<span

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

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

</td>

</tr>

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

<td style="padding: 0.75pt;"> Linux IA-32</td>

IA-32</td>

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

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

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

size="3">gcc<font

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

is considered experimental and is not part of the nightly

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

</tr>

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

</td>

gcc<span

gcc

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

(versions 3.xx, 4.xx)

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

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

Version 1.7 and up</td>

z/OS Version 1.7 and up</td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this release (No

Platforms not Actively supported for this release

(No

current Nightly Build Test Results

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

cellspacing="1">

<tbody>

height="26">

Platform and

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

</td>

height="26">

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

Compilers<span

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

</td>

</tr>

<tr>

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

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

Vista, Windows 7, Windows Server 2008

</td>

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

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

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

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

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

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

the Windows. </td>

</tr>

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

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

higher</td>

and higher</td>

</tr>

<tr>

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

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

8</big></td>

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

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

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

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

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

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

</td>

</tr>

<tr>

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

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

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

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

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

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

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

</td>

</tr>

<tr>

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

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

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

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

OpenVMS

for OpenVMS Alpha</big></td>

Alpha</big></td>

</tr>

<tr>

<td><big> HP OpenVMS 8.3 or later

<td><big> HP OpenVMS 8.3 or

IA64</big></td>

later IA64</big></td>

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

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

or later required on

OpenVMS IA64</big></td>

</tr>

<tr>

Windows 2000

</td>

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

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

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

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

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

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

regularly tested.</td>

tested.</td>

</tr>

<tr>

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

</td>

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

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

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

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

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

</tr>

<tr>

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

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

IX86)</big></td>

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

</tr>

</tbody>

</table>

Platform patches

Platform patches

The

following is a list known of platform patches Pegasus requires.

The following is a list known of platform

patches Pegasus requires.

<ol>

<li>

RHAS

2.1

2.1 needs the update to fix Red Hat Bugzilla 98815.

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

multithreading bug in

(Bugzilla 6232). This is fixed in RHEL 4.5

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

Linux multiple versions -

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

multithreaded client intermittently fails connecting to IPv6 (Pegasus

248052)

Bugzilla

6586) (Red Hat bug 248052)

</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can be

Further information regarding Pegasus support on IBM platforms can

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>

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

Further information regarding Pegasus support on HP platforms can

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>

found at:

The OpenPegasus Bugzilla database documents any defects found in

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

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

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

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

</a></h2>

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

The Pegasus bugzilla database documents any defects found in Pegasus

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

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

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

database</a>.

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

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

subsequent versions.  Therefore, a search of the OpenPegasus

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

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

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 and all subsequent

versions.  Therefore, a search of

the Open Pegasus 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>,

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

2.6.1_APPROVED</a>,

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

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

release.

etc) will yield all changes to

- Changes for this release (bugs Tagged

the Pegasus CVS tree for that Pegasus release.

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>

     - Changes for this release (bugs Tagged

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

Pegasus 2.11.0_APPROVED bug list.</a>

     - (2.11. 1) Changes between the 2.11.0 release

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

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

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

Control

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

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

The Pegasus project is controlled largely through the CVS repository

The OpenPegasus project is controlled largely through the CVS

and a set of documents

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

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

definition and review mechanism for new and modified Pegasus

and

functionality and for the definition and documentation of releases.

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.

repository.

<ul>

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

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

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

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

2.12.x

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

Release Status</a>) - A

section in the Pegasus wiki is used

section in the Pegasus wiki is used throughout the development of

throughout the development of this version as the control point for

this version as the control point for functionality that will go

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

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

PEPs that represent the Pegasus  functionality changes for this

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

version of Pegasus. </li>

OpenPegasus

Build and Configuration Options  for Selected Platforms -  <span

Build and Configuration

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

Options  for Selected

information was  released as a Pegasus PEP. Starting with

Platforms -  In previous

Pegasus 2.9.0 the information is located in the OpenPegasus CVS

versions of Pegasus this information was  released as a Pegasus

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

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

<li> OpenPegasus External Interfaces -The

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

list of the OpenPegasus interfaces that are considered external

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

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

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

by the Steering Committee all subsequent releases of Pegasus MUST

exception is explicitly approved by the Steering Committee all

continue to support these interfaces. Interfaces not explicitly

subsequent releases of Pegasus MUST continue to support these

listed in this document, should be considered as internal and

interfaces. Interfaces not explicitly listed in this document, should

subject to change.In previous Pegasus releases this information

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

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

releases this information was available as a separate PEP. Starting

information is integrated into the Pegasus repositoryas  <small

with Pegasus 2.9.0 this information is integrated into the Pegasus

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

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

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

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

inclusion in the OpenPegasus

<li> OpenPegasus  SDK Packaging Definition - Defines

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

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

previous Pegasus releases this document was made available as s

separate Pegasus PEP document rather than in the CVS repository.

</li>

</li>

<li> Pegasus  Runtime Packaging Definition - Defines

<li> Pegasus  Runtime Packaging Definition

the recommended set of files for inclusion in this OpenPegasus

- Defines the recommended set

release. Starting with Pegasus release 2.11.0, this idocument

of files for inclusion in this OpenPegasus

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

release. Starting with Pegasus release 2.11.0, this idocument contained

In previous releases this was made available as a seperate Pegasus

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

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

In previous

releases this was made available as a seperate Pegasus PEP document

<li>Pegasus Release Notes -  PEP

rather than in the CVS repository.  </li>

364 - (This document is located

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

in the approved PEP repository and the OpenPegasus source tree

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

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

</ul>

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

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

A

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

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

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

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

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

documentation - </li>

documentation - </li>

See the header files and the HTML  API

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

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

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

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

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

documentation.  In particular the Common/tests unit tests contain

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

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

use of the Common APIs.

Providers - </li>

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

Readme.html in the Pegasus source tree 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.

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

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

Clients - </li>

Clients - </li>

API documentation and the documentation on the Pegasus

API documentation and the documentation on the Pegasus Technical

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

Workshop which is available on the Pegasus web site.

The

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

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

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

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

OpenPegasus web site.  While these are the original design

the OpenPegasus web site.  While these are the original design

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

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

the design and implementation of these features.

</ul>

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

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

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

license

work for additional information regarding copyright ownership. Each

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with

contributor licenses this file to you under the OpenPegasus Open Source

this work for additional information regarding copyright ownership.

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

Each contributor licenses this file to you under the OpenPegasus Open

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

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

"Software"),

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

to deal in the Software without restriction, including without

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

limitation

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

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

the following conditions:

sublicense,

The above copyright notice and this permission notice shall be included

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

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

Line 2163

Line 1998

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

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

</div>

</body>

</html>

</body></html>

Legend:

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

No CVS admin address has been configured