pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.7 and 1.19.2.1

version 1.7, 2006/03/28 19:58:13

version 1.19.2.1, 2013/03/18 14:15:54

Line 1

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

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

<head>

http-equiv="Content-Type">

<style>

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

</style>

Line 963

Line 964

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

</head>

<o:smarttagtype

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> <o:Revision>4</o:Revision> <o:TotalTime>211</o:TotalTime> <o:Created>2004-04-05T14:13:00Z</o:Created> <o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>5026</o:Words> <o:Characters>28651</o:Characters> <o:Company>IBM</o:Company> <o:Lines>238</o:Lines> <o:Paragraphs>67</o:Paragraphs> <o:CharactersWithSpaces>33610</o:CharactersWithSpaces> <o:Version>10.4219</o:Version> </o:DocumentProperties></xml><![endif]--><!--[if gte mso 9]><xml>

<w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:Compatibility> <w:ApplyBreakingRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument></xml><![endif]-->

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

style="color: black;">

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

width="100%"></div>

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

center;" align="center"><span style="font-size: 13.5pt;

color: black;">OpenPegasus Enhancement Proposal (PEP)<o:p></o:p>

<span

style="color: black;">

PEP #: 364

Title: Release

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

<o:Revision>4</o:Revision>

<o:TotalTime>211</o:TotalTime>

<o:Created>2004-04-05T14:13:00Z</o:Created>

<o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved>

<o:Pages>1</o:Pages>

<o:Words>5026</o:Words>

<o:Characters>28651</o:Characters>

<o:Company>IBM</o:Company>

<o:Lines>238</o:Lines>

<o:Paragraphs>67</o:Paragraphs>

<o:CharactersWithSpaces>33610</o:CharactersWithSpaces>

<o:Version>10.4219</o:Version>

</o:DocumentProperties>

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

<w:WordDocument>

<w:SpellingState>Clean</w:SpellingState>

<w:GrammarState>Clean</w:GrammarState>

<w:Compatibility>

<w:ApplyBreakingRules/>

</w:Compatibility>

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

</w:WordDocument>

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

Notes for OpenPegasus version 2.12.1

Created: 10

September 2012

Authors: Karl

Schopmeyer, Marek Szermutzky

Pegasus

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

PEP #: 249

Title: Release

Notes for OpenPegasus 2.5.1

Version: 1.0

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

Authors: Karl Schopmeyer

Status:  draft

Version History:

Version

History:

<table class="MsoNormalTable" style="width: 100%;" id="table1"

border="1" cellpadding="0" cellspacing="1" height="155"

width="100%">

<tbody>

<td style="padding: 0.75pt; background: rgb(202, 230, 202)

<o:p> </o:p>

none repeat scroll 0% 50%; -moz-background-clip: initial;

-moz-background-origin: initial;

-moz-background-inline-policy: initial;" height="27">

<p class="MsoNormal" style="text-align: center;"

align="center"><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;" height="27">

<p class="MsoNormal" style="text-align: center;"

align="center"><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;" height="27">

<p class="MsoNormal" style="text-align: center;"

align="center"><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;" height="27">

<p class="MsoNormal" style="text-align: center;"

align="center"><span style="font-family: Arial;

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

</td>

</tr>

<p class="MsoNormal" style="text-align: center;"

align="center"><span style="font-family: Arial; color:

black;"> 1.0<o:p></o:p>

</td>

<p class="MsoNormal" style="text-align: center;"

align="center"> <span

style="font-family: Arial;">10 September 2012

</td>

<p class="MsoNormal" style="text-align: center;"

align="center"> <font

size="2">Karl Schopmeyer

</td>

<span style="font-family: Arial;

color: black;">Initial Submission <span

style="color: red;"><o:p><font

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

</td>

</tr>

<o:p> </o:p>

<tr>

<td style="padding: 0.75pt;" align="center" height="21">10

September 2012

</td>

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

<o:p> </o:p>

Schopmeyer

</td>

<td style="padding: 0.75pt;" height="21"> Minor fixes

<o:p> </o:p>

and complete links to PEPs

</td>

</tr>

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

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

September 2012

</td>

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

<o:p>  1 March

Schopmeyer

2006</o:p>

</td>

Karl Schopmeyer

</td>

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

Initial

all comments from first review

Submission<o:p>

</o:p>

</td>

</tr>

<tr>

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

<td style="padding: 0.75pt;" align="center" height="21">18

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

September 2012

<td style="padding: 0.75pt;">Fix editorial errors</td>

</td>

</tr>

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

Schopmeyer

</td>

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

<td style="padding: 0.75pt;" height="21"> Fix comments

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

on bug 8830 (compatibility considerations) and bug

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

9172(repupgrade)

Review week of 12 March 2006</td>

</td>

</tr>

<tr>

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

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

2006</td>

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

1.3

Schopmeyer</td>

</td>

<td style="padding: 0.75pt;">Typos</td>

<td style="padding: 0.75pt;" align="center" height="23">14

March 2013

</td>

<td style="padding: 0.75pt;" align="center" height="23">Marek

Szermutzky

</td>

<td style="padding: 0.75pt;" height="23">Update for 2.12.1

Release

</td>

</tr>

</tbody>

</table>

<o:p> </o:p>

<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

</a>

the 2.12.1 release of the OpenPegasus CIM Server. The purpose of

this PEP is to summarize the characteristics of this release,

point to other documentation that defines the release in more

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

detail, and provide additional information about this release

</o:p></h2>

that is not available in the other Pegasus documentation.

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

width="100%"></div>

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

<ol>

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

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

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

this Release</a></li>

This Release</a></li>

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

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

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

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

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

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

Considerations</a></li>

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

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

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

Platforms</a></li>

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

with DMTF Specifications</a></li>

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

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

in This Release</a></li>

<li> <a

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

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

Bugs</a></li>

Release

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

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

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

Documentation</a></li>

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

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

</ol>

<h2>Availability

<h2>Availability of this Release</h2>

of this Release</h2>

NOTE: This document

defines the OpenPegasus 2.12.0 minor version release with

