pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.10 and 1.17

version 1.10, 2007/01/09 18:25:09

version 1.17, 2010/03/26 13:20:35

Line 1

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

<head>

<style>

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

</style>

<style>

<!--

/* Font Definitions */

Line 949

Line 946

{margin-bottom:0in;}

-->

</style>

<style>

/* Style Definitions */

table.MsoNormalTable

Line 965

Line 961

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

Line 997

Line 990

</w:Compatibility>

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

</w:WordDocument>

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

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

</head>

Pegasus

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

PEP #: 287

PEP #: 355

Title: Release

Notes for OpenPegasus 2.6.0

Notes for OpenPegasus version 2.10.0

Created: <st1:date year="2004" day="23" month="3">19 December 2006</st1:date>

Created: 21 January 2010

Authors: Karl Schopmeyer

Line 1032

Line 1020

Version History:

<tbody>

Line 1074

Line 1062

<o:p>  19 December

2006</o:p>

21 January 2010

</td>

Line 1089

Line 1077

Initial

Submission<o:p>

Submission <o:p>

</o:p>

</td>

Line 1098

Line 1086

<tr>

<td style="padding: 0.75pt;" align="center" height="21">20 December 2006</td>

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

<td style="padding: 0.75pt;" height="21">Remove functionality description section</td>

<td style="padding: 0.75pt;" height="21"> Remove PEP 353 and 354 from

list and point to repository.Clean up PEP list</td>

</tr>

Line 1112

Line 1101

<td style="padding: 0.75pt;" align="center" height="21">2 January 2007</td>

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

<td style="padding: 0.75pt;" height="21">Fix comments from 1.1. Note comments are in

Red in text for now.</td>

</tr>

Line 1125

Line 1113

<td style="padding: 0.75pt;" align="center" height="21">3 January 2007</td>

<td style="padding: 0.75pt;" align="center" height="21">25 March 2010</td>

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

<td style="padding: 0.75pt;" height="21">Clean up remaining comments and remove

<td style="padding: 0.75pt;" height="21">Incorporate comments from Vote on

comment markers.</td>

this PEP - This version approved</td>

</tr>

<td style="padding: 0.75pt;" align="center" height="23">8 January</td>

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

<td style="padding: 0.75pt;" height="23">Move approved PEP, reflecting

changes to 1.3 for approval</td>

</tr>

Line 1151

Line 1138

</tbody>

</table>

<o:p> </o:p>

Abstract: This document defines the release notes for the

Abstract: This document defines the release notes for the 2.6.0 release of the Pegasus CIM Server.

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

The purpose of this PEP is simply to summarize the characteristics of this

to summarize the characteristics of this release, point to other

release, point to other documentation that defines the release in more detail,

documentation that defines the release in more detail, and provide

and provide additional information about this release that is not available in

additional information about this release that is not available in the

the other Pegasus documentation. <a href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35" target="_self">

other Pegasus documentation.

</a>

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

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

</o:p></h2>

<ol>

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

<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="#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="#Supported Platforms">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 Bugs">OpenPegasus Bugs</a></li>

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

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

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>

This release is available in a number of forms including:

<ul>

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

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

These can be

downloaded from the OpenPegasus Web

site at <a 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.. A source RPM is  available on the

<li>OpenPegasus  binary and source RPMs on the OpenPegasus web

OpenPegasus web site that can be used to build binaries for most LSB-compliant RPM-based Linux distributions and versions.</li>

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

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

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

WEB site</a>.

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

Pegasus source

tree.

</div>

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

Line 1233

Line 1199

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

Pegasus users and developers the status of the various features found in Pegasus

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

each feature.Pegasus 2.6.0

each feature.Pegasus 2.10.0

is a major release, extending Pegasus 2.5 in selected

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

areas as described in the Pegasus  PEP defining this release (see PEP 218)

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:

more information access the PEP for each change defined:

Table of Major Changes for this Release

Table of Major Changes for this Release

<tbody>

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

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

</tr>

<td align="left" width="75%">WS-Management Support in CIM Server - Phase II.

NOTE: This is an update of the same PEP number that incorporated

WS_Management changes to Pegasus 2.9.0 to incorporate more WS_Management

functionality.</td>

2.2</a> </td>

</tr>

<tr>

<td align="left" width="75%">Extend CIMCLI to create/modify instances with other features</td>

</tr>

<td align="left" width="75%">Single-Memory-Object for CMPI structure</td>

</tr>

