pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.15 and 1.21

version 1.15, 2008/12/18 16:40:58

version 1.21, 2015/03/18 17:07:01

Line 1

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

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

<head>

<style>

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

</style>

Line 962

Line 973

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

<o:DocumentProperties> <o:Author>IBM_User</o:Author> <o:LastAuthor> </o:LastAuthor> <o:Revision>4</o:Revision> <o:TotalTime>211</o:TotalTime> <o:Created>2004-04-05T14:13:00Z</o:Created> <o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>5026</o:Words> <o:Characters>28651</o:Characters> <o:Company>IBM</o:Company> <o:Lines>238</o:Lines> <o:Paragraphs>67</o:Paragraphs> <o:CharactersWithSpaces>33610</o:CharactersWithSpaces> <o:Version>10.4219</o:Version> </o:DocumentProperties></xml><![endif]--><!--[if gte mso 9]><xml>

<w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:Compatibility> <w:ApplyBreakingRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument></xml><![endif]-->

<o:smarttagtype

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

<o:smarttagtype

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

namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml>

<o:DocumentProperties>

<o:Author>IBM_User</o:Author>

<o:LastAuthor> </o:LastAuthor>

<o:Revision>4</o:Revision>

<o:TotalTime>211</o:TotalTime>

<o:Created>2004-04-05T14:13:00Z</o:Created>

<o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved>

<o:Pages>1</o:Pages>

<o:Words>5026</o:Words>

<o:Characters>28651</o:Characters>

<o:Company>IBM</o:Company>

<o:Lines>238</o:Lines>

<o:Paragraphs>67</o:Paragraphs>

<o:CharactersWithSpaces>33610</o:CharactersWithSpaces>

<o:Version>10.4219</o:Version>

</o:DocumentProperties>

</xml><![endif]--><!--[if gte mso 9]><xml>

<w:WordDocument>

<w:SpellingState>Clean</w:SpellingState>

<w:GrammarState>Clean</w:GrammarState>

<w:Compatibility>

<w:ApplyBreakingRules/>

</w:Compatibility>

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

</w:WordDocument>

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

</head>

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

style="color: black;">

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

OpenPegasus Enhancement

width="100%"></div>

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

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

align="center">Pegasus

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

PEP #: 368

PEP #: 332

Title: Release

Notes for OpenPegasus 2.8.0

Notes for OpenPegasus version 2.14.0

Created: 20 November 2014

Created: 21 June 2008

Authors: Karl

Schopmeyer

Authors: Karl Schopmeyer

Status:  draft

Version History:

<tbody>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

</tr>

0.99<o:p></o:p>

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

</td>

12 Nov. 2014

21 June 2008

</td>

Karl Schopmeyer

Karl Schopmeyer

</td>

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

Initial

Submission<o:p>

</o:p>

</td>

</tr>

<tr>

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

</td>

<td style="padding: 0.75pt;" align="center" height="21">14 March 2015

</td>

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

</td>

<td style="padding: 0.75pt;" height="21">Update to finish the document (approved as bug 9684)

</td>

</tr>

</td>

</td>

</td>

</td>

</tr>

<tr>

</td>

</td>

</td>

</td>

</tr>

</tr>

</tbody>

</table>

Abstract: This document defines the release notes for the 2.14.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

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

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

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

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>

Pegasus overall status by release is defined by  a

Nothing changes for clients that do not support HTTP cookies (RFC 6465) -

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

their requests are authenticated as usual, either using Basic or Negotiate

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

authentication mechanisms.

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

The timeout for a session is determined by the runtime parameter httpSessionTimeout. If this runtime parameter is set to zero the HTTP cookies option is disabled.

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

areas as described in the Pegasus  PEP defining this release

This option has proven to represent a significant improvement in performance over using PAM for every client operation.

.

<h3>WEBAdmin (OpenPegasus 2.14.0)</h3>OpenPegasus has

included on an experimental basis a web server that acts as an

The major areas of development for this release  were as follows. For

adminstration tool to replace the command line tools.  This option

more information access the PEP for each change defined:

presents the

same information as the major command line tools as web pages so that

parameters can be modified without using the command line tools. 

Table of Major Changes for this Release

It is compiled by

default and may be disabled with the build option

PEGASUS_ENABLE_PROTOCOL_WEB=false. See the file readme.webadmin in the

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

