pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

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

version 1.18, 2011/03/29 13:23:06

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 965

Line 962

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

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

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

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

style="color: black;">

OpenPegasus Enhancement

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

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

width="100%"></div>

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

align="center">Pegasus

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

<span

style="color: black;">

PEP #: 366

PEP #: 359

Title: Release

Notes for OpenPegasus version 2.13.0

Notes for OpenPegasus version 2.11.0

Created: 18 July

Created: 23

2013

March 2011

Authors: Karl

Schopmeyer

Status:  draft

Version History:

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

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

<tbody>

<td

<o:p> </o:p>

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

<o:p> </o:p>

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

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>

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

<span

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

</td>

11 July 2013

<font

size="2">23 March 2011

</td>

Karl Schopmeyer

<span

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

</td>

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

<span

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

Submission <o:p><font

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

</td>

</tr>

<tr>

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

</td>

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

</td>

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

Schopmeyer

</td>

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

before review

</td>

</tr>

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

</td>

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

</td>

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

Schopmeyer

</td>

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

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

Functionality"

</td>

</tr>

<tr>

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

</td>

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

</td>

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

</td>

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

</td>

</tr>

Line 1061

Line 1095

</tr>

</tbody>

</table>

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

style="color: black;">

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

Abstract: This document defines the release notes for the 2.13.0

width="100%"></div>

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

Abstract: This document defines the release notes for the

summarize the characteristics of this release, point to other

2.11.0 release of the OpenPegasus CIM Server. The purpose of this PEP

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

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

width="100%"></div>

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

<ol>

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

Release</a></li>

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

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

of This Release</a></li>

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

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

Considerations</a></li>

<li><a href="#Notes_on_Specific_OpenPegasus">Notes on Specific

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

OpenPegasus Functionality</a>

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

</li>

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

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

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

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

with DMTF Specifications</a></li>

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

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

<li> <a

Release

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

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

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

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

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

Documentation</a></li>

</ol>

<h2>Availability of this Release</h2>

<h2>Availability

This release is available in a number of forms including:

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

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

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

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

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

distributions and versions.</li>

A source RPM is  available on the

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

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

release and subsequent snapshots that are made available in the

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

Pegasus CVS are defined on the OpenPegasus CVS repository web page

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

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

release and

CVS

subsequent snapshots that are made available in the Pegasus CVS are

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

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

snapshots

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

page</a> and the <a title="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus">OpenPegasus

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

WIKI Release Status 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> and the <a title="OpenPegasus WIKI" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">OpenPegasus

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

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

Pegasus source

of the Pegasus source tree.

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>

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

Pegasus overall status by release is defined by  a

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

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

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

WEB Page</a>

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

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

shows the

OpenPegasus 2.13.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.12.0 2.13.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>

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

