pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

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

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

version 1.17.4.2, 2013/06/03 22:34:01

Line 1

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

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

<head>

<style>

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

</style>

Line 448

Line 449

margin:1.0in 1.25in 1.0in 1.25in;

mso-header-margin:.5in;

mso-footer-margin:.5in;

mso-paper-source:0;}

div.Section1

{page:Section1;}

Line 569

Line 571

text-indent:-.25in;}

@list l4:level7

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

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level8

Line 887

Line 890

text-indent:-.25in;}

@list l19

{mso-list-id:1902863286;

mso-list-template-ids:740079056;}

@list l19:level1

{mso-level-number-format:bullet;

Line 959

Line 963

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

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

<o:smarttagtype

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

<o:smarttagtype

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

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

<o:DocumentProperties>

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

<o:LastAuthor> </o:LastAuthor>

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

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

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

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

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

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

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

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

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

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

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

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

</o:DocumentProperties>

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

<w:WordDocument>

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

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

<w:Compatibility>

<w:ApplyBreakingRules/>

</w:Compatibility>

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

</w:WordDocument>

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

</head>

<body lang="EN-US" link="blue" vlink="blue"><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags"

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

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

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

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

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

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

style="color: black;">

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

<span

width="100%"></div>

style="font-size: 13.5pt; color: black;">OpenPegasus Enhancement

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

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

align="center">Pegasus

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

<span

style="color: black;">

PEP #: 230

PEP #: 364

Title: Release

Notes for OpenPegasus 2.5

Notes for OpenPegasus version 2.12.0

Version: 1.8

Created: 10

Created: <st1:date

September 2012

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

Authors: Warren

Authors: Karl

Grunbok, Karl Schopmeyer

Schopmeyer

Status:  draft

Version History:

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

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

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

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

<tbody>

<td

<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">

height="27">

<span

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

</td>

<td

<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">

height="27">

<span

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

</td>

<td

<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">

height="27">

<span

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

</td>

<td

<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">

height="27">

<span

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

</td>

</tr>

<span

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

</td>

<span

<font

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

size="2">10 September 2012

2005

</o:p>

</td>

<span

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

style="font-family: Arial;">Karl Schopmeyer

</o:p>

</td>

<span

<font

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

size="2">Initial Submission <o:p><font

Submission<o:p>

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

</o:p>

</td>

</tr>

<tr>

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

2012

</td>

<td style="padding: 0.75pt;" height="21" align="center">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">26, June 2005

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

2012

</td>

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

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

Schopmeyer

</td>

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

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

comments from first review

</td>

</tr>

<tr>

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

</td>

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

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

2012

</td>

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

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

Schopmeyer

</td>

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

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

security notes.

8830 (compatibility considerations) and bug 9172(repupgrade)

</td>

</tr>

</tr>

</tbody>

</table>

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

style="color: black;">

Abstract: This document defines the release notes for the 2.12.0

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.

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

style="color: black;">

<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

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

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

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

</ol>

<h2>Availability of this Release</h2>

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

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

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

of the Pegasus source tree.

</div>

<h2>OpenPegasus Functionality for This 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.0 is a major release, extending the previous Pegasus

release in selected areas as described in the Pegasus  PEP defining

this release .

NOTE: OpenPegasus releases are categorized as follows:

<ul>

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

release includes major functionality change and  incompatible

behavior changes and/or incompatible public API changes,

</li>

<li>Second number changes (ex 2.11.0 2.12.0) -  Minor 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>

ALL changes for each release are documented in the

OpenPegasus bug data base by tagging each bug(keyword field of

bug).  No change to Pegasus is committed with out this tag on the

bug. Changes for this minor release are  tagged 2.12.0_APPROVED.

All changes for this minor release can be viewed through  this link

to the OpenPegasus bugzilla <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.0_APPROVED">

Pegasus 2.12.0_APPROVED bug list. Bugs.  </a>Bugs marked as

enhancements can be reviewed through the this <a href="http://bugzilla.openpegasus.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=CIM+Server+Core&product=CIMClient+Application&product=CIMClient+DefaultCPlusPlus&product=CIMClient+Java-SNIA&product=CIMConsumer+DefaultCPlusPlus&product=CIMIndicationHandler&product=CIMListener+Dynamic&product=CIMListener+Standalone&product=CIMProvider+CMPI&product=CIMProvider+CMPIRemote&product=CIMProvider+DefaultCPlusPlus&product=CIMProvider+Instrumentation&product=CIMProvider+JMPI&product=CIMSchema&product=CIMServer+Administration&product=CIMServer+Administration+Command&product=CIMServer+Administration+Profiles&product=CIMServer+ProviderManagement&product=CIMServer+Repository&product=CIMServer+SLP&product=OpenPegasus+Build+System&product=OpenPegasus+Documentation&product=OpenPegasus+Security+Defects&product=OpenPegasusProject+Bugzilla&product=OpenPegasusProject+CVS&product=OpenPegasusProject+Website&product=PegasusCIMOM&product=PegasusGeneral&product=RPM+CIMServer&product=TestProduct&product=Unsupported&product=WMI+Mapper&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.12.0_APPROVED&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfield=[Bug+creation]&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_severity&type0-0-0=equals&value0-0-0=enhancement">link

to OpenPegasus bugzilla 2.12.0 enhancement bugs</a> .  Bugs fixed

for subsequent revision releases (ex. 2.12.1) would also be viewed

through corresponding Bugzilla tags for each revisions (ex

2.12.1_APPROVED).

The major areas of development including both enhancements and bug

fixes for this release  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 style="vertical-align: top;">1.3

<td>Provider Lifecycle Indications

</td>

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

<td style="text-align: center;"><a href="https://collaboration.opengroup.org/pegasus/pp/documents/25003/PEP360_PLI_Ver1_2.html">Ver

1.2</a>

</td>

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

</tr>

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

</td>

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

<td width="128"><a href="https://collaboration.opengroup.org/pegasus/pp/origrevdocuments/3195/PEP361_CIMCLIEmbeddedInstanceSupport.htm">Ver

1.1</a>

</td>

</tr>

<tr>

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

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

</td>

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

</td>

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

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

namespace

</td>

<td style="vertical-align: top;">More revisions based on Aug 26

<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

review in Architecture meeting

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

1.5</a>

</td>

</tr>

<tr>

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

<td align="left">PEP 358

</td>

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

<td>WSMan indication handling and subscription support

</td>

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

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

</td>

1.1</a>

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

version  (balloted version)

</td>

</tr>

<tr>

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

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

8891</a>

</td>

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

and subscriptions

</td>

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

<td>

</td>

</tr>

<td style="text-align: center;" align="left" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=5667">Bug

5667</a>

</td>

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

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

and filter functions in CIMInstance class

</td>

<td style="vertical-align: top;">additional comments from review

</td>

</tr>

<tr>

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

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

8952</a></td>

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

<td>

</td>

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

</tr>

<tr>

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

8984</a></td>

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

<td>

</td>

</tr>

<tr>

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

9008</a></td>

<td>Add new Indication runtime configuration variables:

maxIndicaitonDeliveryRetry Attempts  and

minIndicationdeliveryRetryInterval</td>

<td>

</td>

</tr>

<td style="text-align: center;" align="left" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9013">Bug

9013</a>

</td>

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

<td align="left" width="75%"><span

style="">Enable ordered indication delivery from

provider through CIMServer when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE compile flag is set</td>

</td>

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

</tr>

Provider security statement, and clarified Solaris support for 2.5

<tr>

<td style="text-align: center;" align="left"> <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8800">Bug

9080 </a></td>

<td> Guaranteed provider lifecycle

indication delivery during CIMServer shutdonw </td>

</td>

</tr>

<tr>

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

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

9112</a>

</td>

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

<td>Advertise IndicationService conformance to Indications Profileby

imlementing CIM_ElementConformsToProfile when

PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td>

<td>

</td>

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

</tr>

<tr>

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

9114</a>

</td>

<td style="vertical-align: top;">Clarified SLP enablement

<td>Advertise DMTF Indications Profile (DSP1054) 1.1.0 conformance </td>

Paragraph and correction of Power on Linux in platform table

<td>

</td>

</tr>

</tbody>

</table>

<o:p> </o:p>

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

style="color: black;">

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

width="100%"></div>

Abstract: This document defines the release notes for the 2.5

version of the Pegasus CIM Server. <span

style="font-size: 9pt;"><a

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

target="_self">

</a>

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

style="color: black;">

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

width="100%"></div>

<o:p> Contents

</o:p>

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

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

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

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

Documentation</a></li>

</ol>

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

style="color: black;"><a name="Availability_of_this_Release"></a>Availability

of this Release</h2>

This release is available in a number of forms including:

<ul>

<li>Source release in both ZIP and TAR formats. These can be

downloaded from the OpenPegasus Web

site at <a

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

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

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

also available that can be used to build binaries for most

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

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

subsequent snapshots that are made available in the Pegasus CVS are

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

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

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

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

snapshots page</a>.</li>

</ul>

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

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

WEB site</a>.

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

Pegasus source

tree.

Instructions for building the Linux RPMs: <span

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

</>

<ol>

<li>Download

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

<li>rpm

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

<li>

<span

class="norm">Build

the rpms:

</li>

</ol>

<table

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

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

<tbody>

<tr>

<td

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

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

9118</a>

<td

</td>

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

<td>Add support for CIM_IndicationFilter.SourceNamespaces[] property

</td>

<td>

</td>

</tr>

<tr>

<td style="vertical-align: top; text-align: center;">RHEL3

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

9136</a></td>

<td>Runtime configuration option to restrict cimserver to listen on

selected network interfaces</td>

<td>

</td>

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

class="norm">rpmbuild -bb /usr/src/redhat/SPECS/tog-pegasus-

2.5.0-1.spec</td>

</tr>

<tr>

<td style="vertical-align: top; text-align: center;">RHEL4

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

9155</a>

</td>

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

</td>

<td>

</td>

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

class="norm">rpmbuild -bb /usr/src/redhat/SPECS/tog-pegasus-

2.5.0-1.spec</td>

</tr>

<tr>

<td style="vertical-align: top; text-align: center;">SLES 9

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

9159</a></td>

<td>

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

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

<tbody>

<tr>

<td>Add SSL Support to Dynamic Listener

</td>

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

class="norm"> rpmbuild -bb /usr/src/packages/SPECS/tog-pegasus-

2.5.0-1.spe</td>

</tr>

</tbody>

</table>

</td>

<td>

</td>

<li style="font-weight: bold;">After

</tr>

the build the rpms will be in the

following locations:</li>

<table style="width: 100%; text-align: left;" border="1"

cellpadding="2" cellspacing="2">

<tbody>

<tr>

<td

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

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

9172</a>

</td>

<td>Add capability for administrator to override hostname used by

providers. This adds  new runtime configuration variable

hostname and fullyQualifiedHostName. It is necessary to upgrade

existing repositories using repupgrade utility when upgrading from

OpenPegasus less that 2.12.0 and reusing an existing repository.

</td>

<td

<td>

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

of RPMs after the build is complete

</td>

</tr>

<tr>

<td style="vertical-align: top; text-align: center;">RHEL3

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

9215</a>

</td>

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

general. When the server receives  ExecQuery it executes

enumerate instance for providers that do not support ExecQuery and

filters result.

</td>

<td>

</td>

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

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

2.5.0-1.[arch].rpm

/usr/src/redhat/RPMS/[arch]/tog-pegasus-sdk- 2.5.0-1.[arch].rpm.<span

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

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

class="norm">     </td>

</tr>

<tr>

<td style="vertical-align: top; text-align: center;">RHEL4

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

9209 </a>

</td>

<td>Add operations for display class tree and counting instances to

cimcli

</td>

<td>

</td>

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

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

2.5.0-1.[arch].rpm

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

</tr>

<tr>

<td style="vertical-align: top; text-align: center;">SLES9

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

9227</a>

</td>

<td>Enhance cimsub for batches of subscription oriented operations

</td>

<td>

</td>

</tr>

<tr>

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

9229</a>

</td>

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

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

<td>

</td>

</tr>

<tr>

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

9236</a></td>

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

supports only X86 and X86_64 and requires clang version 3 or

greater.

</td>

<td>

</td>

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

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

2.5.0-1.[arch].rpm

/usr/src/packages/RPMS/[arch]/tog-pegasus-sdk- 2.5.01-.[arch].rpm.</td>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality change status

</ol>

between Pegasus versions. <a name="comtag_116">Features

that

have

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

changed status can be identified by a change in color from the

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

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

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

Status WEB Page</a>.

This document shows the Pegasus users and developers the maturity of

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

the various features found in Pegasus using a simple color coded

OpenPegasus 2.12

key.  That document can be found here:  <a

</h3>

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

Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable

Maturity Link</a>

to define "root/PG_InterOp" as the name for the OpenPegasus namespace

with no defined way to change this variable.  Note that an

The overall level of functionality in the Pegasus environment

unsupported method involving editing one file and rebuilding OpenPegasus

effective with

was defined as a workaround in the <a href="%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus

this release is as follows:

wiki faq</a>s.

<h3>CIM Server Functionality</h3>

The following paragraphs list the functions in this release.

All functions are considered community tested and operational unless

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

not generally of the quality or completeness for production

usage.  Interfaces that are part of the Pegasus public

interface definitions but that the Pegasus team feels may change are

marked experimental. In many cases these features  and interfaces

are conditionally compiled with special environment variables. <a

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

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

style="text-decoration: underline;">PEP 200 </a>

provides more detailed information on how to enable

functionality that is conditionally compiled in this release.

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

<ol>

<li>Class Operations (getClass, <span

class="SpellE">deleteClass, modifyClass,

enumerateClass, enumerateClassNames)</li>

<li>Qualifier Operations (getQualifier, setQualifier,

deleteQualifier) </li>

<li>Instance Operations (getInstance, <span

class="SpellE">deleteInstance, modifyInstance,

enumerateInstance, <span

class="SpellE">enumerateInstanceNames, getProperty,

setProperty)</li>

<li>Association Operations (references, referencenames,

associators, associatornames)</li>

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

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

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

considered at alpha quality because it has only been contributor

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

</li>

</ol>

</blockquote>

</div>

<h4>Indications</h4>

<ul>

<li>Process indications - Process indications are operational in

the

Server.  This includes support

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

for

indications and the CIMXML indication handler.</li>

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

lifecycle indications (ie. those

classes of indications derived from CIM_ClassIndication and

CIM_InstIndication) can now be created. Pegasus 2.5 provides some

enablement for the generation of lifecycle indications. For more

details, refer to

</ul>

<h4>Indication Listener</h4>

The generic components for a CIM Listener and a

listener API are operational.  This includes the functions for

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

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

as an indication listener in the Pegasus server.

However, since the definition of a standard name for this namespace in

Pegasus 2.5

DMTF and SNIA specifications ("interop" or "root/interop" with "interop"

includes a new standalone listener that is separate

being the preferred alternative) the use of  "root/PG_InterOp" has

from the current standalone CIMListener and the ExportServer listener

become an issue.

in the CIM server.

The use model that this listener fits is the following:

<ul>

<li> The listener may be packaged as

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

another application. </li>

<li> Consumers

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

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

</ul>

<span

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

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

new "Dynamic Listener" provides a solution for the above use model. It

is essentially a lightweight, pluggable listener that

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

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

bypasses traditional registration procedures.  See <a

href="http://www.openpegasus.org/pp/protected/upreviews/20/1303/PEP195_CIMListenerEnhancementsv1_6.htm"><span

style="color: rgb(51, 51, 255); text-decoration: underline;">PEP 195</a> <span

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

details.

<h4>Object Normalization</h4>

The Object Normalizer is an entity introduced in Pegasus 2.4 that

ensures

objects delivered from providers are complete and accurate. Two major

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

Normalizer drops instances it considers bad, and 2) the Object

