pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.6.12.1, 2006/03/28 20:30:22

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

Line 1

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

<style>

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

</style>

Line 963

Line 961

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

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

<o:DocumentProperties>

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

Line 992

Line 990

</w:Compatibility>

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

</w:WordDocument>

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

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

Pegasus

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

PEP #: 249

PEP #: 355

Title: Release

Notes for OpenPegasus 2.5.1

Notes for OpenPegasus version 2.10.0

Version: 1.0

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

Created: 21 January 2010

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>

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

</td>

<o:p>  1 March

2006</o:p>

21 January 2010

</td>

Karl Schopmeyer

</td>

Initial

Submission<o:p>

Submission <o:p>

</o:p>

</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center">2 March 2006</td>

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

<td style="padding: 0.75pt;">Fix editorial errors</td>

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

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

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

</tr>

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

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

<td style="padding: 0.75pt;">Incorporate comments from

Review week of 12 March 2006</td>

</tr>

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

<tr>

<td style="padding: 0.75pt;" align="center">22 March

2006</td>

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

Schopmeyer</td>

<td style="padding: 0.75pt;">Incorporate comments form

Review 21 March 06 and bring into line with Feature status page</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center">28 March

2006</td>

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

Schopmeyer</td>

<td style="padding: 0.75pt;">Remove all statements

concerning status and point to the Feature Status Page.</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center">28 March

2006</td>

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

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

Schopmeyer</td>

<td style="padding: 0.75pt;">Remove references to

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

status "experimental" for certain features</td>

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

this PEP - This version approved</td>

</tr>

<td style="padding: 0.75pt;" align="center">28 March

2006</td>

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

Schopmeyer</td>

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

</tr>

</tbody>

</table>

<o:p> </o:p>

Abstract: This document defines the release notes for the 2.5.1

Abstract: This document defines the release notes for the

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

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

</a>

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.

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

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

</o:p></h2>

<ol>

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

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

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

Release</a></li>

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

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

Platforms</a></li>

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

with DMTF Specifications</a></li>

<li><a href="#Changes%20in%20This%20Release">Changes

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

in This Release</a></li>

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

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

Bugs</a></li>

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

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

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

Documentation</a></li>

Line 1134

Line 1172

of this Release</h2>

This release is available in a number of forms including:

<ul>

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

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

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

<li>OpenPegasus 2.5.1 binaries are available for Red Hat Enterprise

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

Linux 3.0 and 4.2 and SUSE LINUX Enterprise Server 9.0. A Source RPM is

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

also available that can be used to build binaries for most

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

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

release and

<li>The Pegasus CVS. 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

Line 1151

Line 1189

WEB site</a>.

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

Pegasus source

tree.</div>

tree.

</div>

<h2>Functionality of This Release</h2>

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

Pegasus overall status by release is defined by  a

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

that is available on the OpenPegasus web site .  That

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

web page shows the Pegasus users and developers

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

the status of the various features found in Pegasus using a simple color coded

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

key (white, red, yellow, green).  Pegasus 2.5.1 is a minor release, extending Pegasus 2.5.0 in selected

each feature.Pegasus 2.10.0

areas primarily for bug fixes.  However, there were some signification

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

changes in the feature status for selected functions in 2.5.1 (moving selected

areas as described in the Pegasus  PEP defining this release

functions closer to production-capable status).The following paragraphs list the functionality in this release.   In many cases these features  and interfaces

.

are conditionally compiled with special environment variables.

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

provides more detailed information on how to enable

more information access the PEP for each change defined:

functionality that is conditionally compiled in this release.

NOTE: For current information and history on the status of each feature,

Table of Major Changes for this Release

please access the

OpenPegasus Feature Status WEB Page</a>.  Please see

the Feature status page for the quality/status of each feature because not all

<tbody>

of the features listed below are production ready.

<h3>CIM Server Functionality</h3>

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

<h4>CIM Operations over HTTP support</h4>

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

<ol>

</tr>

<li>Class Operations (getClass, deleteClass, modifyClass,

enumerateClass, enumerateClassNames)</li>

<li>Qualifier Operations (getQualifier, setQualifier,

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

deleteQualifier) </li>

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

<li>Instance Operations (getInstance, deleteInstance, modifyInstance,

WS_Management changes to Pegasus 2.9.0 to incorporate more WS_Management

enumerateInstance, enumerateInstanceNames, getProperty,

functionality.</td>

setProperty)</li>