<li>3rd number changes (2.13.0 to 2.13.1) - Revision(also called point

<font

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

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

</ul>

Changes for this Release

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

ALL changes for each release are documented in the

bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="82%">

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.13.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.13.0_APPROVED">

Pegasus 2.13.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.13.0_APPROVED&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_severity&type0-0-0=equals&value0-0-0=enhancement">link

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

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

corresponding Bugzilla tags for each revisions (ex 2.13.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:

Table of Major

Changes for this Release. Please review  Bugzilla 2.13.0

Enhancements and approved(above) for a complete list

<tbody>

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

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

Version</th>

</tr>

<tr>

<td>Fixed issues where Pegasus compiler converted Schema Qualifer

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

decl to CLASS</td>

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

<td>

href="http://www.openpegasus.org/pp/uploads/40/23224/PEP_318_32bit_providers_in_64bit_OpenPegasusVer10.htm">1.0</a></td>

</td>

</tr>

<tr>

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

</td>

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

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

<td>

</td>

</tr>

<tr>

</td>

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

primarily a development and debug extension.

</td>

<td>

</td>

</tr>

<tr>

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

<td>

</td>

</tr>

<tr>

</td>

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

note below)

</td>

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

304, Version 1.6</a>

</td>

</tr>

<tr>

</td>

<td>Support clang compiler in Production Build

</td>

<td>

</td>

</tr>

<tr>

</td>

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

and sets runtime parameters

</td>

<td>

</td>

</tr>

<tr>

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

</a>and others

</td>

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

unused variable warnings and set compiler defaults to make these

warnings a build error.

</td>

</td>

</tr>

<tr>

</td>

<td>Clean up  issues with building with static libraries

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Reduce static code size (Note: several bug fixes contributed to

this reduction) (see 9555, 9560, 9557, 9558, 9580)

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Log rotation configuration variable to set max file size (see

below for more info)

</td>

<td>

</td>

</tr>

</td>

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

<td align="left" width="75%">Remove compile option

<td width="128"> <a

PEGASUS_CLIENT_TRACE_ENABLE (now always compiles) </td>

href="http://www.openpegasus.org/pp/uploads/40/22030/PEP356_ProviderModuleGrouping.htm">2.2</a>

</td>

</tr>

<tr>

</td>

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

<td>Fix issues requiring restart of cimserver  if indication

Indication Handler</td>

provider reregistered

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

</td>

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

<td>

</td>

</tr>

<tr>

</td>

<td>Initial configure script for OpenPegasus (Experimental, see below)

</td>

<td>

</td>

</tr>

<tr>

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

</td>

<td>Update env_var_LINUX.status and env_var_HPUX.status to change

some build defaults

</td>

</td>

</tr>

<tr>

<td>Modify environment variable definition that controls client

tracing (See below)</td>

<td>

</td>

</tr>

<tr>

</td>

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

mode for WSMAN indications

</td>

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

</td>

</tr>

<tr>

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

<td>

</td>

</tr>

<tr>

</td>

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

operations(see below for more comments)

</td>

<td>

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

Implementation, stage 2

</td>

<td width="128"><a

href="http://www.openpegasus.org/pp/uploads/40/22529/PEP324-DMTF_Indications_Profile_stage2_Ver11.html">1.1</a></td>

</tr>

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

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

</td>

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

OpenSLP 2.0 (See OpenSLP 2.0 issues documented below)

</td>

</td>

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

style="">Improve the

availability of the CIMOM by better isolation from faulty providers</td>

<td width="128"> <a

href="http://www.openpegasus.org/pp/uploads/40/22386/PEP_349_-_Improve_the_availability_of_the_CIMOM_by_better_isolation_from_faulty_providers.htm">0.5</a></td>

</tr>

<tr>

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

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

</td>

<td>Support for ARM 64 CPU by adding platform definition

<td>Add External SLP support to release builds

(Experimental because of limited testing)

</td>

</td>

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

href="http://www.openpegasus.org/pp/uploads/40/21277/PEP350_MultiCIMOM.htm">

</a></td>

</tr>

<tr>

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

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

</a></td>

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

PEGASUS_USE_RELEASE_CONFIG_OPTIONS build option to have true/false

values

</td>

<td>Fix connection between indication handlers and IndicationService

so that OnFatalErrorPolicy works

</td>

<td>

</td>

</tr>

<tr>

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

</td>

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

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

8806</a></td>

</td>

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

<td>

</td>

</tr>

<tr>

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

8825</a></td>

<td>Option to specify multiple provider dirs for release builds</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 style="text-align: center;" width="7%"> <a

</td>

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

<td>Allow remote update of expired user password for PAM session

</a> </td>

based authentication

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

</td>

style="text-decoration: underline;">Enhance WSMan Server Adpater 

<td>

to include enumeration association filters</td>

</td>

</tr>

<tr>

</td>

<td>Role-based authorization extension for CMPI providers

<td width="128"><a

</td>

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

<td>

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

WEB Page</a>.

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

Finally, a significant number of internal changes and corrections

OpenPegasus Functionality Changes</h2>

were made

This section documents specific issues that the OpenPegasus team feels are

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

important to OpenPegasus users with the current release (and possibly

section below

older releases).

for more information.

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

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

NOTE: This functionality was incorporated in OpenPegasus

2.13.0)(bug 9550)</h3>

