pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.12, 2007/10/16 17:27:28

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>

Line 962

Line 961

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

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

</w:Compatibility>

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

</w:WordDocument>

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

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

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

PEP #: 306

PEP #: 355

Title: Release

Notes for OpenPegasus 2.7.0

Notes for OpenPegasus version 2.10.0

Created: 3 October 2007

Created: 21 January 2010

Authors: Karl Schopmeyer

Line 1029

Line 1020

Version History:

<tbody>

Line 1071

Line 1062

<o:p> </o:p>3

October 2007

21 January 2010

</td>

Line 1086

Line 1077

Initial

Submission<o:p>

Submission <o:p>

</o:p>

</td>

Line 1095

Line 1086

<tr>

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

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

<td style="padding: 0.75pt;" height="21">Incorporate data from 2.6.1

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

release notes. Fix per comments in 1.0</td>

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

</tr>

Line 1110

Line 1101

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

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

<td style="padding: 0.75pt;" height="21">Comments from V 1.1 and add

existing document links. Add pep 302 to enhancements</td>

</tr>

Line 1123

Line 1113

<td style="padding: 0.75pt;" align="center" height="21">15 October 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">Add final links</td>

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

this PEP - This version approved</td>

</tr>

Line 1148

Line 1139

</table>

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

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

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

style="color: black;">

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

width="100%"></div>

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

<ol>

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

Line 1176

Line 1163

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

with DMTF Specifications</a></li>

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

<li> <a

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

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

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

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

Documentation</a></li>

Line 1189

Line 1175

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

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

each feature.Pegasus 2.10.0

is a major release, extending Pegasus 2.6 in selected

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

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 PEP for each change defined:

Table of Major Changes for this Release

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

borderColorLight=#CCCCCC border=1 width="82%">

<tbody>

<TBODY>

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

<TH bgColor=#00FFFF>Description of Change</TH>

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

<TH bgColor=#00FFFF width="128">Posted PEP Version</TH>

</tr>

</TR>

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

<TD align="left" width="75%">Add Platform support IBM i5/PASE - Portable Application

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

Solutions Environment (PASE)</TD>

WS_Management changes to Pegasus 2.9.0 to incorporate more WS_Management

functionality.</td>

1.6</a></TD>

</TR>

2.2</a> </td>

</tr>

<tr>

<TD align="left" width="75%">Reduce the Amount of CIM Server code that runs Privileged

(Privilege Separation)</TD>

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

</tr>

1.8</a></TD>

</TR>

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

<TD align="left" width="75%">Add Support for IPv6 - Stage 1 (Note: This functionality

</tr>

was made available but normally disabled

Pegasus 2.6.1)</TD>

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

1.2</a></TD>

</TR>

1.1</a></td>

</tr>

<TD align="left" width="75%">Add IPV6 Support for SNMP Indication Handler

and include NET-SNMP indication handler in Linux RPM </TD>

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

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

1.1</a></TD>

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

</TR>

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

update SystemName property in indication filter/handler and

<TD align="left" width="75%">Enable Remote CMPI for Windows</TD>

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

1.2</a></TD>

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

</TR>

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

<TD align="left" width="75%">Enhanced Log File Support</TD>

</tr>

1.0</a></TD>

</TR>

</tr>

</tbody>

<TD align="left" width="75%">Add support for certificate-based authentication audit

</table>

logging</TD>

1.5</a></TD>

</TR>

<TD width="7%">Bugzilla 6466</TD>

<TD align="left" width="75%">Add two new trace components to facilitate

triage of indication delivery issues</TD>

Bug 6466</a></TD>

</TR>

</TBODY>

</TABLE>

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

Line 1279

for more information.

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

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but it

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

Notes

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

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

Line 1347

Line 1314

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

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;">cimcli ns -l [3ffe:1:2:1]</div>

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

or

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

<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

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

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

6 Addressing Architecture</a>

and <a

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

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:

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.

Line 1383

Line 1348

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

/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

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

described in

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

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

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

bug 6586</a>

and<span

and

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

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

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

Line 1415

Line 1375

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

style="font-weight: bold; ">ipv6.exe tool to install, uninstall, and

query

your IPv6 configuration. For example:

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

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

ipv6 if</div>

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.

Line 1431

Line 1390

For more information on

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

the document

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

IPv6

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

Line 1448

Line 1406

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

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

Line 1459

Line 1417

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

upgrading to this OpenPegasus release.

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

borderColorLight=#CCCCCC border=1 width="80%">

<tbody>

<TBODY>

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

<TH bgColor=#00FFFF width=10%>Bugzilla #</TH>

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

<TH bgColor=#00FFFF>Description</TH>

</tr>

</TR>

<TD align="left">HP-UX only: Introduction of the "explicit" keyword in CIMClass.h and CIMInstance.h may introduce

</tr>

a compile error in some code. Specifically, a compiler-supplied automatic conversion from CIMObject

type to CIMClass or CIMInstance has been removed. The cast operation must be explicitly specified.

</TD>

</tr>

</TR>

<TD>

</tr>

WIPCR00430 recommends an unquoted charset parameter in Content-type header. See the writeup in this bug for a discussion of the validation of the charset parameter in various OpenPegasus releases. In 2.7 we perform "extended" validation that should ignore differences based on whitespace or quotes. The CR recommendation is to not use quotes on the charset parameter, but only at a time when it is expected that all CIMOMs have been updated to accept the charset parameter with or without quotes.</TD>

</TR>

</tr>

<TD>