OpenPegasus

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

source tree for more detailed information on using WEBAdmin.

<TBODY>

Note: This option is considered experimental for 2.14

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

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

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

</h3>

</TR>

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

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

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

<TD align="left" width="75%">Memory Resident Repository</TD>

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

significant performance improvements.

1.3.1</a></TD>

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

</TR>

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

<tr>

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

311</TD>

While testing OpenPegasus with OpenSLP 2.0 the OpenPegasus team found two

<TD align="left" width="75%">WS-Management Support in CIM Server</TD>

issues with this version of OpenSLP.  The patches documented below

allow this version of OpenSLP to work with OpenPegasus

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

1.4</a></TD>

a BUFFER_OVERFLOW exception occurs.  This is because UDP cannot

</tr>

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

according to the specification, OpenSLP should automatically switch to

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

<TD align="left" width="75%">Pluggable Provider Managers - Enhancement</TD>

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

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

1.2</a></TD>

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

</TR>

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

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

Effective with the release of OpenPegasus  2.13 the "interop"

<TD align="left" width="75%">Tracing in OpenPegasus - Enhancement</TD>

namespace support for existing or

older repositories which used

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

1.0</a></TD>

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

</TR>

the repository from "root/PG_InterOp" to

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

9414</a> (PEP304) for

<TD align="left" width="75%">Profile Registration Profile Support</TD>

details.

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

1.3</a></TD>

to be

</TR>

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

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

"root/PG_InterOp"

<TD align="left" width="75%">Track Generated Indications Data</TD>

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

"interop".

1.2</a></TD>

Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable to

</TR>

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

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

involving editing one file and rebuilding OpenPegasus was defined as a

<TD align="left" width="75%">DMTf Indication Profile Implementation, Stage

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

1 (DMTF DSP 1054)</TD>

wiki faq</a>s.

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

1.0</a></TD>

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

</TR>

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

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

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

<TD align="left" width="75%">Track Generated Indications Data</TD>

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

defined OpenPegasus interface, to continue to work with each version

upgrade of OpenPegasus.

1.2</a></TD>

</TR>

Effective OpenPegasus 2.12.0 a new build variable was defined 

</TBODY>

(PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus builder to define

</TABLE>

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

</html>

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

The status of several components of Pegasus functionality change status

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

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

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

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

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

release to this release</a> on the

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

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

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

approach for implementations starting a new repository.

Finally, a significant number of internal changes and corrections were made

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

In order to supexport PEGASUS_CLIENT_TRACE=keyword:keywordport users with

for more information.

existing repositories, in 2.13.0,  migration of existing repositories

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

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

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

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but it

for the interop namespace "root/PG_InterOp" to 

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

the prefered name "interop".

Notes

IPv6 is short for "Internet

NOTE: If the interop namespace

Protocol

name is redefined with PEGASUS_INTEROP_NAMESPACE clients using the

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

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

to replace the current version Internet Protocol, IP Version 4

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

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

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

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

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

PEP

<h3>Configure Script to Control OpenPegasus Builds (OpenPegasus

291</a>.

2.13.0)(Bug 9592)</h3>

The IPv6 support in OpenPegasus is

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

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this

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

variable is "true"; setting this to

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

standard build environment.  However, because OpenPegasus must build

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

configuration tool set, this is an OpenPegasus defined configure

script.  The first very experimental version is part of OpenPegasu

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

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

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

environment variable with options in the pegasus/configure script where

those options are comatible with the Linux standard for defining configure

options and those options control the entire build process including placement

of output and choice of build options.

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

OpenPegasus has

long contained a hidden build controlled function to allow tracing at

the client through an environment variable

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

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

slightly changed

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

environment variable was:

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

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

<pre> export PEGASUS_CLIENT_TRACE=con</pre>

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

2.7.0)</h3>

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but

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

Release Notes

IPv6 Support for OpenPegasus is documented in

PEP 291</a>.

The IPv6 support in OpenPegasus is controlled by the PEGASUS_ENABLE_IPV6

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

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

The following subsections provide

The following subsections provide some information on IPv6 support for the

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

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

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

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

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

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

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

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

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

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

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

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

Listener components. For more information on IPv6 support for your

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

specific platform, refer to the documentation for that platform.

All OpenPegasus externals that support eitcompilerher a hostname or an IP

