pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.11, 2007/08/08 21:20:13

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

Line 1

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

<head>

<style>

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

</style>

Line 962

Line 963

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

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

<o:smarttagtype

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

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>

Line 995

Line 992

</w:Compatibility>

<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>

</w:WordDocument>

</xml><![endif]-->

</xml><![endif]--></head><body lang="EN-US" link="blue" vlink="blue">

</head>

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

style="color: black;">

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

Pegasus

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

PEP #: 359

Title: Release

Notes for OpenPegasus 2.6.1

Notes for OpenPegasus version 2.11.0 and version 2.11.1

Created: <st1:date

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

</st1:date>

Authors: Dave

Sudlik

Status:  approved

Created: 23

March 2011

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

23 March 2011

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

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

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

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>

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

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

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

</td>

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

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

</td>

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

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

</td>

</tr>

</tr>

<tr>

</tr>

</tr>

</tbody>

</table>

<o:p> </o:p>

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

style="color: black;">

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

width="100%"></div>

Abstract: This document defines the release notes for the

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

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

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

to summarize the characteristics of this release, point to other

documentation that defines the release in more detail, and provide

additional information about this release that is not available in the

other Pegasus documentation. <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"

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

target="_self">

and is also available directly in the OpenPegasus source tree root

</a>

library as ReleaseNotes.htm

<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

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

</o:p></h2>

<ol>

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

Release</a></li>

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

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

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

Considerations</a></li>

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

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

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

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

with DMTF Specifications</a></li>

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

<li><a href="#PEGASUS%20Bugs">OpenPegasus Bug Fixes and Changes for this Release

<li> <a

</a></li>

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

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

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

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

Documentation</a></li>

</ol>

<h2>Availability

of this Release</h2>

NOTE: This document defines

the OpenPegasus 2.11.0 version release with comments added to define

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

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

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

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

OpenPegasus tries to execute only bug fixes for revision releases and

not include enhancements but in exceptional cases including 2.11.1 some

extensions are included (See the Functionality of this Release

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

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

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

9014. Note that in OpenPegasus ALL changes including enhancements are

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

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

2.11.1.

This release is available in a number of forms including:

<ul>

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

These can be

downloaded from the OpenPegasus Web

site at <a

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

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

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

<li>OpenPegasus  binary and source RPMs on the

A source RPM is  available on the

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

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

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

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

release and

subsequent snapshots that are made available in the Pegasus CVS are

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

defined on the OpenPegasus CVS repository web page (see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

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

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

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

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

snapshots page</a>.</li>

</ul>

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

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

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

Pegasus source

Line 1158

Line 1151

</div>

<h2>OpenPegasus Functionality for This

Release</h2>

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

Pegasus overall status by release is defined by  a <a

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

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

WEB Page</a>

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

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

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

shows the

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

Pegasus users and developers the status of the various features found

yellow, green) and a description of each feature.

in Pegasus

Pegasus 2.6.1 is a "point"

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

release, extending Pegasus 2.6 in

description of

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

each feature.

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

Pegasus 2.11.0

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

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

these Release Notes.

areas as described in the Pegasus  PEP defining this release

.

The major areas of development for this release  were as

follows. For more information access the documented PEP:

follows. Note that the bugs listed represent only those features

incorporated in bugs without PEPS that are considered enhancements, not

Table of Major Changes for this Release

all bugs incorporated in the release. For

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

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

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

Table of Major

Changes for this Release

<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>Run 32 bit providers in 64 bit OpenPegasus</td>

</tr>

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

</td>

</tr>

<tr>

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

Indication Handler</td>

</tr>

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

</td>

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

Implementation, stage 2

</td>

</tr>

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

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

</td>

Support for IPv6: Stage 1

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

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

</tr>

<tr>

</td>

<td>Add External SLP support to release builds

</td>

</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 style="color: rgb(0, 153, 0);"> <a

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

</td>

</tr>

<tr>

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

8806</a></td>

<td>Diagnose data for BAD UTF8 exception</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>

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

</a> </td>

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

to include enumeration association filters</td>

</td>

</tr>

<td align="left" width="75%"> New runtime configuration options for Indication Service (2.11.1 Release)

</td>

</a></td>

</tr><tr>

</td>

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

backward compatibility due to a new virtual function that was

introduced in Pegasus 2.11.0 (2.11.1 release)

</td>

</td>

</tr>

<tr>

</td>

</td>

</td>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality change

status between Pegasus versions. <a

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 changed status can be identified by a change in color from the

Status WEB Page</a>.

release to this release</a> on the

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

WEB Page</a>.

Finally, a significant number of internal changes and corrections

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

were made

bug section below for more information.

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

section below

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

for more information.

</h3>

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

IPv6 is short for "Internet

NOTE: This functionality was incorporated in OpenPegasus

2.7.0 but it

was felt that the information below was worth repeating in subsequent

Release

Notes

IPv6 is

short for "Internet

Protocol

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

to replace the current version Internet Protocol, IP Version 4

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

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

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

PEP

291</a>.

291</a>.

The IPv6 support in OpenPegasus is

The IPv6 support in OpenPegasus is

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for

controlled by the PEGASUS_ENABLE_IPV6 build variable. Setting this to

this

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

variable is "true"; setting this to

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

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

The following subsections provide

The following subsections provide

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

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

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

Line 1231

Line 1336

Listener components. For more information on IPv6 support for your

specific platform, refer to the documentation for that platform.

All OpenPegasus externals that

All OpenPegasus externals that

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

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

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

Line 1241

Line 1346

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

specified as:

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

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

3ffe:1:2:1 -p 5988

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

</div>

But the cimcli command, which

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; color: rgb(153, 51, 153);">cimcli ns -l

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

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

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

or

or

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

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

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

</div>

For more information on

For more information on

specifying

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

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

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

RFC 2373 - IP Version

6 Addressing Architecture</a>

6 Addressing Architecture</a>

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

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

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

Format for

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

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

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

<h4>IPv6 on Linux</h4>

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

Modern Linux distributions already

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

</h4>

Modern Linux distributions already

contain IPv6-ready kernels, the

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

that this module is not loaded automatically on startup.

Note:

Note:

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

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

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);">test -f

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

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