2.7.0 but it

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

was felt that the information below was worth repeating in subsequent

Release

   * traceFileSizeKBytes -  Defines the size of the

Notes

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

IPv6 is

exceeds the specified size.

short for "Internet

   * numberOfTraceFiles - Specifies the number of the tracefiles

Protocol

for rolling where the default is 3.

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

to replace the current version Internet Protocol, IP Version 4

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

("IPv4"). IPv6 Support for OpenPegasus is documented in <a

</h3>

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

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

PEP

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

291</a>.

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

The IPv6 support in OpenPegasus is

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

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for

significant performance improvements.

this

variable is "true"; setting this to

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

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

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

While testing OpenPegasus with OpenSLP 2.0 the OpenPegasus team found two

issues with this version of OpenSLP.  The patches documented below

allow this version of OpenSLP to work with OpenPegasus

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

a BUFFER_OVERFLOW exception occurs.  This is because UDP cannot

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

according to the specification, OpenSLP should automatically switch to

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

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

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

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

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

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

Effective with the release of OpenPegasus  2.13 the "interop"

namespace support for existing or

older repositories which used

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

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

the repository from "root/PG_InterOp" to

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

9414</a> (PEP304) for

details.

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

to be

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

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

"root/PG_InterOp"

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

"interop".

Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable to

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

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

involving editing one file and rebuilding OpenPegasus was defined as a

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

wiki faq</a>s.

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

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

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

become an issue. Support for forward-compatibility is a fundamental design

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

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

defined OpenPegasus interface, to continue to work with each version

upgrade of OpenPegasus.

Effective OpenPegasus 2.12.0 a new build variable was 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.  This is the logical

approach for implementations starting a new repository.

In order to supexport PEGASUS_CLIENT_TRACE=keyword:keywordport users with

existing repositories, in 2.13.0,  migration of existing repositories

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

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

for the interop namespace "root/PG_InterOp" to 

the prefered name "interop".

NOTE: If the interop namespace

name is redefined with PEGASUS_INTEROP_NAMESPACE clients using the

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

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

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

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

<h3>Configure Script to Control OpenPegasus Builds (OpenPegasus

2.13.0)(Bug 9592)</h3>

OpenPegasus is moving from the use of environment variables to a configure

script to control build.  This is both to make it easier to define

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

standard build environment.  However, because OpenPegasus must build

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

configuration tool set, this is an OpenPegasus defined configure

script.  The first very experimental version is part of OpenPegasu

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

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

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

environment variable with options in the pegasus/configure script where

those options are comatible with the Linux standard for defining configure

options and those options control the entire build process including placement

of output and choice of build options.

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

OpenPegasus has

long contained a hidden build controlled function to allow tracing at

the client through an environment variable

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

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

slightly changed

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

environment variable was:

<pre class="bz_comment_text" id="comment_text_1">export PEGASUS_CLIENT_TRACE=keyword:keyword where the keyword was "con" | "log" | "both" This was changed to: keyword:keyword separately define Client input and output keyword: Client Input only :keyword Client Output Only keyword Client Input and output defined by keyword</pre>

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

<pre> export PEGASUS_CLIENT_TRACE=con</pre>

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

2.7.0)</h3>

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but

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

Release Notes

IPv6 Support for OpenPegasus is documented in

PEP 291</a>.

The IPv6 support in OpenPegasus is controlled by the PEGASUS_ENABLE_IPV6

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

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

The following subsections provide some information on IPv6 support for the

The following subsections provide

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

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

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

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

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

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

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

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

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

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

CIM Server and Listener components. For more information on IPv6 support

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

for your specific platform, refer to the documentation for that platform.

Listener components. For more information on IPv6 support for your

specific platform, refer to the documentation for that platform.

All OpenPegasus externals that support eitcompilerher a hostname or an IP

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

All OpenPegasus externals that

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

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

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

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

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

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

information about the OS running on a host system) takes separate host and

address must be specified without brackets. For example, the

