pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.4, 2005/08/26 16:15:07

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

Line 1

<html xmlns:v="urn:schemas-microsoft-com:vml"

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

<head>

<style>

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

Line 448

margin:1.0in 1.25in 1.0in 1.25in;

mso-header-margin:.5in;

mso-footer-margin:.5in;

mso-paper-source:0;}

div.Section1

{page:Section1;}

Line 569

Line 570

text-indent:-.25in;}

@list l4:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level8

Line 887

Line 889

text-indent:-.25in;}

@list l19

{mso-list-id:1902863286;

mso-list-template-ids:740079056;}

@list l19:level1

{mso-level-number-format:bullet;

Line 959

Line 962

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

href="PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso">

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

<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"

<o:smarttagtype

name="City"/>

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

<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"

<o:smarttagtype

name="place"/>

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

<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"

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

name="date"/>

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

<o:DocumentProperties>

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

<o:LastAuthor> </o:LastAuthor>

Line 995

Line 996

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

</w:WordDocument>

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

</head>

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

style="color: black;">

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

width="100%"></div>

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

align="center">Pegasus

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

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

PEP #: 306

style='color:black'>

</div>

Title: Release

Notes for OpenPegasus 2.7.0

<span

style='font-size:13.5pt;color:black'>Pegasus Enhancement Proposal (PEP)<o:p></o:p>

Created: 3 October 2007

PEP #: 185

Title: Release Notes for OpenPegasus 2.4

Authors: Karl Schopmeyer

Version: 1.4

Created: <st1:date Year="2004" Day="23" Month="3">23 July 2004</st1:date>

Status:  draft

Authors: Karl

Version History:

Schopmeyer

Status:  draft

Version History:

<table class=MsoNormalTable border=1 cellspacing=1 cellpadding=0 width="100%"

style='width:100.0%;mso-cellspacing:.6pt;mso-padding-alt:0in 5.4pt 0in 5.4pt'>

<span

style='font-family:Arial;color:black'><o:p> </o:p>

</td>

<span

style='font-family:Arial;color:black'><o:p> </o:p>

</td>

<span

style='font-family:Arial;color:black'><o:p> </o:p>

</td>

<span

style='font-family:Arial;color:black'><o:p> </o:p>

</td>

</tr>

<span

style='font-family:Arial;color:black'> 1.0<o:p></o:p>

</td>

<o:p>

23 July 3004</o:p>

</td>

<span

style='font-family:Arial;color:black'><o:p> KS</o:p>

</td>

Initial

Submission<o:p> (Incomplete)</o:p>

</td>

</tr>

1.1</td>

26 August 2004</td>

KS</td>

Incorporate comments from 1.0</td>

</tr>

1.2</td>

6  October 2004</td>

KS</td>

Incorporate comments from Review of 1.1</td>

</tr>

1.3</td>

24 October 2004</td>

KS</td>

Update with comments from Version 1.2</td>

</tr>

1.4</td>

1 November 2004</td>

KS</td>

Comments from 1.3</td>

</tr>

</table>

<o:p> </o:p>

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

<tbody>

style='color:black'>

</div>

Abstract: This document defines the release notes that support

<o:p> </o:p>

release 2.4 of the Pegasus platform. <span

style='font-size:9.0pt'><a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35"

target="_self">

</a>

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

</td>

style='color:black'>

</div>

<o:p> </o:p>

<o:p> Contents</o:p>

</td>

<ol>

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

<li><a href="#Functionality of This Release">Functionality of This Release</a></li>

<li><a href="#Relationship to CIM/WBEM Standards">Relationship to CIM/WBEM

Standards</a></li>

<li><a href="Supported%20Platforms">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 in This Release</a></li>

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

<li>

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

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

</ol>

<h2><a name="Availability of this Release">Availability of this Release</a></h2>

This release is available in a number of forms including:

<o:p> </o:p>

<ul>

</td>

<li>source release in both ZIP and TAR formats. These can be downloaded from the OpenPegasus Web

site at <a href="../Application%20Data/Microsoft/Word/www.openpegasus.org">www.openpegasus.org.</a></li>

<li>OpenPegasus 2.4 binaries are available for Red Hat Enterprise Linux 3.0 and

SUSE LINUX Enterprise Server 9.0. A Source RPM is also available that can be

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

versions.</li>

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

release and subsequent snapshots that are made available in the Pegasus CVS are

defined on the

OpenPegasus CVS repository web page (see the

<a href="http://www.openpegasus.org/cvs.tpl?CALLER=page.tpl">OpenPegasus CVS

page</a> for information) using the tags defined on the

<a href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release

snapshots page</a>.</li>

</ul>

The instructions for acquiring the released code are on the

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

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

tree.

<o:p> </o:p>

<a name="comtag_59">Instructions for building the Linux

RPMs: </a>

<ol>

</td>

<li><a name="comtag_59">Download tog-pegasus-2.4.0-1.src.rpm.

</a></li>

<li><a name="comtag_59">rpm -ih tog-pegasus-2.4.0-1.src.rpm

</a></li>

<li>

<a name="comtag_59">Build the rpms</a>:

<a name="comtag_59">For RHEL3 - rpmbuild -bb /usr/src/redhat/SPECS/tog-pegasus- 2.4.0-1.spec </a>

<a name="comtag_59">For SLES9 - rpmbuild -bb /usr/src/packages/SPECS/tog-pegasus- 2.4.0-1.spec </a></li>

<li><a name="comtag_59">After the build the rpms will be in

the following locations: </a>

<a name="comtag_59">For RHEL3 - /usr/src/redhat/RPMS/[arch]/tog-pegasus-

2.4.0-1.[arch].rpm /usr/src/redhat/RPMS/[arch]/tog-pegasus-sdk- 2.4.0-1.[arch].rpm. </a>

<a name="comtag_59">For SLES9 - /usr/src/packages/RPMS/[arch]/tog-pegasus- 2.4.0-1.[arch].rpm /usr/src/packages/RPMS/[arch]/tog-pegasus-sdk-

2.4.01-.[arch].rpm</a>.</li>

</ol>

<h2><a name="Functionality of This Release">Functionality of This Release</a></h2>

</tr>

The overall level of functionality in the Pegasus environment effective with

this release is as follows:

<h3>CIM Server Functionality</h3>

The following paragraphs list the functions in this release.  All

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

functions are considered community tested and operational unless specifically

noted below. Features that are marked alpha or beta are not generally of the

quality or completeness for production usage.  Interfaces that are

part of the Pegasus public interface definitions but that the Pegasus team feels

may change are marked experimental. In many cases these features  and

interfaces are conditionally compiled with special environment variables. PEP

174 provides more detailed information on how to enable functionality that is

conditionally compiled in this release.

</td>

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

<ol>

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

<li>Class Operations (getClass, <span

October 2007

class=SpellE>deleteClass, modifyClass, <span

class=SpellE>enumerateClass, enumerateClassNames)</li>

<li>Qualifier Operations (getQualifier, setQualifier, deleteQualifier) </li>

<li>Instance Operations (getInstance, <span

class=SpellE>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 and there is no test

in the test suite to confirm the functionality.</li>

</ol>

</blockquote>

</div>

</td>

<h4>Indications</h4>

Process indications are operational in the Server.  This includes support

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

Karl Schopmeyer

indications and the CIMXML indication handler.

<h4>Indication Listener</h4>

</td>

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.

</blockquote>

Initial

Submission<o:p>

</o:p>

</td>

</tr>

<h4>Query Language</h4>

<tr>

The query language today is based on WQL and is implemented and used for

filters and in 2.4 for execQuery.  The execQuery support  for WQL has

been implemented in Pegasus 2.4 but is considered alpha quality.

<h4>Class Repository</h4>

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

Pegasus uses an XML based file/directory class repository. All class and qualifier operations

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

access this repository. The repository was modified to improve efficiency in 2.4

by adding a binary repository option to reduce repository size. The binary

repository functions are considered alpha level because they have only been

contributor tested and there is no test function in the automated Pegasus test

suite.

<h4>Instance Repository</h4>

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

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

Pegasus uses an XML based file/directory Instance repository.  The

</tr>

instance  repository may be conditionally used as the default repository

with a Pegasus configuration flag ( As defined in PEP 174, it is normally set 

to NOT use the instance repository as default).

<h4>Server Security</h4>

<li class=MsoNormal style='color:black;mso-list:l14 level1 lfo6;tab-stops:

list .5in'>Basic Authentication (Note that Digest based security is not

implemented) <o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l14 level1 lfo6;tab-stops:

list .5in'>SSL support - SSL is implemented in Pegasus using the <span

class=SpellE>OpenSSL libraries. Pegasus does not provide the <span

class=SpellE>OpenSSL libraries but SSL can be used on any platform

supported by OpenSSL.  Minimum level known

to work is  0.9.6c .   This release of Pegasus was tested

with 0.9.6k.  See <a

href="../Application%20Data/Microsoft/Word/www.openssl.org">openssl.org</a>

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

</ol>

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

<h4> Platform Management Functions</h4>

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

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

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

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

list .5in'>Configuration through the defined configuration parameters (cimconfig)

and server command line options. <o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

list .5in'>Daemon/service operation of the Pegasus CIM Server on all supported platforms<o:p>.</o:p></li>

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

list .5in'>Operation statistics capture using the CIMStatistics classes in

the DMTF Interop model. This function is considered alpha quality and conditionally compiled.  The

default is that this function is not compiled.</li>

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

list .5in'>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;mso-list:l11 level1 lfo9;tab-stops:

list .5in'>Platform Globalization - Pegasus includes support for unicode

data transfers and includes a mechanism for message support in mulitple

languages using the open source ICU libraries (<a href="http://oss.software.ibm.com/icu/">http://oss.software.ibm.com/icu/</a>). Note that this is still marked

experimental.</li>

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

list .5in'>Out-of-process providers (Experimental) - See PEP 072 for more information on

use of this feature </li>

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

list .5in'>Shared class namespaces (Experimental) - See PEP 129 for more information on

use of this feature</li>

<li class=MsoNormal style='color:black;mso-list:l11 level1 lfo9;tab-stops:

list .5in'>Remote providers for the CMPI provider interface (Experimental)

- See PEP 130

for more information on use of this feature</li>

</ol>

<h4>SLP Discovery</h4>

</tr>

SLP support is included but is conditionally compiled with the default.  This code can be enabled by setting the compile

<tr>

environment variable PEGASUS_ENABLE_SLP.   Once compiled, SLP support

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

an SLP service agent in the Pegasus CIM severas 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).

<h4>Provider Managers</h4>

Pegasus is designed to support multiple Provider Managers to allow multiple

provider interfaces to the CIMOM.  The default provider manager is the C++

Interface.  This section defines the additional provider managers available

with Pegasus 2.4.

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

Pegasus 2.4 includes a provider manager for the CMPI C interfaces.

This C interface is the result of a project by the IBM SBLIM team (<span

class=GramE>see� <a

href="http://www-124.ibm.com/sblim/)">http://www-124.ibm.com/sblim/)</a> and

also the working draft of the Open Group specification for these interfaces

which is in review now within the WBEMSource

Initiative (<a href="http://www.wbemsource.org/">http://www.wbemsource.org</a>).

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.

Today, the CMPI provider manager and interfaces are considered experimental

and are subject to change in future versions of Pegasus  until the CMPI

specification is released. Information on writing providers with the CMPI

interface is available in the draft version of the specification today (see

above) and in the following documents (<a href="http://www-124.ibm.com/sblim/doc/CMPIandC++.pdf">http://www-124.ibm.com/sblim/doc/ProviderArchitecture.pdf

</a>and <a href="http://www-124.ibm.com/sblim/doc/CMPIandC++.pdf">

http://www-124.ibm.com/sblim/doc/CMPIandC++.pdf</a>) and readme.cmpi in the

Pegasus source root directory.

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

Pegasus includes an experimental 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>

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

class=SpellE>CIM_Namespace, CIM_ObjectManager,

CIM_CommunicationMechanism, and CIMOMStatistics.</li>

</ul>

<h4>Generic Providers</h4>

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

Generic OperatingSystem provider. See the

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

directory src/Providers/generic.

<h4>Test/Sample Providers</h4>

<td style="padding: 0.75pt;" height="21">Add final links</td>

See the directories src/Providers/TestProviders

</tr>

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

<h3>CIM_Schema</h3>

The default CIM_Schema loaded with this release is

the DMTF CIM 2.8, Final release.  In addition, Pegasus includes a number of

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

directory.   CIM 2.9 preliminary

schema is also available in the CVS but is not the default schema for compile. 

There are also a number of older schema available in the CVS.

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.

<h3>Pegasus MOF Compilers</h3>

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). Use of <span

class=SpellE>cimmof rather that cimmofl is encouraged

wherever possible.

<h3>Client Tools</h3>

<h4>   Pegasus CIM Server Adminstration</h4>

<li class=MsoNormal style='color:black;mso-list:l8 level1 lfo15;tab-stops:

list .5in'>cimuser - Manage Pegasus CIM Server

Users.<o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l8 level1 lfo15;tab-stops:

list .5in'>cimconfig - Manage the Pegasus CIM

Server configuration parameters.<o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l8 level1 lfo15;tab-stops:

list .5in'>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;mso-list:l8 level1 lfo15;tab-stops:

list .5in'>cimprovider - Manage information

about the providers .<o:p></o:p></li>

</ol>

<h4>Information client tools</h4>

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

<li class=MsoNormal style='color:black;mso-list:l4 level1 lfo18;tab-stops:

list .5in'>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;mso-list:l4 level1 lfo18;tab-stops:

list .5in'>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;mso-list:l4 level1 lfo18;tab-stops:

list .5in'>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;mso-list:l4 level1 lfo18;tab-stops:

list .5in'>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>

<h4>Test support Tools</h4>

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

list .5in'>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;mso-list:l0 level1 lfo21;tab-stops:

list .5in'>The Pegasus test suite (see the pegasus/tests directory and the

Pegasus/TestBuildMakeFile)<o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

list .5in'>TestClient - Basic client for overall

platform operation testing. <o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

list .5in'>wbemexec - Test tool that

sends/receives XML from XML input.<o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

list .5in'>CLI - Command line interface for Client commands.<o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l0 level1 lfo21;tab-stops:

list .5in'>Benchmark Test - A benchmark test

environment is provided which includes both a client and provider component.

See src/clients/benchmarkTest for more

information.<o:p></o:p></li>

</ol>

<h3>Pegasus Interface APIs</h3>

</tr>

Details of the Pegasus public interfaces for this release are listed in PEP

189

available from the web site(<a

href="../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 and these are marked as

experimental.   The Pegasus public

interfaces includes the following major functions

<li class=MsoNormal style='color:black;mso-list:l5 level1 lfo24;tab-stops:

list .5in'>Client APIs<o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l5 level1 lfo24;tab-stops:

list .5in'>Provider APIs<o:p></o:p></li>

<li class=MsoNormal style='color:black;mso-list:l5 level1 lfo24;tab-stops:

list .5in'>CIM Object and System function APIs</li>

</ol>

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

</tbody>

public SDK including:

</table>

<li class=MsoNormal style='color:black;mso-list:l5 level1 lfo24;tab-stops:

<span

list .5in'>CIM Listener APIs</li>

style="color: black;">

<li class=MsoNormal style='color:black;mso-list:l5 level1 lfo24;tab-stops:

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

list .5in'>SLP Client (User Agent) APIs which are

width="100%"></div>

extensions to the Client APIs</li>

Abstract: This document defines the release notes for the

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

to summarize the characteristics of this release, point to other

documentation that defines the release in more detail, and provide

additional information about this release that is not available in the

other Pegasus documentation.

<span

style="color: black;">

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

width="100%"></div>

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

<ol>

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

Release</a></li>

<li><a href="#Functionality_of_This_Release">OpenPegasus

Functionality of This Release</a></li>

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

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

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

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

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

with DMTF Specifications</a></li>

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

<li> <a

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

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

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

Documentation</a></li>

</ol>

<h2>Availability

of this Release</h2>

This release is available in a number of forms including:

<ul>

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

These can be

downloaded from the OpenPegasus Web

site at <a

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

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

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

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

release and

subsequent snapshots that are made available in the Pegasus CVS are

defined on the OpenPegasus CVS repository web page (see the <a

href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

CVS page</a> for information) using the tags defined on the <a

href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release

snapshots page</a>.</li>

</ul>

The instructions for acquiring the released code are on the <a

href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus

WEB site</a>.

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

Pegasus source

tree.

</div>

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

<o:p> </o:p>

Pegasus overall status by release is defined by  a

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

The APIs are documented in

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

their respective header files and  in HTML documentation based on the information

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

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

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

OpenPegasus web site. <o:p></o:p>

each feature.Pegasus 2.7.0

is a major release, extending Pegasus 2.6 in selected

<h3>WMI Mapper</h3>

areas as described in the Pegasus  PEP defining this release

.

The WBEM to WMI Mapper provides a way to access

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

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

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

more information access the PEP for each change defined:

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

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

message and extracts from the HTTP message header the user credentials provided

Table of Major Changes for this Release

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

authenticates these credentials, verifying if the provided credentials have

access to the desired WMI data. This is done because the WMI <span

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

class=SpellE>Mapper runs as a service, logged on using an account with

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

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

<TBODY>

WMI Mapper impersonates the user credentials provided

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

data. Hence, ALL requests made to the WMI Mapper MUST

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

contain user credentials.

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

</TR>

<h2><a name="Relationship to CIM/WBEM Standards">Relationship to CIM/WBEM

Standards</a></h2>

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

Solutions Environment (PASE)</TD>

1.6</a></TD>

</TR>

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

(Privilege Separation)</TD>

1.8</a></TD>

</TR>

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

was made available but normally disabled

Pegasus 2.6.1)</TD>

1.2</a></TD>

</TR>

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

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

1.1</a></TD>

</TR>

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

1.2</a></TD>

</TR>

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

1.0</a></TD>

</TR>

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

logging</TD>

1.5</a></TD>

</TR>

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

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

triage of indication delivery issues</TD>

Bug 6466</a></TD>

</TR>

</TBODY>

</TABLE>

</html>

The status of several components of Pegasus functionality change status

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

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

release to this release</a> on the

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

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

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

for more information.

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

IPv6 is short for "Internet

Protocol

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

to replace the current version Internet Protocol, IP Version 4

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

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

PEP

291</a>.

The IPv6 support in OpenPegasus is

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this

variable is "true"; setting this to

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

The following subsections provide

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

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

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

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

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

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

Listener components. For more information on IPv6 support for your

specific platform, refer to the documentation for that platform.

All OpenPegasus externals that

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

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

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

address must be specified without brackets. For example, the

OpenPegasus osinfo client (which returns information about the OS

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

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

specified as:

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

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

But the cimcli command, which

takes

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

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

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

or

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

</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 anymore 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);">test -f

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

For more information on

enabling

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

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

Documentation Project's IPv6 HOWTO</a>.

Warning:

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

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

described in <span

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

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

bug 6586</a>

and<span

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

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

bug 248052</a>,

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

that OpenPegasus with IPv6 enabled may be significantly impacted in these

environments.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6

implementations for Windows Server

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

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

On Windows XP, you can use the <span

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

query

your IPv6 configuration. For example:

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

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

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

IPv6

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

<h4>Testing your OpenPegasus IPv6

support</h4>

As part of the OpenPegasus

automated tests, the TestClient, g11ntest, and IndicationStressTest

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

(::1) if PEGASUS_ENABLE_IPV6=true.

You can also perform manual

tests

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

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

running on the WBEM standard http port of 5988:

osinfo -h ::1</div>

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

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

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

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

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

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

significantly affects interoperability) that may require the Community to make

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

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

upgrading to OpenPegasus 2.7.0.

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

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

<TBODY>

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

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

</TR>

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

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

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

</TD>

</TR>

<TD>

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

</TR>

<TD>

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

</TR>

</TBODY>

</TABLE>

</html>

Pegasus was designed and implemented to comply with the DMTF specifications The following table defines the

level of the DMTF specifications which which Pegasus conforms today.

<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 width="33%" bgcolor="#00FFFF">DMTF Specification</td>

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

<td width="33%" bgcolor="#00FFFF">Specification Version</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%">1.2.0, preliminary, 9 December 2004</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%">2.2.0, preliminary, December 2004</td>

</tr>

<tr>

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

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

</tr>

<tr>

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

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

</tr>

<tr>

<td width="33%">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.8 Final, June 2004</td>

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

</tr>

</tbody>

</table>

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

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

Exceptions to

DMTF Specifications</a></h2>

Each Pegasus release lists as supported platforms those

It is a major goal

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

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

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

specifications.  However, today there are a number of known

assure that the port is maintained as the Pegasus code base is changed. 

differences. 

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

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

to provide the role of test and maintenance, the Pegasus project cannot assure

<ol>

operation. The supported platforms for this Pegasus release are:

<li>Provider Registration - Pegasus supports registration

through a set of Pegasus Provider registration classes rather than

<table class=MsoNormalTable border=1 cellspacing=1 cellpadding=0 width=504

support the DMTF defined Provider Qualifier. Pegasus will not support

style='width:302.25pt;mso-cellspacing:.6pt;mso-padding-alt:0in 5.4pt 0in 5.4pt' height="409">

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

provider registration.  This is not a deviation from the

specifications but is a different method of registration than many CIM

Platform and OS<span

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

style='color:black'><o:p></o:p>

<li>Indications -Today Pegasus supports process

</td>

indications and lifecycle indications when defined specifically by

providers. Pegasus does not support lifecycle indications if they are

Compilers<span

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

style='color:black'><o:p></o:p>

color="#ff0000">  For

</td>

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

</tr>

<font

face="Courier New" size="2"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

<li>

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

<font

</td>

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

option on Instance Operations

HP aC++

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

The DMTF specifications have deprecated the use of qualifiers on

</td>

instance operations with the 1.2 CIM Operations Specification. 

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 Enumerate Instances operations was modified. This change

was incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

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

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

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

specification for more information.</li>

<li>

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOF Compiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

</li>

<li>Pegasus implements

chunking

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

defined in that specification Refer to bug

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

</li>

</ol>

<h2>OpenPegasus <a

name="Supported Platforms">Supported

Platforms</a></h2>

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus

code

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

regularly document issues and/or fix defects as the Pegasus

code base is changed. 

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

a group

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

Pegasus cannot be

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

responsibility of the entity that packages and/or compiles OpenPegasus

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

bugzilla database for a list of relevant defects that affect their

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

Pegasus release are:

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

cellpadding="0" cellspacing="1">

<tbody>

<td

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

height="26">

Platform and

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

</td>

<td

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

height="26">

Compilers<span

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

</td>

</tr>

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

</td>

HP <span

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

</td>

</tr>

<span

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

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

</td>

<span

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

</td>

</tr>

<span

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

</td>

<span

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

</td>

</tr>

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

</td>

<span

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

</td>

</tr>

Linux IA-32</td>

<span

style="color: black;">gcc

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

</tr>

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

</td>

<span

style="color: black;">gcc

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

</td>

</tr>

Windows 2000

</td>

Microsoft Visual C++ Ver.  6 and Microsoft .Net compiler version. Works on VC .NET 2003 v7.1).