</div>

For more information on

For more information on

enabling

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

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

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

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

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

Documentation Project's IPv6 HOWTO</a>.

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

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

Warning:

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

described in

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

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

bug 6586</a> and <a

bug 6586</a>

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

and

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

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

bug 248052</a>, and manifests

bug 248052</a>,

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

and manifests itself as an intermittent IPv6 socket failure. You

OpenPegasus with IPv6 enabled may be

should be aware

significantly impacted in these environments.<br

that OpenPegasus with IPv6 enabled may be significantly impacted in

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

these

environments.

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

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6

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

On Windows XP, you can use the ipv6.exe

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

tool to install, uninstall, and

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

query

your IPv6 configuration. For example:<br

your IPv6 configuration. For example:

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

<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);">ipv6 install

ipv6 if</big></div>

ipv6 if

Windows Vista

</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 in 2.6.1 has not yet been tested

Note that the OpenPegasus IPv6 support has not yet been tested

on Windows Vista or Windows Server 2008.<br

on Windows Vista or Windows Server 2008.

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

For more information on

For more information on

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

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

the document

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

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

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

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

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

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

<h4>Testing your OpenPegasus IPv6

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

support</h4>

support</h4>

As part of the OpenPegasus

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

(::1) if PEGASUS_ENABLE_IPV6=true.

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

You can also perform manual

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

running on the WBEM standard http port of 5988:

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

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

osinfo -h ::1

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

</div>

Support for forward-compatibility is a fundamental design principle

for the

<ol>

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

</ol>

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 defect

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

Clients when

upgrading to this OpenPegasus release.

<tbody>

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

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

</tr>

<td align="left">The requirement for providers (CMPI and C++) to

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

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

on performance the CIMInstance::filter() and

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

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

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

allow users to actually filter properties from an instance, new

function CIMInstance::filterInstance() will actually filter properties

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

versions of Pegasus.</td>

</tr>

<td>

</td>

<td>

</td>

</tr>

<td>

</td>

<td>

</td>

</tr>

<td>

</td>

<td>

</td>

</tr>

<td>

