pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.6, 2005/09/26 15:41:17

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

Line 1

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

<head>

<style>

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

</style>

Line 448

Line 449

margin:1.0in 1.25in 1.0in 1.25in;

mso-header-margin:.5in;

mso-footer-margin:.5in;

mso-paper-source:0;}

div.Section1

{page:Section1;}

Line 569

Line 571

text-indent:-.25in;}

@list l4:level7

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

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level8

Line 887

Line 890

text-indent:-.25in;}

@list l19

{mso-list-id:1902863286;

mso-list-template-ids:740079056;}

@list l19:level1

{mso-level-number-format:bullet;

Line 959

Line 963

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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" name="City"></o:smarttagtype>

<o:smarttagtype

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

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

<o:smarttagtype

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

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

<o:DocumentProperties>

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

<o:LastAuthor> </o:LastAuthor>

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

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

Pegasus

width="100%"></div>

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

align="center">Pegasus

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

<span

style="color: black;">

PEP #: 230

PEP #: 249

Title: Release

Notes for OpenPegasus 2.5

Notes for OpenPegasus 2.5.1

Version: 1.8

Version: 1.0

Created: <st1:date

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

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

Authors: Karl Schopmeyer

Authors: Warren

Grunbok, Karl Schopmeyer

Status:  draft

Version History:

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

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

<tbody>

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

<o:p> </o:p>

<span

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

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

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

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

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

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

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

</td>

</tr>

<o:p> </o:p>

<span

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

</td>

<span

<o:p> </o:p>

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

2005

</o:p>

</td>

<span

<o:p> </o:p>

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

</o:p>

</td>

<span

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

Submission<o:p>

</o:p>

</td>

</tr>

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

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

</td>

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

</td>

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

</td>

</tr>

<tr>

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

</td>

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

</td>

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

</td>

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

security notes.

</td>

</tr>

<tr>

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

</td>

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

</td>

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

</td>

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

</td>

</tr>

<tr>

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

</td>

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

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

<o:p>  1 March

2006</o:p>

</td>

Karl Schopmeyer

</td>

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

version  (balloted version)

Initial

Submission<o:p>

</o:p>

</td>

</tr>

<tr>

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

</td>

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

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

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

</td>

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

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

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

</td>

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

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

Review week of 12 March 2006</td>

</td>

</tr>

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

<tr>

Provider security statement, and clarified Solaris support for 2.5

</td>

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

2006</td>

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

Schopmeyer</td>

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

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

</tr>

<tr>

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

2006</td>

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

Schopmeyer</td>

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

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

</tr>

<tr>

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

2006</td>

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

Schopmeyer</td>

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

status "experimental" for certain features</td>

</tr>

<tr>

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

</td>

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

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

2006</td>

</td>

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

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

Schopmeyer</td>

</td>

<td style="padding: 0.75pt;">Typos</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

style="color: black;">

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

Abstract: This document defines the release notes for the 2.5.1

width="100%"></div>

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

Abstract: This document defines the release notes for the 2.5

version of the Pegasus CIM Server. <span

style="font-size: 9pt;"><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

style="color: black;">

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

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

width="100%"></div>

</o:p></h2>

<o:p> Contents

</o:p>

<ol>

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

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

this Release</a></li>

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

This Release</a></li>

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

Line 1184

Line 1125

in This Release</a></li>

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

Bugs</a></li>

<li> <a

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

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

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

site at <a

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

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

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

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

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

also available that can be used to build binaries for most

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

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

subsequent snapshots that are made available in the Pegasus CVS are

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

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

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

CVS page</a> for information) using the tags defined on the <a href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release

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 <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus

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

WEB site</a>.

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

Pegasus source

tree.

tree.</div>

Instructions for building the Linux RPMs: <span

<h2>Functionality of This Release</h2>

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

Pegasus overall status by release is defined by  a

</>

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

<ol>

that is available on the OpenPegasus web site .  That

<li>Download