All OpenPegasus externals that

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

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

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

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

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

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

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

address must be specified without brackets. For example, the

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

OpenPegasus osinfo client (which returns information about the OS

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

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

interface would be specified as:

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>

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

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

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

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

But the cimcli command, which

delimited with brackets, for example:

takes

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

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

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

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

<div style="margin-left: 40px;">cimcli ns -l [3ffe:1:2:1]</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

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

specifying

RFC

IPv6 addresses, refer to <a

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

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

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

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

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

contain IPv6-ready kernels, the

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

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

module is not loaded automatically on startup.

that this module is not loaded automatically on startup.

Note:

Note: you shouldn't use

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

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

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

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

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

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

to use series 2.6.x now.

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

To check whether your current

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

running

short automated test looks like:

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>

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

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

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

For more information on

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

enabling

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

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

Documentation Project's IPv6 HOWTO</a>.

Warning:

Warning: There is currently an

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

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

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

RHEL5 and SLES10 systems. This problem is described in

described in <span

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

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

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

bug

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

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

bug 6586</a>

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

be significantly impacted in these environments.

and<span

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

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

Microsoft provides supported IPv6 implementations for Windows Server 2003,

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

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

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

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

On Windows XP, you can use the <span

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

On Windows XP, you can use the ipv6.exe

query

tool to install, uninstall, and query your IPv6 configuration. For

your IPv6 configuration. For example:

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

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

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

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

Note that the OpenPegasus IPv6 support has not yet been tested

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

on Windows Vista or Windows Server 2008.

Windows Server 2008.

For more information on

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

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

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

the document

<h4>Testing  OpenPegasus IPv6 support</h4>

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

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

IPv6

IndicationStressTest test clients were modified to run tests using the

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

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

<h4>Testing your OpenPegasus IPv6

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

support</h4>

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

As part of the OpenPegasus

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

automated tests, the TestClient, g11ntest, and IndicationStressTest

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

(::1) if PEGASUS_ENABLE_IPV6=true.

You can also perform manual

tests

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

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

running on the WBEM standard http port of 5988:

osinfo -h ::1</div>

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

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

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

Support for forward-compatibility is a fundamental design principle for the

Considerations</a></h2>

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

Support for forward-compatibility is a fundamental design principle for

Providers or Clients, using only the externally defined OpenPegasus interface,

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

to continue to work with a minor version upgrade of OpenPegasus. However, there

OpenPegasus providers or clients, using only the externally defined

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

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

significantly affects interoperability) that may require the Community to make

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

potentially incompatible changes. The following table contains a list of defect

non-compliance with a standard that significantly affects

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

interoperability) that may require the community to make potentially

upgrading to OpenPegasus 2.8.0.

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

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

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

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

upgrading to this OpenPegasus release.

<TBODY>

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

<tbody>

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

</TR>

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

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

</tr>

<TD align="left">In Pegasus 2.8, the behavior of the setName() method is

changed in the Pegasus C++ interface for the CIM data type model. For

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

data types that use a shared representation model, the setName() method

8830</a></td>

now throws an Exception when the object is "contained" by another CIM

<td align="left">Starting

data object.

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

Specifically, setName() may throw the new exception in these cases:

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

CIMProperty contained by CIMClass, CIMInstance, and CIMObject

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

CIMQualifier contained by CIMClass, CIMInstance, CIMObject,

on performance the CIMInstance::filter() and

CIMProperty, CIMParameter, and CIMMethod

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

CIMMethod contained by CIMClass

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

CIMParameter contained by CIMMethod</TD>

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

</TR>

allow users to actually filter properties from an instance in a

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

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

<TD>

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

In Pegasus 2.8, the C++ CMPI IndicationMI function

CIMServer will do the filtering but allows the provider to prefilter

signatures have been changed to fit the CMPIIndicationMIFT definitions.

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

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

The CmpiResult parameter in CmpiIndicationMI authorizeFilter, mustPoll,

</td>

activateFilter and deActivateFilter have been removed cause it does not

</tr>

exist in the CMPIIndicationMIFT definitions.

The missing CmpiContext parameter and CMPIStatus have been added to

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

enableIndications and disableIndications.</TD>

9369</a>

</TR>

</td>

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

fixed in OpenPegasus 2.13.0. Reregistering of an