NOTE: Visual C++ Ver. 6 no longer being regularly tested.</td>

</tr>

<tr>

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

PowerLinux<span

style='color:black'><o:p></o:p>

</td>

gcc<span

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

style='color:black'><o:p></o:p>

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

</td>

</tr>

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

zLinux<span

style='color:black'><o:p></o:p>

</td>

gcc<span

style='color:black'><o:p></o:p>

</td>

</tr>

<tr>

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

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

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

</td>

style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span

style="color: rgb(153, 51, 153);">7.3-009 or later required for OpenVMS

gcc<span

Alpha</big></td>

style='color:black'><o:p></o:p>

</td>

</tr>

<tr>

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

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

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

</td>

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

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

gcc<span

later required<font

style='color:black'> (versions 2.9x and 3.xx)<o:p></o:p>

style="color: rgb(0, 0, 0);"> on OpenVMS IA64</big></td>

</td>

</tr>

<tr>

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

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

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

</td>

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

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

Microsoft

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

Visual C++ Ver 6 and Microsoft .Net compiler Version.   <span

style='color:black'>Works on VC .NET 2003 (aka

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

</td>

</tr>

<tr>

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

Windows XP<o:p></o:p>

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

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

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

</td>

Microsoft

Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1<span lang=NL style='color:black;mso-ansi-language:

NL'><o:p></o:p>

</td>

</tr>

Sun Solaris 9</td>

Sun workshop 6, update 2</td>

</tr>

MacOS version 10.2 and higher</td>

gcc 3.3</td>

</tr>

</tbody>

</table>

Platform patches

Further information regarding Pegasus support on IBM platforms can be found at:<a

<font

href="http://publib.boulder.ibm.com/eserver/v1r1/en_US/index.html" target="_"> http://publib.boulder.ibm.com/eserver/v1r1/en_US/index.html.</a>

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

patches Pegasus requires.

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

<o:p> </o:p>

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

It is a major goal

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

specifications.  However, today there are a number of known differences. 

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

<ol>

<li>Provider Registration - Pegasus supports registration through a set of

Pegasus Provider registration classes rather than support the DMTF defined Provider

Qualifier. Pegasus will not support this qualifier in the future. See the readme for more information on provider registration.</li>

<li> Indications -Today Pegasus supports process indications but does not

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

<li>

Instance qualifiers and class

<font

qualifiers on some Operations -

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

The DMTF specifications are unclear regarding the inclusion of qualifiers on

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

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>

RHEL 4.4 multithreading bug in

CIM MOF compiler function for instance aliasing - The

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

Pegasus MOF compiler does not today support this function.  This function is

RHEL 4.5</li>

planned for a future version.

</li>

<li>

Red Hat and SUSE Linux

multiple versions -

multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla

6586) (Red Hat bug 248052) </li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can