web page shows the Pegasus users and developers

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

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

<li>rpm

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

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

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

<li>

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

<span

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

class="norm">Build

are conditionally compiled with special environment variables.

the rpms:

</li>

</ol>

<table

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

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

All functions are considered community tested and operational unless

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

not generally of the quality or completeness for production

usage.  Interfaces that are part of the Pegasus public

interface definitions but that the Pegasus team feels may change are

marked experimental. In many cases these features  and interfaces

are conditionally compiled with special environment variables. <a

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

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.

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

please access the

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

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

of the features listed below are production ready.

<h3>CIM Server Functionality</h3>

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

<ol>

<li>Class Operations (getClass, <span

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

class="SpellE">deleteClass, modifyClass,

enumerateClass, enumerateClassNames)</li>

<li>Qualifier Operations (getQualifier, setQualifier,

deleteQualifier) </li>

<li>Instance Operations (getInstance, <span

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

class="SpellE">deleteInstance, modifyInstance,

enumerateInstance, enumerateInstanceNames, getProperty,

enumerateInstance, <span

class="SpellE">enumerateInstanceNames, getProperty,

setProperty)</li>

<li>Association Operations (references, referencenames,

associators, associatornames)</li>

Line 1364

Line 1190

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

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

considered at alpha quality because it has only been contributor

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

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

today does not support the ExecuteQuery operation defined as the Query

operation for CQL.

</li>

</ol>

</blockquote>

</div>

<h4>Indications</h4>

<h4>Indication Processing</h4>

<ul>

<ol>

<li>Process indications - Process indications are operational in

the

Server.  This includes support

Line 1385

Line 1213

enablement for the generation of lifecycle indications. For more

details, refer to

</ul>

</ol>

<h4>Indication Listener</h4>

<h4>Query Language</h4>

The generic components for a CIM Listener and a

Pegasus includes the  WQL  query language which is implemented and

listener API are operational.  This includes the functions for

used for filters and in version 2.4 for execQuery.

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

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

as an indication listener in the Pegasus server.

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

Pegasus 2.5

combine to describe the CQL  functionality supported.

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 droped instances it considered bad, and 2) the Object

Normalizer code slows performance. These issues are now addressed by

Normalizer code slowed performance. These issues are now addressed by

moving the Object Normalizer from the Dispatcher to the Response

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

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

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

CIMOM/provider boundary.

Two new configuration properties were added to control object

<h4>Embedded Object Support</h4>

normalization.

Pegasus 2.5 provides embedded object support. The proposed solution

<ol>

is restricted to the following:<ul>

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

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

normalization for provider objects.</li>

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

<li>excludeModulesFromNormalization (colon delimited list of

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

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.

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

</li>

</ul>

<h3>Pegasus Repositories

</h3>

</blockquote>

<h4>Query Language</h4>

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

used for filters and in 2.4 for execQuery.

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

193, 205 combine to describe the function submitted.

<h4>Schema Repository</h4>

By default, Pegasus uses an XML-based

By default, Pegasus uses an XML-based

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

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

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

To use the binary encoding feature a new configuration

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

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

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

bugzilla 3642 for details.) <span

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

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

readme.binaryrepository file in the Pegasus source root directory.

</div>

<h4>Instance Repository</h4>

<h4>Compressed Repository</h4>

The

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

Pegasus schema repository may also be configured to hold instance

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

data.  Although instances may be place in the

repository

it was not designed as a

high volume data store.

<h4>Compressed Repository Feature</h4>

A compressed repository

feature has been added for

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

the

Line 1510

Line 1278

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

(readme.compressed_repository). Note

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

activated for

automatic tests.

automatic tests.Further information on the use of the compressed

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

</div>

root directory.

<h4>Pegasus MOF Compilers</h4>

<h4>Instance Repository</h4>

Pegasus implements a MOF compiler that can operate either at the

The

client

Pegasus schema repository may also be configured to hold instance

interface to the Pegasus CIM Server (cimmof)