port options. In this case a host with an IPv6-configured network

OpenPegasus osinfo client (which returns information about the OS

interface would be specified as:

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

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

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>osinfo -h 3ffe:1:2:1 -p 5988</big></div>

specified as:

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

<div

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

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

delimited with brackets, for example:

color="#000000">osinfo -h

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

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

But the cimcli command, which

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

takes

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

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

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

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

or

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

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

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

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

</div>

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

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 this

contain IPv6-ready kernels, the

module is not loaded automatically on startup.

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

that this module is not loaded automatically on startup.

Note: you shouldn't use

Note:

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

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

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

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

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

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

to use series 2.6.x now.

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

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

To check whether your current

short automated test looks like:

running

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

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

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

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

<div

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

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

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

color="#000000">test -f

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

For more information on

enabling

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

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

Documentation Project's IPv6 HOWTO</a>.

Warning: There is currently an

Warning:

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

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

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 6586</a> and <a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat

bug 6586</a>

bug

and

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

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

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

bug 248052</a>,

be significantly impacted in these environments.

and manifests itself as an intermittent IPv6 socket failure. You

should be aware

that OpenPegasus with IPv6 enabled may be significantly impacted in

these

environments.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6

Microsoft provides supported IPv6 implementations for Windows Server 2003,

implementations for Windows Server

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

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

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

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

On Windows XP, you can use the ipv6.exe

tool to install, uninstall, and 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>ipv6 install

<div

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

color="#000000">ipv6 install

ipv6 if</big></div>

Windows Vista

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

and Windows Server 2008 support an integrated

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

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

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

Note that the OpenPegasus IPv6 support has not yet been tested

Windows Server 2008.

on Windows Vista or Windows Server 2008.

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

For more information on

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

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

the document

<h4>Testing  OpenPegasus IPv6 support</h4>

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

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

color="#000000">IPv6

IndicationStressTest test clients were modified to run tests using the

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

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

<h4>Testing your OpenPegasus IPv6

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

support</h4>

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

As part of the OpenPegasus

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

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 IPv6-configured network interface.

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

running on the WBEM standard http port of 5988:

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

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

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

Considerations</a></h2>

Support for forward-compatibility is a fundamental design principle

Support for forward-compatibility is a fundamental design principle for

for the

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

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

OpenPegasus providers or clients, using only the externally defined

OpenPegasus

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

Providers or Clients, using only the externally defined OpenPegasus

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

interface,

non-compliance with a standard that significantly affects

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

interoperability) that may require the community to make potentially

However, there

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

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

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

that

upgrading to this OpenPegasus release.

significantly affects interoperability) that may require the Community

to make

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.

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

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

allow users to actually filter properties from an instance, new

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

function CIMInstance::filterInstance() will actually filter properties

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

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

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

versions of Pegasus.</td>

CIMServer will do the filtering but allows the provider to prefilter

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

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

</td>

</tr>

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

9369</a>

</td>

</tr>

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

fixed in OpenPegasus 2.13.0. Reregistering of an

indication provider requires that the  cimserver be restarted

to send the enableIndication request to the providers. This issue

</tr>

has existed starting with OpenPegasus 2.10 to  version 2.12.

If the cimserver is not restarted the indication will not be

enabled for the reregistered provider. </td>

</tr>

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

Line 1555

</tr>

<tr>

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

<td width="33%">2.36.0 Final ( default build Schema) </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/SNIA SMI

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

Profiles Supported</h2>

Exceptions to

DMTF Specifications</a></h2>

Today OpenPegasus includes support for several DMTF profiles including:

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 DSP 1033, Version 1.0.0</li>

<li>Provider Registration - Pegasus supports registration

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

provider registration.  This is not a deviation from the

</li>

specifications but is a different method of registration than many CIM

<li>SNIA Profile Registration 1.0.0

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

</li>

<li>Indications -Today Pegasus supports process

<li>SNIA Server 1.1.0 & 1.2.0

indications and lifecycle indications when defined specifically by

</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 really a deviation from the specifications since there is no