<li>Association Operations (references, referencenames,

associators, associatornames)</li>

2.2</a> </td>

<li>Methods Operations (invokeMethod)</li>

</tr>

<li>Query operation - Support for ExecQuery was added in 2.4 with

<tr>

WQL as query language and is defined in PEP 119. This feature is

considered at alpha quality because it has only been contributor

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

tested.  Additional tests have been added in 2.5 for ExecQuery. Pegasus

today does not support the ExecuteQuery operation defined as the Query

</tr>

operation for CQL.

</li>

</ol>

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

</blockquote>

</div>

</tr>

<h4>Indication Processing</h4>

<ol>

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

<li>Process indications - Process indications are operational in

the

Server.  This includes support

1.1</a></td>

for subscriptions, filters, and indication handlers, the provider API

</tr>

for

indications and the CIMXML indication handler.</li>

<li>Lifecycle indications - With the support for embedded objects,

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

lifecycle indications (ie. those

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

classes of indications derived from CIM_ClassIndication and

CIM_InstIndication) can now be created. Pegasus 2.5 provides some

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

enablement for the generation of lifecycle indications. For more

details, refer to

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

update SystemName property in indication filter/handler and

</ol>

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

<h4>Query Language</h4>

Pegasus includes the  WQL  query language which is implemented and

used for filters and in version 2.4 for execQuery.

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

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

</tr>

</tr>

</tbody>

</table>

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

release to this release</a> on the

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

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

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

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

PEP

291</a>.

The IPv6 support in OpenPegasus is

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this

variable is "true"; setting this to

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

CQL Stage 1 has been added for Pegasus 2.5.  PEPs 138, 193, 205

The following subsections provide

combine to describe the CQL  functionality supported.

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

<h4>Object Normalization</h4>

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

The Object Normalizer is an entity introduced in Pegasus 2.4 that

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

ensures

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

objects delivered from providers are complete and accurate. Two major

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

issues were identified with the initial implementation: 1) the Object

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

Normalizer droped instances it considered bad, and 2) the Object

Listener components. For more information on IPv6 support for your

Normalizer code slowed performance. These issues are now addressed by

specific platform, refer to the documentation for that platform.

moving the Object Normalizer from the Dispatcher to the Response

Handler (or equivalent) and optimizing the existing implementation. The

All OpenPegasus externals that

move allows errors to be reported to the provider at the point of

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

delivery and ensures that only a single copy is made to preserve the

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

CIMOM/provider boundary.

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

<h4>Embedded Object Support</h4>

address must be specified without brackets. For example, the

Pegasus 2.5 provides embedded object support. The proposed solution

OpenPegasus osinfo client (which returns information about the OS

is restricted to the following:<ul>

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

<li>The only representation for embedded objects supported by this

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

PEP is CIM-XML (i.e. id does not support MOF encoded objects). </li>

specified as:

<li>CIMObject is implemented as a new CIMValue type. This type will be used

internally to represent embedded objects. When externalized (via

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

CIM-XML) these objects will be converted to strings representing valid

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

INSTANCE or CLASS elements, in accordance with the CIM Infrastructure

But the cimcli command, which

Specification.  Embedded instances will also carry the

takes

EmbeddedObject attribute with

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

the value "object", as specified by CR Interop-00217.001.

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

</li>

</ul>

<h3>Pegasus Repositories

</h3>

</blockquote>

<h4>Schema Repository</h4>

By default, Pegasus uses an XML-based

schema repository. A binary encoding option is also available for the repository.

Note: Users may experience an incompatibility moving a binary repository from

Pegasus 2.4 to 2.5. In Pegasus 2.5, measures have been taken to improve

the ability to maintain compatibility with subsequent releases. (See bugzilla 3642 for details.)</div>

Further information on the use of the binary repository is in the

readme.binaryrepository file in the Pegasus source root directory.

<h4>Instance Repository</h4>

The

Pegasus schema repository may also be configured to hold instance

data.  Although instances may be place in the

repository

it was not designed as a

high volume data store.

<h4>Compressed Repository Feature</h4>

A compressed repository

feature has been added for

pegasus 2.5 that compresses the repository written to disk. This allows

the

repository to be as much as 50% smaller on disk. It uses an external

compression library (zlib) and has been tested with zlib 1.2.2. This

feature is

documented in PEP 214 and also in a Readme

(readme.compressed_repository). Note

that the tests for this feature are in the test suite but not

activated for

automatic tests.Further information on the use of the compressed

repository is in the readme.compressedrepository file in the Pegasus source

root directory.

<h4>Pegasus MOF Compilers</h4>

Pegasus implements a MOF compiler that can operate either at the

client

interface to the Pegasus CIM Server (cimmof)

or directly interfacing with a CIM

repository (cimmofl).

The direct interface compiler is used primarily to provide an

initial

class/instance repository. WARNING:

The use of cimmofl

to manipulate instances in the repository bypasses any provider that is

registered to serve these  instances and simply installs the

instances in the

instance repository; this may result in 1) bad data in the repository