data.  <font

or directly interfacing with a CIM

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

repository (cimmofl).

repository

The direct interface compiler is used primarily to provide an

it was not designed as a

initial

high volume data store.

class/instance repository. WARNING:

The use of cimmofl

to manipulate instances in the repository bypasses any provider that is

registered to serve these  instances and simply installs the

instances in the

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

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

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

available until the server is stopped and restarted in some

cases.  Use of cimmofl in general is

discouraged and particularly  to manipulate

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

<h4>Security Considerations

<h3>Security Considerations</h3>

</h4>

OpenPegasus 2.5 (and

prior) contains several mechanisms to perform authorization, but none

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

of these authorization checks are performed by default.

By registering any provider which fails to do appropriate authorization

checks, the consequences may include information leakage, data

corruption, or unintended elevation of privilege. Please ensure that

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

your systems and data:

your systems and data:

1. Only install/register providers which perform authorization

1. Only install/register providers which perform authorization

appropriate for your environment.

appropriate for your environment.

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

<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

Line 1560

Line 1333

3. Namespace authorization is also available.

For administration issues please refer to

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

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

<h4>Server Security</h4>

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

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

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

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

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

implemented in Pegasus using the OpenSSL

libraries. Pegasus does not provide the OpenSSL

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

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

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

with multiple versions of  OpenSSL versions

is  0.9.6c .   This release of Pegasus was tested with

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

0.9.6k.  See <a

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

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

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

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

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

SSLv3

and TLSv1 by default. SSLv2 is

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

See<a

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

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

PEP 237</a> for details on

PEP 200</a> for details on

configuration.

</li>

</ol>

<h4>Client Security<span

<h4>Client Security</h4>

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

Certificate management

Certificate management 

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

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

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

client verification support by providing a robust solution to managing

client certificates and certificate revocation lists via standard CIM

operations. It allows certificates to be associated with particular

Line 1600

Line 1368

and are the responsibility of the client to implement on their

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

more details on client security.

Note: <span

Note: WBEM clients are responsible for SSL

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

certificate verification using Pegasus and/or SSL libraries as

appropriate. Consequences of not doing so include leakage of

authentication credentials to unauthorized parties.

Line 1609

Line 1376

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

the defined configuration parameters (cimconfig) and server command

line options.<font

line options.  NOTE: When installed

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

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

enableAuthentication to true can result in improper operation of the

SLP

Line 1621

Line 1387

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.

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

</o:p></li>

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

capture using the <font

capture using the CIM_StatisticalData classes in

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

the DMTF Interop model. This

function is considered alpha quality and conditionally compiled.

</li>

Line 1636

Line 1400

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

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

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

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

<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

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

(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

the CMPI provider interface - See PEP 130 for more

information on use of this feature</li>

information on use of this feature.</li>

</ol>

<h4>SLP Discovery</h4>

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

a platform basis. <a

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

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

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

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

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

enable or disable this code.  PEGASUS_DISABLE_SLP and

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

PEGASUS_ENABLE_SLP are the environment variables that control inclusion

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

of this feature.  Once compiled, SLP

environment variable (PEGASUS_HAS_OPENSLP)  Once compiled, SLP

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

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

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

internal agent or OpenSLP)  and

generates SLP advertisements compatible with the DMTF slp template

specification. The SLP support also includes  extensions to the

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

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

public SDK).

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

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

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

<h4>Indication Handlers</h4>

<h5>System Log Indication Handler

</h5>

The SysLog Indication Handler is a new

for 2.5

type of Indication Handler which allows CIM Indications to be delivered

to the system syslog file. It has following features:

<h4>Provider Managers</h4>

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

an entry made by Syslog Indication Handler.

If a subscriber includes PerceivedSeverity property in the SELECT

list of the filter condition for the indication, the PerceivedSeverity

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

severity 'LOG_INFO' is used.

See

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

206</a> for details.

<h5>Email Indication Handler

</h5>

