pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

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

version 1.20, 2013/07/18 13:41:36

Line 1

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

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

<head>

<style>

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

</style>

Line 962

Line 965

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

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

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

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

OpenPegasus Enhancement

width="100%"></div>

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

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

PEP #: 366

Title: Release

Notes for OpenPegasus 2.6.1

Notes for OpenPegasus version 2.13.0

Created: <st1:date

Created: 18 July

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

2013

</st1:date>

Authors: Dave

Sudlik

Status:  approved

Authors: Karl

Schopmeyer

Status:  draft

Version History:

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

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

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

<o:p> </o:p>

height="27">

</td>

<span

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

<o:p> </o:p>

</td>

<td

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

<o:p> </o:p>

height="27">

</td>

<span

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

<o:p> </o:p>

</td>

<td

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

height="27">

<span

style="font-family: Arial; color: black;"><o:p> Author</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> Change Description

</o:p>

</td>

</tr>

<span

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

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

</td>

<span

11 July 2013

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

August 2007

</o:p>

</td>

<span

Karl Schopmeyer

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

</td>

<span

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

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

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

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

this color. <o:p><font

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

</td>

</tr>

<tr>

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

<td style="padding: 0.75pt;" 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="vertical-align: top; text-align: center;">8 August 2007

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

before review

</td>

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

</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="vertical-align: top;">Updates from review <span

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

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

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>

</tr>

</tbody>

</table>

<o:p> </o:p>

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

style="color: black;">

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

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.6.1 release of the OpenPegasus CIM Server. The purpose of this PEP is

simply to summarize the characteristics of this release, point to other

documentation that defines the release in more detail, and provide

additional information about this release that is not available in the

other Pegasus documentation. <span

other Pegasus documentation.

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

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

target="_self">

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

</a>

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

style="color: black;">

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

width="100%"></div>

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

</o:p></h2>

<ol>

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

Release</a></li>

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

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

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

of This Release</a></li>

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

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

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

Considerations</a></li>

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

OpenPegasus Functionality</a>

</li>

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

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

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

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

with DMTF Specifications</a></li>

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

<li> <a

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

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

Release

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

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

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

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

Documentation</a></li>

</ol>

<h2>Availability

<h2>Availability of this Release</h2>

of this Release</h2>

This release is available in a number of forms including:

This release is available in a number of forms including:

<ul>

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

These can be

These can be downloaded from the OpenPegasus

downloaded from the OpenPegasus Web

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

site at <a

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

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

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

<li>OpenPegasus  binary and source RPMs on the

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

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

distributions and versions.</li>

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

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

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

release and subsequent snapshots that are made available in the

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

Pegasus CVS are defined on the OpenPegasus CVS repository web page

release and

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

subsequent snapshots that are made available in the Pegasus CVS are

CVS

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

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

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

snapshots

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

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

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

WIKI Release Status Page</a>.</li>

snapshots page</a>.</li>

</ul>

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

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

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

WEB site</a>.

WEB

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

site</a> and the <a title="OpenPegasus WIKI" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">OpenPegasus

Pegasus source

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

tree.

of the Pegasus source tree.

</div>

<h2>OpenPegasus Functionality for This

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

Release</h2>

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

Pegasus overall status by release is defined by  a <a

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

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

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

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

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

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

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

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

yellow, green) and a description of each feature.

OpenPegasus 2.13.0 is a major release, extending the previous Pegasus

Pegasus 2.6.1 is a "point"

release in selected areas as described in the Pegasus  PEP defining

release, extending Pegasus 2.6 in

this release .

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

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

NOTE: OpenPegasus releases are categorized as follows:

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

<ul>

these Release Notes.

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

release includes major functionality change and  incompatible

The major areas of development for this release  were as

behavior changes and/or incompatible public API changes,

follows. For more information access the documented PEP:

</li>

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

Table of Major Changes for this Release

includes new functionality but maintains behavior and public API

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

compatibility,

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

</li>