found at: <a

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

style="text-decoration: underline; color: rgb(51, 51, 255);">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</a>

Further information regarding Pegasus support on HP platforms can

found at:

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

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

The Pegasus bugzilla database documents any defects found in Pegasus

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

database</a>.

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

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

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

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

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

(ex. 

2.6.0_APPROVED</a>,

2.6.1_APPROVED</a>,

<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>) will yield all changes to

the Pegasus CVS tree for that Pegasus release.

     - Changes for Pegasus 2.7.0 release (bugs Tagged

2.7.0_APPROVED) 

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

<h2><a

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

The Pegasus project is controlled largely through a set of documents

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

modified Pegasus functionality and for the definition and documentation

of releases.

Specifically the following PEPs define the characteristics of this

Pegasus release. These PEPs are available at

OpenPegasus Approved PEPs.</a>

MultiRequest Oprations - Pegasus does not support the DMTF defined MultiRequest

Operation option.

<ol>

</li>

<li>

PEP 296 - OpenPegasus Release Definition - This PEP is used

throughout the development of this version as the control point for

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

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

LocalOnly option on some 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>

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

Options  for Selected

Platforms</li>

MOFCompiler namespace pragma - The Pegasus compiler does not support the namespace pragma.

<li>

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

interfaces for clients and providers that are considered external and

