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

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

version 1.8, 2006/03/28 20:27:53

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 959

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 993

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

</w:WordDocument>

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

</head>

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

style="color: black;">

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

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

style='color:black'>

width="100%"></div>

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

align="center">Pegasus

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

</div>

<span

style="color: black;">

<span

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

PEP #: 230

Title: Release

Notes for OpenPegasus 2.5

PEP #: 185

Version: 1.8

Created: <st1:date

Title: Release Notes for OpenPegasus 2.4

year="2004" day="23" month="3">1 April 2005</st1:date>

Authors: Warren

Version: 1.4

Grunbok, Karl Schopmeyer

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

Status:  draft

Version History:

Authors: Karl

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

Schopmeyer

cellpadding="0" cellspacing="1" width="100%">

<tbody>

Status:  draft

<td

Version History:

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">

<span

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

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

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

</td>

<td

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">

<span

<span

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

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

</td>

<td

<span

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">

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

<span

</td>

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

</td>

<span

<td

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

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">

</td>

<span

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

<span

</td>

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

</tr>

</td>

</tr>

<span

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

<span

</td>

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

</td>

<span

style="font-family: Arial; color: black;"><o:p>  1,April

<o:p>

2005

23 July 3004</o:p>

</o:p>

</td>

<span

<span

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

style="font-family: Arial; color: black;"><o:p>Warren Grunbok

</td>

</o:p>

</td>

Initial

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

<span

</td>

style="font-family: Arial; color: black;">Initial

</tr>

Submission<o:p>

</o:p>

</td>

1.1</td>

</tr>

26 August 2004</td>

<td style="padding: 0.75pt;" align="center">26, June 2005

KS</td>

</td>

<td style="padding: 0.75pt;">Warren Grunbok

Incorporate comments from 1.0</td>

</td>

</tr>

<td style="padding: 0.75pt;">revisions based on Comments

</td>

</tr>

1.2</td>

<tr>

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

6  October 2004</td>

</td>

<td style="vertical-align: top;">22, July 2005

KS</td>

</td>

<td style="vertical-align: top;">Warren Grunbok

Incorporate comments from Review of 1.1</td>

</td>

</tr>

<td style="vertical-align: top;">fixed some broken links, added

security notes.

</td>

1.3</td>

</tr>

<tr>

24 October 2004</td>

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

</td>

KS</td>

<td style="vertical-align: top;">23, Aug 2005

</td>

Update with comments from Version 1.2</td>

<td style="vertical-align: top;">Warren Grunbok

</tr>

</td>

<td style="vertical-align: top;">Revisions based on comments

</td>

1.4</td>

</tr>

<tr>

1 November 2004</td>

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

</td>

KS</td>

<td style="vertical-align: top;">30.Aug 2005

</td>

Comments from 1.3</td>

<td style="vertical-align: top;">Warren Grunbok

</td>

<td style="vertical-align: top;">More revisions based on Aug 26

review in Architecture meeting

</td>

</tr>

<tr>

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

</td>

<td style="vertical-align: top;">12, Sept 2005

</td>

<td style="vertical-align: top;">Warren Grunbok

</td>

<td style="vertical-align: top;">Minor comment updates from 1.4

version  (balloted version)

</td>

</tr>

<tr>

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

</td>

<td style="vertical-align: top;">14,Sept 2005

</td>

<td style="vertical-align: top;">Warren Grunbok

</td>

<td style="vertical-align: top;">additional comments from review

</td>

</tr>

<tr>

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

</td>

<td style="vertical-align: top;">20, Sept 2005

</td>

<td style="vertical-align: top;">Warren Grunbok

</td>

<td style="vertical-align: top;">Added Solaris back in, corrected

Provider security statement, and clarified Solaris support for 2.5

</td>

</tr>

<tr>

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

</td>

<td style="vertical-align: top;">21, Sept 2005

</td>

<td style="vertical-align: top;">Warren Grunbok

</td>

<td style="vertical-align: top;">Clarified SLP enablement

Paragraph and correction of Power on Linux in platform table

</td>

</tr>

</tbody>

</table>

<o:p> </o:p>

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

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

style="color: black;">

style='color:black'>

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

width="100%"></div>

Abstract: This document defines the release notes for the 2.5

version of the Pegasus CIM Server. <span

</div>

style="font-size: 9pt;"><a

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" style="text-align: center;" align="center"><span

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

style="color: black;">

style='color:black'>

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

width="100%"></div>

<o:p> Contents

</o:p>

</div>

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

<ol>

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

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

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

this Release</a></li>

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

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

Standards</a></li>

This Release</a></li>

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

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

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

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

Specifications</a></li>

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

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

Platforms</a></li>

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

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

<li>

with DMTF Specifications</a></li>

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

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

in This Release</a></li>

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

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

Bugs</a></li>

<li> <a

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

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

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

Documentation</a></li>

</ol>

<h2><a name="Availability_of_this_Release_"></a><span

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

style="color: black;"><a name="Availability_of_this_Release"></a>Availability

of this Release</h2>

This release is available in a number of forms including:

<ul>

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

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

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

downloaded from the OpenPegasus Web

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

site at <a

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

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

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

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

versions.</li>

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

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

also available that can be used to build binaries for most

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

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