<li>3rd number changes (2.13.0 to 2.13.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.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="#e0e8ef">Description</th>

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

<th bgcolor="#e0e8ef">Posted PEP

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

Version</th>

</tr>

<tr>

<td>Fixed issues where Pegasus compiler converted Schema Qualifer

decl to CLASS</td>

<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%">Remove compile option

PEGASUS_CLIENT_TRACE_ENABLE (now always compiles) </td>

</td>

</tr>

<tr>

</td>

<td>Fix issues requiring restart of cimserver  if indication

provider reregistered

</td>

<td>

</td>

</tr>

<tr>

</td>

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

</td>

<td>

</td>

</tr>

<tr>

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

</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="color: rgb(153, 51, 153);" align="left">OpenPegasus

Support for IPv6: Stage 1

</td>

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

OpenSLP 2.0 (See OpenSLP 2.0 issues documented below)

</td>

</td>

</tr>

<tr>

</td>

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

(Experimental because of limited testing)

</td>

</td>

</tr>

<tr>

</td>

<td>Fix connection between indication handlers and IndicationService

so that OnFatalErrorPolicy works

</td>

<td>

</td>

</tr>

<tr>

</td>

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

</td>

<td>

</td>

</tr>

<tr>

</td>

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

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

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

based authentication

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Role-based authorization extension for CMPI providers

</td>

<td>

</td>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality change

status between Pegasus versions. <a

The status of several components of Pegasus functionality change status

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

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

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

that

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

have

Status WEB Page</a>.

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

Finally, a significant number of internal changes and corrections

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

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

Status WEB Page</a>.

bug section below for more information.

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

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

OpenPegasus Functionality Changes</h2>

This section documents specific issues that the OpenPegasus team feels are

important to OpenPegasus users with the current release (and possibly

older releases).

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

2.13.0)(bug 9550)</h3>

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

   * traceFileSizeKBytes -  Defines the size of the

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

exceeds the specified size.

   * numberOfTraceFiles - Specifies the number of the tracefiles

for rolling where the default is 3.

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

</h3>

IPv6 is short for "Internet

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

Protocol

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

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

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

to replace the current version Internet Protocol, IP Version 4

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

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

significant performance improvements.

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

291</a>.

<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

The IPv6 support in OpenPegasus is

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

controlled by the PEGASUS_ENABLE_IPV6 build variable. Setting this to

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

While testing OpenPegasus with OpenSLP 2.0 the OpenPegasus team found two

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

issues with this version of OpenSLP.  The patches documented below

allow this version of OpenSLP to work with OpenPegasus

The following subsections provide

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

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

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

a BUFFER_OVERFLOW exception occurs.  This is because UDP cannot

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

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

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

according to the specification, OpenSLP should automatically switch to

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

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

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

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

Listener components. For more information on IPv6 support for your

specific platform, refer to the documentation for that platform.

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

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

All OpenPegasus externals that

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

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

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

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

Effective with the release of OpenPegasus  2.13 the "interop"

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

namespace support for existing or

address must be specified without brackets. For example, the

older repositories which used