if there are registered providers, 2) corruption of the repository if

the CIM Server is running or, 3) MOF data that is loaded but not

available until the server is stopped and restarted in some

cases.  Use of cimmofl in general is

discouraged and particularly  to manipulate

instances served by a registered providers (ex. Provider registration).

<h3>Security Considerations</h3>

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

OpenPegasus 2.5 (and

or

prior versions) contains several mechanisms to perform authorization, but none

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

of these authorization checks are performed by default.

By registering any provider which fails to do appropriate authorization

checks, the consequences may include information leakage, data

corruption, or unintended elevation of privilege. Please ensure that

one of the following mechanisms is used to ensure appropriate access to

your systems and data:

1. Only install/register providers which perform authorization

appropriate for your environment.

<div style="margin-left: 40px;">a. For providers, this may include registering to

'Run-as-requestor' (not available prior to Pegasus 2.5) and/or

performing authorization checks within the provider.

b. For administrators, ensure that the providers you have registered in

your environment have performed sufficient authorization checks. Also,

monitor announcements of security defects in those providers and follow

the recommendations in those announcements as soon as possible.

c. For distributors of Pegasus or providers, ensure that the providers

you are shipping have performed appropriate authorization checks, and

relay announcements of discovered security defects to your users.

</div>

2. Restrict users with

access to Pegasus to a specific authorized user group of trusted

individuals.

3. Namespace authorization is also available.

For administration issues please refer to

For more information on

the SSL Admin Guide found in the source repository at:   pegasus/doc/PegasusSSLGuidelines.htm

specifying

<h4>Server Security</h4>

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

6 Addressing Architecture</a>

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

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

(Note that Digest based security is not implemented in Pegasus)</li>

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

<li class="MsoNormal" style="color: black;">PAM authentication <o:p></o:p></li>

<h4>IPv6 on Linux</h4>

<li class="MsoNormal" style="color: black;">SSL support - SSL is

Modern Linux distributions already

implemented in Pegasus using the OpenSSL

contain IPv6-ready kernels, the

libraries. Pegasus does not provide the OpenSSL

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

libraries but SSL can be used on any platform supported by OpenSSL. .   This release of Pegasus was tested

that this module is not loaded automatically on startup.

with multiple versions of  OpenSSL versions

Note:

0.9.7 and 0.9.8.   Effective with Pegasus 2.5.1 the Open SSL version

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

0.9.6 is no longer supported. See <a href="http://www.openpegasus.org/pp/uploads/40/Application%20Data/Microsoft/Word/www.openssl.org">openssl.org</a>

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

for OpenSSL release information<o:p>.</o:p></li>

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

<li class="MsoNormal" style="color: black;">SSL levels - SSLv3

to use series 2.6.x now.

and TLSv1 by default. SSLv2 is

disabled by default and only enabled by a compile time option.

See<a href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502">

PEP 237</a> for details on

configuration.

</li>

</ol>

<h4>Client Security</h4>

Certificate management

and User-based certificate authentication . A new control provider and CLI for certificate management tasks. It expands upon the existing SSL

client verification support by providing a robust solution to managing

client certificates and certificate revocation lists via standard CIM

operations. It allows certificates to be associated with particular

system users for enhanced authorization capabilities.

CN/ Host

name checks are not performed as a function of SSL or client libraries

and are the responsibility of the client to implement on their

own.  See the SSL guide found in the /pegasus/doc directory for

more details on client security.