<TD>

indication provider requires that the  cimserver be restarted

In Pegasus 2.8, the CMPI property filter handling has

to send the enableIndication request to the providers. This issue

been improved in performance.

has existed starting with OpenPegasus 2.10 to  version 2.12.

Two things have changed in the behaviour of the property filter

If the cimserver is not restarted the indication will not be

handling:

enabled for the reregistered provider. </td>

* Repeated applying of property filters onto the same instance will now

</tr>

only leave the properties which build the most common dominator on the

</tbody>

instance.

</table>

* It is not possible anymore to add properties not defined for the

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

corresponding class to an instance.</TD>

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

</TR>

specifications The following table defines the level of the DMTF

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

<TD>

In Pegasus 2.8, the algorithm used by the MessageLoader

to search the accept language list to determine which message file to

open was changed. Before Pegasus 2.8, the Message Loader used the

following algorithm:

1.) The Message Loader will search the accept

language list for an exact match. The first exact match found will

be returned.

2.) If an exact match does not exist, the Message Loader will return

an ICU "fallback" match for the first entry in accept language list.

3.) If an ICU "fallback" match does not exist for the first entry,

it will return the ROOT resource bundle.

</blockquote>

With the release of Pegasus 2.8, the Message Loader will

not longer return ICU "fallback" matches. In addition, it will give

preference to the default process locale over the ROOT resource bundle.

In Pegasus 2.8, the Message Loader has been modified to use the

following algorithm:

<ul>

1.) The Message Loader will search the accept

language list for an exact match. The first exact match found will

be returned.

2.) If an exact match does not exist, the Message Loader will return

an exact match for the default process locale.

3.) If an exact match for the default process locale is not found,

it will return the ROOT resource bundle.

</ul>

</TD>

</TR>

7501</a></TD>

<TD>

Since OpenPegasus 2.7.2 the way CMPI_chars are added to

arrays was corrected to follow the CMPI specification. Following the

CMPI specification means that CMPI_chars are not to be dereferenced,

contrary to all other subtypes of CMPIValues.

If you experience an error since switching over to OpenPegasus 2.8

saying "The byte sequence starting at offset xx is not valid UTF-8

encoding", this is an indication for a missing update in the provider

code.

The update for a C CMPI provider using arrays of CMPI_chars is to use a

char* now as input parameter instead of a char**.

CMPI Example:

char* role = "Unknown";

array = CMNewArray(_broker,1,CMPI_chars,rc);

from:

CMSetArrayElementAt(array,0,(CMPIValue*)&role,CMPI_chars);

to:

CMSetArrayElementAt(array,0,(CMPIValue*)role,CMPI_chars);</TD>

</TR>

</TBODY>

</TABLE>

</html>

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

Line 1583

Line 1770

</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%">Version 1.4, 26 August 2013

</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%">Version 2.4.0 16 January 2014

</td>

</tr>

<tr>

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

Line 1603

Line 1792

</tr>

<tr>

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

<td width="33%">2.17.1 Final,  14 Dec 2007( default) </td>

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

</tr>

<tr>

<td>DSP0226 - Web Services for Management

</td>

<td>Version 1.1.1

</td>

</tr>

<tr>

<td>DSP0227 - WS-Management CIM Binding Specification

</td>

<td>Version 1.2.0

</td>

</tr>

<tr>

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

<td>Version 1.1.0

</td>

</tr><tr>

<td style="vertical-align: top;">DSP0212 - Filter Query Language

</td>

<td style="vertical-align: top;">Version 1.0.1, 22 August 2013

</td>

</tr>

</tbody>

</table>

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

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

Exceptions to

Profiles Supported</h2>

DMTF Specifications</a></h2>

It is a major goal

Today OpenPegasus includes support for several DMTF profiles including:

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

specifications.  However, today there are a number of known

differences. 

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

<ol>

<li>Provider Registration - Pegasus supports registration

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

through a set of Pegasus Provider registration classes rather than

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

support the DMTF defined Provider Qualifier. Pegasus will not support

SNIA SMI Indication profile it also supports this profile. This

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

profile is enabled by compiling OpenPegasus with the buld variable

provider registration.  This is not a deviation from the

PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

specifications but is a different method of registration than many CIM

</li>

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

<li>SNIA Profile Registration 1.0.0