Normalizer code slows performance. These issues are now addressed by

moving the Object Normalizer from the Dispatcher to the Response

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

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

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

CIMOM/provider boundary.

Two new configuration properties were added to control object

normalization.

<ol>

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

normalization for provider objects.</li>

<li>excludeModulesFromNormalization (colon delimited list of

provider modules) - List the provider modules by name (as specified in

PG_ProviderModule.Name) to exclude from normalization. Keep in mind

that all objects managed by all providers will be excluded from

normalization if its module name appears in this list.

</li>

</ol>

<h4>Embedded Object support</h4>

Pegasus 2.5 now provides embedded object support. The proposed solution

is restricted to the following:

The only representation for embedded objects supported by this

PEP is CIM-XML.

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

internally to represent embedded objects. When externalized (via

CIM-XML) these objects will be converted to strings representing valid

INSTANCE or CLASS elements, in accordance with the CIM Infrastructure

Specification.  Embedded instances will also carry the

EmbeddedObject attribute with

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

</blockquote>

<h4>Query Language</h4>

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

used for filters and in 2.4 for execQuery.

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

Effective OpenPegasus 2.12.0 a new build variable has been

193, 205 combine to describe the function submitted.

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

<h4>Schema Repository</h4>

However, today OpenPegasus is committed to the single namespace defined