<td align="left" width="75%">Separate Internal Modules from Common Library</td>

1.1</a></td>

</tr>

<tr><td style="text-align: center;">PEP 350</td><td>Multi CIMOM support on

same OS </td><td style="text-align: center;">

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

<a name="comtag_90">repupgrade utility enhancement to

update SystemName property in indication filter/handler and

ObjectManager instances</a> </td><td style="text-align: center;"> </td></tr><tr align="center">

<a name="comtag_95">Indication service can be

disabled/enabled dynamically</a> </td>

</tr>

<TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666

borderColorLight=#cccccc border=1>

</tr>

<TBODY>

</tbody>

</table>

<TH bgColor=#E0E8EF>Description</TH>

<TH bgColor=#E0E8EF>Posted PEP Version</TH>

</TR>

<TD align="left">Embedded Instance Support in Pegasus</TD>

<TD>

1.3</a>

</TD>

</TR>

<TD align="left">Providing SMI-Server Profile through OpenPegasus</TD>

<TD>

1.5.1</a></TD>

</TR>

<TD align="left">Incorporation of CIM_Error into OpenPegasus Infrastructure</TD>

<TD>

1.4</a>

</TD>

</TR>

<TD align="left">Language Interfaces</TD>

<TD>

1.0</a>

</TD>

</TR>

<TD align="left">Reducing Pegasus Code size and static memory usage</TD>

<TD>

1.3.1</a>

</TD>

</TR>

<TD align="left">Indication Subscription Management</TD>

<TD>

1.2</a>

</TD>

</TR>

<TD align="left">Audit Logging</TD>

<TD>

1.4</a></TD>

</TR>

<TD align="left">SSL Certificate Management Command Interfaces</TD>

<TD>

1.2</a></TD>

</TR>

<TD align="left">CMPI 2.0 Currency</TD>

<TD>

1.1</a>

</TD>

</TR>

<TD align="left">SLP enhancements for Pegasus 2.6</TD>

<TD>

1.5</a></TD>

</TR>

<TD align="left">Repository Archive</TD>

<TD>

1.1</a>

</TD>

</TR>

</TBODY>

</TABLE>

</UL>

</html>

The status of several components of Pegasus functionality change status

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

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

Line 1351

Line 1278

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

for more information.

<ol>

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

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but it

</ol>

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 href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">

PEP

291</a>.

The IPv6 support in OpenPegasus is

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this

variable is "true"; setting this to

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

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

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

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

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

Listener components. For more information on IPv6 support for your

specific platform, refer to the documentation for that platform.

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

address must be specified without brackets. For example, the

OpenPegasus osinfo client (which returns information about the OS

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

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

specified as:

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

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

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>

For more information on

specifying

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

6 Addressing Architecture</a>

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

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

<h4>IPv6 on Linux</h4>

Modern Linux distributions already

contain IPv6-ready kernels, the

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

that this module is not loaded automatically on startup.

Note:

you shouldn't use 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 information on

enabling

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

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

Documentation Project's IPv6 HOWTO</a>.

Warning:

There is currently an 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

IPv6

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

<h4>Testing your 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:

osinfo -h ::1</big></div>

<h2><a name="Compatibility_Considerations_">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 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>

</tr>

</tr>

</tr>

</tr>

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

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

to which this version of Pegasus aims to conform today.

DMTF specifications to which this version of Pegasus aims to conform

today.

<tbody>

<tr>

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

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

</tr>

<tr>

<td width="33%">DSP 0004 - CIM Infrastructure Specification</td>

<td width="33%">Version 2.3 Final, 4 October 2005</td>

</tr>

<tr>

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

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

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

</tr>

<tr>

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

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

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

</tr>

<tr>

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

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

</tr>

<tr>

<td width="33%">DSP 0205 - WBEM Discovery using SLP</td>

<td width="33%">1.0, preliminary, 27 January 2004</td>

</tr>

<tr>

<td width="33%">DSP 0206 - WBEM SLP Template</td>

<td width="33%">1.0.0, Preliminary, January 2004</td>

</tr>

<tr>

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

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

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

pegasus CVS)</td>

</tr>

</tbody>

</table>

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

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

Exceptions to

DMTF Specifications</a></h2>

It is a major goal

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

specifications.  However, today there are a number of known

differences. 

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

<ol>

<li>Provider Registration - Pegasus supports registration

through a set of Pegasus Provider registration classes rather than

support the DMTF defined Provider Qualifier. Pegasus will not support

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