Note: WBEM clients are responsible for SSL

certificate verification using Pegasus and/or SSL libraries as

appropriate. Consequences of not doing so include leakage of

authentication credentials to unauthorized parties.

<h4>Platform Management Functions</h4>

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

the defined configuration parameters (cimconfig) and server command

line options.  NOTE: When installed

as a service on Windows, setting the run-time config option

enableAuthentication to true can result in improper operation of the

SLP

provider and other providers. In order to circumvent this defect, an

Administrator should change the user that the service runs under from

the Local

System user to a local, privileged user (e.g. Administrator).

See bugzilla 4142 for details. <o:p></o:p></li>

<li class="MsoNormal" style="color: black;">Daemon/service

operation of the Pegasus CIM Server on all supported platforms<o:p>

with the exception of HP OpenVMS.</o:p></li>

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

capture using the CIM_StatisticalData classes in

the DMTF Interop model. This

function is considered alpha quality and conditionally compiled.

</li>

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

pluggable provider managers.  Provider managers are provided for

the Pegasus C++ provider interface, the CMPI C provider interface and

an alpha quality Java provider interface (JMPI).</li>

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

- Pegasus includes support for unicode data transfers and includes a

mechanism for message support in multiple languages using the open

source ICU libraries (<a href="http://oss.software.ibm.com/icu/">http://oss.software.ibm.com/icu/</a>).</li>

<li class="MsoNormal" style="color: black;">Out-of-process providers - See PEP 072 for more information on use of

this feature </li>

<li class="MsoNormal" style="color: black;">Shared class namespaces - See PEP 129 for more information on use of this feature.</li>

<li class="MsoNormal" style="color: black;">Remote providers for

the CMPI provider interface - See PEP 130 for more

information on use of this feature.</li>

</ol>

<h4>SLP Discovery</h4>

SLP support is included but is conditionally compiled in or out on

a platform basis. <a href="http://www.openpegasus.org/pp/uploads/40/8502/PEP200_RecommendedReleaseOptions.htm">

PEP 237</a> describes the  environment variable (PEGASUS_ENABLE_SLP) to

enable or disable this code.  Effective with Pegasus 2.5.1, support has

been added for the use of OpenSLP as the Service Agent (SA) in addition to the

internal to the Service Agent.  This is controlled through an additional

environment variable (PEGASUS_HAS_OPENSLP)  Once compiled, SLP

support is enabled with the slp configuration parameter (slp=true). SLP

support includes an SLP service agent in the Pegasus CIM sever (either the

internal agent or OpenSLP)  and

generates SLP advertisements compatible with the DMTF slp template

specification. The SLP support also includes  extensions to the

CIM Client libraries to execute SLP User Agent requests and analyze the

results (note that these interfaces are not yet part of the Pegasus

public SDK).

Note: Pegasus on Windows is built with SLP support on by default.

<h4>Indication Handlers</h4>

<h5>System Log Indication Handler

</h5>

The SysLog Indication Handler is a new

for 2.5

type of Indication Handler which allows CIM Indications to be delivered

to the system syslog file. It has following features:

Each syslog file entry has a tag 'CIM Indication' to distinguish

an entry made by Syslog Indication Handler.

If a subscriber includes PerceivedSeverity property in the SELECT

list of the filter condition for the indication, the PerceivedSeverity

will be mapped to syslog error severity. Otherwise, syslog error

severity 'LOG_INFO' is used.

See

<a href="http://www.openpegasus.org/pp/uploads/40/7165/PEP206-SystemLogIndicationHandler.htm" style="color: blue; text-decoration: underline;">PEP

206</a> for details.

<h5>Email Indication Handler

</h5>

The Email Indication Handler is a new

for 2.5

type of Indication Handler that allows CIM Indications to be delivered

to a specified e-mail address.   See

<a href="http://www.openpegasus.org/pp/uploads/40/7166/PEP207-EmailIndicationHandler.htm" style="color: blue; text-decoration: underline;">PEP

207</a>  for details.

</blockquote>

<h4>Pegasus Provider Interfaces</h4>

Pegasus is designed to support multiple Provider Managers to allow

multiple provider interfaces to the CIMOM.  The two default

provider managers are the Pegasus C++ Interface and Common

Manageability Programming Interface (CMPI) Interface.

<h5>C++ Provider Interface</h5>

This is the original

interface defined for OpenPegasus Providers.  It provides an interface

for both operations and indications. Many of the sample and test providers are

written to this interface.  This interface includes a callback into the

CIMOM (CIMOMHandle).

<h5>CMPI C interface Provider Manager<o:p></o:p></h5>

To check whether your current

Pegasus 2.5 includes

running

a provider manager for the CMPI C interfaces. This C interface is the

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

result of a project by the IBM SBLIM team (see 

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

http://sblim.sourceforge.net) and is written to the Common

Manageability Programming Interface, which is an OpenGroup standard.

The CMPI

specification is available at:

http://www.opengroup.org/bookstore/catalog/c051.htm. This provides a

standardized C level interface for creating providers that can be

registered with the Pegasus CIM Server in the same manner as the

current C++ providers.  The

ability for CMPI providers to do user authorization is now available in

Pegasus 2.5.1.

Information on writing providers with the CMPI interface is available

in the specification today (see above) and in the following documents

(http://sblim.sourceforge.net/whitepaper.html and

http://sblim.sourceforge.net/presentations.html) and readme.cmpi in the

Pegasus source root directory.

NOTE: See the Feature status page

for exact status of the CMPI provider manager for different Pegasus

platforms.

<h5>JMPI Java Interface Provider Manager</h5>

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

Pegasus

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

includes a provider manager for Java

For more information on

provider interfaces based on the SNIA provider interface

enabling

definitions.  This provider manager is  considered alpha

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

quality and is not compiled in the default build.   See

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

readme.jmpi in the Pegasus source root directory for more information.

Documentation Project's IPv6 HOWTO</a>.

</blockquote>

<h3>    Providers</h3>

<div style="margin-left: 40px;">New for 2.5 is the ability of Providers

to run out of process at

request user- level and running CMPI providers remotely or out of

process space.

Administrators should check the providers to

Warning:

ensure that the provider vendor

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

has made use of available authorization capability.

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

</div>

described in

There are a number of providers available

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

in the Pegasus release.

bug 6586</a>

This includes providers in the following categories:

and

<h4>Pegasus Internal Providers</h4>

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

Pegasus provides a set of "internal" providers that have direct

bug 248052</a>,

access to the CIMOM for information and provide information and

services to support the CIMOM and its administration.    The

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

providers in this category are mostly defined in the directory

that OpenPegasus with IPv6 enabled may be significantly impacted in these

src/pegasus/controlproviders and include support for the following

environments.

classes:

<h4>IPv6 on Windows</h4>

<ul>

Microsoft provides supported IPv6

<li>DMTF Interop classes including __Namespace,  CIM_Namespace, CIM_ObjectManager,

implementations for Windows Server

CIM_CommunicationMechanism, and

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

CIMOMStatistics.</li>

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

</ul>

On Windows XP, you can use the ipv6.exe tool to install, uninstall, and

<h4>CMPI Remote Providers</h4>

query

Pegasus includes an support for

your IPv6 configuration. For example:

running CMPI providers to be run on remote systems without the need for

an extra CIMOM. It uses a special proxying provider to relay requests

to a remote location using so-called communication layers. The remote

side has to start a CMPIRDaemon process, which accepts remote requests

and passes them on to CMPI style providers.<h3>

Generic Providers</h3>

These are providers that support multiple pegauss platforms and include the Generic OperatingSystem provider. See

the

directory src/Providers/generic.

<h4>Test/Sample Providers</h4>

See the directories src/Providers/TestProviders

and src/Providers/sample for more

information about test and

sample providers.

<h4>Managed System Providers</h4>

ComputerSystem, DNSAdmin,

DNSService, Operating System, Process,

Processor. For

more information on these providers see the documentation for each

provider in

the directory src/Providers/ManagedSystem

<h4>Server Statistics Provider

</h4>

CIM Server statistics, based on the DMTF 'CIM_StatisticalData' class,

are implemented in this release. The statistics gathering is compiled

by default but it is disabled through a property in the singleton

CIM_ObjectManager class. It may be enabled or disabled by performing a

ModifyInstance operation on the 'CIM_ObjectManager instance

in the 'PG_InterOp' namespace to set the GatherStatisticalData property

to 'true' or 'false'. This property setting is persistent across CIM

Server restarts. A statistics display test tool, cimperf, is available

from the Pegasus CVS repository. <h4>SLP Provider</h4>

This provider acts as the definer of

SLP information for SLP registration and also controls the Pegasus SLP

Service Agent. It is treated as a normal provider rather than a control

provider because it does not use internal functions of the CIMOM to

generate any of its information today. (conditionally compiled today)

</blockquote>

<h2>Pegasus Indication Listeners</h2>

The generic components for a CIM Listener and a

listener API are operational.  This includes the functions for

HTTP, XML indication input and response, and consumers of indications.

This code can be used to define a separate listener package and is used

as an indication listener in the Pegasus server.

Pegasus includes 3 separate Indication Listeners.

<h3>Embedded CIMListener</h3>

This listener is embedded in the CIMServer and allows the

server to accept indications and route them.

<h3>Standalone Static CIMListener</h3>

This is a standalone listener that combines the functions

of listener and consumer into a single element.

<h3>Standalone Dynamic Listener</h3>

Pegasus 2.5

includes a new standalone dynamic listener that is separate

from the current standalone CIMListener and the ExportServer listener

in the CIM server.

The use model that this listener fits is the following:

<ul>

<li> The listener may be packaged as

part of the CIMOM or it may be packaged independently as part of

another application. </li>

<li> Consumers

are developed independently of the listener and may be shipped with the

listener or added to an installed listener at a future time. </li>

</ul>

This

dynamic listener provides a solution for the above use model. It

is essentially a lightweight, pluggable listener that

provides a small set of management features. The DynamicListener can be

run inside a daemon or a service. It is easily configurable and

bypasses traditional registration procedures.  See

<a href="http://www.openpegasus.org/pp/protected/upreviews/20/1303/PEP195_CIMListenerEnhancementsv1_6.htm" style="color: blue; text-decoration: underline;">PEP 195</a>  for

details.

</blockquote>

<h3>CIM_Schema</h3>

The default CIM_Schema loaded with this

release is

the DMTF CIM 2.9, final release.  In addition, Pegasus includes

a number of

local classes defined for Pegasus.  These are defined in the pegasus/Schemas

directory.   There are also a

number of older schema available in the CVS.  Further, the CIM 2.10 and CIM

2.11 schemas are available in the CVS repository and the Pegasus is compatible

with these Schemas.

The mechanism to install other schemas than the default is defined

in the mak/config.mak

NOTE: The CIM 2.5 schema is

maintained in the

CVS repository because it remains the basis for parts of the Pegasus

test

environment.

</blockquote>

<h3>Pegasus CIM Server Administration</h3>

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

- Manage Pegasus CIM Server Users.<o:p></o:p></li>

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

- Manage the Pegasus CIM Server configuration parameters.<o:p></o:p></li>

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

- Manage the CIM Server authorization characteristics. Today this is

authorizing users to namespaces.<o:p></o:p></li>

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

- Manage information about the providers .</li>

</ol>

Server admin

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

note:

ipv6 if</big></div>

<div style="margin-left: 40px;">The default behavior for determining

Windows Vista

the CIM server's HTTP and HTTPS ports has changed.  In previous

and Windows Server 2008 support an integrated

releases, any value in /etc/services would override a port explicitly

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

specified in the configuration.  The new order for determining the

Note that the OpenPegasus IPv6 support has not yet been tested

CIM server's HTTP and HTTPS ports is as follows:

on Windows Vista or Windows Server 2008.

1) An explicitly specified port value takes precedence over any other

values.

For more information on

</div>

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

<div style="margin-left: 40px;">2) If no port is specified, the value

the document

in /etc/services is used.

3) If no value is specified in /etc/services, the default WBEM port is