specification or profile for provider registration today but is a

different method of registration than many CIM Servers and means that

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

<li>Lifecycle Indications -Today Pegasus supports process

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

For more

color="#ff0000">  For

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

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

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

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

<li> IncludeQualifiers

size="2">.</li>

option

<li>

on Instance Operations

<font

- The DMTF specifications have deprecated the use of qualifiers on

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

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

option on Instance Operations

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

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

complete the qualifiers on instances in accordance with the

definition (such as KEY qualifiers on properties).   Pegasus

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,

includeQualifiers operation parameter is set.</li>

the normalizer does apply qualifiers to returned instances if the

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

includeQualifiers operation parameter is set.

version of Specification for CIM Operations over HTTP, the definition

of the LocalOnly parameter for the GetInstance and Enumerate Instances

operations was modified. This change was incorrect, resulted in

reduced functionality and introduced a number of backward

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

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

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

properties returned. See Appendix C of this specification for more

information.</li>

<li>MultiRequest CIM/XML Option

-  Pegasus does not support the DMTF defined MultiRequest

Operation option (See DSP0200).

</li>

<li>MOF Namespace Pragma -The

<li>LocalOnly option on instance

Pegasus compiler does not support the namespace pragma defined in DSP

Operations - With the 1.1 version of Specification for CIM

0004. Namespaces for the OpenPegasus repository are defined through

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

arguments for the MOF Compiler

GetInstance and Enumerate Instances operations was modified. This

change

was incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

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

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

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

specification for more information.</li>

<li>

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>CIMOperation Trailer - Pegasus implements chunking based on

<li>

the DSP0200 1.2.0 preliminary spec. including the operation trailer

MOF Compiler namespace pragma - The

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

Pegasus compiler does not support the namespace pragma.

</li>

<li>CIMOperation Trailer - Pegasus implements

chunking

based on the DSP0200 1.2.0 preliminary spec. including the operation

trailer defined in that specification Refer to bug <a

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

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

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

is used Pegasus is returning a noncompliant response to enumerate type

requests. </li>

<li>Whitespace in XML value Element

- Pegasus trims the leading and trailing whitespace from XML value

elements that are of the Type String.  This behavior is

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>

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

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". Effective with OpenPegasus 2.13.0 the reupgrade utility has been extended to allow existing repositories to be converted from the use of "root/PG_Interop" to "interop" (See discussion above).  The default in the CVS source code is still "root/PG_InterOp".

</li>

<li>OpenPegasus WSMAN protocol on windows does not handle NaN, INF,

or -INFHowever, t (bug  <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>)

- If requests or responses include properties or parameters with

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

states NaN, INF, or -INF on a Windows platform, the input is not

accepted because these special strings are not understood by the

decoder on Windows.</li>

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

Real64 property and Parameter types for the CIM/XML protocol -

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

Today the DMTF Specification DSP0201 allows only numeric information

in the format definition for this type and does not all the special

strings Nan, etc. However, OpenPegasus actually outputs the special

strings if  that is what is defined in the internal values. 

OpenPegasus does not allow these special Strings on input however,</li>