provider registration.  This is not a deviation from the specifications but

provider registration.  This is not a deviation from the

is a different method of registration than many CIM Servers and means that the

specifications but is a different method of registration than many CIM

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

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

indications and lifecycle indications when defined specifically by

lifecycle indications when defined specifically by providers. Pegasus does not

providers. Pegasus does not support lifecycle indications if they are

support lifecycle indications if they are not defined by the provider or for

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

changes to CIM Classes.

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

For more information see the Pegasus CVS

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

file  <a name="comtag_137"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

<li>

IncludeQualifiers

IncludeQualifiers

option on Instance Operations

The DMTF specifications have deprecated the use of qualifiers on instance

The DMTF specifications have deprecated the use of qualifiers on

operations with the 1.2 CIM Operations Specification.  Some CIM Client implementations expect instances

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

definition (such as KEY qualifiers on properties).   Pegasus

Line 1479

Line 1531

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

</li>

includeQualifiers operation parameter is set.</li><li>LocalOnly option on instance

<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

Line 1493

Line 1543

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

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

specification for more information.</li>

<li>

MultiRequest Operations - Pegasus

MultiRequest Oprations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOFCompiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

</li>

<li>CIMOperation Trailer - Pegasus implements

chunking

based on the DSP0200 1.2.0 preliminary spec. including the operation trailer

defined in that specification Refer to bug

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

This trailer was completely removed from the DSP0200 1.2 final specification

as a non-compatible change so that if chunking is used Pegasus is returning

a noncompliant response to enumerate type requests.

</li>

</ol>

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

Platforms</a></h2>

Each OpenPegasus release lists as 'active' platforms those

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus code base

hardware/software platforms that have recognized ports for the Pegasus

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

code

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

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

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

regularly document issues and/or fix defects as the Pegasus

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

code base is changed. 

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

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

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

a group

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

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

database for a list of relevant defects that affect their platform.  

Pegasus cannot be

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

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

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

responsibility of the entity that packages and/or compiles OpenPegasus

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

for shipment or deployment, to read, and actively monitor the Pegasus bugzilla database for a list of relevant defects that affect their

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

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

of the release are reported in the second table.Actively Supported Platforms (Nightly Tests Reported for this release)

Pegasus release are:

<tbody>

Platform and

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

</td>

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

</td>

</tr>

HP-UX<o:p> PA_RISC and

Itanium</o:p>

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

</td>

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

</td>

</tr>

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

</td>

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

</td>

</tr>

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

</td>

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

</td>

</tr>

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

</td>

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

</td>

</tr>

Linux IA-32</td>

Linux IA-32<o:p></o:p>

gcc

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

</tr>

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

</td>

gcc

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

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

Platform and

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

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

</td>

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

Microsoft