therefore "frozen".

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

<li>

controlled through Pegasus PEP documents.  PEP 97 is the controlling document

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

this release and lists the original set of changes proposed and the status of

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

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 this release were:

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Expansion of platform globalization.</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Expansion of SLP support (still

experimental and by default not compiled in the 2.4 release).</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Inclusion of the Pluggable Provider   manager

(Providermanager2)as the default provider manager. Note that the original

provider manager will NOT be supported in the future.</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Inclusion of Pluggable

CMPI provider manager and the JMPI provider.  </li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Inclusion of the out-of-process

provider mechanism and the remote provider mechanism for CMPI. (Experimental)</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Addition of the binary repository

option. (Experimental)</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Addition of the shared namespace

concept so that class and qualifier definitions can be shared between multiple

namespaces. (Experimental)</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Refactoring of the HTTP monitor.</li>

<li class=MsoNormal style='color:black;mso-list:l21 level1 lfo27;tab-stops:

list .5in'>

Addition of HTTP chunking.

Note that the internal segmenentation of operation responses allowing better control of memory within

the cimom is planned for the future.</li>

</ol>

Note that there were a number of objectives that were not completely achieved

including: <o:p></o:p>

<li class=MsoNormal style='color:black;mso-list:l10 level1 lfo30;tab-stops:

list .5in'>Complete move to segmented operation responses and positive control of memory

for operations.   The chunking code has been incorporated and the

Pegasus client and the Server HTTP components handle chunking.  The

components necessary to segment operation responses from the providers was not

completed and will be included in a future version.</li>

</ol>

The complete set of PEPs defined for this release is

defined in PEP 97.

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

The current bug list for Pegasus is openly available on the

<a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus web

site</a>.  As of the release of 2.4 release date, the following list represents

what the Pegasus community feels are a subset of  open bugs with

OpenPegasus 2.4 that may be of particular interest to users. Please see the bug reports

(the number is a link to the report) to determine if there are any workarounds,

patches, etc. for particular bugs.

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=730

style='width:437.95pt;mso-cellspacing:0in;mso-padding-alt:2.4pt 2.4pt 2.4pt 2.4pt'>

<span

style='mso-fareast-font-family:"Times New Roman"'><a

href="buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Pegasus+CLI+Commands&product=PegasusCIMOM&product=PegasusClient&product=PegasusCompiler&product=PegasusGeneral&product=PegasusJavaCIMClient&product=PegasusProvider&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&newqueryname=&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id">ID</a>

<o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'><a

class=SpellE>Sev</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'><a

class=SpellE>Pri</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'><a

class=SpellE>Plt</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'><a