The Email Indication Handler is a new

for 2.5

type of Indication Handler that allows CIM Indications to be delivered

to a specified e-mail address.   See

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

207</a>  for details.

</blockquote>

<h4>Pegasus Provider Interfaces</h4>

Pegasus is designed to support multiple Provider Managers to allow

multiple provider interfaces to the CIMOM.  The two default

provider managers are the Pegasus C++ Interface and Common

Manageability Programming Interface (CMPI) Interface.

Manageability Programming Interface (CMPI) Interface.

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

This is the original

interface defined for OpenPegasus Providers.  It provides an interface

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

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

CIMOM (CIMOMHandle).

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

Pegasus 2.5 includes

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

Line 1683

Line 1476

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

standardized C level interface for creating providers that can be

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

current C++ providers.  <span

current C++ providers.  The

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

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

Pegasus 2.5.

Pegasus 2.5.1.

Information on writing providers with the CMPI interface is available

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

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

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

Pegasus source root directory.

Pegasus source root directory.

NOTE: See the Feature status page

for exact status of the CMPI provider manager for different Pegasus

platforms.

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

Pegasus includes an experimental provider manager for Java

Pegasus

includes a provider manager for Java

provider interfaces based on the SNIA provider interface

definitions.  This provider manager is  considered alpha

quality and is not compiled in the default build.   See

Line 1723

Line 1520

src/pegasus/controlproviders and include support for the following

classes:

<ul>

<li>DMTF Interop classes including __Namespace,  <span

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

class="SpellE">CIM_Namespace, CIM_ObjectManager,

CIM_CommunicationMechanism, and

CIMOMStatistics.</li>

</ul>

<h4>CMPI Remote</h4>

<h4>CMPI Remote Providers</h4>

Pegasus includes an support for

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.

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

Generic Providers</h3>

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

<h4>Generic Providers</h4>

Generic OperatingSystem provider. See

the

directory src/Providers/generic.

<h4>Test/Sample Providers</h4>

See the directories src/Providers/TestProviders

and src/Providers/Sample for more

and src/Providers/sample for more

information about test and

sample providers.

<h4>Managed System Providers</h4>

Line 1754

Line 1547

more information on these providers see the documentation for each

provider in

the directory src/Providers/ManagedSystem

<h4>Server Statistics

<h4>Server Statistics Provider

</h4>

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

are implemented in this release. The statistics gathering is disabled

are implemented in this release. The statistics gathering is compiled

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

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

ModifyInstance operation on the singleton 'CIM_ObjectManager' instance

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

ModifyInstance operation on the 'CIM_ObjectManager instance

in the 'PG_InterOp' namespace to set the GatherStatisticalData property

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

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

from the Pegasus CVS repository.

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

<h4>

</h4>

<h4>SLP Provider</h4>

This provider acts as the definer of

SLP information for SLP registration and also controls the Pegasus SLP

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

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

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

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

</blockquote>

<h2>Pegasus Indication Listeners</h2>

The generic components for a CIM Listener and a

listener API are operational.  This includes the functions for

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

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

as an indication listener in the Pegasus server.

Pegasus includes 3 separate Indication Listeners.

<h3>Embedded CIMListener</h3>

This listener is embedded in the CIMServer and allows the

server to accept indications and route them.

<h3>Standalone Static CIMListener</h3>

This is a standalone listener that combines the functions

of listener and consumer into a single element.

<h3>Standalone Dynamic Listener</h3>

Pegasus 2.5

includes a new standalone dynamic listener that is separate

from the current standalone CIMListener and the ExportServer listener

in the CIM server.

The use model that this listener fits is the following:

<ul>

<li> The listener may be packaged as

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

another application. </li>

<li> Consumers

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

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

</ul>

This

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

is essentially a lightweight, pluggable listener that

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

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

bypasses traditional registration procedures.  See

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

details.

</blockquote>

<h3>CIM_Schema</h3>

The default CIM_Schema loaded with this