The MOF Compiler now rejects some property values that are invalid according to the DMTF specification that it previously accepted.</TD>

</TR>

</TBODY>

</tr>

</TABLE>

</tbody>

</html>

</table>

<h2>OpenPegasus Relationship to

CIM/WBEM Standards</h2>

Pegasus was designed and implemented to comply with the DMTF

Line 1508

Line 1464

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

Line 1484

</tr>

<tr>

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

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

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

</tr>

</tbody>

</table>

Line 1551

Line 1507

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

<font

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

face="Courier New" size="2"> 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 1575

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,

</li>

the normalizer does apply qualifiers to returned instances if the

<li>LocalOnly option on instance

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

Operations - With the 1.1 version of Specification for CIM

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

GetInstance and Enumerate Instances operations was modified. This change

Line 1595

Line 1551

MOF Compiler namespace pragma - The

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

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

<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

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

code

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

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

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

regularly document issues and/or fix defects as the Pegasus

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

code base is changed. 

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

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

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

a group

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

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

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

Pegasus cannot be

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

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

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

responsibility of the entity that packages and/or compiles OpenPegasus

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

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

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

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:

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

cellpadding="0" cellspacing="1">

<tbody>

<td

style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;"

height="26">

Platform and

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

</td>

<td

style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;"

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

height="26">

Compilers<span

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

</td>

</tr>

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

HP-UX<o:p> PA_RISC and

Itanium</o:p>

</td>

HP <span

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

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

</td>

</tr>

<span

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

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

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

</td>

<span

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

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

</td>

</tr>

<span

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

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

</td>

<span

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

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

</td>

</tr>

Line 1675

Line 1619

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

</td>

<span

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

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

</td>

</tr>

Linux IA-32</td>

<span

gcc

style="color: black;">gcc

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

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

</tr>

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

</td>

<span

gcc

style="color: black;">gcc

(versions 3.xx, 4.xx)

(versions 2.9x, 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>

Windows 2000

Platform and

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

</td>

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

</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 XP, Windows 2003

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

</td>

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

Line 1719

Line 1672

</tr>

<tr>

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

<td style="vertical-align: top;"><big>Solaris 8</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 or later required for OpenVMS

Alpha</big></td>

</tr>

<tr>

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

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

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

style="color: rgb(0, 0, 0);">HP C++ V7.3-023 or

later required<font

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

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>

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

The following is a list known of platform

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

patches Pegasus requires.

<ol>

<li>

<font

RHAS

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

2.1 needs the update to fix Red Hat Bugzilla 98815.</li>

<li>

RHEL 4.4 multithreading bug in

Line 1775

Line 1730

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

Line 1787

Line 1740

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

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

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

were documented through bugs.  Bugs reports were filed not only for bugs and

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

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

only for bugs and

representing the work on PEPs done for Pegasus 2.6 and all subsequent versions.  Therefore, a search of

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

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

new code

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

versions.  Therefore, a search of

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

version

(ex. 

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>) will yield all changes to

<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.7.0 release (bugs Tagged

     - Changes for this release (bugs Tagged

2.7.0_APPROVED) 

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

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

Pegasus 2.10.0_APPROVED bug list.</a>

<h2><a

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

name="Pegasus Release Control and Version Definition Documentation">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 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 at

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

section in the Pegasus wiki is used

<ol>

<li>

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

<li>

OpenPegasus  Build and Configuration

<a href="http://www.openpegasus.org/pp/uploads/40/14873/PEP292_RecommendedReleaseOptions.htm">PEP 292</a> -  OpenPegasus  Build and Configuration

Options  for Selected

Platforms</li>

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>

<a href="http://www.openpegasus.org/pp/uploads/40/14874/PEP293_ExternalInterface2.7.htm">PEP 293</a> - OpenPegasus 2.7 External Interfaces - Lists the public

OpenPegasus External Interfaces -

interfaces for clients and providers that are considered external and

therefore "frozen".

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>

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/14875/PEP294_SDKFile2.7.0.htm">PEP 294</a> - OpenPegasus  SDK Packaging Definition - Defines the

OpenPegasus  SDK Packaging Definition - </li>

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

PEP 352</a> - Defines the

recommended set of files for inclusion in the OpenPegasus SDK

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/14877/PEP295_RuntimePackaging2.7.0.htm">PEP 295</a> - Pegasus  Runtime Packaging Definition - Defines the

Pegasus  Runtime Packaging Definition -

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

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

recommended set of files for inclusion in this OpenPegasus release.

<li>PEP 306 - 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>

</ol>

</ol>

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

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

The following documentation is available for the this Pegasus

The following documentation is available for the this Pegasus

release:

release:

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

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

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

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

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

documentation, and documentation from the Pegasus Technical Workshop

which is available on the Pegasus web site.</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;">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

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with

this work for additional information regarding copyright ownership.

<span

Each contributor licenses this file to you under the OpenPegasus Open

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

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

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

License.

style="color: black;">

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

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

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

width="100%">

to deal in the Software without restriction, including without limitation

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

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

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

Open Group; VERITAS Software Corporation; Intel Corp.

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

The above copyright notice and this permission notice shall be included

Permission is hereby granted, free of charge, to any

in all copies or substantial portions of the Software.

person obtaining a copy  of this software and associated

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

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

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

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

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

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

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

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

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

to do so, subject to the following conditions:

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>

</body></html>

</html>

Legend:

Removed from v.1.12
changed lines
	Added in v.1.17

No CVS admin address has been configured