IPv6

used.

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

</div>

<h3>Information client tools</h3>

These tools provide information on the objects managed by the server.

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

- output classes and/or instance information from the Pegasus

repository in MOF or XML format.<o:p></o:p></li>

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

- Generate a set of standard information on the Domain

Name System (DNS) configuration from CIM Classes. Note that the

information generated is dependent on the information available from

providers and differs from system to system.<o:p></o:p></li>

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

- Generates a set of standard information from the Network

Schema.  Information generated varies by system because of the

level of provider support.<o:p></o:p></li>

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

- Generate a set of standard information on the Operating System from

CIM Classes. Note that the information generated is dependent on the

information available from providers and differs from system to system<o:p></o:p></li>

</ol>

<h3>Test support Tools</h3>

<li class="MsoNormal" style="color: black;">Pegasus unit tests

(available through the "tests" option on the Pegasus make files) these

tests are defined throughout the Pegasus source tree typically in

"tests" directories.        <o:p></o:p></li>

<li class="MsoNormal" style="color: black;">The Pegasus test suite

(see the pegasus/tests directory)<o:p></o:p></li>

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

- Basic client for overall platform operation testing. <o:p></o:p></li>

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

- Test tool that sends/receives XML from XML input.<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">CLI - Command line

interface for Client commands.<o:p></o:p></li>

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

