pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

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

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 887

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 959

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>

<w:ApplyBreakingRules/>

</w:Compatibility>

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

</w:WordDocument>

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

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

style='color:black'>

</div>

Notes for OpenPegasus version 2.12.1

Created: 10

September 2012

Authors: Karl

<span

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

PEP #: 185

Title: Release Notes for OpenPegasus 2.4

Schopmeyer, Marek Szermutzky

Status:  draft

Version

History:

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

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

width="100%">

<tbody>

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

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

-moz-background-origin: initial;

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

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

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

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

</td>

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

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

-moz-background-origin: initial;

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

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

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

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

</td>

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

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

-moz-background-origin: initial;

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

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

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

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

</td>

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

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

-moz-background-origin: initial;

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

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

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

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

</td>

</tr>

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

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

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

</td>

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

align="center"> <span

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

</td>

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

align="center"> <font

size="2">Karl Schopmeyer

</td>

<span style="font-family: Arial;

color: black;">Initial Submission <span

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

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

</td>

</tr>

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

Version: 1.4

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

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

Authors: Karl

Szermutzky

Schopmeyer

</td>

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

Status:  draft

Release

</td>

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>

<o:p>

23 July 3004</o:p>

</td>

<span

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

</td>

Initial

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

</td>

</tr>

1.1</td>

26 August 2004</td>

KS</td>

Incorporate comments from 1.0</td>

</tr>

1.2</td>

6  October 2004</td>

KS</td>

Incorporate comments from Review of 1.1</td>

</tr>

1.3</td>

24 October 2004</td>

KS</td>

Update with comments from Version 1.2</td>

</tr>

1.4</td>

1 November 2004</td>

KS</td>

Comments from 1.3</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.4 of the Pegasus platform. <span

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

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

target="_self">

</a>

<div class=MsoNormal 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> Contents</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

<ol>

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

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

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

Standards</a></li>

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

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

Specifications</a></li>

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

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

<li>

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

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

</ol>

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

This release is available in a number of forms including:

<ul>

page</a>.</li>

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

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

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

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

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

versions.</li>

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

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

defined on the

