pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.6.12.2, 2006/07/12 19:53:48

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

<style>

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

</style>

Line 964

Line 973

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

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

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

Pegasus

OpenPegasus Enhancement

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

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

PEP #: 368

Title: Release

Notes for OpenPegasus 2.5.1 and Subsequent 2.5 minor releases

Notes for OpenPegasus version 2.14.0

Version: 1.7

Created: 20 November 2014

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

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>

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

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

</td>

<o:p>  1 March

12 Nov. 2014

2006</o:p>

</td>

Karl Schopmeyer

</td>

Initial

Karl Schopmeyer

Submission<o:p>

</td>

</o:p>

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

</td>

</tr>

<tr>

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

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

</td>

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

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

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

</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 style="padding: 0.75pt;" align="center">20 March 2006</td>

</td>

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

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

</td>

Review week of 12 March 2006</td>

</tr>

</td>

<tr>

</td>

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

</tr>

2006</td>

<tr>

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

Schopmeyer</td>

</td>

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

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

</td>

</tr>

<tr>

</td>

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

</td>

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

Schopmeyer</td>

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

status "experimental" for certain features</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;">Typos - Approved by

architecture group</td>

</tr>

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

2006</td>

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

Schopmeyer</td>

<td style="padding: 0.75pt;">Update to reflect Pegasus

2.5.2 release</td>

</tr>

</tbody>

</table>

<o:p> </o:p>

Abstract: This document defines the release notes for the 2.5.1

and subsequent 2.5 minor releases 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">

Abstract: This document defines the release notes for the 2.14.0

</a>

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.

<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

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

of This Release</a></li>

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

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

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

Considerations</a></li>

Platforms</a></li>

<li><a href="#Notes_on_Specific_OpenPegasus">Notes on Specific

OpenPegasus Functionality</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="#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

Release

Bugs</a></li>

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

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

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

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

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

Documentation</a></li>

</ol>

<h2>Availability

<h2>Availability of this Release</h2>

of this Release</h2>

This release is available in a number of forms including:

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.

downloaded from the OpenPegasus Web

These can be downloaded from the OpenPegasus

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

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

<li>OpenPegasus 2.5.x binaries are available for Red Hat Enterprise

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

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

source RPM is  available on the OpenPegasus web site that can be

also available that can be used to build binaries for most

used to build binaries for most LSB-compliant RPM-based Linux

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

distributions and versions.</li>

<li>The Pegasus CVS. The CVS tags representing this release and

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

subsequent snapshots that are made available in the Pegasus CVS are

release and subsequent snapshots that are made available in the

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

Pegasus CVS are defined on the OpenPegasus CVS repository web page

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

(see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

snapshots page</a>.</li>

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> and the <a title="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus">OpenPegasus

WIKI Release Status 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>.

The instructions for acquiring the released code are on the <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus

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

WEB

Pegasus source

site</a> and the <a title="OpenPegasus WIKI" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">OpenPegasus

tree.</div>

WIKI</a>. Installation instructions are part of the README in the root

of the Pegasus source tree.

<h2>Functionality of 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

web page shows the Pegasus users and developers

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

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

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

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

functions closer to production-capable status). Pegasus 2.5.2 is a minor release

providing changes that have been defined through pegasus bugs.The following paragraphs list the functionality in this release.   In many cases these features  and interfaces

are conditionally compiled with special environment variables.

provides more detailed information on how to enable

functionality that is conditionally compiled in this release.

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

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

of the features listed below are production ready.

<h3>CIM Server Functionality</h3>

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

<ol>

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

enumerateClass, enumerateClassNames)</li>

<li>Qualifier Operations (getQualifier, setQualifier,

deleteQualifier) </li>

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

enumerateInstance, enumerateInstanceNames, getProperty,

setProperty)</li>

<li>Association Operations (references, referencenames,

associators, associatornames)</li>

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

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

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

considered at alpha quality because it has only been contributor

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

today does not support the ExecuteQuery operation defined as the Query

operation for CQL.

</li>

</ol>

</blockquote>

</div>

<h4>Indication Processing</h4>

<ol>

<li>Process indications - Process indications are operational in