<li>Indications -Today Pegasus supports process

</li>

indications and lifecycle indications when defined specifically by

<li>SNIA Server 1.1.0 & 1.2.0

</li>

</ol>

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

to DMTF Specifications</a></h2>

It is a major goal of the OpenPegasus project to both drive and utilize

the DMTF CIM/WBEM specifications.  However, today there are a number

of known differences.  As of this release, some of the differences

include the following:

<ol>

<li>Provider Registration

- Pegasus supports registration through a set of Pegasus Provider

registration classes rather than support the DMTF defined Provider

Qualifier. Pegasus will not support this qualifier in the future. See

the readme for more information on provider registration.  This is

not really a deviation from the specifications since there is no

specification or profile for provider registration today but is a

different method of registration than many CIM Servers and means that

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

<li>Lifecycle Indications -Today Pegasus supports process

iPegasusndications and lifecycle indications when defined specifically by

providers. Pegasus does not support lifecycle indications if they are

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

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

color="#ff0000">  For

For more

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

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

<li>

option

<font

on Instance Operations

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

- The DMTF specifications have deprecated the use of qualifiers on

option on Instance Operations

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

stated specifically that the client should NOT depend on the

The DMTF specifications have deprecated the use of qualifiers on

includeQualifiers parameter of the CIM/XML instance operations

instance operations with the 1.2 CIM Operations Specification. 

returning qualifiers.  Some CIM Client implementations expect

Some CIM Client implementations expect instances

instances returned from the CIM Server to include the qualifiers

returned

defined in the class definition (such as KEY qualifiers on

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

properties).   Pegasus today expects the provider to

definition (such as KEY qualifiers on properties).   Pegasus

complete the qualifiers on instances in accordance with the

today expects the provider to complete the qualifiers on instances in

specification and generally the interpretation is that Pegasus

accordance with the specification and generally the interpretation is

applies class level qualifiers when the includeInstance parameter is

that Pegasus applies class level qualifiers when the includeInstance

supplied on instance operations.  However, Pegasus today is

parameter is supplied on instance operations.  However, Pegasus

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

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

depend on Pegasus accurately honoring the includeQualifier parameter

should NOT depend on Pegasus accurately honoring the includeQualifier

for instance operations.  In the future it is expected that

parameter for instance operations.  In the future it is expected

Pegasus will deprecate the use of qualifiers on instance operations

that Pegasus will deprecate the use of qualifiers on instance

completely.  When Pegasus uses object normalization, the

operations completely.

normalizer does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.</li>

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

version of Specification for CIM Operations over HTTP, the definition

of the LocalOnly parameter for the GetInstance and Enumerate Instances

operations was modified. This change was incorrect, resulted in

reduced functionality and introduced a number of backward

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

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

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

properties returned. See Appendix C of this specification for more

information.</li>

<li>MultiRequest CIM/XML Option

-  Pegasus does not support the DMTF defined MultiRequest

Operation option (See DSP0200).

</li>

<li>LocalOnly option on instance

<li>MOF Namespace Pragma -The

Operations - With the 1.1 version of Specification for CIM

Pegasus compiler does not support the namespace pragma defined in DSP

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

0004. Namespaces for the OpenPegasus repository are defined through

GetInstance and Enumerate Instances operations was modified. This change

arguments for the MOF Compiler

was incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

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

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

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

specification for more information.</li>

<li>

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

<li>CIMOperation Trailer - Pegasus implements chunking based on

MOF Compiler namespace pragma - The

the DSP0200 1.2.0 preliminary spec. including the operation trailer

Pegasus compiler does not support the namespace pragma.

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

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

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

is used Pegasus is returning a noncompliant response to enumerate type

requests. </li>

<li>Whitespace in XML value Element

- Pegasus trims the leading and trailing whitespace from XML value

elements that are of the Type String.  This behavior is

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

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

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

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

documented bugs in Pegasus such as this that the OpenPegasus team

feels cannot be incorporated into the code until a major version

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

<li>modifyInstance operation behavior

in the Pegasus repository does not match the DMTF specification.

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

all properties rather than just the properties supplied with the

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

for more information.</li>

<li>OpenPegasus Interop Namespace

- The default interop namespace name in OpenPegasus is

"root/PG_Interop".  In versions of OpenPegasus prior to 2.12.0

this could be changed during build by modifying a string definition in