release is

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

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

a number of

local classes defined for Pegasus.  These are defined in the

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

pegasus/Schemas

directory.   There are also a

number of older schema available in the CVS.

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

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

with these Schemas.

The mechanism to install other schemas than the default is defined

in the mak/config.mak

NOTE: The CIM 2.5 schema is

Line 1792

Line 1624

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

test

environment.

<h3>Pegasus MOF Compilers</h3>

</blockquote>

Pegasus implements a MOF compiler that can operate either at the

client

interface to the Pegasus CIM Server (cimmof)

or directly interfacing with a CIM

repository (cimmofl).

The direct interface compiler is used primarily to provide an

initial

class/instance repository. WARNING:

the use of cimmofl

to manipulate instances in the repository bypasses any provider that is

registered to serve these  instances and simply installs the

instances in the

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

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

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

available until the server is stopped and restarted in some

cases.  Use of cimmofl in general is

discouraged and particularly  to manipulate

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

<h3>Client Tools</h3>

Lightweight statistics are now implemented for

the

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

client,

and the

elapsed time spent on the network between client and server.

<h3>Pegasus CIM Server Administration</h3>

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

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

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

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

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

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

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

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

- Manage the CIM Server authorization characteristics. Today this is

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

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

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

- Manage information about the providers .</li>

</ol>

Line 1853

Line 1656

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

- output classes and/or instance information from the Pegasus

- output classes and/or instance information from the Pegasus

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

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

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

- Generate a set of standard information on the Domain

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

information generated is dependent on the information available from

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

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

<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

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

Line 1887

Line 1690

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

benchmark test environment is provided which includes both a client and

provider component. See src/clients/benchmarkTest

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

for more information.</li>

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

the

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

client,

and the

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

</ol>

<h3>Pegasus Interface APIs</h3>

Details of the Pegasus public interfaces for this release are listed

in PEP 209

available from the web site(<a

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="http://www.openpegasus.org/pp/uploads/40/Administrator/My%20Documents/processes/www.openpegasus.org">www.openpegasus.org</a>).

That document is the authorative source for the list

That document is the authorative source

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

for the list of publicly supported Pegasus APIs.   The Client

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

and Provider API were originally frozen at the Pegasus version 2.1

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

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

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

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

compatible with this release without compilation.  There have been

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

extensions and new interfaces added for this release.

release without compilation.  There have been extensions and new

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

  The Pegasus public

interfaces includes the following major functions

Line 1913

Line 1720

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

in the public SDK including:

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

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

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

<li class="MsoNormal">CIM Listener

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

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

running or a physical separation between the indication listener and

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

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

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

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

<li>New CIM Listener now provides selective

indication delivery.

indication delivery.

</li>

<li>New CIM Listener

<li>New CIM Listener

keeps all consumer libraries in memory for the duration of its

execution.

execution.

</li>

<li>New CIM Listener

<li>New CIM Listener

is now pluggable.

is now pluggable.</li>

</li>

<li>New CIM Listener

<li>New CIM Listener

now provides reliable indication delivery.</li>

now provides reliable indication delivery.</li>

</ul>

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

Line 1952

Line 1756

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

the

OpenPegasus web site.

<o:p></o:p>

<h3>WMI Mapper</h3>

WMI Mapper

The WBEM to WMI Mapper provides a way

to access

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

Line 1968

Line 1772

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

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

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

account with

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

this, the

Line 1981

Line 1784

MUST

contain user credentials.

<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

<h2>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 The following table defines the level of the DMTF specifications

specifications which which Pegasus conforms today.

to which this version of Pegasus conforms today.

<tbody>

<tr>

Line 2072

Line 1843

Pegasus release are:

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

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

<tbody>

<td

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

height="26" width="211">

Platform and

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

</td>

<td

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

height="26" width="289">

Compilers<span

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

</td>

</tr>

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

width="211">

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

</td>

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

width="289">

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

HP <span

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

</td>