By default, Pegasus uses an XML-based

at build "(root/PG_InterOp", "interop", or "root/interop"). However, a

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

number of OpenPegasus  installations are committed to the

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

"root/PG_InterOp" name and must maintain their repositories through

updates of OpenPegasus. While we are working on this issue today (which

To use the binary encoding feature a new configuration

means that a running version of OpenPegasus must accept both the and new

properties was

names and not confuse clients, listeners or providers that would use

added:

either name) the OpenPegasus team did not complete that work for this

enableBinaryRepository (true|false) - Enables

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

disables binary repository.

solution.

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

NOTE: If you redefine the interop namespace name with

repository, the compressed repository

PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp" namespace

functionality has

will not connect with the updated version of OpenPegasus.

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

support

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

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

compression enabled records are always written compressed but both

compressed

and non-compressed records can be read allowing an easy migration path.

Note:  <span

class="norm">Note:

Users may experience an incompatibility moving a binary repository from

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

the ability to maintain compatibility with subsequent releases. (See

bugzilla 3642 for details.) <span

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

</div>

<h4>Compressed Repository</h4>

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

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

feature has been added for

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

the

repository to be as much as 50% smaller on disk. It uses an external

compression library (zlib) and has been tested with zlib 1.2.2. This

feature is

documented in PEP 214 and also in a Readme