Visual C++ Ver 6 and Microsoft .Net compiler Version.   Works on VC .NET 2003 (aka

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

</td>

</tr>

<tr>

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

Windows XP<o:p>, Windows

2003</o:p>

</td>

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

Note: Visual C++ Ver. 6 no longer being regular tested.

Microsoft

Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1<o:p></o:p>

</td>

</tr>

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

<td style="padding: 0.75pt; width: 126.75pt;" height="43" width="211"> MacOS version 10.2 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>HP OpenVMS Alpha

</big></td>

<td style="vertical-align: top;"> <big>HP C++ V6.5-042 for OpenVMS

Alpha and above</big> </td>

</tr>

<tr>

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

<td style="vertical-align: top;"><big> HP OpenVMS IA64</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

<td style="vertical-align: top;"><big>HP C++ V7.1-011 on OpenVMS IA64 and above</big>

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

</td>

</tr>

<tr>

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

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

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

</big></td>

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

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

Alpha</big></td></tr>

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

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

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

later required on OpenVMS IA64</big></td></tr>

<tr>

Windows 2000

</td>

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 style="vertical-align: top;"><big>Solaris 9

</td>

</big></td>

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

Note: Visual C++ Ver. 6 no longer being regular tested.

<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>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td><td><big>CC Compiler Sun Studio 5.11</big></td></tr>

</tbody>

</table>

Platform patches

Platform patches

The following is a list of platform

patches Pegasus requires.

The following is a list known of platform

patches Pegasus requires.

<ol>

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

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

database</a>.

with the keyword 2.6.0_APPROVED so that

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

all changes for this release can be found with the following bug search.

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

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

only for bugs and

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

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

new code

representing the work on PEPs done for Pegasus 2.6.  Therefore, a search of

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

the bugzilla base for bugs with the tag 2.6.0_Approved will yield all changes to

versions.  Therefore, a search of

the Pegasus CVS tree for Pegasus 2.6.0.

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

version

(ex. 

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

    - Changes for Pegasus 2.6.0 release (bugs Tagged

     - Changes for this release (bugs Tagged

2.6.0_APPROVED) 

2.10.0_APPROVED). The link is <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.10.0_APPROVED">

Pegasus 2.10.0_APPROVED bug list.</a>

Pegasus 2.6.0_APPROVED bug list</a>

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

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

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

The Pegasus project is controlled largely through a set of documents

The Pegasus project is controlled largely through the CVS repository and a set of documents

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

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

modified Pegasus functionality and for the definition and documentation

of releases.

of releases.The following documentation defines the characteristics of this

Pegasus release. The PEPs are available at

Specifically the following PEPs define the characteristics of this

Pegasus release. These PEPs are available on as

OpenPegasus Approved PEPs.</a><ol>

OpenPegasus Approved PEPs.</a>

<li>

OpenPegasus Release Definition/Status -  </li>No PEP (See Wiki Section <a href="http://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_9_x">OpenPegasus 2.10.x Release Status</a>) - A

<ol>

section in the Pegasus wiki is used

<li>

PEP 218 - OpenPegasus Release Definition - This PEP 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>

represent the Pegasus  functionality changes for this version of Pegasus.

OpenPegasus  Build and Configuration

Options  for Selected

Platforms -

<a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/*checkout*/pegasus/doc/BuildAndReleaseOptions.html?rev=1.18">CVS Respository Build And Release Options Document</a> -

In previous versions of Pegasus this

information was  releases as a Pegasus PEP. Starting with Pegasus 2.9.0

the information is located in the OpenPegasus CVS repository as <big>

pegasus/doc/BuildAndReleaseOptions.html</big>.</li>

<li>

PEP 277 -  OpenPegasus  Build and Configuration

OpenPegasus External Interfaces -

Options  for Selected

Platforms</li>

CVS Repository External Interfaces Document</a>- 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 repository as  pegasus/doc/EnternalInterface.html.

<li>

PEP 278 OpenPegaus 2.5 External Interfaces - Lists the public

OpenPegasus  SDK Packaging Definition - </li>

interfaces for clients and providers that are considered external and

therefore "frozen".

PEP 352</a> - Defines the

recommended set of files for inclusion in the OpenPegasus SDK

</li>

<li>

PEP 279 - OpenPegasus  SDK Packaging Definition - Defines the

Pegasus  Runtime Packaging Definition -

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

PEP 351</a> - </li>Defines the

recommended set of files for inclusion in this OpenPegasus release.

<li>PEP 280 - Pegasus  Runtime Packaging Definition - Defines the

recommended set of files for inclusion in this OpenPegasus release.</li>

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

<li>Pegasus Release Notes -  PEP 355

- (This document is located in the

approved PEP

repository and the OpenPegasus source tree root directory)

repository and the OpenPegasus source tree root directory (<big>pegasus/ReleaseNotes.htm</big>)

</li>

<li>PEP 289  - Pegasus readme.txt for this release (Located in PEP repository

</ol>

and also in the OpenPegasus

source

tree root directory).</li>

</ol>

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

The following documentation is available for the this Pegasus

release:

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

The following documentation is available for the this Pegasus

release:

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

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

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

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

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

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

<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

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

Providers - </li>Readme.html in the Pegasus source tree Root Directory, API

documentation, and documentation from the Pegasus Technical Workshop

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

which is available on the Pegasus web site.

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

Clients - API documentation and the documentation on the Pegasus

Clients - </li>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;">Compiler operation and

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

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

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

<o:p></o:p>

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with

this work for additional information regarding copyright ownership.

Each contributor licenses this file to you under the OpenPegasus Open

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

License.

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

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

copy of this software and associated documentation files (the "Software"),

Group; VERITAS Software Corporation; Intel Corp.

to deal in the Software without restriction, including without limitation

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

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

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

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

The above copyright notice and this permission notice shall be included

obtaining a copy  of this software and associated documentation files (the

in all copies or substantial portions of the Software.

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

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

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

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

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

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

the Software is furnished 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,

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

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE

SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE

SOFTWARE IS PROVIDED  "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS 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
changed lines
	Added in v.1.17

No CVS admin address has been configured