<o:p></o:p>

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=14">14</a> <o:p></o:p>

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

MOF

Compiler does not support aliasing <o:p></o:p>

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=377">377</a> <o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>enh<span style='mso-fareast-font-family:

"Times New Roman"'> <o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>Multirequest operations<span style='mso-fareast-font-family:

"Times New Roman"'> not supported <o:p></o:p>

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=424">424</a> <o:p></o:p>

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>XMLParser<span style='mso-fareast-font-family:

"Times New Roman"'> removes whitespace <o:p></o:p>

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=482">482</a> <o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>maj<span style='mso-fareast-font-family:

"Times New Roman"'> <o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

Absence

of REFERENCECLASSNAME in XML causes error <o:p></o:p>

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=786">786</a> <o:p></o:p>

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>CIMRepository<span style='mso-fareast-font-family:

"Times New Roman"'> enumerateinstances <span

class=SpellE>deepInheritance, etc. procesing

</td>

</tr>

<a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1195">1195</a> <o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>maj<span style='mso-fareast-font-family:

"Times New Roman"'> <o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>ResponseHandler<span style='mso-fareast-font-family:

"Times New Roman"'> should clone CIM* objects before modifying

them

</td>

</tr>

<tr>

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1285" style="color: blue; text-decoration: underline; text-underline: single">1285</a> <o:p></o:p>

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>EnumerateInstanceNames<span

