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

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

version 1.10, 2007/01/09 18:25:09

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

</style>

<style>

<!--

/* Font Definitions */

Line 448

Line 450

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 572

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 891

text-indent:-.25in;}

@list l19

{mso-list-id:1902863286;

mso-list-template-ids:740079056;}

@list l19:level1

{mso-level-number-format:bullet;

Line 944

Line 949

{margin-bottom:0in;}

-->

</style>

<style>

/* Style Definitions */

table.MsoNormalTable

Line 959

Line 965

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

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

name="City"/>

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

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

name="place"/>

<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:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"

name="date"/>

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

<o:DocumentProperties>

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

<o:LastAuthor> </o:LastAuthor>

Line 996

Line 999

</w:WordDocument>

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

</head>

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

style='color:black'>

Pegasus

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

</div>

<span

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

PEP #: 185

Title: Release Notes for OpenPegasus 2.4

PEP #: 287

Title: Release

Notes for OpenPegasus 2.6.0

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

Authors: Karl Schopmeyer

Status:  draft

Version History:

<tbody>

<o:p> </o:p>

</td>

Version: 1.4

<o:p> </o:p>

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

</td>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

Authors: Karl

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

style='color:black'>

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

</div>

</td>

Abstract: This document defines the release notes that support

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

<o:p>  19 December

style='color:black'>

2006</o:p>

</td>

</div>

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

Karl Schopmeyer

<ol>

</td>

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

Initial

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

</tr>

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

<tr>

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

RPMs: </a>

<ol>

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

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

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

The overall level of functionality in the Pegasus environment effective with

<td style="padding: 0.75pt;" height="21">Remove functionality description section</td>

this release is as follows:

<h3>CIM Server Functionality</h3>

</tr>

The following paragraphs list the functions in this release.  All

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.

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

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

<ol>

<li>Class Operations (getClass, <span

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 style="padding: 0.75pt;" height="21">Fix comments from 1.1. Note comments are in

Red in text for now.</td>

<h4>Indications</h4>

</tr>

Process indications are operational in the Server.  This includes support

<tr>

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

indications and the CIMXML indication handler.

<h4>Indication Listener</h4>

The generic components for a CIM

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

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>

<td style="padding: 0.75pt;" height="21">Clean up remaining comments and remove

comment markers.</td>

</tr>

<h4>Query Language</h4>

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="23">8 January</td>

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

<td style="padding: 0.75pt;" align="center" height="23">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="23">Move approved PEP, reflecting

changes to 1.3 for approval</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>

</tbody>

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

</table>

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

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

<o:p> </o:p>

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

<h4> Platform Management Functions</h4>

Abstract: This document defines the release notes for the 2.6.0 release of the Pegasus CIM Server.

The purpose of this PEP is simply 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. <a href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35" target="_self">

</a>

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

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>

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

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

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>

</o:p></h2>

<li>DMTF Interop classes including __Namespace,  <span

class=SpellE>CIM_Namespace, CIM_ObjectManager,

CIM_CommunicationMechanism, and CIMOMStatistics.</li>

</ul>

<h4>Generic Providers</h4>

<ol>

Generic OperatingSystem provider. See the

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

directory src/Providers/generic.

<h4>Test/Sample Providers</h4>

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

Release</a></li>

See the directories src/Providers/TestProviders

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

and src/Providers/Sample for more information about test and

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

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>

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

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

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

with DMTF Specifications</a></li>

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

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

OpenPegasus Release Control and Version Definition Documentation</a></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><a href="#General%20Documentation">General

Documentation</a></li>

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

<h2>Availability

of this Release</h2>

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

This release is available in a number of forms including:

189

available from the web site(<a

<ul>

href="../Administrator/My%20Documents/processes/www.openpegasus.org">www.openpegasus.org</a>).

That document is the authorative source for the list

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

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

downloaded from the OpenPegasus Web

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

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

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

<li>OpenPegasus  binary and source RPMs on the OpenPegasus web

compatible with this release without compilation.  There have been

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

extensions and new interfaces added for this release and these are marked as

experimental.   The Pegasus public

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

interfaces includes the following major functions

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

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

snapshots page</a>.</li>

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

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

</ul>

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

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

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

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

WEB site</a>.

</ol>

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

Pegasus source

tree.

</div>

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

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

Pegasus overall status by release is defined by  a

public SDK including:

<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) and a description of

each feature.Pegasus 2.6.0

is a major release, extending Pegasus 2.5 in selected

areas as described in the Pegasus  PEP defining this release (see PEP 218)

.

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

more information access the documented PEP:

Table of Major Changes for this Release

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

borderColorLight=#cccccc border=1>

<TBODY>

<TH bgColor=#E0E8EF>Description</TH>

<TH bgColor=#E0E8EF>Posted PEP Version</TH>

</TR>

<TD align="left">Embedded Instance Support in Pegasus</TD>

<TD>

1.3</a>

</TD>

</TR>

<TD align="left">Providing SMI-Server Profile through OpenPegasus</TD>

<TD>

1.5.1</a></TD>

</TR>

<TD align="left">Incorporation of CIM_Error into OpenPegasus Infrastructure</TD>

<TD>

1.4</a>

</TD>

</TR>

<TD align="left">Language Interfaces</TD>

<TD>

1.0</a>

</TD>

</TR>

<TD align="left">Reducing Pegasus Code size and static memory usage</TD>

<TD>

1.3.1</a>

</TD>

</TR>

<TD align="left">Indication Subscription Management</TD>

<TD>

1.2</a>

</TD>

</TR>

<TD align="left">Audit Logging</TD>

<TD>

1.4</a></TD>

</TR>

<TD align="left">SSL Certificate Management Command Interfaces</TD>

<TD>

1.2</a></TD>

</TR>

<TD align="left">CMPI 2.0 Currency</TD>

<TD>

1.1</a>

</TD>

</TR>

<TD align="left">SLP enhancements for Pegasus 2.6</TD>

<TD>

1.5</a></TD>

</TR>

<TD align="left">Repository Archive</TD>

<TD>

1.1</a>

</TD>

</TR>

</TBODY>

</TABLE>

</UL>

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

<ol>

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

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

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

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

extensions to the Client APIs</li>

</ol>

<o:p> </o:p>

<h2>OpenPegasus Relationship to

CIM/WBEM Standards</h2>

The APIs are documented in

Pegasus was designed and implemented to comply with the DMTF

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

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

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

to which this version of Pegasus aims to conform today.

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

<h3>WMI Mapper</h3>

The WBEM to WMI Mapper provides a way to access

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

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

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

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

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

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

authenticates these credentials, verifying if the provided credentials have

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

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

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

WMI Mapper impersonates the user credentials provided

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

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

contain user credentials.

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

Standards</a></h2>

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

<tbody>

level of the DMTF specifications which which Pegasus conforms today.

<tr>

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

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

<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%">Version 2.2 with Addendum</td>

<td width="33%">DSP 0004 - CIM Infrastructure Specification</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.9 Final, Jan. 2005 ( default) 2.13.1 (available in

pegasus CVS)</td>

</tr>

</tbody>

</table>

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

<h2><a name="Conformance with DMTF Specifications">Conformance 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

operation. The supported platforms for this Pegasus release are:

<ol>

<li>Provider Registration - Pegasus supports registration

through a set of Pegasus Provider registration classes rather than

support the DMTF defined Provider Qualifier. Pegasus will not support

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

provider registration.  This is not a deviation from the specifications but

is a different method of registration than many CIM Servers and means that the

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

<li> Indications -Today Pegasus supports process indications and

lifecycle indications when defined specifically by providers. Pegasus does not

support lifecycle indications if they are not defined by the provider or for

changes to CIM Classes.

For more information see the Pegasus CVS

file  <a name="comtag_137"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

<li>

IncludeQualifiers

option on Instance Operations

The DMTF specifications have deprecated the use of qualifiers on instance

operations with the 1.2 CIM Operations Specification.  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. See Appendix C of this

specification for more information.</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>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:

<tbody>

Platform and

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

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

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

Platform and OS<span

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

</td>

Compilers<span

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

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

</td>

</tr>

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

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

</td>

HP aC++

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

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

</td>

</tr>

PowerLinux<span

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

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

</td>

gcc<span

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

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

</td>

</tr>

zLinux<span

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

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

</td>

gcc<span

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

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

</td>

</tr>

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

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

</td>

gcc<span

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

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

</td>

</tr>

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

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

</td>

gcc<span

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

gcc

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

</td>

</tr>

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

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

</td>

Microsoft

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

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

Microsoft

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></o:p>

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

</table>

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

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>

Windows XP<o:p>, Windows

Further information regarding Pegasus support on HP platforms can be found at:

2003</o:p>

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

<o:p> </o:p>

</td>

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

It is a major goal

Microsoft

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

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

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

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

<ol>

</td>

<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

</tr>

qualifiers on some 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>

CIM MOF compiler function for instance aliasing - The

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

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

planned for a future version.

</li>

<td style="padding: 0.75pt; width: 173.25pt;" height="43" width="289"> gcc 3.3,

<li>

gcc 4.01</td>

MultiRequest Oprations - Pegasus does not support the DMTF defined MultiRequest

</tr>

Operation option.

</li>

<tr>

<li>

LocalOnly option on some instance Operations -

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

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>

</big></td>

<li>

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

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

Alpha and above</big> </td>

</li>

</tr>

</ol>

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

<tr>

The development and release of each version of Pegasus is defined and

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

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

this release and lists 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 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>

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

</td>

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

</tr>

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

<tr>

<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

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

defined in PEP 97.

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

</big></td>

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

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

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

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

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

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

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

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

Corrected in This Release</a>

</h2>

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>

</tbody>

</table>

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

Platform patches

The following is a list of platform

patches Pegasus requires.

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

RHAS

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

2.1 needs the update to fix Red Hat Bugzilla 98815.

functionality and for the definition and documentation of releases.

Specifically the following PEPs define the characteristics of this Pegasus

release.

</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="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>.  Note that all changes  committed for this release have been marked

with the keyword 2.6.0_APPROVED so that

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

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

were documented through bugs.  Thus bugs 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.  Therefore, a search of

the bugzilla base for bugs with the tag 2.6.0_Approved will yield all changes to

the Pegasus CVS tree for Pegasus 2.6.0.

    - Changes for Pegasus 2.6.0 release (bugs Tagged

2.6.0_APPROVED) 

Pegasus 2.6.0_APPROVED bug list</a>

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

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

The Pegasus project is controlled largely through a set of documents

(PEPs) that serve 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 on as

OpenPegasus Approved PEPs.</a>

<ol>

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

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

<li>

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

PEP 218 - OpenPegasus Release Definition - This PEP is used

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

throughout the development of this version as the control point for

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

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

directory).</li>