OpenPegasus osinfo client (which returns information about the OS

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

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

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

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

the repository from "root/PG_InterOp" to

specified as:

"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

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

details.

3ffe:1:2:1 -p 5988

</div>

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

But the cimcli command, which

to be

takes

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

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

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

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

"root/PG_InterOp"

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

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

"interop".

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

or

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

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

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

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

involving editing one file and rebuilding OpenPegasus was defined as a

</div>

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.

For more information on

specifying

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

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

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

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

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

6 Addressing Architecture</a>

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

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

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

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

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

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

defined OpenPegasus interface, to continue to work with each version

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

upgrade of OpenPegasus.

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

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

Effective OpenPegasus 2.12.0 a new build variable was defined 

</h4>

(PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus builder to define

Modern Linux distributions already

an alternate name for the Interop namespace to either "interop" or

contain IPv6-ready kernels, the

"root/interop" (ex. PEGASUS_INTEROP_NAMESPACE = interop).  Once this

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

build variable is defined and OpenPegasus compiled, the actual name of the

that this module is not loaded automatically on startup.

interop namespace is what was defined in this varaible and all components

Note:

of OpenPegasus use this as the interop namespace name include the complete

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

OpenPegasus test suite.  The only name for the interop namespace will

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

be the name defined through this build variable.  This is the logical

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

approach for implementations starting a new repository.

to use series 2.6.x now.

In order to supexport PEGASUS_CLIENT_TRACE=keyword:keywordport users with

To check whether your current

existing repositories, in 2.13.0,  migration of existing repositories

running

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

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

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

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

for the interop namespace "root/PG_InterOp" to 

the prefered name "interop".

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

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

NOTE: If the interop namespace

</div>

name is redefined with PEGASUS_INTEROP_NAMESPACE clients using the

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

For more information on

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

enabling

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

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

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

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

<h3>Configure Script to Control OpenPegasus Builds (OpenPegasus

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

2.13.0)(Bug 9592)</h3>

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

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

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

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

Warning:

standard build environment.  However, because OpenPegasus must build

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

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

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

configuration tool set, this is an OpenPegasus defined configure

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

script.  The first very experimental version is part of OpenPegasu

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

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

bug 6586</a> and <a

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

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

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

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

bug 248052</a>, and manifests

environment variable with options in the pegasus/configure script where

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

those options are comatible with the Linux standard for defining configure

OpenPegasus with IPv6 enabled may be

options and those options control the entire build process including placement

significantly impacted in these environments.<br

of output and choice of build options.

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

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

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

OpenPegasus has

Microsoft provides supported IPv6

long contained a hidden build controlled function to allow tracing at

implementations for Windows Server

the client through an environment variable

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

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

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

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

On Windows XP, you can use the <span

slightly changed

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

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

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

environment variable was:

query

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

your IPv6 configuration. For example:<br

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

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

<pre> export PEGASUS_CLIENT_TRACE=con</pre>

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

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

2.7.0)</h3>

ipv6 if

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but

</div>

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

Release Notes

Windows Vista

and Windows Server 2008 support an integrated

IPv6 Support for OpenPegasus is documented in

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

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

PEP 291</a>.

on Windows Vista or Windows Server 2008.<br

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

The IPv6 support in OpenPegasus is controlled by the PEGASUS_ENABLE_IPV6

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

For more information on

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

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

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

The following subsections provide some information on IPv6 support for the

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

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

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

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

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

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

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

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

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

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

support</h4>

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

As part of the OpenPegasus

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

automated tests, the TestClient, g11ntest, and IndicationStressTest

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

All OpenPegasus externals that support eitcompilerher a hostname or an IP

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

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

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

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

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

You can also perform manual

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

tests

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

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

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

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

interface would be specified as:

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

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

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

osinfo -h ::1

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

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

delimited with brackets, for example:

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

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

or

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

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

</div>

<ol>

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

</ol>

RFC

<h2>OpenPegasus Relationship to

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

CIM/WBEM Standards</h2>

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

Pegasus was designed and implemented to comply with the DMTF

<h4>IPv6 on Linux</h4>

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

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

DMTF specifications to which this version of Pegasus aims to conform

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

today.

module is not loaded automatically on startup.

Note: you shouldn't use

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

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

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

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

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

short automated test looks like:

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

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

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

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

Documentation Project's IPv6 HOWTO</a>.

Warning: There is currently an

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

RHEL5 and SLES10 systems. This problem is described in

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

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

bug

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

socket failure. You 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 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

example:

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

ipv6 if</big></div>

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

implementation known as the Next Generation TCP/IP stack. 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 Windows

platforms, refer to the document <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>

As part of the OpenPegasus 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

Considerations</a></h2>

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 a minor version upgrade of

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

non-compliance with a standard that significantly affects

interoperability) that may require the community to make potentially

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

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

upgrading to this OpenPegasus release.

<tbody>

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

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

</tr>

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

8830</a></td>

<td align="left">Starting

with OpenPegasus 2.11.0 the requirement for providers (CMPI and C++) to

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

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

on performance the CIMInstance::filter() and

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

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

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

allow users to actually filter properties from an instance in a

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

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

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

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>

<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

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>

</tbody>

</table>

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

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

specifications The following table defines the level of the DMTF

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

<tbody>

<tr>

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

Line 1378

Line 1712

</tr>

<tr>

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

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

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

</tr>

<tr>

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

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

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

</tr>

<tr>

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

Line 1398

Line 1732

</tr>

<tr>

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

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

<td width="33%">2.36.0 Final ( default build Schema) </td>

in pegasus CVS)</td>

</tr>

<tr>

<td>DSP0226 - Web Services for Management

</td>

<td>Version 1.1.1

</td>

</tr>

<tr>

<td>DSP0227 - WS-Management CIM Binding Specification

</td>

<td>Version 1.2.0

</td>

</tr>

<tr>

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

<td>Version 1.1.0

</td>

</tr>

</tbody>

</table>

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

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

Exceptions to

Profiles Supported</h2>

