pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.8 and 1.10.2.1

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

version 1.10.2.1, 2007/10/05 18:19:26

Line 448

margin:1.0in 1.25in 1.0in 1.25in;

mso-header-margin:.5in;

mso-footer-margin:.5in;

mso-paper-source:0;}

div.Section1

{page:Section1;}

Line 569

Line 570

text-indent:-.25in;}

@list l4:level7

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

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level8

Line 887

Line 889

text-indent:-.25in;}

@list l19

{mso-list-id:1902863286;

mso-list-template-ids:740079056;}

@list l19:level1

{mso-level-number-format:bullet;

Line 994

Line 997

</w:WordDocument>

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

</head>

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

style="color: black;">

Line 1006

Line 1009

<span

style="color: black;">

PEP #: 230

PEP #: 305

Title: Release

Notes for OpenPegasus 2.5

Notes for OpenPegasus 2.6.1

Version: 1.8

Created: <st1:date

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

year="2004" day="23" month="3">3 August 2007

Authors: Warren

</st1:date>

Grunbok, Karl Schopmeyer

Authors: Dave

Sudlik

Status:  draft

Status:  approved

Version History:

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

<table class="MsoNormalTable" style="width: 868px; height: 54px;"

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

border="1" cellpadding="0" cellspacing="1">

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

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

height="27">

<span

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

style="font-family: Arial; color: black;"><o:p>Version </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;">

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

height="27">

<span

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

style="font-family: Arial; color: black;"><o:p>Date </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;">

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

height="27">

<span

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

style="font-family: Arial; color: black;"><o:p> Author</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;">

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

height="27">

<span

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

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

</o:p>

</td>

</tr>

<span

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

</td>

<span

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

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

2005

August 2007

</o:p>

</td>

<span

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

style="font-family: Arial;">Dave Sudlik

</o:p>

</td>

<span

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

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

Submission<o:p>

Submission. Updates for 2.6.1 (from 2.6) are highlighted <span

</o:p>

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

</td>

this color. <o:p><font

</tr>

size="2"> </o:p>

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

</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 style="vertical-align: top; text-align: center;">1.1

</td>

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

<td style="vertical-align: top; text-align: center;">8 August 2007

</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 style="vertical-align: top; text-align: center;">Dave Sudlik

</td>

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

<td style="vertical-align: top;">Updates from review <span

</td>

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

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

Line 1157

Line 1094

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

Abstract: This document defines the release notes for the

version of the Pegasus CIM Server. <span

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

simply to summarize the characteristics of this release, point to other

documentation that defines the release in more detail, and provide

additional information about this release that is not available in the

other Pegasus documentation. <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">

Line 1167

Line 1108

style="color: black;">

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

width="100%"></div>

<o:p> Contents

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

</o:p>

</o:p></h2>

<ol>

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

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

this Release</a></li>

Release</a></li>

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

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

This Release</a></li>

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

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

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

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

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

Platforms</a></li>

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

with DMTF Specifications</a></li>

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

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

in This Release</a></li>

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

Bugs</a></li>

<li> <a

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

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

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

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

Documentation</a></li>

</ol>

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

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

These can be

downloaded from the OpenPegasus Web

site at <a

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

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

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

<li>OpenPegasus  binary and source RPMs on the

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

OpenPegasus web site.. The source RPM is  available on the

also available that can be used to build binaries for most

OpenPegasus web site that can be used to build binaries for most

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

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

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

release and

subsequent snapshots that are made available in the Pegasus CVS are

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

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

Line 1211

Line 1149

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

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

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

<h2>OpenPegasus Functionality for This

</>

Release</h2>

<ol>

Pegasus overall status by release is defined by  a <a

<li>Download

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

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

Page</a> that is available on the OpenPegasus web site .  That web

<li>rpm

page shows the Pegasus users and developers the status of the various

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

features found in Pegasus using a simple color coded key (white, red,

<li>

yellow, green) and a description of each feature.

<span

Pegasus 2.6.1 is a "point"

class="norm">Build

release, extending Pegasus 2.6 in

the rpms:

selected areas. Normally an OpenPegasus "point" release does not

</li>

contain major new pieces of functionality, but in this case one new PEP

</ol>

was added for IPv6 support, the description of which has been added to

these Release Notes.

<table

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

The major areas of development for this release  were as

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

follows. For more information access the documented PEP:

<tbody>

<tr>

Table of Major Changes for this Release

<td

<table style="font-family: Arial;" bordercolordark="#666666"

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

bordercolorlight="#cccccc" border="1" cellspacing="1">

<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

<th bgcolor="#e0e8ef">Description</th>

</td>

<th bgcolor="#e0e8ef">Posted PEP

<td

Version</th>

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

</tr>

of RPMs after the build is complete

</td>

</tr>

<td style="color: rgb(153, 51, 153);" align="left">OpenPegasus

<tr>

Support for IPv6: Stage 1

<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

<td style="color: rgb(0, 153, 0);"> <a

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

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

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>

The status of several components of Pegasus functionality change

</ol>

status between Pegasus versions. <a

name="comtag_116">Features that have changed status can be identified

by a change in color from the previous release to this release</a>

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

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

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

Status WEB Page</a>.

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

Finally, a significant number of internal changes and corrections

This document shows the Pegasus users and developers the maturity of

were made under the control of the Pegasus bugzilla bug system. See the

the various features found in Pegasus using a simple color coded

bug section below for more information.

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.

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

<ol>

<li>Class Operations (getClass, <span

class="SpellE">deleteClass, modifyClass,

enumerateClass, enumerateClassNames)</li>

<li>Qualifier Operations (getQualifier, setQualifier,

deleteQualifier) </li>

<li>Instance Operations (getInstance, <span

class="SpellE">deleteInstance, modifyInstance,

enumerateInstance, <span

class="SpellE">enumerateInstanceNames, getProperty,

setProperty)</li>

<li>Association Operations (references, referencenames,

associators, associatornames)</li>

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

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

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

considered at alpha quality because it has only been contributor

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

</li>

</ol>

</blockquote>

</div>

<h4>Indications</h4>

<ul>

<li>Process indications - Process indications are operational in

the

Server.  This includes support

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

for

indications and the CIMXML indication handler.</li>

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

lifecycle indications (ie. those

classes of indications derived from CIM_ClassIndication and

CIM_InstIndication) can now be created. Pegasus 2.5 provides some

enablement for the generation of lifecycle indications. For more

details, refer to

</ul>

<h4>Indication Listener</h4>

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.

<h3 style="color: rgb(153, 51, 153);">IPv6 Support

Pegasus 2.5

</h3>

includes a new standalone listener that is separate

IPv6 is short for "Internet

from the current standalone CIMListener and the ExportServer listener

Protocol

in the CIM server.

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

The use model that this listener fits is the following:

to replace the current version Internet Protocol, IP Version 4

<ul>

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

<li> The listener may be packaged as

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

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

291</a>.

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

used for filters and in 2.4 for execQuery.

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

The IPv6 support in OpenPegasus is

193, 205 combine to describe the function submitted.

controlled by the PEGASUS_ENABLE_IPV6 build variable. Setting this to

'true' before building OpenPegasus will enable the IPv6 support. In

2.6.1 this variable will default to 'false' to omit the IPv6 support.

<h4>Schema Repository</h4>

The following subsections provide

By default, Pegasus uses an XML-based

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

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

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

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

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

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

To use the binary encoding feature a new configuration

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

properties was

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

added:

Listener components. For more information on IPv6 support for your

enableBinaryRepository (true|false) - Enables

specific platform, refer to the documentation for that platform.

disables binary repository.

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

All OpenPegasus externals that

repository, the compressed repository

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

functionality has

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

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

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

support

address must be specified without brackets. For example, the

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

OpenPegasus osinfo client (which returns information about the OS

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

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

compression enabled records are always written compressed but both

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

compressed

specified as:

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 schema repository may also be configured to hold instance

data.  <font

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

repository

it was not designed as a

high volume data store.

<h4>Security Considerations

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

</h4>

3ffe:1:2:1 -p 5988

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

But the cimcli command, which

access to Pegasus to a specific authorized user group of trusted

takes

individuals.

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

3. Namespace authorization is also available.

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

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

(Note that Digest based security is not implemented)</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

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

is  0.9.6c .   This release of Pegasus was tested with

0.9.6k.  See <a

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

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

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

SSLv3

and TLSv1 by default. SSLv2 is

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

See<a

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

PEP 200</a> for details on

configuration.

</li>

</ol>

<h4>Client Security<span

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

Certificate management 

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

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

client verification support by providing a robust solution to managing

client certificates and certificate revocation lists via standard CIM

operations. It allows certificates to be associated with particular

system users for enhanced authorization capabilities.

CN/ Host

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

and are the responsibility of the client to implement on their

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

more details on client security.

Note: <span

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.

<h4>Platform Management Functions</h4>

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

the defined configuration parameters (cimconfig) and server command

line options.<font

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

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

Administrator should change the user that the service runs under from

the Local

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

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

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

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

with the exception of HP OpenVMS.

</o:p></li>

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

capture using the <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

a platform basis. <a

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

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

enable or disable this code.  PEGASUS_DISABLE_SLP and

PEGASUS_ENABLE_SLP are the environment variables that control inclusion

of this feature.  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

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>

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

Pegasus is designed to support multiple Provider Managers to allow

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

multiple provider interfaces to the CIMOM.  The two default

or

provider managers are the Pegasus C++ Interface and Common

Manageability Programming Interface (CMPI) Interface.

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

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

[3ffe:1:2:1]:5989

Pegasus 2.5 includes

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

result of a project by the IBM SBLIM team (see 

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

Manageability Programming Interface, which is an OpenGroup standard.

The CMPI

specification is available at:

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

standardized C level interface for creating providers that can be

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

current C++ providers.  <span

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

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

Pegasus 2.5.

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.

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

Pegasus includes an experimental provider manager for Java

provider interfaces based on the SNIA provider interface

definitions.  This provider manager is  considered alpha

quality and is not compiled in the default build.   See

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

</blockquote>

<h3>    Providers</h3>

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

to run out of process at

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

process space.

Administrators should check the providers to

ensure that the provider vendor

has made use of available authorization capability.

</div>

There are a number of providers available

in the Pegasus release.

For more information on

This includes providers in the following categories:

specifying

IPv6 addresses, refer to <a style="color: rgb(153, 51, 153);"

<h4>Pegasus Internal Providers</h4>

href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP Version

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

6 Addressing Architecture</a>

access to the CIMOM for information and provide information and

and <a style="color: rgb(153, 51, 153);"

services to support the CIMOM and its administration.    The

href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 - Format for

providers in this category are mostly defined in the directory

Literal IPv6 Addresses in URL's</a><span

src/pegasus/controlproviders and include support for the following

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

classes:

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

<ul>

<h4 style="color: rgb(153, 51, 153);">IPv6 on Linux

<li>DMTF Interop classes including __Namespace,  <span

</h4>

class="SpellE">CIM_Namespace, CIM_ObjectManager,

Modern Linux distributions already

CIM_CommunicationMechanism, and

contain IPv6-ready kernels, the

CIMOMStatistics.</li>

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

</ul>

that this module is not loaded automatically on startup.

<h4>CMPI Remote</h4>

Note:

you shouldn't anymore use kernel series 2.2.x, because it's not

Pegasus includes an experimental support for

IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no

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

longer improved according to definitions in latest RFCs. It's recommend

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

to use series 2.6.x now.

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

the

directory src/Providers/generic.

<h4>Test/Sample Providers</h4>

See the directories src/Providers/TestProviders

and src/Providers/Sample for more

information about test and

sample providers.

<h4>Managed System Providers</h4>

ComputerSystem, DNSAdmin,

DNSService, Operating System, Process,

Processor. For

more information on these providers see the documentation for each

provider in

the directory src/Providers/ManagedSystem

<h4>Server Statistics

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

SLP information for SLP registration and also controls the Pegasus SLP

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

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

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

</blockquote>

<h3>CIM_Schema</h3>

The default CIM_Schema loaded with this

release is

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

a number of

local classes defined for Pegasus.  These are defined in the

pegasus/Schemas

directory.   There are also a

number of older schema available in the CVS.

The mechanism to install other schemas than the default is defined

in the mak/config.mak

NOTE: The CIM 2.5 schema is

maintained in the

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

test

environment.

<h3>Pegasus MOF Compilers</h3>

Pegasus implements a MOF compiler that can operate either at the

client

interface to the Pegasus CIM Server (cimmof)

or directly interfacing with a CIM

repository (cimmofl).

The direct interface compiler is used primarily to provide an

initial

class/instance repository. WARNING:

the use of cimmofl

to manipulate instances in the repository bypasses any provider that is

registered to serve these  instances and simply installs the

instances in the

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

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

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

available until the server is stopped and restarted in some

cases.  Use of cimmofl in general is

discouraged and particularly  to manipulate

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

<h3>Client Tools</h3>

To check whether your current

Lightweight statistics are now implemented for

running

the

kernel supports IPv6, take a look into your /proc filesystem. The entry

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

/proc/net/if_inet6 must exist. A short automated test looks like:

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

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

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

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

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

- Manage the CIM Server authorization characteristics. Today this is

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

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

- Manage information about the providers .</li>

</ol>

Server admin

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

- output classes and/or instance information from the Pegasus

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

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

- Generate a set of standard information on the Domain

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

information generated is dependent on the information available from

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

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

- Generates a set of standard information from the Network

Schema.  Information generated varies by system because of the

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

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

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

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

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

</ol>

<h3>Test support Tools</h3>

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

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

tests are defined throughout the Pegasus source tree typically in

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

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

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

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

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

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

- Test tool that sends/receives XML from XML input.<o:p></o:p></li>

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

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

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

benchmark test environment is provided which includes both a client and

provider component. See src/clients/benchmarkTest

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

</ol>

<h3>Pegasus Interface APIs</h3>

Details of the Pegasus public interfaces for this release are listed

in PEP 209

available from the web site(<a

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

That document is the authorative source

for the list of publicly supported Pegasus APIs.   The Client

and Provider API were originally frozen at the Pegasus version 2.1

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

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

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

release without compilation.  There have been extensions and new

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

  The Pegasus public

interfaces includes the following major functions

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

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

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

function APIs</li>

</ol>

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

in the public SDK including:

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

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

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>

The APIs are

documented in

their respective header files and  in HTML documentation based on

the information

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>

The WBEM to WMI Mapper provides a way

to access

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

requests

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

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

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

XML

message and extracts from the HTTP message header the user credentials

provided

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

authenticates these credentials, verifying if the provided credentials

have

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

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

account with

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

this, the

WMI Mapper impersonates the user

credentials provided

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

browse WMI

data. Hence, ALL requests made to the WMI Mapper

MUST

contain user credentials.

<h3>Indication Handlers</h3>

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

System Log Indication Handler

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

<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

For more information on

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

enabling

</ul>

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

<ul>

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

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

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

list of the filter condition for the indication, the PerceivedSeverity

Documentation Project's IPv6 HOWTO</a><span

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

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

severity 'LOG_INFO' is used.</li>

<li>See <a

Warning:

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

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

206</a> for details.

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

</li>

described in <a style="color: rgb(153, 51, 153);"

</ul>

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

bug 6586</a> and <a

Email Indicaiton Handler

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

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

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

for 2.5

bug 248052</a>, and manifests

type of Indication Handler that allows CIM Indications to be delivered

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

to a specified e-mail address.   See <a

OpenPegasus with IPv6 enabled may be

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

significantly impacted in these environments.<br

207</a>  for details.

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

<h4 style="color: rgb(153, 51, 153);">IPv6 on Windows</h4>

Microsoft provides supported IPv6

implementations for Windows Server

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

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

On Windows XP, you can use the <span

style="font-weight: bold; color: rgb(153, 51, 153);">ipv6.exe<span

style="color: rgb(153, 51, 153);"> tool to install, uninstall, and

query

your IPv6 configuration. For example:<br

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

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

ipv6 if

</div>

Windows Vista

and Windows Server 2008 support an integrated

IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack.

Note that the OpenPegasus IPv6 support in 2.6.1 has not yet been tested

on Windows Vista or Windows Server 2008.<br

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

For more information on

installing, configuring, and using IPv6 on Windows platforms, refer to

the document <a style="color: rgb(153, 51, 153);"

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

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

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

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

<h4 style="color: rgb(153, 51, 153);">Testing your OpenPegasus IPv6

support</h4>

As part of the OpenPegasus

automated tests, the TestClient, g11ntest, and IndicationStressTest

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

(::1) if PEGASUS_ENABLE_IPV6=true.<br

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

You can also perform manual

tests

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

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

running on the wbem standard http port of 5988:<br

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

osinfo -h ::1

</div>

<ol>

</ol>

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

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

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

specifications which which Pegasus conforms today.

DMTF specifications to which this version of Pegasus aims to conform

today.

<tbody>

<tr>

Line 2027

Line 1373

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

</tr>

<tr>

<td width="33%">DSP 0004 CIM Specification</td>

<td width="33%">DSP 0004 - CIM Infrastructure Specification</td>

<td width="33%">Version 2.2 with Addendum</td>

<td width="33%">Version 2.3 Final, 4 October 2005</td>

</tr>

<tr>

<td width="33%">DSP 0200 - CIM Operations over HTTP</td>

<td width="33%">1.1, final, 6  January 2002</td>

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

</tr>

<tr>

<td width="33%">DSP 0201 - Representation of CIM in XML</td>

<td width="33%">2.1, preliminary, May 2, 2002</td>

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

</tr>

<tr>

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

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

</tr>

<tr>

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

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

</tr>

<tr>

<td width="33%">WBEM SLP Template</td>

<td width="33%">DSP 0206 - WBEM SLP Template</td>

<td width="33%">1.0.0, Preliminary, January 2004</td>

</tr>

<tr>

<td width="33%">CIM Schema </td>

<td width="33%">2.9 Final, Jan. 2005</td>

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

in pegasus CVS)</td>

</tr>

</tbody>

</table>

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

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

Exceptions to

DMTF Specifications</a></h2>

It is a major goal

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

specifications.  However, today there are a number of known

differences. 

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

<ol>

<li>Provider Registration - Pegasus supports registration

through a set of Pegasus Provider registration classes rather than

support the DMTF defined Provider Qualifier. Pegasus will not support

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

provider registration.  This is not a deviation from the

specifications but is a different method of registration than many CIM

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

<li> Indications -Today Pegasus supports process

indications and lifecycle indications when defined specifically by

providers. Pegasus does not support lifecycle indications if they are

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

color="#ff0000">  For

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

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

<li>

<font

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

option on Instance Operations

The DMTF specifications have deprecated the use of qualifiers on

instance operations with the 1.2 CIM Operations Specification. 

Some CIM Client implementations expect instances

returned

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

definition (such as KEY qualifiers on properties).   Pegasus

today expects the provider to complete the qualifiers on instances in

accordance with the specification and generally the interpretation is

that Pegasus applies class level qualifiers when the includeInstance

parameter is supplied on instance operations.  However, Pegasus

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

should NOT depend on Pegasus accurately honoring the includeQualifier

parameter for instance operations.  In the future it is expected

that Pegasus will deprecate the use of qualifiers on instance

operations completely.

</li>

<li>LocalOnly option on instance

Operations - With the 1.1 version of Specification for CIM

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

GetInstance and EnumerateInstances operations was modified. This change

was incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

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

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

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

specification for more information.</li>

<li>

MultiRequest Oprations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOFCompiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

</li>

<li>Pegasus implements

chunking

based on the DSP0200 1.2.0 preliminary spec. Refer to bug <a

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

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

style="color: rgb(153, 51, 153);"> for more details.

</li>

</ol>

<h2>OpenPegasus <a

name="Supported Platforms">Supported

Platforms</a></h2>

Each Pegasus release lists as 'active' platforms those

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus

code

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

Line 2070

Line 1492

bugzilla database for a list of relevant defects that affect their

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

Pegasus release are:

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

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

<tbody>

Line 2139

Line 1560

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

width="211">

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

Linux IA-32, <span

style="color: rgb(153, 51, 153);">X86_64<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>

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

</td>

</tr>

Line 2164

Line 1586

<tr>

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

width="211">

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

Windows XP<o:p>,

Windows 2003</o:p>

</td>

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

width="289">

Line 2177

Line 1600

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

width="289"> gcc 3.3, gcc 4.01</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

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

style="color: rgb(153, 51, 153);">7.3-009 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>

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

style="color: rgb(153, 51, 153);">2-021 on OpenVMS IA64 and

above</big> </td>

</tr>

<tr>

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

style="color: rgb(0, 0, 0);">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

color="RED">Solaris 8

color="RED">Solaris 9

* See below for additional info

</big></td>

</big></td>

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

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

</td>

</tr>

</tbody>

</table>

Solaris:  Solaris testing

Platform patches

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

<font

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

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

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

<font

style="color: rgb(0, 0, 0);">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

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>

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

</o:p>

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

DMTF Specifications</a></h2>

It is a major goal

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

specifications.  However, today there are a number of known

differences. 

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

<ol>

<li>Provider Registration - Pegasus supports registration

through a set of Pegasus Provider registration classes rather than

support the DMTF defined Provider Qualifier. Pegasus will not support

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

provider registration.</li>

<li> Indications -Today Pegasus supports process

indications but does not

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

<li>

<font

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

option on Instance Operations

The DMTF specifications are unclear regarding the inclusion of

qualifiers on

CIM instances.  Some CIM Client implementations expect instances