pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

version 1.3, 2005/08/26 16:13:44

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

Line 1

<html xmlns:v="urn:schemas-microsoft-com:vml"

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

<head>

http-equiv="Content-Type">

<style>

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

</style>

Line 448

Line 450

margin:1.0in 1.25in 1.0in 1.25in;

mso-header-margin:.5in;

mso-footer-margin:.5in;

mso-paper-source:0;}

div.Section1

{page:Section1;}

Line 569

Line 572

text-indent:-.25in;}

@list l4:level7

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

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level8

Line 598

Line 602

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

mso-level-number-position:left;

text-indent:-.25in;}

@list l5:level5

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

mso-level-number-position:left;

Line 888

Line 891

text-indent:-.25in;}

@list l19

{mso-list-id:1902863286;

mso-list-template-ids:740079056;}

@list l19:level1

{mso-level-number-format:bullet;

Line 960

Line 964

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso">

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

</head>

name="City"/>

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

<o:smarttagtype

name="place"/>

namespaceuri="urn:schemas-microsoft-com:office:smarttags"

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

name="City"></o:smarttagtype> <o:smarttagtype

name="date"/>

namespaceuri="urn:schemas-microsoft-com:office:smarttags"

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

name="place"></o:smarttagtype><o:smarttagtype

<o:DocumentProperties>

namespaceuri="urn:schemas-microsoft-com:office:smarttags"

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

name="date"></o:smarttagtype><!--[if gte mso 9]><xml>

<o:LastAuthor> </o:LastAuthor>

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

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

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

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

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

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

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

style="color: black;">

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

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

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

width="100%"></div>

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

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

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

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

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

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

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

<span

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

style="color: black;">

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

PEP #: 364

</o:DocumentProperties>

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

Title: Release

<w:WordDocument>

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

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

<w:Compatibility>

Notes for OpenPegasus version 2.12.1

<w:ApplyBreakingRules/>

Created: 10

</w:Compatibility>

September 2012

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

</w:WordDocument>

Authors: Karl

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

Schopmeyer, Marek Szermutzky

Status:  draft

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

Version

style='color:black'>

History:

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

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

width="100%">

</div>

<tbody>

<span

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

style='font-size:13.5pt;color:black'>Pegasus Enhancement Proposal (PEP)<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;"

PEP #: 150<o:p></o:p>

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

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

Title: Release Notes Pegasus 2.3.2

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

<tr>

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

September 2012

</td>

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

Schopmeyer

</td>

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

and complete links to PEPs

</td>

</tr>

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

September 2012

</td>

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

Schopmeyer

</td>

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

all comments from first review

</td>

</tr>

<tr>

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

September 2012

</td>

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

Schopmeyer

</td>

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

on bug 8830 (compatibility considerations) and bug

9172(repupgrade)

</td>

</tr>

1.3

</td>

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

March 2013

</td>

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

Version: 1.5

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

Szermutzky

</td>

Authors: <st1:City><st1:place>Warren</st1:place></st1:City> <span

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

class=SpellE>Grunbok

Release

                Karl

Schopmeyer

Status:  draft

Version History:

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

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

<span

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

</td>

<span

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

</td>

<span

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

</td>

<span

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

</td>

</tr>

<span

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

</td>

<st1:date

Year="2004" Day="23" Month="3">

23

March 2004</st1:date><o:p></o:p>

</td>

<span

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

</td>

Initial

Submission<o:p></o:p>

</td>

</tr>

<span

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

</td>

<st1:date

Year="2004" Day="4" Month="4">

4

April 2004</st1:date><o:p></o:p>

</td>

<span

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

mso-fareast-font-family:"Times New Roman";color:black'><o:p>K

Schopmeyer</o:p>

</td>

Incorporate comments

from� review<o:p></o:p>

</td>

</tr>

<o:p>

1.2/3</o:p>

</td>

<o:p>

15

April 2004</o:p>

</td>

<o:p>

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

mso-fareast-font-family:"Times New Roman";color:black'><o:p>K

Schopmeyer</o:p>

</td>

<o:p>

Incorporate

comments from Second review</o:p>

</td>

</tr>

<span style='font-family:Arial;

mso-fareast-font-family:"Times New Roman";color:black'><o:p>

1.4</o:p>

</td>

<span style='font-family:Arial;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> 20

April 2004</o:p>

</td>

<span style='font-family:Arial;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> K

Schopmeyer</o:p>

</td>

<span style='font-family:Arial;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> Incorporate

review comments from third Review</o:p>

</td>

</tr>

<span style='font-size:9.0pt;font-family:Verdana;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> 1.5</o:p>

</td>

<span style='font-size:9.0pt;font-family:Verdana;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> 28 April

2004</o:p>

</td>

<span style='font-size:9.0pt;font-family:Verdana;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> K.

Schopmeyer</o:p>

</td>

<span style='font-size:9.0pt;font-family:Verdana;

mso-fareast-font-family:"Times New Roman";color:black'><o:p> Add

Bug 1400 to bug list.</o:p>

</td>

</tr>

</tbody>

</table>

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

width="100%"></div>

Abstract: This document defines the release notes for

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

detail, and provide additional information about this release

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="#Functionality_of_This_Release">OpenPegasus

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

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

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

<o:p> </o:p>

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

style='color:black'>

with DMTF Specifications</a></li>

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

<li> <a

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

Release

</div>

Abstract: This document defines the release notes that support

release 2.3.2 of the Pegasus platform.  This release notes document incorporates

the Pegasus version 2.3.0 and 2.3.1 release notes plus a delta for 2.3.2.  Comments made

to these release notes have also been incorporated.<span

style='font-size:9.0pt'><a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35"

target="_self">

</a>

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

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

style='color:black'>

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

</ol>

<h2>Availability 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 ZIP EXE) and TAR

formats. These can be downloaded from the <span

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

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

<li>OpenPegasus source RPMs on the OpenPegasus web

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

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

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

<li>The OpenPegasus CVS repository. The CVS tags

representing this release and subsequent snapshots that are

made available in the Pegasus CVS are defined on the