the code. Effective version 2.12.0 this  has become a build option

with the build configuraton environment variable

PEGASUS_INTEROP_NAMESPACE = <name for this namespace> however,

the default if built without this change is still "root/PG_InterOp".

Effective with OpenPegasus 2.13.0 the reupgrade utility has been

extended to allow existing repositories to be converted from the use of

"root/PG_Interop" to "interop" (See discussion above).  The

default in the CVS source code is still "root/PG_InterOp".

</li>

<li>CIMOperation Trailer - Pegasus implements

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

chunking

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

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

- If requests or responses include properties or parameters with

defined in that specification Refer to bug

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

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

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

accepted because these special strings are not understood by the

This trailer was completely removed from the DSP0200 1.2 final specification

decoder on Windows.</li>

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

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

a noncompliant response to enumerate type requests.

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

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

Today the DMTF Specification DSP0201 allows only numeric information

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

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

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

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

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

Covered properties (properties which have the same name in a

superclass and subclass without overridding the property in the

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

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

general agreement is that the requirement itself is not supportable

and particularly not with the existing OpenPegasus APIs. 

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

CIM 3.0).</li>

<li>FQL Query Language

(bug 9956) incorporated has some limitations with respect to the DMTF

defined Query Language (does not support full regex defined in the

specification and does not support embedded instance comparison).

</li>

</ol>

<h2>OpenPegasus <a

name="Supported Platforms">Supported

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

Platforms</a></h2>

Each OpenPegasus release lists as 'active' platforms those

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

Each OpenPegasus release lists as 'active' platforms those

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

hardware/software platforms that have recognized ports for the Pegasus

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

code 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 code base is

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

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

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

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

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

operation of  Pegasus cannot be assured.  In all cases,

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

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

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

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

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

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

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

relevant defects that affect their platform.   The platforms

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

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

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

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

of the release are reported in the second table

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