the

Server.  This includes support

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

for

indications and the CIMXML indication handler.</li>

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

lifecycle indications (ie. those

classes of indications derived from CIM_ClassIndication and

CIM_InstIndication) can now be created. Pegasus 2.5 provides some

enablement for the generation of lifecycle indications. For more

details, refer to

</ol>

<h4>Query Language</h4>

Pegasus includes the  WQL  query language which is implemented and

used for filters and in version 2.4 for execQuery.

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

combine to describe the CQL  functionality supported.

<h4>Object Normalization</h4>

The Object Normalizer is an entity introduced in Pegasus 2.4 that

ensures

objects delivered from providers are complete and accurate. Two major

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

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

Normalizer code slowed performance. These issues are now addressed by

moving the Object Normalizer from the Dispatcher to the Response

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

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

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

CIMOM/provider boundary.

<h4>Embedded Object Support</h4>

Pegasus 2.5 provides embedded object support. The proposed solution

is restricted to the following:<ul>

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

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

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

internally to represent embedded objects. When externalized (via

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

INSTANCE or CLASS elements, in accordance with the CIM Infrastructure

Specification.  Embedded instances will also carry the

EmbeddedObject attribute with

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

</li>

</ul>

<h3>Pegasus Repositories

</h3>

</blockquote>

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

<h4>Schema Repository</h4>

OpenPegasus overall status by release is defined by  a <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature

By default, Pegasus uses an XML-based

Status WEB Page</a> that is available on the OpenPegasus web site

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

.  That web page shows the Pegasus users and developers the status of

the various features found in OpenPegasus using a simple color coded key

(white, red, yellow, green) and a description of each feature.

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>

OpenPegasus 2.5 (and

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

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

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

<h4>Server Security</h4>

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

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

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

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

implemented in Pegasus using the OpenSSL

libraries. Pegasus does not provide the OpenSSL

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

with multiple versions of  OpenSSL versions

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

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>

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

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

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>

Pegasus 2.5 includes

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

result of a project by the IBM SBLIM team (see 

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>

Pegasus

includes a provider manager for Java

provider interfaces based on the SNIA provider interface

definitions.  This provider manager is  considered alpha

quality and is not compiled in the default build.   See

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

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

ensure that the provider vendor

has made use of available authorization capability.

</div>

There are a number of providers available

in the Pegasus release.

This includes providers in the following categories:

<h4>Pegasus Internal Providers</h4>

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

access to the CIMOM for information and provide information and

services to support the CIMOM and its administration.    The

providers in this category are mostly defined in the directory

src/pegasus/controlproviders and include support for the following

classes:

<ul>

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

CIM_CommunicationMechanism, and

CIMOMStatistics.</li>

</ul>

<h4>CMPI Remote Providers</h4>

Pegasus includes an support for

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

OpenPegasus 2.14.0 is a major release, extending the previous Pegasus

note:

release in selected areas as described in these release notes.

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

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

NOTE: OpenPegasus releases are categorized as follows:

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

specified in the configuration.  The new order for determining the

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

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

values.

</div>

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

in /etc/services is used.

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

used.

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

<li>First number of version changes (ex. 2.x.x to 3.0.0) -  Major

indication delivery.

release includes major functionality change and  incompatible

</li>

behavior changes and/or incompatible public API changes,

<li>New CIM Listener

</li>

keeps all consumer libraries in memory for the duration of its

<li>Second number changes (ex 2.12.0 2.14.0) -  Minor Release and

execution.

includes new functionality but maintains behavior and public API

compatibility,

</li>

<li>New CIM Listener

<li>3rd number changes (2.14.0 to 2.14.1) - Revision(also called point

is now pluggable.</li>

release) release and only includes bug fixes.</li>

<li>New CIM Listener

now provides reliable indication delivery.</li>

</ul>

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

ALL changes for each release are documented in the

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

OpenPegasus bug data base by tagging each bug(keyword field of bug). 

</ol>

No change to Pegasus is committed with out this tag on the bug. Changes

<o:p> </o:p>

for this minor release are  tagged 2.14.0_APPROVED. All changes for

The APIs are

this minor release can be viewed through  this link to the

documented in

OpenPegasus bugzilla <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.14.0_APPROVED">

their respective header files and  in HTML documentation based on

Pegasus 2.14.0_APPROVED bug list. Bugs.  </a>Bugs marked as

the information

enhancements can be reviewed through the this <a href="http://bugzilla.openpegasus.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=CIM+Server+Core&product=CIMClient+Application&product=CIMClient+DefaultCPlusPlus&product=CIMClient+Java-SNIA&product=CIMConsumer+DefaultCPlusPlus&product=CIMIndicationHandler&product=CIMListener+Dynamic&product=CIMListener+Standalone&product=CIMProvider+CMPI&product=CIMProvider+CMPIRemote&product=CIMProvider+DefaultCPlusPlus&product=CIMProvider+Instrumentation&product=CIMProvider+JMPI&product=CIMSchema&product=CIMServer+Administration&product=CIMServer+Administration+Command&product=CIMServer+Administration+Profiles&product=CIMServer+ProviderManagement&product=CIMServer+Repository&product=CIMServer+SLP&product=OpenPegasus+Build+System&product=OpenPegasus+Documentation&product=OpenPegasus+Security+Defects&product=OpenPegasusProject+Bugzilla&product=OpenPegasusProject+CVS&product=OpenPegasusProject+Website&product=PegasusCIMOM&product=PegasusGeneral&product=RPM+CIMServer&product=TestProduct&product=Unsupported&product=WMI+Mapper&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.14.0_APPROVED&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_severity&type0-0-0=equals&value0-0-0=enhancement">link

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

to OpenPegasus bugzilla 2.14.0 enhancement bugs</a> .  Bugs fixed

the

for subsequent revision releases (ex. 2.14.1) would also be viewed through

OpenPegasus web site.

corresponding Bugzilla tags for each revisions (ex 2.14.1_APPROVED).

WMI Mapper

The major areas of development including both enhancements and bug fixes

The WBEM to WMI Mapper provides a way

for this release  were as follows. Note that the bugs listed

to access

represent only those features incorporated in bugs without PEPS that are

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

considered enhancements, not all bugs incorporated in the release. For

requests

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

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

Table of Major

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

Changes this Release. Review  Bugzilla 2.14.0

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

Enhancements and approved(above) for a complete list

XML

message and extracts from the HTTP message header the user credentials

provided

<tbody>

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

authenticates these credentials, verifying if the provided credentials

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

</tr>

<tr>

<td>Support only TLS V1.2 Protocol for Security Compliance

</td>

</tr>

<tr>

</td>

<td>Support DMTF defined Pull Operations (per DMTF

specification DSP 0200 and 0201). This is a major extension to

OpenPegasus and implements all of the DMTF defined pull operations with

NO changes to providers. This includes extentions to both the server

and client code as well as new operations implemented in cimcli to

allow execution of pull operations and pull operations with FQL.

</td>

</tr>

<tr>

</td>

<td>Fix issue causing failures when cmpi returned

instances that do not have a class. This was causing problems with the

Jobs profiles which specifically return information for which there is

no class.

</td>

</tr>

<tr>

</td>

<td>Dynamic disable of the reliable Indication feature

</td>

</tr>

<tr>

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

</td>

<td style="vertical-align: top;">FootPrint Reduction

</td>

</tr>

<tr>

</td>

<td style="vertical-align: top;">Generate mini-CA and signed certificate instead of self-signed certificates</td>

</tr>

<tr>

</td>

<td>Include cimcli in release packages

</td>

</tr>

<tr>

</td>

<td style="vertical-align: top;">support HTTP Negotiate Authentication in OpenPegasus

</td>

</tr>

<tr>

</td>

<td>Reduce overhead of use of PAM by use of a

SessionCookie.  This also introduces a new runtime configuration

parameter to control the session timeout

</td>

</tr>

<tr>

</td>

<td>Incorporate FQL (Filter Query Language) support for the pull operations (Experimental)

</td>

</tr>

<tr>

</td>

<td>Several minor extension to the APIs (ex. extend String class methods)

</td>

</tr>

</td>

<td align="left" width="75%">Improve CLANG compiler support

</td>

</tr>

<tr>

</td>

<td>Initial CIMRS and Web Admin support (This is Experimental and the CIMRS function will be modified for CIMRS V2 specification)

</td>

</tr>

<tr>

</td>

<td>Correct old error in the Memory Resident

Repository logic. This logic did not work in several previous versions

because of the issues documented in this bug.

</td>

</tr>

<tr>

</td>

<td>Update default CIM Schema to CIM 2.41

</td>

</tr>

<tr>

</td>

<td>Add scripts for load testing of OpenPegasus (see the directory src/Unsupported/Scripts/UinxLoadTests)

</td>

</tr>

<tr>

</td>

<td align="left" width="75%">Fix issue with the configuration parameters for numberOfTraceFiles and traceFileSizeKbytes.

</td>

</tr>

<tr>

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>

</td>

</tr>

</td>

</td>

</tr>

<tr>

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>

</td>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality change status

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

that

have

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

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

account with

previous release to this release</a> on the <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature

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

Status WEB Page</a>.

this, the

WMI Mapper impersonates the user

<h2><a name="Notes_on_Specific_OpenPegasus"></a>Notes on Specific

credentials provided

OpenPegasus Functionality Changes</h2>

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

This section documents specific issues that the OpenPegasus team feels are

browse WMI

important to OpenPegasus users with the current release (and possibly

data. Hence, ALL requests made to the WMI Mapper

older releases).

MUST

contain user credentials.

<h3>Add new RunTime Variables to control trace file size and Rotation(OpenPegasus

2.13.0)(bug 9550)</h3>

<ol>

As of OpenPegasus 2.14.0, several new runtime variables have been added that can be manipulated with the cimconfig utility:

</ol>

<h2>Relationship to

* pullOperationsMaxObjectCount -

CIM/WBEM Standards</h2>

Defines the maximum allowed value of the maxObjectCount argument on

Pegasus was designed and implemented to comply with the DMTF

open and pull operation requests which defines the maximum number of

specifications The following table defines the level of the DMTF specifications

instances or paths that will be returned in a single open or pull

to which this version of Pegasus conforms today.

response. Requests that have a value higher than this configuration

parameter will be rejected. The default is10000. This may be set to any

value between 1 and 10000.

* pullOperationsDefaultTimeout

- Defines the default timeout in seconds between the time a pull open

response is sent by the server and a subsequent pull or close response

received from the client if the value is not set by the client in the

request. This can be set to any value between 1 and 90 seconds.

Default=30

* pullOperationsMaxTimeout

- Defines the maximum allowable value for the maxTimeout argument that

is part of the pull open... (openEnumerationInstances, etc) requests.

Any value higher than the value set in this configuration parameter

will cause the request to be rejected by the CIMServer. The default=90

seconds. TODO - Explain more on all of these above

* httpSessionTimeout -

Allows using a cookie to temporarily bypass the PAM authentication in

favor of the cookie provided by the server during a single session.

This is a performance enhancement.  If this variable is set to

zero (default) the cookie bypass is disabled, the server will not send

nor accept the id cookie.  If set to

an integer, a client session will maintain the cookie for the number of

seconds defined by the value of this variable. Enabled with a build

parameter PEGASUS_ENABLE_SESSION_COOKIES.

* sslBackwardCompatibility

- Limits OpenPegasus support to TLS 1.2/OpenSSL1.01. Can be set to

allow backward compatibility with older versions of TLS/OpenSSL.

The following sections describe in more detail some of the more

significatn changes in this release as well as carrying forward some of

the same information for the last release to be sure users are aware

what these changes affect.

<h3>DMTF Pull Client operations and FQL Query Language (OpenPegasus 2.14.0)</h3>As

of DMTF DSP0200 version 1.4, new client operations (generally named the

pull operations have been part of the CIM/XML protocol). This consists

of a set of new operations (open..., pull..., close) that allow getting

enumerations, associations, references (and their corresponding name

operations) as a sequence

of operations (an enumeration sequence) rather than a single monolithic operation.

This will provider several advantages including:

1. Better control of client memory since the client can determine the size of each response.

2. Clearly separates the return of errors from data.

Pegasus 2.14 supports all of these operations in both in the CIM/XML

client and the server. For more information on the implementation and

use of

these operation see the following documents:

1. OpenPegasus <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:workgroups:pulloperationsupportworkgroup:pull_operation_support_work_group">Wiki page</a> for this project.

2. PEP documenting the Pull operations and FQL

<h3>HTTP Sessions(OpenPegasus 2.14.0)</h3>Allows using a cookie to

enhance performance of PAM.  This function is enabled with the

build varaible  PEGASUS_ENABLE_SESSION_COOKIES. When

the option is enabled, the OpenPegasus CIM server will

use HTTP cookies for session management (RFC 6265).

After a successful client authentication the client is given a cookie. The

client is then not asked for re-authentication as long as it provides the

same cookie in all subsequent requests and until the session expires. Session

expiry is configurable using httpSessionTimeout configuration option.

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

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

authentication mechanisms.

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.

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

adminstration tool to replace the command line tools.  This option

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. 

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

OpenPegasus

source tree for more detailed information on using WEBAdmin.

Note: This option is considered experimental for 2.14

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

</h3>

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

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

significant performance improvements.

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

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

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

While testing OpenPegasus with OpenSLP 2.0 the OpenPegasus team found two

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,

a BUFFER_OVERFLOW exception occurs.  This is because UDP cannot

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

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

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

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"

namespace support for existing or

older repositories which used

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

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

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

details.

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

to be

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"

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

"interop".

Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable to

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

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

wiki faq</a>s.

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

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

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

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

defined OpenPegasus interface, to continue to work with each version

upgrade of OpenPegasus.

Effective OpenPegasus 2.12.0 a new build variable was defined 

(PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus builder to define

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

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

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

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

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

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

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

approach for implementations starting a new repository.

In order to supexport PEGASUS_CLIENT_TRACE=keyword:keywordport users with

existing repositories, in 2.13.0,  migration of existing repositories

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

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

for the interop namespace "root/PG_InterOp" to 

the prefered name "interop".

NOTE: If the interop namespace

name is redefined with PEGASUS_INTEROP_NAMESPACE clients using the

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

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

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

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

<h3>Configure Script to Control OpenPegasus Builds (OpenPegasus

2.13.0)(Bug 9592)</h3>

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

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

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 some information on IPv6 support for the

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

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

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

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

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

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

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

All OpenPegasus externals that support eitcompilerher a hostname or an IP

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

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

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

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

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

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

interface would be specified as:

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>osinfo -h 3ffe:1:2:1 -p 5988</big></div>

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

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

delimited with brackets, for example:

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

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

or

<div style="margin-left: 40px;"><big>cimcli

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

</div>

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

RFC

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

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

<h4>IPv6 on Linux</h4>

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

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

module is not loaded automatically on startup.

Note: you shouldn't use

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

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

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

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

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

short automated test looks like:

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>test -f /proc/net/if_inet6 && echo "Running

kernel is IPv6 ready"</big></div>

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

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

Documentation Project's IPv6 HOWTO</a>.

Warning: There is currently an

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

RHEL5 and SLES10 systems. This problem is described in

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

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

bug

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

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

be significantly impacted in these environments.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6 implementations for Windows Server 2003,

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

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

On Windows XP, you can use the ipv6.exe

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

example:

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

ipv6 if</big></div>

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

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

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

Windows Server 2008.

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

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

<h4>Testing  OpenPegasus IPv6 support</h4>

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

IndicationStressTest test clients were modified to run tests using the

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

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

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

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

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

<h2><a name="Compatibility_Considerations_">OpenPegasus 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 defects/fixes

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

upgrading to this OpenPegasus release.

<tbody>

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

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

</tr>

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

8830</a></td>

<td align="left">Starting

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

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

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

on performance the CIMInstance::filter() and

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

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

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

allow users to actually filter properties from an instance in a

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

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

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

CIMServer will do the filtering but allows the provider to prefilter

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

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

</td>

</tr>

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

9369</a>

</td>

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

fixed in OpenPegasus 2.13.0. Reregistering of an

indication provider requires that the  cimserver be restarted

to send the enableIndication request to the providers. This issue

has existed starting with OpenPegasus 2.10 to  version 2.12.

If the cimserver is not restarted the indication will not be

enabled for the reregistered provider. </td>

</tr>

</tbody>

</table>

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

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

specifications The following table defines the level of the DMTF

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

<tbody>

<tr>

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

<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.4, 26 August 2013

</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.4.0 16 January 2014

</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.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="Supported Platforms">Supported

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

Profiles Supported</h2>

Today OpenPegasus includes support for several DMTF profiles including:

<ol>

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

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

SNIA SMI Indication profile it also supports this profile. This

profile is enabled by compiling OpenPegasus with the buld variable

PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

</li>

<li>SNIA Profile Registration 1.0.0

</li>

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

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 Over HTTP Specification (DSP0200) 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 CIM/XML Option

-  Pegasus does not support the DMTF defined MultiRequest

Operation option (See DSP0200).

</li>

<li>MOF Namespace Pragma -The

Pegasus compiler does not support the namespace pragma defined in DSP

0004. Namespaces for the OpenPegasus repository are defined through

arguments for the MOF Compiler

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

<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>OpenPegasus WSMAN protocol on windows does not handle NaN, INF,

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

- If requests or responses include properties or parameters with

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

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

accepted because these special strings are not understood by the

decoder on Windows.</li>

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

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

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

code

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

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

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

regularly document issues and/or fix defects as the Pegasus

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

code base is changed. 

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

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

operation of  Pegasus cannot be assured.  In all cases,

a group

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

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

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

Pegasus cannot be

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

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

relevant defects that affect their platform.   The platforms

responsibility of the entity that packages and/or compiles OpenPegasus

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

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

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

bugzilla database for a list of relevant defects that affect their

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

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

platforms which have been ported but do not have test results that are

Pegasus release are:

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

Actively Supported Platforms (Nightly Tests Reported for this release)

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

HP aC++

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

</td>

</tr>

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

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>

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

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

IA-32</td>

</td>

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

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

gcc

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

</td>

</tr>

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

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

</td>

Microsoft

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

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

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

</td>

</tr>

<tr>

Windows XP<o:p>, Windows

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

2003</o:p>

Version 1.7 and up</td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this release (No

current Nightly Build Test Results)

<tbody>

Platform and

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

</td>

Microsoft

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

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

</td>

</tr>

<tr>

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

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

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

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

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

the Windows. </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

</big></td>

8</big></td>

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

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

Alpha and above</big> </td>

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

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

</td>

</tr>

<tr>

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

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

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

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

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

</big></td>

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

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

for OpenVMS Alpha</big></td>

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

</tr>

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

<tr>

</td>

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

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

</big></td>

Windows 2000

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

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

<h3>Platform patches </h3>

Platform patches

The following is a list known of

The following is a list of platform

platform patches Pegasus requires.

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

<li> RHAS 2.1 needs the update to

through a set of Pegasus Provider registration classes rather than

fix Red Hat Bugzilla 98815.

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

The DMTF specifications are unclear regarding the inclusion of

qualifiers on

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

</li>

<li>LocalOnly option on instance

Operations - With the 1.1 version of Specification for CIM

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

GetInstance and EnumerateInstances operations was modified. This change

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

<li>

CIM MOF compiler function for

instance aliasing - The Pegasus MOF compiler does not today support

this function.  This function is planned for a future version.

</li>

<li>

MultiRequest Oprations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOFCompiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

</li>

</ol>

<h2><a name="Changes in This Release">Changes in This Release</a></h2>

The development and release of each version of Pegasus is defined

and

controlled through Pegasus PEP documents.  PEP 180 is the

controlling document  for Pegasus 2.5.0 and PEP 239 is the controlling

document for this release. These PEPs list the original set of changes proposed and the

status of

each of those changes. Note that not all of the originally defined

functionality was completed for this release.

In general, the areas of development for release 2.5.0 were:

Addition of CQL

stage 1 support

</li>

Refactoring of

Object Normalizer function to improve performance.

</li>

Out of Process

Provider user level request.

</li>

Embedded Object

support.

</li>

Command Line

Utilities

</li>

CIMDateTime

enhancements

</li>

Completion of

AutoPtr enhancements.

</li>

Certificate

management and user-based certificate authentication

</li>

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

Completion of HTTP

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

chunking. Pegasus

now supports HTTP V1.1 transfer encoding otherwise known as chunking .<a href="http://www.openpegasus.org/pp/uploads/40/5097/PEP140_ChunkedEncoding_4.3.html">

PEP 140</a> describes the implementation details.

</li>

<li class="MsoNormal" style="color: black;">Client side performance

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

statistics</li>

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

<li class="MsoNormal" style="color: black;">Syslog Indication handler.</li>

Hat bug 248052)</li>

<li class="MsoNormal" style="color: black;">Email Indication handler.</li>

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

<li class="MsoNormal" style="color: black;">Port to OpenVMS.</li>

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

</ol>

For release 2.5.1, a number of additional changes were made( See PEP 239 for

</div>

more details) Note: there was no PEP controlling Pegasus 2.5.2 changes, simply

approved bugs:.

Further information regarding Pegasus support on IBM platforms can be

<li>Significant performance improvements ( better than 10 to 1 for operations

and 3 to 1 for indications). (bug 4225)</li>

<li>Improved support for the several platforms (Solaris, MacOS, HardHat Linux)</li>

Further information regarding Pegasus support on HP platforms can be found

<li>Modified Makefile targets for easier usage.</li>

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

<li>Extended and reorganized unit and end-end tests.</li>

<h2><a name="PEGASUS Bugs">Pegasus Defects</a></h2>

<li>Completed implementation of statistics gathering for operations.</li>

The OpenPegasus Bugzilla database documents defects found in Pegasus

<li>Further integrated CMPI and added additional tests.</li>

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

<li>Consolidate some of the compile-time variables. Largely this meant moving

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

from separate variables for DISABLE and ENABLE to a single variable where the

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

value representes the state.</li>

documented through bugs. Therefore all source code changes to OpenPegasus

<li>Corrected error where Pegasus could not maintain general whitespace in

are documented through bugs providing a complete history of changes and

strings (bug 4624).</li>

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

<li>SLP extended to allow optional use of OpenSLP as the Service Agent (SA) in place of

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

the Pegasus internal SA.</li>

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

<li>Changes to align OpenPegasus and Red Hat RPM packaging and configuration

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

options.</li>

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

<li>Additonal testing and integration of the  JMPI provider manager.</li>

</ol>

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

Specifically the status of several components of Pegasus functionality were

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

moved in status on the Feature Status Page as follows:

release.

<ol>

<li>Binary Repository move to green (production capable). (see bug 4388)</li>

     - Changes for this release (bugs Tagged

<li>Out of Process providers</li>

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

<li>Pegasus Provider Interfaces, User Context for Linux and Unix</li>

Pegasus 2.13.0_APPROVED bug list.</a>

</ol>

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

Control

The complete set of changes defined for this release

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

is defined in PEP 239

The OpenPegasus project is controlled largely through the CVS repository

<h2><a name="PEGASUS Bugs">Pegasus defects

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

</a></h2>

mechanism for new and modified Pegasus functionality and for the

The Pegasus bugzilla database documents any defects found in Pegasus

definition and documentation of releases.

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

database</a>.  Note that bugs committed for Pegasus 2.5.1 have been marked

The following documentation defines the characteristics of this Pegasus

with the keyword 2.5.1_APPROVED so that

release. The documents are available in the OpenPegasus CVS

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

repository.

changes between Pegasus 2.5.1 and 2.5.2 are documented in bugs with the keyword

<ul>

2.5.2_APPROVED. These are a minor release all of the fixes were documented as

<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

bugs so that even the changes listed in the previous section are listed as bugs.

2.13.x

The following links provide a list of the bugs for each version

Release Status</a>) - A

section in the Pegasus wiki is used throughout the development of

    - Changes for Pegasus 2.5.1 release (bugs Tagged

this version as the control point for functionality that will go

2.5.1_APPROVED) 

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

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

http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVED</a>

OpenPegasus

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

    - Changes for Pegasus 2.5.2 release (bugs Tagged

information was  released as a Pegasus PEP. Starting with

2.5.2_APPROVED)<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&">

Pegasus 2.9.0 the information is located in the OpenPegasus CVS

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

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

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

<li> OpenPegasus External Interfaces -The

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

list of the OpenPegasus interfaces that are considered external

The Pegasus project is controlled largely through a set of documents

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

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

by the Steering Committee all subsequent releases of Pegasus MUST

modified Pegasus functionality and for the definition and documentation

continue to support these interfaces. Interfaces not explicitly

of releases.

listed in this document, should be considered as internal and

Specifically the following PEPs define the characteristics of this

subject to change.In previous Pegasus releases this information

Pegasus release.

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

<ol>

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

<li>

<a href="http://www.openpegasus.org/pp/uploads/40/8568/PEP209_ExternalInterface2.5.htm">PEP 209</a> - OpenPegaus 2.5 External Interfaces.

<li> OpenPegasus  SDK Packaging Definition - Defines

</li>

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

<li>

Starting with Pegasus release 2.11.0, this document is available

<a href="http://www.openpegasus.org/pp/uploads/40/10083/PEP237_RecommendedReleaseOptions.htm">PEP  237</a> - OpenPegasus  Build and Configuration

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

Option  for Selected

In previous Pegasus releases this document was made available as s

Platforms</li>

separate Pegasus PEP document rather than in the CVS repository.

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

</li>

repository and the Pegasus source tree root directory)</li>

<li> Pegasus  Runtime Packaging Definition - Defines

<li>

the recommended set of files for inclusion in this OpenPegasus

<a href="http://www.openpegasus.org/pp/uploads/40/9825/PEP242_RuntimePackaging2.5.1.htm">PEP 242</a> -  Pegasus  Runtime Packaging Definition

release. Starting with Pegasus release 2.11.0, this idocument

</li>

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

<li>

In previous releases this was made available as a seperate Pegasus

<a href="http://www.openpegasus.org/pp/uploads/40/9820/PEP243_SDKFile2.5.1.htm">PEP 243</a>  - OpenPegasus  SDK Packaging Definition</li>

PEP document rather than in the CVS repository.  </li>

<li>PEP 251  - Pegasus readme.txt for  (Located in PEP repository

and also in the Pegasus

<li>Pegasus Release Notes -

source

PEP 368 - (This document

tree root directory).</li>

is located in the approved PEP repository and the OpenPegasus

<li>

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

<a href="http://www.openpegasus.org/pp/uploads/40/10067/PEP239_2_5_1ReleaseDefinition.htm">PEP 239</a> - OpenPegasus Release Definition - This PEP is used

throughout the development of this version as the control point for

</ul>

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

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

PEPs that represent the Pegasus 2.5 functionality changes.  (as of

this document verion of PEP 230, PEP 180 is listed as draft status)</li>

The following documentation is available for the this Pegasus release:

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

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

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

documentation - See the header files and the HTML  API

</li>

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

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

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

documentation - See the header files and the HTML

documentation.  In particular the Common/tests unit tests contain

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

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

documentation is the existing utilities and test programs and the

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

examples in the API documentation.  In particular the

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

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

documentation, and documentation from the Pegasus Technical Workshop

Common APIs. </li>

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

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

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

Providers - Readme.html in the Pegasus source tree Root

Clients - API documentation and the documentation on the Pegasus

Directory, API documentation, and documentation from the Pegasus

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

Technical Workshop which is available on the Pegasus web site.

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

</li>

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

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

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

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

<o:p></o:p>

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

work for additional information regarding copyright ownership. Each

contributor licenses this file to you under the OpenPegasus Open Source

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

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

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

Group; VERITAS Software Corporation; Intel Corp.

copy of this software and associated documentation files (the

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

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

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

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

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

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

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

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

the following conditions:

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

The above copyright notice and this permission notice shall be included

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

in all copies or substantial portions of the Software.

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

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

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

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

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

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

IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

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

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE

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

AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,

OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

SOFTWARE.</div>

</div>

</body></html>

Legend:

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

No CVS admin address has been configured