summaryrefslogtreecommitdiffstats
path: root/ReleaseNotes.htm
diff options
context:
space:
mode:
authordave.sudlik <dave.sudlik>2005-09-26 15:41:17 +0000
committerdave.sudlik <dave.sudlik>2005-09-26 15:41:17 +0000
commitae8d21656031fa526304880749b3508fe170dee6 (patch)
tree4b5e25fc8e2e04f7d4404467ed1a14c991f56b21 /ReleaseNotes.htm
parente49a4788f616c2768f6faa3e48deadbc189d179a (diff)
downloadtog-pegasus-ae8d21656031fa526304880749b3508fe170dee6.zip
tog-pegasus-ae8d21656031fa526304880749b3508fe170dee6.tar.gz
tog-pegasus-ae8d21656031fa526304880749b3508fe170dee6.tar.xz
TITLE: Release Notes for OpenPegasus 2.5 DESCRIPTION: ReleaseNotes.htm
Diffstat (limited to 'ReleaseNotes.htm')
-rw-r--r--ReleaseNotes.htm1541
1 files changed, 1495 insertions, 46 deletions
diff --git a/ReleaseNotes.htm b/ReleaseNotes.htm
index 9ee1cbd..ca8628f 100644
--- a/ReleaseNotes.htm
+++ b/ReleaseNotes.htm
@@ -1,10 +1,10 @@
-<html xmlns:v="urn:schemas-microsoft-com:vml"
-
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html xmlns:v="urn:schemas-microsoft-com:vml">
<head>
-<style>
+ <style>
st1\:*{behavior:url(#ieooui) }
-</style>
-<style>
+ </style>
+ <style>
<!--
/* Font Definitions */
@font-face
@@ -598,7 +598,6 @@ div.Section1
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
-
@list l5:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
@@ -944,8 +943,8 @@ ol
ul
{margin-bottom:0in;}
-->
-</style>
-<style>
+ </style>
+ <style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
@@ -959,17 +958,15 @@ ul
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman"}
-</style>
-<link rel=Edit-Time-Data
-href="PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso">
-<title>PEP</title>
-<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
- name="City"/>
-<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
- name="place"/>
-<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
- name="date"/>
-<!--[if gte mso 9]><xml>
+ </style>
+ <link rel="Edit-Time-Data"
+ href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso">
+ <title>PEP</title>
+ <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>
@@ -996,33 +993,1485 @@ href="PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso">
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
-
-<body lang=EN-US link=blue vlink=blue style='tab-interval:.5in'>
-
-<div class=Section1>
-
-<div class=MsoNormal align=center style='text-align:center'><span
-style='color:black'>
-
-<hr size=2 width="100%" noshade color="#009900" align=center>
-
-</span></div>
-
+</head>
+<body style="" lang="EN-US" link="blue" vlink="blue">
+<div class="Section1">
+<div class="MsoNormal" style="text-align: center;" align="center"><span
+ style="color: black;">
+<hr align="center" color="#009900" noshade="noshade" size="2"
+ width="100%"></span></div>
+<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;"
+ align="center"><b><span style="font-size: 13.5pt; color: black;">Pegasus
+Enhancement Proposal (PEP)<o:p></o:p></span></b></p>
+<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span
+ style="color: black;"><br>
+<br>
+<b>PEP #:</b> 230<br>
+</span></p>
+<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release
+Notes for OpenPegasus 2.5</p>
+<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version: </b>1.8</p>
+<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> <st1:date
+ year="2004" day="23" month="3">1 April 2005</st1:date></p>
+<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Warren
+Grunbok, Karl Schopmeyer<br>
+</p>
+<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status:&nbsp; </b>draft</p>
+<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p>
+<table class="MsoNormalTable" style="width: 100%;" border="1"
+ cellpadding="0" cellspacing="1" width="100%">
+ <tbody>
+ <tr style="">
+ <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;">
+ <p class="MsoNormal" style="text-align: center;" align="center"><b><span
+ style="font-family: Arial; color: black;"><o:p>&nbsp;</o:p></span></b></p>
+ </td>
+ <td
+ style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">
+ <p class="MsoNormal" style="text-align: center;" align="center"><b><span
+ style="font-family: Arial; color: black;"><o:p>&nbsp;</o:p></span></b></p>
+ </td>
+ <td
+ style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">
+ <p class="MsoNormal" style="text-align: center;" align="center"><b><span
+ style="font-family: Arial; color: black;"><o:p>&nbsp;</o:p></span></b></p>
+ </td>
+ <td
+ style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">
+ <p class="MsoNormal" style="text-align: center;" align="center"><b><span
+ style="font-family: Arial; color: black;"><o:p>&nbsp;</o:p></span></b></p>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt;">
+ <p class="MsoNormal" style="text-align: center;" align="center"><span
+ style="font-family: Arial; color: black;"><font size="2">&nbsp;1.0</font><o:p></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt;">
+ <p class="MsoNormal" style="text-align: center;" align="center"><span
+ style="font-family: Arial; color: black;"><o:p>&nbsp; <font size="2">1,April
+2005<br>
+ </font></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt;">
+ <p class="MsoNormal" style="text-align: center;" align="center"><span
+ style="font-family: Arial; color: black;"><o:p>Warren Grunbok<br>
+ </o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt;">
+ <p class="MsoNormal"><span
+ style="font-family: Arial; color: black;"><font size="1">Initial
+Submission</font><o:p><font size="1"> <br>
+ </font></o:p></span></p>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt;" align="center">&nbsp;1.1</td>
+ <td style="padding: 0.75pt;" align="center">26, June 2005&nbsp; <br>
+ </td>
+ <td style="padding: 0.75pt;">Warren Grunbok<br>
+ </td>
+ <td style="padding: 0.75pt;">revisions based on Comments&nbsp; <br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;">1.2<br>
+ </td>
+ <td style="vertical-align: top;">22, July 2005<br>
+ </td>
+ <td style="vertical-align: top;">Warren Grunbok<br>
+ </td>
+ <td style="vertical-align: top;">fixed some broken links, added
+security notes. <br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;">1.3<br>
+ </td>
+ <td style="vertical-align: top;">23, Aug 2005<br>
+ </td>
+ <td style="vertical-align: top;">Warren Grunbok<br>
+ </td>
+ <td style="vertical-align: top;">Revisions based on comments<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;">1.4<br>
+ </td>
+ <td style="vertical-align: top;">30.Aug 2005<br>
+ </td>
+ <td style="vertical-align: top;">Warren Grunbok<br>
+ </td>
+ <td style="vertical-align: top;">More revisions based on Aug 26
+review in Architecture meeting<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;">1.5<br>
+ </td>
+ <td style="vertical-align: top;">12, Sept 2005<br>
+ </td>
+ <td style="vertical-align: top;">Warren Grunbok<br>
+ </td>
+ <td style="vertical-align: top;">Minor comment updates from 1.4
+version&nbsp; (balloted version)<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;">1.6<br>
+ </td>
+ <td style="vertical-align: top;">14,Sept 2005<br>
+ </td>
+ <td style="vertical-align: top;">Warren Grunbok<br>
+ </td>
+ <td style="vertical-align: top;">additional comments from review<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;">1.7<br>
+ </td>
+ <td style="vertical-align: top;">20, Sept 2005<br>
+ </td>
+ <td style="vertical-align: top;">Warren Grunbok<br>
+ </td>
+ <td style="vertical-align: top;">Added Solaris back in, corrected
+Provider security statement, and clarified Solaris support for 2.5<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;">1.8<br>
+ </td>
+ <td style="vertical-align: top;">21, Sept 2005<br>
+ </td>
+ <td style="vertical-align: top;">Warren Grunbok<br>
+ </td>
+ <td style="vertical-align: top;">Clarified SLP enablement
+Paragraph and correction of Power on Linux in platform table<br>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<p><o:p>&nbsp;</o:p></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%"></span></div>
+<p><b>Abstract:</b> This document defines the release notes for the 2.5
+version of the Pegasus CIM Server. <span class="norm1"><span
+ style="font-size: 9pt;"><a
+ href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&amp;file=Pegasus2_3_1ReleaseNotes.html&amp;tag=35"
+ target="_self"><br>
+</a></span></span></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%"></span></div>
+<p><b><o:p><font size="4">&nbsp;Contents<br>
+</font></o:p></b></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</span></h2>
+<p>This release is available in a number of forms including:</p>
+<ul>
+ <li>Source release in both ZIP and TAR formats. These can be
+downloaded from the <span class="SpellE">OpenPegasus</span> Web
+site at <a
+ href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&amp;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&amp;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&amp;ggid=392">Pegasus
+WEB site</a>.
+Installation instructions are part of the README in the root of the
+Pegasus source
+tree.<br>
+<br>
+<span class="norm">Instructions for building the Linux RPMs: <span
+ style="color: rgb(255, 0, 0);"></span><br>
+</span></>
+<ol>
+ <li><span class="norm"><span style="font-weight: bold;">Download</span>
+tog-pegasus-2.5.0-1.src.rpm. </span></li>
+ <li><span class="norm"><span style="font-weight: bold;">rpm</span>
+-ih tog-pegasus-2.5.0-1.src.rpm </span></li>
+ <li>
+ <p style="margin-top: 0pt; margin-bottom: 0pt; font-weight: bold;"><span
+ class="norm">Build
+the rpms:</span></p>
+ </li>
+</ol>
+<span class="norm"></span>
+<table
+ style="margin-left: auto; margin-right: auto; text-align: left; width: 712px; height: 116px;"
+ border="1" cellpadding="2" cellspacing="2">
+ <tbody>
+ <tr>
+ <td
+ style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Distro</td>
+ <td
+ style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Command<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top; text-align: center;">RHEL3<br>
+ </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</span></td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top; text-align: center;">RHEL4<br>
+ </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</span></td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top; text-align: center;">SLES 9 <br>
+ </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</span></td>
+ </tr>
+ </tbody>
+</table>
+<span class="norm"></span>
+<ol start="4">
+ <span class="norm"><br>
+ </span><li style="font-weight: bold;"><span class="norm">After
+the build the rpms will be in the
+following locations:</span></li>
+&nbsp;&nbsp;<span class="norm"></span>
+ <table style="width: 100%; text-align: left;" border="1"
+ cellpadding="2" cellspacing="2">
+ <tbody>
+ <tr>
+ <td
+ style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Distro<br>
+ </td>
+ <td
+ style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Location
+of RPMs after the build is complete<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top; text-align: center;">RHEL3<br>
+ </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: &quot;times new roman&quot;;"></span><span
+ style="font-family: &quot;times new roman&quot;;"></span></span><span
+ class="norm"> &nbsp;&nbsp;&nbsp; </span></td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top; text-align: center;">RHEL4<br>
+ </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></td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top; text-align: center;">SLES9<br>
+ </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.</span></td>
+ </tr>
+ </tbody>
+ </table>
+ <span class="norm"></span><span class="norm"></span>
+</ol>
+<span class="norm">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+&nbsp; </span><span class="norm"></span>
+<h2><a name="Functionality_of_This_Release"></a><span
+ style="color: black;">Functionality of This Release</span></h2>
+New for the Pegasus 2.5 release is a Feature Maturity Dashboard.&nbsp;
+This document shows the Pegasus users and developers the maturity of
+the various features found in Pegasus using a simple color coded
+key.&nbsp; That document can be found here:&nbsp; <a
+ href="http://www.openpegasus.org/page.tpl?ggid=799">Feature
+Maturity Link</a><br>
+<span style="font-family: &quot;times new roman&quot;;"><br>
+</span>The overall level of functionality in the Pegasus environment
+effective with
+this release is as follows:
+<h3><b>CIM Server Functionality</b></h3>
+<p>The following paragraphs list the functions in this release.&nbsp;
+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.&nbsp;&nbsp;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&nbsp; and interfaces
+are conditionally compiled with special environment variables. <a
+ href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&amp;gdid=8502"><span
+ style="color: rgb(255, 0, 0);"><span style="color: rgb(51, 102, 255);"><span
+ style="text-decoration: underline;">PEP 200</span>&nbsp;</span></span></a>
+provides more detailed information on how to enable
+functionality that is conditionally compiled in this release.</p>
+<blockquote>
+ <h4><b>CIM Operations over HTTP support</b></h4>
+ <ol>
+ <li>Class Operations (<span class="SpellE">getClass</span>, <span
+ class="SpellE">deleteClass</span>, <span class="SpellE">modifyClass</span>,
+ <span class="SpellE">enumerateClass</span>, <span class="SpellE">enumerateClassNames</span>)</li>
+ <li>Qualifier Operations (getQualifier, setQualifier,
+deleteQualifier) </li>
+ <li>Instance Operations (<span class="SpellE">getInstance</span>, <span
+ class="SpellE">deleteInstance</span>, <span class="SpellE">modifyInstance</span>,
+ <span class="SpellE">enumerateInstance</span>, <span
+ class="SpellE">enumerateInstanceNames</span>, <span class="SpellE">getProperty</span>,
+ <span class="SpellE">setProperty</span>)</li>
+ <li>Association Operations (references, <span class="SpellE">referencenames</span>,
+ <span class="SpellE">associators</span>, <span class="SpellE">associatornames)</span></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.&nbsp; Additional tests have been added in 2.5 for ExecQuery.<br>
+ </li>
+ </ol>
+</blockquote>
</div>
-
-<p>This is a place-holder for the 2.5 Release Notes which be added just before
-the release.</p>
-<p>Earlier versions can be downloaded from CVS, or from among the Release PEPS
-<a href="http://www.openpegasus.org/pp/documents.tpl?gdc_category=14&gdc_docage=0&grouped=Y&S=gdc_title&R=desc">
-here</a>.</p>
-<span
-style='color:black'>
-
-<hr size=2 width="100%" noshade color="#009900" align=center>
-
-</span>
+<blockquote>
+ <h4><b>Indications</b></h4>
+ <ul>
+ <li>Process indications - Process indications are operational in
+the
+Server.&nbsp; 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
+&lt;src/Unsupported/LifecycleIndicationProvider/readme.LifecycleIndications.htm&gt;.</li>
+ </ul>
+ <h4><b>Indication Listener</b></h4>
+ <p class="MsoNormal">The generic components for a CIM Listener and a
+listener API are operational.&nbsp; 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. <br>
+ </p>
+ <p class="MsoNormal"><br>
+ <font style="color: rgb(0, 0, 0);" color="#330099">Pegasus 2.5
+includes a new standalone listener that is separate
+from the current standalone CIMListener and the ExportServer listener
+in the CIM server.
+The use model that this listener fits is the following:
+ <ul>
+ <li><span class="norm"></span>&nbsp;The listener may be packaged as
+part of the CIMOM or it may be packaged independently as part of
+another application. </li>
+ <li><span class="norm"></span>&nbsp;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>
+ </font> </p>
+ <p><span style="color: rgb(0, 0, 0);" class="norm"></span><span
+ style="color: rgb(0, 0, 0);">&nbsp;</span><font color="#330099"><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.&nbsp; 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</span></a>&nbsp;<span
+ style="color: rgb(255, 0, 0);"> </span>for
+details.</span> </font></p>
+ <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.<br>
+Two new configuration properties were added to control object
+normalization.<br>
+ <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.<br>
+ </li>
+ </ol>
+ <br>
+ <h4>Embedded Object support</h4>
+Pegasus 2.5 now provides embedded object support. The proposed solution
+is restricted to the following:<br>
+The only representation for embedded objects supported by this
+PEP is CIM-XML. <br>
+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.&nbsp; Embedded instances will also carry the
+EmbeddedObject attribute with
+the value "object", as specified by CR Interop-00217.001. <br>
+ <br>
+ <p class="MsoNormal"> </p>
+</blockquote>
+<div class="Section1">
+<blockquote>
+ <h4><b>Query Language</b></h4>
+ <p>The query language today is based on WQL and is implemented and
+used for filters and in 2.4 for execQuery.&nbsp; <br>
+ </p>
+ <p>CQL Stage 1 has been included for Pegasus 2.5.&nbsp; PEPs 138,
+193, 205 combine to describe the function submitted.<br>
+ </p>
+ <h4><b>Schema Repository</b></h4>
+ <span class="norm"></span>By default, Pegasus uses an XML-based
+schema repository. A binary encoding option is also available.<span
+ style="font-family: &quot;times new roman&quot;;"><br>
+ <br>
+ </span>To use the binary encoding feature a new configuration
+properties was
+added:<br>
+ <p>&nbsp;&nbsp;&nbsp; enableBinaryRepository (true|false) - Enables
+or
+disables binary repository.<br>
+ </p>
+ <div style="margin-left: 40px;">&nbsp;In addition to the binary
+repository, the compressed repository
+functionality has
+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.<br>
+ <br>
+ <span style="color: rgb(51, 102, 255);">Note:&nbsp; </span><span
+ class="norm"></span><span style="color: rgb(51, 102, 255);">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><font><font color="RED"> </font></font><span
+ style="color: rgb(51, 102, 255);">See bugzilla 3642 for details.<br>
+ </span></div>
+ <h4><b><b>Compressed Repository</b></b></h4>
+ <div style="margin-left: 40px;"><span class="norm"></span><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.</font><br>
+ <span style="color: rgb(51, 102, 255);"><br>
+ </span><font><font color="RED"> </font></font></div>
+ <p> </p>
+ <h4><b>Instance Repository</b></h4>
+ <p><span class="norm"></span><font style="color: rgb(0, 0, 0);">The
+Pegasus schema repository may also be configured to hold instance
+data.&nbsp; </font><span class="norm"></span><font
+ style="color: rgb(0, 0, 0);">Although instances may be place in the
+repository
+it was </font><font style="color: rgb(0, 0, 0);">not designed as a
+high volume data store</font><span style="color: rgb(0, 0, 0);">. </span><br>
+ <br>
+ </p>
+ <h4><b><b>Security Considerations<br>
+ </b></b></h4>
+ <font style="color: rgb(0, 0, 0);" color="RED">OpenPegasus 2.5 (and
+prior) contains several mechanisms to perform authorization, but none
+of these authorization checks are performed by default.
+By registering any provider which fails to do appropriate authorization
+checks, the consequences may include information leakage, data
+corruption, or unintended elevation of privilege. Please ensure that
+one of the following mechanisms is used to ensure appropriate access to
+your systems and data:<br>
+1. Only install/register providers which perform authorization
+appropriate for your environment.<br>
+ </font>
+ <div style="margin-left: 40px;"><font style="color: rgb(0, 0, 0);"
+ color="RED">a. For providers, this may include registering to
+'Run-as-requestor' (not available prior to Pegasus 2.5) and/or
+performing authorization checks within the provider.<br>
+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. <br>
+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.</font><br>
+ </div>
+ <font style="color: rgb(0, 0, 0);" color="RED">2. Restrict users with
+access to Pegasus to a specific authorized user group of trusted
+individuals.<br>
+3. Namespace authorization is also available.<br>
+ <br>
+ </font><span class="norm">For administration issues please refer to
+the SSL Admin Guide found at: &nbsp; </span>pegasus/doc/PegasusSSLGuidelines.htm<br>
+ <h4><b>Server Security</b></h4>
+ <ol style="margin-top: 0in;" start="1" type="1">
+ <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 <span class="SpellE">OpenSSL</span>
+libraries. Pegasus does not provide the <span class="SpellE">OpenSSL</span>
+libraries but SSL can be used on any platform supported by <span
+ class="SpellE">OpenSSL</span>.&nbsp; Minimum level known to work
+is&nbsp; 0.9.6c .&nbsp;&nbsp; This release of Pegasus was tested with
+0.9.6k.&nbsp; See <a
+ href="http://www.openpegasus.org/pp/uploads/40/Application%20Data/Microsoft/Word/www.openssl.org">openssl.org</a>
+for <span class="SpellE">OpenSSL</span> release information<o:p>.</o:p></li>
+ <li class="MsoNormal" style="color: black;">SSL levels<br>
+ <span class="norm"></span><font style="color: rgb(0, 0, 0);">SSLv3
+and TLSv1 by default. SSLv2 is
+disabled by default and only enabled by a compile time option</font>.&nbsp;
+See<a
+ href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&amp;gdid=8502">
+PEP 200</a> for details on
+configuration.<br>
+ </li>
+ </ol>
+ <b> </b>
+ <h4><b>Client Security</b><span style="font-family: times new roman;"><span
+ style="font-style: italic;"><span style="font-weight: bold;"></span></span></span></h4>
+Certificate management&nbsp;
+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.<br>
+ <span class="norm"></span><font style="color: rgb(0, 0, 0);">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.&nbsp; See the SSL guide found in the /pegasus/doc directory for
+more details on client security.</font><br>
+Note: <span class="norm"><font><font color="RED"><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.</span> </font></font></span>
+ <h4><b>Platform Management Functions</b></h4>
+ <ol style="margin-top: 0in;" start="1" type="1">
+ <li class="MsoNormal" style="color: black;">Configuration through
+the defined configuration parameters (cimconfig) and server command
+line options.<span class="norm"></span><font
+ style="color: rgb(0, 0, 0);" color="RED">&nbsp; 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.</font> <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.<br>
+ </o:p></li>
+ <li class="MsoNormal" style="color: black;">Operation statistics
+capture using the <span class="norm"></span><font
+ style="color: rgb(0, 0, 0);">CIM_StatisticalData </font>classes in
+the DMTF Interop model. This
+function is considered alpha quality and conditionally compiled. <br>
+ </li>
+ <li class="MsoNormal" style="color: black;">Multiple
+pluggable provider managers.&nbsp; 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><b>SLP Discovery</b></h4>
+ <p>SLP support is included but is conditionally compiled in or out on
+a platform basis.&nbsp;<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.&nbsp; PEGASUS_DISABLE_SLP and
+PEGASUS_ENABLE_SLP are the environment variables that control inclusion
+of this feature.&nbsp; 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&nbsp; 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).<br>
+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.<br>
+ </p>
+ <h4>Provider Managers</h4>
+ <p>Pegasus is designed to support multiple Provider Managers to allow
+multiple provider interfaces to the CIMOM.&nbsp; The two default
+provider managers are the Pegasus C++ Interface and Common
+Manageability Programming Interface (CMPI) Interface.<br>
+ </p>
+ <blockquote>
+ <h5><b style="">CMPI C interface Provider Manager<o:p></o:p></b></h5>
+ <span style="font-family: &quot;times new roman&quot;;">Pegasus 2.5 includes
+a provider manager for the CMPI C interfaces. This C interface is the
+result of a project by the IBM SBLIM team (see&nbsp;
+http://sblim.sourceforge.net) and is written to the Common
+Manageability Programming Interface, which is an OpenGroup standard.
+The CMPI
+specification is available at:
+http://www.opengroup.org/bookstore/catalog/c051.htm. This provides a
+standardized C level interface for creating providers that can be
+registered with the Pegasus CIM Server in the same manner as the
+current C++ providers.&nbsp; </span><span
+ style="font-family: &quot;times new roman&quot;;"><span class="norm"></span></span>The
+ability for CMPI providers to do user authorization is now available in
+Pegasus 2.5.<br>
+ <span style="font-family: &quot;times new roman&quot;;"> <br>
+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.</span><br>
+ <h5>JMPI Java Interface Provider Manager</h5>
+ <p>Pegasus includes an experimental provider manager for Java
+provider interfaces based on the SNIA provider interface
+definitions.&nbsp; This provider manager is&nbsp; considered alpha
+quality and is not compiled in the default build.&nbsp;&nbsp; See
+readme.jmpi in the Pegasus source root directory for more information.</p>
+ </blockquote>
+</blockquote>
+<h3><b>&nbsp;&nbsp;&nbsp; Providers</b></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.<br>
+<br>
+<span class="norm"></span>Administrators should check the providers to
+ensure that the provider vendor
+has made use of available authorization capability.<br>
+</div>
+<p style="margin-left: 40px;">There are a number of providers available
+in the Pegasus release.
+This includes providers in the following categories:</p>
+<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
+ <h4>Pegasus Internal Providers</h4>
+ <p>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.&nbsp; &nbsp; The
+providers in this category are mostly defined in the directory
+src/pegasus/controlproviders and include support for the following
+classes:</p>
+ <ul>
+ <li>DMTF Interop classes including __Namespace,&nbsp; <span
+ class="SpellE">CIM_Namespace</span>, <span class="SpellE">CIM_ObjectManager</span>,
+ <span class="SpellE">CIM_CommunicationMechanism, and
+CIMOMStatistics.</span></li>
+ </ul>
+ <h4><span class="SpellE">CMPI Remote</span></h4>
+ <h4><span class="SpellE"></span></h4>
+ <span class="SpellE">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.<br>
+ </span><span class="SpellE"></span><span class="SpellE"><br>
+ </span>
+ <h4><b>Generic Providers</b></h4>
+ <p>Generic <span class="SpellE">OperatingSystem</span> provider. See
+the
+directory <span class="SpellE">src</span>/Providers/generic.</p>
+ <h4><b>Test/Sample Providers</b></h4>
+ <p>See the directories <span class="SpellE">src/Providers/TestProviders</span>
+and <span class="SpellE">src</span>/Providers/Sample for more
+information about test and
+sample providers.</p>
+ <h4><b>Managed System Providers</b></h4>
+ <p><span class="SpellE">ComputerSystem</span>, <span class="SpellE">DNSAdmin</span>,
+ <span class="SpellE">DNSService</span>, Operating System, Process,
+Processor. For
+more information on these providers see the documentation for each
+provider in
+the directory <span class="SpellE">src/Providers/ManagedSystem</span></p>
+ <h4><span class="SpellE">Server Statistics<br>
+ </span></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><br>
+ <span class="SpellE"></span></h4>
+ <h4><span class="SpellE">SLP Provider</span></h4>
+ <p><span class="SpellE">This provider acts as the definer of&nbsp;
+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)<br>
+ </span></p>
+ <br>
+ <br>
+</blockquote>
+<h3><span class="SpellE"><b>CIM_Schema</b></span></h3>
+<p>The default <span class="SpellE">CIM_Schema</span> loaded with this
+release is
+the DMTF CIM 2.9, Final release.&nbsp; In addition, Pegasus includes
+a number of
+local classes defined for Pegasus.&nbsp; These are defined in the
+pegasus/Schemas
+directory.&nbsp;&nbsp;&nbsp;<span style=""></span>There are also a
+number of older schema available in the CVS.</p>
+<p>The mechanism to install other schemas than the default is defined
+in the mak/config.mak</p>
+<p style="margin-bottom: 12pt;"><b>NOTE:</b> The CIM 2.5 schema is
+maintained in the
+CVS repository because it remains the basis for parts of the Pegasus
+test
+environment.</p>
+<h3><b>Pegasus MOF Compilers</b></h3>
+<p>Pegasus implements a MOF compiler that can operate either at the
+client
+interface to the Pegasus CIM Server (<span class="SpellE">cimmof</span>)
+or directly interfacing with a CIM
+repository (<span class="SpellE">cimmofl</span>).</p>
+<p>The direct interface compiler is used primarily to provide an
+initial
+class/instance repository. <font color="#ff0000"><b>WARNING:</b></font>&nbsp;
+the use of <span class="SpellE">cimmofl</span>
+to manipulate instances in the repository bypasses any provider that is
+registered to serve these&nbsp; 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.&nbsp; Use of <span class="SpellE">cimmofl in general is
+discouraged and particularly </span>&nbsp;to manipulate
+instances served by a registered providers (ex. Provider registration).
+<br>
+</p>
+<h3><b>Client Tools</b></h3>
+Lightweight statistics are now implemented for
+the
+client. The client statistics surfaces the elapsed time spent in the
+client,
+and the
+elapsed time spent on the network between client and server.<br>
+<br>
+<h3><b>Pegasus CIM Server <span class="SpellE">Administration</span></b></h3>
+<ol style="margin-top: 0in;" start="1" type="1">
+ <li class="MsoNormal" style="color: black;"><span class="SpellE">cimuser</span>
+- Manage Pegasus CIM Server Users.<o:p></o:p></li>
+ <li class="MsoNormal" style="color: black;"><span class="SpellE">cimconfig</span>
+- Manage the Pegasus CIM Server configuration parameters.<o:p></o:p></li>
+ <li class="MsoNormal" style="color: black;"><span class="SpellE">cimauth</span>
+- Manage the CIM Server authorization characteristics. Today this is
+authorizing users to namespaces.<o:p></o:p></li>
+ <li class="MsoNormal" style="color: black;"><span class="SpellE">cimprovider</span>
+- Manage information about the providers .</li>
+</ol>
+<br>
+&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-weight: bold;">Server admin
+note:</span><br>
+<div style="margin-left: 40px;">The default behavior for determining
+the CIM server's HTTP and HTTPS ports has changed.&nbsp; In previous
+releases, any value in /etc/services would override a port explicitly
+specified in the configuration.&nbsp; The new order for determining the
+CIM server's HTTP and HTTPS ports is as follows:<br>
+1) An explicitly specified port value takes precedence over any other
+values.<br>
+</div>
+<div style="margin-left: 40px;">2) If no port is specified, the value
+in /etc/services is used.<br>
+3) If no value is specified in /etc/services, the default WBEM port is
+used.<br>
+</div>
+<h3><b>Information client tools</b></h3>
+<p>These tools provide information on the objects managed by the server.</p>
+<ol style="margin-top: 0in;" start="1" type="1">
+ <li class="MsoNormal" style="color: black;"><span class="SpellE">tomof</span>
+- 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;"><span class="SpellE">dnsinfo</span>
+- Generate a set of standard information on the <span class="SpellE">Domain</span>
+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;"><span class="SpellE">ipinfo</span>
+- Generates a set of standard information from the Network
+Schema.&nbsp; Information generated varies by system because of the
+level of provider support.<o:p></o:p></li>
+ <li class="MsoNormal" style="color: black;"><span class="SpellE">osinfo</span>
+- 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><b>Test support Tools</b></h3>
+<ol style="margin-top: 0in;" start="1" type="1">
+ <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.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></li>
+ <li class="MsoNormal" style="color: black;">The Pegasus test suite
+(see the pegasus/tests directory<span class="SpellE"></span>)<o:p></o:p></li>
+ <li class="MsoNormal" style="color: black;"><b><span class="SpellE">TestClient</span>
+ </b>- Basic client for overall platform operation testing. <o:p></o:p></li>
+ <li class="MsoNormal" style="color: black;"><b><span class="SpellE">wbemexec</span></b>
+- Test tool that sends/receives XML from XML input.<o:p></o:p></li>
+ <li class="MsoNormal" style="color: black;"><b>CLI</b> - Command line
+interface for Client commands.<o:p></o:p></li>
+ <li class="MsoNormal" style="color: black;"><b>Benchmark Test</b> - A
+benchmark test environment is provided which includes both a client and
+provider component. See <span class="SpellE">src/clients/benchmarkTest</span>
+for more information.<o:p></o:p></li>
+</ol>
+<h3><b>Pegasus Interface APIs</b></h3>
+<p>Details of the Pegasus public interfaces for this release are listed
+in PEP 209
+available from the web <span class="GramE">site(</span><a
+ href="http://www.openpegasus.org/pp/uploads/40/Administrator/My%20Documents/processes/www.openpegasus.org">www.openpegasus.org</a>).
+That document is the <span class="SpellE">authorative</span> source
+for the list of publicly supported Pegasus APIs.&nbsp;&nbsp; The Client
+and Provider API were originally frozen at the&nbsp;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.&nbsp; There have been extensions and new
+interfaces added for this release and these are marked as experimental.
+&nbsp; The Pegasus public
+interfaces includes the following major functions</p>
+<ol style="margin-top: 0in;" start="1" type="1">
+ <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>
+<p>In addition, there are other client interfaces which are not today
+in the public SDK including:</p>
+<ol style="margin-top: 0in;" start="1" type="1">
+ <li class="MsoNormal" style="color: rgb(0, 0, 0);"><span style=""
+ lang="DA">CIM Listener APIs</span></li>
+ <ul style="color: rgb(0, 0, 0);">
+ <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.</font></li>
+ <ul>
+ <li><font size="2"><b>New CIM Listener now provides selective
+indication delivery.</b><span class="norm"></span></font><br>
+ </li>
+ <li><span class="norm"></span><font size="2"><b>New CIM Listener
+keeps all consumer libraries in memory for the duration of its
+execution.</b><span class="norm"></span></font><br>
+ </li>
+ <li><span class="norm"></span><font size="2"><b>New CIM Listener
+is now pluggable.</b><br>
+ <span class="norm"></span></font></li>
+ <li><span class="norm"></span><font size="2"><b>New CIM Listener
+now provides reliable indication delivery.</b></font></li>
+ </ul>
+ </ul>
+ <li class="MsoNormal" style="color: black;"><span lang="da">SLP
+Client (User Agent) APIs which are extensions to the Client APIs</span></li>
+</ol>
+<p class="MsoNormal"><span style="color: black;"><o:p>&nbsp;</o:p></span></p>
+<p class="MsoNormal"><span style="color: black;">The APIs are
+documented in
+their respective header files and&nbsp; in HTML documentation based on
+the information
+in the header files extracted with the doc++ tool will be available on
+the
+OpenPegasus web site.<br>
+&nbsp;<o:p></o:p></span></p>
+<h3><b>WMI <span class="SpellE">Mapper</span></b></h3>
+<p>The WBEM to WMI <span class="SpellE">Mapper</span> provides a way
+to access
+WMI data from Windows platform systems. It converts incoming XML/CIM
+requests
+to Microsoft WMI requests, executes the requests, converts the results
+to
+XML/CIM and returns the results to the client. WMI <span class="SpellE">Mapper</span>
+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 <span class="SpellE">Mapper</span>
+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</span> runs as a service, logged on using an
+account with
+administrative rights (which has all access to WMI data). Because of
+this, the
+WMI <span class="SpellE">Mapper</span> 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 <span class="SpellE">Mapper</span>
+MUST
+contain user credentials.<br>
+</p>
+<h3><b><b>Indication Handlers</b></b></h3>
+System Log Indication Handler<br>
+<div style="margin-left: 40px;">The SysLog Indication Handler is a new
+for 2.5
+type of Indication Handler which allows CIM Indications to be delivered
+to the system syslog file. It has following features:<br>
+</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.<br>
+ </li>
+</ul>
+<br>
+Email Indicaiton Handler<br>
+<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.&nbsp;&nbsp; See <a
+ href="http://www.openpegasus.org/pp/uploads/40/7166/PEP207-EmailIndicationHandler.htm">PEP
+207</a>&nbsp; for details. <br>
+</div>
+<br>
+<br>
+<ol>
+</ol>
+<h2><a name="Relationship_to_CIMWBEM_Standards"></a>Relationship to
+CIM/WBEM Standards</h2>
+<p>Pegasus was designed and implemented to comply with the DMTF
+specifications The following table defines the level of the DMTF
+specifications which which Pegasus conforms today.</p>
+<table id="AutoNumber1" border="1" cellspacing="1" width="100%">
+ <tbody>
+ <tr>
+ <td bgcolor="#00ffff" width="33%"><b>DMTF Specification</b></td>
+ <td bgcolor="#00ffff" width="33%"><b>Specification Version</b></td>
+ </tr>
+ <tr>
+ <td width="33%">DSP 0004 CIM Specification</td>
+ <td width="33%">Version 2.2 with Addendum</td>
+ </tr>
+ <tr>
+ <td width="33%">DSP 0200 - CIM Operations over HTTP</td>
+ <td width="33%">1.1, final, 6&nbsp; January 2002</td>
+ </tr>
+ <tr>
+ <td width="33%">DSP 0201 - Representation of CIM in XML</td>
+ <td width="33%">2.1, preliminary, May 2, 2002</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%">1.0.0</td>
+ </tr>
+ <tr>
+ <td width="33%">CIM Schema </td>
+ <td width="33%">2.9 Final, Jan. 2005</td>
+ </tr>
+ </tbody>
+</table>
+<h2><b><span style="font-family: Times;"><a name="Supported Platforms">Supported
+Platforms</a></span></b></h2>
+<p>Each Pegasus release lists as 'active' platforms those
+hardware/software platforms that have recognized ports for the Pegasus
+code
+base including a maintainer for the platform that will be willing to
+regularly document issues and/or fix defects as the Pegasus
+code base is changed.&nbsp;
+Pegasus may be operable on other platforms (ex. Windows 98) but without
+a group
+to provide the role of test and maintenance, correct operation of&nbsp;
+Pegasus cannot be
+assured.&nbsp; In all cases, including the active platforms, it is the
+responsibility of the entity that packages and/or compiles OpenPegasus
+for shipment or deployment, to read, and actively monitor the Pegasus
+bugzilla database for a list of relevant defects that affect their
+platform. &nbsp; The platforms that are considered 'active' for this
+Pegasus release are:<br>
+<span class="norm"></span><br>
+</p>
+<table class="MsoNormalTable" style="width: 302.25pt;" border="1"
+ cellpadding="0" cellspacing="1" height="409" width="504">
+ <tbody>
+ <tr style="">
+ <td
+ 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" width="211">
+ <p class="MsoNormal"><b><span style="color: black;">Platform and
+OS</span></b><span style="color: black;"><o:p></o:p></span></p>
+ </td>
+ <td
+ 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: 173.25pt;"
+ height="26" width="289">
+ <p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span
+ style="color: black;"><o:p></o:p></span></p>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt; width: 126.75pt;" height="25"
+ width="211">
+ <p class="MsoNormal"><span style="color: black;">HP-UX<o:p></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt; width: 173.25pt;" height="25"
+ width="289">
+ <p class="MsoNormal"><span style="color: black;">HP <span
+ class="SpellE">aC</span>++ B3910B<o:p></o:p></span></p>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt; width: 126.75pt;" height="25"
+ width="211">
+ <p class="MsoNormal"><span class="SpellE"><span
+ style="color: black;">Linux on Power</span></span><span
+ style="color: black;"><o:p></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt; width: 173.25pt;" height="25"
+ width="289">
+ <p class="MsoNormal"><span class="SpellE"><span
+ style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt; width: 126.75pt;" height="25"
+ width="211">
+ <p class="MsoNormal"><span class="SpellE"><span
+ style="color: black;">zLinux</span></span><span style="color: black;"><o:p></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt; width: 173.25pt;" height="25"
+ width="289">
+ <p class="MsoNormal"><span class="SpellE"><span
+ style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt; width: 126.75pt;" height="25"
+ width="211">
+ <p class="MsoNormal"><span style="color: black;">Linux Itanium<o:p></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt; width: 173.25pt;" height="25"
+ width="289">
+ <p class="MsoNormal"><span class="SpellE"><span
+ style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt; width: 126.75pt;" height="25"
+ width="211">
+ <p class="MsoNormal"><span style="color: black;">Linux IA-32<o:p></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt; width: 173.25pt;" height="25"
+ width="289">
+ <p class="MsoNormal"><span class="SpellE"><span
+ style="color: black;">gcc</span></span><span style="color: black;">
+(versions 2.9x and 3.xx)<o:p></o:p></span></p>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt; width: 126.75pt;" height="91"
+ width="211">
+ <p class="MsoNormal"><span style="color: black;">Windows 2000<o:p></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt; width: 173.25pt;" height="91"
+ width="289">
+ <p class="MsoNormal"><span style="color: black;" lang="NL">Microsoft
+Visual C++ Ver 6 and Microsoft .Net compiler Version.&nbsp;&nbsp; </span><span
+ style="color: black;">Works on VC .NET 2003 (<span class="SpellE">aka</span>
+v7.1)<o:p></o:p></span></p>
+ </td>
+ </tr>
+ <tr>
+ <td style="padding: 0.75pt; width: 126.75pt;" height="69"
+ width="211">
+ <p class="MsoNormal"><span style="color: black;">Windows XP<o:p></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt; width: 173.25pt;" height="69"
+ width="289">
+ <p class="MsoNormal"><span style="color: black;" lang="NL">Microsoft
+Visual C++ Ver. 6 and Microsoft .Net compiler Version </span>7.1<span
+ style="color: black;" lang="NL"><o:p></o:p></span></p>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt; width: 126.75pt;" height="43"
+ width="211"> <font size="3">MacOS version 10.2 and higher</font></td>
+ <td style="padding: 0.75pt; width: 173.25pt;" height="43"
+ width="289"> <font size="3">gcc 3.3</font></td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;"><big>HP OpenVMS Alpha<br>
+ </big></td>
+ <td style="vertical-align: top;">&nbsp;<big><font
+ style="color: rgb(0, 0, 0);" color="RED">HP C++ V6.5-042 for OpenVMS
+Alpha and above</font></big> </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;"><big><span class="norm"></span><font
+ style="color: rgb(0, 0, 0);"> HP OpenVMS IA64</font></big></td>
+ <td style="vertical-align: top;"><span class="norm"></span><big><font
+ style="color: rgb(0, 0, 0);">HP C++ V7.1-011 on OpenVMS IA64 and above</font></big>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;"><span class="norm"></span><big><font><font
+ color="RED"><span style="color: rgb(0, 0, 0);">Solaris 8<br>
+* See below for additional info<br>
+ </span> </font></font></big></td>
+ <td style="vertical-align: top;"><big>GNU&nbsp; 2.95.3</big><br>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<br>
+<span style="font-weight: bold;">Solaris:</span>&nbsp; Solaris testing
+began late in the 2.5 release cycle, thus has not been thoroughly
+tested.&nbsp; In order for Pegasus 2.5 to function properly on that
+platform, changes documented in OpenPegasus Bugzilla 4179&nbsp; must be
+applied.&nbsp;<span class="norm"><font color="RED">
+</font></span>
+<h2><small><b><b>Platform patches</b></b></small></h2>
+<font style="color: rgb(0, 0, 0);">The following is a list of platform
+patches Pegasus requires.<br>
+<br>
+</font>
+<div style="margin-left: 40px;"><font style="color: rgb(0, 0, 0);">RHAS
+2.1 needs the update to fix Red Hat Bugzilla 98815.</font><br>
+</div>
+<br>
+<p>Further information regarding Pegasus support on IBM platforms can
+be
+found at: <a
+ href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span
+ style="text-decoration: underline; color: rgb(51, 51, 255);">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</span></a>
+</p>
+<p> <br>
+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>.</p>
+<p><o:p><br>
+</o:p></p>
+<h2><a name="Conformance with DMTF Specifications">Conformance with
+DMTF Specifications</a></h2>
+<p>It is a major goal
+of the OpenPegasus project to both drive and utilize the DMTF CIM/WBEM
+specifications.&nbsp; However, today there are a number of known
+differences.&nbsp;
+As of this release, some of the differences include the following:</p>
+<ol>
+ <li><b>Provider Registration</b> - 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>&nbsp;<b>Indications </b>-Today Pegasus supports process
+indications but does not
+include any specific support for lifecycle indications.</li>
+ <li>
+ <p class="MsoNormal"><span style="color: black;">&nbsp;</span><font
+ style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers
+option on Instance Operations</font><span style="color: black;"><b>&nbsp;</b>
+-
+The DMTF specifications are unclear regarding the inclusion of
+qualifiers on
+CIM instances.&nbsp; 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).&nbsp; </span>&nbsp;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.&nbsp; 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.&nbsp; In the future it is expected
+that Pegasus will deprecate the use of qualifiers on instance
+operations completely.</p>
+ </li>
+ <li><b>LocalOnly option on instance
+Operations </b>- 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>
+ <p class="MsoNormal">&nbsp;<b>CIM MOF compiler function for
+instance aliasing</b> - The Pegasus MOF compiler does not today support
+this function.&nbsp; This function is planned for a future version.</p>
+ </li>
+ <li>
+ <p class="MsoNormal"><b>&nbsp;MultiRequest Oprations</b> - Pegasus
+does not support the DMTF defined MultiRequest Operation option.</p>
+ </li>
+ <li>
+ <p class="MsoNormal"><b>MOFCompiler namespace pragma</b> - The
+Pegasus compiler does not support the namespace pragma.</p>
+ </li>
+</ol>
+<h2><a name="Changes in This Release">Changes in This Release</a></h2>
+<p>The development and release of each version of Pegasus is defined
+and
+controlled through Pegasus PEP documents.&nbsp; 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.</p>
+<p>In general, the areas of development for this release were:</p>
+<ol style="margin-top: 0in;" start="1" type="1">
+ <li class="MsoNormal" style="color: black;">
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">Addition of CQL
+stage 1 support<br>
+ </p>
+ </li>
+ <li class="MsoNormal" style="color: black;">
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">Refactoring of
+Object Normalizer function to improve performance. </p>
+ </li>
+ <li class="MsoNormal" style="color: black;">
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">Out of Process
+Provider user level request.<br>
+ </p>
+ </li>
+ <li class="MsoNormal" style="color: black;">
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">Embedded Object
+support.&nbsp; </p>
+ </li>
+ <li class="MsoNormal" style="color: black;">
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">Command Line
+Utilities<br>
+ </p>
+ </li>
+ <li class="MsoNormal" style="color: black;">
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">CIMDateTime
+enhancements<br>
+ </p>
+ </li>
+ <li class="MsoNormal" style="color: black;">
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of
+AutoPtr enhancements. </p>
+ </li>
+ <li class="MsoNormal" style="color: black;">
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">Certificate
+management and user-based certificate authentication<br>
+ </p>
+ </li>
+ <li class="MsoNormal" style="color: black;">
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of HTTP
+chunking. <font style="color: rgb(51, 51, 255);" color="RED">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.</font></p>
+ </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>
+<p class="MsoNormal" style="margin-left: 0.5in;">&nbsp;</p>
+The complete set of <span class="SpellE">PEPs</span> defined for
+this release is defined in PEP 180.
+<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus defects<br>
+</a></span></h2>
+<p>The Pegasus bugzilla database documents any defects found in Pegasus
+and&nbsp; is available through the following link:&nbsp; <a
+ href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla
+database</a>.&nbsp; <br>
+</p>
+<br>
+<h2><a
+ name="Pegasus Release Control and Version Definition Documentation">Pegasus
+Release Control and Version Definition Documentation</a></h2>
+<p>The Pegasus project is controlled largely through a set of documents
+(PEPs) that serve as the definition and review mechanism for new and
+modified Pegasus functionality and for the definition and documentation
+of releases.</p>
+<p>Specifically the following PEPs define the characteristics of this
+Pegasus release.</p>
+<ol>
+ <li><a
+ href="http://www.openpegasus.org/pp/protected/upreviews/20/1682/PEP209_ExternalInterface2.5.htm">PEP
+209</a> - OpenPegaus 2.5 External Interfaces (as of this document
+verion of PEP 230, PEP 209 is listed as draft status)<br>
+ </li>
+ <li><a
+ href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&amp;gdid=8502">PEP&nbsp;
+200</a> - OpenPegaus 2.5 Build and Configuration
+Option&nbsp; for Selected
+Platforms</li>
+ <li>PEP 230 - Pegasus 2.5 Release Notes (This document)</li>
+ <li><a
+ href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&amp;gdid=8503">PEP
+227</a> -&nbsp; Pegasus 2.5 Runtime Packaging Definition<br>
+ </li>
+ <li><a
+ href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&amp;gdid=8466">PEP
+210</a>&nbsp; - OpenPegasus 2.5 SDK Packaging Definition</li>
+ <li>PEP 235&nbsp; - Pegasus readme.txt for 2.5 (also in the Pegasus
+source
+tree root directory).</li>
+ <li><a
+ href="http://www.openpegasus.org/pp/protected/revdoc.tpl?CALLER=revdocuments.tpl&amp;grid=1411">PEP
+180</a> - OpenPegasus Release Definition - This PEP is used
+throughout the development of this version as the control point for
+functionality that will go into the release and points to all of the
+PEPs that represent the Pegasus 2.5 functionality changes.&nbsp; (as of
+this document verion of PEP 230, PEP 180 is listed as draft status)</li>
+</ol>
+<h2><a name="General Documentation">General Documentation</a></h2>
+<p>The following documentation is available for the this Pegasus
+release:</p>
+<ul style="margin-top: 0in;" type="disc">
+ <li class="MsoNormal" style="color: black;"><b>Utilities</b> - A
+combination of help generally available with the -h option for each
+command and HTML documentation for most of the tools.<o:p></o:p></li>
+ <li class="MsoNormal" style="color: black;"><b>API and&nbsp; usage
+documentation</b> - See the header files and the HTML&nbsp; API
+documentation that is on the web site. The best API usage documentation
+is the existing utilities and test programs and the examples in the API
+documentation.&nbsp; In particular the Common/tests unit tests contain
+extensive examples of the use of the Common APIs.</li>
+ <li class="MsoNormal" style="color: black;"><b>Building and Debugging
+Providers </b>- Readme.html in the Pegasus Root Directory, API
+documentation, and documentation from the Pegasus Technical Workshop
+which is available on the Pegasus web site.</li>
+ <li class="MsoNormal" style="color: black;"><b>Building and Debugging
+Clients</b> - API documentation and the documentation on the Pegasus
+Technical Workshop which is available on the Pegasus web site.</li>
+ <li class="MsoNormal" style="color: black;"><b>Compiler operation and
+commands</b> - compiler help (cimmofl -h)</li>
+ <li class="MsoNormal" style="color: black;"><b>PEPs</b> - The
+features of Pegasus that have been installed in this and the previous
+few versions are defined by Pegasus PEPs that are available on the
+OpenPegasus web site.&nbsp; While these are the original design
+documents largely and use in the process of defining and approving the
+overall characteristics of new functionality, they serve as a guide to
+the design and implementation of these features.</li>
+</ul>
+&nbsp;
+<p class="MsoNormal" style="margin-left: 0.5in;"><span
+ style="color: black;">&nbsp; <o:p></o:p></span></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%"></span></div>
+<p><i><font size="2">Copyright (c) 2005 EMC Corporation;
+Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open Group;
+VERITAS Software Corporation</font><br>
+<br>
+</i><i><span style="font-size: 7.5pt;">Permission is hereby granted,
+free of
+charge, to any person obtaining a copy&nbsp; of this software and
+associated
+documentation files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use, copy,
+modify,
+merge, publish, distribute, sublicense, and/or sell copies of the
+Software, and
+to permit persons to whom the Software is furnished to do so, subject
+to the
+following conditions:</span><br>
+</i><i><span style="font-size: 10pt;"><br>
+</span></i><i><span style="font-size: 7.5pt;">THE ABOVE COPYRIGHT
+NOTICE AND THIS
+PERMISSION NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL
+PORTIONS OF
+THE SOFTWARE. THE SOFTWARE IS PROVIDED&nbsp; "AS IS", WITHOUT
+WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
+THE
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE
+FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
+CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR
+THE USE OR OTHER DEALINGS IN THE SOFTWARE.</span></i></p>
<p>&nbsp;</p>
-
+</div>
</body>
-
-</html> \ No newline at end of file
+</html>