OpenPegasus CVS repository web page (see the <a

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

CVS

</div>

<o:p> </o:p>

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

<h2>Availability of the Release</h2>

This release is available as a source release in both ZIP and TAR formats.

The release can be downloaded from the OpenPegsaus Web

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

In addition, this release is available through Pegasus CVS. The CVS tag for the

snapshot representing this release is RELEASE_2_3_2-snapshot_1 and the

branch tag representing the current state of version 2_3_2 is

RELEASE_2_3_2-branch.  This branch defines the current released version of

the Pegasus major

release 2.3.  RELEASE_2_3_2-root defines the initial release point

where Pegasus 2.3 branched from the trunk..  This snapshot release and any

subsequent updates to version 2.3.2 will be announced on the web site and

the Pegasus mailing list.� Specific

additinal snapshots to this release will be marked in the CVS as

RELEASE_2_3_2-snapshot_x, where x is the number of the snapshot and these will correspond to equivalent

zip and tar files made available on the web site.

The instructions for acquiring the released code are on the WEB site.

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

tree.

The OpenPegasus project is currently not providing binary releases.

There may be additional point releases to the Pegasus 2.3 release and these

will be announced on the <a href="http://www.openpegasus.org">Pegasus web site</a>. <span

style='font-size:9.0pt'> <a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=47"

target="_self">

</a>

<h2>Functionality of This Release</h2>

The overall level of functionality in the Pegasus environment effective with

this release is as follows:

CIM Server

CIM Operations over HTTP support

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

list .5in'>Class Operations (getClass, <span

class=SpellE>deleteClass, modifyClass, <span

class=SpellE>enumerateClass, enumerateClassNames)

- Operational<a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=40"

target="_self"></a><o:p></o:p></li>

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

list .5in'>Qualifier Operations getQualifier, setQualifier, deleteQualifier)

- Operational</li>

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

list .5in'>Instance Operations (getInstance, <span

class=SpellE>deleteInstance, modifyInstance,

enumerateInstance, enumerateInstanceNames,

getProperty, setProperty)

-   Operational<o:p></o:p></li>

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

list .5in'>Association Operations (references, referencenames,

associators, associatornames)

- Operational <a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=43"

target="_self"></a><o:p></o:p></li>

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

list .5in'>Methods- Operational<span

style='font-size:9.0pt'><a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=44"

target="_self"></a><o:p></o:p></li>

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

list .5in'>Query operation (Not Operational) <o:p></o:p></li>

</ol>

<span

style='font-size:9.0pt'><a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=45"

target="_self">

</a><o:p></o:p>

Indications

Process indications are operational in the Server.  This includes support

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

indications and the CIMXML indication handler. The Pegasus server can be used as

an Indication client.  The Client indication  API support is complete,

but the interfaces are marked experimental for version 2.3 because

this is the first major release version of Pegasus in which these APIs were

available.

Query Language

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

filters.  However, the executeQuery operation

has not been implemented pending the availability of a standard DMTF Query

language.

Class Repository

XML based file/directory Class repository. All class and qualifier operations

access this repository.

Instance Repository

XML based file/directory Instance repository.  The instance repository

is used as the default repository unless a flag is set disabling this

repository for client operations.

Security

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

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

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

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

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

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

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

supported by OpenSSL.  Minimum level known

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

with 0.9.6k.  See <a

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

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

</ol>

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

WEB

Platform Management Functions

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

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

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

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

list .5in'>Daemon operation on all supported platforms<o:p>.</o:p></li>

</ol>

SLP Discovery<a name="comtag_61">

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

</a>SLP support is included but is conditionally compiled with the default to

the root of the Pegasus source tree.

not compile it.  This code can be enabled by setting the compile

</div>

environment variable PEGASUS_ENABLE_SLP. Note that this release differs from

2.3.1 in that the SLP functions have been completed and tested in an

<h2>OpenPegasus Functionality in 2.12

interoperable environment.� Also, the

Release</h2>

provider for the interop classes (CIM_ObjectManager,

OpenPegasus overall status by release is defined by  a <a

CIM_Namespace,

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

etc.) is enabled along with the SLP discovery.

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

If the SLP discovery is not enabled, these interop

site .  That web page shows the Pegasus users and developers

classes are also not available.

the status of the various features found in OpenPegasus using a

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

CMPI Provider Manager<o:p></o:p>

description of each feature.

OpenPegasus 2.12.1 is a Revision release.

Pegasus 2.3.2 includes as a compilable option a

new set of code that allows multiple provider managers and also a second

NOTE: OpenPegasus releases are categorized as follows:

provider manager for the CMPI C interfaces.

<ul>

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

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

class=GramE>see� <a

Major release includes major functionality change and 

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

incompatible behavior changes and/or incompatible public API

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

changes,

which is in review now within the WBEMSource

</li>

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

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

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

Release and includes new functionality but maintains behavior

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

and public API compatibility,

providers.

</li>

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

Today, the CMPI provider manager and interfaces are considered experimental

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

and are subject to change in future versions of Pegasus.

The CMPI provider manager, sample providers and the hooks into Pegasus are

all conditionally compiled with the environment variables ENABLE_CMPI_PROVIDER_MANAGER

and ENABLE_PROVIDERMANAGER_2. See PEP 144 for details.

</blockquote>

Providers

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

This includes providers in the following categories:

Internal (control) Providers

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

list .5in'>__Namespace provider - Serves the __Namespace class to allow

manipulation of namespaces.<a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=65"

target="_self"></a><o:p></o:p></li>

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

list .5in'>Subscription Classes Providers - These provide subscription,

filter, and indication handler processing.<o:p></o:p></li>

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

list .5in'>Provider registration Providers - This provide registration of

providers using the PG_Provider classes.<o:p></o:p></li>

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

list .5in'>ConfigProvider - Manages Pegasus <span

class=SpellE>configuraton information.<o:p></o:p></li>

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

list .5in'>UserAuthProvider - Manages password,

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

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

list .5in'>ShutdownProvider - Provides support

for Pegasus shutdown.<o:p></o:p></li>

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

list .5in'>Interop Provider - Supports many of

the DMTF Interop Schema Classes including <span

class=SpellE>CIM_Namespace, CIM_ObjectManager,

CIM_CommunicationMechanism, etc.. (Note that

this provider is part of the SLP work package so is not compiled as part

of the default compile. The environment variable PEGASUS_ENABLE_SLP must

be set to enable this option.)<o:p></o:p></li>