DMTF Specifications</a></h2>

It is a major goal

Today OpenPegasus includes support for several DMTF profiles including:

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

specifications.  However, today there are a number of known

differences. 

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

<ol>

<li>Provider Registration - Pegasus supports registration

<li>DMTF ProfileRegistration Version DSP 1033, Version 1.0.0</li>

through a set of Pegasus Provider registration classes rather than

<li>DMTF Indications DSP 1054, Version 1.1.0. Since this is effectively the same as the

support the DMTF defined Provider Qualifier. Pegasus will not support

SNIA SMI Indication profile it also supports this profile. This

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

profile is enabled by compiling OpenPegasus with the buld variable

provider registration.  This is not a deviation from the

PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

specifications but is a different method of registration than many CIM

</li>

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

<li>SNIA Profile Registration 1.0.0

<li> Indications -Today Pegasus supports process

</li>

indications and lifecycle indications when defined specifically by

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

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

color="#ff0000">  For

For more

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

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

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

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

<li>

<li> IncludeQualifiers

<font

option

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

on Instance Operations

option on Instance Operations

- The DMTF specifications have deprecated the use of qualifiers on

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

The DMTF specifications have deprecated the use of qualifiers on

stated specifically that the client should NOT depend on the

instance operations with the 1.2 CIM Operations Specification. 

includeQualifiers parameter of the CIM/XML instance operations

Some CIM Client implementations expect instances

returning qualifiers.  Some CIM Client implementations expect

returned

instances returned from the CIM Server to include the qualifiers

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

defined in the class definition (such as KEY qualifiers on

definition (such as KEY qualifiers on properties).   Pegasus

properties).   Pegasus today expects the provider to

today expects the provider to complete the qualifiers on instances in

complete the qualifiers on instances in accordance with the

accordance with the specification and generally the interpretation is

specification and generally the interpretation is that Pegasus

that Pegasus applies class level qualifiers when the includeInstance

applies class level qualifiers when the includeInstance parameter is

parameter is supplied on instance operations.  However, Pegasus

supplied on instance operations.  However, Pegasus today is

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

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

should NOT depend on Pegasus accurately honoring the includeQualifier

depend on Pegasus accurately honoring the includeQualifier parameter

parameter for instance operations.  In the future it is expected

for instance operations.  In the future it is expected that

that Pegasus will deprecate the use of qualifiers on instance

Pegasus will deprecate the use of qualifiers on instance operations

operations completely.

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

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>LocalOnly option on instance

<li>MOF Namespace Pragma -The

Operations - With the 1.1 version of Specification for CIM

Pegasus compiler does not support the namespace pragma defined in DSP

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

0004. Namespaces for the OpenPegasus repository are defined through

GetInstance and EnumerateInstances operations was modified. This change

arguments for the MOF Compiler

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

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

<li>CIMOperation Trailer - Pegasus implements chunking based on

MOFCompiler namespace pragma - The

the DSP0200 1.2.0 preliminary spec. including the operation trailer

Pegasus compiler does not support the namespace pragma.

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

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

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

is used Pegasus is returning a noncompliant response to enumerate type

requests. </li>

<li>Whitespace in XML value Element

- Pegasus trims the leading and trailing whitespace from XML value

elements that are of the Type String.  This behavior is

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

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

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

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

documented bugs in Pegasus such as this that the OpenPegasus team

feels cannot be incorporated into the code until a major version

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

<li>modifyInstance operation behavior

in the Pegasus repository does not match the DMTF specification.

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

all properties rather than just the properties supplied with the

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

for more information.</li>

<li>OpenPegasus Interop Namespace - The default interop namespace

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

OpenPegasus prior to 2.12.0 this could be changed during build by

modifying a string definition in the code. Effective version 2.12.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>Pegasus implements

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

chunking

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

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

- If requests or responses include properties or parameters with

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

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

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

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

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

accepted because these special strings are not understood by the

decoder on Windows.</li>

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

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

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

Today the DMTF Specification DSP0201 allows only numeric information

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

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

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

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

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

Covered properties (properties which have the same name in a

superclass and subclass without overridding the property in the

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

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

general agreement is that the requirement itself is not supportable

and particularly not with the existing OpenPegasus APIs. 

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

CIM 3.0).

</li>

</ol>

<h2>OpenPegasus <a

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

name="Supported Platforms">Supported