benchmark test environment is provided which includes both a client and

provider component. See src/clients/benchmarkTest

for more information.</li>

<li class="MsoNormal" style="color: black;">cimperf  - Lightweight statistics are implemented for

the

client. The client statistics surfaces the elapsed time spent in the

client,

and the

elapsed time spent on the network between client and server.</li>

</ol>

<h3>Pegasus Interface APIs</h3>

Details of the Pegasus public interfaces for this release are listed

in PEP 209

available from the web site(<a href="http://www.openpegasus.org/pp/uploads/40/Administrator/My%20Documents/processes/www.openpegasus.org">www.openpegasus.org</a>).

That document is the authorative source for the list

of publicly supported Pegasus APIs.   The Client and Provider API were

originally frozen at the Pegasus version 2.1 release. The interfaces in the

release of Pegasus 2.1 are forward compatible to this release. Well-behaved

clients and providers compiled to the Pegasus 2.1 or 2.2 interfaces should be

compatible with this release without compilation.  There have been

extensions and new interfaces added for this release.

  The Pegasus public

interfaces includes the following major functions

<li class="MsoNormal" style="color: black;">Client APIs<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">Provider APIs<o:p></o:p></li>

<li class="MsoNormal" style="color: black;">CIM Object and System

function APIs</li>