</ul>

The major areas of development including both enhancements and bug

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

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

PEP/BUG for each change defined below:

<font

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

of Major Changes for this Release

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

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

width="82%">

<tbody>

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

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

Version</th>

</tr>

<tr>

<td>Provider Lifecycle Indications

</td>

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

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

Generic Providers

Generic OperatingSystem provider. See the

directory src/Providers/generic.

Test/Sample Providers

See the directories src/Providers/TestProviders

1.2</a>

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

</td>

sample providers.

</tr>

Managed System Providers

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

ComputerSystem, DNSAdmin,

instances

DNSService, Operating System, Process, Processor. For

</td>

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

<td width="128"><a

the directory src/Providers/ManagedSystem

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

CIMOM Statistics Providers

IBMStatisticalData - This is an early version of

the work that became CIM_StatisticalData. It is

similar to CIM_StatisticalData and provides the same

data but the structure of the Classes is slightly different. This will be

standardized to the DMTF definition in a future version of Pegasus.

</blockquote>

CIM_Schema

The default CIM_Schema loaded with this release is

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

local classes defined for Pegasus.  These are visible in the Schemas

directory.   CIM 2.8� schema is

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

The mechanism to switch to the the 2.8 schema is via

environment variable: PEGASUS_CIM_SCHEMA = (See Config.mak).

export PEGASUS_CIM_SCHEMA=CIM28

NOTE: the CIM 2.5 schema is maintained in the

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

environment.

Pegasus MOF Compiler

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

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

repository (cimmofl).

The direct interface compiler is used primarily to provide an initial

class/instance repository. WARNING:

the use of cimmofl

to manipulate instances in the repository bypasses any provider that is

registered to serve these  instances and simply installs the instances in the

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

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

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

stopped and restarted in some cases.  Use of cimmofl in

general is discouraged and particularly  to manipulate

instances served by a registered providers (ex.

Provider registration). Use of <span

class=SpellE>cimmof rather that cimmofl

wherever possible.

Client Tools

Pegasus CIM Server Adminstration

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

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

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

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

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

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

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

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

authorization characteristics. Today this is authorizing users to

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

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

list .5in'>cimprovider - Manage information

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

</ol>

Information client tools

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

1.1</a>

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

</td>

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

</tr>

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

<tr>

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

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

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

</td>

information on the Dmain Name System (DNS)

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

configuration from CIM Classes. Note that the information generated is dependent

interop namespace

on the information available from providers and differs from system to

</td>

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

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

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

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

list .5in'>ipinfo - Generates a set of standard

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

information from the Network Schema.  Information generated varies by

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

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

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

information on the Operating System from CIM Classes. Note that the

information generated is dependent on the information available from

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

</ol>

Test support Tools

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

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

option on the Pegasus make files       

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

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

list .5in'>The Pegasus Test Suite (see the tests directory and the

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

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

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

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

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

list .5in'>wbemexec - Test tool that

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

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

list .5in'>CLI - Command line interface for Client commands.<o:p></o:p></li>

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

list .5in'>Benchmark Test - Introduced with Pegasus 2.3, a benchmark test

environment is not provided which includes both a client and provider component.

See src/clients/benchmarkTest for more

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

</ol>

Pegasus Interface APIs

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

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