OpenPegasus CVS repository web page (see the

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

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

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

snapshots page</a>.</li>

</ul>

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

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

WEB

The instructions for acquiring the released code are on the

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

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

tree.

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

RPMs: </a>

<ol>

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

</a></li>

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

</a></li>

<li>

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

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

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

the root of the Pegasus source tree.

</div>

<h2>OpenPegasus Functionality in 2.12

Release</h2>

OpenPegasus overall status by release is defined by  a <a

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

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

site .  That web page shows the Pegasus users and developers

the status of the various features found in OpenPegasus using a

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

description of each feature.

OpenPegasus 2.12.1 is a Revision release.

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

NOTE: OpenPegasus releases are categorized as follows:

<li><a name="comtag_59">After the build the rpms will be in

<ul>

the following locations: </a>

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

<a name="comtag_59">For RHEL3 - /usr/src/redhat/RPMS/[arch]/tog-pegasus-

Major release includes major functionality change and 

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

incompatible behavior changes and/or incompatible public API

changes,

<a name="comtag_59">For SLES9 - /usr/src/packages/RPMS/[arch]/tog-pegasus- 2.4.0-1.[arch].rpm /usr/src/packages/RPMS/[arch]/tog-pegasus-sdk-

</li>

2.4.01-.[arch].rpm</a>.</li>

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

</ol>

Release and includes new functionality but maintains behavior

and public API compatibility,

</li>

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

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

</ul>

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

<h2><a name="Functionality of This Release">Functionality of This Release</a></h2>

The overall level of functionality in the Pegasus environment effective with

this release is as follows:

<h3>CIM Server Functionality</h3>

1.2</a>

</td>

</tr>

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

instances

</td>

<td width="128"><a

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

The following paragraphs list the functions in this release.  All

functions are considered community tested and operational unless specifically

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

quality or completeness for production usage.  Interfaces that are

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

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

interfaces are conditionally compiled with special environment variables. PEP

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

conditionally compiled in this release.

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

1.1</a>

</td>

</tr>

<tr>

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

</td>

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

interop namespace

</td>

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

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

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

<ol>

<li>Class Operations (getClass, <span

class=SpellE>deleteClass, modifyClass, <span

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

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

<li>Instance Operations (getInstance, <span

class=SpellE>deleteInstance, modifyInstance,

enumerateInstance, enumerateInstanceNames,

getProperty, setProperty)</li>

<li>Association Operations (references, referencenames,

associators, associatornames)</li>

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

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

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

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

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

</ol>

</blockquote>

</div>

<h4>Indications</h4>

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

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.

<h4>Indication Listener</h4>

The generic components for a CIM

1.1</a>

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

</td>

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

</tr>

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

<tr>

indication listener in the Pegasus server.

<td><a

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

</blockquote>

8891</a>

</td>

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

destinations and subscriptions

</td>

<td>

</td>

</tr>

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

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

<h4>Query Language</h4>

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

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

been implemented in Pegasus 2.4 but is considered alpha quality.

<h4>Class Repository</h4>

5667</a>

</td>

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

buildInstance and filter functions in CIMInstance class

</td>

</td>

</tr>

<tr>

<td><a

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

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

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

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

repository functions are considered alpha level because they have only been

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

suite.

<h4>Instance Repository</h4>

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

8952</a></td>

instance  repository may be conditionally used as the default repository

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

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

<td>

to NOT use the instance repository as default).

</td>

</tr>

<tr>

<td><a

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

<h4>Server Security</h4>

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

list .5in'>Basic Authentication (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>

8984</a></td>

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

<td>

</td>

</tr>

<tr>

<td><a

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

<h4> Platform Management Functions</h4>

<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/service operation of the Pegasus CIM Server on all supported platforms<o:p>.</o:p></li>

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

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

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

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

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

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

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

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

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

data transfers and includes a mechanism for message support in mulitple

languages using the open source ICU libraries (<a href="http://oss.software.ibm.com/icu/">http://oss.software.ibm.com/icu/</a>). Note that this is still marked

experimental.</li>

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

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

use of this feature </li>

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

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

use of this feature</li>

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

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

- See PEP 130

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

</ol>

<h4>SLP Discovery</h4>

9008</a></td>

<td>Add new Indication runtime configuration variables:

maxIndicaitonDeliveryRetry Attempts  and

minIndicationdeliveryRetryInterval</td>

<td>

</td>

</tr>

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

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

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

environment variable PEGASUS_ENABLE_SLP.   Once compiled, SLP support

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

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

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

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

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

<h4>Provider Managers</h4>

Pegasus is designed to support multiple Provider Managers to allow multiple

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

Interface.  This section defines the additional provider managers available

with Pegasus 2.4.

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

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

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

class=GramE>see� <a

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

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

which is in review now within the WBEMSource

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

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

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

providers.

Today, the CMPI provider manager and interfaces are considered experimental

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

specification is released. Information on writing providers with the CMPI

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

above) and in the following documents (<a href="http://www-124.ibm.com/sblim/doc/CMPIandC++.pdf">http://www-124.ibm.com/sblim/doc/ProviderArchitecture.pdf

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

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

Pegasus source root directory.

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

Pegasus includes an experimental provider manager for Java provider

interfaces based on the SNIA provider interface definitions.  This provider

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

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

</blockquote>

<h3>Providers</h3>

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

This includes providers in the following categories:

<h4>Pegasus Internal Providers</h4>

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

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

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

and include support for the following classes:

<ul>

<li>DMTF Interop classes including __Namespace,  <span

class=SpellE>CIM_Namespace, CIM_ObjectManager,

CIM_CommunicationMechanism, and CIMOMStatistics.</li>

</ul>

<h4>Generic Providers</h4>

9013</a>

</td>

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

windowtext;">Enable ordered

indication delivery from provider through CIMServer when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE compile flag is set</td>

<td width="128"> <a

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

</td>

</tr>

<tr>

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

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

Generic OperatingSystem provider. See the

directory src/Providers/generic.

<h4>Test/Sample Providers</h4>

See the directories src/Providers/TestProviders

9080 </a></td>

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

<td> Guaranteed provider

sample providers.

lifecycle indication delivery during CIMServer shutdown </td>

<h4>Managed System Providers</h4>

</td>

</tr>

ComputerSystem, DNSAdmin,

<tr>

DNSService, Operating System, Process, Processor. For

<td><a

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

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

the directory src/Providers/ManagedSystem

<h4>SLP Provider</h4>

This provider acts as the definer of  SLP

information for SLP registration and also controls the Pegasus SLP Service

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

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

information today. (conditionally compiled today)

</blockquote>

<h3>CIM_Schema</h3>

The default CIM_Schema loaded with this release is

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

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

directory.   CIM 2.9 preliminary

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

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

The mechanism to install other schemas than the default is

defined in the mak/config.mak

NOTE: The CIM 2.5 schema is maintained in the

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

environment.

<h3>Pegasus MOF Compilers</h3>

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

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

repository (cimmofl).

The direct interface compiler is used primarily to provide an initial

class/instance repository. WARNING:

the use of cimmofl

to manipulate instances in the repository bypasses any provider that is

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

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

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

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

stopped and restarted in some cases.  Use of cimmofl in

general is discouraged and particularly  to manipulate

instances served by a registered providers (ex.

Provider registration). Use of <span

class=SpellE>cimmof rather that cimmofl is encouraged

wherever possible.

<h3>Client Tools</h3>

<h4>   Pegasus CIM Server Adminstration</h4>

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

<h4>Information client tools</h4>

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

9112</a>

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

</td>

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

<td>Advertise IndicationService conformance to Indications

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

Profile by imlementing CIM_ElementConformsToProfile when

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

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td>

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

<td>

information on the Domain Name System (DNS)

</td>

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

</tr>

on the information available from providers and differs from system to

<tr>

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

<td><a

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

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

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

information from the Network Schema.  Information generated varies by

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

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

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

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

information generated is dependent on the information available from

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

</ol>

<h4>Test support Tools</h4>

<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) these tests are defined throughout the

Pegasus source tree typically in "tests" directories.       

<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 pegasus/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 - A benchmark test

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

See src/clients/benchmarkTest for more

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

</ol>

<h3>Pegasus Interface APIs</h3>

9114</a>

</td>

<td>Advertise DMTF Indications Profile (DSP1054) 1.1.0

conformance </td>

<td>

</td>

</tr>

<tr>

<td><a

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

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

189

available from the web site(<a

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

That document is the authorative source for the list

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

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

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

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

compatible with this release without compilation.  There have been

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

experimental.   The Pegasus public

interfaces includes the following major functions

<li class=MsoNormal style='color:black;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>

</ol>

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

public SDK including:

9118</a>

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

</td>

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

<td>Add support for CIM_IndicationFilter.SourceNamespaces[]

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

property

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

</td>

extensions to the Client APIs</li>

<td>

</ol>

</td>

</tr>

<tr>

<td><a

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

<o:p> </o:p>

The APIs are documented in

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

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

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

<h3>WMI Mapper</h3>

The WBEM to WMI Mapper provides a way to access

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

to Microsoft WMI requests, executes the requests, converts the results 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.

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

Standards</a></h2>

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

level of the DMTF specifications which which Pegasus conforms today.

9136</a></td>

<tr>

<td>Runtime configuration option to restrict cimserver to

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

listen on selected network interfaces</td>

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

<td>

</tr>

</td>

<tr>

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

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

</tr>

<tr>

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

<td><a

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

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

9155</a>

</td>

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

default schema

</td>

<td>

</td>

</tr>

<tr>

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

<td><a

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

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

</tr>

9159</a></td>

<td>

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

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

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

<tbody>

<tr>

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

<td>Add SSL Support to Dynamic Listener

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

</td>

</tr>

<tr>

</tbody>

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

</table>

</td>

<td>

</td>

</tr>

<tr>

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

<td><a

<td width="33%">2.8 Final, June 2004</td>

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

</tr>

</table>

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

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 this Pegasus release are:

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

9172</a>

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

Platform and OS<span

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

</td>

<td>Add capability for administrator to override hostname

Compilers<span

used by providers. This adds  new runtime

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

configuration variable hostname and

fullyQualifiedHostName. It is necessary to upgrade

existing repositories using repupgrade utility when

upgrading from OpenPegasus less than 2.12.0 and reusing an

existing repository.

</td>

</tr>

<td>

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

</td>

HP aC++

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

</td>

</tr>

<tr>

<td><a

PowerLinux<span

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

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

</td>

gcc<span

9215</a>

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

</td>

</tr>

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

in general. When the server receives  ExecQuery it

executes enumerate instance for providers that do not

zLinux<span

support ExecQuery and filters result.

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

</td>

<td>

gcc<span

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

</td>

</tr>

<tr>

<td><a

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

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

</td>

gcc<span

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

9209 </a>

</td>

</tr>

<td>Add operations for display class tree and counting

instances to cimcli

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

</td>

<td>

gcc<span

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

</td>

</tr>

<tr>

<td><a

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

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

9227</a>

</td>

<td>Enhance cimsub for batches of subscription oriented

operations

</td>

<td>

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>

<tr>

<td><a

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

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

9229</a>

</td>

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

Microsoft

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

Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1<span lang=NL style='color:black;mso-ansi-language:

<td>

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

</td>

</tr>

<tr>

<td><a

Sun Solaris 9</td>

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

Sun workshop 6, update 2</td>

</tr>

MacOS version 10.2 and higher</td>

gcc 3.3</td>

</tr>

</table>

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/go/wbem">http://www.hp.com/go/wbem</a>.

<o:p> </o:p>

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

It is a major goal

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

specifications.  However, today there are a number of known differences. 

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

<ol>

<li>Provider Registration - Pegasus supports registration through a set of

Pegasus Provider registration classes rather than support the DMTF defined Provider

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

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

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

<li>

Instance qualifiers and class

9236</a></td>

qualifiers on some Operations -

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

The DMTF specifications are unclear regarding the inclusion of qualifiers on

version supports only X86 and X86_64 and requires clang

CIM instances.  Some CIM Client implementations expect instances returned

version 3 or greater.

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

</td>

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

<td>

accordance with the specification and generally the interpretation is that

</td>

Pegasus applies class level qualifiers when the includeInstance parameter is

</tr>

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

</tbody>

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

</table>

accurately honoring the includeQualifier parameter for instance operations. 

The status of several components of Pegasus functionality

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

change status between Pegasus versions. <a

on instance operations completely.

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

identified by a change in color from the previous release to

this release</a> on the <a

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

Status WEB Page</a>.

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

OpenPegasus 2.12

</h3>

Prior to version 2.12 OpenPegasus used an OpenPegasus internal

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

OpenPegasus namespace with no defined way to change this

variable.  Note that an unsupported method involving

editing one file and rebuilding OpenPegasus was defined as a

workaround in the <a

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

</li>

<li>

CIM MOF compiler function for instance aliasing - The

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

planned for a future version.

</li>

wiki faq</a>s.

<li>

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

MultiRequest Oprations - Pegasus does not support the DMTF defined MultiRequest

Operation option.

</li>

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

<li>

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

LocalOnly option on some instance Operations -

With the 1.1 version of Specification for CIM Operations over HTTP, the

definition of the LocalOnly parameter for the GetInstance and EnumerateInstances

operations was modified. This change was incorrect, resulted in reduced

functionality and introduced a number of backward compatibility issues. As a

result of issues introduced by this change, we strongly recommend that CIM

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

filter the set of set of properties returned.

</li>

<li>

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

6586</a> and

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

bug

</li>

</ol>

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

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

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

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

IPv6 socket failure. You should be aware that OpenPegasus with

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

IPv6 enabled may be significantly impacted in these

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

environments.

functionality was completed for this release.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6 implementations for Windows

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

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

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

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

list .5in'>

example:

Expansion of platform globalization.</li>

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

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

list .5in'>

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

Expansion of SLP support (still

ipv6 if</big></div>

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

Windows Vista and Windows Server 2008 support an integrated

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

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

list .5in'>

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

Inclusion of the Pluggable Provider   manager

tested on Windows Vista or Windows Server 2008.

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

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

For more information on installing, configuring, and using IPv6

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

on Windows platforms, refer to the document <a

list .5in'>

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

Inclusion of Pluggable

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

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

Questions</a>.

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

list .5in'>

<h4>Testing  OpenPegasus IPv6 support</h4>

Inclusion of the out-of-process

As part of the OpenPegasus automated tests, the TestClient,

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

g11ntest, and IndicationStressTest test clients were modified to

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

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

list .5in'>

PEGASUS_ENABLE_IPV6=true.

Addition of the binary repository

option. (Experimental)</li>

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

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

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

list .5in'>

IPv6 loopback on a system with OpenPegasus running on the WBEM

Addition of the shared namespace

standard http port of 5988:

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

namespaces. (Experimental)</li>

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

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

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

list .5in'>

Considerations</a></h2>

Refactoring of the HTTP monitor.</li>

Support for forward-compatibility is a fundamental design

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

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

list .5in'>

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

Addition of HTTP chunking.

the externally defined OpenPegasus interface, to continue to

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

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

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

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

</ol>

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

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

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

8830</a></td>

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

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

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

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

for operations.   The chunking code has been incorporated and the

properties from instances has been relieved. The server

Pegasus client and the Server HTTP components handle chunking.  The

will do the filtering at the protocol adapter level. To

components necessary to segment operation responses from the providers was not

avoid a negative impact on performance the

completed and will be included in a future version.</li>

CIMInstance::filter() and

</ol>

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

The complete set of PEPs defined for this release is

defined in PEP 97.

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

The current bug list for Pegasus is openly available on the

9369</a>

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

</td>

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

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

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

requires that the  cimserver be restarted to send the

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

enableIndication request to the providers. This issue has

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

existed starting with OpenPegasus 2.10 to the current

patches, etc. for particular bugs.

version. If the cimserver is not restarted the indication

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

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

</tr>

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

</tbody>

</table>

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

<span

Pegasus was designed and implemented to comply with the DMTF

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

CIM/WBEM specifications The following table defines the level of

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>

the DMTF specifications to which this version of Pegasus aims to

<o:p></o:p>

conform today.

</td>

<tbody>

<span

<tr>

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

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

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

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

</td>

<span

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

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

</td>

<span

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

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

</td>

<span

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

<o:p></o:p>

</td>

</tr>

<a

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

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

MOF

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

</td>

</tr>

<a

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

</td>

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

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

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

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

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

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

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

</td>

</tr>

<a

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

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

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

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

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

</td>

</tr>

<a

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

</td>

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

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

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

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

Absence

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

</td>

</tr>

<a

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

</td>

nor

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

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

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

"Times New Roman"'> enumerateinstances <span

class=SpellE>deepInheritance, etc. procesing

</td>

</tr>

<a

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

</td>

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

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

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

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

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

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

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

them

</td>

</tr>

<tr>

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

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

</tr>

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1285" style="color: blue; text-decoration: underline; text-underline: single">1285</a> <o:p></o:p>

<tr>

</td>

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

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

nor

</tr>

<o:p></o:p>

<tr>

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

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

</tr>

<tr>

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

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

</tr>

<tr>

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

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

</tr>

<tr>

<td width="33%">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>Version 1.1.1

P2

<o:p></o:p>

</td>

</tr>

PC

<tr>

<o:p></o:p>

<td>DSP0227 - WS-Management CIM Binding Specification

</td>

<td>Version 1.2.0

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

"Times New Roman"'>EnumerateInstanceNames<span

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

class=SpellE>CIMException

</td>

</tr>

<tr>

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

<td>Version 1.1.0

href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=1307" style="color: blue; text-decoration: underline; text-underline: single">1307</a> <o:p></o:p>

</td>

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

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

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

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

Functionality on errors with Enumerate Functions. Should we

generate error or send existing data. Today we pass data.

</td>

</tr>

</td>

</td>

</td>

</td>

</td>

</tr>

</tbody>

</table>

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

SMI Profiles Supported</h2>

Today OpenPegasus includes support for several DMTF profiles

including the ones defined below:

<ol>

<li>DMTF ProfileRegistration Version 1.0.0</li>

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

as the SNIA SMI Indication profile it also supports this

profile. This profile is enabled by compiling OpenPegasus with

the build variable PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

</li>

<li>SNIA Profile Registration 1.0.0</li>

<li>SNIA Server 1.1.0 & 1.2.0

</li>

</ol>

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

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

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

utilize the DMTF CIM/WBEM specifications.  However, today

there are a number of known differences.  As of this

release, some of the differences include the following:

<ol>

<li>Provider Registration - Pegasus supports registration

through a set of Pegasus Provider registration classes rather

than support the DMTF defined Provider Qualifier. Pegasus will

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

more information on provider registration.  This is not a

deviation from the specifications but is a different method of

registration than many CIM Servers and means that the the

provider qualifier is unused in Pegasus.</li>

<li>Lifecycle Indications -Today Pegasus supports

process indications and lifecycle indications when defined

specifically by providers. Pegasus does not support lifecycle

indications if they are not defined by the provider or for

changes to CIM Classes. <span

class="norm"> For more

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

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

size="2">.</li>

<li>

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

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

Operations

- The DMTF specifications have deprecated the use of

qualifiers on instance operations with the 1.2 CIM

Operations Specification and stated specifically that the

client should NOT depend on the includeQualifiers

parameter of the CIM/XML instance operations returning

qualifiers.  Some CIM Client implementations expect

instances returned from the CIM Server to include the

qualifiers defined in the class definition (such as KEY

qualifiers on properties).   Pegasus

today expects the provider to complete the qualifiers on

instances in accordance with the specification and generally

the interpretation is that Pegasus applies class level

qualifiers when the includeInstance parameter is supplied on

instance operations.  However, Pegasus today is

inconsistent in the return of qualifiers so that the user

should NOT depend on Pegasus accurately honoring the

includeQualifier parameter for instance operations.  In

the future it is expected that Pegasus will deprecate the

use of qualifiers on instance operations completely.

 When Pegasus uses object normalization, the normalizer

does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.

</li>

<li>LocalOnly option on instance Operations - With the

1.1 version of Specification for CIM Operations over HTTP, the

definition of the LocalOnly parameter for the GetInstance and

Enumerate Instances operations was modified. This change was

incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

introduced by this change, we strongly recommend that CIM

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

this parameter to filter the set of set of properties

returned. See Appendix C of this specification for more

information.</li>

<li>

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation

option.

</li>

<li>

MOF Compiler namespace pragma -

The Pegasus compiler does not support the namespace pragma.

</li>

<li>CIMOperation Trailer - Pegasus implements chunking

based on the DSP0200 1.2.0 preliminary spec. including the

operation trailer defined in that specification Refer to bug <a

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

for more details. This trailer was completely removed from the

DSP0200 1.2 final specification as a non-compatible change so

that if chunking is used Pegasus is returning a noncompliant

response to enumerate type requests. </li>

<li>Whitespace in XML value

Element - Pegasus trims the leading and trailing

whitespace from XML value elements that are of the Type

String.  This behavior is documented in Pegasus bug <a

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

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

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

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

are some documented bugs in Pegasus such as this that the

OpenPegasus team feels cannot be incorporated into the code

until a major version update.  These bugs are documented

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

<li>modifyInstance operation

behavior in the Pegasus repository does not match the DMTF

specification. Under some conditions (ex. if no

propertyList is supplied) it modifies all properties rather

than just the properties supplied with the request thereby

Nulling out existing values. See bug <a

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

for more information.</li>

<li>OpenPegasus Interop Namespace - The default interop

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

versions of OpenPegasus prior to 2.12.0 this could be changed

during build by modifying a string definition in the code.

Effective version 2.12 this  has become a build option

with the build configuration environment variable

PEGASUS_INTEROP_NAMESPACE = <name for this namespace>

however, the default if built without this change is still

"root/PG_InterOp"

</li>

<li>OpenPegasus WSMAN protocol on windows does not handle

NaN, INF, or -INF (bug  <a

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

- If requests or responses include properties or parameters

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

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

input is not accepted because these special strings are not

understood by the decoder on Windows.</li>

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

Real32 and Real64 property and Parameter types for the

CIM/XML protocol - (bug <a

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

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

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

<h2><a name="Bugs Corrected in This Release">Bugs

Corrected in This Release</a>

Today the DMTF Specification DSP0201 allows only numeric

</h2>

information in the format definition for this type and does

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

The current bug list for Pegasus is openly available on the

actually outputs the special strings if  that is what is

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

defined in the internal values.  OpenPegasus does not

database</a>.  The database can be searched for bugs fixed based on date

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

and Pegasus version.

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

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

Specifically the following Bugs which were listed in the release notes for

Covered properties (properties which have the same name in a

Pegasus 2.3.2 have been fixed.

superclass and subclass without overridding the property in

the superclass) are not allowed in OpenPegasus. While the

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

requirement for this functionality was added to DSP0004

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

subsequent to version 2.4, the general agreement is that the

requirement itself is not supportable and particularly not

with the existing OpenPegasus APIs.  Further, the

<span

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

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

3.0).

</li>

</ol>

<o:p></o:p>

<h2>OpenPegasus <a

</td>

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

Each OpenPegasus release lists as 'active'

<span

platforms those hardware/software platforms that have recognized

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

ports for the Pegasus code base including a maintainer for the

platform that will be willing to regularly document issues

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

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

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

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

correct operation of  Pegasus cannot be assured.  In

all cases, including the active platforms, it is the

responsibility of the entity that packages and/or compiles

OpenPegasus for shipment or deployment, to read, and actively

monitor the Pegasus Bugzilla database for a list of relevant

defects that affect their platform.   The platforms

that are considered ported are shown in the two tables

below.  The first table represents platform for which

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

Nightly Build Test WEB Page. Those platforms which have been

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

of the release are reported in the second table.

Actively Supported Platforms (Nightly Tests Reported for this

release)

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

cellpadding="0" cellspacing="1">

<tbody>

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

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

-moz-background-origin: initial;

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

height="26">

Platform

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

</td>

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

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

-moz-background-origin: initial;

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

height="26">

Compilers<span

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

</td>

</tr>

HP-UX<o:p>

PA_RISC and Itanium</o:p>

</td>

HP <span

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

</td>

</tr>

<span

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

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

</td>

<span

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

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

</td>

</tr>

<span

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

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

</td>

<span

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

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

</td>

</tr>

Linux

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

</td>

<span

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

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

</td>

</tr>

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

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

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

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

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

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

experimental and is not part of the nightly tests

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

</tr>

Linux

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

</td>

<span

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

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

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

compiler usage is considered experimental and is not

part of the nightly tests today)

</td>

</tr>

<span

<tr>

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

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

and up</td>

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

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

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

</tr>

</tbody>

</table>

Platforms not Actively supported for this

release (No current Nightly Build Test Results

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

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

<tbody>

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

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

-moz-background-origin: initial;

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

height="26">

Platform

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

</td>

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

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

-moz-background-origin: initial;

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

height="26">

Compilers<span

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

</td>

</tr>

<span

<tr>

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

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

Windows Vista, Windows 7, Windows Server 2008

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

</td>

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

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

6 no longer being regular tested.Note that today there

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

</tr>

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

10.3 and higher</td>

</tr>

<tr>

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

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

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

2.95.3,  Sun CC compiler V 5.8. Note that the

latest thread patch (108993) may be required. (see

Pegasus bug 4632)</big>

</td>

</tr>

<span

<tr>

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

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

color="RED">Solaris

9</big></td>

<o:p></o:p>

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

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

</td>

</tr>

<tr>

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

<td><big>HP

C++ V7.3-009

544</a>

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

</td>

</tr>

<tr>

maj

<td><big> HP OpenVMS 8.3

</td>

or later IA64</big></td>

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

P2

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

<o:p></o:p>

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

</td>

</tr>

<tr>

All

<o:p></o:p>

Windows

</td>

2000

</td>

MOF compiler does not convert escape characters

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

</td>

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

</tr>

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

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

</td>

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

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

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

</td>

P2

<o:p></o:p>

</td>

PC

<o:p></o:p>

</td>

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

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

</td>

</tr>

nor</td>

P2</td>

All</td>

Sample providers should not be declared in Pegasus namespace</td>

</tr>

nor</td>

nor</td>

PC</td>

MOF compiler does not handle "/* ... */" comments.</td>

</tr>

</td>

maj

<o:p></o:p>

</td>

P2

<o:p></o:p>

</td>

All

<o:p></o:p>

</td>

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

"Times New Roman"'>Disabling https prevents indication delivery through http. <o:p></o:p>

</td>

<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

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

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

platform patches Pegasus requires.

The Pegasus project is controlled largely through a set of documents (PEPs)

that serve as the definition and review mechanism for new and modified Pegasus

functionality and for the definition and documentation of releases.

Specifically the following PEPs define the characteristics of this Pegasus

release.

<ol>

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

<li>

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

<font

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

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

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

to fix Red Hat Bugzilla 98815.

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

</li>

directory).</li>

<li>

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

RHEL 4.4

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

multithreading bug in getpwuid-r could cause a CIM Server

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

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

2.4 functionality changes.</li>

</li>

<li>

Red Hat and

SUSE Linux multiple versions - multithreaded client

intermittently fails connecting to IPv6 (Pegasus Bugzilla

6586) (Red Hat bug 248052)

</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms

can be found at: <a

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

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

Further information regarding Pegasus support on HP platforms

can be found at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.

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

Defects</a></h2>

The OpenPegasus Bugzilla database documents any defects found

in Pegasus and  is available through the following

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

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

The following documentation is available for the this Pegasus release:

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

list .5in'>Utilities - A combination of help generally available with the

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

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

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

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

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

documentation.  In particular the

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

Common APIs.</li>

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

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

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

documentation on 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'>Compiler operation and commands - compiler help (cimmofl

-h)</li>

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

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

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

available on the OpenPegasus web site.  While these are the original

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

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

design and implementation of these features.</li>

</ul>

<o:p></o:p>

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

style='color:black'>

</div>

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

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

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

Corporation

documented through bugs.  Bugs reports are filed not only

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

Permission is hereby granted, free of

process of committing new code representing the work on PEPs

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

done for OpenPegasus 2.6 and all subsequent versions. 

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

Therefore, a search of the OpenPegasus Bugzilla base for bugs

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

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

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

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

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

following conditions:

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

2.6.1_APPROVED</a>, <a

THE ABOVE COPYRIGHT NOTICE AND THIS

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

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

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

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

OpenPegasus release.

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

- Changes between the 2.12.0 release

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

and 2.12.1 revision are defined in bugs tagged

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE

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

FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,

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

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

THE USE OR OTHER DEALINGS IN THE SOFTWARE.

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>

The following documentation is available for the this

Pegasus release:

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

</li>

A combination of help generally available with the --help

option for each command and HTML documentation for most of the

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

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

usage documentation - </li>

See the header files and the HTML  API documentation

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

existing utilities and test programs and the examples in the API

documentation.  In particular the Common/tests unit tests

contain extensive examples of the use of the Common APIs.

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

Debugging Providers - </li>

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

documentation, and documentation from the Pegasus Technical

Workshop which is available on the Pegasus web site.

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

Debugging Clients - </li>

API documentation and the documentation on the Pegasus

Technical Workshop which is available on the Pegasus web site.

The features of Pegasus that have been installed in this and

the previous few versions are defined by Pegasus PEPs that are

available on the OpenPegasus web site.  While these are the

original design documents largely and use in the process of

defining and approving the overall characteristics of new

functionality, they serve as a guide to the design and

implementation of these features.

</ul>

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

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.4
changed lines
	Added in v.1.19.2.1

No CVS admin address has been configured