</td>

<td>

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

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

</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.22.1 Final,  22 Oct 2009( default) </td>

in pegasus CVS)</td>

</tr>

</tbody>

</table>

Line 1419

Line 1566

provider registration.  This is not a deviation from the

specifications but is a different method of registration than many CIM

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

<li> Indications -Today Pegasus supports process

<li>Indications -Today Pegasus supports process

indications and lifecycle indications when defined specifically by

providers. Pegasus does not support lifecycle indications if they are

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

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

color="#ff0000">  For

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

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

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

<li>

<font

IncludeQualifiers

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

option on Instance Operations

The DMTF specifications have deprecated the use of qualifiers on

instance operations with the 1.2 CIM Operations Specification. 

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 instances

returned

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

Line 1445

Line 1592

should NOT depend on Pegasus accurately honoring the includeQualifier

parameter for instance operations.  In the future it is expected

that Pegasus will deprecate the use of qualifiers on instance

operations completely.

operations completely.  When Pegasus uses object normalization,

the normalizer does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.

</li>

<li>LocalOnly option on instance

Operations - With the 1.1 version of Specification for CIM

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

GetInstance and EnumerateInstances operations was modified. This change

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

Line 1458

Line 1608

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

specification for more information.</li>

<li>

MultiRequest Oprations - Pegasus

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOFCompiler namespace pragma - The

MOF Compiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

Pegasus compiler does not support the namespace pragma.

</li>

<li>Pegasus implements

<li>CIMOperation Trailer - Pegasus implements

chunking

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

based on the DSP0200 1.2.0 preliminary spec. including the operation

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

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

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

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

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

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 modified 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>Covered Properties (multiple properties with the same name but different class origin)

- The DMTF Spec DSP0004 now defines the requirement for covered

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

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

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

including a maintainer for the platform that will be willing to

regularly document issues and/or fix defects as the Pegasus

regularly

code base is changed. 

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

changed. 

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

a group

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

Pegasus cannot be

Pegasus

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

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

it is the

responsibility of the entity that packages and/or compiles OpenPegasus

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

for

bugzilla database for a list of relevant defects that affect their

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

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

bugzilla

Pegasus release are:

database for a list of relevant defects that affect their

platform.  

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

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

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

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

the time

of the release are reported in the second table.

Actively Supported Platforms (Nightly Tests Reported for this

release)

<tbody>

<td

style="padding: 0.75pt; background: rgb(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++ B3910B<o:p></o:p>

HP <span

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

</td>

</tr>

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

width="211">

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

<span

</td>

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

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

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

</td>

<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 IA-32</td>

width="211">

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

Linux IA-32, <span

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

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

</tr>

</td>

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

width="289">

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

<span

style="color: black;">gcc

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

</td>

gcc

(versions 3.xx, 4.xx)

</td>

</tr>

<tr>

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

z/OS Version 1.7 and up</td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this release