<li>OpenPegasus does not handle covered properties - (bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">3571</a>)

Covered properties (properties which have the same name in a

superclass and subclass without overridding the property in the

superclass) are not allowed in OpenPegasus. While the requirement for

this functionality was added to DSP0004 subsequent to version 2.4, the

general agreement is that the requirement itself is not supportable

and particularly not with the existing OpenPegasus APIs. 

Further, the requirement is expected to be removed in the future (i.e

CIM 3.0).

</li>

</ol>

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

<h2>OpenPegasus <a

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 to

code base

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

including a maintainer for the platform that will be willing to

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

regularly

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

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

operation of  Pegasus cannot be assured.  In all cases,

changed. 

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

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

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

a group

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

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

relevant defects that affect their platform.   The platforms

Pegasus

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

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

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

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 sofr which testing is done on a

regular

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

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

platforms

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

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

the time

Actively Supported Platforms (Nightly Tests Reported for this release)

of the release are reported in the second table.

Actively Supported Platforms (Nightly Tests Reported for this

release)

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

cellpadding="0" cellspacing="1">

<tbody>

<td

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

height="26">

Platform and

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

</td>

<td

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

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

height="26">

Compilers<span

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

</td>

</tr>

Line 1928

Line 1713

PA_RISC and Itanium</o:p>

</td>

HP aC++

HP <span

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

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

</td>

</tr>

Linux

<span

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

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

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

</td>

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

<span

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

</td>

</tr>

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

<span

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

</td>

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

<span

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

</td>

</tr>

Line 1954

Line 1743

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

</td>

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

<span

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

</td>

</tr>

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

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

IA-32</td>

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

<td style="padding: 0.75pt;"> gcc (versions 3.xx, 4.7) clang(The clang compiler usage

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

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

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

style="color: black;">

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

</tr>

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

</td>

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

<span

style="color: black;">gcc

(versions 3.xx, 4.xx)

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

current Nightly Build Test Results)

(No

current Nightly Build Test Results

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

cellpadding="0" cellspacing="1">

<tbody>

<td

style="padding: 0.75pt; background: rgb(0, 255, 255) 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>

<td

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

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

height="26">

Compilers<span

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

</td>

</tr>

<tr>

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

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

Vista, Windows 7, Windows Server 2008 </td>

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

</td>

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

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

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

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

the Windows. </td>

Ver. 6 no longer being regular tested. </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><span

8</big></td>

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

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

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

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

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

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

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

</td>

</tr>

<tr>

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

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

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

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

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

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

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

</td>

</tr>

<tr>

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

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

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

for OpenVMS Alpha</big></td>

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

OpenVMS

Alpha</big></td>

</tr>

<tr>

<td><big> HP OpenVMS 8.3 or later

<td><big> HP OpenVMS 8.3 or

IA64</big></td>

later IA64</big></td>

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

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

or later required on

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

OpenVMS IA64</big></td>

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

</tr>

<tr>

Windows 2000

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

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

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

</td>

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

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

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

</tr>

<tr>

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

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

IX86)</big></td>

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

</tr>

</tbody>

</table>

<h3>Platform patches </h3>

Platform patches

The following is a list known of

<font

platform patches Pegasus requires.

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

patches Pegasus requires.

<ol>

<li> RHAS 2.1 needs the update to

<li>

fix Red Hat Bugzilla 98815.

<font

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

2.1 needs the update to fix Red Hat Bugzilla 98815.

</li>

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

<li>

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

RHEL 4.4

multithreading bug in

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

fixed in

RHEL 4.5

</li>

<li>

Red Hat and SUSE

Linux multiple versions -

multithreaded client intermittently fails connecting to IPv6 (Pegasus

Bugzilla

6586) (Red Hat bug 248052)

</li>

<li> Red Hat and SUSE Linux multiple versions - multithreaded client

intermittently fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red

Hat bug 248052)</li>

<li> OpenSLP Version 2.0 - This release of OpenSLP requires the

patches for OpenSLP version 2.0 documented above.</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms 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">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"><span

style="text-decoration: underline; color: rgb(51, 51, 255);">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</a>

Further information regarding Pegasus support on HP platforms can be found

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

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>

The OpenPegasus Bugzilla database documents defects found in Pegasus

The Pegasus bugzilla database documents any defects found in Pegasus

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

and  is available through the following link:  <a

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

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

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

database</a>.

documented through bugs. Therefore all source code changes to OpenPegasus

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

are documented through bugs providing a complete history of changes and

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

the reasons for those changes.  Bugs reports are filed not only for

only for bugs and

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

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

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

new code

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

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

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

versions.  Therefore, a search of

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

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

version

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

(ex. 

release.

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

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

2.6.1_APPROVED</a>,

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

etc) will yield all changes to

the Pegasus CVS tree for that Pegasus release.

     - Changes for this release (bugs Tagged

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

2.11.0_APPROVED). The link is <a

Pegasus 2.13.0_APPROVED bug list.</a>

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

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