(readme.compressed_repository). It is

considered experimental today because it is not in the automated tests.

Note

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

activiated for

automatic tests.

</div>

<h4>Instance Repository</h4>

The

Pegasus schema repository may also be configured to hold instance

data.  <font

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

repository

it was not designed as a

high volume data store.

<h4>Security Considerations

</h4>

<h3>Information on  IPv6 Support (PEP 291)</h3>

OpenPegasus 2.5 (and

NOTE: This functionality was incorporated in OpenPegasus 2.7.0

prior) contains several mechanisms to perform authorization, but none

but it was felt that the information below was worth repeating in

of these authorization checks are performed by default.

subsequent Release Notes

By registering any provider which fails to do appropriate authorization

IPv6 is short

checks, the consequences may include information leakage, data

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

corruption, or unintended elevation of privilege. Please ensure that

protocol designed by the IETF to replace the current version Internet

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

Protocol, IP Version 4 ("IPv4"). IPv6 Support for OpenPegasus is

your systems and data:

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

1. Only install/register providers which perform authorization

PEP 291</a>.

appropriate for your environment.

The IPv6 support in OpenPegasus is controlled by the

PEGASUS_ENABLE_IPV6 build variable. The default for this variable is

<div style="margin-left: 40px;"><font style="color: rgb(0, 0, 0);"

"true"; setting this to 'false' before building OpenPegasus will disable

color="RED">a. For providers, this may include registering to

the IPv6 support.

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

performing authorization checks within the provider.

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

your environment have performed sufficient authorization checks. Also,

monitor announcements of security defects in those providers and follow

the recommendations in those announcements as soon as possible.

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

you are shipping have performed appropriate authorization checks, and

relay announcements of discovered security defects to your users.

</div>

2. Restrict users with

access to Pegasus to a specific authorized user group of trusted

individuals.

3. Namespace authorization is also available.

For administration issues please refer to

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

<h4>Server Security</h4>

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

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

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

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

implemented in Pegasus using the OpenSSL

libraries. Pegasus does not provide the OpenSSL

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

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

is  0.9.6c .   This release of Pegasus was tested with

0.9.6k.  See <a

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

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

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

SSLv3

and TLSv1 by default. SSLv2 is

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

See<a

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

PEP 200</a> for details on

configuration.

</li>

</ol>

<h4>Client Security<span

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

Certificate management 

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

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

client verification support by providing a robust solution to managing

client certificates and certificate revocation lists via standard CIM

operations. It allows certificates to be associated with particular

system users for enhanced authorization capabilities.

CN/ Host

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

and are the responsibility of the client to implement on their

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

more details on client security.

Note: <span

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

certificate verification using Pegasus and/or SSL libraries as

appropriate. Consequences of not doing so include leakage of

authentication credentials to unauthorized parties.

<h4>Platform Management Functions</h4>

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

the defined configuration parameters (cimconfig) and server command

line options.<font

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

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

enableAuthentication to true can result in improper operation of the

SLP

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

Administrator should change the user that the service runs under from

the Local

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

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

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

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

with the exception of HP OpenVMS.

</o:p></li>

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

capture using the <font

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

the DMTF Interop model. This

function is considered alpha quality and conditionally compiled.

</li>

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

pluggable provider managers.  Provider managers are provided for

the Pegasus C++ provider interface, the CMPI C provider interface and

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

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

- Pegasus includes support for unicode data transfers and includes a

mechanism for message support in multiple languages using the open

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

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

<li class="MsoNormal" style="color: black;">Out-of-process

providers (Experimental) - See PEP 072 for more information on use of

this feature </li>

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

(Experimental) - See PEP 129 for more information on use of this feature</li>

<li class="MsoNormal" style="color: black;">Remote providers for

the CMPI provider interface (Experimental) - See PEP 130 for more

information on use of this feature</li>

</ol>

<h4>SLP Discovery</h4>

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

a platform basis. <a

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

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

enable or disable this code.  PEGASUS_DISABLE_SLP and

PEGASUS_ENABLE_SLP are the environment variables that control inclusion

of this feature.  Once compiled, SLP

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

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

generates SLP advertisements compatible with the DMTF slp template

specification. The SLP support also includes  extensions to the

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

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

public SDK).

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

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

<h4>Provider Managers</h4>

The following subsections provide some information on IPv6 support for

Pegasus is designed to support multiple Provider Managers to allow

the Linux and Windows platforms. Note that in the 2.6.1 release there is

multiple provider interfaces to the CIMOM.  The two default

no automatic run-time detection of IPv6 support on a platform by

provider managers are the Pegasus C++ Interface and Common

OpenPegasus. If you build with PEGASUS_ENABLE_IPV6=true, your platform

Manageability Programming Interface (CMPI) Interface.

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

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

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

Pegasus 2.5 includes

specified. If the required input is just an IP address (eg. no optional

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

or required port number), then the IPv6 address must be specified

