summaryrefslogtreecommitdiffstats
path: root/ReleaseNotes.htm
diff options
context:
space:
mode:
authorkarl <karl>2012-09-20 05:48:51 +0000
committerkarl <karl>2012-09-20 05:48:51 +0000
commitf71d7aded55f6ed82fb5eada34024946cff5384f (patch)
tree29c5793290e9a7a56feb0960e4ce8a584fffcc4c /ReleaseNotes.htm
parent334e673051fc06a975d23c118ee55322e8dde011 (diff)
downloadtog-pegasus-f71d7aded55f6ed82fb5eada34024946cff5384f.zip
tog-pegasus-f71d7aded55f6ed82fb5eada34024946cff5384f.tar.gz
tog-pegasus-f71d7aded55f6ed82fb5eada34024946cff5384f.tar.xz
BUG#: 9372
TITLE: OpenPegasus 2.12.0 Release Notes PEP 364 DESCRIPTION: Updates the file ReleaseNotes.htm to reflect the 2.12.0 approved Release Note PEP, PEP 364
Diffstat (limited to 'ReleaseNotes.htm')
-rw-r--r--ReleaseNotes.htm2303
1 files changed, 1205 insertions, 1098 deletions
diff --git a/ReleaseNotes.htm b/ReleaseNotes.htm
index 8022d55..b7f1c10 100644
--- a/ReleaseNotes.htm
+++ b/ReleaseNotes.htm
@@ -1,10 +1,11 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html xmlns:v="urn:schemas-microsoft-com:vml">
-<head>
- <style>
+ <head>
+ <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
+ <style>
st1\:*{behavior:url(#ieooui) }
</style>
- <style>
+ <style>
<!--
/* Font Definitions */
@font-face
@@ -947,7 +948,7 @@ ul
{margin-bottom:0in;}
-->
</style>
- <style>
+ <style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
@@ -962,1099 +963,1205 @@ ul
font-size:10.0pt;
font-family:"Times New Roman"}
</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>
- <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">
-<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>
-<b>PEP #:</b> 359<br>
-</span></p>
-<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release
-Notes for OpenPegasus version 2.11.0</p>
-<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 23
-March 2011</p>
-<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>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%;" id="table1"
- border="1" cellpadding="0" cellspacing="1" height="155" 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;"
- height="27">
- <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;"
- height="27">
- <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;"
- height="27">
- <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;"
- height="27">
- <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;" height="22">
- <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;" align="left" height="22">
- <p class="MsoNormal" style="text-align: center;" align="center"> <font
- size="2"><span style="font-family: Arial;">23 March 2011</span></font></p>
- </td>
- <td style="padding: 0.75pt;" align="left" height="22">
- <p class="MsoNormal" style="text-align: center;" align="center"> <span
- style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p>
- </td>
- <td style="padding: 0.75pt;" height="22">
- <p class="MsoNormal"><span
- style="font-family: Arial; color: black;"><font size="2">Initial
-Submission&nbsp;<span style="color: red;"></span></font><o:p><font
- size="2"> </font></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td style="padding: 0.75pt;" align="center" height="21">&nbsp;</td>
- <td style="padding: 0.75pt;" align="center" height="21">&nbsp;</td>
- <td style="padding: 0.75pt;" align="center" height="21">&nbsp;</td>
- <td style="padding: 0.75pt;" height="21">&nbsp;</td>
- </tr>
- <tr style="">
- <td style="padding: 0.75pt;" align="center" height="21">&nbsp;</td>
- <td style="padding: 0.75pt;" align="center" height="21">&nbsp;</td>
- <td style="padding: 0.75pt;" align="center" height="21">&nbsp;</td>
- <td style="padding: 0.75pt;" height="21">&nbsp;</td>
- </tr>
- <tr>
- <td style="padding: 0.75pt;" align="center" height="21">&nbsp;</td>
- <td style="padding: 0.75pt;" align="center" height="21">&nbsp;</td>
- <td style="padding: 0.75pt;" align="center" height="21">&nbsp;</td>
- <td style="padding: 0.75pt;" height="21">&nbsp;</td>
- </tr>
- <tr style="">
- <td style="padding: 0.75pt;" align="center" height="23">&nbsp;&nbsp;</td>
- <td style="padding: 0.75pt;" align="center" height="23">&nbsp;&nbsp;</td>
- <td style="padding: 0.75pt;" align="center" height="23">&nbsp;&nbsp;</td>
- <td style="padding: 0.75pt;" height="23">&nbsp;&nbsp;</td>
- </tr>
- </tbody>
-</table>
-<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.11.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.</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>
-<h2 style="margin-bottom: 1px;"><b><o:p><font size="5">&nbsp;Contents</font></o:p></b></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><span style="color: black;">Availability
-of this Release</span></h2>
-<p>This release is available in a number of forms including:</p>
-<ul>
- <li><b>Source release</b> in both ZIP (and ZIP EXE) 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>&nbsp;</li>
- <li><b>OpenPegasus&nbsp;source RPMs</b> on the OpenPegasus web site..
-A source RPM is&nbsp; 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><b>The Pegasus CVS repository</b>. 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>
-<p>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.</p>
-</div>
-<div class="Section1">
-<h2><span style="color: black;">OpenPegasus Functionality for This
-Release</span></h2>
-Pegasus overall status by release is defined by&nbsp; a
-<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status
-WEB Page</a>
-that is available on the OpenPegasus web site .&nbsp; That web page
-shows the
-Pegasus users and developers the status of the various features found
-in Pegasus
-using a simple color coded key (white, red, yellow, green) and a
-description of
-each feature.
-<p>Pegasus 2.11.0
-is a major release, extending the previous Pegasus release in selected
-areas as described in the Pegasus&nbsp; PEP defining this release
-.&nbsp; </p>
-<p>The major areas of development for this release&nbsp; 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:</p>
-<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font
- style="font-weight: bold;" size="4">&nbsp;&nbsp;&nbsp; Table of Major
-Changes for this Release</font></p>
-<table style="font-family: Arial;" bordercolordark="#666666"
- bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="82%">
- <tbody>
- <tr align="center">
- <th bgcolor="#00ffff">PEP/BUG #</th>
- <th bgcolor="#00ffff">Description of Change</th>
- <th bgcolor="#00ffff" width="128">Posted PEP<br>
-Version</th>
- </tr>
- <tr>
- <td>PEP 318</td>
- <td>Run 32 bit providers in 64 bit OpenPegasus</td>
- <td style="text-align: center;"><a
- href="http://www.openpegasus.org/pp/uploads/40/23224/PEP_318_32bit_providers_in_64bit_OpenPegasusVer10.htm">1.0</a></td>
- </tr>
- <tr align="center">
- <td style="text-align: center;" width="7%">PEP 356</td>
- <td align="left" width="75%">Provider Module Grouping</td>
- <td width="128"> <a
- href="http://www.openpegasus.org/pp/uploads/40/22030/PEP356_ProviderModuleGrouping.htm">2.2</a><br>
- </td>
- </tr>
- <tr>
- <td style="text-align: center;" width="7%">PEP 357</td>
- <td align="left" width="75%">SNMP V3 Trap Generation in Pegasus
-Indication Handler</td>
- <td style="text-align: center;" width="128"><a
- href="http://www.openpegasus.org/pp/uploads/40/23237/PEP_357_-_SNMP_v3_trap_generation_in_Pegasus_.htm">1.0</a></td>
- </tr>
- <tr align="center">
- <td style="text-align: center;" width="7%">PEP 324<br>
- </td>
- <td align="left" width="75%">DMTF Indications Profile (DSP 1054)
-Implementation, stage 2 <br>
- </td>
- <td width="128"><a
- href="http://www.openpegasus.org/pp/uploads/40/22529/PEP324-DMTF_Indications_Profile_stage2_Ver11.html">1.1</a></td>
- </tr>
- <tr align="center">
- <td style="text-align: center;" width="7%">PEP 349<br>
- </td>
- <td align="left" width="75%"><span style="color: windowtext;"><span
- style=""></span>Improve the
-availability of the CIMOM by better isolation from faulty providers</span></td>
- <td width="128"> <a
- href="http://www.openpegasus.org/pp/uploads/40/22386/PEP_349_-_Improve_the_availability_of_the_CIMOM_by_better_isolation_from_faulty_providers.htm">0.5</a></td>
- </tr>
- <tr>
- <td style="text-align: center;"><a
- href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8787">Bug 8787</a><br>
- </td>
- <td>Add External SLP support to release builds<br>
- </td>
- <td style="text-align: center;"> <a
- href="http://www.openpegasus.org/pp/uploads/40/21277/PEP350_MultiCIMOM.htm">
- </a></td>
- </tr>
- <tr>
- <td style="text-align: center;"> <a
- href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8800">Bug 8800<br>
- </a></td>
- <td> <span class="norm"><a name="comtag_90"></a>enable
-PEGASUS_USE_RELEASE_CONFIG_OPTIONS build option to have true/false
-values</span><br>
- </td>
- <td style="text-align: center;"><br>
- </td>
- </tr>
- <tr>
- <td style="text-align: center;"><a
- href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8806">Bug
-8806</a></td>
- <td>Diagnose data for BAD UTF8 exception</td>
- <td>&nbsp;</td>
- </tr>
- <tr>
- <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8825">Bug
-8825</a></td>
- <td>Option to specify multiple provider dirs for release builds</td>
- <td>&nbsp;</td>
- </tr>
- <tr>
- <td style="text-align: center;"><a
- href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8839">Bug
-8839</a></td>
- <td>OOP Provider recovery enhancement</td>
- <td>&nbsp;</td>
- </tr>
- <tr>
- <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8845">Bug
-8845</a></td>
- <td><font size="1"><big><big>Enhance SSL Certificate info to
-expose the whole certificate</big></big><br>
- </font></td>
- <td>&nbsp;</td>
- </tr>
- <tr align="center">
- <td style="text-align: center;" width="7%"> <a
- href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8871">Bug 8871<br>
- </a> </td>
- <td align="left" width="75%"><span
- style="text-decoration: underline;">Enhance WSMan Server Adpater&nbsp;
-to include enumeration association filters</span></td>
- <td width="128">&nbsp;<br>
- </td>
- </tr>
- <tr align="center">
- <td style="text-align: center;" width="7%">&nbsp;</td>
- <td align="left" width="75%"> </td>
- <td width="128"><a
- href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8171"><br>
- </a></td>
- </tr>
- </tbody>
-</table>
-<p>The status of several components of Pegasus functionality change
-status
-between Pegasus versions. <span class="norm"><a name="comtag_116">Features
-that
-have changed status can be identified by a change in color from the
-previous
-release to this release</a></span> on the
-<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status
-WEB Page</a>.</p>
-<p>Finally, a significant number of internal changes and corrections
-were made
-under the control of the Pegasus bugzilla bug system. See the bug
-section below
-for more information.</p>
-<h3><font color="#000000">Information on&nbsp; IPv6 Support (PEP 291)</font></h3>
-<p><b>NOTE:</b> This functionality was incorporated in OpenPegasus
-2.7.0 but it
-was felt that the information below was worth repeating in subsequent
+ <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>
+ </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="Section1">
+ <div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;">
+ <hr color="#009900" align="center" 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;">OpenPegasus 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>
+ <b>PEP #:</b> 364<br>
+ </span></p>
+ <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release
+ Notes for OpenPegasus version 2.12.0</p>
+ <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 10
+ September 2012<br>
+ </p>
+ <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>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%;" id="table1" height="155"
+ 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;"
+ height="27">
+ <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;"
+ height="27">
+ <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;"
+ height="27">
+ <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;"
+ height="27">
+ <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;" height="22">
+ <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;" height="22" align="left">
+ <p class="MsoNormal" style="text-align: center;" align="center"> <font
+ size="2"><span style="font-family: Arial;">10 September 2012<br>
+ </span></font></p>
+ </td>
+ <td style="padding: 0.75pt;" height="22" align="left">
+ <p class="MsoNormal" style="text-align: center;" align="center"> <span
+ style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p>
+ </td>
+ <td style="padding: 0.75pt;" height="22">
+ <p class="MsoNormal"><span style="font-family: Arial; color: black;"><font
+ size="2">Initial Submission&nbsp;<span style="color: red;"></span></font><o:p><font
+ size="2"> </font></o:p></span></p>
+ </td>
+ </tr>
+ <tr>
+ <td style="padding: 0.75pt;" height="21" align="center">&nbsp;1.01</td>
+ <td style="padding: 0.75pt;" height="21" align="center">10 September
+ 2012 <br>
+ </td>
+ <td style="padding: 0.75pt;" height="21" align="center">Karl
+ Schopmeyer <br>
+ </td>
+ <td style="padding: 0.75pt;" height="21">&nbsp;Minor fixes and
+ complete links to PEPs<br>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt;" height="21" align="center">&nbsp;1.1</td>
+ <td style="padding: 0.75pt;" height="21" align="center">11 September
+ 2012 <br>
+ </td>
+ <td style="padding: 0.75pt;" height="21" align="center">Karl
+ Schopmeyer <br>
+ </td>
+ <td style="padding: 0.75pt;" height="21">&nbsp;Incorporate all
+ comments from first review<br>
+ </td>
+ </tr>
+ <tr>
+ <td style="padding: 0.75pt;" height="21" align="center">&nbsp;1.2</td>
+ <td style="padding: 0.75pt;" height="21" align="center">18 September
+ 2012 <br>
+ </td>
+ <td style="padding: 0.75pt;" height="21" align="center">Karl
+ Schopmeyer <br>
+ </td>
+ <td style="padding: 0.75pt;" height="21">&nbsp;Fix comments on bug
+ 8830 (compatibility considerations) and bug 9172(repupgrade)<br>
+ </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt;" height="23" align="center">&nbsp;&nbsp;</td>
+ <td style="padding: 0.75pt;" height="23" align="center">&nbsp;&nbsp;</td>
+ <td style="padding: 0.75pt;" height="23" align="center">&nbsp;&nbsp;</td>
+ <td style="padding: 0.75pt;" height="23">&nbsp;&nbsp;</td>
+ </tr>
+ </tbody>
+ </table>
+ <div class="MsoNormal" style="text-align: center;" align="center"> <span
+ style="color: black;">
+ <hr color="#009900" align="center" noshade="noshade" size="2" width="100%"></span></div>
+ <p><b>Abstract:</b> 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.</p>
+ <div class="MsoNormal" style="text-align: center;" align="center"> <span
+ style="color: black;">
+ <hr color="#009900" align="center" noshade="noshade" size="2" width="100%"></span></div>
+ <h2 style="margin-bottom: 1px;"><b><o:p><font size="5">&nbsp;Contents</font></o:p></b></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
-Notes</p>
-<p style="color: rgb(153, 51, 153);"><font color="#000000">IPv6 is
-short for "Internet
-Protocol
-Version 6". IPv6 is the "next generation" protocol designed by the IETF
-to replace the current version Internet Protocol, IP Version 4
-("IPv4"). IPv6 Support for OpenPegasus is documented in </font> <a
- href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">
-<font color="#3333ff">PEP
-291</font></a><font color="#000000">.</font></p>
-<p>The IPv6 support in OpenPegasus is
-controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for
-this
-variable is "true"; setting this to
-'false' before building OpenPegasus will disable the IPv6 support.<br>
-</p>
-<p>The following subsections provide
-some information on IPv6 support for the Linux and Windows platforms.
-Note that in the 2.6.1 release there is no automatic run-time detection
-of IPv6 support on a platform by OpenPegasus. If you build with
-PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you will
-get a build failure (missing header files), a run-time bind() failure,
-or possibly some other failure. This applies to both the CIM Server and
-Listener components. For more information on IPv6 support for your
-specific platform, refer to the documentation for that platform.<br>
-</p>
-<p>All OpenPegasus externals that
-support either a hostname or an IP address as input have been updated
-to allow an IPv6 address to be specified. If the required input is just
-an IP address (eg. no optional or required port number), then the IPv6
-address must be specified without brackets. For example, the
-OpenPegasus osinfo client (which returns information about the OS
-running on a host system) takes separate host and port options. In this
-case a host with an IPv6-configured network interface would be
-specified as:<br>
-</p>
-<div
- style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font
- color="#000000">osinfo -h
-3ffe:1:2:1 -p 5988</font></big></div>
-<p>But the cimcli command, which
-takes
-an optional "location" option including an optional port number,
-requires the IPv6 address to be delimited with brackets, for example:<br>
-</p>
-<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns
--l [3ffe:1:2:1]</big></div>
-<p>or</p>
-<div style="margin-left: 40px;"><big><span
- style="font-family: monospace;">cimcli ns -l [3ffe:1:2:1]:5989</span></big><br>
-</div>
-<br>
-For more information on
-specifying
-IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF
-RFC 2373 - IP Version
-6 Addressing Architecture</a>
-and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 -
-Format for
-Literal IPv6 Addresses in URL's</a>.<br>
-<h4><font color="#000000">IPv6 on Linux</font></h4>
-<p>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.</p>
-<p><span style="font-weight: bold;">Note:
-</span>you shouldn't&nbsp;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.<br>
-</p>
-<p>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:<br>
-</p>
-<div
- style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font
- color="#000000">test -f
-/proc/net/if_inet6 &amp;&amp; echo "Running kernel is IPv6 ready"</font></big></div>
-<p>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>.<br>
-<br>
-<span style="font-weight: bold;">Warning</span>:
-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 <span style="color: rgb(153, 51, 153);">
-<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus
-bug 6586</a>
-</span>and<span style="color: rgb(153, 51, 153);">
-<a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat
-bug 248052</a>,
-</span>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.</p>
-<h4><font color="#000000">IPv6 on Windows</font></h4>
-<p>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.</p>
-On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span>
-tool to install, uninstall, and
-query
-your IPv6 configuration. For example:<br>
-<br>
-<div
- style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font
- color="#000000">ipv6 install<br>
-ipv6 if</font></big></div>
-<p>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.<br>
-<br>
-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</font></a>.<br>
-</p>
-<h4><font color="#000000">Testing your OpenPegasus IPv6
-support</font></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.<br>
-<br>
-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:<br>
-<div style="margin-left: 40px;"><br>
-<big style="font-family: monospace;"> osinfo -h ::1</big></div>
-<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2>
-<p>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
+ Control and Version Definition Documentation</a></li>
+ <li><a href="#General%20Documentation">General Documentation</a></li>
+ </ol>
+ <h2><span style="color: black;">Availability of this Release</span></h2>
+ <p>This release is available in a number of forms including:</p>
+ <ul>
+ <li><b>Source release</b> in both ZIP (and ZIP EXE) 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>&nbsp;</li>
+ <li><b>OpenPegasus&nbsp;source RPMs</b> on the OpenPegasus web site.. A
+ source RPM is&nbsp; 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><b>TheOpenPegasus CVS repository</b>. 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>
+ <p>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.</p>
+ </div>
+ <div class="Section1">
+ <h2><span style="color: black;">OpenPegasus Functionality for This Release</span></h2>
+ OpenPegasus overall status by release is defined by&nbsp; a <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature
+ Status WEB Page</a> that is available on the OpenPegasus web site
+ .&nbsp; 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.
+ <p>OpenPegasus 2.12.0 is a major release, extending the previous Pegasus
+ release in selected areas as described in the Pegasus&nbsp; PEP defining
+ this release . <br>
+ </p>
+ <p>NOTE: OpenPegasus releases are categorized as follows:</p>
+ <ul>
+ <li>First number of version changes (ex. 2.x.x to 3.0.0) -&nbsp; Major
+ release includes major functionality change and&nbsp; incompatible
+ behavior changes and/or incompatible public API changes, <br>
+ </li>
+ <li>Second number changes (ex 2.11.0 2.12.0) -&nbsp; Minor Release and
+ includes new functionality but maintains behavior and public API
+ compatibility, <br>
+ </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>
+ <p><u><b>ALL</b></u> changes for each release are documented in the
+ OpenPegasus bug data base by tagging each bug(keyword field of
+ bug).&nbsp; No change to Pegasus is committed with out this tag on the
+ bug. Changes for this minor release are&nbsp; tagged 2.12.0_APPROVED.
+ All changes for this minor release can be viewed through&nbsp; this link
+ to the OpenPegasus bugzilla&nbsp;<a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.0_APPROVED">
+ Pegasus 2.12.0_APPROVED bug list. Bugs.&nbsp; </a>Bugs marked as
+ enhancements can be reviewed through the this <a href="http://bugzilla.openpegasus.org/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=CIM+Server+Core&amp;product=CIMClient+Application&amp;product=CIMClient+DefaultCPlusPlus&amp;product=CIMClient+Java-SNIA&amp;product=CIMConsumer+DefaultCPlusPlus&amp;product=CIMIndicationHandler&amp;product=CIMListener+Dynamic&amp;product=CIMListener+Standalone&amp;product=CIMProvider+CMPI&amp;product=CIMProvider+CMPIRemote&amp;product=CIMProvider+DefaultCPlusPlus&amp;product=CIMProvider+Instrumentation&amp;product=CIMProvider+JMPI&amp;product=CIMSchema&amp;product=CIMServer+Administration&amp;product=CIMServer+Administration+Command&amp;product=CIMServer+Administration+Profiles&amp;product=CIMServer+ProviderManagement&amp;product=CIMServer+Repository&amp;product=CIMServer+SLP&amp;product=OpenPegasus+Build+System&amp;product=OpenPegasus+Documentation&amp;product=OpenPegasus+Security+Defects&amp;product=OpenPegasusProject+Bugzilla&amp;product=OpenPegasusProject+CVS&amp;product=OpenPegasusProject+Website&amp;product=PegasusCIMOM&amp;product=PegasusGeneral&amp;product=RPM+CIMServer&amp;product=TestProduct&amp;product=Unsupported&amp;product=WMI+Mapper&amp;long_desc_type=substring&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=allwordssubstr&amp;status_whiteboard=&amp;keywords_type=allwords&amp;keywords=2.12.0_APPROVED&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=RESOLVED&amp;bug_status=VERIFIED&amp;bug_status=CLOSED&amp;emailtype1=substring&amp;email1=&amp;emailassigned_to2=1&amp;emailreporter2=1&amp;emailqa_contact2=1&amp;emailcc2=1&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfield=[Bug+creation]&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=bug_severity&amp;type0-0-0=equals&amp;value0-0-0=enhancement">link
+ to OpenPegasus bugzilla 2.12.0 enhancement bugs</a> .&nbsp; 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).<br>
+ </p>
+ <p>The major areas of development including both enhancements and bug
+ fixes for this release&nbsp; 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:</p>
+ <p style="margin-top: 0pt; margin-bottom: 0pt;" align="left">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font
+ style="font-weight: bold;" size="4">&nbsp;&nbsp;&nbsp; Table of Major
+ Changes for this Release</font></p>
+ <table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC"
+ border="1" cellspacing="1" width="82%">
+ <tbody>
+ <tr align="center">
+ <th bgcolor="#00ffff">PEP/BUG #</th>
+ <th bgcolor="#00ffff">Description of Change</th>
+ <th bgcolor="#00ffff" width="128">Posted PEP<br>
+ Version</th>
+ </tr>
+ <tr>
+ <td align="left">PEP 360</td>
+ <td>Provider Lifecycle Indications<br>
+ </td>
+ <td style="text-align: center;"><a href="https://collaboration.opengroup.org/pegasus/pp/documents/25003/PEP360_PLI_Ver1_2.html">Ver
+ 1.2</a><br>
+ </td>
+ </tr>
+ <tr align="center">
+ <td align="left" width="7%">PEP 361</td>
+ <td align="left" width="75%">cimcli support for embedded instances<br>
+ </td>
+ <td width="128"><a href="https://collaboration.opengroup.org/pegasus/pp/origrevdocuments/3195/PEP361_CIMCLIEmbeddedInstanceSupport.htm">Ver
+ 1.1</a><br>
+ </td>
+ </tr>
+ <tr>
+ <td align="left" width="7%">PEP 304<br>
+ </td>
+ <td align="left" width="75%">Allow modification of name of interop
+ namespace<br>
+ </td>
+ <td style="text-align: center;" width="128"><a href="http://www.openpegasus.org/pp/uploads/40/23237/PEP_357_-_SNMP_v3_trap_generation_in_Pegasus_.htm"></a><a
+ href="https://collaboration.opengroup.org/pegasus/pp/documents/24686/PEP304_NamespaceRenaming.htm">Ver
+ 1.5</a><br>
+ </td>
+ </tr>
+ <tr>
+ <td align="left">PEP 358<br>
+ </td>
+ <td>WSMan indication handling and subscription support<br>
+ </td>
+ <td align="center"><a href="https://collaboration.opengroup.org/pegasus/pp/documents/26240/PEP_358_-_WSMAN_Eventing_support_in_Pegasus_.htm">Ver
+ 1.1</a><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8891">Bug
+ 8891</a><br>
+ </td>
+ <td>Enhance cimsub to add operations to create filters, destinations
+ and subscriptions<br>
+ </td>
+ <td><br>
+ </td>
+ </tr>
+ <tr align="center">
+ <td style="text-align: center;" align="left" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=5667">Bug
+ 5667</a><br>
+ </td>
+ <td align="left" width="75%">Remove experimental form buildInstance
+ and filter functions in CIMInstance class<br>
+ </td>
+ <td width="128"><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8952">Bug
+ 8952</a></td>
+ <td> Support Configurable cipher suites in OpenPegasus</td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8904">Bug
+ 8984</a></td>
+ <td>Add support for indication deliver connection pooling</td>
+ <td><br>
+ </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&nbsp; and
+ minIndicationdeliveryRetryInterval</td>
+ <td><br>
+ </td>
+ </tr>
+ <tr align="center">
+ <td style="text-align: center;" align="left" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9013">Bug
+ 9013</a><br>
+ </td>
+ <td align="left" width="75%"><span style="color: windowtext;"><span
+ style=""></span></span>Enable ordered indication delivery from
+ provider through CIMServer when
+ PEGASUS_ENABLE_DMTF_INDICATION_PROFILE compile flag is set</td>
+ <td width="128"> <a href="http://www.openpegasus.org/pp/uploads/40/22386/PEP_349_-_Improve_the_availability_of_the_CIMOM_by_better_isolation_from_faulty_providers.htm"></a><br>
+ </td>
+ </tr>
+ <tr>
+ <td style="text-align: center;" align="left"> <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8800">Bug
+ 9080 </a></td>
+ <td> <span class="norm"></span>Guaranteed provider lifecycle
+ indication delivery during CIMServer shutdonw </td>
+ <td style="text-align: center;"><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9112">Bug
+ 9112</a><br>
+ </td>
+ <td>Advertise IndicationService conformance to Indications Profileby
+ imlementing CIM_ElementConformsToProfile when
+ PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9114">Bug
+ 9114</a><br>
+ </td>
+ <td>Advertise DMTF Indications Profile (DSP1054) 1.1.0 conformance </td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9118">Bug
+ 9118</a><br>
+ </td>
+ <td>Add support for CIM_IndicationFilter.SourceNamespaces[] property<br>
+ </td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9136">Bug
+ 9136</a></td>
+ <td>Runtime configuration option to restrict cimserver to listen on
+ selected network interfaces</td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9155">Bug
+ 9155</a><br>
+ </td>
+ <td>Update to include CIM 2.31 Schema and set this as default schema<br>
+ </td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9159">Bug
+ 9159</a></td>
+ <td>
+ <table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC"
+ border="1" cellspacing="1" width="82%">
+ <tbody>
+ <tr>
+ <td>Add SSL Support to Dynamic Listener<br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9172">Bug
+ 9172</a><br>
+ </td>
+ <td>Add capability for administrator to override hostname used by
+ providers. This adds&nbsp; 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.<br>
+ </td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9215">Bug
+ 9215</a><br>
+ </td>
+ <td>Add support of CQL query language to ExecQuery operation in
+ general. When the server receives&nbsp; ExecQuery it executes
+ enumerate instance for providers that do not support ExecQuery and
+ filters result.<br>
+ </td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9209">Bug
+ 9209 </a><br>
+ </td>
+ <td>Add operations for display class tree and counting instances to
+ cimcli<br>
+ </td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9227">Bug
+ 9227</a><br>
+ </td>
+ <td>Enhance cimsub for batches of subscription oriented operations<br>
+ </td>
+ <td><br>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9229">Bug
+ 9229</a><br>
+ </td>
+ <td><a name="comtag_197">Add gcc build support on hp-ux for the
+ Common, Client and General libraries.</a></td>
+ <td><br>
+ </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.<br>
+ </td>
+ <td><br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>The status of several components of Pegasus functionality change status
+ between Pegasus versions. <span class="norm"><a name="comtag_116">Features
that
-significantly affects interoperability) that may require the Community
-to make
-potentially incompatible changes. The following table contains a list
-of defect
-fixes that MAY impact, even well-behaved, OpenPegasus Providers or
-Clients when
-upgrading to this OpenPegasus release.</p>
-<p>&nbsp;</p>
-<table style="font-family: Arial;" bordercolordark="#666666"
- bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="80%">
- <tbody>
- <tr align="center">
- <th bgcolor="#00ffff" width="10%">Bugzilla #</th>
- <th bgcolor="#00ffff">Description</th>
- </tr>
- <tr align="center">
- <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8830">8830</a></td>
- <td align="left">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>
- <tr align="center">
- <td></td>
- <td></td>
- </tr>
- <tr align="center">
- <td></td>
- <td></td>
- </tr>
- <tr align="center">
- <td></td>
- <td></td>
- </tr>
- <tr align="center">
- <td></td>
- <td></td>
- </tr>
- </tbody>
-</table>
-<h2>OpenPegasus Relationship to
-CIM/WBEM Standards</h2>
-<p>Pegasus was designed and implemented to comply with the DMTF
-CIM/WBEM specifications The following table defines the level of the
-DMTF specifications to which this version of Pegasus aims to conform
-today.</p>
-<table id="AutoNumber1" border="1" cellspacing="1" width="80%">
- <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 Infrastructure Specification</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%">Version 1.2, Final, January 09, 2007</td>
- </tr>
- <tr>
- <td width="33%">DSP 0201 - Representation of CIM in XML</td>
- <td width="33%">Version 2.2 Final, January 09, 2007</td>
- </tr>
- <tr>
- <td width="33%">DSP 0202 - CIM Query Language Specification</td>
- <td width="33%">1.0.0, preliminary, 9 December 2004</td>
- </tr>
- <tr>
- <td width="33%">DSP 0205 - WBEM Discovery using SLP</td>
- <td width="33%">1.0, preliminary, 27 January 2004</td>
- </tr>
- <tr>
- <td width="33%">DSP 0206 - WBEM SLP Template</td>
- <td width="33%">1.0.0, Preliminary, January 2004</td>
- </tr>
- <tr>
- <td width="33%">CIM Schema </td>
- <td width="33%">2.22.1 Final,&nbsp; 22 Oct 2009( default) </td>
- </tr>
- </tbody>
-</table>
-<h2><a name="Conformance with DMTF Specifications">Conformance
-Exceptions to
-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.&nbsp; 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><b>Indications </b>-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.<font
- color="#ff0000"> </font><span class="norm"><font color="#ff0000">&nbsp;</font>For
-more information see the Pegasus CVS file:<a name="comtag_137"><font
- size="2"> </font><font face="Courier New" size="2">&nbsp;pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a><font
- size="2">.</font></span></li>
- <li>
- <p class="MsoNormal"><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 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.&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. &nbsp;When Pegasus uses object normalization,
-the normalizer does apply qualifiers to returned instances if the
-includeQualifiers operation parameter is set.</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 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>
- <p class="MsoNormal"><b>MultiRequest Operations</b> - Pegasus
-does not support the DMTF defined MultiRequest Operation option.</p>
- </li>
- <li>
- <p class="MsoNormal"><b>MOF Compiler namespace pragma</b> - The
-Pegasus compiler does not support the namespace pragma.</p>
- </li>
- <li><b>CIMOperation Trailer </b>- 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.&nbsp;</li>
- <li><span style="font-weight: bold;">Whitespace in XML value Element</span>
-- Pegasus trims the leading and trailing whitespace from XML value
-elements that are of the Type String. &nbsp;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. &nbsp;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 modified until a major version update. &nbsp;These bugs are
-documented with the Bugzilla tag <big style="font-weight: bold;"><samp>"3.0_TARGET".</samp></big></li>
- <li><span style="font-weight: bold;">modifyInstance operation
-behavior in the Pegasus repository does not match the DMTF specification</span>.
-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>
-</ol>
-<h2><b><span style="font-family: Times;">OpenPegasus <a
- name="Supported Platforms">Supported
-Platforms</a></span></b></h2>
-<p align="left">Each OpenPegasus release lists as 'active' platforms
-those
-hardware/software platforms that have recognized ports for the Pegasus
-code base
-including a maintainer for the platform that will be willing to
-regularly
-document issues and/or fix defects as the Pegasus code base is
-changed.&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;&nbsp;
-The platforms that are considered ported are shown in the two tables
-below.&nbsp;
-The first table represents platform sofr which testing is done on a
-regular
-basis and reported to the Pegasus Nightly Build Test WEB Page. Those
-platforms
-which have been ported but do not have test results that are current at
-the time
-of the release are reported in the second table.</p>
-<b>Actively Supported Platforms (Nightly Tests Reported for this
-release)</b>
-<table class="MsoNormalTable" style="width: 90%;" border="1"
- cellpadding="0" cellspacing="1">
- <tbody>
- <tr style="">
- <td
- style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;"
- height="26">
- <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(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;"
- height="26">
- <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;">
- <p class="MsoNormal"><span style="color: black;">HP-UX<o:p>
-PA_RISC and Itanium</o:p></span></p>
- </td>
- <td style="padding: 0.75pt;">
- <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;">
- <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;">
- <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;">
- <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;">
- <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;">
- <p class="MsoNormal"><span style="color: black;">Linux Itanium<o:p></o:p></span></p>
- </td>
- <td style="padding: 0.75pt;">
- <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;"> <span style="color: black;"><font
- size="3">Linux IA-32</font></span></td>
- <td style="padding: 0.75pt;"> <span class="SpellE"><span
- style="color: black;"><font size="3">gcc</font></span></span><span
- style="color: black;"><font size="3">
-(versions 3.xx, 4.xx)</font><o:p></o:p></span></td>
- </tr>
- <tr style="">
- <td style="padding: 0.75pt;">
- <p class="MsoNormal"><span style="color: black;">Linux X86_64<o:p></o:p></span></p>
- </td>
- <td style="padding: 0.75pt;">
- <p class="MsoNormal"><span class="SpellE"><span
- style="color: black;">gcc</span></span><span style="color: black;">
-(versions 3.xx, 4.xx)</span></p>
- </td>
- </tr>
- <tr>
- <td style="vertical-align: top;"><font size="3">z/OS V1.7 and up</font></td>
- <td style="vertical-align: top;"><font size="3">XL C/C++ from
-z/OS Version 1.7 and up</font></td>
- </tr>
- </tbody>
-</table>
-&nbsp;
-<p align="center"><b>Platforms not Actively supported for this release
-(No
-current Nightly Build Test Results</b></p>
-<table class="MsoNormalTable" style="width: 90%;" id="table2" border="1"
- cellpadding="0" cellspacing="1">
- <tbody>
- <tr style="">
- <td
- style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;"
- height="26">
- <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(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;"
- height="26">
- <p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span
- style="color: black;"><o:p></o:p></span></p>
- </td>
- </tr>
- <tr>
- <td style="padding: 0.75pt;"> <font size="3">Windows XP</font>
- <p></p>
- </td>
- <td style="padding: 0.75pt;"> <font size="3">Microsoft Visual
-C++ Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++
-Ver. 6 no longer being regular tested. </font> </td>
- </tr>
- <tr style="">
- <td style="padding: 0.75pt;"> <font size="3">MacOS version 10.3
-and higher</font></td>
- <td style="padding: 0.75pt;"> <font size="3">gcc 4.01</font></td>
- </tr>
- <tr>
- <td style="vertical-align: top;"><big><font color="RED"><span
- style="color: rgb(0, 0, 0);">Solaris 8</span></font></big></td>
- <td style="vertical-align: top;"><big>GNU&nbsp; 2.95.3,&nbsp; Sun
-CC compiler V 5.8. Note that the latest thread patch (108993) may be
-required. (see Pegasus bug 4632)</big><br>
- </td>
- </tr>
- <tr>
- <td style="vertical-align: top;"><span class="norm"></span><big><font
- color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9</span></font></big></td>
- <td style="vertical-align: top;"><big>GNU&nbsp; 2.95.3, Sun
-WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br>
- </td>
- </tr>
- <tr>
- <td><big>HP OpenVMS 8.3 or later Alpha</big></td>
- <td><big><font style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span
- style="color: rgb(153, 51, 153);">7.3-009 or later required</span> for
-OpenVMS
-Alpha</font></big></td>
- </tr>
- <tr>
- <td><big><font style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or
-later IA64</font></big></td>
- <td><big><font style="color: rgb(0, 0, 0);">HP C++ V7.</font><font
- color="#993399">3-023 or later required</font><font
- style="color: rgb(0, 0, 0);"> on OpenVMS IA64</font></big></td>
- </tr>
- <tr>
- <td style="padding: 0.75pt;">
- <p class="MsoNormal"><span style="color: black;">Windows 2000</span></p>
- </td>
- <td style="padding: 0.75pt;"> <font size="3">Microsoft Visual
-C++ Ver.&nbsp; 6 and Microsoft .Net compiler version.&nbsp;Works on VC
-.NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being regularly
-tested.</font></td>
- </tr>
- <tr>
- <td style="padding: 0.75pt;"> <font size="3">Windows 2003</font>
- <p></p>
- </td>
- <td style="padding: 0.75pt;"> <font size="3">Microsoft Visual
-C++ Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++
-Ver. 6 no longer being regular tested. </font> </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>
-<p><b>Platform patches</b>
-</p>
-<p style="margin-top: 0pt; margin-bottom: 0pt;"><font
- style="color: rgb(0, 0, 0);">The following is a list known of platform
-patches Pegasus requires.</font></p>
-<div style="margin-left: 40px;">
-<ol>
- <li>
- <p style="margin-top: 0pt; margin-bottom: 0pt;"> <font
- style="color: rgb(0, 0, 0);">RHAS
-2.1 needs the update to fix Red Hat Bugzilla 98815.</font></p>
- </li>
- <li>
- <p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4
-multithreading bug in
-getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is
-fixed in
-RHEL 4.5</p>
- </li>
- <li>
- <p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE
-Linux multiple versions -
-multithreaded client intermittently fails connecting to IPv6 (Pegasus
-Bugzilla
-6586) (Red Hat bug 248052)<br>
- </p>
- </li>
-</ol>
-</div>
-<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> 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>
-<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</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;&nbsp;
-Effective with the start of the Pegasus 2.6 work, all changes to the
-CVS tree are documented through bugs.&nbsp; Bugs reports are filed not
-only for bugs and
-their corresponding fixes but also as part of the process of committing
-new code
-representing the work on PEPs done for Pegasus 2.6 and all subsequent
-versions.&nbsp; Therefore, a search of
-the Open Pegasus bugzilla base for bugs with the tag for a particular
-version
-(ex.&nbsp;
-<a
- href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED">2.6.0_APPROVED</a>,
-<a
- href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED">
-2.6.1_APPROVED</a>,
-<a
- href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>,
-etc) will yield all changes to
-the Pegasus CVS tree for that Pegasus release.</p>
-<p>
-&nbsp;&nbsp;&nbsp;&nbsp; - Changes for this release (bugs Tagged
-2.11.0_APPROVED). The link is&nbsp;<a
- href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.11.0_APPROVED">
-Pegasus 2.11.0_APPROVED bug list.</a></p>
-<h2><a
- name="Pegasus Release Control and Version Definition Documentation">Release
-Control and Version Definition Documentation</a></h2>
-<p>The Pegasus project is controlled largely through the CVS repository
-and a set of documents
-(PEPs) that serve both as the definition and review mechanism for new
-and
-modified Pegasus functionality and for the definition and documentation
-of releases.</p>
-The following documentation defines the characteristics of this Pegasus
-release. The documents are available&nbsp;in the OpenPegasus CVS
-repository.
-<br>
-<ul>
- <li><b> OpenPegasus Release Definition/Status -No PEP (See Wiki
-Section <a
- href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_11_x">OpenPegasus
-2.11.x Release Status</a>) - <span style="font-weight: normal;">A&nbsp;
-section in the Pegasus wiki is used
-throughout the development of this version as the control point for
-functionality that will go into the release and points to all of the
-PEPs that represent the Pegasus&nbsp; functionality changes for this
-version of Pegasus</span>.&nbsp;</b></li>
- <b> </b><span style="font-weight: bold;"></span><b>OpenPegasus&nbsp;
-Build and Configuration
-Options&nbsp; for Selected
-Platforms -&nbsp; <span style="font-weight: normal;">In previous
-versions of Pegasus this information was&nbsp; released as a Pegasus
-PEP. Starting with Pegasus 2.9.0 the information is located in the
-OpenPegasus CVS repository as <big style="font-weight: bold;"> <span
- style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</span></big>.</span></b><b>
- <li> OpenPegasus External Interfaces -<span
- style="font-weight: normal;">The list of the OpenPegasus interfaces
-that are considered external and therefore "frozen". Unless an
-exception is explicitly approved by the Steering Committee all
-subsequent releases of Pegasus MUST continue to support these
-interfaces. Interfaces not explicitly listed in this document, should
-be considered as internal and subject to change.In previous Pegasus
-releases this information was available as a separate PEP. Starting
-with Pegasus 2.9.0 this information is integrated into the Pegasus
-repositoryas&nbsp; </span><small style="font-weight: bold;"><font
- face="Courier New" size="4"><small>pegasus/doc/EnternalInterface.html</small></font></small><span
- style="font-weight: normal;">.</span></li>
- </b> <li><b> OpenPegasus&nbsp; SDK Packaging Definition - <span
- style="font-weight: normal;">Defines the recommended set of files for
-inclusion in the OpenPegasus
-SDK. Starting with Pegasus release 2.11.0, this document is available
-in the Pegasus CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>.
-In
-previous Pegasus releases this document was made available as s
-separate Pegasus PEP document rather than in the CVS repository.</span>&nbsp;
- </b></li>
- <b> </b> <b> <li>&nbsp;Pegasus&nbsp; Runtime Packaging Definition
--&nbsp;<span style="font-weight: normal;">Defines the recommended set
-of files for inclusion in this OpenPegasus
-release. Starting with Pegasus release 2.11.0, this 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. </span>&nbsp;</li>
- </b> <b> <li>Pegasus Release Notes -&nbsp;<span
- style="font-weight: normal;"> </span>PEP 355 - <span
- style="font-weight: normal;"> (This document is located in the
-approved PEP repository and the OpenPegasus source tree root directory (<big
- style="font-weight: bold;"><span style="font-family: monospace;">pegasus/ReleaseNotes.htm</span></big>)</span></li>
- </b>
-</ul>
-<h2><b><a name="General Documentation">General Documentation</a></b></h2>
-<p><b>The following documentation is available for the this Pegasus
-release:</b></p>
-<ul style="margin-top: 0in;" type="disc">
- <b> <li class="MsoNormal" style="color: black;"><b>Utilities</b> - </li>
- </b>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> <b> <li
- class="MsoNormal" style="color: black;"><b>API and&nbsp; usage
-documentation</b> - </li>
- </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. <b> <li
- class="MsoNormal" style="color: black;"><b>Building and Debugging
-Providers </b>- </li>
- </b>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. <b> <li class="MsoNormal"
- style="color: black;"><b>Building and Debugging
-Clients</b> - </li>
- </b>API documentation and the documentation on the Pegasus
-Technical Workshop which is available on the Pegasus web site. <b> <li
- class="MsoNormal" style="color: black;"><b>PEPs</b> - </li>
- </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.
-</ul>
-<hr>Licensed to The Open Group (TOG) under one or more contributor
-license
-agreements. Refer to the OpenPegasusNOTICE.txt file distributed with
-this work for additional information regarding copyright ownership.
-Each contributor licenses this file to you under the OpenPegasus Open
-Source License; you may not use this file except in compliance with the
-License.
-<p>Permission is hereby granted, free of charge, to any person
-obtaining a
-copy of this software and associated documentation files (the
-"Software"),
-to deal in the Software without restriction, including without
-limitation
-the rights to use, copy, modify, merge, publish, distribute,
-sublicense,
-and/or sell copies of the Software, and to permit persons to whom the
-Software is furnished to do so, subject to the following conditions:</p>
-<p>The above copyright notice and this permission notice shall be
-included
-in all copies or substantial portions of the Software.</p>
-<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
-</div>
-</body>
+have
+ changed status can be identified by a change in color from the
+ previous release to this release</a></span> on the <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature
+ Status WEB Page</a>.</p>
+ <h3><b>Information on Interop namespace name (root/PG_InterOp) for
+ OpenPegasus 2.12<br>
+ </b></h3>
+ <p>Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable
+ to define "root/PG_InterOp" as the name for the OpenPegasus namespace
+ with no defined way to change this variable.&nbsp; Note that an
+ unsupported method involving editing one file and rebuilding OpenPegasus
+ was defined as a workaround in the <a href="%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus
+ wiki faq</a>s.&nbsp; <br>
+ </p>
+ <p>However, since the definition of a standard name for this namespace in
+ DMTF and SNIA specifications ("interop" or "root/interop" with "interop"
+ being the preferred alternative) the use of&nbsp; "root/PG_InterOp" has
+ become an issue.<br>
+ </p>
+ <p>Effective OpenPegasus 2.12.0 a new build variable has been
+ defined&nbsp; (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).&nbsp; 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.&nbsp; The only name for the interop namespace will be the name
+ defined through this build variable.<br>
+ </p>
+ <p>However, today OpenPegasus is committed to the single namespace defined
+ at build "(root/PG_InterOp", "interop", or "root/interop"). However, a
+ number of OpenPegasus&nbsp; installations are committed to the
+ "root/PG_InterOp" name and must maintain their repositories through
+ updates of OpenPegasus. While we are working on this issue today (which
+ means that a running version of OpenPegasus must accept both the and new
+ names and not confuse clients, listeners or providers that would use
+ either name) the OpenPegasus team did not complete that work for this
+ release. See bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9250">9250</a>
+ for more information about possible solutions and our progress on a
+ solution.<br>
+ </p>
+ <p>NOTE: If you redefine the interop namespace name with
+ PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp" namespace
+ will not connect with the updated version of OpenPegasus. <br>
+ </p>
+ <h3><font color="#000000"></font></h3>
+ <h3><font color="#000000">Information on&nbsp; IPv6 Support (PEP 291)</font></h3>
+ <p><b>NOTE:</b> This functionality was incorporated in OpenPegasus 2.7.0
+ but it was felt that the information below was worth repeating in
+ subsequent Release Notes</p>
+ <p style="color: rgb(153, 51, 153);"><font color="#000000">IPv6 is short
+ for "Internet Protocol Version 6". IPv6 is the "next generation"
+ protocol designed by the IETF to replace the current version Internet
+ Protocol, IP Version 4 ("IPv4"). IPv6 Support for OpenPegasus is
+ documented in </font> <a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">
+ <font color="#3333ff">PEP 291</font></a><font color="#000000">.</font></p>
+ <p>The IPv6 support in OpenPegasus is controlled by the
+ PEGASUS_ENABLE_IPV6 build variable. The default for this variable is
+ "true"; setting this to 'false' before building OpenPegasus will disable
+ the IPv6 support.<br>
+ </p>
+ <p>The following subsections provide some information on IPv6 support for
+ the Linux and Windows platforms. Note that in the 2.6.1 release there is
+ no automatic run-time detection of IPv6 support on a platform by
+ OpenPegasus. If you build with PEGASUS_ENABLE_IPV6=true, your platform
+ must support IPv6 or you will get a build failure (missing header
+ files), a run-time bind() failure, or possibly some other failure. This
+ applies to both the CIM Server and Listener components. For more
+ information on IPv6 support for your specific platform, refer to the
+ documentation for that platform.<br>
+ </p>
+ <p>All OpenPegasus externals that support either a hostname or an IP
+ address as input have been updated to allow an IPv6 address to be
+ specified. If the required input is just an IP address (eg. no optional
+ or required port number), then the IPv6 address must be specified
+ without brackets. For example, the OpenPegasus osinfo client (which
+ returns information about the OS running on a host system) takes
+ separate host and port options. In this case a host with an
+ IPv6-configured network interface would be specified as:<br>
+ </p>
+ <div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font
+ color="#000000">osinfo -h 3ffe:1:2:1 -p 5988</font></big></div>
+ <p>But the cimcli command, which takes an optional "location" option
+ including an optional port number, requires the IPv6 address to be
+ delimited with brackets, for example:<br>
+ </p>
+ <div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns -l
+ [3ffe:1:2:1]</big></div>
+ <p>or</p>
+ <div style="margin-left: 40px;"><big><span style="font-family: monospace;">cimcli
+ ns -l [3ffe:1:2:1]:5989</span></big><br>
+ </div>
+ <br>
+ For more information on specifying IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF
+RFC
+ 2373 - IP Version 6 Addressing Architecture</a> and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF
+ RFC 2732 - Format for Literal IPv6 Addresses in URL's</a>.<br>
+ <h4><font color="#000000">IPv6 on Linux</font></h4>
+ <p>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.</p>
+ <p><span style="font-weight: bold;">Note: </span>you shouldn't&nbsp;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.<br>
+ </p>
+ <p>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:<br>
+ </p>
+ <div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font
+ color="#000000">test -f /proc/net/if_inet6 &amp;&amp; echo "Running
+ kernel is IPv6 ready"</font></big></div>
+ <p>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>.<br>
+ <br>
+ <span style="font-weight: bold;">Warning</span>: 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 <span style="color: rgb(153, 51, 153);">
+ <a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus
+bug
+ 6586</a> </span>and<span style="color: rgb(153, 51, 153);"> <a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat
+bug
+ 248052</a>, </span>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.</p>
+ <h4><font color="#000000">IPv6 on Windows</font></h4>
+ <p>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.</p>
+ On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span>
+ tool to install, uninstall, and query your IPv6 configuration. For
+ example:<br>
+ <br>
+ <div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font
+ color="#000000">ipv6 install<br>
+ ipv6 if</font></big></div>
+ <p>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.<br>
+ <br>
+ 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</font></a>.<br>
+ </p>
+ <h4><font color="#000000">Testing&nbsp; OpenPegasus IPv6 support</font></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.<br>
+ <br>
+ 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:<br>
+ <div style="margin-left: 40px;"><br>
+ <big style="font-family: monospace;"> osinfo -h ::1</big></div>
+ <h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2>
+ <p>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. <br>
+ </p>
+ <table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC"
+ border="1" cellspacing="1" width="80%">
+ <tbody>
+ <tr align="center">
+ <th bgcolor="#00ffff" width="10%">Bugzilla #</th>
+ <th bgcolor="#00ffff">Description</th>
+ </tr>
+ <tr align="center">
+ <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>
+ <tr align="center">
+ <td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9369">Bug
+ 9369</a><br>
+ </td>
+ <td align="left">Reregistering of an indication provider requires
+ that the&nbsp; 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>
+ <p>Pegasus was designed and implemented to comply with the DMTF CIM/WBEM
+ specifications The following table defines the level of the DMTF
+ specifications to which this version of Pegasus aims to conform today.</p>
+ <table id="AutoNumber1" border="1" cellspacing="1" width="80%">
+ <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 Infrastructure Specification</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%">Version 1.2, Final, January 09, 2007</td>
+ </tr>
+ <tr>
+ <td width="33%">DSP 0201 - Representation of CIM in XML</td>
+ <td width="33%">Version 2.2 Final, January 09, 2007</td>
+ </tr>
+ <tr>
+ <td width="33%">DSP 0202 - CIM Query Language Specification</td>
+ <td width="33%">1.0.0, preliminary, 9 December 2004</td>
+ </tr>
+ <tr>
+ <td width="33%">DSP 0205 - WBEM Discovery using SLP</td>
+ <td width="33%">1.0, preliminary, 27 January 2004</td>
+ </tr>
+ <tr>
+ <td width="33%">DSP 0206 - WBEM SLP Template</td>
+ <td width="33%">1.0.0, Preliminary, January 2004</td>
+ </tr>
+ <tr>
+ <td width="33%">CIM Schema </td>
+ <td width="33%">2.31.0 Final ( default) </td>
+ </tr>
+ <tr>
+ <td>DSP0226 - Web Services for Management<br>
+ </td>
+ <td>Version 1.1.1<br>
+ </td>
+ </tr>
+ <tr>
+ <td>DSP0227 - WS-Management CIM Binding Specification<br>
+ </td>
+ <td>Version 1.2.0<br>
+ </td>
+ </tr>
+ <tr>
+ <td>DSP0230 - WS-CIM Mapping Specification </td>
+ <td>Version 1.1.0<br>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIS SMI
+ Profiles Supported</h2>
+ <p>Today OpenPegasus includes support for several DMTF profiles including
+ the ones defined below:</p>
+ <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.<br>
+ </li>
+ <li>SNIA Profile Registration 1.0.0</li>
+ <li>SNIA Server 1.1.0 &amp; 1.2.0<br>
+ </li>
+ </ol>
+ <h2><a name="Conformance with DMTF Specifications">Conformance Exceptions
+ to 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.&nbsp; 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><b>Lifecycle Indications </b>-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.<font color="#ff0000">
+ </font><span class="norm"><font color="#ff0000">&nbsp;</font>For more
+ information see the Pegasus CVS file:<a name="comtag_137"><font size="2">
+ </font><font face="Courier New" size="2">&nbsp;pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a><font
+ size="2">.</font></span></li>
+ <li>
+ <p class="MsoNormal"><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 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.&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. &nbsp;When Pegasus uses object normalization, the
+ normalizer does apply qualifiers to returned instances if the
+ includeQualifiers operation parameter is set.</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 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>
+ <p class="MsoNormal"><b>MultiRequest Operations</b> - Pegasus does not
+ support the DMTF defined MultiRequest Operation option.</p>
+ </li>
+ <li>
+ <p class="MsoNormal"><b>MOF Compiler namespace pragma</b> - The
+ Pegasus compiler does not support the namespace pragma.</p>
+ </li>
+ <li><b>CIMOperation Trailer </b>- 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.&nbsp;</li>
+ <li><span style="font-weight: bold;">Whitespace in XML value Element</span>
+ - Pegasus trims the leading and trailing whitespace from XML value
+ elements that are of the Type String. &nbsp;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. &nbsp;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. &nbsp;These bugs are documented with the Bugzilla tag <big style="font-weight: bold;"><samp>"3.0_TARGET".</samp></big></li>
+ <li><span style="font-weight: bold;">modifyInstance operation behavior
+ in the Pegasus repository does not match the DMTF specification</span>.
+ 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><b>OpenPegasus Interop Namespace</b> - The default interop namespace
+ name in OpenPegasus is "root/PG_Interop".&nbsp; 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&nbsp; has become a build option with the build configuraton
+ environment variable PEGASUS_INTEROP_NAMESPACE = &lt;name for this
+ namespace&gt; however, the default if built without this change is
+ still "root/PG_InterOp"<br>
+ </li>
+ <li><b>OpenPegasus WSMAN protocol on windows does not handle NaN, INF,
+ or -INF</b> (bug&nbsp; <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><b>OpenPegasus outputs Nan, INF, -INF special values for Real32 and
+ Real64 property and Parameter types for the CIM/XML protocol</b> -
+ (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&nbsp; that is what is defined in the internal values.&nbsp;
+ OpenPegasus does not allow these special Strings on input however,</li>
+ <li><b>OpenPegasus does not handle covered properties</b> - (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.&nbsp;
+ Further, the requirement is expected to be removed in the future (i.e
+ CIM 3.0).<br>
+ </li>
+ </ol>
+ <h2><b><span style="font-family: Times;">OpenPegasus <a name="Supported Platforms">Supported
+ Platforms</a></span></b></h2>
+ <p align="left">Each OpenPegasus release lists as 'active' platforms those
+ hardware/software platforms that have recognized ports for the Pegasus
+ code base including a maintainer for the platform that will be willing
+ to regularly document issues and/or fix defects as the Pegasus code base
+ is changed.&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;&nbsp;
+ The platforms that are considered ported are shown in the two tables
+ below.&nbsp; The first table represents platform for which testing is
+ done on a regular basis and reported to the Pegasus Nightly Build Test
+ WEB Page. Those platforms which have been ported but do not have test
+ results that are current at the time of the release are reported in the
+ second table.</p>
+ <b>Actively Supported Platforms (Nightly Tests Reported for this release)</b>
+ <table class="MsoNormalTable" style="width: 90%;" border="1" cellpadding="0"
+ cellspacing="1">
+ <tbody>
+ <tr style="">
+ <td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;"
+ height="26">
+ <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(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;"
+ height="26">
+ <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;">
+ <p class="MsoNormal"><span style="color: black;">HP-UX<o:p>
+ PA_RISC and Itanium</o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt;">
+ <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;">
+ <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;">
+ <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;">
+ <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;">
+ <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;">
+ <p class="MsoNormal"><span style="color: black;">Linux Itanium<o:p></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt;">
+ <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;"> <span style="color: black;"><font size="3">Linux
+ IA-32</font></span></td>
+ <td style="padding: 0.75pt;"> <span class="SpellE"><span style="color: black;"><font
+ size="3">gcc</font></span></span><span style="color: black;"><font
+ size="3"> (versions 3.xx, 4.xx) clang(The clang compiler usage
+ is considered experimental and is not part of the nightly
+ tests today)</font><o:p></o:p></span></td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt;">
+ <p class="MsoNormal"><span style="color: black;">Linux X86_64<o:p></o:p></span></p>
+ </td>
+ <td style="padding: 0.75pt;">
+ <p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span
+ style="color: black;"> (versions 3.xx, 4.xx) </span><span style="color: black;"><font
+ size="3">clang(The clang compiler usage is considered
+ experimental and is not part of the nightly tests today)</font></span></p>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;"><font size="3">z/OS V1.7 and up</font></td>
+ <td style="vertical-align: top;"><font size="3">XL C/C++ from z/OS
+ Version 1.7 and up</font></td>
+ </tr>
+ </tbody>
+ </table>
+ &nbsp;
+ <p align="center"><b>Platforms not Actively supported for this release (No
+ current Nightly Build Test Results</b></p>
+ <table class="MsoNormalTable" style="width: 90%;" id="table2" border="1" cellpadding="0"
+ cellspacing="1">
+ <tbody>
+ <tr style="">
+ <td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;"
+ height="26">
+ <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(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;"
+ height="26">
+ <p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span
+ style="color: black;"><o:p></o:p></span></p>
+ </td>
+ </tr>
+ <tr>
+ <td style="padding: 0.75pt;"> <font size="3">Windows XP, Windows
+ Vista, Windows 7, Windows Server 2008</font>
+ <p></p>
+ </td>
+ <td style="padding: 0.75pt;"> <font size="3">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.</font> </td>
+ </tr>
+ <tr style="">
+ <td style="padding: 0.75pt;"> <font size="3">MacOS version 10.3 and
+ higher</font></td>
+ <td style="padding: 0.75pt;"> <font size="3">gcc 4.01</font></td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;"><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris
+ 8</span></font></big></td>
+ <td style="vertical-align: top;"><big>GNU&nbsp; 2.95.3,&nbsp; Sun CC
+ compiler V 5.8. Note that the latest thread patch (108993) may
+ be required. (see Pegasus bug 4632)</big><br>
+ </td>
+ </tr>
+ <tr>
+ <td style="vertical-align: top;"><span class="norm"></span><big><font
+ color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9</span></font></big></td>
+ <td style="vertical-align: top;"><big>GNU&nbsp; 2.95.3, Sun WorkShop
+ 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br>
+ </td>
+ </tr>
+ <tr>
+ <td><big>HP OpenVMS 8.3 or later Alpha</big></td>
+ <td><big><font style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span
+ style="color: rgb(153, 51, 153);">7.3-009 or later required</span>
+ for OpenVMS Alpha</font></big></td>
+ </tr>
+ <tr>
+ <td><big><font style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later
+ IA64</font></big></td>
+ <td><big><font style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023
+ or later required</font><font style="color: rgb(0, 0, 0);"> on
+ OpenVMS IA64</font></big></td>
+ </tr>
+ <tr>
+ <td style="padding: 0.75pt;">
+ <p class="MsoNormal"><span style="color: black;">Windows 2000</span></p>
+ </td>
+ <td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++
+ Ver.&nbsp; 6 and Microsoft .Net compiler version.&nbsp;Works on
+ VC .NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being
+ regularly tested.</font></td>
+ </tr>
+ <tr>
+ <td style="padding: 0.75pt;"> <font size="3">Windows 2003</font>
+ <p></p>
+ </td>
+ <td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++
+ Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++
+ Ver. 6 no longer being regular tested. </font> </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>
+ <p><b>Platform patches</b> </p>
+ <p style="margin-top: 0pt; margin-bottom: 0pt;"><font style="color: rgb(0, 0, 0);">The
+ following is a list known of platform patches Pegasus requires.</font></p>
+ <div style="margin-left: 40px;">
+ <ol>
+ <li>
+ <p style="margin-top: 0pt; margin-bottom: 0pt;"> <font style="color: rgb(0, 0, 0);">RHAS
+2.1
+ needs the update to fix Red Hat Bugzilla 98815.</font></p>
+ </li>
+ <li>
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4
+ multithreading bug in getpwuid-r could cause a CIM Server failure
+ (Bugzilla 6232). This is fixed in RHEL 4.5</p>
+ </li>
+ <li>
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE
+ Linux multiple versions - multithreaded client intermittently
+ fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red Hat bug
+ 248052)<br>
+ </p>
+ </li>
+ </ol>
+ </div>
+ <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> 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>
+ <h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2>
+ <p>The OpenPegasus 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;&nbsp; Effective with the start of the
+ OpenPegasus 2.6 work, all changes to the CVS tree are documented through
+ bugs.&nbsp; Bugs reports are filed not only for bugs and their
+ corresponding fixes but also as part of the process of committing new
+ code representing the work on PEPs done for OpenPegasus 2.6 and all
+ subsequent versions.&nbsp; Therefore, a search of the OpenPegasus
+ Bugzilla base for bugs with the tag for a particular version (ex.&nbsp;
+ <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED">2.6.0_APPROVED</a>,
+ <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED">
+ 2.6.1_APPROVED</a>, <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>,
+ etc) will yield all changes to the Pegasus CVS tree for that OpenPegasus
+ release.</p>
+ <p> &nbsp;&nbsp;&nbsp;&nbsp; - Changes for this release (bugs Tagged
+ 2.12.0_APPROVED). The link is&nbsp;<a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.0_APPROVED">
+ Pegasus 2.12.0_APPROVED bug list.</a></p>
+ <h2><a name="Pegasus Release Control and Version Definition Documentation">Release
+Control
+ and Version Definition Documentation</a></h2>
+ <p>The OpenPegasus project is controlled largely through the CVS
+ repository and a set of documents (PEPs) that serve both as the
+ definition and review mechanism for new and modified Pegasus
+ functionality and for the definition and documentation of releases.</p>
+ The following documentation defines the characteristics of this Pegasus
+ release. The documents are available&nbsp;in the OpenPegasus CVS
+ repository. <br>
+ <ul>
+ <li><b> OpenPegasus Release Definition/Status -No PEP (See Wiki Section
+ <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_12_x">OpenPegasus
+2.12.x
+ Release Status</a>) - <span style="font-weight: normal;">A&nbsp;
+ section in the Pegasus wiki is used throughout the development of
+ this version as the control point for functionality that will go
+ into the release and points to all of the PEPs that represent the
+ Pegasus&nbsp; functionality changes for this version of Pegasus</span>.&nbsp;</b></li>
+ <b> </b><span style="font-weight: bold;"></span><b>OpenPegasus&nbsp;
+ Build and Configuration Options&nbsp; for Selected Platforms -&nbsp; <span
+ style="font-weight: normal;">In previous versions of Pegasus this
+ information was&nbsp; released as a Pegasus PEP. Starting with
+ Pegasus 2.9.0 the information is located in the OpenPegasus CVS
+ repository as <big style="font-weight: bold;"> <span style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</span></big>.</span></b><b>
+ <li> OpenPegasus External Interfaces -<span style="font-weight: normal;">The
+ list of the OpenPegasus interfaces that are considered external
+ and therefore "frozen". Unless an exception is explicitly approved
+ by the Steering Committee all subsequent releases of Pegasus MUST
+ continue to support these interfaces. Interfaces not explicitly
+ listed in this document, should be considered as internal and
+ subject to change.In previous Pegasus releases this information
+ was available as a separate PEP. Starting with Pegasus 2.9.0 this
+ information is integrated into the Pegasus repositoryas&nbsp; </span><small
+ style="font-weight: bold;"><font face="Courier New" size="4"><small>pegasus/doc/EnternalInterface.html</small></font></small><span
+ style="font-weight: normal;">.</span></li>
+ </b>
+ <li><b> OpenPegasus&nbsp; SDK Packaging Definition - <span style="font-weight: normal;">Defines
+ the recommended set of files for inclusion in the OpenPegasus SDK.
+ Starting with Pegasus release 2.11.0, this document is available
+ in the Pegasus CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>.
+ In previous Pegasus releases this document was made available as s
+ separate Pegasus PEP document rather than in the CVS repository.</span>&nbsp;
+ </b></li> <b> </b> <b>
+ <li>&nbsp;Pegasus&nbsp; Runtime Packaging Definition -&nbsp;<span style="font-weight: normal;">Defines
+ the recommended set of files for inclusion in this OpenPegasus
+ release. Starting with Pegasus release 2.11.0, this 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. </span>&nbsp;</li>
+ </b> <b>
+ <li>Pegasus Release Notes -&nbsp;<span style="font-weight: normal;"> </span>PEP
+ 364 - <span style="font-weight: normal;"> (This document is located
+ in the approved PEP repository and the OpenPegasus source tree
+ root directory (<big style="font-weight: bold;"><span style="font-family: monospace;">pegasus/ReleaseNotes.htm</span></big>)</span></li>
+ </b>
+ </ul>
+ <h2><b><a name="General Documentation">General Documentation</a></b></h2>
+ <p><b>The following documentation is available for the this Pegasus
+ release:</b></p>
+ <ul style="margin-top: 0in;" type="disc">
+ <b>
+ <li class="MsoNormal" style="color: black;"><b>Utilities</b> - </li>
+ </b>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> <b>
+ <li class="MsoNormal" style="color: black;"><b>API and&nbsp; usage
+ documentation</b> - </li>
+ </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. <b>
+ <li class="MsoNormal" style="color: black;"><b>Building and Debugging
+ Providers </b>- </li>
+ </b>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. <b>
+ <li class="MsoNormal" style="color: black;"><b>Building and Debugging
+ Clients</b> - </li>
+ </b>API documentation and the documentation on the Pegasus Technical
+ Workshop which is available on the Pegasus web site. <b>
+ <li class="MsoNormal" style="color: black;"><b>PEPs</b> - </li>
+ </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.
+ </ul>
+ <hr>Licensed to The Open Group (TOG) under one or more contributor license
+ agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this
+ work for additional information regarding copyright ownership. Each
+ contributor licenses this file to you under the OpenPegasus Open Source
+ License; you may not use this file except in compliance with the License.
+ <p>Permission is hereby granted, free of charge, to any person obtaining a
+ copy of this software and associated documentation files (the
+ "Software"), to deal in the Software without restriction, including
+ without limitation the rights to use, copy, modify, merge, publish,
+ distribute, sublicense, and/or sell copies of the Software, and to
+ permit persons to whom the Software is furnished to do so, subject to
+ the following conditions:</p>
+ <p>The above copyright notice and this permission notice shall be included
+ in all copies or substantial portions of the Software.</p>
+ <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+ OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+ IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+ CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+ TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
+ </div>
+ </body>
</html>