comments added to define the 2.12.1 revision to that minor

release.  OpenPegasus 2.12.1 is a bug fix revision to

OpenPegasus 2.12.0. The complete list of changes (total of 12

bugs fixed)  is defined in OpenPegasus bugzilla with the <a

href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.1_APPROVED">2.12.1_APPROVED

bugs</a> query.  We recommend that all users of 2.12.0

review this list. OpenPegasus tries to execute only bug fixes

for revision releases and not include enhancements. The

OpenPegasus team recommends that users of Pegasus 2.12.0 update

to Pegasus 2.12.1. Note that in OpenPegasus ALL changes

including enhancements are defined as bugs and committed only

when the APPROVED keyword is set so that the list in the query

above defines ALL changes between 2.11.0 and 2.11.1.

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

downloaded from the OpenPegasus Web

formats. These can be downloaded from the <span

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

class="SpellE">OpenPegasus Web site at <a

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

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

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

<li>OpenPegasus source RPMs on the OpenPegasus web

also available that can be used to build binaries for most

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

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

site that can be used to build binaries for most LSB-compliant

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

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

subsequent snapshots that are made available in the Pegasus CVS are

<li>The OpenPegasus CVS repository. The CVS tags

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

representing this release and subsequent snapshots that are

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

made available in the Pegasus CVS are defined on the

snapshots page</a>.</li>

OpenPegasus CVS repository web page (see the <a

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

CVS

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

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

snapshots

page</a>.</li>

</ul>

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

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

WEB site</a>.

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

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

WEB

Pegasus source

tree.</div>

<h2>Functionality of This Release</h2>

site</a>. Installation instructions are part of the README in

Pegasus overall status by release is defined by  a

the root of the Pegasus source tree.

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

that is available on the OpenPegasus web site .  That

web page shows the Pegasus users and developers

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

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

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

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

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

are conditionally compiled with special environment variables.

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, deleteClass, modifyClass,

enumerateClass, enumerateClassNames)</li>

<li>Qualifier Operations (getQualifier, setQualifier,

deleteQualifier) </li>

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

enumerateInstance, enumerateInstanceNames, getProperty,

setProperty)</li>

<li>Association Operations (references, referencenames,

associators, associatornames)</li>

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

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

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

considered at alpha quality because it has only been contributor

tested.  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>Indication Processing</h4>

<h2>OpenPegasus Functionality in 2.12

<ol>

Release</h2>

<li>Process indications - Process indications are operational in

OpenPegasus overall status by release is defined by  a <a

the

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

Server.  This includes support

Status WEB Page</a> that is available on the OpenPegasus web

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

site .  That web page shows the Pegasus users and developers

for

the status of the various features found in OpenPegasus using a

indications and the CIMXML indication handler.</li>

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

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

description of each feature.

lifecycle indications (ie. those

OpenPegasus 2.12.1 is a Revision release.

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

</ol>

<h4>Query Language</h4>

Pegasus includes the  WQL  query language which is implemented and

used for filters and in version 2.4 for execQuery.

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

NOTE: OpenPegasus releases are categorized as follows:

combine to describe the CQL  functionality supported.

<ul>

<h4>Object Normalization</h4>

<li>First number of version changes (ex. 2.x.x to 3.0.0) -

The Object Normalizer is an entity introduced in Pegasus 2.4 that

Major release includes major functionality change and 

ensures

incompatible behavior changes and/or incompatible public API

objects delivered from providers are complete and accurate. Two major

changes,

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

</li>

Normalizer droped instances it considered bad, and 2) the Object

<li>Second number changes (ex 2.11.0 2.12.0) -  Minor

Normalizer code slowed performance. These issues are now addressed by

Release and includes new functionality but maintains behavior

moving the Object Normalizer from the Dispatcher to the Response

and public API compatibility,

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.

<h4>Embedded Object Support</h4>

Pegasus 2.5 provides embedded object support. The proposed solution

is restricted to the following:<ul>

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

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

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

</li>

<li>3rd number changes (2.12.0 to 2.12.1) - Revision(also called

point release) release and only includes bug fixes.</li>

</ul>

<h3>Pegasus Repositories

</h3>

The major areas of development including both enhancements and bug

fixes for the minor release 2.12 were as follows. Note that the

</blockquote>

bugs listed represent only those features incorporated in bugs

without PEPS that are considered enhancements, not all bugs

incorporated in the release. For more information access the

<h4>Schema Repository</h4>

PEP/BUG for each change defined below:

By default, Pegasus uses an XML-based

<font

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

style="font-weight: bold;" size="4">    Table

of Major Changes for this Release

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

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

bordercolorlight="#CCCCCC" border="1" cellspacing="1"

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

width="82%">

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

<tbody>

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

readme.binaryrepository file in the Pegasus source root directory.

<h4>Instance Repository</h4>

<th bgcolor="#00ffff">Description of Change</th>

The

<th bgcolor="#00ffff" width="128">Posted PEP

Pegasus schema repository may also be configured to hold instance

Version</th>

data.  Although instances may be place in the

</tr>

repository

<tr>

it was not designed as a

high volume data store.

<td>Provider Lifecycle Indications

<h4>Compressed Repository Feature</h4>

</td>

A compressed repository

<td style="text-align: center;"><a

feature has been added for

href="https://collaboration.opengroup.org/pegasus/pp/documents/25003/PEP360_PLI_Ver1_2.html">Ver

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

1.2</a>

feature is

</td>

documented in PEP 214 and also in a Readme

</tr>

(readme.compressed_repository). Note

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

activated for

<td align="left" width="75%">cimcli support for embedded

automatic tests.Further information on the use of the compressed

instances

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

</td>

root directory.

<td width="128"><a

<h4>Pegasus MOF Compilers</h4>

href="https://collaboration.opengroup.org/pegasus/pp/origrevdocuments/3195/PEP361_CIMCLIEmbeddedInstanceSupport.htm">Ver

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

1.1</a>

repository (cimmofl).

</td>

The direct interface compiler is used primarily to provide an

</tr>

initial

<tr>

class/instance repository. WARNING:

<td align="left" width="7%">PEP 304

The use of cimmofl

</td>

to manipulate instances in the repository bypasses any provider that is

<td align="left" width="75%">Allow modification of name of

registered to serve these  instances and simply installs the

interop namespace

instances in the

</td>

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

<td style="text-align: center;" width="128"><a

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

href="http://www.openpegasus.org/pp/uploads/40/23237/PEP_357_-_SNMP_v3_trap_generation_in_Pegasus_.htm"></a><a

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

href="https://collaboration.opengroup.org/pegasus/pp/documents/24686/PEP304_NamespaceRenaming.htm">Ver

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

1.5</a>

</td>

</tr>

<tr>

<td align="left">PEP 358

</td>

<td>WSMan indication handling and subscription support

</td>

<td align="center"><a

href="https://collaboration.opengroup.org/pegasus/pp/documents/26240/PEP_358_-_WSMAN_Eventing_support_in_Pegasus_.htm">Ver

1.1</a>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8891">Bug

8891</a>

</td>

<td>Enhance cimsub to add operations to create filters,

destinations and subscriptions

</td>

<td>

</td>

</tr>

<td style="text-align: center;" align="left" width="7%"><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=5667">Bug

5667</a>

</td>

<td align="left" width="75%">Remove experimental from

buildInstance and filter functions in CIMInstance class

</td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8952">Bug

8952</a></td>

<td> Support Configurable cipher suites in OpenPegasus</td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8904">Bug

8984</a></td>

<td>Add support for indication deliver connection pooling</td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9008">Bug

9008</a></td>

<td>Add new Indication runtime configuration variables:

maxIndicaitonDeliveryRetry Attempts  and

minIndicationdeliveryRetryInterval</td>

<td>

</td>

</tr>

<td style="text-align: center;" align="left" width="7%"><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9013">Bug

9013</a>

</td>

<td align="left" width="75%"><span style="color:

windowtext;">Enable ordered

indication delivery from provider through CIMServer when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE compile flag is set</td>

<td width="128"> <a

href="http://www.openpegasus.org/pp/uploads/40/22386/PEP_349_-_Improve_the_availability_of_the_CIMOM_by_better_isolation_from_faulty_providers.htm"></a>

</td>

</tr>

<tr>

<td style="text-align: center;" align="left"> <a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8800">Bug

9080 </a></td>

<td> Guaranteed provider

lifecycle indication delivery during CIMServer shutdown </td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9112">Bug

9112</a>

</td>

<td>Advertise IndicationService conformance to Indications

Profile by imlementing CIM_ElementConformsToProfile when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9114">Bug

9114</a>

</td>

<td>Advertise DMTF Indications Profile (DSP1054) 1.1.0

conformance </td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9118">Bug

9118</a>

</td>

<td>Add support for CIM_IndicationFilter.SourceNamespaces[]

property

</td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9136">Bug

9136</a></td>

<td>Runtime configuration option to restrict cimserver to

listen on selected network interfaces</td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9155">Bug

9155</a>

</td>

<td>Update to include CIM 2.31 Schema and set this as

default schema

</td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9159">Bug

9159</a></td>

<td>

<table style="font-family: Arial;"

bordercolordark="#666666" bordercolorlight="#CCCCCC"

border="1" cellspacing="1" width="82%">

<tbody>

<tr>

<td>Add SSL Support to Dynamic Listener

</td>

</tr>

</tbody>

</table>

</td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9172">Bug

9172</a>

</td>

<td>Add capability for administrator to override hostname

used by providers. This adds  new runtime

configuration variable hostname and

fullyQualifiedHostName. It is necessary to upgrade

existing repositories using repupgrade utility when

upgrading from OpenPegasus less than 2.12.0 and reusing an

existing repository.

</td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9215">Bug

9215</a>

</td>

<td>Add support of CQL query language to ExecQuery operation

in general. When the server receives  ExecQuery it

executes enumerate instance for providers that do not

support ExecQuery and filters result.

</td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9209">Bug

9209 </a>

</td>

<td>Add operations for display class tree and counting

instances to cimcli

</td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9227">Bug

9227</a>

</td>

<td>Enhance cimsub for batches of subscription oriented

operations

</td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9229">Bug

9229</a>

</td>

<td><a name="comtag_197">Add gcc build support on hp-ux for

the Common, Client and General libraries.</a></td>

<td>

</td>

</tr>

<tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9236">Bug

9236</a></td>

<td>Support for clang/clang++ compiler on Linux. This

version supports only X86 and X86_64 and requires clang

version 3 or greater.

</td>

<td>

</td>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality

change status between Pegasus versions. <a

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

identified by a change in color from the previous release to

this release</a> on the <a

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

Status WEB Page</a>.

<h3>Information on Interop namespace name (root/PG_InterOp) for

OpenPegasus 2.12

</h3>

Prior to version 2.12 OpenPegasus used an OpenPegasus internal

variable to define "root/PG_InterOp" as the name for the

OpenPegasus namespace with no defined way to change this

variable.  Note that an unsupported method involving

editing one file and rebuilding OpenPegasus was defined as a

workaround in the <a

href="%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus

wiki faq</a>s.

However, since the definition of a standard name for this

namespace in DMTF and SNIA specifications ("interop" or

"root/interop" with "interop" being the preferred alternative)

the use of  "root/PG_InterOp" has become an issue.

Effective OpenPegasus 2.12.0 a new build variable has been

defined  (PEGASUS_INTEROP_NAMESPACE) which allows an

OpenPegasus builder to define an alternate name for the Interop

namespace to either "interop" or "root/interop" (ex.

PEGASUS_INTEROP_NAMESPACE = interop).  Once this build

variable is defined and OpenPegasus compiled, the actual name of

the interop namespace is what was defined in this variable and

all components of OpenPegasus use this as the interop namespace

name include the complete OpenPegasus test suite.  The only

name for the interop namespace will be the name defined through

this build variable.

However, today OpenPegasus is committed to the single namespace

defined at build "(root/PG_InterOp", "interop", or

"root/interop"). However, a number of OpenPegasus 