style='mso-fareast-font-family:"Times New Roman"'> generates namespace error <span

class=SpellE>CIMException

</td>

</tr>

<tr>

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1307" style="color: blue; text-decoration: underline; text-underline: single">1307</a> <o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>maj<span style='mso-fareast-font-family:

"Times New Roman"'> <o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

Functionality on errors with Enumerate Functions. Should we

generate error or send existing data. Today we pass data.

</td>

</tr>

</td>

</td>

</td>

</td>

</td>

</tr>

</table>

<span style='mso-fareast-font-family:"Times New Roman";

display:none;mso-hide:all'><o:p> </o:p>

<h2><a name="Bugs Corrected in This Release">Bugs

<li>

Corrected in This Release</a>

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

</h2>

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

The current bug list for Pegasus is openly available on the

<a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus web site bug

database</a>.  The database can be searched for bugs fixed based on date

and Pegasus version.

Specifically the following Bugs which were listed in the release notes for

Pegasus 2.3.2 have been fixed.

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=730

style='width:437.95pt;mso-cellspacing:0in;mso-padding-alt:2.4pt 2.4pt 2.4pt 2.4pt'>

<span

style='mso-fareast-font-family:"Times New Roman"'>

<o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'>

class=SpellE>Sev</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'>

class=SpellE>Pri</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'>