</ol>

In addition, there are other client interfaces which are not today

in the public SDK including:

<li class="MsoNormal" style="color: rgb(0, 0, 0);">CIM Listener APIs</li>

<li class="MsoNormal">CIM Listener

is a component that can be used to consume indications without a

dependency on the Pegasus CIMOM. In environments where no CIMOM is

running or a physical separation between the indication listener and

the CIMOM is desired, CIM Listener fits the bill. Still, there are

several enhancements that are necessary to make CIM Listener scalable. Enhancements were deemed significant

enough to propose a new listener that builds off CIMListener's

basic capabilities, yet allows the existing CIMListener to remain the

same.</li>

<ul>

<li>New CIM Listener now provides selective

indication delivery.

</li>

<li>New CIM Listener

keeps all consumer libraries in memory for the duration of its

execution.

</li>

<li>New CIM Listener

is now pluggable.</li>

<li>New CIM Listener

now provides reliable indication delivery.</li>

</ul>

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

Client (User Agent) APIs which are extensions to the Client APIs</li>

</ol>

<o:p> </o:p>

The APIs are

documented in

their respective header files and  in HTML documentation based on

the information

in the header files extracted with the doc++ tool will be available on

the

OpenPegasus web site.

WMI Mapper

The WBEM to WMI Mapper provides a way

to access

WMI data from Windows platform systems. It converts incoming XML/CIM

requests

to Microsoft WMI requests, executes the requests, converts the results

XML/CIM and returns the results to the client. WMI Mapper

receives an HTTP message containing the XML/CIM request. It decodes the

XML

message and extracts from the HTTP message header the user credentials

provided

on the connection (username and password). The WMI Mapper

authenticates these credentials, verifying if the provided credentials

have

access to the desired WMI data. This is done because the WMI Mapper runs as a service, logged on using an

account with

administrative rights (which has all access to WMI data). Because of

this, the

WMI Mapper impersonates the user

credentials provided

on the HTTP message to ensure that the calling user has rights to

browse WMI

data. Hence, ALL requests made to the WMI Mapper

MUST

contain user credentials.

<ol>

<h4>Testing your OpenPegasus IPv6

</ol>

support</h4>

<h2>Relationship to

As part of the OpenPegasus

automated tests, the TestClient, g11ntest, and IndicationStressTest

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