represent the Pegasus  functionality changes for this version of Pegasus.</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

<li>

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

PEP 277 -  OpenPegasus  Build and Configuration

2.4 functionality changes.</li>

Options  for Selected

Platforms</li>

<li>

PEP 278 OpenPegaus 2.5 External Interfaces - Lists the public

interfaces for clients and providers that are considered external and

therefore "frozen".

</li>

<li>

PEP 279 - OpenPegasus  SDK Packaging Definition - Defines the

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

<li>PEP 280 - Pegasus  Runtime Packaging Definition - Defines the

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

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

approved PEP

repository and the OpenPegasus source tree root directory)

</li>

<li>PEP 289  - Pegasus readme.txt for this release (Located in PEP repository

and also in the OpenPegasus

source

tree root directory).</li>

</ol>

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

The following documentation is available for the this Pegasus release:

The following documentation is available for the this Pegasus

release:

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

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

-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

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

documentation.  In particular the

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

Common APIs.</li>

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

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:

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

documentation on the Pegasus Technical Workshop which is available on the

Pegasus web site.</li>

<li class=MsoNormal style='color:black;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:

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

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

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

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

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

documentation - See the header files and the HTML  API

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

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

documentation.  In particular the Common/tests unit tests contain

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

<li class="MsoNormal" style="color: black;">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;">Building and Debugging

Clients - API documentation and the documentation on the Pegasus

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

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

commands - compiler help (cimmofl -h)</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>

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

</ul>

style='color:black'>

<o:p></o:p>

</div>

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

Group; VERITAS Software Corporation; Intel Corp.

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

Corporation

Permission is hereby granted, free of

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

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

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

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

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

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

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

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

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

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

following conditions:

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

THE ABOVE COPYRIGHT NOTICE AND THIS

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

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

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE

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

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

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

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

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

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

FOR ANY 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 SOFTWARE OR

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

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.4
changed lines
	Added in v.1.10

No CVS admin address has been configured