(No

current Nightly Build Test Results

<tbody>

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

width="211">

Platform and

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

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

</td>

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

width="289">

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

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"

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

width="211">

Windows XP<o:p>,

Windows 2003</o:p>

</td>

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

width="289">

Microsoft

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

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

</td>

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

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

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

</tr>

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

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

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

and 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 8</big></td>

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

</big></td>

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

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

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

</big></td>

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

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

</td>

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

Platform patches

Platform patches

<font

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

patches Pegasus requires.

The following is a list known of platform

patches Pegasus requires.

<font

<ol>

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

<li>

2.1 needs the update to fix Red Hat Bugzilla 98815.

RHAS

2.1 needs the update to fix Red Hat Bugzilla 98815.

</li>

<li>

RHEL 4.4

multithreading bug in

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

fixed in

RHEL 4.5

</li>

<li>

Red Hat and SUSE

Linux multiple versions -

multithreaded client intermittently fails connecting to IPv6 (Pegasus

Bugzilla

6586) (Red Hat bug 248052)

</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can

found at: <a

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

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>

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

</a></h2>

The Pegasus bugzilla database documents any defects found in Pegasus

and  is available through the following link:  <a

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

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

database</a>.

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

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

release have been marked with the keyword 2.6.<span

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

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

only for bugs and

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

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

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

new code

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

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

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

versions.  Therefore, a search of

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

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

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

version

base for bugs with the tag 2.6.<span

(ex. 

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

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

yield

all changes to the

2.6.1_APPROVED</a>,

Pegasus RELEASE_2_6-branch

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

CVS branch since

etc) will yield all changes to

Pegasus 2.6.0.

the Pegasus CVS tree for that Pegasus release.

- Changes for Pegasus 2.6.<span

     - Changes for this release (bugs Tagged

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

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

face="Courier New">2.6.1_APPROVED)

Pegasus 2.11.0_APPROVED bug list.</a>

     - (2.11. 1) Changes between the 2.11.0 release

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

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

2.6.1_APPROVED bug list</a>

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

<h4>2.6.1 bugs of special interest:

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

</h4>

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

<ul>

The Pegasus project is controlled largely through the CVS repository

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

and a set of documents

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

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

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

and

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

The following documentation defines the characteristics of this Pegasus

Pegasus 2.6 release. These PEPs are available as

release. The documents are available in the OpenPegasus CVS

repository.

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

Approved PEPs.</a>

<ul>

For this 2.6.1 point release,

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

only

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

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

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

references should be back to the 2.6 release PEPs.

section in the Pegasus wiki is used

<ol>

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

used

throughout the development of this version as the control point for

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

PEPs that represent the Pegasus  functionality changes for this

version of Pegasus.</li>

version of Pegasus. </li>

<li> PEP 277 -  OpenPegasus 2.6 Build and Configuration

OpenPegasus

Options  for Selected

Build and Configuration

Platforms</li>

Options  for Selected

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

Platforms -  In previous

public interfaces for clients and providers that are considered

versions of Pegasus this information was  released as a Pegasus

external and therefore "frozen".

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

</li>

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

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

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

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

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

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

exception is explicitly approved by the Steering Committee all

Defines the recommended set of files for inclusion in this OpenPegasus

subsequent releases of Pegasus MUST continue to support these

release.</li>

interfaces. Interfaces not explicitly listed in this document, should

<li>PEP 305 - Pegasus 2.6.1

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

Release

releases this information was available as a separate PEP. Starting

Notes (This document located in

with Pegasus 2.9.0 this information is integrated into the Pegasus

the approved PEP repository and the OpenPegasus source tree root

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

directory)

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

</li>

inclusion in the OpenPegasus

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

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

repository and also in the OpenPegasus

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

source

tree root directory).</li>

previous Pegasus releases this document was made available as s

</ol>

separate Pegasus PEP document rather than in the CVS repository.

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

</li>

The following documentation is available for the this Pegasus

<li> Pegasus  Runtime Packaging Definition

release:

- 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 355 - (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 Documentation</a></h2>

The following documentation is available for the this Pegasus

release:

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

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

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

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 each

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

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

documentation - See the header files and the HTML  API

documentation - </li>

See the header files and the HTML  API

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

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

documentation.  In particular the Common/tests unit tests contain

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

extensive examples of the use of the 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 Root Directory, API

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

documentation, and documentation from the Pegasus Technical Workshop

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

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

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

Clients - </li>

Clients - API documentation and the documentation on the Pegasus

API documentation and the documentation on 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;">PEPs - </li>

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

The

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

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

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

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

OpenPegasus web site.  While these are the original design

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

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

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

the design and implementation of these features.

</ul>

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

<span

license

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

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with

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

this work for additional information regarding copyright ownership.

style="color: black;">

Each contributor licenses this file to you under the OpenPegasus Open

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

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

width="100%">

License.

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

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

obtaining a

Open Group; VERITAS Software Corporation; Intel Corp.

copy of this software and associated documentation files (the

"Software"),

Permission is hereby granted, free of charge, to any

to deal in the Software without restriction, including without

person obtaining a copy  of this software and associated

limitation

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

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

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

sublicense,

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

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

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

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

to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be

included

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION

in all copies or substantial portions of the Software.

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

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

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

EXPRESS

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

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

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

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

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

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

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

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

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

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

</div>

</div>

</body>

</html>

</body></html>

Legend:

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

No CVS admin address has been configured