available from the web site(<a

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

This 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 release 2.3 Well-behaved

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

compatible with Pegasus 2.3 without compilation.  There have been

extensions and new interfaces added for release 2.3 and these are shown as

experimental.   The Pegasus public

interfaces includes the following major functions

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

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

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

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

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

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

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

list .5in'>CIM Listener

(experimental for Pegasus 2.3.2)<o:p></o:p></li>

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

list .5in'>SLP Client (experimental for Pegasus 2.3.2)<o:p></o:p></li>

</ol>

<o:p> </o:p>

The APIs are documented in

1.1</a>

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

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

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

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 to

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

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

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

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

authenticates these credentials, verifying if the provided credentials have

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

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

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

WMI Mapper impersonates the user credentials provided

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

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

contain user credentials.

<a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=132"

target="_self">

</a>Supported Platforms

<a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=134"

target="_self">

</a>Each Pegasus release lists as supported 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

assure that the port is maintained 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, the Pegasus project cannot assure

operation. The supported platforms for Pegasus release 2.3.2 are:

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

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

Platform and OS<span

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

</td>

Compilers<span

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

</td>

</tr>

AIX 5.2<o:p></o:p>

</td>

VisualAge<span

style='color:black'> C++ Version 5.0.2.3<o:p></o:p>

</td>

</tr>

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

</td>

HP aC++

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

</td>

</tr>

PowerLinux<span

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

</td>

gcc<span

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

</td>

</tr>

zLinux<span

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

</td>

gcc<span

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

</td>

</tr>

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

</td>

gcc<span

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

</td>

</tr>

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

</td>

gcc<span

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

</td>

</tr>

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

</td>

Microsoft

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

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

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

</td>

</tr>

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

</td>

Microsoft

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

style='color:red'>7.1<span lang=NL style='color:black;mso-ansi-language:

NL'><o:p></o:p>

</td>

</tr>

</table>

<tr>

<td><a

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

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

href="http://publib.boulder.ibm.com/eserver/v1r1/en_US/index.html" target="_"> http://publib.boulder.ibm.com/eserver/v1r1/en_US/index.html.</a>

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

href="http://www.hp.com/large/infrastructure/management/wbem" target="_">http://www.hp.com/large/infrastructure/management/wbem</a>/.

<o:p> </o:p>

<h2>Conformance with DMTF Specifications</h2>

Pegasus tries to conform to the CIM specifications.  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 Pegasus 2.3.2, some of the differences include the following:

1. Provider Registration - Pegasus supports registration through a set of

Provider registration classes and does not support the DMTF defined Provider

Qualifier. See the readme for more information on provider registration.

2. Indications. Today Pegasus supports process indications but does not

include any specific support for lifecycle indications.

3. Interop Schema implementation differences.

Today Pegasus provides alternatives to some of the classes in the <span

class=SpellE>Interop Schema including CIM_StatisticalData.

Note that the CIM_ObjectManager and other similar

classes are only compiled with the SLP option.

4. Today Pegasus does not support the execQuery pending the availability of

a standard for the query language.  Pegasus is expected to support

execQuery in a future release with the new CQL query language and possibly WQL.

5. Instance qualifiers and class

qualifiers on some Operations -

The DMTF specifications are unclear regarding the inclusion of qualifiers on

CIM instances.  Some CIM Client implementations expect instances returned

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

(such as KEY qualifiers on properties).  Pegasus is based on the

interpretation that class-defined qualifiers are not included in instances, so

incompatibilities may exist with clients that rely on these qualifiers.<o:p></o:p>

<o:p> </o:p>

6. HTTP Chunking � Today the Pegasus

implementation defines itself as supporting HTTP 1.1 but does NOT support

chunking. This is a high priority for a future version.

7. CIM MOF compiler functions for instance aliasing - The

Pegasus compiler does not today support thi functions.  This function is

planned for a future version.

8. MultiRequest Oprations - Pegasus does not support the DMTF defined MultiRequest

Operation option.

9. LocalOnly option on some instance Operations - Because of

incompatible changes made between CIM Operation specification versions, the DMTF

has determined that there is confusion in the use of the LocalOnly parameter on

instance operations and the

results it will return.  The definition changed between version 1.0 and

version 1.1 of the CIM Operations

over HTTP Specification  so that the information provided to

the requestor may be different between a CIM Operations version 1.0 specification

implementation and a version 1.1 implementation.  Therefore, the Pegasus

community discourages the use of this parameter on any operations. NOTE:

We recommend that client users always set localOnly to False (remember that the

default is true) on instance

operations to avoid the confusion of different information from different CIM

Server implementations.

NOTE: This problem does not apply to the class

operations such as getClass, etc.

<h2>Changes in Release 2.3</h2>

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

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

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

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

functionality was completed for this release.

In general, the changes implemented for this release were:

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

list .5in'>

Introduction of platform globalization.</li>

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

list .5in'>

Introduction of a listener API.</li>

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

list .5in'>

Introduction of SLP (still experimental and by default not

compiled in the 2.3.2 release).</li>

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

list .5in'>

Introduction of a new pluggable Provider Manager (still

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

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

list .5in'>

Introduction of extensive changes to the HTTP monitor (still

experimental and not compiled in the 2.3.2 release).</li>

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

list .5in'>

Inclusion of Pluggable

CMPI provider manager.  Note: This makes use of the PPM item

described below.  This is an optional compile.</li>

</ol>

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

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

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

list .5in'>SLP integration - This code is in place but is compiled only

with a conditional compile flag. This code can be enabled by setting the

environment variable PEGASUS_SLP_ENABLE and recompiling Pegasus.<o:p></o:p></li>

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

list .5in'>Pluggable

provider manager - This was a major objective but because the code changes

were extensive and released very late in the development

cycle of 2.3, both the old and the new provider managers are maintained in

the release AND the old provider manager is defined as the default

compile.  To compile and run with the new pluggable provider manager

functions the user must set a compile flag (TBD).  NOTE: It is the

intention of the Pegasus project to move to the new provider manager as

soon as possible.<o:p></o:p></li>

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

list .5in'>HTTP Monitor enhancements - As with the Pluggable Provider

Manager, it was the intention to incorporate a number of enhancements to

the HTTP monitor.  Again because the time in the development phase

when they were submitted, the project team elected to release 2.3.2 with

the existing monitor as the default compile but with the code for both

monitors. It is the intention to move to the new monitor as soon as

possible and users are free to work with either implementation.  To

compile and run with the new monitor use the flag PEGASUS_MONITOR2.<o:p></o:p></li>

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

list .5in'>CMPI Pluggable Provider Mgr - The CMPI Provider manager was

added as a PEP to release 2.3.2 and uses the same flag as the Pluggable

provider manager to control its compilation. Without setting this flag before

the build process this provider manager and its sample providers are NOT

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

</ol>

The set of PEPs defined for release 2.3 is below

along with the final implementation status. Note that release 2.3.2 introduced no new <span

class=SpellE>PEPs beyond what was in release 2.3.0. All of these PEPS are

available on the OpenPegasus web site.

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

8891</a>

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

<td width="20%" style='width:20.26%;background:#00CC99;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

PEP #<span

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

</td>

<td width="46%" style='width:46.22%;background:#00CC99;padding:.75pt .75pt .75pt .75pt;

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

height:13.5pt'>

destinations and subscriptions

PEP Description<span

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

</td>

<td width="33%" style='width:33.2%;background:#00CC99;padding:.75pt .75pt .75pt .75pt;

<td>

height:13.5pt'>

Status<span

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

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

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

height:13.5pt'>

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

56<o:p></o:p>

5667</a>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

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

height:13.5pt'>

buildInstance and filter functions in CIMInstance class

Unicode Support in

Infrastructure<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

<o:p> </o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:13.5pt'>

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

58<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

8952</a></td>

Unicode Support in

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

Infrastructure<o:p></o:p>

<td>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

<a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=168"

target="_self">

</a><o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:13.5pt'>

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

68<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

8984</a></td>

Provider Manager Interface -

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

Multiple provider support<o:p></o:p>

<td>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Implemented - but requires

compile flag to integrate.<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:13.5pt'>

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

84<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

9008</a></td>

Provider Manager Interface,

<td>Add new Indication runtime configuration variables:

Pluggable provider manager configuration<o:p></o:p>

maxIndicaitonDeliveryRetry Attempts  and

</td>

minIndicationdeliveryRetryInterval</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>

height:13.5pt'>

Implemented - see above.<o:p></o:p>

</td>

</tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

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

height:13.5pt'>

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

86<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

9013</a>

Provider Manager Interface,

pluggable provider manager.<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

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

height:13.5pt'>

windowtext;">Enable ordered

Implemented - see above.<o:p></o:p>

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 width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

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

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

height:13.5pt'>

60<o:p></o:p>

</td>

9080 </a></td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

<td> Guaranteed provider

height:13.5pt'>

lifecycle indication delivery during CIMServer shutdown </td>

Secure connections between CIM

Listener and CIM server<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:13.5pt'>

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

62<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

9112</a>

SNMP Mapper

Indication Handler<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>Advertise IndicationService conformance to Indications

height:13.5pt'>

Profile by imlementing CIM_ElementConformsToProfile when

Implemented<o:p></o:p>

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td>

<td>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:13.5pt'>

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

67<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:13.5pt'>

9114</a>

Indication Consumer registration<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>Advertise DMTF Indications Profile (DSP1054) 1.1.0

height:13.5pt'>

conformance </td>

<o:p> </o:p>

<td>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:13.5pt'>

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

76<o:p></o:p>

9118</a>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

<td>Add support for CIM_IndicationFilter.SourceNamespaces[]

height:13.5pt'>

property

CIM Listener Client API,

Libraries, SDK<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>

height:13.5pt'>

Implemented - Experimental<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:10.5pt'>

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

75<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

9136</a></td>

Indication Subscription

<td>Runtime configuration option to restrict cimserver to

Performance Enhancements<o:p></o:p>

listen on selected network interfaces</td>

</td>

<td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:10.5pt'>

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

30<o:p></o:p>

9155</a>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

default schema

SLP support<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>

height:10.5pt'>

Implemented - Optional compile<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:10.5pt'>

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

52<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

9159</a></td>

Interop<span

<td>

style='color:black'> Schema provider support<o:p></o:p>

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

</td>

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

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

<tbody>

Implemented - Optional compile<o:p></o:p>

<tr>

<td>Add SSL Support to Dynamic Listener

</td>

</tr>

</tbody>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

</table>

height:10.5pt'>

88<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Polling design socket change.<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>

height:10.5pt'>

<o:p> </o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:10.5pt'>

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

64<o:p></o:p>

9172</a>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

<td>Add capability for administrator to override hostname

height:10.5pt'>

used by providers. This adds  new runtime

Java implementation of CIM

configuration variable hostname and

Client and Listener Interface<o:p></o:p>

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 width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>

height:10.5pt'>

Included in Pegasus based SNIA <span

class=SpellE>OpenCimom Java Classes.<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:10.5pt'>

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

65<o:p></o:p>

9215</a>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

in general. When the server receives  ExecQuery it

Benchmark test utility<o:p></o:p>

executes enumerate instance for providers that do not

support ExecQuery and filters result.

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>

height:10.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:10.5pt'>

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

74<o:p></o:p>

9209 </a>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

<td>Add operations for display class tree and counting

height:10.5pt'>

instances to cimcli

SSL certificate verification

callback enhancement<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>

height:10.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:10.5pt'>

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

73<o:p></o:p>

9227</a>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

<td>Enhance cimsub for batches of subscription oriented

height:10.5pt'>

operations

Support CIM Schema 2.8

preliminary<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>

height:10.5pt'>

<o:p> </o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:10.5pt'>

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

79<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

9229</a>

WMI Mapper

- local connection enhancements<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

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

<o:p> </o:p>

<td>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

<td><a

height:10.5pt'>

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

77<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

9236</a></td>

Default instance provider<o:p></o:p>

<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 width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>

height:10.5pt'>

Implemented<o:p></o:p>

</td>

</tr>

</tbody>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

</table>

height:10.5pt'>

The status of several components of Pegasus functionality

85<o:p></o:p>

change status between Pegasus versions. <a

</td>

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

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

identified by a change in color from the previous release to

height:10.5pt'>

this release</a> on the <a

Configuration Property Table

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

Enhancement<o:p></o:p>

Status WEB Page</a>.

</td>

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

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

OpenPegasus 2.12

height:10.5pt'>

</h3>

Implemented<o:p></o:p>

Prior to version 2.12 OpenPegasus used an OpenPegasus internal

</td>

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>Information on  IPv6 Support (PEP

291)</h3>

NOTE: This functionality was incorporated in OpenPegasus

2.7.0 but it was felt that the information below was worth

repeating in subsequent Release Notes

IPv6 is

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

generation" protocol designed by the IETF to replace the

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

Support for OpenPegasus is documented in <a

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

PEP 291</a>.

The IPv6 support in OpenPegasus is controlled by the

PEGASUS_ENABLE_IPV6 build variable. The default for this

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

OpenPegasus will disable the IPv6 support.

The following subsections provide some information on IPv6

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

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>

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

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

Version 6 Addressing Architecture</a> and <a

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

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

<h4>IPv6 on Linux</h4>

Modern Linux distributions already contain IPv6-ready kernels,

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

possible that this module is not loaded automatically on

startup.

Note: you

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

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

is no longer improved according to definitions in latest RFCs.

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

To check whether your current running kernel supports IPv6,

take a look into your /proc filesystem. The entry

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

like:

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

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

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

ready"</big></div>

For more information on enabling IPv6 in the Linux kernel and

configuring network interfaces, refer to <a

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

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

Warning: There is

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

seen intermittently on RHEL5 and SLES10 systems. This problem is

described in <a

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

bug

6586</a> and

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

bug

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

IPv6 socket failure. You should be aware that OpenPegasus with

IPv6 enabled may be significantly impacted in these

environments.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6 implementations for Windows

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

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

On Windows XP, you can use the ipv6.exe

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

example:

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

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

ipv6 if</big></div>

Windows Vista and Windows Server 2008 support an integrated

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

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

tested on Windows Vista or Windows Server 2008.

For more information on installing, configuring, and using IPv6

on Windows platforms, refer to the document <a

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

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

Questions</a>.

<h4>Testing  OpenPegasus IPv6 support</h4>

As part of the OpenPegasus automated tests, the TestClient,

g11ntest, and IndicationStressTest test clients were modified to

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

PEGASUS_ENABLE_IPV6=true.

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

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

IPv6 loopback on a system with OpenPegasus running on the WBEM

standard http port of 5988:

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

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

Considerations</a></h2>

Support for forward-compatibility is a fundamental design

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

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

the externally defined OpenPegasus interface, to continue to

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

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

standard that significantly affects interoperability) that may

require the community to make potentially incompatible changes.

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

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

upgrading to this OpenPegasus release.

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

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

width="80%">

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

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

</table>

height:10.5pt'>

<h2>OpenPegasus Relationship to CIM/WBEM Standards</h2>

90<o:p></o:p>

Pegasus was designed and implemented to comply with the DMTF

</td>

CIM/WBEM specifications The following table defines the level of

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

the DMTF specifications to which this version of Pegasus aims to

height:10.5pt'>

conform today.

Add

IO trace diagnostics to CIMClient<o:p></o:p>

<tbody>

</td>

<tr>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

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

Implemented<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

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

89<o:p></o:p>

</td>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

SLP Client Integration<o:p></o:p>

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

height:10.5pt'>

Implemented but not compiled by

default<o:p></o:p>

</td>

</tr>

<tr>

<td width="20%" style='width:20.26%;padding:.75pt .75pt .75pt .75pt;

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

height:10.5pt'>

<td width="33%">Version 1.2, Final, January 09, 2007</td>

<a

</tr>

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=306"

<tr>

target="_self">99</a><span

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

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

<td width="33%">Version 2.2 Final, January 09, 2007</td>

</td>

</tr>

<td width="46%" style='width:46.22%;padding:.75pt .75pt .75pt .75pt;

<tr>

height:10.5pt'>

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

<a

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

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=307"

</tr>

target="_self">Restructure of CIMRequest

<tr>

Message</a> <o:p></o:p>

<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%">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.31.0 Final ( default) </td>

</tr>

<tr>

<td>DSP0226 - Web Services for Management

</td>

<td width="33%" style='width:33.2%;padding:.75pt .75pt .75pt .75pt;

<td>Version 1.1.1

height:10.5pt'>

<a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=536&file=PEP098Pegasus2_3ReleaseNotes.htm&tag=308"

target="_self">Implemented but not compiled by

default</a> <o:p></o:p>

</td>

</tr>

<tr>

<td>DSP0227 - WS-Management CIM Binding Specification

102<o:p></o:p>

</td>

<td>Version 1.2.0

CMPI Pluggable Provider <o:p></o:p>

</td>

</tr>

Implemented but not compiled by

<tr>

default <o:p></o:p>

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

<td>Version 1.1.0

</td>

</tr>

</tbody>

</table>

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

<h2>PEGASUS Bugs</h2>

SMI Profiles Supported</h2>

Today OpenPegasus includes support for several DMTF profiles

The current bug list for Pegasus is openly available on the OpenPegasus web

including the ones defined below:

site.  As of the release of 2.3.2 release date, the following list

<ol>

represents what the Pegasus community feels are a subset of  open bugs with OpenPegasus

<li>DMTF ProfileRegistration Version 1.0.0</li>

2.3.2 that may be of particular interest to users. Please see the bug reports

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

(the number is a link to the report) to determine if there are any workarounds,

as the SNIA SMI Indication profile it also supports this

patches, etc. for particular bugs.

profile. This profile is enabled by compiling OpenPegasus with

the build variable PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

<o:p> </o:p>

</li>

<li>SNIA Profile Registration 1.0.0</li>

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

<li>SNIA Server 1.1.0 & 1.2.0

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

</li>

</ol>

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

<span

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

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

It is a major goal of the OpenPegasus project to both drive and

href="buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Pegasus+CLI+Commands&product=PegasusCIMOM&product=PegasusClient&product=PegasusCompiler&product=PegasusGeneral&product=PegasusJavaCIMClient&product=PegasusProvider&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&priority=P1&priority=P2&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&newqueryname=&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id">ID</a>

utilize the DMTF CIM/WBEM specifications.  However, today

<o:p></o:p>

there are a number of known differences.  As of this

</td>

release, some of the differences include the following:

<ol>

<span

<li>Provider Registration - Pegasus supports registration

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

through a set of Pegasus Provider registration classes rather

than support the DMTF defined Provider Qualifier. Pegasus will

class=SpellE>Sev</a> <o:p></o:p>

not support this qualifier in the future. See the readme for

</td>

more information on provider registration.  This is not a

deviation from the specifications but is a different method of

<span

registration than many CIM Servers and means that the the

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

provider qualifier is unused in Pegasus.</li>

<li>Lifecycle Indications -Today Pegasus supports

class=SpellE>Pri</a> <o:p></o:p>

process indications and lifecycle indications when defined

</td>

specifically by providers. Pegasus does not support lifecycle

indications if they are not defined by the provider or for

<span

changes to CIM Classes. <span

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

class="norm"> For more

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

class=SpellE>Plt</a> <o:p></o:p>

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

</td>

size="2">.</li>

<li>

<span

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

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

font-weight: bold;">IncludeQualifiers option on Instance

Operations

<o:p></o:p>

- The DMTF specifications have deprecated the use of

</td>

qualifiers on instance operations with the 1.2 CIM

</tr>

Operations Specification and stated specifically that the

client should NOT depend on the includeQualifiers

parameter of the CIM/XML instance operations returning

<a

qualifiers.  Some CIM Client implementations expect

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=14">14</a> <o:p></o:p>

instances returned from the CIM Server to include the

</td>

qualifiers defined in the class definition (such as KEY

qualifiers on properties).   Pegasus

nor

today expects the provider to complete the qualifiers on

<o:p></o:p>

instances in accordance with the specification and generally

</td>

the interpretation is that Pegasus applies class level

qualifiers when the includeInstance parameter is supplied on

P2

instance operations.  However, Pegasus today is

<o:p></o:p>

inconsistent in the return of qualifiers so that the user

</td>

should NOT depend on Pegasus accurately honoring the

includeQualifier parameter for instance operations.  In

All

the future it is expected that Pegasus will deprecate the

<o:p></o:p>

use of qualifiers on instance operations completely.

</td>

 When Pegasus uses object normalization, the normalizer

does apply qualifiers to returned instances if the

MOF

includeQualifiers operation parameter is set.

Compiler does not support aliasing <o:p></o:p>

</li>

</td>

<li>LocalOnly option on instance Operations - With the

</tr>

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

<a

incorrect, resulted in reduced functionality and introduced a

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=377">377</a> <o:p></o:p>

number of backward compatibility issues. As a result of issues

</td>

introduced by this change, we strongly recommend that CIM

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

<span style='mso-fareast-font-family:

this parameter to filter the set of set of properties

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

returned. See Appendix C of this specification for more

"Times New Roman"'> <o:p></o:p>

information.</li>

</td>

<li>

MultiRequest Operations - Pegasus

P2

does not support the DMTF defined MultiRequest Operation

<o:p></o:p>

option.

</td>

</li>

<li>

PC

MOF Compiler namespace pragma -

<o:p></o:p>

The Pegasus compiler does not support the namespace pragma.

</td>

</li>

<li>CIMOperation Trailer - Pegasus implements chunking

<span style='mso-fareast-font-family:

based on the DSP0200 1.2.0 preliminary spec. including the

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

operation trailer defined in that specification Refer to bug <a

"Times New Roman"'> not supported <o:p></o:p>

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

</td>

for more details. This trailer was completely removed from the

</tr>

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>

<a

<li>Whitespace in XML value

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=424">424</a> <o:p></o:p>

Element - Pegasus trims the leading and trailing

</td>

whitespace from XML value elements that are of the Type

String.  This behavior is documented in Pegasus bug <a

nor

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

<o:p></o:p>

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

</td>

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

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

P2

are some documented bugs in Pegasus such as this that the

<o:p></o:p>

OpenPegasus team feels cannot be incorporated into the code

</td>

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>

All

<li>modifyInstance operation

<o:p></o:p>

behavior in the Pegasus repository does not match the DMTF

</td>

specification. Under some conditions (ex. if no

propertyList is supplied) it modifies all properties rather

<span style='mso-fareast-font-family:

than just the properties supplied with the request thereby

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

Nulling out existing values. See bug <a

"Times New Roman"'> removes whitespace <o:p></o:p>

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

</td>

for more information.</li>

</tr>

<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

<a

during build by modifying a string definition in the code.

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=482">482</a> <o:p></o:p>

Effective version 2.12 this  has become a build option

</td>

with the build configuration environment variable

PEGASUS_INTEROP_NAMESPACE = <name for this namespace>

<span style='mso-fareast-font-family:

however, the default if built without this change is still

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

"root/PG_InterOp"

"Times New Roman"'> <o:p></o:p>

</li>

</td>

<li>OpenPegasus WSMAN protocol on windows does not handle

NaN, INF, or -INF (bug  <a

P2

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

<o:p></o:p>

- If requests or responses include properties or parameters

</td>

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

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

PC

input is not accepted because these special strings are not

<o:p></o:p>

understood by the decoder on Windows.</li>

</td>

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

Real32 and Real64 property and Parameter types for the

Absence

CIM/XML protocol - (bug <a

of REFERENCECLASSNAME in XML causes error <o:p></o:p>

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

</td>

</tr>

Today the DMTF Specification DSP0201 allows only numeric

<a

information in the format definition for this type and does

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=544">544</a> <o:p></o:p>

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

</td>

actually outputs the special strings if  that is what is

defined in the internal values.  OpenPegasus does not

<span style='mso-fareast-font-family:

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

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

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

"Times New Roman"'> <o:p></o:p>

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

</td>

Covered properties (properties which have the same name in a

superclass and subclass without overridding the property in

P2

the superclass) are not allowed in OpenPegasus. While the

<o:p></o:p>

requirement for this functionality was added to DSP0004

</td>

subsequent to version 2.4, the general agreement is that the

requirement itself is not supportable and particularly not

All

with the existing OpenPegasus APIs.  Further, the

<o:p></o:p>

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

</td>

3.0).

</li>

MOF

</ol>

compiler does not convert escape characters <o:p></o:p>

<h2>OpenPegasus <a

</td>

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

</tr>

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

<a

platform that will be willing to regularly document issues

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=786">786</a> <o:p></o:p>

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

</td>

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

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

nor

correct operation of  Pegasus cannot be assured.  In

<o:p></o:p>

all cases, including the active platforms, it is the

</td>

responsibility of the entity that packages and/or compiles

OpenPegasus for shipment or deployment, to read, and actively

P2

monitor the Pegasus Bugzilla database for a list of relevant

<o:p></o:p>

defects that affect their platform.   The platforms

</td>

that are considered ported are shown in the two tables

below.  The first table represents platform for which

PC

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

<o:p></o:p>

Nightly Build Test WEB Page. Those platforms which have been

</td>

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

of the release are reported in the second table.

<span style='mso-fareast-font-family:

Actively Supported Platforms (Nightly Tests Reported for this

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

release)

"Times New Roman"'> enumerateinstances <span

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

class=SpellE>deepInheritance, etc. procesing

cellpadding="0" cellspacing="1">

</td>

<tbody>

</tr>

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

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

<a

-moz-background-origin: initial;

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1054">1054</a> <o:p></o:p>

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

</td>

height="26">

Platform

nor

<o:p></o:p>

</td>

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

</td>

P2

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

<o:p></o:p>

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

</td>

-moz-background-origin: initial;

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

PC

height="26">

<o:p></o:p>

Compilers<span

</td>

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

</td>

<span style='mso-fareast-font-family:

</tr>

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

"Times New Roman"'> stop responding after stress query of repository <o:p></o:p>

</td>

HP-UX<o:p>

</tr>

PA_RISC and Itanium</o:p>

</td>

<a

HP <span

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1179">1179</a> <o:p></o:p>

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

</td>

</tr>

nor

<o:p></o:p>

</td>

<span

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

P2

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

<o:p></o:p>

</td>

<span

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

All

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

<o:p></o:p>

</td>

</tr>

Sample

providers should not be declared in Pegasus namespace <o:p></o:p>

<span

</td>

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

</tr>

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

</td>

<a

<span

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1195">1195</a> <o:p></o:p>

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

</td>

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

</td>

<span style='mso-fareast-font-family:

</tr>

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

"Times New Roman"'> <o:p></o:p>

</td>

Linux

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

P2

</td>

<o:p></o:p>

</td>

<span

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

All

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

<o:p></o:p>

</td>

</tr>

<span style='mso-fareast-font-family:

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

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

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

"Times New Roman"'> should clone CIM* objects before modifying

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

them

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

</td>

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

</tr>

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

experimental and is not part of the nightly tests

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

<a

</tr>

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1285">1285</a> <o:p></o:p>

</td>

Linux

nor

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

<o:p></o:p>

</td>

<span

P2

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

<o:p></o:p>

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

</td>

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

compiler usage is considered experimental and is not

PC

part of the nightly tests today)

<o:p></o:p>

</td>

</tr>

<tr>

<span style='mso-fareast-font-family:

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

"Times New Roman"'>EnumerateInstanceNames<span

and up</td>

style='mso-fareast-font-family:"Times New Roman"'> generates namespace error <span

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

class=SpellE>CIMException

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

</td>

</tr>

</tbody>

</table>

<span style='mso-fareast-font-family:"Times New Roman";

Platforms not Actively supported for this

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

release (No current Nightly Build Test Results

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

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

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

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

<tbody>

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

<a

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

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1307">1307</a> <o:p></o:p>

-moz-background-origin: initial;

</td>

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

height="26">

<span style='mso-fareast-font-family:

Platform

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

"Times New Roman"'> <o:p></o:p>

</td>

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

</td>

P2

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

<o:p></o:p>

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

</td>

-moz-background-origin: initial;

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

All

height="26">

<o:p></o:p>

Compilers<span

</td>

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

</td>

Functionality on errors with Enumerate Functions. Should we

</tr>

generate error or send existing data. Today we pass data.

<tr>

</td>

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

</tr>

Windows Vista, Windows 7, Windows Server 2008

</td>

<a

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

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1330">1330</a> <o:p></o:p>

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

</td>

6 no longer being regular tested.Note that today there

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

nor

</tr>

<o:p></o:p>

</td>

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

10.3 and higher</td>

P2

<o:p></o:p>

</tr>

</td>

<tr>

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

PC

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

<o:p></o:p>

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

</td>

2.95.3,  Sun CC compiler V 5.8. Note that the

latest thread patch (108993) may be required. (see

MOF compiler does not handle "/* ... */" comments.

Pegasus bug 4632)</big>

</td>

</tr>

<tr>

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

color="RED">Solaris

1400</a></td>

9</big></td>

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

maj</td>

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

</td>

P1</td>

</tr>

<tr>

All</td>

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

<td><big>HP

Disabling https prevents indication delivery through http.</td>

C++ V7.3-009

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

</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="padding: 0.75pt;"> Windows 2003

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

<font

<o:p></o:p>

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

platform patches Pegasus requires.

<h2>List of Bugs Corrected in Pegasus 2.3

</h2>

<ol>

<li>

The current bug list for Pegasus is openly available on the OpenPegasus web

<font

site bug database.  This site defines the mechanism so that the user can list the bugs

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

that have been fixed between the release of Pegasus 2.2 and the current release.

to fix Red Hat Bugzilla 98815.

</li>

<li>

<h2>Documentation</h2>

RHEL 4.4

multithreading bug in getpwuid-r could cause a CIM Server

The following documentation is available for the this Pegasus release:

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

</li>

<li>

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

Red Hat and

list .5in'>Pegasus Build and Installation - Readme in

SUSE Linux multiple versions - multithreaded client

the Pegasus Root Directory<o:p></o:p></li>

intermittently fails connecting to IPv6 (Pegasus Bugzilla

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

6586) (Red Hat bug 248052)

list .5in'>Pegasus Operation - Readme in the Pegasus

Root Directory<o:p></o:p></li>

</li>

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

</ol>

list .5in'>APIs - See the header files and the HTML  API documentation that is

</div>

on the web site. <o:p></o:p></li>

Further information regarding Pegasus support on IBM platforms

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

can be found at: <a

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

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

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

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>

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

list .5in'>API usage documentation - The best API usage documentation is

Further information regarding Pegasus support on HP platforms

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

can be found at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.

documentation.  In particular the

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

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

Defects</a></h2>

Common APIs.</li>

The OpenPegasus Bugzilla database documents any defects found

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

in Pegasus and  is available through the following

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

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

Directory, API documentation, and documentation from the Pegasus Technical

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

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

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

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

documentation on the Pegasus Technical Workshop which is available on the

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

Pegasus web site.</li>

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>

- Changes that were made in the minor

release 2.12 are in bugs Tagged 2.12.0_APPROVED. The link

is <a

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

Pegasus 2.12.0_APPROVED bug list.</a>

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

Documentation">Release Control and Version Definition

Documentation</a></h2>

The OpenPegasus project is controlled largely through the CVS

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

definition and review mechanism for new and modified Pegasus

functionality and for the definition and documentation of

releases.

The following documentation defines the characteristics of this

Pegasus release. The documents are available in the

OpenPegasus CVS repository.

<ul>

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

Section <a

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

2.12.x

Release Status</a>) - A

section in the Pegasus wiki is used throughout the

development of this version as the control point for

functionality that will go into the release and points to

all of the PEPs that represent the Pegasus 

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

OpenPegasus

Build and Configuration Options  for Selected Platforms

-  In previous

versions of Pegasus this information was  released as a

Pegasus PEP. Starting with Pegasus 2.9.0 the information is

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>

<o:p></o:p>

The following documentation is available for the this

Pegasus release:

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

style='color:black'>

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

</li>

A combination of help generally available with the --help

</div>

option for each command and HTML documentation for most of the

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

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

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

usage documentation - </li>

See the header files and the HTML  API documentation

Permission is hereby granted, free of

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

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

existing utilities and test programs and the examples in the API

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

documentation.  In particular the Common/tests unit tests

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

contain extensive examples of the use of the Common APIs.

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

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

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

Debugging Providers - </li>

following conditions:

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

documentation, and documentation from the Pegasus Technical

THE ABOVE COPYRIGHT NOTICE AND THIS

Workshop which is available on the Pegasus web site.

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

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

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

Debugging Clients - </li>

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

API documentation and the documentation on the Pegasus

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

Technical Workshop which is available on the Pegasus web site.

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

FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,

The features of Pegasus that have been installed in this and

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

the previous few versions are defined by Pegasus PEPs that are

THE USE OR OTHER DEALINGS IN THE SOFTWARE.

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

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

file except in compliance with the License.

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

obtaining a copy of this software and associated documentation

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

restriction, including without limitation the rights to use,

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

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

Software is furnished to do so, subject to the following

conditions:

The above copyright notice and this permission notice shall be

included in all copies or substantial portions of the Software.

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

EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT

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

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

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

OTHER DEALINGS IN THE SOFTWARE.

</div>

</body>

</html>

Legend:

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

No CVS admin address has been configured