Pegasus 2.11.0_APPROVED bug list.</a>

Control

<h2><a

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

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

The OpenPegasus project is controlled largely through the CVS repository

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

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

The Pegasus project is controlled largely through the CVS repository

mechanism for new and modified Pegasus functionality and for the

and a set of documents

definition and documentation of releases.

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

and

modified Pegasus functionality and for the definition and documentation

of releases.

The following documentation defines the characteristics of this Pegasus

release. The documents are available in the OpenPegasus CVS

repository.

repository.

<ul>

<li> OpenPegasus Release Definition/Status - (See Wiki Section <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_12_x">OpenPegasus

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

2.13.x

Section <a

Release Status</a>) - A

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

section in the Pegasus wiki is used throughout the development of

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

this version as the control point for functionality that will go

section in the Pegasus wiki is used

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

throughout the development of this version as the control point for

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

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

PEPs that represent the Pegasus  functionality changes for this

version of Pegasus. </li>

OpenPegasus

Build and Configuration Options  for Selected Platforms -  In previous versions of Pegasus this

Build and Configuration

information was  released as a Pegasus PEP. Starting with

Options  for Selected

Pegasus 2.9.0 the information is located in the OpenPegasus CVS

Platforms -  In previous

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

versions of Pegasus this information was  released as a Pegasus

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

list of the OpenPegasus interfaces that are considered external

style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</big>.

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

<li> OpenPegasus External Interfaces -<span

by the Steering Committee all subsequent releases of Pegasus MUST

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

continue to support these interfaces. Interfaces not explicitly

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

listed in this document, should be considered as internal and

exception is explicitly approved by the Steering Committee all

subject to change.In previous Pegasus releases this information

subsequent releases of Pegasus MUST continue to support these

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

interfaces. Interfaces not explicitly listed in this document, should

information is integrated into the Pegasus repositoryas  pegasus/doc/EnternalInterface.html.</li>

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

releases this information was available as a separate PEP. Starting

<li> OpenPegasus  SDK Packaging Definition - Defines

with Pegasus 2.9.0 this information is integrated into the Pegasus

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

repositoryas  <font

Starting with Pegasus release 2.11.0, this document is available

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

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

<li> OpenPegasus  SDK Packaging Definition - <span

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

inclusion in the OpenPegasus

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

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

In previous Pegasus releases this document was made available as s

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 -

rather than in the CVS repository.  </li>

PEP 364 - (This document

<li>Pegasus Release Notes - <span

is located in the approved PEP repository and the OpenPegasus

style="font-weight: normal;"> PEP 355 - <span

source tree root directory (<big>pegasus/ReleaseNotes.htm</big>)</li>

style="font-weight: normal;"> (This document is located in the

approved PEP repository and the OpenPegasus source tree root directory (<big

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

</ul>

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

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

The following documentation is available for the this Pegasus

The following documentation is available for the this Pegasus release:

release:

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

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

</li>

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

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

documentation - </li>

documentation - See the header files and the HTML

See the header files and the HTML  API

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

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

documentation is the existing utilities and test programs and the

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

examples in the API documentation.  In particular the

documentation.  In particular the Common/tests unit tests contain

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

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

Common APIs. </li>

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

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

Providers - </li>

Providers - Readme.html in the Pegasus source tree Root

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

Directory, API documentation, and documentation from the Pegasus

documentation, and documentation from the Pegasus Technical Workshop

Technical Workshop which is available on the Pegasus web site.

which is available on the Pegasus web site. <li class="MsoNormal"

</li>

style="color: black;">Building and Debugging

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

Clients - </li>

Clients -API documentation and the documentation on the

API documentation and the documentation on the Pegasus

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

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

</li>

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

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

The

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

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

OpenPegasus web site.  While these are the original design

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

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

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

the design and implementation of these features.

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

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

development team and as a user information resource.  The wiki

can be accessed at <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start</a></li>

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

Line 2056

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

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

</div>

</body></html>

</body>

</html>

Legend:

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

No CVS admin address has been configured