(::1) if PEGASUS_ENABLE_IPV6=true.

You can also perform manual

tests

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

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

running on the WBEM standard http port of 5988:

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

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

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

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

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

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

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

significantly affects interoperability) that may require the Community to make

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

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

upgrading to this OpenPegasus release.

<tbody>

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

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

</tr>

</tr>

</tr>

</tr>

</tr>

</tr>

</tbody>

</table>

<h2>OpenPegasus Relationship to

CIM/WBEM Standards</h2>

Pegasus was designed and implemented to comply with the DMTF

specifications The following table defines the level of the DMTF specifications

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

to which this version of Pegasus conforms today.

DMTF specifications to which this version of Pegasus aims to conform

today.

<tbody>

<tr>

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

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

</tr>

<tr>

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

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

<td width="33%">Version 2.2 with Addendum</td>

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

</tr>

<tr>

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

<td width="33%">1.1, final, 6  January 2002</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.1, preliminary, May 2, 2002</td>

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

</tr>

<tr>

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

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

</tr>

<tr>

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

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

</tr>

<tr>

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

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

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

</tr>

<tr>

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

<td width="33%">2.9 Final, Jan. 2005</td>

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

</tr>

</tbody>

</table>

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

<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 a deviation from the

specifications but is a different method of registration than many CIM

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

<li>Indications -Today Pegasus supports process

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

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

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

<li>

IncludeQualifiers

option on Instance Operations

The DMTF specifications have deprecated the use of qualifiers on

instance operations with the 1.2 CIM Operations Specification and

stated specifically that the client should NOT depend on the

includeQualifiers parameter of the CIM/XML instance operations

returning qualifiers. 

Some CIM Client implementations expect instances

returned

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

definition (such as KEY qualifiers on properties).   Pegasus

today expects the provider to complete the qualifiers on instances in

accordance with the specification and generally the interpretation is

that Pegasus applies class level qualifiers when the includeInstance

parameter is supplied on instance operations.  However, Pegasus

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

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.  When Pegasus uses object normalization,

the normalizer does apply qualifiers to returned instances if the

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

Operations - With the 1.1 version of Specification for CIM

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

GetInstance and Enumerate Instances operations was modified. This change

was incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

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

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

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

specification for more information.</li>

<li>

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOF Compiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

</li>

<li>CIMOperation Trailer - Pegasus implements

chunking

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

defined in that specification Refer to bug

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

This trailer was completely removed from the DSP0200 1.2 final specification

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

a noncompliant response to enumerate type requests.

</li>

</ol>

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

Platforms</a></h2>

Each Pegasus 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:

<tbody>

Platform and

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

</td>

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

</td>

</tr>

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

HP-UX<o:p> PA_RISC and

Itanium</o:p>

</td>

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

</td>

</tr>

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

</td>

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

</td>

</tr>

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

</td>

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

</td>

</tr>

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

</td>

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

</td>

</tr>

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

Linux IA-32</td>

gcc

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

</tr>

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

</td>

gcc

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

(versions 3.xx, 4.xx)

</td>

</tr>

<tr>

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

1.7 and up</td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this release (No

current Nightly Build Test Results

<tbody>

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

Platform and

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

</td>

Microsoft

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

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

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

</td>

</tr>

<tr>

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

Windows XP<o:p>, Windows

</td>

2003</o:p>

</td>

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

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

Microsoft

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

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="43" width="211"> MacOS version 10.2 and higher</td>

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

</tr>

<tr>

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

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

</big></td>

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

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

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

Alpha and above</big> </td>

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

</tr>

<tr>

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

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

</td>

</tr>

<tr>

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

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

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

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

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

</td>

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

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

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

</big></td>

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

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

The following is a list of platform

patches Pegasus requires.

The following is a list known of platform

patches Pegasus requires.

RHAS

2.1 needs the update to fix Red Hat Bugzilla 98815.

</div>

Further information regarding Pegasus support on IBM platforms can

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

Further information regarding Pegasus support on HP platforms can be

found at:

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

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

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

<li> Indications -Today Pegasus supports process

indications but does not

include any specific support for lifecycle indications.</li>

<li>

IncludeQualifiers

option on Instance Operations

RHAS

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

The DMTF specifications are unclear regarding the inclusion of

qualifiers on

CIM instances.  Some CIM Client implementations expect instances