Actively Supported Platforms (Nightly Tests Reported for this release

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

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

cellpadding="0" cellspacing="1">

Actively Supported Platforms (Nightly Tests Reported for this release)

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

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

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

</td>

</tr>

<span

Linux

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

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

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 1753

Line 2031

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

</td>

<span

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

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

</td>

</tr>

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

Linux IA-32</td>

IA-32</td>

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

<span

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

style="color: black;">gcc

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

</tr>

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

</td>

<span

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

style="color: black;">gcc

(versions 2.9x, 3.xx, 4.xx)

</td>

</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 style="vertical-align: top;"><big>HP OpenVMS 8.3 or later 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 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;">XL C/C++ from z/OS Version

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

1.7 and up</td>

Version 1.7 and up</td>

</tr>

</tbody>

</table>

Platforms no Actively supported for this release (No

current Nightly Build Test Results

Platforms not Actively supported for this release (No

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

current Nightly Build Test Results)

cellpadding="0" cellspacing="1" id="table2">

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

<tr>

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

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

</td>

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

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

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

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

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

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

the Windows. </td>

</td>

</tr>

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

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

higher</td>

</tr>

<tr>

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

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

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

8</big></td>

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

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

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

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

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

be 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>GNU  2.95.3, Sun WorkShop

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

</td>

</tr>

<tr>

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

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

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

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

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

for OpenVMS Alpha</big></td>

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

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

<h3>Platform patches </h3>

<font

The following is a list known of

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

platform patches Pegasus requires.

patches Pegasus requires.

<ol>

<li>

<li> RHAS 2.1 needs the update to

fix Red Hat Bugzilla 98815.

<font

</li>

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

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

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

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

<li>

</li>

RHEL 4.4 multithreading bug in

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

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

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

RHEL 4.5</li>

Hat bug 248052)</li>

<li>

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

Red Hat and SUSE Linux

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

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

Further information regarding Pegasus support on IBM platforms can be

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

Further information regarding Pegasus support on HP platforms can

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

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

The OpenPegasus Bugzilla database documents defects found in Pegasus

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

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

database</a>.

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

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

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

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

documented through bugs. Therefore all source code changes to OpenPegasus

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

are documented through bugs providing a complete history of changes and

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

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

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

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

(ex. 

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

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

2.6.0_APPROVED</a>,

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

2.6.1_APPROVED</a>,

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

<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

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

the Pegasus CVS tree for that Pegasus release.

release.

     - Changes for this release (bugs Tagged

     - Changes for Pegasus 2.8.0 release (bugs Tagged

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

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

Pegasus 2.13.0_APPROVED bug list.</a>

Pegasus 2.8.0_APPROVED bug list</a>

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

Control

<h2><a

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

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

The OpenPegasus project is controlled largely through the CVS repository

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

The Pegasus project is controlled largely through a set of documents

mechanism for new and modified Pegasus functionality and for the

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

definition and documentation of releases.

modified Pegasus functionality and for the definition and documentation

of releases.

The following documentation defines the characteristics of this Pegasus

release. The documents are available in the OpenPegasus CVS

Specifically the following PEPs define the characteristics of this

repository.

Pegasus release. These PEPs are available at

<ul>

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

OpenPegasus Approved PEPs.</a>

2.13.x

Release Status</a>) - A

section in the Pegasus wiki is used throughout the development of

this version as the control point for functionality that will go

<ol>

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

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

<li>

OpenPegasus

PEP 333 - OpenPegasus Release Definition - This PEP ( and a corresponding

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

section in the Pegasus wiki) is used

information was  released as a Pegasus PEP. Starting with

throughout the development of this version as the control point for

Pegasus 2.9.0 the information is located in the OpenPegasus CVS

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

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

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

<li> OpenPegasus External Interfaces -The

list of the OpenPegasus interfaces that are considered external

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

<li>

by the Steering Committee all subsequent releases of Pegasus MUST

continue to support these interfaces. Interfaces not explicitly

PEP 308</a> -  OpenPegasus  Build and Configuration

listed in this document, should be considered as internal and

Options  for Selected

subject to change.In previous Pegasus releases this information

Platforms</li>

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

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

<li>

<li> OpenPegasus  SDK Packaging Definition - Defines

PEP 329</a> - OpenPegasus 2.8 External Interfaces - Lists the public

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

interfaces for clients and providers that are considered external and

Starting with Pegasus release 2.11.0, this document is available

therefore "frozen".

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

In previous Pegasus releases this document was made available as s

</li>

separate Pegasus PEP document rather than in the CVS repository.

</li>

<li>

<li> Pegasus  Runtime Packaging Definition - Defines

the recommended set of files for inclusion in this OpenPegasus

PEP 330</a> - OpenPegasus  SDK Packaging Definition - Defines the

release. Starting with Pegasus release 2.11.0, this idocument

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

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>

<li>Pegasus Release Notes -

PEP 368 - (This document

PEP 331</a> - Pegasus  Runtime Packaging Definition - Defines the

is located in the approved PEP repository and the OpenPegasus

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

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

</ul>

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

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

approved PEP

The following documentation is available for the this Pegasus release:

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

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

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

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

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

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

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

</li>

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

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

documentation - See the header files and the HTML

documentation - See the header files and the HTML  API

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

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

documentation is the existing utilities and test programs and the

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

examples in the API documentation.  In particular the

documentation.  In particular the Common/tests unit tests contain

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

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

Common APIs. </li>

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

Providers - Readme.html in the Pegasus source tree Root

Directory, API documentation, and documentation from the Pegasus

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

Technical Workshop which is available on the Pegasus web site.

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

</li>

documentation, and documentation from the Pegasus Technical Workshop

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

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

Clients -API documentation and the documentation on the

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

</li>

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

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

Clients - API documentation and the documentation on the Pegasus

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

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

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

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

OpenPegasus web site.  While these are the original design

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

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

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

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

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

development team and as a user information resource.  The wiki

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

</ul>

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

<hr >

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

Licensed to The Open Group (TOG) under one or more contributor license

work for additional information regarding copyright ownership. Each

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with

contributor licenses this file to you under the OpenPegasus Open Source

this work for additional information regarding copyright ownership.

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

Each contributor licenses this file to you under the OpenPegasus Open

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

License.

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

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

copy of this software and associated documentation files (the

to deal in the Software without restriction, including without limitation

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

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

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

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

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

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

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

the following conditions:

The above copyright notice and this permission notice shall be included

in all copies or substantial portions of the Software.

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

Line 2044

Line 2289

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

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

</div>

</body>

</html>

</body></html>

Legend:

Removed from v.1.15
changed lines
	Added in v.1.21

No CVS admin address has been configured