</tr>

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

width="211">

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

<span

</td>

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

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

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

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

<span

</td>

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

</td>

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

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

</td>

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

width="289">

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

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

gcc

<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

Visual C++ Ver 6 and Microsoft .Net compiler Version.   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"

width="211">

Windows XP<o:p>, Windows

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

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

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

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

</td>

</tr>

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

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

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

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

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

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

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

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

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

</td>

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

</tr>

<tr>

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

</big></td>

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

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

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

</td>

</tr>

<tr>

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

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

color="RED">Solaris 8

</big></td>

* See below for additional info

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

</big></td>

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

</td>

</tr>

</tbody>

</table>

Solaris:  Solaris testing

Platform patches

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

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

RHAS

2.1 needs the update to fix Red Hat Bugzilla 98815.

</div>

</div>

Further information regarding Pegasus support on IBM platforms can

found at: <a

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

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:

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

<o:p>

</o:p>

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

DMTF Specifications</a></h2>

It is a major goal

Line 2248

Line 1983

indications but does not

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

<li>

<font

IncludeQualifiers

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

option on Instance Operations

The DMTF specifications are unclear regarding the inclusion of

Line 2295

Line 2029

The development and release of each version of Pegasus is defined

and

controlled through Pegasus PEP documents.  PEP 180 is the

controlling document

controlling document  for Pegasus 2.5.0 and PEP 239 is the controlling

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

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

status of

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

functionality was completed for this release.

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

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

Addition of CQL

Line 2341

Line 2075

</li>

Completion of HTTP

chunking. Pegasus

chunking. Pegasus

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

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

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

PEP 140</a> describes the implementation details.

PEP 140</a> describes the implementation details.

</li>

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

statistics</li>

Line 2352

Line 2085

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

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

</ol>

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

more details):.

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

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

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

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

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

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

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

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

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

value representes the state.</li>

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

strings (bug 4624).</li>

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

the Pegasus internal SA.</li>

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

options.</li>

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

</ol>

Specifically the status of several components of Pegasus functionality were

moved in status on the Feature Status Page as follows:

<ol>

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

<li>Out of Process providers</li>

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

</ol>

The complete set of PEPs defined for

The complete set of changes defined for this release

this release is defined in PEP 180.

is defined in PEP 239

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

</a></h2>

The Pegasus bugzilla database documents any defects found in Pegasus

and  is available through the following link:  <a

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

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

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

database</a>.

with the keyword 2.5.1_APPROVED so that

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

Note that since this was a minor release all of the fixes were documented as

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

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

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

<h2><a

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

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

The Pegasus project is controlled largely through a set of documents

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

Line 2373

Line 2138

Specifically the following PEPs define the characteristics of this

Pegasus release.

<ol>

<li><a

<li>

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

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

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

</li>

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

<li>

</li>

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

<li><a

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

200</a> - OpenPegaus 2.5 Build and Configuration

Option  for Selected

Platforms</li>

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

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

<li><a

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

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

<li>

227</a> -  Pegasus 2.5 Runtime Packaging Definition

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

</li>

<li><a

<li>

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

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

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

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

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

and also in the Pegasus

source

tree root directory).</li>

<li><a

<li>

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

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

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

Line 2433

Line 2194

the design and implementation of these features.</li>

</ul>

<span

<o:p></o:p>

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

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

style="color: black;">

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

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

width="100%"></div>

Group; VERITAS Software Corporation; Intel Corp.

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

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

VERITAS Software Corporation

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

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

Permission is hereby granted,

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

free of

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

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

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

associated

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

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE

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

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

modify,

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

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

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

Software, and

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

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

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

to the

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

following conditions:

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

SOFTWARE.</div>

THE ABOVE COPYRIGHT

NOTICE AND THIS

PERMISSION NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL

PORTIONS OF

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

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

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>

</body></html>

Legend:

Removed from v.1.6
changed lines
	Added in v.1.6.12.1

No CVS admin address has been configured