class=SpellE>Plt</a> <o:p></o:p>

</td>

<span

style='mso-fareast-font-family:"Times New Roman"'>

<o:p></o:p>

</td>

</tr>

544</a>

</td>

maj

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

MOF compiler does not convert escape characters

</td>

</tr>

1054</a> <o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>enh<span style='mso-fareast-font-family:

"Times New Roman"'> <o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>cimserver stop responding after stress query of repository <o:p></o:p>

</td>

</tr>

nor</td>

P2</td>

All</td>

Sample providers should not be declared in Pegasus namespace</td>

</tr>

nor</td>

nor</td>

PC</td>

MOF compiler does not handle "/* ... */" comments.</td>

</tr>

</td>

maj

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

<span style='mso-fareast-font-family:

"Times New Roman"'>Disabling https prevents indication delivery through http. <o:p></o:p>

</td>

</tr>

</table>

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

The Pegasus project is controlled largely through a set of documents (PEPs)

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

that serve as the definition and review mechanism for new and modified Pegasus

approved PEP

functionality and for the definition and documentation of releases.

repository and the OpenPegasus source tree root directory)

Specifically the following PEPs define the characteristics of this Pegasus

</li>

release.

<ol>

<li>PEP 189 - OpenPegaus 2.4 External Interfaces</li>

<li>PEP 188 - OpenPegaus 2.4 Packaging Definition for Selected Platforms</li>

<li>PEP 185 - Pegasus 2.4 Release Notes (This document)</li>

<li>PEP 181 - OpenPegasus 2.4 SDK Packaging Definition</li>

<li>PEP 175 - Pegasus readme.txt for 2.4 (also in the Pegasus source tree root

directory).</li>

<li>PEP 97 - OpenPegasus Release Definition - This PEP is used throughout the

development of this version as the control point for functionality that will

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

2.4 functionality changes.</li>

</ol>

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

The following documentation is available for the this Pegasus

The following documentation is available for the this Pegasus release:

release:

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

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

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

list .5in'>Utilities - A combination of help generally available with the

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

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

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

list .5in'>API and  usage documentation - See the header files and the

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

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

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

documentation - See the header files and the HTML  API

documentation.  In particular the

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

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

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

Common APIs.</li>

documentation.  In particular the Common/tests unit tests contain

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

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

list .5in'>Building and Debugging Providers - Readme.html in the Pegasus Root

Directory, API documentation, and documentation from the Pegasus Technical

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

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

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

list .5in'>Building and Debugging Clients - API documentation and the

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

documentation on the Pegasus Technical Workshop which is available on the

documentation, and documentation from the Pegasus Technical Workshop

Pegasus web site.</li>

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

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

list .5in'>Compiler operation and commands - compiler help (cimmofl

-h)</li>

<li class=MsoNormal style='color:black;mso-list:l2 level1 lfo33;tab-stops:

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

list .5in'>PEPs - The features of Pegasus that have been installed

Clients - API documentation and the documentation on the Pegasus

in this and the previous few versions are defined by Pegasus PEPs that are

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

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

</ul>

<o:p></o:p>

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

style='color:black'>

</div>

Development Company, L.P.; IBM Corp.; The Open Group; VERITAS Software

<span

Corporation

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

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

style="color: black;">

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

width="100%">

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

Open Group; VERITAS Software Corporation; Intel Corp.

Permission is hereby granted, free of

Permission is hereby granted, free of charge, to any

charge, to any person obtaining a copy  of this software and associated

person obtaining a copy  of this software and associated

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

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

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

merge, publish, distribute, sublicense, and/or sell copies of the Software, and

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

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

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

following conditions:

to do so, subject to the following conditions:

THE ABOVE COPYRIGHT NOTICE AND THIS

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION

PERMISSION NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF

NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE

THE SOFTWARE. THE SOFTWARE IS PROVIDED  "AS IS", WITHOUT

SOFTWARE. THE SOFTWARE IS PROVIDED  "AS IS", WITHOUT WARRANTY OF

WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE

ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE

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

LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION

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

OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION

THE USE OR OTHER DEALINGS IN THE SOFTWARE.

WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

</div>

</div>

</body>

</html>

Legend:

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

No CVS admin address has been configured