Platforms</a></h2>

Each OpenPegasus release lists as 'active' platforms those

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus

code

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

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

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

regularly document issues and/or fix defects as the Pegasus

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

code base is changed. 

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

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

operation of  Pegasus cannot be assured.  In all cases,

a group

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

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

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

Pegasus cannot be

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

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

relevant defects that affect their platform.   The platforms

responsibility of the entity that packages and/or compiles OpenPegasus

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

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

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

bugzilla database for a list of relevant defects that affect their

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

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

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

Pegasus release are:

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

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

Actively Supported Platforms (Nightly Tests Reported for this release)

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

<tbody>

<td

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

height="26" width="211">

Platform and

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

</td>

<td

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

height="26" width="289">

Compilers<span

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

</td>

</tr>

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

width="211">

HP-UX<o:p>

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

PA_RISC and Itanium</o:p>

</td>

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

width="289">

HP aC++

HP <span

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

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

</td>

</tr>

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

width="211">

Linux

<span

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

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

</td>

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

</td>

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

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

width="289">

<span

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

</td>

</tr>

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

width="211">

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

<span

</td>

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

</td>

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

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

width="289">

<span

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

</td>

</tr>

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

width="211">

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

</td>

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

width="289">

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

<span

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

</td>

</tr>

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

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

width="211">

IA-32</td>

Linux IA-32, <span

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

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

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

</td>

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

width="289">

<span

style="color: black;">gcc

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

</td>

</tr>

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

width="211">

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

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

</td>

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

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

width="289">

Microsoft

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

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

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

</td>

</tr>

<tr>

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

width="211">

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

Windows XP<o:p>,

Version 1.7 and up</td>

Windows 2003</o:p>

</tr>

</td>

</tbody>

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

</table>

width="289">

Microsoft

Platforms not Actively supported for this release (No

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

current Nightly Build Test Results)

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

<tbody>

Platform and

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

</td>

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

</td>

</tr>

<tr>

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

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

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

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

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

the Windows. </td>

</tr>

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

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

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

higher</td>

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

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

</tr>

<tr>

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

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

8</big></td>

</big></td>

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

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

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

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

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

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

Alpha and above</big> </td>

</tr>

<tr>

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

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

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

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

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

above</big> </td>

</tr>

<tr>

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

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

</big></td>

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

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

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

</td>

</tr>

<tr>

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

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

color="RED">Solaris 9

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

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

for OpenVMS Alpha</big></td>

</tr>

<tr>

<td><big> HP OpenVMS 8.3 or later

IA64</big></td>

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

or later required on

OpenVMS IA64</big></td>

</tr>

<tr>

Windows 2000

</td>

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

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

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

regularly tested.</td>

</tr>

<tr>

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

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

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

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

</tr>

<tr>

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

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

</tr>

</tbody>

</table>

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

patches Pegasus requires.

<font

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

2.1 needs the update to fix Red Hat Bugzilla 98815.

</div>

Further information regarding Pegasus support on IBM platforms can

found at: <a

href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><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

found at:

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

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

The Pegasus bugzilla database documents any defects found in Pegasus

and  is available through the following link:  <a

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

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

release have been marked with the keyword 2.6.<span

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

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

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

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

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

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

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

base for bugs with the tag 2.6.<span

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

yield

all changes to the

Pegasus RELEASE_2_6-branch

CVS branch since

Pegasus 2.6.0.

- Changes for Pegasus 2.6.<span

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

face="Courier New">2.6.1_APPROVED)

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

2.6.1_APPROVED bug list</a>

<h4>2.6.1 bugs of special interest:

</h4>

<ul>

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

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

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

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

was changed to include the RTLD_GLOBAL option for all POSIX platforms

except VMS.

</li>

</ul>

<h2><a

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

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

The Pegasus project is controlled largely through a set of documents

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

modified Pegasus functionality and for the definition and documentation

of releases.

Specifically the following PEPs define the characteristics of the

Pegasus 2.6 release. These PEPs are available as

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

Approved PEPs.</a>

For this 2.6.1 point release,

only

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

references should be back to the 2.6 release PEPs.

<ol>

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

<li> RHAS 2.1 needs the update to

fix Red Hat Bugzilla 98815.

used

throughout the development of this version as the control point for

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

PEPs that represent the Pegasus  functionality changes for this

version of Pegasus.</li>