installations are committed to the "root/PG_InterOp" name and

must maintain their repositories through updates of OpenPegasus.

While we are working on this issue today (which means that a

running version of OpenPegasus must accept both the and new

names and not confuse clients, listeners or providers that would

use either name) the OpenPegasus team did not complete that work

for this release. See bug <a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9250">9250</a>

for more information about possible solutions and our progress

on a solution.

NOTE: If you redefine the interop namespace name with

PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp"

namespace will not connect with the updated version of

OpenPegasus.

<h3>Security Considerations</h3>

OpenPegasus 2.5 (and

<h3>Information on  IPv6 Support (PEP

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

291)</h3>

of these authorization checks are performed by default.

NOTE: This functionality was incorporated in OpenPegasus

By registering any provider which fails to do appropriate authorization

2.7.0 but it was felt that the information below was worth

checks, the consequences may include information leakage, data

repeating in subsequent Release Notes

corruption, or unintended elevation of privilege. Please ensure that

IPv6 is

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

short for "Internet Protocol Version 6". IPv6 is the "next

your systems and data:

generation" protocol designed by the IETF to replace the

1. Only install/register providers which perform authorization

current version Internet Protocol, IP Version 4 ("IPv4"). IPv6

appropriate for your environment.

Support for OpenPegasus is documented in <a

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

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

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

PEP 291</a>.

performing authorization checks within the provider.

The IPv6 support in OpenPegasus is controlled by the

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

PEGASUS_ENABLE_IPV6 build variable. The default for this

your environment have performed sufficient authorization checks. Also,

variable is "true"; setting this to 'false' before building

monitor announcements of security defects in those providers and follow

OpenPegasus will disable the IPv6 support.

the recommendations in those announcements as soon as possible.

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

The following subsections provide some information on IPv6

you are shipping have performed appropriate authorization checks, and

support for the Linux and Windows platforms. Note that in the

relay announcements of discovered security defects to your users.

2.6.1 release there is no automatic run-time detection of IPv6

support on a platform by OpenPegasus. If you build with

PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you

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

bind() failure, or possibly some other failure. This applies to

both the CIM Server and Listener components. For more

information on IPv6 support for your specific platform, refer to

the documentation for that platform.

All OpenPegasus externals that support either a hostname or an

IP address as input have been updated to allow an IPv6 address

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

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

must be specified without brackets. For example, the OpenPegasus

osinfo client (which returns information about the OS running on

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

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

specified as:

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

font-family: monospace;"><big>osinfo -h

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

But the cimcli command, which takes an optional "location"

option including an optional port number, requires the IPv6

address to be delimited with brackets, for example:

<div style="margin-left: 40px; font-family: monospace;"><big>cimcli

ns -l [3ffe:1:2:1]</big></div>

or

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

monospace;">cimcli ns -l [3ffe:1:2:1]:5989</big>

</div>

2. Restrict users with

access to Pegasus to a specific authorized user group of trusted

individuals.

3. Namespace authorization is also available.

For administration issues please refer to

For more information on specifying IPv6 addresses, refer to <a

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

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

<h4>Server Security</h4>

Version 6 Addressing Architecture</a> and <a

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

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

Format for Literal IPv6 Addresses in URL's</a>.

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

<h4>IPv6 on Linux</h4>

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

Modern Linux distributions already contain IPv6-ready kernels,

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

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

implemented in Pegasus using the OpenSSL

possible that this module is not loaded automatically on

libraries. Pegasus does not provide the OpenSSL

startup.

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

Note: you

with multiple versions of  OpenSSL versions

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

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

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

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>

is no longer improved according to definitions in latest RFCs.

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

It's recommend to use series 2.6.x now.

<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 237</a> for details on

configuration.

</li>

</ol>

<h4>Client Security</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: 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.  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 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>).</li>

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

this feature </li>

<li class="MsoNormal" style="color: black;">Shared class namespaces - 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 - 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 237</a> describes the  environment variable (PEGASUS_ENABLE_SLP) to

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

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

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

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

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

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.

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

To check whether your current running kernel supports IPv6,

Pegasus 2.5 includes

take a look into your /proc filesystem. The entry

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

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

result of a project by the IBM SBLIM team (see 

like:

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

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

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.

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>

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

Pegasus

font-family: monospace;"><big>test -f

includes a provider manager for Java

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

provider interfaces based on the SNIA provider interface

ready"</big></div>

definitions.  This provider manager is  considered alpha

For more information on enabling IPv6 in the Linux kernel and

quality and is not compiled in the default build.   See

configuring network interfaces, refer to <a

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

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

</blockquote>

Linux Documentation Project's IPv6 HOWTO</a>.

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

Warning: There is

ensure that the provider vendor

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

has made use of available authorization capability.

seen intermittently on RHEL5 and SLES10 systems. This problem is

</div>

described in <a

There are a number of providers available

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

in the Pegasus release.

bug

This includes providers in the following categories:

<h4>Pegasus Internal Providers</h4>

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

6586</a> and

access to the CIMOM for information and provide information and

services to support the CIMOM and its administration.    The

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

providers in this category are mostly defined in the directory

bug

src/pegasus/controlproviders and include support for the following

classes:

<ul>

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

248052</a>, and manifests itself as an intermittent

CIM_CommunicationMechanism, and

IPv6 socket failure. You should be aware that OpenPegasus with

CIMOMStatistics.</li>

IPv6 enabled may be significantly impacted in these

</ul>

environments.

<h4>CMPI Remote Providers</h4>

<h4>IPv6 on Windows</h4>

Pegasus includes an support for

Microsoft provides supported IPv6 implementations for Windows

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

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

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

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

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

On Windows XP, you can use the ipv6.exe

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

tool to install, uninstall, and query your IPv6 configuration. For

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

example:

Generic Providers</h3>

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

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

the

font-family: monospace;"><big>ipv6 install

directory src/Providers/generic.

ipv6 if</big></div>

<h4>Test/Sample Providers</h4>

Windows Vista and Windows Server 2008 support an integrated

See the directories src/Providers/TestProviders

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

and src/Providers/sample for more

stack. Note that the OpenPegasus IPv6 support has not yet been

information about test and

tested on Windows Vista or Windows Server 2008.

sample providers.

<h4>Managed System Providers</h4>

For more information on installing, configuring, and using IPv6

ComputerSystem, DNSAdmin,

on Windows platforms, refer to the document <a

DNSService, Operating System, Process,

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

Processor. For

color="#000000">IPv6 for Microsoft Windows: Frequently Asked

more information on these providers see the documentation for each

Questions</a>.

provider in

the directory src/Providers/ManagedSystem

<h4>Server Statistics Provider

</h4>

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

are implemented in this release. The statistics gathering is compiled

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

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

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

<h4>Testing  OpenPegasus IPv6 support</h4>

<h3>Embedded CIMListener</h3>

As part of the OpenPegasus automated tests, the TestClient,

This listener is embedded in the CIMServer and allows the

g11ntest, and IndicationStressTest test clients were modified to

server to accept indications and route them.

run tests using the IPv6 loopback address (::1) if

<h3>Standalone Static CIMListener</h3>

PEGASUS_ENABLE_IPV6=true.

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

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

maintained in the

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

test

environment.

</blockquote>

<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

You can also perform manual tests using the IPv6 loopback or a

note:

real IPv6-configured network interface. For example, using the

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

IPv6 loopback on a system with OpenPegasus running on the WBEM

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

standard http port of 5988:

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

specified in the configuration.  The new order for determining the

<big style="font-family: monospace;"> osinfo -h ::1</big></div>

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

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

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

Considerations</a></h2>

values.

Support for forward-compatibility is a fundamental design

</div>

principle for the OpenPegasus project. As a community, our goal

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

is for well-behaved OpenPegasus providers or clients, using only

in /etc/services is used.

the externally defined OpenPegasus interface, to continue to

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

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

used.

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

</div>

standard that significantly affects interoperability) that may

<h3>Information client tools</h3>

require the community to make potentially incompatible changes.

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

The following table contains a list of defects/fixes that MAY

impact, even well-behaved, OpenPegasus providers or clients when

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

upgrading to this OpenPegasus release.

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

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

WMI Mapper

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

<ol>

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

</ol>

bordercolorlight="#CCCCCC" border="1" cellspacing="1"

<h2>Relationship to

width="80%">

CIM/WBEM Standards</h2>

<tbody>

<th bgcolor="#00ffff" width="10%">Bugzilla #</th>

<th bgcolor="#00ffff">Description</th>

</tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8830">Bug

8830</a></td>

<td align="left">Starting with OpenPegasus 2.11.0 the

requirement for providers (CMPI and C++) to filter

properties from instances has been relieved. The server

will do the filtering at the protocol adapter level. To

avoid a negative impact on performance the

CIMInstance::filter() and

CMPIInstanceFT.setPropertyFilter() functions have been

changed to a NOP. This may be a change in behavior for

provider relying in some unknown way on the instance being

filtered through these functions. To allow users to

actually filter properties from an instance, new function

CIMInstance::filterInstance() will actually filter

properties from an instance exactly as the

CIMInstance::filter() did in previous versions of Pegasus.</td>

</tr>

<td><a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9369">Bug

9369</a>

</td>

<td align="left">Reregistering of an indication provider

requires that the  cimserver be restarted to send the

enableIndication request to the providers. This issue has

existed starting with OpenPegasus 2.10 to the current

version. If the cimserver is not restarted the indication

will not be enabled for the reregistered provider. </td>

</tr>

</tbody>

</table>

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

CIM/WBEM specifications The following table defines the level of

to which this version of Pegasus conforms today.

the DMTF specifications to which this version of Pegasus aims to

conform today.

<tbody>

<tr>

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

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

</tr>

<tr>

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

<td width="33%">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%">Version 1.2, Final, January 09, 2007</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%">Version 2.2 Final, January 09, 2007</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.31.0 Final ( default) </td>

</tr>

<tr>

<td>DSP0226 - Web Services for Management

</td>

<td>Version 1.1.1

</td>

</tr>

<tr>

<td>DSP0227 - WS-Management CIM Binding Specification

</td>

<td>Version 1.2.0

</td>

</tr>

<tr>

<td>DSP0230 - WS-CIM Mapping Specification </td>

<td>Version 1.1.0

</td>

</tr>

</tbody>

</table>

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

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

Platforms</a></h2>

SMI Profiles Supported</h2>

Each Pegasus release lists as 'active' platforms those

Today OpenPegasus includes support for several DMTF profiles

hardware/software platforms that have recognized ports for the Pegasus

including the ones defined below:

code

<ol>

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

<li>DMTF ProfileRegistration Version 1.0.0</li>

regularly document issues and/or fix defects as the Pegasus

<li>DMTF Indications 1.1.0. Since this is effectively the same

code base is changed. 

as the SNIA SMI Indication profile it also supports this

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

profile. This profile is enabled by compiling OpenPegasus with

a group

the build variable PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

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

</li>

Pegasus cannot be

<li>SNIA Profile Registration 1.0.0</li>

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

<li>SNIA Server 1.1.0 & 1.2.0

responsibility of the entity that packages and/or compiles OpenPegasus

</li>

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

</ol>

bugzilla database for a list of relevant defects that affect their

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

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

Exceptions to DMTF Specifications</a></h2>

Pegasus release are:

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

class="norm"> For more

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

size="2">  pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a><font

size="2">.</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 and stated specifically that the

client should NOT depend on the includeQualifiers

parameter of the CIM/XML instance operations returning

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

 When Pegasus uses object normalization, the normalizer

does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.

</li>

<li>LocalOnly option on instance Operations - With the

1.1 version of Specification for CIM Operations over HTTP, the

definition of the LocalOnly parameter for the GetInstance and

Enumerate Instances operations was modified. This change was

incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

introduced by this change, we strongly recommend that CIM

Clients set LocalOnly = false and do not rely on the use of

this parameter to filter the set of set of properties

returned. See Appendix C of this specification for more

information.</li>

<li>

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation

option.

</li>

<li>

MOF Compiler namespace pragma -

The Pegasus compiler does not support the namespace pragma.

</li>

<li>CIMOperation Trailer - Pegasus implements chunking

based on the DSP0200 1.2.0 preliminary spec. including the

operation trailer defined in that specification Refer to bug <a

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

for more details. This trailer was completely removed from the

DSP0200 1.2 final specification as a non-compatible change so

that if chunking is used Pegasus is returning a noncompliant

response to enumerate type requests. </li>

<li>Whitespace in XML value

Element - Pegasus trims the leading and trailing

whitespace from XML value elements that are of the Type

String.  This behavior is documented in Pegasus bug <a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8773">8773</a>

and there is a patch available for users.  However, since

the change is considered a change to behavior this will not be

patched until pegasus does a major version update. NOTE: There

are some documented bugs in Pegasus such as this that the

OpenPegasus team feels cannot be incorporated into the code

until a major version update.  These bugs are documented

with the Bugzilla tag <big style="font-weight: bold;"><samp>"3.0_TARGET".</samp></big></li>

<li>modifyInstance operation

behavior in the Pegasus repository does not match the DMTF

specification. Under some conditions (ex. if no

propertyList is supplied) it modifies all properties rather

than just the properties supplied with the request thereby

Nulling out existing values. See bug <a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8752">8752</a>

for more information.</li>

<li>OpenPegasus Interop Namespace - The default interop

namespace name in OpenPegasus is "root/PG_Interop".  In

versions of OpenPegasus prior to 2.12.0 this could be changed

during build by modifying a string definition in the code.

Effective version 2.12 this  has become a build option

with the build configuration environment variable

PEGASUS_INTEROP_NAMESPACE = <name for this namespace>

however, the default if built without this change is still

"root/PG_InterOp"

</li>

<li>OpenPegasus WSMAN protocol on windows does not handle

NaN, INF, or -INF (bug  <a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>)

- If requests or responses include properties or parameters

with floating point property types (Real32 or Real64) with the

special states NaN, INF, or -INF on a Windows platform, the

input is not accepted because these special strings are not

understood by the decoder on Windows.</li>

<li>OpenPegasus outputs Nan, INF, -INF special values for

Real32 and Real64 property and Parameter types for the

CIM/XML protocol - (bug <a

href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9392">9392</a>).

Today the DMTF Specification DSP0201 allows only numeric

information in the format definition for this type and does

not all the special strings Nan, etc. However, OpenPegasus

actually outputs the special strings if  that is what is

defined in the internal values.  OpenPegasus does not

allow these special Strings on input however,</li>

<li>OpenPegasus does not handle covered properties - (bug

<a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">3571</a>)

Covered properties (properties which have the same name in a

superclass and subclass without overridding the property in

the superclass) are not allowed in OpenPegasus. While the

requirement for this functionality was added to DSP0004

subsequent to version 2.4, the general agreement is that the

requirement itself is not supportable and particularly not

with the existing OpenPegasus APIs.  Further, the

requirement is expected to be removed in the future (i.e CIM

3.0).

</li>

</ol>

<h2>OpenPegasus <a

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

Each OpenPegasus release lists as 'active'

platforms those hardware/software platforms that have recognized

ports for the Pegasus code base including a maintainer for the

platform that will be willing to regularly document issues

and/or fix defects as the Pegasus code base is changed. 

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

without a group to provide the role of test and maintenance,

correct operation of  Pegasus cannot be assured.  In

all cases, including the active platforms, it is the

responsibility of the entity that packages and/or compiles

OpenPegasus for shipment or deployment, to read, and actively

monitor the Pegasus Bugzilla database for a list of relevant

defects that affect their platform.   The platforms

that are considered ported are shown in the two tables

below.  The first table represents platform for which

testing is done on a regular basis and reported to the Pegasus

Nightly Build Test WEB Page. Those platforms which have been

ported but do not have test results that are current at the time

of the release are reported in the second table.

Actively Supported Platforms (Nightly Tests Reported for this

release)

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

cellpadding="0" cellspacing="1">

<tbody>

<td style="padding: 0.75pt; background: rgb(0, 255, 255)

Platform and

none repeat scroll 0% 50%; -moz-background-clip: initial;

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

-moz-background-origin: initial;

-moz-background-inline-policy: initial; width: 240px;"

height="26">

Platform

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

</td>

<td style="padding: 0.75pt; background: rgb(0, 255, 255)

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

none repeat scroll 0% 50%; -moz-background-clip: initial;

-moz-background-origin: initial;

-moz-background-inline-policy: initial; width: 75%;"

height="26">

Compilers<span

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

</td>

</tr>

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

HP-UX<o:p>

PA_RISC and Itanium</o:p>

</td>

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

HP <span

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

</td>

</tr>

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

<span

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

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

</td>

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

<span

style="color: black;">gcc<span

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

</td>

</tr>

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

<span

style="color: black;">zLinux<span

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

</td>

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

<span

style="color: black;">gcc<span

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

</td>

</tr>

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

Linux

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

</td>

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

<span

style="color: black;">gcc<span

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

</td>

</tr>

<td style="padding: 0.75pt;"> <font

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

size="3">Linux IA-32</td>

<td style="padding: 0.75pt;"> <span

style="color: black;">gcc<span

style="color: black;"> (versions 3.xx,

4.xx) clang(The clang compiler usage is considered

experimental and is not part of the nightly tests

today)<o:p></o:p></td>

</tr>

Linux

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

</td>

gcc

<span

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

style="color: black;">gcc<span

style="color: black;"> (versions 3.xx, 4.xx) <span

style="color: black;">clang(The clang

compiler usage is considered experimental and is not

part of the nightly tests today)

</td>

</tr>

<tr>

<td style="vertical-align: top;">z/OS V1.7

and up</td>

<td style="vertical-align: top;">XL C/C++

from z/OS Version 1.7 and up</td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this

release (No current Nightly Build Test Results

<table class="MsoNormalTable" style="width: 90%;" id="table2"

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

<tbody>

<td style="padding: 0.75pt; background: rgb(0, 255, 255)

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

none repeat scroll 0% 50%; -moz-background-clip: initial;

-moz-background-origin: initial;

-moz-background-inline-policy: initial; width: 240px;"

height="26">

Platform

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

</td>

<td style="padding: 0.75pt; background: rgb(0, 255, 255)

Microsoft

none repeat scroll 0% 50%; -moz-background-clip: initial;

Visual C++ Ver 6 and Microsoft .Net compiler Version.   Works on VC .NET 2003 (aka

-moz-background-origin: initial;

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

-moz-background-inline-policy: initial; width: 75%;"

height="26">

Compilers<span

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

</td>

</tr>

<tr>

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

Windows XP<o:p>, Windows

Windows Vista, Windows 7, Windows Server 2008

2003</o:p>

</td>

Microsoft

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

</td>

<td style="padding: 0.75pt;"> Microsoft

Visual C++ Compilers 2003 - 2010.. Note: Visual C++ Ver.

6 no longer being regular tested.Note that today there

are some open issues with the Windows. </td>

</tr>

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

<td style="padding: 0.75pt;"> MacOS version

10.3 and higher</td>

</tr>

<tr>

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

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

</big></td>

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

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

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

Alpha and above</big> </td>

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> HP OpenVMS IA64</big></td>

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

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

color="RED">Solaris

9</big></td>

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

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

</td>

</tr>

<tr>

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

<td><big>HP OpenVMS 8.3 or later Alpha</big></td>

</big></td>

<td><big>HP

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

C++ V7.3-009

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

or later required for OpenVMS Alpha</big></td>

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

</tr>

<tr>

<td><big> HP OpenVMS 8.3

or later IA64</big></td>

<td><big>HP C++ V7.<font

color="#993399">3-023 or later required<font

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

</tr>

<tr>

Windows

2000

</td>

<td style="padding: 0.75pt;"> Microsoft

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

version. Works on VC .NET 2003 v7.1). NOTE: Visual

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

</tr>

<tr>

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

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

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

<td style="padding: 0.75pt;"> Microsoft

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

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

tested. </td>

</tr>

<tr>

<td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc

and IX86)</big></td>

<td><big>CC Compiler Sun Studio 5.11</big></td>

</tr>

</tbody>

</table>

Platform patches

Platform patches

<font

The following is a list of platform

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

patches Pegasus requires.

platform patches Pegasus requires.

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">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</a>

Further information regarding Pegasus support on HP platforms can be

found at:

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

<h2><a name="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>

IncludeQualifiers

option on Instance Operations

The DMTF specifications are unclear regarding the inclusion of

qualifiers on

CIM instances.  Some CIM Client implementations expect instances

returned

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

definition (such as KEY qualifiers on properties).   Pegasus

today expects the provider to complete the qualifiers on instances in

accordance with the specification and generally the interpretation is

that Pegasus applies class level qualifiers when the includeInstance

parameter is supplied on instance operations.  However, Pegasus

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

should NOT depend on Pegasus accurately honoring the includeQualifier

parameter for instance operations.  In the future it is expected

that Pegasus will deprecate the use of qualifiers on instance

operations completely.

</li>

<li>LocalOnly option on instance

Operations - With the 1.1 version of Specification for CIM

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

GetInstance and EnumerateInstances operations was modified. This change

was incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

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

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

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

<li>

CIM MOF compiler function for

<font

instance aliasing - The Pegasus MOF compiler does not today support

style="color: rgb(0, 0, 0);">RHAS 2.1 needs the update

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

to fix Red Hat Bugzilla 98815.

</li>

<li>

MultiRequest Oprations - Pegasus

RHEL 4.4

does not support the DMTF defined MultiRequest Operation option.

multithreading bug in getpwuid-r could cause a CIM Server

failure (Bugzilla 6232). This is fixed in RHEL 4.5

</li>

<li>

MOFCompiler namespace pragma - The

Red Hat and

Pegasus compiler does not support the namespace pragma.

SUSE Linux multiple versions - multithreaded client

</li>

intermittently fails connecting to IPv6 (Pegasus Bugzilla

</ol>

6586) (Red Hat bug 248052)

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

The development and release of each version of Pegasus is defined

and

controlled through Pegasus PEP documents.  PEP 180 is the

controlling document  for Pegasus 2.5.0 and PEP 239 is the controlling

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

Addition of CQL

stage 1 support

</li>

</ol>

Refactoring of

</div>

Object Normalizer function to improve performance.

Further information regarding Pegasus support on IBM platforms

</li>

can be found at: <a

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

Out of Process

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>

Provider user level request.

</li>

Embedded Object

support.

</li>

Command Line

Utilities

</li>

CIMDateTime

enhancements

</li>

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

Completion of

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

AutoPtr enhancements.

Defects</a></h2>

</li>

The OpenPegasus Bugzilla database documents any defects found

in Pegasus and  is available through the following

Certificate

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

management and user-based certificate authentication

bugzilla database</a>.   Effective with the start of

the OpenPegasus 2.6 work, all changes to the CVS tree are

documented through bugs.  Bugs reports are filed not only

for bugs and their corresponding fixes but also as part of the

process of committing new code representing the work on PEPs

done for OpenPegasus 2.6 and all subsequent versions. 

Therefore, a search of the OpenPegasus Bugzilla base for bugs

with the tag for a particular version (ex.  <a

href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED">2.6.0_APPROVED</a>,

href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED">

2.6.1_APPROVED</a>, <a

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

etc) will yield all changes to the Pegasus CVS tree for that

OpenPegasus release.

- Changes between the 2.12.0 release

and 2.12.1 revision are defined in bugs tagged

(2.12.1.APPROVED). The complete list of 12 bugs is <a

href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.1_APPROVED">2.12.1_APPROVED

bugs</a>

</li>

- Changes that were made in the minor

release 2.12 are in bugs Tagged 2.12.0_APPROVED. The link

Completion of HTTP

is <a

chunking. Pegasus

href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.0_APPROVED">

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

Pegasus 2.12.0_APPROVED bug list.</a>

PEP 140</a> describes the implementation details.

</li>

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

statistics</li>

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

<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 changes defined for this release

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 href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla

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

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

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

Documentation">Release Control and Version Definition

The Pegasus project is controlled largely through a set of documents

Documentation</a></h2>

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

The OpenPegasus project is controlled largely through the CVS

modified Pegasus functionality and for the definition and documentation

repository and a set of documents (PEPs) that serve both as the

of releases.

definition and review mechanism for new and modified Pegasus

Specifically the following PEPs define the characteristics of this

functionality and for the definition and documentation of

Pegasus release.

releases.

<ol>

The following documentation defines the characteristics of this

<li>

Pegasus release. The documents are available in the

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

OpenPegasus CVS repository.

</li>

<ul>

<li>

<li> OpenPegasus Release Definition/Status -No PEP (See Wiki

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

Section <a

Option  for Selected

href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2.12_x">OpenPegasus

Platforms</li>

2.12.x

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

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

<li>

<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

Release Status</a>) - A

</li>

<li>

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

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

section in the Pegasus wiki is used throughout the

and also in the Pegasus

development of this version as the control point for

source

functionality that will go into the release and points to

tree root directory).</li>

all of the PEPs that represent the Pegasus 

<li>

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

<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

OpenPegasus

throughout the development of this version as the control point for

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

PEPs that represent the Pegasus 2.5 functionality changes.  (as of

this document verion of PEP 230, PEP 180 is listed as draft status)</li>

Build and Configuration Options  for Selected Platforms

</ol>

-  In previous

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

versions of Pegasus this information was  released as a

The following documentation is available for the this Pegasus

Pegasus PEP. Starting with Pegasus 2.9.0 the information is

release:

located in the OpenPegasus CVS repository as <big

style="font-weight: bold;"> <span style="font-family:

monospace;">pegasus/doc/BuildAndReleaseOptions.html</big>.

<li> OpenPegasus External Interfaces -<span

style="font-weight: normal;">The list of the OpenPegasus

interfaces that are considered external and therefore

"frozen". Unless an exception is explicitly approved by

the Steering Committee all subsequent releases of Pegasus

MUST continue to support these interfaces. Interfaces not

explicitly listed in this document, should be considered

as internal and subject to change.In previous Pegasus

releases this information was available as a separate PEP.

Starting with Pegasus 2.9.0 this information is integrated

into the Pegasus repositoryas  <small

style="font-weight: bold;"><font face="Courier New"

size="4">pegasus/doc/EnternalInterface.html<span

style="font-weight: normal;">.</li>

<li> OpenPegasus  SDK Packaging Definition - <span

style="font-weight: normal;">Defines the recommended set

of files for inclusion in the OpenPegasus SDK. Starting

with Pegasus release 2.11.0, this document is available in

the Pegasus CVS repository as <big style="font-weight:

bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>.

In previous Pegasus releases this document was made

available as s separate Pegasus PEP document rather than

in the CVS repository.  </li>

<li> Pegasus  Runtime Packaging Definition - <span

style="font-weight: normal;">Defines the recommended set

of files for inclusion in this OpenPegasus release.

Starting with Pegasus release 2.11.0, this document is

contained in the CVS repository as <big

style="font-weight: bold;"><samp>pegasus/doc/RuntimePackaging.html</samp></big>.

In previous releases this was made available as a seperate

Pegasus PEP document rather than in the CVS repository.  </li>

<li>Pegasus Release Notes - <span style="font-weight:

normal;"> PEP 364 - <span style="font-weight:

normal;"> (This document is located in the approved PEP

repository and the OpenPegasus source tree root directory

(<big style="font-weight: bold;"><span style="font-family:

monospace;">pegasus/ReleaseNotes.htm</big>)</li>

</ul>

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

The following documentation is available for the this

Pegasus release:

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

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

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

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

</li>

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

A combination of help generally available with the --help

documentation - See the header files and the HTML  API

option for each command and HTML documentation for most of the

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

tools.<o:p></o:p>

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

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

documentation.  In particular the Common/tests unit tests contain

usage documentation - </li>

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

See the header files and the HTML  API documentation

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

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

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

existing utilities and test programs and the examples in the API

documentation, and documentation from the Pegasus Technical Workshop

documentation.  In particular the Common/tests unit tests

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

contain extensive examples of the use of the Common APIs.

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

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

Clients - API documentation and the documentation on the Pegasus

Debugging Providers - </li>

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

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

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

documentation, and documentation from the Pegasus Technical

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

Workshop which is available on the Pegasus web site.

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

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

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

Debugging Clients - </li>

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

API documentation and the documentation on the Pegasus

OpenPegasus web site.  While these are the original design

Technical Workshop which is available on the Pegasus web site.

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

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

The features of Pegasus that have been installed in this and

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

the previous few versions are defined by Pegasus PEPs that are

available on the OpenPegasus web site.  While these are the

original design documents largely and use in the process of

defining and approving the overall characteristics of new

functionality, they serve as a guide to the design and

implementation of these features.

</ul>

<hr>Licensed to The Open Group (TOG) under one or more contributor

<o:p></o:p>

license agreements. Refer to the OpenPegasusNOTICE.txt file

distributed with this work for additional information regarding

under the OpenPegasus Open Source License; you may not use this

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

file except in compliance with the License.

Group; VERITAS Software Corporation; Intel Corp.

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

obtaining a copy of this software and associated documentation

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

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

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

restriction, including without limitation the rights to use,

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

copy, modify, merge, publish, distribute, sublicense, and/or

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

sell copies of the Software, and to permit persons to whom the

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

Software is furnished to do so, subject to the following

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

conditions:

The above copyright notice and this permission notice shall be

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE

included in all copies or substantial portions of the Software.

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

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,

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

EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES

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

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

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

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT

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

HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,

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

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

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

FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR

SOFTWARE.</div>

OTHER DEALINGS IN THE SOFTWARE.

</div>

</body></html>

</body>

</html>

Legend:

Removed from v.1.7
changed lines
	Added in v.1.19.2.1

No CVS admin address has been configured