defined on the

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

OpenPegasus CVS repository web page (see the

subsequent snapshots that are made available in the Pegasus CVS are

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

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

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

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

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

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

The instructions for acquiring the released code are on the

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

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

WEB site</a>.

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

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

tree.

Pegasus source

tree.

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

Instructions for building the Linux RPMs: <span

RPMs: </a>

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

</>

<ol>

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

<li>Download

</a></li>

tog-pegasus-2.5.0-1.src.rpm. </li>

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

<li>rpm

</a></li>

-ih tog-pegasus-2.5.0-1.src.rpm </li>

<li>

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

<span

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

class="norm">Build

the rpms:

</li>

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

<table

style="margin-left: auto; margin-right: auto; text-align: left; width: 712px; height: 116px;"

The overall level of functionality in the Pegasus environment effective with

border="1" cellpadding="2" cellspacing="2">

this release is as follows:

<tbody>

<tr>

<td

style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Distro</td>

<td

style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Command

</td>

</tr>

<tr>

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

</td>

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

class="norm">rpmbuild -bb /usr/src/redhat/SPECS/tog-pegasus-

2.5.0-1.spec</td>

</tr>

<tr>

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

</td>

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

class="norm">rpmbuild -bb /usr/src/redhat/SPECS/tog-pegasus-

2.5.0-1.spec</td>

</tr>

<tr>

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

</td>

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

class="norm"> rpmbuild -bb /usr/src/packages/SPECS/tog-pegasus-

2.5.0-1.spe</td>

</tr>

</tbody>

</table>

<li style="font-weight: bold;">After

the build the rpms will be in the

following locations:</li>

<table style="width: 100%; text-align: left;" border="1"

cellpadding="2" cellspacing="2">

<tbody>

<tr>

<td

style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Distro

</td>

<td

style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Location

of RPMs after the build is complete

</td>

</tr>

<tr>

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

</td>

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

class="norm">/usr/src/redhat/RPMS/[arch]/tog-pegasus-

2.5.0-1.[arch].rpm

/usr/src/redhat/RPMS/[arch]/tog-pegasus-sdk- 2.5.0-1.[arch].rpm.<span

style="font-family: "times new roman";"><span

style="font-family: "times new roman";"><span

class="norm">     </td>

</tr>

<tr>

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

</td>

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

class="norm">/usr/src/redhat/RPMS/[arch]/tog-pegasus-

2.5.0-1.[arch].rpm

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

</tr>

<tr>

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

</td>

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

class="norm">/usr/src/packages/RPMS/[arch]/tog-pegasus-

2.5.0-1.[arch].rpm

/usr/src/packages/RPMS/[arch]/tog-pegasus-sdk- 2.5.01-.[arch].rpm.</td>

</tr>

</tbody>

</table>

</ol>

<h2><a name="Functionality_of_This_Release"></a><span

style="color: black;">Functionality of This Release</h2>

New for the Pegasus 2.5 release is a Feature Maturity Dashboard. 

This document shows the Pegasus users and developers the maturity of

the various features found in Pegasus using a simple color coded

key.  That document can be found here:  <a

href="http://www.openpegasus.org/page.tpl?ggid=799">Feature

Maturity Link</a>

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.

The following paragraphs list the functions in this release.  All

All functions are considered community tested and operational unless

functions are considered community tested and operational unless specifically

specifically noted below. Features that are marked alpha or beta are

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

not generally of the quality or completeness for production

quality or completeness for production usage.  Interfaces that are

usage.  Interfaces that are part of the Pegasus public

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

interface definitions but that the Pegasus team feels may change are

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

marked experimental. In many cases these features  and interfaces

interfaces are conditionally compiled with special environment variables. PEP

are conditionally compiled with special environment variables. <a

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

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

conditionally compiled in this release.

style="color: rgb(255, 0, 0);"><span

style="text-decoration: underline;">PEP 200 </a>

provides more detailed information on how to enable

functionality that is conditionally compiled in this release.

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

<ol>

<li>Class Operations (getClass, <span

<li>Class Operations (getClass, <span

class=SpellE>deleteClass, modifyClass, <span

class="SpellE">deleteClass, modifyClass,

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

enumerateClass, enumerateClassNames)</li>

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

<li>Qualifier Operations (getQualifier, setQualifier,

<li>Instance Operations (getInstance, <span

deleteQualifier) </li>

class=SpellE>deleteInstance, modifyInstance,

<li>Instance Operations (getInstance, <span

enumerateInstance, enumerateInstanceNames,

class="SpellE">deleteInstance, modifyInstance,

getProperty, setProperty)</li>

enumerateInstance, <span

<li>Association Operations (references, referencenames,

class="SpellE">enumerateInstanceNames, getProperty,

associators, associatornames)</li>

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

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

alpha quality because it has only been contributor tested and there is no test

considered at alpha quality because it has only been contributor

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

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

</li>

</ol>

</blockquote>

</div>

<h4>Indications</h4>

<ul>

Process indications are operational in the Server.  This includes support

<li>Process indications - Process indications are operational in

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

the

indications and the CIMXML indication handler.

Server.  This includes support

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

for

indications and the CIMXML indication handler.</li>

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

lifecycle indications (ie. those

classes of indications derived from CIM_ClassIndication and

CIM_InstIndication) can now be created. Pegasus 2.5 provides some

enablement for the generation of lifecycle indications. For more

details, refer to

</ul>

<h4>Indication Listener</h4>

The generic components for a CIM Listener and a

The generic components for a CIM

listener API are operational.  This includes the functions for

Listener and a listener API are operational.  This includes the functions

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

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

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

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

as an indication listener in the Pegasus server.

indication listener in the Pegasus server.

Pegasus 2.5

includes a new standalone listener that is separate

from the current standalone CIMListener and the ExportServer listener

in the CIM server.

The use model that this listener fits is the following:

<ul>

<li> The listener may be packaged as

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

another application. </li>

<li> Consumers

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

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

</ul>

<span

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

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

new "Dynamic Listener" provides a solution for the above use model. It

is essentially a lightweight, pluggable listener that

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

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

bypasses traditional registration procedures.  See <a

href="http://www.openpegasus.org/pp/protected/upreviews/20/1303/PEP195_CIMListenerEnhancementsv1_6.htm"><span

style="color: rgb(51, 51, 255); text-decoration: underline;">PEP 195</a> <span

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

details.

<h4>Object Normalization</h4>

The Object Normalizer is an entity introduced in Pegasus 2.4 that

ensures

objects delivered from providers are complete and accurate. Two major

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

Normalizer drops instances it considers bad, and 2) the Object

Normalizer code slows performance. These issues are now addressed by

moving the Object Normalizer from the Dispatcher to the Response

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

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

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

CIMOM/provider boundary.

Two new configuration properties were added to control object

normalization.

<ol>

<li>enableNormalization (true|false) - Enables or disables object

normalization for provider objects.</li>

<li>excludeModulesFromNormalization (colon delimited list of

provider modules) - List the provider modules by name (as specified in

PG_ProviderModule.Name) to exclude from normalization. Keep in mind

that all objects managed by all providers will be excluded from

normalization if its module name appears in this list.

</li>

</ol>

<h4>Embedded Object support</h4>

Pegasus 2.5 now provides embedded object support. The proposed solution

is restricted to the following:

The only representation for embedded objects supported by this

PEP is CIM-XML.

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

internally to represent embedded objects. When externalized (via

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

INSTANCE or CLASS elements, in accordance with the CIM Infrastructure

Specification.  Embedded instances will also carry the

EmbeddedObject attribute with

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

</blockquote>

<h4>Query Language</h4>

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

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

used for filters and in 2.4 for execQuery.

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

been implemented in Pegasus 2.4 but is considered alpha quality.

CQL Stage 1 has been included for Pegasus 2.5.  PEPs 138,

193, 205 combine to describe the function submitted.

<h4>Class Repository</h4>

<h4>Schema Repository</h4>

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

By default, Pegasus uses an XML-based

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

schema repository. A binary encoding option is also available.<span

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

style="font-family: "times new roman";">

repository functions are considered alpha level because they have only been

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

To use the binary encoding feature a new configuration

suite.

properties was

added:

enableBinaryRepository (true|false) - Enables

disables binary repository.

<div style="margin-left: 40px;"> In addition to the binary

repository, the compressed repository

functionality has

been added as a build time conditional compile. It defaults to not

support

compression. When enabled the zlib library, used for the compression

algorithims, must be installed on the build and target systems. With

compression enabled records are always written compressed but both

compressed

and non-compressed records can be read allowing an easy migration path.

Note:  <span

class="norm">Note:

Users may experience an incompatibility moving a binary repository from

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

the ability to maintain compatibility with subsequent releases. (See

bugzilla 3642 for details.) <span

style="color: rgb(51, 102, 255);">See bugzilla 3642 for details.

</div>

<h4>Compressed Repository</h4>

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

style="color: rgb(0, 0, 0);" color="RED">A compressed repository

feature has been added for

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

the

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

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

feature is

documented in PEP 214 and also in a Readme

(readme.compressed_repository). It is

considered experimental today because it is not in the automated tests.

Note

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

activiated for

automatic tests.

</div>

<h4>Instance Repository</h4>

The

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

Pegasus schema repository may also be configured to hold instance

instance  repository may be conditionally used as the default repository

data.  <font

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

style="color: rgb(0, 0, 0);">Although instances may be place in the

to NOT use the instance repository as default).

repository

it was not designed as a

high volume data store.

<h4>Security Considerations

</h4>

OpenPegasus 2.5 (and

prior) contains several mechanisms to perform authorization, but none

of these authorization checks are performed by default.

By registering any provider which fails to do appropriate authorization

checks, the consequences may include information leakage, data

corruption, or unintended elevation of privilege. Please ensure that

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

your systems and data:

1. Only install/register providers which perform authorization

appropriate for your environment.

<div style="margin-left: 40px;"><font style="color: rgb(0, 0, 0);"

color="RED">a. For providers, this may include registering to

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

performing authorization checks within the provider.

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

your environment have performed sufficient authorization checks. Also,

monitor announcements of security defects in those providers and follow

the recommendations in those announcements as soon as possible.

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

you are shipping have performed appropriate authorization checks, and

relay announcements of discovered security defects to your users.

</div>

2. Restrict users with

access to Pegasus to a specific authorized user group of trusted

individuals.

3. Namespace authorization is also available.

For administration issues please refer to

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

<h4>Server Security</h4>

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

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

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

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

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

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

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

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

implemented in Pegasus using the OpenSSL

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

libraries. Pegasus does not provide the OpenSSL

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

libraries but SSL can be used on any platform supported by <span

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

class="SpellE">OpenSSL.  Minimum level known to work

supported by OpenSSL.  Minimum level known

is  0.9.6c .   This release of Pegasus was tested with

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

0.9.6k.  See <a

with 0.9.6k.  See <a

href="http://www.openpegasus.org/pp/uploads/40/Application%20Data/Microsoft/Word/www.openssl.org">openssl.org</a>

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

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

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

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

SSLv3

and TLSv1 by default. SSLv2 is

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

See<a

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

PEP 200</a> for details on

configuration.

</li>

</ol>

<h4>Client Security<span

<h4> Platform Management Functions</h4>

style="font-style: italic;"></h4>

Certificate management 

and User-based certificate authentication . A new control provider and

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

CLI for certificate management tasks. It expands upon the existing SSL

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

client verification support by providing a robust solution to managing

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

client certificates and certificate revocation lists via standard CIM

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

operations. It allows certificates to be associated with particular

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

system users for enhanced authorization capabilities.

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

CN/ Host

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

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

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

and are the responsibility of the client to implement on their

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

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

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

more details on client security.

list .5in'>Multiple pluggable provider managers.  Provider managers are provided for the Pegasus C++ provider interface, the CMPI C provider interface

Note: <span

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

style="color: rgb(0, 0, 0);">WBEM clients are responsible for SSL

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

certificate verification using Pegasus and/or SSL libraries as

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

appropriate. Consequences of not doing so include leakage of

data transfers and includes a mechanism for message support in mulitple

authentication credentials to unauthorized parties.

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

<h4>Platform Management Functions</h4>

experimental.</li>

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

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

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

the defined configuration parameters (cimconfig) and server command

use of this feature </li>

line options.<font

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

style="color: rgb(0, 0, 0);" color="RED">  NOTE: When installed

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

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

use of this feature</li>

enableAuthentication to true can result in improper operation of the

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

SLP

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

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

- See PEP 130

Administrator should change the user that the service runs under from

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

the Local

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

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

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

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

with the exception of HP OpenVMS.

</o:p></li>

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

capture using the <font

style="color: rgb(0, 0, 0);">CIM_StatisticalData classes in

the DMTF Interop model. This

function is considered alpha quality and conditionally compiled.

</li>

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

pluggable provider managers.  Provider managers are provided for

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

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

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

- Pegasus includes support for unicode data transfers and includes a

mechanism for message support in multiple languages using the open

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

Note that this is still marked experimental.</li>

<li class="MsoNormal" style="color: black;">Out-of-process

providers (Experimental) - See PEP 072 for more information on use of

this feature </li>

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

(Experimental) - See PEP 129 for more information on use of this feature</li>

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

the CMPI provider interface (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 in or out on

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

a platform basis. <a

environment variable PEGASUS_ENABLE_SLP.   Once compiled, SLP support

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

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

PEP 200</a> describes the use of proper environment variable use to

an SLP service agent in the Pegasus CIM severas and generates SLP advertisements compatible with the DMTF

enable or disable this code.  PEGASUS_DISABLE_SLP and

slp template specification. The SLP support also includes  extensions to the CIM

PEGASUS_ENABLE_SLP are the environment variables that control inclusion

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

of this feature.  Once compiled, SLP

(note that these interfaces are not yet part of the Pegasus public SDK).

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

support includes an SLP service agent in the Pegasus CIM sever and

generates SLP advertisements compatible with the DMTF slp template

specification. The SLP support also includes  extensions to the

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

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

public SDK).

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

exclude it from the build, then PEGASUS_DISABLE_SLP must be set.

<h4>Provider Managers</h4>

Pegasus is designed to support multiple Provider Managers to allow

Pegasus is designed to support multiple Provider Managers to allow multiple

multiple provider interfaces to the CIMOM.  The two default

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

provider managers are the Pegasus C++ Interface and Common

Interface.  This section defines the additional provider managers available

Manageability Programming Interface (CMPI) Interface.

with Pegasus 2.4.

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

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

Pegasus 2.5 includes

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

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

result of a project by the IBM SBLIM team (see 

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

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

class=GramE>see� <a

Manageability Programming Interface, which is an OpenGroup standard.

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

The CMPI

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

specification is available at:

which is in review now within the WBEMSource

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

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

standardized C level interface for creating providers that can be

This provides a standardized C level interface for creating providers that can

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

be registered with the Pegasus CIM Server in the same manner as the current C++

current C++ providers.  <span

providers.

style="font-family: "times new roman";">The

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

Today, the CMPI provider manager and interfaces are considered experimental

Pegasus 2.5.

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

specification is released. Information on writing providers with the CMPI

Information on writing providers with the CMPI interface is available

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

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

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

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

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

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

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

Pegasus source root directory.

Pegasus source root directory.

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

Pegasus includes an experimental provider manager for Java

Pegasus includes an experimental provider manager for Java provider

provider interfaces based on the SNIA provider interface

interfaces based on the SNIA provider interface definitions.  This provider

definitions.  This provider manager is  considered alpha

manager is  considered alpha quality and is not compiled in the default build.  

quality and is not compiled in the default build.   See

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

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

</blockquote>

<h3>    Providers</h3>

<h3>Providers</h3>

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

to run out of process at

There are a number of providers available in the Pegasus release.

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

process space.

Administrators should check the providers to

ensure that the provider vendor

has made use of available authorization capability.

</div>

There are a number of providers available

in the Pegasus release.

This includes providers in the following categories:

<h4>Pegasus Internal Providers</h4>

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

Pegasus provides a set of "internal" providers that have direct access to the

access to the CIMOM for information and provide information and

CIMOM for information and provide information and services to support the CIMOM

services to support the CIMOM and its administration.    The

and its administration.    The providers in this category are mostly defined in the directory src/pegasus/controlproviders

providers in this category are mostly defined in the directory

and include support for the following classes:

src/pegasus/controlproviders and include support for the following

classes:

<ul>

<li>DMTF Interop classes including __Namespace,  <span

class=SpellE>CIM_Namespace, CIM_ObjectManager,

class="SpellE">CIM_Namespace, CIM_ObjectManager,

CIM_CommunicationMechanism, and CIMOMStatistics.</li>

CIM_CommunicationMechanism, and

CIMOMStatistics.</li>

</ul>

<h4>CMPI Remote</h4>

Pegasus includes an experimental support for

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

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

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

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

and passes them on to CMPI style providers.

<h4>Generic Providers</h4>

Generic OperatingSystem provider. See

Generic OperatingSystem provider. See the

the

directory src/Providers/generic.

directory src/Providers/generic.

<h4>Test/Sample Providers</h4>

See the directories src/Providers/TestProviders

See the directories src/Providers/TestProviders

and src/Providers/Sample for more

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

information about test and

sample providers.

<h4>Managed System Providers</h4>

ComputerSystem, DNSAdmin,

ComputerSystem, DNSAdmin,

DNSService, Operating System, Process,

DNSService, Operating System, Process, Processor. For

Processor. For

more information on these providers see the documentation for each provider in

more information on these providers see the documentation for each

the directory src/Providers/ManagedSystem

provider in

the directory src/Providers/ManagedSystem

<h4>Server Statistics

</h4>

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

are implemented in this release. The statistics gathering is disabled

by default. It may be enabled or disabled by performing a

ModifyInstance operation on the singleton 'CIM_ObjectManager' instance

in the 'PG_InterOp' namespace to set the GatherStatisticalData property

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

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

from the Pegasus CVS repository.

<h4>

</h4>

<h4>SLP Provider</h4>

This provider acts as the definer of

This provider acts as the definer of  SLP

SLP information for SLP registration and also controls the Pegasus SLP

information for SLP registration and also controls the Pegasus SLP Service

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

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

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

it does not use internal functions of the CIMOM to generate any of its

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

information today. (conditionally compiled today)

</blockquote>

<h3>CIM_Schema</h3>

<h3>CIM_Schema</h3>

The default CIM_Schema loaded with this

release is

The default CIM_Schema loaded with this release is

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

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

a number of

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

local classes defined for Pegasus.  These are defined in the

directory.   CIM 2.9 preliminary

pegasus/Schemas

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

directory.   There are also a

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

number of older schema available in the CVS.

The mechanism to install other schemas than the default is defined

The mechanism to install other schemas than the default is

in the mak/config.mak

defined in the mak/config.mak

NOTE: The CIM 2.5 schema is

maintained in the

NOTE: The CIM 2.5 schema is maintained in the

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

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

test

environment.

<h3>Pegasus MOF Compilers</h3>

Pegasus implements a MOF compiler that can operate either at the

Pegasus implements a MOF compiler that can operate either at the client

client

interface to the Pegasus CIM Server (cimmof) or directly interfacing with a CIM

interface to the Pegasus CIM Server (cimmof)

repository (cimmofl).

or directly interfacing with a CIM

repository (cimmofl).

The direct interface compiler is used primarily to provide an initial

The direct interface compiler is used primarily to provide an

class/instance repository. WARNING:

initial

the use of cimmofl

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

registered to serve these  instances and simply installs the

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

instances in the

are registered providers, 2) corruption of the repository if the CIM Server is

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

running or, 3) MOF data that is loaded but not available until the server is

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

stopped and restarted in some cases.  Use of cimmofl in

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

general is discouraged and particularly  to manipulate

available until the server is stopped and restarted in some

instances served by a registered providers (ex.

cases.  Use of cimmofl in general is

Provider registration). Use of <span

discouraged and particularly  to manipulate

class=SpellE>cimmof rather that cimmofl is encouraged

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

wherever possible.

<h3>Client Tools</h3>

Lightweight statistics are now implemented for

<h4>   Pegasus CIM Server Adminstration</h4>

the

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

client,

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

and the

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

elapsed time spent on the network between client and server.

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

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

<h3>Pegasus CIM Server Administration</h3>

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

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

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

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

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

list .5in'>cimauth - Manage the CIM Server

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

authorization characteristics. Today this is authorizing users to

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

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

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

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

- Manage the CIM Server authorization characteristics. Today this is

list .5in'>cimprovider - Manage information

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

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

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

- Manage information about the providers .</li>

</ol>

<h4>Information client tools</h4>

Server admin

note:

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

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

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

specified in the configuration.  The new order for determining the

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

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

values.

</div>

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

in /etc/services is used.

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

used.

</div>

<h3>Information client tools</h3>

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

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

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

- output classes and/or instance information from the Pegasus

list .5in'>tomof - output classes and/or

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

instance information from the Pegasus repository in MOF or XML format.<o:p></o:p></li>

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

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

- Generate a set of standard information on the Domain

list .5in'>dnsinfo - Generate a set of standard

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

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>

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

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

- Generates a set of standard information from the Network

Schema.  Information generated varies by system because of the

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

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

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

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

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

</ol>

<h3>Test support Tools</h3>

<h4>Test support Tools</h4>

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

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

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

tests are defined throughout the Pegasus source tree typically in

list .5in'>Pegasus unit tests (available through the "tests"

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

option on the Pegasus make files) these tests are defined throughout the

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