<li> PEP 277 -  OpenPegasus 2.6 Build and Configuration

Options  for Selected

Platforms</li>

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

public interfaces for clients and providers that are considered

external and therefore "frozen".

</li>

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

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

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

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

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

Defines the recommended set of files for inclusion in this OpenPegasus

release.</li>

<li>PEP 305 - Pegasus 2.6.1

Release

Notes (This document located in

the approved PEP repository and the OpenPegasus source tree root

directory)

</li>

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

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

repository and also in the OpenPegasus

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

source

Hat bug 248052)</li>

tree root directory).</li>

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

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

</ol>

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

</div>

The following documentation is available for the this Pegasus

release:

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>

Further information regarding Pegasus support on HP platforms can be found

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

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

The OpenPegasus Bugzilla database documents defects found in Pegasus

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

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

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

documented through bugs. Therefore all source code changes to OpenPegasus

are documented through bugs providing a complete history of changes and

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

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

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

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

Bugzilla base for bugs with the tag for a particular version (ex.  <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED">2.6.0_APPROVED</a>,

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

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

release.

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

Pegasus 2.13.0_APPROVED bug list.</a>

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

Control

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

The OpenPegasus project is controlled largely through the CVS repository

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

mechanism for new and modified Pegasus functionality and for the

definition and documentation of releases.

The following documentation defines the characteristics of this Pegasus

release. The documents are available in the OpenPegasus CVS

repository.

<ul>

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

2.13.x

Release Status</a>) - A

section in the Pegasus wiki is used throughout the development of

this version as the control point for functionality that will go

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

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

OpenPegasus

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

information was  released as a Pegasus PEP. Starting with

Pegasus 2.9.0 the information is located in the OpenPegasus CVS

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

<li> OpenPegasus External Interfaces -The

list of the OpenPegasus interfaces that are considered external

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

by the Steering Committee all subsequent releases of Pegasus MUST

continue to support these interfaces. Interfaces not explicitly

listed in this document, should be considered as internal and

subject to change.In previous Pegasus releases this information

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

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

<li> OpenPegasus  SDK Packaging Definition - Defines

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

Starting with Pegasus release 2.11.0, this document is available

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

In previous Pegasus releases this document was made available as s

separate Pegasus PEP document rather than in the CVS repository.

</li>

<li> Pegasus  Runtime Packaging Definition - Defines

the recommended set of files for inclusion in this OpenPegasus

release. Starting with Pegasus release 2.11.0, this idocument

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

In previous releases this was made available as a seperate Pegasus

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

<li>Pegasus Release Notes -

PEP 364 - (This document

is located in the approved PEP repository and the OpenPegasus

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

</ul>

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

The following documentation is available for the this Pegasus release:

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

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

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

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

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

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

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

documentation - See the header files and the HTML  API

</li>

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

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

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

documentation - See the header files and the HTML

documentation.  In particular the Common/tests unit tests contain

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

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

documentation is the existing utilities and test programs and the

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

examples in the API documentation.  In particular the

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

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

documentation, and documentation from the Pegasus Technical Workshop

Common APIs. </li>

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

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

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

Providers - Readme.html in the Pegasus source tree Root

Clients - API documentation and the documentation on the Pegasus

Directory, API documentation, and documentation from the Pegasus

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

Technical Workshop which is available on the Pegasus web site.

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

</li>

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

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

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

Clients -API documentation and the documentation on the

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

</li>

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

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

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

OpenPegasus web site.  While these are the original design

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

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

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

<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

<span

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

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

work for additional information regarding copyright ownership. Each

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

contributor licenses this file to you under the OpenPegasus Open Source

style="color: black;">

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

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

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

width="100%">

copy of this software and associated documentation files (the

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

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

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

Open Group; VERITAS Software Corporation; Intel Corp.

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

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

Permission is hereby granted, free of charge, to any

the following conditions:

person obtaining a copy  of this software and associated

The above copyright notice and this permission notice shall be included

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

in all copies or substantial portions of the Software.

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

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

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

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

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

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

to do so, subject to the following conditions:

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

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

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION

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

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

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

SOFTWARE. THE SOFTWARE IS PROVIDED  "AS IS", WITHOUT WARRANTY OF

ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE

LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION

OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION

WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

</div>

</div>

</body>

</html>

</body></html>

Legend:

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

No CVS admin address has been configured