result of a project by the IBM SBLIM team (see 

without brackets. For example, the OpenPegasus osinfo client (which

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

returns information about the OS running on a host system) takes

Manageability Programming Interface, which is an OpenGroup standard.

separate host and port options. In this case a host with an

The CMPI

IPv6-configured network interface would be specified as:

specification is available at:

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

standardized C level interface for creating providers that can be

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

current C++ providers.  <span

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

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

Pegasus 2.5.

Information on writing providers with the CMPI interface is available

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

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

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

Pegasus source root directory.

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

Pegasus includes an experimental provider manager for Java

provider interfaces based on the SNIA provider interface

definitions.  This provider manager is  considered alpha

quality and is not compiled in the default build.   See

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

</blockquote>

<h3>    Providers</h3>

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

to run out of process at

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

process space.

Administrators should check the providers to

ensure that the provider vendor

has made use of available authorization capability.

</div>

There are a number of providers available

in the Pegasus release.

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>CMPI Remote</h4>

Pegasus includes an experimental support for

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

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

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

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

and passes them on to CMPI style providers.

<h4>Generic Providers</h4>

Generic OperatingSystem provider. See

the

directory src/Providers/generic.

<h4>Test/Sample Providers</h4>

See the directories src/Providers/TestProviders

and src/Providers/Sample for more

information about test and

sample providers.

<h4>Managed System Providers</h4>

ComputerSystem, DNSAdmin,

DNSService, Operating System, Process,

Processor. For

more information on these providers see the documentation for each

provider in

the directory src/Providers/ManagedSystem

<h4>Server Statistics

</h4>

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

are implemented in this release. The statistics gathering is disabled

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

ModifyInstance operation on the singleton 'CIM_ObjectManager' instance

in the 'PG_InterOp' namespace to set the GatherStatisticalData property

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

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

from the Pegasus CVS repository.

<h4>

</h4>

<h4>SLP Provider</h4>

This provider acts as the definer of

SLP information for SLP registration and also controls the Pegasus SLP

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

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

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

</blockquote>

<h3>CIM_Schema</h3>

The default CIM_Schema loaded with this

release is

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

a number of

local classes defined for Pegasus.  These are defined in the

pegasus/Schemas

directory.   There are also a

number of older schema available in the CVS.

The mechanism to install other schemas than the default is defined

in the mak/config.mak

NOTE: The CIM 2.5 schema is

maintained in the

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

test

environment.

<h3>Pegasus MOF Compilers</h3>

Pegasus implements a MOF compiler that can operate either at the

client

interface to the Pegasus CIM Server (cimmof)

or directly interfacing with a CIM

repository (cimmofl).

The direct interface compiler is used primarily to provide an

initial

class/instance repository. WARNING:

the use of cimmofl

to manipulate instances in the repository bypasses any provider that is

registered to serve these  instances and simply installs the

instances in the

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

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

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

available until the server is stopped and restarted in some

cases.  Use of cimmofl in general is

discouraged and particularly  to manipulate

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

<h3>Client Tools</h3>

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font

Lightweight statistics are now implemented for

color="#000000">osinfo -h 3ffe:1:2:1 -p 5988</big></div>

the

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

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

including an optional port number, requires the IPv6 address to be

client,

delimited with brackets, for example:

and the

elapsed time spent on the network between client and server.

<h3>Pegasus CIM Server Administration</h3>

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

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

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

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

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

- Manage the CIM Server authorization characteristics. Today this is

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

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

- Manage information about the providers .</li>

</ol>

Server admin

note:

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

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

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

specified in the configuration.  The new order for determining the

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

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

values.

</div>

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

in /etc/services is used.

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

used.

</div>

<h3>Information client tools</h3>

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

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

- output classes and/or instance information from the Pegasus

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

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

- Generate a set of standard information on the Domain

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

information generated is dependent on the information available from

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

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

- Generates a set of standard information from the Network

Schema.  Information generated varies by system because of the

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

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

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

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

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

</ol>

<h3>Test support Tools</h3>

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

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

tests are defined throughout the Pegasus source tree typically in

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

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

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

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

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

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

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

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

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

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

benchmark test environment is provided which includes both a client and

provider component. See src/clients/benchmarkTest

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

</ol>

<h3>Pegasus Interface APIs</h3>

Details of the Pegasus public interfaces for this release are listed

in PEP 209

available from the web site(<a

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

That document is the authorative source

for the list of publicly supported Pegasus APIs.   The Client

and Provider API were originally frozen at the Pegasus version 2.1

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

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

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

release without compilation.  There have been extensions and new

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

  The Pegasus public

interfaces includes the following major functions

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

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

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

function APIs</li>

</ol>

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

in the public SDK including:

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

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

<li class="MsoNormal">CIM Listener

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

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

running or a physical separation between the indication listener and

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

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

style="color: rgb(0, 0, 0);">Enhancements were deemed significant

enough to propose a new listener that builds off CIMListener's

basic capabilities, yet allows the existing CIMListener to remain the

same.</li>

<ul>

<li>New CIM Listener now provides selective

indication delivery.

</li>

<li>New CIM Listener

keeps all consumer libraries in memory for the duration of its

execution.

</li>

<li>New CIM Listener

is now pluggable.

</li>

<li>New CIM Listener

now provides reliable indication delivery.</li>

</ul>

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

Client (User Agent) APIs which are extensions to the Client APIs</li>

</ol>

<o:p> </o:p>

The APIs are

documented in

their respective header files and  in HTML documentation based on

the information

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

the

OpenPegasus web site.

<o:p></o:p>

<h3>WMI Mapper</h3>

The WBEM to WMI Mapper provides a way

to access

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

requests

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

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

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

XML

message and extracts from the HTTP message header the user credentials

provided

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

authenticates these credentials, verifying if the provided credentials

have

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

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

account with

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

this, the

WMI Mapper impersonates the user

credentials provided

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

browse WMI

data. Hence, ALL requests made to the WMI Mapper

MUST

contain user credentials.

<h3>Indication Handlers</h3>

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

System Log Indication Handler

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

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

or

for 2.5

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

type of Indication Handler which allows CIM Indications to be delivered

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

to the system syslog file. It has following features:

</div>

<ul>

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

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

</ul>

<ul>

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

list of the filter condition for the indication, the PerceivedSeverity

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

severity 'LOG_INFO' is used.</li>

<li>See <a

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

206</a> for details.

</li>

</ul>

Email Indicaiton Handler

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

for 2.5

type of Indication Handler that allows CIM Indications to be delivered

to a specified e-mail address.   See <a

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

207</a>  for details.

</div>

<ol>

For more information on specifying IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF

</ol>

RFC

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

2373 - IP Version 6 Addressing Architecture</a> and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF

CIM/WBEM Standards</h2>

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

Pegasus was designed and implemented to comply with the DMTF

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

color="#000000">test -f /proc/net/if_inet6 && echo "Running

kernel is IPv6 ready"</big></div>

For more information on enabling IPv6 in the Linux kernel and

configuring network interfaces, refer to <a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The

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

Warning: There is currently an

open issue with RedHat to address a problem that is seen intermittently

on RHEL5 and SLES10 systems. This problem is described in

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

bug

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

bug

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

socket failure. You should be aware that OpenPegasus with IPv6 enabled

may be significantly impacted in these environments.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6 implementations for Windows Server

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

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

On Windows XP, you can use the ipv6.exe

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

example:

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font

color="#000000">ipv6 install

ipv6 if</big></div>

Windows Vista and Windows Server 2008 support an integrated IPv4 and

IPv6 implementation known as the Next Generation TCP/IP stack. Note that

the OpenPegasus IPv6 support has not yet been tested on Windows Vista or

Windows Server 2008.

For more information on installing, configuring, and using IPv6 on

Windows platforms, refer to the document <a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"><font

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

Questions</a>.

<h4>Testing  OpenPegasus IPv6 support</h4>

As part of the OpenPegasus automated tests, the TestClient, g11ntest, and

IndicationStressTest test clients were modified to run tests using the

IPv6 loopback address (::1) if PEGASUS_ENABLE_IPV6=true.

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

IPv6-configured network interface. For example, using the IPv6 loopback on

a system with OpenPegasus running on the WBEM standard http port of 5988:

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

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

Support for forward-compatibility is a fundamental design principle for

the OpenPegasus project. As a community, our goal is for well-behaved

OpenPegasus providers or clients, using only the externally defined

OpenPegasus interface, to continue to work with a minor version upgrade

of OpenPegasus. However, there are certain classes of errors (e.g.,

non-compliance with a standard that significantly affects

interoperability) that may require the community to make potentially

incompatible changes. The following table contains a list of

defects/fixes that MAY impact, even well-behaved, OpenPegasus providers

or clients when upgrading to this OpenPegasus release.

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

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

<tbody>

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

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

</tr>

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

8830</a></td>

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

for providers (CMPI and C++) to filter properties from instances

has been relieved. The server will do the filtering at the

protocol adapter level. To avoid a negative impact on performance

the CIMInstance::filter() and CMPIInstanceFT.setPropertyFilter()

functions have been changed to a NOP. This may be a change in

behavior for provider relying in some unknown way on the instance

being filtered through these functions. To allow users to actually

filter properties from an instance, new function

CIMInstance::filterInstance() will actually filter properties from

an instance exactly as the CIMInstance::filter() did in previous

versions of Pegasus.</td>

</tr>

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

9369</a>

</td>

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

that the  cimserver be restarted to send the enableIndication

request to the providers. This issue has existed starting with

OpenPegasus 2.10 to the current version. If the cimserver is not

restarted the indication will not be enabled for the reregistered

provider. </td>

</tr>

</tbody>

</table>

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

Pegasus was designed and implemented to comply with the DMTF CIM/WBEM

specifications The following table defines the level of the DMTF

specifications which which Pegasus conforms today.

specifications to which this version of Pegasus aims to conform today.

<tbody>

<tr>

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

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

</tr>

<tr>

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

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

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

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

</tr>

<tr>

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

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

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

</tr>

<tr>

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

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

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

</tr>

<tr>

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

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

</tr>

<tr>

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

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

</tr>

<tr>

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

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

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

</tr>

<tr>

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

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

<td width="33%">2.31.0 Final ( default) </td>

</tr>

<tr>

<td>DSP0226 - Web Services for Management

</td>

<td>Version 1.1.1

</td>

</tr>

<tr>

<td>DSP0227 - WS-Management CIM Binding Specification

</td>

<td>Version 1.2.0

</td>

</tr>

<tr>

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

<td>Version 1.1.0

</td>

</tr>

</tbody>

</table>

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

<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIS 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 buld 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.

For more

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

pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a><font

size="2">.</li>

<li>

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 configuraton

environment variable PEGASUS_INTEROP_NAMESPACE = <name for this

namespace> however, the default if built without this change is

still "root/PG_InterOp"

</li>

<li>OpenPegasus WSMAN protocol on windows does not handle NaN, INF,

or -INF (bug  <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>)

- If requests or responses include properties or parameters with

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

states NaN, INF, or -INF on a Windows platform, the input is not

accepted because these special strings are not understood by the

decoder on Windows.</li>

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

Real64 property and Parameter types for the CIM/XML protocol -

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

Today the DMTF Specification DSP0201 allows only numeric information

in the format definition for this type and does not all the special

strings Nan, etc. However, OpenPegasus actually outputs the special

strings if  that is what is defined in the internal values. 

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

<li>OpenPegasus does not handle covered properties - (bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">3571</a>)

Covered properties (properties which have the same name in a

superclass and subclass without overridding the property in the

superclass) are not allowed in OpenPegasus. While the requirement for

this functionality was added to DSP0004 subsequent to version 2.4, the

general agreement is that the requirement itself is not supportable

and particularly not with the existing OpenPegasus APIs. 

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

CIM 3.0).

</li>

</ol>

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

Platforms</a></h2>

Each Pegasus release lists as 'active' platforms those

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus

code

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

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

to regularly document issues and/or fix defects as the Pegasus code base

regularly document issues and/or fix defects as the Pegasus

is changed.  Pegasus may be operable on other platforms (ex.

code base is changed. 

Windows 98) but without a group to provide the role of test and

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

maintenance, correct operation of  Pegasus cannot be assured. 

a group

In all cases, including the active platforms, it is the responsibility

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

of the entity that packages and/or compiles OpenPegasus for shipment or

Pegasus cannot be

deployment, to read, and actively monitor the Pegasus Bugzilla database

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

for a list of relevant defects that affect their platform.  

responsibility of the entity that packages and/or compiles OpenPegasus

The platforms that are considered ported are shown in the two tables

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

below.  The first table represents platform for which testing is

bugzilla database for a list of relevant defects that affect their

done on a regular basis and reported to the Pegasus Nightly Build Test

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

WEB Page. Those platforms which have been ported but do not have test

Pegasus release are:

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: 302.25pt;" border="1"

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

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

cellspacing="1">

<tbody>

<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: 240px;"

style="padding: 0.75pt; background: rgb(153, 255, 153) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 126.75pt;"

height="26">

height="26" width="211">

Platform and

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

</td>

<td

height="26">

height="26" width="289">

Compilers<span

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

</td>

</tr>

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

width="211">

HP-UX<o:p>

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

PA_RISC and Itanium</o:p>

</td>

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

width="289">

HP aC++

HP <span

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

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

</td>

</tr>

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

width="211">

Linux

<span

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

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

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

</td>

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

width="289">

gcc<span

<span

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

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

</td>

</tr>

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

width="211">

zLinux<span

<span

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

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

</td>

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

gcc<span

width="289">

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

<span

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

</td>

</tr>

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

width="211">

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

</td>

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

width="289">

gcc<span

<span

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

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

</td>

</tr>

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

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

width="211">

IA-32</td>

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

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

</td>

size="3">gcc<font

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

size="3"> (versions 3.xx, 4.xx) clang(The clang compiler usage

width="289">

is considered experimental and is not part of the nightly

<span

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

style="color: black;">gcc

</tr>

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

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

</td>

gcc<span

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

size="3">clang(The clang compiler usage is considered

experimental and is not part of the nightly tests today)

</td>

</tr>

<tr>

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

Version 1.7 and up</td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this release (No

current Nightly Build Test Results

<table class="MsoNormalTable" style="width: 90%;" id="table2" border="1" cellpadding="0"

cellspacing="1">

<tbody>

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

width="211">

height="26">

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

Platform and

</td>

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

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

</td>

width="289">

Microsoft

height="26">

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

Compilers<span

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

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

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

</td>

</tr>

<tr>

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

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

width="211">

Vista, Windows 7, Windows Server 2008

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

</td>

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

width="289">

Microsoft

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

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

</td>

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

Compilers 2003 - 2010.. Note: Visual C++ Ver. 6 no longer being

regular tested.Note that today there are some open issues with

the Windows. </td>

</tr>

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

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

width="211"> MacOS version 10.2 and higher</td>

higher</td>

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

width="289"> gcc 3.3</td>

</tr>

<tr>

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

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

</big></td>

8</big></td>

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

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

style="color: rgb(0, 0, 0);" color="RED">HP C++ V6.5-042 for OpenVMS

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

Alpha and above</big> </td>

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

</td>

</tr>

<tr>

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

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

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

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

color="RED">Solaris 9</big></td>

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

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

</td>

</tr>

<tr>

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

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

color="RED">Solaris 8

<td><big>HP C++ V<span

* See below for additional info

style="color: rgb(153, 51, 153);">7.3-009 or later required

</big></td>

for OpenVMS Alpha</big></td>

</tr>

<tr>

<td><big> HP OpenVMS 8.3 or later

IA64</big></td>

<td><big>HP C++ V7.3-023

or later required on

OpenVMS IA64</big></td>

</tr>

<tr>

Windows 2000

</td>

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

Ver.  6 and Microsoft .Net compiler version. Works on

VC .NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being

regularly tested.</td>

</tr>

<tr>

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

</td>

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

Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++

Ver. 6 no longer being regular tested. </td>

</tr>

<tr>

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

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

</tr>

</tbody>

</table>

Platform patches

Solaris:  Solaris testing

The

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

following is a list known of platform patches Pegasus requires.

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

platform, changes documented in OpenPegasus Bugzilla 4179  must be

applied.

<h2>Platform patches</h2>

The following is a list of platform

patches Pegasus requires.

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

2.1 needs the update to fix Red Hat Bugzilla 98815.

</div>

Further information regarding Pegasus support on IBM platforms can

found at: <a

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

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

Further information regarding Pegasus support on HP platforms can 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>

<font

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

option on Instance Operations

The DMTF specifications are unclear regarding the inclusion of

qualifiers on

CIM instances.  Some CIM Client implementations expect instances

returned

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

definition (such as KEY qualifiers on properties).   Pegasus

today expects the provider to complete the qualifiers on instances in

accordance with the specification and generally the interpretation is

that Pegasus applies class level qualifiers when the includeInstance

parameter is supplied on instance operations.  However, Pegasus

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

should NOT depend on Pegasus accurately honoring the includeQualifier

parameter for instance operations.  In the future it is expected

that Pegasus will deprecate the use of qualifiers on instance

operations completely.

</li>

<li>LocalOnly option on instance

Operations - With the 1.1 version of Specification for CIM

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

GetInstance and EnumerateInstances operations was modified. This change

was incorrect, resulted in reduced functionality and introduced a

number of backward compatibility issues. As a result of issues

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

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

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

<li>

CIM MOF compiler function for

RHAS

instance aliasing - The Pegasus MOF compiler does not today support

2.1

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

needs the update to fix Red Hat Bugzilla 98815.

</li>

<li>

MultiRequest Oprations - Pegasus

RHEL 4.4

does not support the DMTF defined MultiRequest Operation option.

multithreading bug in getpwuid-r could cause a CIM Server failure

(Bugzilla 6232). This is fixed in RHEL 4.5

</li>

<li>

MOFCompiler namespace pragma - The

Red Hat and SUSE

Pegasus compiler does not support the namespace pragma.

Linux multiple versions - multithreaded client intermittently

</li>

fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red Hat bug

</ol>

248052)

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

The development and release of each version of Pegasus is defined

and

controlled through Pegasus PEP documents.  PEP 180 is the

controlling document

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

status of

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

functionality was completed for this release.

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

Addition of CQL

stage 1 support

</li>

Refactoring of

Object Normalizer function to improve performance.

</li>

Out of Process

Provider user level request.

</li>

Embedded Object

support.

</li>

Command Line

Utilities

</li>

CIMDateTime

enhancements

</li>

Completion of

AutoPtr enhancements.

</li>

Certificate

management and user-based certificate authentication

</li>

Completion of HTTP

chunking. Pegasus

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

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

PEP 140</a> describes the implementation details.

</li>

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

statistics</li>

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

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

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

</ol>

</div>

The complete set of PEPs defined for

Further information regarding Pegasus support on IBM platforms can be

this release is defined in PEP 180.

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

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

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>

</a></h2>

The Pegasus bugzilla database documents any defects found in Pegasus

and  is available through the following link:  <a

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

database</a>.

Further information regarding Pegasus support on HP platforms can be

<h2><a

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

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

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

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

The OpenPegasus Bugzilla database documents any defects found in

The Pegasus project is controlled largely through a set of documents

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

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

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

modified Pegasus functionality and for the definition and documentation

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

of releases.

bugs.  Bugs reports are filed not only for bugs and their

Specifically the following PEPs define the characteristics of this

corresponding fixes but also as part of the process of committing new

Pegasus release.

code representing the work on PEPs done for OpenPegasus 2.6 and all

<ol>

subsequent versions.  Therefore, a search of the OpenPegasus

<li><a

Bugzilla base for bugs with the tag for a particular version (ex. 

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

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

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

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

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

</li>

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

<li><a

release.

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

- Changes for this release (bugs Tagged

200</a> - OpenPegaus 2.5 Build and Configuration

2.12.0_APPROVED). The link is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.0_APPROVED">

Option  for Selected

Pegasus 2.12.0_APPROVED bug list.</a>

Platforms</li>

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

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

Control

<li><a

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

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

The OpenPegasus project is controlled largely through the CVS

227</a> -  Pegasus 2.5 Runtime Packaging Definition

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

</li>

definition and review mechanism for new and modified Pegasus

<li><a

functionality and for the definition and documentation of releases.

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

The following documentation defines the characteristics of this Pegasus

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

release. The documents are available in the OpenPegasus CVS

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

repository.

source

<ul>

tree root directory).</li>

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

<li><a

<a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_12_x">OpenPegasus

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

2.12.x

180</a> - OpenPegasus Release Definition - This PEP is used

Release Status</a>) - A

throughout the development of this version as the control point for

section in the Pegasus wiki is used throughout the development of

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

this version as the control point for functionality that will go

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

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

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

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

</ol>

OpenPegasus

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

Build and Configuration Options  for Selected Platforms -  <span

The following documentation is available for the this Pegasus

style="font-weight: normal;">In previous versions of Pegasus this

release:

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;"> pegasus/doc/BuildAndReleaseOptions.html</big>.

<li> OpenPegasus External Interfaces -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;">pegasus/doc/EnternalInterface.html<span

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

<li> OpenPegasus  SDK Packaging Definition - 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 - Defines

the recommended set of files for inclusion in this OpenPegasus

release. Starting with Pegasus release 2.11.0, this idocument

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

364 - (This document is located

in the approved PEP repository and the OpenPegasus source tree

root directory (<big style="font-weight: bold;">pegasus/ReleaseNotes.htm</big>)</li>

</ul>

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

The following documentation is available for the this Pegasus

release:

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

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

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

command and HTML documentation for most of the tools.<o:p></o:p></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 - See the header files and the HTML  API

documentation - </li>

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

See the header files and the HTML  API documentation that is on

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

the web site. The best API usage documentation is the existing utilities

documentation.  In particular the Common/tests unit tests contain

and test programs and the examples in the API documentation.  In

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

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 - Readme.html in the Pegasus Root Directory, API

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>

which is available on the Pegasus web site.

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

Clients - API documentation and the documentation on the Pegasus

Clients - </li>

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

API documentation and the documentation on the Pegasus Technical

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

Workshop which is available on the Pegasus web site.

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

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

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

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

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

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

the OpenPegasus web site.  While these are the original design

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>

the design and implementation of these features.

</ul>

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

<span

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this

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

work for additional information regarding copyright ownership. Each

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

contributor licenses this file to you under the OpenPegasus Open Source

style="color: black;">

License; you may not use this file except in compliance with the License.

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

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

width="100%"></div>

copy of this software and associated documentation files (the

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

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

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

VERITAS Software Corporation

distribute, sublicense, and/or sell copies of the Software, and to

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

Permission is hereby granted,

the following conditions:

free of

The above copyright notice and this permission notice shall be included

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

in all copies or substantial portions of the Software.

associated

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

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

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

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

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

modify,

IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY

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

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

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

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

THE USE OR OTHER DEALINGS IN THE SOFTWARE.

</div>

</body>

</html>

Legend:

Removed from v.1.8
changed lines
	Added in v.1.17.4.2

No CVS admin address has been configured