Pegasus source tree typically in "tests" directories.       

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

<o:p></o:p></li>

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

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

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

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

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

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

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

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

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

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

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

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

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

benchmark test environment is provided which includes both a client and

list .5in'>wbemexec - Test tool that

provider component. See src/clients/benchmarkTest

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

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

Details of the Pegasus public interfaces for this release are listed

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

in PEP 209

189

available from the web site(<a

available from the web site(<a

href="http://www.openpegasus.org/pp/uploads/40/Administrator/My%20Documents/processes/www.openpegasus.org">www.openpegasus.org</a>).

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

That document is the authorative source

That document is the authorative source for the list

for the list of publicly supported Pegasus APIs.   The Client

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

and Provider API were originally frozen at the Pegasus version 2.1

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

release. The interfaces in the release of Pegasus 2.1 are forward

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

compatible to this release. Well-behaved clients and providers compiled

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

to the Pegasus 2.1 or 2.2 interfaces should be compatible with this

compatible with this release without compilation.  There have been

release without compilation.  There have been extensions and new

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

interfaces added for this release and these are marked as experimental.

experimental.   The Pegasus public

  The Pegasus public

interfaces includes the following major functions

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

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

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

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

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

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

function APIs</li>

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 addition, there are other client interfaces which are not today in the

in the public SDK including:

public SDK including:

<li class="MsoNormal" style="color: rgb(0, 0, 0);"><span style=""

lang="DA">CIM Listener APIs</li>

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

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

<li class="MsoNormal">CIM Listener

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

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

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

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

extensions to the Client APIs</li>

running or a physical separation between the indication listener and

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

several enhancements that are necessary to make CIM Listener scalable. <font

style="color: rgb(0, 0, 0);">Enhancements were deemed significant

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

basic capabilities, yet allows the existing CIMListener to remain the

same.</li>

<ul>

<li>New CIM Listener now provides selective

indication delivery.

</li>

<li>New CIM Listener

keeps all consumer libraries in memory for the duration of its

execution.

</li>

<li>New CIM Listener

is now pluggable.

</li>

<li>New CIM Listener

now provides reliable indication delivery.</li>

</ul>

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

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

</ol>

<o:p> </o:p>

<o:p> </o:p>

The APIs are

documented in

The APIs are documented in

their respective header files and  in HTML documentation based on

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

the information

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

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

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

the

OpenPegasus web site.

<h3>WMI Mapper</h3>

<o:p></o:p>

<h3>WMI Mapper</h3>

The WBEM to WMI Mapper provides a way to access

The WBEM to WMI Mapper provides a way

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

to access

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

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

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

requests

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

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

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

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

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

authenticates these credentials, verifying if the provided credentials have

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

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

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

account with

WMI Mapper impersonates the user credentials provided

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

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

this, the

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

WMI Mapper impersonates the user

contain user credentials.

credentials provided

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

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

browse WMI

Standards</a></h2>

data. Hence, ALL requests made to the WMI Mapper

MUST

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

contain user credentials.

level of the DMTF specifications which which Pegasus conforms today.

<h3>Indication Handlers</h3>

System Log Indication Handler

<div style="margin-left: 40px;">The SysLog Indication Handler is a new

for 2.5

type of Indication Handler which allows CIM Indications to be delivered

to the system syslog file. It has following features:

</div>

<ul>

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

an entry made by Syslog Indication Handler.</li>

</ul>

<ul>

<li>If a subscriber includes PerceivedSeverity property in the SELECT

list of the filter condition for the indication, the PerceivedSeverity

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

severity 'LOG_INFO' is used.</li>

<li>See <a

href="http://www.openpegasus.org/pp/uploads/40/7165/PEP206-SystemLogIndicationHandler.htm">PEP

206</a> for details.

</li>

</ul>

Email Indicaiton Handler

<div style="margin-left: 40px;">The Email Indication Handler is a new

for 2.5

type of Indication Handler that allows CIM Indications to be delivered

to a specified e-mail address.   See <a

href="http://www.openpegasus.org/pp/uploads/40/7166/PEP207-EmailIndicationHandler.htm">PEP

207</a>  for details.

</div>

<ol>

</ol>

<h2><a name="Relationship_to_CIMWBEM_Standards"></a>Relationship to

CIM/WBEM Standards</h2>

Pegasus was designed and implemented to comply with the DMTF

specifications The following table defines the level of the DMTF

specifications which which Pegasus conforms 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>

Line 1634

Line 2048

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

</tr>

</tbody>

</table>

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

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

Platforms</a></h2>

Each Pegasus release lists as 'active' platforms those

Each Pegasus release lists as supported platforms those

hardware/software platforms that have recognized ports for the Pegasus

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

code

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

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

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

regularly document issues and/or fix defects as the Pegasus

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

code base is changed. 

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

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

operation. The supported platforms for this Pegasus release are:

a group

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

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

Pegasus cannot be

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

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

Platform and OS<span

bugzilla database for a list of relevant defects that affect their

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

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

</td>

Pegasus release are:

Compilers<span

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

<table class="MsoNormalTable" style="width: 302.25pt;" border="1"

</td>

cellpadding="0" cellspacing="1" height="409" width="504">

</tr>

<tbody>

<td

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

style="padding: 0.75pt; background: rgb(153, 255, 153) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 126.75pt;"

</td>

height="26" width="211">

Platform and

HP aC++

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

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

</td>

<td

</tr>

height="26" width="289">

Compilers<span

PowerLinux<span

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

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

</td>

</tr>

gcc<span

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

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

width="211">

</td>

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

</tr>

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

zLinux<span

HP <span

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

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

</td>

</tr>

gcc<span

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

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

</td>

width="211">

</tr>

<span

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

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

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

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

gcc<span

<span

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

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

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

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

width="211">

</td>

<span

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

gcc<span

</td>

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

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

</td>

width="289">

</tr>

<span

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

</td>

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

</tr>

</td>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

Microsoft

width="211">

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

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

<span

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

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

width="211">

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

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

<span

style="color: black;">gcc

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

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="91"

width="211">

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

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="91"

width="289">

Microsoft

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

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

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

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

</td>

</tr>

<tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="69"

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

width="211">

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

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="69"

width="289">

Microsoft

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

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

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="43"

width="211"> MacOS version 10.2 and higher</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="43"

width="289"> gcc 3.3</td>

</tr>

<tr>

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

</big></td>

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

style="color: rgb(0, 0, 0);" color="RED">HP C++ V6.5-042 for OpenVMS

Alpha and above</big> </td>

</tr>

<tr>

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

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

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

style="color: rgb(0, 0, 0);">HP C++ V7.1-011 on OpenVMS IA64 and above</big>

</td>

</tr>

<tr>

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

color="RED">Solaris 8

* See below for additional info

</big></td>

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

Solaris:  Solaris testing

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

began late in the 2.5 release cycle, thus has not been thoroughly

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>

tested.  In order for Pegasus 2.5 to function properly on that

platform, changes documented in OpenPegasus Bugzilla 4179  must be

applied.

<h2>Platform patches</h2>

The following is a list of platform

patches Pegasus requires.

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

2.1 needs the update to fix Red Hat Bugzilla 98815.

</div>

Further information regarding Pegasus support on IBM platforms can

found at: <a

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

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

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

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

</o:p>

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

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

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. 

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

<li>Provider Registration - Pegasus supports registration

Pegasus Provider registration classes rather than support the DMTF defined Provider

through a set of Pegasus Provider registration classes rather than

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

support the DMTF defined Provider Qualifier. Pegasus will not support

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

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>

<font

Instance qualifiers and class

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

qualifiers on some Operations -

option on Instance Operations

The DMTF specifications are unclear regarding the inclusion of qualifiers on

CIM instances.  Some CIM Client implementations expect instances returned

The DMTF specifications are unclear regarding the inclusion of

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

qualifiers on

(such as KEY qualifiers on properties).   Pegasus today expects the provider to complete the qualifiers on instances in

CIM instances.  Some CIM Client implementations expect instances

accordance with the specification and generally the interpretation is that

returned

Pegasus applies class level qualifiers when the includeInstance parameter is

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

supplied on instance operations.  However, Pegasus today is inconsistent in

definition (such as KEY qualifiers on properties).   Pegasus

the return of qualifiers so that the user should NOT depend on Pegasus

today expects the provider to complete the qualifiers on instances in

accurately honoring the includeQualifier parameter for instance operations. 

accordance with the specification and generally the interpretation is

In the future it is expected that Pegasus will deprecate the use of qualifiers

that Pegasus applies class level qualifiers when the includeInstance

on instance operations completely.

parameter is supplied on instance operations.  However, Pegasus

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

should NOT depend on Pegasus accurately honoring the includeQualifier

parameter for instance operations.  In the future it is expected

that Pegasus will deprecate the use of qualifiers on instance

operations completely.

</li>

<li>LocalOnly option on instance

Operations - With the 1.1 version of Specification for CIM

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

GetInstance and EnumerateInstances operations was modified. This change

was incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

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

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

filter the set of set of properties returned.</li>

<li>

CIM MOF compiler function for

CIM MOF compiler function for instance aliasing - The

instance aliasing - The Pegasus MOF compiler does not today support

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

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

planned for a future version.

</li>

<li>

MultiRequest Oprations - Pegasus

MultiRequest Oprations - Pegasus does not support the DMTF defined MultiRequest

does not support the DMTF defined MultiRequest Operation option.

Operation option.

</li>

<li>

MOFCompiler namespace pragma - The

LocalOnly option on some instance Operations -

Pegasus compiler does not support the namespace pragma.

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>

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

</li>

</ol>

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

The development and release of each version of Pegasus is defined

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

and

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

controlled through Pegasus PEP documents.  PEP 180 is the

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

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:

Addition of CQL

list .5in'>

stage 1 support

Expansion of platform globalization.</li>

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

</li>

list .5in'>

Expansion of SLP support (still

Refactoring of

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

Object Normalizer function to improve performance.

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

</li>

list .5in'>

Inclusion of the Pluggable Provider   manager

Out of Process

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

Provider user level request.

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

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

</li>

list .5in'>

Inclusion of Pluggable

Embedded Object

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

support.

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

</li>

list .5in'>

Inclusion of the out-of-process

Command Line

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

Utilities

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

list .5in'>

</li>

Addition of the binary repository

option. (Experimental)</li>

CIMDateTime

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

enhancements

list .5in'>

Addition of the shared namespace

</li>

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

namespaces. (Experimental)</li>

Completion of

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

AutoPtr enhancements.

list .5in'>

</li>

Refactoring of the HTTP monitor.</li>

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

Certificate

list .5in'>

management and user-based certificate authentication

Addition of HTTP chunking.

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

</li>

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

</ol>

Completion of HTTP

chunking. Pegasus

now supports HTTP V1.1 transfer encoding otherwise known as chunking .<a

href="http://www.openpegasus.org/pp/uploads/40/5097/PEP140_ChunkedEncoding_4.3.html">

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

PEP 140</a> describes the implementation details.

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

</li>

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

statistics</li>

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

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

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

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

for operations.   The chunking code has been incorporated and the

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

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

The complete set of PEPs defined for

defined in PEP 97.

this release is defined in PEP 180.

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

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

</a></h2>

The Pegasus bugzilla database documents any defects found in Pegasus

The current bug list for Pegasus is openly available on the

and  is available through the following link:  <a

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

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

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

database</a>.

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,

<h2><a

patches, etc. for particular bugs.

name="Pegasus Release Control and Version Definition Documentation">Pegasus

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

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

The Pegasus project is controlled largely through a set of documents

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

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

modified Pegasus functionality and for the definition and documentation

of releases.

<span

Specifically the following PEPs define the characteristics of this

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

Pegasus release.

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

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>

</table>

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.

<ol>

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

<li><a

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

href="http://www.openpegasus.org/pp/protected/upreviews/20/1682/PEP209_ExternalInterface2.5.htm">PEP

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

209</a> - OpenPegaus 2.5 External Interfaces (as of this document

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

verion of PEP 230, PEP 209 is listed as draft status)

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

</li>

directory).</li>

<li><a

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

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

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

200</a> - OpenPegaus 2.5 Build and Configuration

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

Option  for Selected

2.4 functionality changes.</li>

Platforms</li>

<li>PEP 230 - Pegasus 2.5 Release Notes (This document)</li>

<li><a

href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8503">PEP

227</a> -  Pegasus 2.5 Runtime Packaging Definition

</li>

<li><a

href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8466">PEP

210</a>  - OpenPegasus 2.5 SDK Packaging Definition</li>

<li>PEP 235  - Pegasus readme.txt for 2.5 (also in the Pegasus

source

tree root directory).</li>

<li><a

href="http://www.openpegasus.org/pp/protected/revdoc.tpl?CALLER=revdocuments.tpl&grid=1411">PEP

180</a> - 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.5 functionality changes.  (as of

this document verion of PEP 230, PEP 180 is listed as draft status)</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 -h 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;">API and  usage

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

documentation - See the header files and the HTML  API

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

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

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

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

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

documentation.  In particular the Common/tests unit tests contain

documentation.  In particular the

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

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

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

Common APIs.</li>

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

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

documentation, and documentation from the Pegasus Technical Workshop

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

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

Directory, API documentation, and documentation from the Pegasus Technical

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

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

Clients - API documentation and the documentation on the Pegasus

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

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

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

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

documentation on the Pegasus Technical Workshop which is available on the

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

Pegasus web site.</li>

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

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

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

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

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

-h)</li>

OpenPegasus web site.  While these are the original design

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

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

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

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

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

the design and implementation of these features.</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>

</ul>

<o:p></o:p>

<span

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

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

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

style='color:black'>

style="color: black;">

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

width="100%"></div>

</div>

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

VERITAS Software Corporation

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

Permission is hereby granted,

Corporation

free of

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

Permission is hereby granted, free of

associated

charge, to any 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,

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

modify,

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

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

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

Software, and

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

to the

following conditions:

THE ABOVE COPYRIGHT NOTICE AND THIS

THE ABOVE COPYRIGHT

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

NOTICE AND THIS

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

PERMISSION NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL

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

PORTIONS OF

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

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

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

FOR ANY CLAIM, DAMAGES OR OTHER 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>

</body>

</html>

Legend:

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

No CVS admin address has been configured