version 1.8, 2006/03/28 20:27:53
|
version 1.17.4.1, 2011/10/11 18:17:09
|
|
|
margin:1.0in 1.25in 1.0in 1.25in; | margin:1.0in 1.25in 1.0in 1.25in; |
mso-header-margin:.5in; | mso-header-margin:.5in; |
mso-footer-margin:.5in; | mso-footer-margin:.5in; |
|
|
mso-paper-source:0;} | mso-paper-source:0;} |
div.Section1 | div.Section1 |
{page:Section1;} | {page:Section1;} |
|
|
text-indent:-.25in;} | text-indent:-.25in;} |
@list l4:level7 | @list l4:level7 |
{mso-level-tab-stop:3.5in; | {mso-level-tab-stop:3.5in; |
|
|
mso-level-number-position:left; | mso-level-number-position:left; |
text-indent:-.25in;} | text-indent:-.25in;} |
@list l4:level8 | @list l4:level8 |
|
|
text-indent:-.25in;} | text-indent:-.25in;} |
@list l19 | @list l19 |
{mso-list-id:1902863286; | {mso-list-id:1902863286; |
|
|
mso-list-template-ids:740079056;} | mso-list-template-ids:740079056;} |
@list l19:level1 | @list l19:level1 |
{mso-level-number-format:bullet; | {mso-level-number-format:bullet; |
|
|
</w:WordDocument> | </w:WordDocument> |
</xml><![endif]--> | </xml><![endif]--> |
</head> | </head> |
<body style="" lang="EN-US" link="blue" vlink="blue"> |
<body lang="EN-US" link="blue" vlink="blue"> |
<div class="Section1"> | <div class="Section1"> |
<div class="MsoNormal" style="text-align: center;" align="center"><span | <div class="MsoNormal" style="text-align: center;" align="center"><span |
style="color: black;"> | style="color: black;"> |
|
|
align="center"><b><span style="font-size: 13.5pt; color: black;">Pegasus | align="center"><b><span style="font-size: 13.5pt; color: black;">Pegasus |
Enhancement Proposal (PEP)<o:p></o:p></span></b></p> | Enhancement Proposal (PEP)<o:p></o:p></span></b></p> |
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span | <p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span |
style="color: black;"><br> |
style="color: black;"> |
<br> | <br> |
<b>PEP #:</b> 230<br> |
<b>PEP #:</b> 359<br> |
</span></p> | </span></p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release |
Notes for OpenPegasus 2.5</p> |
Notes for OpenPegasus version 2.11.0</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version: </b>1.8</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 23 |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> <st1:date |
March 2011</p> |
year="2004" day="23" month="3">1 April 2005</st1:date></p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Karl |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Warren |
Schopmeyer<br> |
Grunbok, Karl Schopmeyer<br> |
|
</p> | </p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>draft</p> | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>draft</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p> | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p> |
<table class="MsoNormalTable" style="width: 100%;" border="1" |
<table class="MsoNormalTable" style="width: 100%;" id="table1" |
cellpadding="0" cellspacing="1" width="100%"> |
border="1" cellpadding="0" cellspacing="1" height="155" width="100%"> |
<tbody> | <tbody> |
<tr style=""> | <tr style=""> |
<td | <td |
style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"> |
style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" |
|
height="27"> |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span | <p class="MsoNormal" style="text-align: center;" align="center"><b><span |
style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
</td> | </td> |
<td | <td |
style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"> |
style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" |
|
height="27"> |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span | <p class="MsoNormal" style="text-align: center;" align="center"><b><span |
style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
</td> | </td> |
<td | <td |
style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"> |
style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" |
|
height="27"> |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span | <p class="MsoNormal" style="text-align: center;" align="center"><b><span |
style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
</td> | </td> |
<td | <td |
style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"> |
style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" |
|
height="27"> |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span | <p class="MsoNormal" style="text-align: center;" align="center"><b><span |
style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" height="22"> |
<p class="MsoNormal" style="text-align: center;" align="center"><span | <p class="MsoNormal" style="text-align: center;" align="center"><span |
style="font-family: Arial; color: black;"><font size="2"> 1.0</font><o:p></o:p></span></p> | style="font-family: Arial; color: black;"><font size="2"> 1.0</font><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" align="left" height="22"> |
<p class="MsoNormal" style="text-align: center;" align="center"><span |
<p class="MsoNormal" style="text-align: center;" align="center"> <font |
style="font-family: Arial; color: black;"><o:p> <font size="2">1,April |
size="2"><span style="font-family: Arial;">23 March 2011</span></font></p> |
2005<br> |
|
</font></o:p></span></p> |
|
</td> | </td> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" align="left" height="22"> |
<p class="MsoNormal" style="text-align: center;" align="center"><span | <p class="MsoNormal" style="text-align: center;" align="center"><span |
style="font-family: Arial; color: black;"><o:p>Warren Grunbok<br> |
style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> |
</o:p></span></p> |
|
</td> | </td> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" height="22"> |
<p class="MsoNormal"><span | <p class="MsoNormal"><span |
style="font-family: Arial; color: black;"><font size="1">Initial |
style="font-family: Arial; color: black;"><font size="2">Initial |
Submission</font><o:p><font size="1"> <br> |
Submission <span style="color: red;"></span></font><o:p><font |
</font></o:p></span></p> |
size="2"> </font></o:p></span></p> |
</td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;" align="center"> 1.1</td> |
|
<td style="padding: 0.75pt;" align="center">26, June 2005 <br> |
|
</td> |
|
<td style="padding: 0.75pt;">Warren Grunbok<br> |
|
</td> |
|
<td style="padding: 0.75pt;">revisions based on Comments <br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.2<br> |
|
</td> |
|
<td style="vertical-align: top;">22, July 2005<br> |
|
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">fixed some broken links, added |
|
security notes. <br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.3<br> |
|
</td> |
|
<td style="vertical-align: top;">23, Aug 2005<br> |
|
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">Revisions based on comments<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.4<br> |
|
</td> |
|
<td style="vertical-align: top;">30.Aug 2005<br> |
|
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">More revisions based on Aug 26 |
|
review in Architecture meeting<br> |
|
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;">1.5<br> |
<td style="padding: 0.75pt;" align="center" height="21"> </td> |
</td> |
<td style="padding: 0.75pt;" align="center" height="21"> </td> |
<td style="vertical-align: top;">12, Sept 2005<br> |
<td style="padding: 0.75pt;" align="center" height="21"> </td> |
</td> |
<td style="padding: 0.75pt;" height="21"> </td> |
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">Minor comment updates from 1.4 |
|
version (balloted version)<br> |
|
</td> |
|
</tr> | </tr> |
<tr> |
<tr style=""> |
<td style="vertical-align: top;">1.6<br> |
<td style="padding: 0.75pt;" align="center" height="21"> </td> |
</td> |
<td style="padding: 0.75pt;" align="center" height="21"> </td> |
<td style="vertical-align: top;">14,Sept 2005<br> |
<td style="padding: 0.75pt;" align="center" height="21"> </td> |
</td> |
<td style="padding: 0.75pt;" height="21"> </td> |
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">additional comments from review<br> |
|
</td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;">1.7<br> |
<td style="padding: 0.75pt;" align="center" height="21"> </td> |
</td> |
<td style="padding: 0.75pt;" align="center" height="21"> </td> |
<td style="vertical-align: top;">20, Sept 2005<br> |
<td style="padding: 0.75pt;" align="center" height="21"> </td> |
</td> |
<td style="padding: 0.75pt;" height="21"> </td> |
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">Added Solaris back in, corrected |
|
Provider security statement, and clarified Solaris support for 2.5<br> |
|
</td> |
|
</tr> | </tr> |
<tr> |
<tr style=""> |
<td style="vertical-align: top;">1.8<br> |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
</td> |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
<td style="vertical-align: top;">21, Sept 2005<br> |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
</td> |
<td style="padding: 0.75pt;" height="23"> </td> |
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">Clarified SLP enablement |
|
Paragraph and correction of Power on Linux in platform table<br> |
|
</td> |
|
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<p><o:p> </o:p></p> |
|
<div class="MsoNormal" style="text-align: center;" align="center"><span | <div class="MsoNormal" style="text-align: center;" align="center"><span |
style="color: black;"> | style="color: black;"> |
<hr align="center" color="#009900" noshade="noshade" size="2" | <hr align="center" color="#009900" noshade="noshade" size="2" |
width="100%"></span></div> | width="100%"></span></div> |
<p><b>Abstract:</b> This document defines the release notes for the 2.5 |
<p><b>Abstract:</b> This document defines the release notes for the |
version of the Pegasus CIM Server. <span class="norm1"><span |
2.11.0 release of the OpenPegasus CIM Server. The purpose of this PEP |
style="font-size: 9pt;"><a |
is |
href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35" |
to summarize the characteristics of this release, point to other |
target="_self"><br> |
documentation that defines the release in more detail, and provide |
</a></span></span></p> |
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 | <div class="MsoNormal" style="text-align: center;" align="center"><span |
style="color: black;"> | style="color: black;"> |
<hr align="center" color="#009900" noshade="noshade" size="2" | <hr align="center" color="#009900" noshade="noshade" size="2" |
width="100%"></span></div> | width="100%"></span></div> |
<p><b><o:p><font size="4"> Contents<br> |
<h2 style="margin-bottom: 1px;"><b><o:p><font size="5"> Contents</font></o:p></b></h2> |
</font></o:p></b></p> |
|
<ol> | <ol> |
<li><a href="#Availability_of_this_Release_">Availability of |
<li><a href="#Availability_of_this_Release_">Availability of this |
this Release</a></li> |
Release</a></li> |
<li><a href="#Functionality_of_This_Release">Functionality of |
<li><a href="#Functionality_of_This_Release">OpenPegasus |
This Release</a></li> |
Functionality of This Release</a></li> |
|
<li><a href="#Compatibility_Considerations_">Compatibility |
|
Considerations</a></li> |
<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship | <li><a href="#Relationship_to_CIMWBEM_Standards">Relationship |
to CIM/WBEM Standards</a></li> | to CIM/WBEM Standards</a></li> |
<li><a href="#Supported%20Platforms">Supported |
<li><a href="#Supported%20Platforms">OpenPegasus Supported Platforms</a></li> |
Platforms</a></li> |
|
<li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance | <li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance |
with DMTF Specifications</a></li> | with DMTF Specifications</a></li> |
<li><a href="#Changes%20in%20This%20Release">Changes |
<li><a href="#PEGASUS%20Bugs">OpenPegasus Bugs</a></li> |
in This Release</a></li> |
|
<li><a href="#PEGASUS%20Bugs">PEGASUS |
|
Bugs</a></li> |
|
<li> <a | <li> <a |
href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">Pegasus |
href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus |
Release Control and Version Definition Documentation</a></li> | Release Control and Version Definition Documentation</a></li> |
<li><a href="#General%20Documentation">General | <li><a href="#General%20Documentation">General |
Documentation</a></li> | Documentation</a></li> |
</ol> | </ol> |
<h2><a name="Availability_of_this_Release_"></a><span |
<h2><span style="color: black;">Availability |
style="color: black;"><a name="Availability_of_this_Release"></a>Availability |
|
of this Release</span></h2> | of this Release</span></h2> |
<p>This release is available in a number of forms including:</p> | <p>This release is available in a number of forms including:</p> |
<ul> | <ul> |
<li>Source release in both ZIP and TAR formats. These can be |
<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 | downloaded from the <span class="SpellE">OpenPegasus</span> Web |
site at <a | site at <a |
href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a></li> |
href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li> |
<li>OpenPegasus 2.5 binaries are available for Red Hat Enterprise |
<li><b>OpenPegasus source RPMs</b> on the OpenPegasus web site.. |
Linux 3.0 and 4.2 and SUSE LINUX Enterprise Server 9.0. A Source RPM is |
A source RPM is available on the |
also available that can be used to build binaries for most |
OpenPegasus web site that can be used to build binaries for most |
LSB-compliant RPM-based Linux distributions and versions.</li> | LSB-compliant RPM-based Linux distributions and versions.</li> |
<li>The Pegasus CVS. The CVS tags representing this release and |
<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 | subsequent snapshots that are made available in the Pegasus CVS are |
defined on the OpenPegasus CVS repository web page (see the <a | defined on the OpenPegasus CVS repository web page (see the <a |
href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus | href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus |
|
|
href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release | href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release |
snapshots page</a>.</li> | snapshots page</a>.</li> |
</ul> | </ul> |
<>The instructions for acquiring the released code are on the <a |
<p>The instructions for acquiring the released code are on the <a |
href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus | href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus |
WEB site</a>. | WEB site</a>. |
Installation instructions are part of the README in the root of the | Installation instructions are part of the README in the root of the |
Pegasus source | Pegasus source |
tree.<br> |
tree.</p> |
<br> |
</div> |
<span class="norm">Instructions for building the Linux RPMs: <span |
<div class="Section1"> |
style="color: rgb(255, 0, 0);"></span><br> |
<h2><span style="color: black;">OpenPegasus Functionality for This |
</span></> |
Release</span></h2> |
<ol> |
Pegasus overall status by release is defined by a |
<li><span class="norm"><span style="font-weight: bold;">Download</span> |
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status |
tog-pegasus-2.5.0-1.src.rpm. </span></li> |
WEB Page</a> |
<li><span class="norm"><span style="font-weight: bold;">rpm</span> |
that is available on the OpenPegasus web site . That web page |
-ih tog-pegasus-2.5.0-1.src.rpm </span></li> |
shows the |
<li> |
Pegasus users and developers the status of the various features found |
<p style="margin-top: 0pt; margin-bottom: 0pt; font-weight: bold;"><span |
in Pegasus |
class="norm">Build |
using a simple color coded key (white, red, yellow, green) and a |
the rpms:</span></p> |
description of |
</li> |
each feature. |
</ol> |
<p>Pegasus 2.11.0 |
<span class="norm"></span> |
is a major release, extending the previous Pegasus release in selected |
<table |
areas as described in the Pegasus PEP defining this release |
style="margin-left: auto; margin-right: auto; text-align: left; width: 712px; height: 116px;" |
. </p> |
border="1" cellpadding="2" cellspacing="2"> |
<p>The major areas of development for this release were as |
|
follows. Note that the bugs listed represent only those features |
|
incorporated in bugs without PEPS that are considered enhancements, not |
|
all bugs incorporated in the release. For |
|
more information access the PEP/BUG for each change defined below:</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font |
|
style="font-weight: bold;" size="4"> 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> | <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> | <tr> |
<td |
<td>PEP 318</td> |
style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Distro</td> |
<td>Run 32 bit providers in 64 bit OpenPegasus</td> |
<td |
<td style="text-align: center;"><a |
style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Command<br> |
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> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top; text-align: center;">RHEL3<br> |
<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> |
<td style="vertical-align: top; text-align: center;"><span |
<td width="128"><a |
class="norm">rpmbuild -bb /usr/src/redhat/SPECS/tog-pegasus- |
href="http://www.openpegasus.org/pp/uploads/40/22529/PEP324-DMTF_Indications_Profile_stage2_Ver11.html">1.1</a></td> |
2.5.0-1.spec</span></td> |
|
</tr> | </tr> |
<tr> |
<tr align="center"> |
<td style="vertical-align: top; text-align: center;">RHEL4<br> |
<td style="text-align: center;" width="7%">PEP 349<br> |
</td> | </td> |
<td style="vertical-align: top; text-align: center;"><span |
<td align="left" width="75%"><span style="color: windowtext;"><span |
class="norm">rpmbuild -bb /usr/src/redhat/SPECS/tog-pegasus- |
style=""></span>Improve the |
2.5.0-1.spec</span></td> |
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> |
<tr> | <tr> |
<td style="vertical-align: top; text-align: center;">SLES 9 <br> |
<td style="text-align: center;"><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8787">Bug 8787</a><br> |
</td> | </td> |
<td style="vertical-align: top; text-align: center;"><span |
<td>Add External SLP support to release builds<br> |
class="norm"> rpmbuild -bb /usr/src/packages/SPECS/tog-pegasus- |
</td> |
2.5.0-1.spe</span></td> |
<td style="text-align: center;"> <a |
|
href="http://www.openpegasus.org/pp/uploads/40/21277/PEP350_MultiCIMOM.htm"> |
|
</a></td> |
</tr> | </tr> |
</tbody> |
|
</table> |
|
<span class="norm"></span> |
|
<ol start="4"> |
|
<span class="norm"><br> |
|
</span><li style="font-weight: bold;"><span class="norm">After |
|
the build the rpms will be in the |
|
following locations:</span></li> |
|
<span class="norm"></span> |
|
<table style="width: 100%; text-align: left;" border="1" |
|
cellpadding="2" cellspacing="2"> |
|
<tbody> |
|
<tr> | <tr> |
<td |
<td style="text-align: center;"> <a |
style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Distro<br> |
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> |
<td |
<td style="text-align: center;"><br> |
style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Location |
|
of RPMs after the build is complete<br> |
|
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top; text-align: center;">RHEL3<br> |
<td style="text-align: center;"><a |
</td> |
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8806">Bug |
<td style="vertical-align: top; text-align: center;"><span |
8806</a></td> |
class="norm">/usr/src/redhat/RPMS/[arch]/tog-pegasus- |
<td>Diagnose data for BAD UTF8 exception</td> |
2.5.0-1.[arch].rpm |
<td> </td> |
/usr/src/redhat/RPMS/[arch]/tog-pegasus-sdk- 2.5.0-1.[arch].rpm.<span |
|
style="font-family: "times new roman";"></span><span |
|
style="font-family: "times new roman";"></span></span><span |
|
class="norm"> </span></td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top; text-align: center;">RHEL4<br> |
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8825">Bug |
</td> |
8825</a></td> |
<td style="vertical-align: top; text-align: center;"><span |
<td>Option to specify multiple provider dirs for release builds</td> |
class="norm">/usr/src/redhat/RPMS/[arch]/tog-pegasus- |
<td> </td> |
2.5.0-1.[arch].rpm |
</tr> |
/usr/src/redhat/RPMS/[arch]/tog-pegasus-sdk- 2.5.0-1.[arch].rpm.</span></td> |
<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> </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top; text-align: center;">SLES9<br> |
<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> </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 |
|
to include enumeration association filters</span></td> |
|
<td width="128"> <br> |
</td> | </td> |
<td style="vertical-align: top; text-align: center;"><span |
</tr> |
class="norm">/usr/src/packages/RPMS/[arch]/tog-pegasus- |
<tr align="center"> |
2.5.0-1.[arch].rpm |
<td style="text-align: center;" width="7%"> </td> |
/usr/src/packages/RPMS/[arch]/tog-pegasus-sdk- 2.5.01-.[arch].rpm.</span></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> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<span class="norm"></span><span class="norm"></span> |
<p>The status of several components of Pegasus functionality change |
</ol> |
status |
<span class="norm"> |
between Pegasus versions. <span class="norm"><a name="comtag_116">Features |
</span><span class="norm"></span> |
that |
<h2><a name="Functionality_of_This_Release"></a><span |
have changed status can be identified by a change in color from the |
style="color: black;">Functionality of This Release</span></h2> |
previous |
New for the Pegasus 2.5 release is a Feature Maturity Dashboard. |
release to this release</a></span> on the |
This document shows the Pegasus users and developers the maturity of |
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status |
the various features found in Pegasus using a simple color coded |
WEB Page</a>.</p> |
key. That document can be found here: <a |
<p>Finally, a significant number of internal changes and corrections |
href="http://www.openpegasus.org/page.tpl?ggid=799">Feature |
were made |
Maturity Link</a><br> |
under the control of the Pegasus bugzilla bug system. See the bug |
<span style="font-family: "times new roman";"><br> |
section below |
</span>The overall level of functionality in the Pegasus environment |
for more information.</p> |
effective with |
<h3><font color="#000000">Information on IPv6 Support (PEP 291)</font></h3> |
this release is as follows: |
<p><b>NOTE:</b> This functionality was incorporated in OpenPegasus |
<h3><b>CIM Server Functionality</b></h3> |
2.7.0 but it |
<p>The following paragraphs list the functions in this release. |
was felt that the information below was worth repeating in subsequent |
All functions are considered community tested and operational unless |
Release |
specifically noted below. Features that are marked alpha or beta are |
Notes</p> |
not generally of the quality or completeness for production |
<p style="color: rgb(153, 51, 153);"><font color="#000000">IPv6 is |
usage. Interfaces that are part of the Pegasus public |
short for "Internet |
interface definitions but that the Pegasus team feels may change are |
Protocol |
marked experimental. In many cases these features and interfaces |
Version 6". IPv6 is the "next generation" protocol designed by the IETF |
are conditionally compiled with special environment variables. <a |
to replace the current version Internet Protocol, IP Version 4 |
href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502"><span |
("IPv4"). IPv6 Support for OpenPegasus is documented in </font> <a |
style="color: rgb(255, 0, 0);"><span style="color: rgb(51, 102, 255);"><span |
href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html"> |
style="text-decoration: underline;">PEP 200</span> </span></span></a> |
<font color="#3333ff">PEP |
provides more detailed information on how to enable |
291</font></a><font color="#000000">.</font></p> |
functionality that is conditionally compiled in this release.</p> |
<p>The IPv6 support in OpenPegasus is |
<blockquote> |
controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for |
<h4><b>CIM Operations over HTTP support</b></h4> |
this |
<ol> |
variable is "true"; setting this to |
<li>Class Operations (<span class="SpellE">getClass</span>, <span |
'false' before building OpenPegasus will disable the IPv6 support.<br> |
class="SpellE">deleteClass</span>, <span class="SpellE">modifyClass</span>, |
|
<span class="SpellE">enumerateClass</span>, <span class="SpellE">enumerateClassNames</span>)</li> |
|
<li>Qualifier Operations (getQualifier, setQualifier, |
|
deleteQualifier) </li> |
|
<li>Instance Operations (<span class="SpellE">getInstance</span>, <span |
|
class="SpellE">deleteInstance</span>, <span class="SpellE">modifyInstance</span>, |
|
<span class="SpellE">enumerateInstance</span>, <span |
|
class="SpellE">enumerateInstanceNames</span>, <span class="SpellE">getProperty</span>, |
|
<span class="SpellE">setProperty</span>)</li> |
|
<li>Association Operations (references, <span class="SpellE">referencenames</span>, |
|
<span class="SpellE">associators</span>, <span class="SpellE">associatornames)</span></li> |
|
<li>Methods Operations (invokeMethod)</li> |
|
<li>Query operation - Support for ExecQuery was added in 2.4 with |
|
WQL as query language and is defined in PEP 119. This feature is |
|
considered at alpha quality because it has only been contributor |
|
tested. Additional tests have been added in 2.5 for ExecQuery.<br> |
|
</li> |
|
</ol> |
|
</blockquote> |
|
</div> |
|
<blockquote> |
|
<h4><b>Indications</b></h4> |
|
<ul> |
|
<li>Process indications - Process indications are operational in |
|
the |
|
Server. This includes support |
|
for subscriptions, filters, and indication handlers, the provider API |
|
for |
|
indications and the CIMXML indication handler.</li> |
|
<li>Lifecycle indications - With the support for embedded objects, |
|
lifecycle indications (ie. those |
|
classes of indications derived from CIM_ClassIndication and |
|
CIM_InstIndication) can now be created. Pegasus 2.5 provides some |
|
enablement for the generation of lifecycle indications. For more |
|
details, refer to |
|
<src/Unsupported/LifecycleIndicationProvider/readme.LifecycleIndications.htm>.</li> |
|
</ul> |
|
<h4><b>Indication Listener</b></h4> |
|
<p class="MsoNormal">The generic components for a CIM Listener and a |
|
listener API are operational. This includes the functions for |
|
HTTP, XML indication input and response, and consumers of indications. |
|
This code can be used to define a separate listener package and is used |
|
as an indication listener in the Pegasus server. <br> |
|
</p> |
|
<p class="MsoNormal"><br> |
|
<font style="color: rgb(0, 0, 0);" color="#330099">Pegasus 2.5 |
|
includes a new standalone listener that is separate |
|
from the current standalone CIMListener and the ExportServer listener |
|
in the CIM server. |
|
The use model that this listener fits is the following: |
|
<ul> |
|
<li><span class="norm"></span> The listener may be packaged as |
|
part of the CIMOM or it may be packaged independently as part of |
|
another application. </li> |
|
<li><span class="norm"></span> Consumers |
|
are developed independently of the listener and may be shipped with the |
|
listener or added to an installed listener at a future time. </li> |
|
</ul> |
|
</font> </p> |
|
<p><span style="color: rgb(0, 0, 0);" class="norm"></span><span |
|
style="color: rgb(0, 0, 0);"> </span><font color="#330099"><span |
|
style="color: rgb(0, 0, 0);">This |
|
new "Dynamic Listener" provides a solution for the above use model. It |
|
is essentially a lightweight, pluggable listener that |
|
provides a small set of management features. The DynamicListener can be |
|
run inside a daemon or a service. It is easily configurable and |
|
bypasses traditional registration procedures. See <a |
|
href="http://www.openpegasus.org/pp/protected/upreviews/20/1303/PEP195_CIMListenerEnhancementsv1_6.htm"><span |
|
style="color: rgb(51, 51, 255); text-decoration: underline;">PEP 195</span></a> <span |
|
style="color: rgb(255, 0, 0);"> </span>for |
|
details.</span> </font></p> |
|
<h4>Object Normalization</h4> |
|
The Object Normalizer is an entity introduced in Pegasus 2.4 that |
|
ensures |
|
objects delivered from providers are complete and accurate. Two major |
|
issues were identified with the initial implementation: 1) the Object |
|
Normalizer drops instances it considers bad, and 2) the Object |
|
Normalizer code slows performance. These issues are now addressed by |
|
moving the Object Normalizer from the Dispatcher to the Response |
|
Handler (or equivalent) and optimizing the existing implementation. The |
|
move allows errors to be reported to the provider at the point of |
|
delivery and ensures that only a single copy is made to preserve the |
|
CIMOM/provider boundary.<br> |
|
Two new configuration properties were added to control object |
|
normalization.<br> |
|
<ol> |
|
<li>enableNormalization (true|false) - Enables or disables object |
|
normalization for provider objects.</li> |
|
<li>excludeModulesFromNormalization (colon delimited list of |
|
provider modules) - List the provider modules by name (as specified in |
|
PG_ProviderModule.Name) to exclude from normalization. Keep in mind |
|
that all objects managed by all providers will be excluded from |
|
normalization if its module name appears in this list.<br> |
|
</li> |
|
</ol> |
|
<br> |
|
<h4>Embedded Object support</h4> |
|
Pegasus 2.5 now provides embedded object support. The proposed solution |
|
is restricted to the following:<br> |
|
The only representation for embedded objects supported by this |
|
PEP is CIM-XML. <br> |
|
CIMObject is implemented as a new CIMValue type. This type will be used |
|
internally to represent embedded objects. When externalized (via |
|
CIM-XML) these objects will be converted to strings representing valid |
|
INSTANCE or CLASS elements, in accordance with the CIM Infrastructure |
|
Specification. Embedded instances will also carry the |
|
EmbeddedObject attribute with |
|
the value "object", as specified by CR Interop-00217.001. <br> |
|
<br> |
|
<p class="MsoNormal"> </p> |
|
</blockquote> |
|
<div class="Section1"> |
|
<blockquote> |
|
<h4><b>Query Language</b></h4> |
|
<p>The query language today is based on WQL and is implemented and |
|
used for filters and in 2.4 for execQuery. <br> |
|
</p> | </p> |
<p>CQL Stage 1 has been included for Pegasus 2.5. PEPs 138, |
<p>The following subsections provide |
193, 205 combine to describe the function submitted.<br> |
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> |
<h4><b>Schema Repository</b></h4> |
<p>All OpenPegasus externals that |
<span class="norm"></span>By default, Pegasus uses an XML-based |
support either a hostname or an IP address as input have been updated |
schema repository. A binary encoding option is also available.<span |
to allow an IPv6 address to be specified. If the required input is just |
style="font-family: "times new roman";"><br> |
an IP address (eg. no optional or required port number), then the IPv6 |
<br> |
address must be specified without brackets. For example, the |
</span>To use the binary encoding feature a new configuration |
OpenPegasus osinfo client (which returns information about the OS |
properties was |
running on a host system) takes separate host and port options. In this |
added:<br> |
case a host with an IPv6-configured network interface would be |
<p> enableBinaryRepository (true|false) - Enables |
specified as:<br> |
or |
|
disables binary repository.<br> |
|
</p> | </p> |
<div style="margin-left: 40px;"> In addition to the binary |
<div |
repository, the compressed repository |
style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font |
functionality has |
color="#000000">osinfo -h |
been added as a build time conditional compile. It defaults to not |
3ffe:1:2:1 -p 5988</font></big></div> |
support |
<p>But the cimcli command, which |
compression. When enabled the zlib library, used for the compression |
takes |
algorithims, must be installed on the build and target systems. With |
an optional "location" option including an optional port number, |
compression enabled records are always written compressed but both |
requires the IPv6 address to be delimited with brackets, for example:<br> |
compressed |
|
and non-compressed records can be read allowing an easy migration path.<br> |
|
<br> |
|
<span style="color: rgb(51, 102, 255);">Note: </span><span |
|
class="norm"></span><span style="color: rgb(51, 102, 255);">Note: |
|
Users may experience an incompatibility moving a binary repository from |
|
Pegasus 2.4 to 2.5. In Pegasus 2.5, measures have been taken to improve |
|
the ability to maintain compatibility with subsequent releases. (See |
|
bugzilla 3642 for details.)</span><font><font color="RED"> </font></font><span |
|
style="color: rgb(51, 102, 255);">See bugzilla 3642 for details.<br> |
|
</span></div> |
|
<h4><b><b>Compressed Repository</b></b></h4> |
|
<div style="margin-left: 40px;"><span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);" color="RED">A compressed repository |
|
feature has been added for |
|
pegasus 2.5 that compresses the repository written to disk. This allows |
|
the |
|
repository to be as much as 50% smaller on disk. It uses an external |
|
compression library (zlib) and has been tested with zlib 1.2.2. This |
|
feature is |
|
documented in PEP 214 and also in a Readme |
|
(readme.compressed_repository). It is |
|
considered experimental today because it is not in the automated tests. |
|
Note |
|
that the tests for this feature are in the test suite but not |
|
activiated for |
|
automatic tests.</font><br> |
|
<span style="color: rgb(51, 102, 255);"><br> |
|
</span><font><font color="RED"> </font></font></div> |
|
<p> </p> |
|
<h4><b>Instance Repository</b></h4> |
|
<p><span class="norm"></span><font style="color: rgb(0, 0, 0);">The |
|
Pegasus schema repository may also be configured to hold instance |
|
data. </font><span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);">Although instances may be place in the |
|
repository |
|
it was </font><font style="color: rgb(0, 0, 0);">not designed as a |
|
high volume data store</font><span style="color: rgb(0, 0, 0);">. </span><br> |
|
<br> |
|
</p> | </p> |
<h4><b><b>Security Considerations<br> |
<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns |
</b></b></h4> |
-l [3ffe:1:2:1]</big></div> |
<font style="color: rgb(0, 0, 0);" color="RED">OpenPegasus 2.5 (and |
<p>or</p> |
prior) contains several mechanisms to perform authorization, but none |
<div style="margin-left: 40px;"><big><span |
of these authorization checks are performed by default. |
style="font-family: monospace;">cimcli ns -l [3ffe:1:2:1]:5989</span></big><br> |
By registering any provider which fails to do appropriate authorization |
|
checks, the consequences may include information leakage, data |
|
corruption, or unintended elevation of privilege. Please ensure that |
|
one of the following mechanisms is used to ensure appropriate access to |
|
your systems and data:<br> |
|
1. Only install/register providers which perform authorization |
|
appropriate for your environment.<br> |
|
</font> |
|
<div style="margin-left: 40px;"><font style="color: rgb(0, 0, 0);" |
|
color="RED">a. For providers, this may include registering to |
|
'Run-as-requestor' (not available prior to Pegasus 2.5) and/or |
|
performing authorization checks within the provider.<br> |
|
b. For administrators, ensure that the providers you have registered in |
|
your environment have performed sufficient authorization checks. Also, |
|
monitor announcements of security defects in those providers and follow |
|
the recommendations in those announcements as soon as possible. <br> |
|
c. For distributors of Pegasus or providers, ensure that the providers |
|
you are shipping have performed appropriate authorization checks, and |
|
relay announcements of discovered security defects to your users.</font><br> |
|
</div> | </div> |
<font style="color: rgb(0, 0, 0);" color="RED">2. Restrict users with |
|
access to Pegasus to a specific authorized user group of trusted |
|
individuals.<br> |
|
3. Namespace authorization is also available.<br> |
|
<br> | <br> |
</font><span class="norm">For administration issues please refer to |
For more information on |
the SSL Admin Guide found at: </span>pegasus/doc/PegasusSSLGuidelines.htm<br> |
specifying |
<h4><b>Server Security</b></h4> |
IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF |
<ol style="margin-top: 0in;" start="1" type="1"> |
RFC 2373 - IP Version |
<li class="MsoNormal" style="color: black;">Basic Authentication |
6 Addressing Architecture</a> |
(Note that Digest based security is not implemented)</li> |
and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 - |
<li class="MsoNormal" style="color: black;">PAM authentication <o:p></o:p></li> |
Format for |
<li class="MsoNormal" style="color: black;">SSL support - SSL is |
Literal IPv6 Addresses in URL's</a>.<br> |
implemented in Pegasus using the <span class="SpellE">OpenSSL</span> |
<h4><font color="#000000">IPv6 on Linux</font></h4> |
libraries. Pegasus does not provide the <span class="SpellE">OpenSSL</span> |
<p>Modern Linux distributions already |
libraries but SSL can be used on any platform supported by <span |
contain IPv6-ready kernels, the |
class="SpellE">OpenSSL</span>. Minimum level known to work |
IPv6 capability is generally compiled as a module, but it's possible |
is 0.9.6c . This release of Pegasus was tested with |
that this module is not loaded automatically on startup.</p> |
0.9.6k. See <a |
<p><span style="font-weight: bold;">Note: |
href="http://www.openpegasus.org/pp/uploads/40/Application%20Data/Microsoft/Word/www.openssl.org">openssl.org</a> |
</span>you shouldn't use kernel series 2.2.x, because it's not |
for <span class="SpellE">OpenSSL</span> release information<o:p>.</o:p></li> |
IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no |
<li class="MsoNormal" style="color: black;">SSL levels<br> |
longer improved according to definitions in latest RFCs. It's recommend |
<span class="norm"></span><font style="color: rgb(0, 0, 0);">SSLv3 |
to use series 2.6.x now.<br> |
and TLSv1 by default. SSLv2 is |
|
disabled by default and only enabled by a compile time option</font>. |
|
See<a |
|
href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502"> |
|
PEP 200</a> for details on |
|
configuration.<br> |
|
</li> |
|
</ol> |
|
<b> </b> |
|
<h4><b>Client Security</b><span style="font-family: times new roman;"><span |
|
style="font-style: italic;"><span style="font-weight: bold;"></span></span></span></h4> |
|
Certificate management |
|
and User-based certificate authentication . A new control provider and |
|
CLI for certificate management tasks. It expands upon the existing SSL |
|
client verification support by providing a robust solution to managing |
|
client certificates and certificate revocation lists via standard CIM |
|
operations. It allows certificates to be associated with particular |
|
system users for enhanced authorization capabilities.<br> |
|
<span class="norm"></span><font style="color: rgb(0, 0, 0);">CN/ Host |
|
name checks are not performed as a function of SSL or client libraries |
|
and are the responsibility of the client to implement on their |
|
own. See the SSL guide found in the /pegasus/doc directory for |
|
more details on client security.</font><br> |
|
Note: <span class="norm"><font><font color="RED"><span |
|
style="color: rgb(0, 0, 0);">WBEM clients are responsible for SSL |
|
certificate verification using Pegasus and/or SSL libraries as |
|
appropriate. Consequences of not doing so include leakage of |
|
authentication credentials to unauthorized parties.</span> </font></font></span> |
|
<h4><b>Platform Management Functions</b></h4> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Configuration through |
|
the defined configuration parameters (cimconfig) and server command |
|
line options.<span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);" color="RED"> NOTE: When installed |
|
as a service on Windows, setting the run-time config option |
|
enableAuthentication to true can result in improper operation of the |
|
SLP |
|
provider and other providers. In order to circumvent this defect, an |
|
Administrator should change the user that the service runs under from |
|
the Local |
|
System user to a local, privileged user (e.g. Administrator). |
|
See bugzilla 4142 for details.</font> <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">Daemon/service |
|
operation of the Pegasus CIM Server on all supported platforms<o:p> |
|
with the exception of HP OpenVMS.<br> |
|
</o:p></li> |
|
<li class="MsoNormal" style="color: black;">Operation statistics |
|
capture using the <span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);">CIM_StatisticalData </font>classes in |
|
the DMTF Interop model. This |
|
function is considered alpha quality and conditionally compiled. <br> |
|
</li> |
|
<li class="MsoNormal" style="color: black;">Multiple |
|
pluggable provider managers. Provider managers are provided for |
|
the Pegasus C++ provider interface, the CMPI C provider interface and |
|
an alpha quality Java provider interface (JMPI).</li> |
|
<li class="MsoNormal" style="color: black;">Platform Globalization |
|
- Pegasus includes support for unicode data transfers and includes a |
|
mechanism for message support in multiple languages using the open |
|
source ICU libraries (<a href="http://oss.software.ibm.com/icu/">http://oss.software.ibm.com/icu/</a>). |
|
Note that this is still marked experimental.</li> |
|
<li class="MsoNormal" style="color: black;">Out-of-process |
|
providers (Experimental) - See PEP 072 for more information on use of |
|
this feature </li> |
|
<li class="MsoNormal" style="color: black;">Shared class namespaces |
|
(Experimental) - See PEP 129 for more information on use of this feature</li> |
|
<li class="MsoNormal" style="color: black;">Remote providers for |
|
the CMPI provider interface (Experimental) - See PEP 130 for more |
|
information on use of this feature</li> |
|
</ol> |
|
<h4><b>SLP Discovery</b></h4> |
|
<p>SLP support is included but is conditionally compiled in or out on |
|
a platform basis. <a |
|
href="http://www.openpegasus.org/pp/uploads/40/8502/PEP200_RecommendedReleaseOptions.htm"> |
|
PEP 200</a> describes the use of proper environment variable use to |
|
enable or disable this code. PEGASUS_DISABLE_SLP and |
|
PEGASUS_ENABLE_SLP are the environment variables that control inclusion |
|
of this feature. Once compiled, SLP |
|
support is enabled with the slp configuration parameter (slp=true). SLP |
|
support includes an SLP service agent in the Pegasus CIM sever and |
|
generates SLP advertisements compatible with the DMTF slp template |
|
specification. The SLP support also includes extensions to the |
|
CIM Client libraries to execute SLP User Agent requests and analyze the |
|
results (note that these interfaces are not yet part of the Pegasus |
|
public SDK).<br> |
|
Note: Pegasus on Windows is built with SLP support on by default and to |
|
exclude it from the build, then PEGASUS_DISABLE_SLP must be set.<br> |
|
</p> | </p> |
<h4>Provider Managers</h4> |
<p>To check whether your current |
<p>Pegasus is designed to support multiple Provider Managers to allow |
running |
multiple provider interfaces to the CIMOM. The two default |
kernel supports IPv6, take a look into your /proc filesystem. The entry |
provider managers are the Pegasus C++ Interface and Common |
/proc/net/if_inet6 must exist. A short automated test looks like:<br> |
Manageability Programming Interface (CMPI) Interface.<br> |
|
</p> | </p> |
<blockquote> |
<div |
<h5><b style="">CMPI C interface Provider Manager<o:p></o:p></b></h5> |
style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font |
<span style="font-family: "times new roman";">Pegasus 2.5 includes |
color="#000000">test -f |
a provider manager for the CMPI C interfaces. This C interface is the |
/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"</font></big></div> |
result of a project by the IBM SBLIM team (see |
<p>For more information on |
http://sblim.sourceforge.net) and is written to the Common |
enabling |
Manageability Programming Interface, which is an OpenGroup standard. |
IPv6 in the Linux kernel and configuring network interfaces, refer to |
The CMPI |
<a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux |
specification is available at: |
Documentation Project's IPv6 HOWTO</a>.<br> |
http://www.opengroup.org/bookstore/catalog/c051.htm. This provides a |
<br> |
standardized C level interface for creating providers that can be |
<span style="font-weight: bold;">Warning</span>: |
registered with the Pegasus CIM Server in the same manner as the |
There is currently an open issue with RedHat to address a problem that |
current C++ providers. </span><span |
is seen intermittently on RHEL5 and SLES10 systems. This problem is |
style="font-family: "times new roman";"><span class="norm"></span></span>The |
described in <span style="color: rgb(153, 51, 153);"> |
ability for CMPI providers to do user authorization is now available in |
<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
Pegasus 2.5.<br> |
bug 6586</a> |
<span style="font-family: "times new roman";"> <br> |
</span>and<span style="color: rgb(153, 51, 153);"> |
Information on writing providers with the CMPI interface is available |
<a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat |
in the specification today (see above) and in the following documents |
bug 248052</a>, |
(http://sblim.sourceforge.net/whitepaper.html and |
</span>and manifests itself as an intermittent IPv6 socket failure. You |
http://sblim.sourceforge.net/presentations.html) and readme.cmpi in the |
should be aware |
Pegasus source root directory.</span><br> |
that OpenPegasus with IPv6 enabled may be significantly impacted in |
<h5>JMPI Java Interface Provider Manager</h5> |
these |
<p>Pegasus includes an experimental provider manager for Java |
environments.</p> |
provider interfaces based on the SNIA provider interface |
<h4><font color="#000000">IPv6 on Windows</font></h4> |
definitions. This provider manager is considered alpha |
<p>Microsoft provides supported IPv6 |
quality and is not compiled in the default build. See |
implementations for Windows Server |
readme.jmpi in the Pegasus source root directory for more information.</p> |
2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service |
</blockquote> |
Pack 2 (SP2), and Windows CE .NET 4.1 and later.</p> |
</blockquote> |
On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span> |
<h3><b> Providers</b></h3> |
tool to install, uninstall, and |
<div style="margin-left: 40px;">New for 2.5 is the ability of Providers |
query |
to run out of process at |
your IPv6 configuration. For example:<br> |
request user- level and running CMPI providers remotely or out of |
<br> |
process space.<br> |
<div |
<br> |
style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font |
<span class="norm"></span>Administrators should check the providers to |
color="#000000">ipv6 install<br> |
ensure that the provider vendor |
ipv6 if</font></big></div> |
has made use of available authorization capability.<br> |
<p>Windows Vista |
</div> |
and Windows Server 2008 support an integrated |
<p style="margin-left: 40px;">There are a number of providers available |
IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack. |
in the Pegasus release. |
Note that the OpenPegasus IPv6 support has not yet been tested |
This includes providers in the following categories:</p> |
on Windows Vista or Windows Server 2008.<br> |
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;"> |
<br> |
<h4>Pegasus Internal Providers</h4> |
For more information on |
<p>Pegasus provides a set of "internal" providers that have direct |
installing, configuring, and using IPv6 on Windows platforms, refer to |
access to the CIMOM for information and provide information and |
the document |
services to support the CIMOM and its administration. The |
<a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"><font |
providers in this category are mostly defined in the directory |
color="#000000">IPv6 |
src/pegasus/controlproviders and include support for the following |
for Microsoft Windows: Frequently Asked Questions</font></a>.<br> |
classes:</p> |
|
<ul> |
|
<li>DMTF Interop classes including __Namespace, <span |
|
class="SpellE">CIM_Namespace</span>, <span class="SpellE">CIM_ObjectManager</span>, |
|
<span class="SpellE">CIM_CommunicationMechanism, and |
|
CIMOMStatistics.</span></li> |
|
</ul> |
|
<h4><span class="SpellE">CMPI Remote</span></h4> |
|
<h4><span class="SpellE"></span></h4> |
|
<span class="SpellE">Pegasus includes an experimental support for |
|
running CMPI providers to be run on remote systems without the need for |
|
an extra CIMOM. It uses a special proxying provider to relay requests |
|
to a remote location using so-called communication layers. The remote |
|
side has to start a CMPIRDaemon process, which accepts remote requests |
|
and passes them on to CMPI style providers.<br> |
|
</span><span class="SpellE"></span><span class="SpellE"><br> |
|
</span> |
|
<h4><b>Generic Providers</b></h4> |
|
<p>Generic <span class="SpellE">OperatingSystem</span> provider. See |
|
the |
|
directory <span class="SpellE">src</span>/Providers/generic.</p> |
|
<h4><b>Test/Sample Providers</b></h4> |
|
<p>See the directories <span class="SpellE">src/Providers/TestProviders</span> |
|
and <span class="SpellE">src</span>/Providers/Sample for more |
|
information about test and |
|
sample providers.</p> |
|
<h4><b>Managed System Providers</b></h4> |
|
<p><span class="SpellE">ComputerSystem</span>, <span class="SpellE">DNSAdmin</span>, |
|
<span class="SpellE">DNSService</span>, Operating System, Process, |
|
Processor. For |
|
more information on these providers see the documentation for each |
|
provider in |
|
the directory <span class="SpellE">src/Providers/ManagedSystem</span></p> |
|
<h4><span class="SpellE">Server Statistics<br> |
|
</span></h4> |
|
CIM Server statistics, based on the DMTF 'CIM_StatisticalData' class, |
|
are implemented in this release. The statistics gathering is disabled |
|
by default. It may be enabled or disabled by performing a |
|
ModifyInstance operation on the singleton 'CIM_ObjectManager' instance |
|
in the 'PG_InterOp' namespace to set the GatherStatisticalData property |
|
to 'true' or 'false'. This property setting is persistent across CIM |
|
Server restarts. A statistics display test tool, cimperf, is available |
|
from the Pegasus CVS repository. |
|
<h4><br> |
|
<span class="SpellE"></span></h4> |
|
<h4><span class="SpellE">SLP Provider</span></h4> |
|
<p><span class="SpellE">This provider acts as the definer of |
|
SLP information for SLP registration and also controls the Pegasus SLP |
|
Service Agent. It is treated as a normal provider rather than a control |
|
provider because it does not use internal functions of the CIMOM to |
|
generate any of its information today. (conditionally compiled today)<br> |
|
</span></p> |
|
<br> |
|
<br> |
|
</blockquote> |
|
<h3><span class="SpellE"><b>CIM_Schema</b></span></h3> |
|
<p>The default <span class="SpellE">CIM_Schema</span> loaded with this |
|
release is |
|
the DMTF CIM 2.9, Final release. In addition, Pegasus includes |
|
a number of |
|
local classes defined for Pegasus. These are defined in the |
|
pegasus/Schemas |
|
directory. <span style=""></span>There are also a |
|
number of older schema available in the CVS.</p> |
|
<p>The mechanism to install other schemas than the default is defined |
|
in the mak/config.mak</p> |
|
<p style="margin-bottom: 12pt;"><b>NOTE:</b> The CIM 2.5 schema is |
|
maintained in the |
|
CVS repository because it remains the basis for parts of the Pegasus |
|
test |
|
environment.</p> |
|
<h3><b>Pegasus MOF Compilers</b></h3> |
|
<p>Pegasus implements a MOF compiler that can operate either at the |
|
client |
|
interface to the Pegasus CIM Server (<span class="SpellE">cimmof</span>) |
|
or directly interfacing with a CIM |
|
repository (<span class="SpellE">cimmofl</span>).</p> |
|
<p>The direct interface compiler is used primarily to provide an |
|
initial |
|
class/instance repository. <font color="#ff0000"><b>WARNING:</b></font> |
|
the use of <span class="SpellE">cimmofl</span> |
|
to manipulate instances in the repository bypasses any provider that is |
|
registered to serve these instances and simply installs the |
|
instances in the |
|
instance repository; this may result in 1) bad data in the repository |
|
if there are registered providers, 2) corruption of the repository if |
|
the CIM Server is running or, 3) MOF data that is loaded but not |
|
available until the server is stopped and restarted in some |
|
cases. Use of <span class="SpellE">cimmofl in general is |
|
discouraged and particularly </span> to manipulate |
|
instances served by a registered providers (ex. Provider registration). |
|
<br> |
|
</p> | </p> |
<h3><b>Client Tools</b></h3> |
<h4><font color="#000000">Testing your OpenPegasus IPv6 |
Lightweight statistics are now implemented for |
support</font></h4> |
the |
As part of the OpenPegasus |
client. The client statistics surfaces the elapsed time spent in the |
automated tests, the TestClient, g11ntest, and IndicationStressTest |
client, |
test clients were modified to run tests using the IPv6 loopback address |
and the |
(::1) if PEGASUS_ENABLE_IPV6=true.<br> |
elapsed time spent on the network between client and server.<br> |
<br> |
<br> |
You can also perform manual |
<h3><b>Pegasus CIM Server <span class="SpellE">Administration</span></b></h3> |
tests |
<ol style="margin-top: 0in;" start="1" type="1"> |
using the IPv6 loopback or a real IPv6-configured network interface. |
<li class="MsoNormal" style="color: black;"><span class="SpellE">cimuser</span> |
For example, using the IPv6 loopback on a system with OpenPegasus |
- Manage Pegasus CIM Server Users.<o:p></o:p></li> |
running on the WBEM standard http port of 5988:<br> |
<li class="MsoNormal" style="color: black;"><span class="SpellE">cimconfig</span> |
<div style="margin-left: 40px;"><br> |
- Manage the Pegasus CIM Server configuration parameters.<o:p></o:p></li> |
<big style="font-family: monospace;"> osinfo -h ::1</big></div> |
<li class="MsoNormal" style="color: black;"><span class="SpellE">cimauth</span> |
<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2> |
- Manage the CIM Server authorization characteristics. Today this is |
<p>Support for forward-compatibility is a fundamental design principle |
authorizing users to namespaces.<o:p></o:p></li> |
for the |
<li class="MsoNormal" style="color: black;"><span class="SpellE">cimprovider</span> |
OpenPegasus project. As a Community, our goal is for well-behaved |
- Manage information about the providers .</li> |
OpenPegasus |
</ol> |
Providers or Clients, using only the externally defined OpenPegasus |
<br> |
interface, |
<span style="font-weight: bold;">Server admin |
to continue to work with a minor version upgrade of OpenPegasus. |
note:</span><br> |
However, there |
<div style="margin-left: 40px;">The default behavior for determining |
are certain classes of errors (e.g., non-compliance with a standard |
the CIM server's HTTP and HTTPS ports has changed. In previous |
that |
releases, any value in /etc/services would override a port explicitly |
significantly affects interoperability) that may require the Community |
specified in the configuration. The new order for determining the |
to make |
CIM server's HTTP and HTTPS ports is as follows:<br> |
potentially incompatible changes. The following table contains a list |
1) An explicitly specified port value takes precedence over any other |
of defect |
values.<br> |
fixes that MAY impact, even well-behaved, OpenPegasus Providers or |
</div> |
Clients when |
<div style="margin-left: 40px;">2) If no port is specified, the value |
upgrading to this OpenPegasus release.</p> |
in /etc/services is used.<br> |
<p> </p> |
3) If no value is specified in /etc/services, the default WBEM port is |
<table style="font-family: Arial;" bordercolordark="#666666" |
used.<br> |
bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="80%"> |
</div> |
<tbody> |
<h3><b>Information client tools</b></h3> |
<tr align="center"> |
<p>These tools provide information on the objects managed by the server.</p> |
<th bgcolor="#00ffff" width="10%">Bugzilla #</th> |
<ol style="margin-top: 0in;" start="1" type="1"> |
<th bgcolor="#00ffff">Description</th> |
<li class="MsoNormal" style="color: black;"><span class="SpellE">tomof</span> |
</tr> |
- output classes and/or instance information from the Pegasus |
<tr align="center"> |
repository in MOF or XML format.<o:p></o:p></li> |
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8830">8830</a></td> |
<li class="MsoNormal" style="color: black;"><span class="SpellE">dnsinfo</span> |
<td align="left">The requirement for providers (CMPI and C++) to |
- Generate a set of standard information on the <span class="SpellE">Domain</span> |
filter properties from instances has been relieved. The server will do |
Name System (DNS) configuration from CIM Classes. Note that the |
the filtering at the protocol adapter level. To avoid a negative impact |
information generated is dependent on the information available from |
on performance the CIMInstance::filter() and |
providers and differs from system to system.<o:p></o:p></li> |
CMPIInstanceFT.setPropertyFilter() functions have been changed to a |
<li class="MsoNormal" style="color: black;"><span class="SpellE">ipinfo</span> |
NOP. This may be a change in behavior for provider relying in some |
- Generates a set of standard information from the Network |
unknown way on the instance being filtered through these functions. To |
Schema. Information generated varies by system because of the |
allow users to actually filter properties from an instance, new |
level of provider support.<o:p></o:p></li> |
function CIMInstance::filterInstance() will actually filter properties |
<li class="MsoNormal" style="color: black;"><span class="SpellE">osinfo</span> |
from an instance exactly as the CIMInstance::filter() did in previous |
- Generate a set of standard information on the Operating System from |
versions of Pegasus.</td> |
CIM Classes. Note that the information generated is dependent on the |
</tr> |
information available from providers and differs from system to system<o:p></o:p></li> |
<tr align="center"> |
</ol> |
<td></td> |
<h3><b>Test support Tools</b></h3> |
<td></td> |
<ol style="margin-top: 0in;" start="1" type="1"> |
</tr> |
<li class="MsoNormal" style="color: black;">Pegasus unit tests |
<tr align="center"> |
(available through the "tests" option on the Pegasus make files) these |
<td></td> |
tests are defined throughout the Pegasus source tree typically in |
<td></td> |
"tests" directories. <o:p></o:p></li> |
</tr> |
<li class="MsoNormal" style="color: black;">The Pegasus test suite |
<tr align="center"> |
(see the pegasus/tests directory<span class="SpellE"></span>)<o:p></o:p></li> |
<td></td> |
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">TestClient</span> |
<td></td> |
</b>- Basic client for overall platform operation testing. <o:p></o:p></li> |
</tr> |
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">wbemexec</span></b> |
<tr align="center"> |
- Test tool that sends/receives XML from XML input.<o:p></o:p></li> |
<td></td> |
<li class="MsoNormal" style="color: black;"><b>CLI</b> - Command line |
<td></td> |
interface for Client commands.<o:p></o:p></li> |
</tr> |
<li class="MsoNormal" style="color: black;"><b>Benchmark Test</b> - A |
</tbody> |
benchmark test environment is provided which includes both a client and |
</table> |
provider component. See <span class="SpellE">src/clients/benchmarkTest</span> |
<h2>OpenPegasus Relationship to |
for more information.<o:p></o:p></li> |
|
</ol> |
|
<h3><b>Pegasus Interface APIs</b></h3> |
|
<p>Details of the Pegasus public interfaces for this release are listed |
|
in PEP 209 |
|
available from the web <span class="GramE">site(</span><a |
|
href="http://www.openpegasus.org/pp/uploads/40/Administrator/My%20Documents/processes/www.openpegasus.org">www.openpegasus.org</a>). |
|
That document is the <span class="SpellE">authorative</span> source |
|
for the list of publicly supported Pegasus APIs. The Client |
|
and Provider API were originally frozen at the Pegasus version 2.1 |
|
release. The interfaces in the release of Pegasus 2.1 are forward |
|
compatible to this release. Well-behaved clients and providers compiled |
|
to the Pegasus 2.1 or 2.2 interfaces should be compatible with this |
|
release without compilation. There have been extensions and new |
|
interfaces added for this release and these are marked as experimental. |
|
The Pegasus public |
|
interfaces includes the following major functions</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Client APIs<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">Provider APIs<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">CIM Object and System |
|
function APIs</li> |
|
</ol> |
|
<p>In addition, there are other client interfaces which are not today |
|
in the public SDK including:</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: rgb(0, 0, 0);"><span style="" |
|
lang="DA">CIM Listener APIs</span></li> |
|
<ul style="color: rgb(0, 0, 0);"> |
|
<li class="MsoNormal">CIM Listener |
|
is a component that can be used to consume indications without a |
|
dependency on the Pegasus CIMOM. In environments where no CIMOM is |
|
running or a physical separation between the indication listener and |
|
the CIMOM is desired, CIM Listener fits the bill. Still, there are |
|
several enhancements that are necessary to make CIM Listener scalable. <font |
|
style="color: rgb(0, 0, 0);">Enhancements were deemed significant |
|
enough to propose a new listener that builds off CIMListener's |
|
basic capabilities, yet allows the existing CIMListener to remain the |
|
same.</font></li> |
|
<ul> |
|
<li><font size="2"><b>New CIM Listener now provides selective |
|
indication delivery.</b><span class="norm"></span></font><br> |
|
</li> |
|
<li><span class="norm"></span><font size="2"><b>New CIM Listener |
|
keeps all consumer libraries in memory for the duration of its |
|
execution.</b><span class="norm"></span></font><br> |
|
</li> |
|
<li><span class="norm"></span><font size="2"><b>New CIM Listener |
|
is now pluggable.</b><br> |
|
<span class="norm"></span></font></li> |
|
<li><span class="norm"></span><font size="2"><b>New CIM Listener |
|
now provides reliable indication delivery.</b></font></li> |
|
</ul> |
|
</ul> |
|
<li class="MsoNormal" style="color: black;"><span lang="da">SLP |
|
Client (User Agent) APIs which are extensions to the Client APIs</span></li> |
|
</ol> |
|
<p class="MsoNormal"><span style="color: black;"><o:p> </o:p></span></p> |
|
<p class="MsoNormal"><span style="color: black;">The APIs are |
|
documented in |
|
their respective header files and in HTML documentation based on |
|
the information |
|
in the header files extracted with the doc++ tool will be available on |
|
the |
|
OpenPegasus web site.<br> |
|
<o:p></o:p></span></p> |
|
<h3><b>WMI <span class="SpellE">Mapper</span></b></h3> |
|
<p>The WBEM to WMI <span class="SpellE">Mapper</span> provides a way |
|
to access |
|
WMI data from Windows platform systems. It converts incoming XML/CIM |
|
requests |
|
to Microsoft WMI requests, executes the requests, converts the results |
|
to |
|
XML/CIM and returns the results to the client. WMI <span class="SpellE">Mapper</span> |
|
receives an HTTP message containing the XML/CIM request. It decodes the |
|
XML |
|
message and extracts from the HTTP message header the user credentials |
|
provided |
|
on the connection (username and password). The WMI <span class="SpellE">Mapper</span> |
|
authenticates these credentials, verifying if the provided credentials |
|
have |
|
access to the desired WMI data. This is done because the WMI <span |
|
class="SpellE">Mapper</span> runs as a service, logged on using an |
|
account with |
|
administrative rights (which has all access to WMI data). Because of |
|
this, the |
|
WMI <span class="SpellE">Mapper</span> impersonates the user |
|
credentials provided |
|
on the HTTP message to ensure that the calling user has rights to |
|
browse WMI |
|
data. Hence, ALL requests made to the WMI <span class="SpellE">Mapper</span> |
|
MUST |
|
contain user credentials.<br> |
|
</p> |
|
<h3><b><b>Indication Handlers</b></b></h3> |
|
System Log Indication Handler<br> |
|
<div style="margin-left: 40px;">The SysLog Indication Handler is a new |
|
for 2.5 |
|
type of Indication Handler which allows CIM Indications to be delivered |
|
to the system syslog file. It has following features:<br> |
|
</div> |
|
<ul> |
|
<li>Each syslog file entry has a tag 'CIM Indication' to distinguish |
|
an entry made by Syslog Indication Handler.</li> |
|
</ul> |
|
<ul> |
|
<li>If a subscriber includes PerceivedSeverity property in the SELECT |
|
list of the filter condition for the indication, the PerceivedSeverity |
|
will be mapped to syslog error severity. Otherwise, syslog error |
|
severity 'LOG_INFO' is used.</li> |
|
<li>See <a |
|
href="http://www.openpegasus.org/pp/uploads/40/7165/PEP206-SystemLogIndicationHandler.htm">PEP |
|
206</a> for details.<br> |
|
</li> |
|
</ul> |
|
<br> |
|
Email Indicaiton Handler<br> |
|
<div style="margin-left: 40px;">The Email Indication Handler is a new |
|
for 2.5 |
|
type of Indication Handler that allows CIM Indications to be delivered |
|
to a specified e-mail address. See <a |
|
href="http://www.openpegasus.org/pp/uploads/40/7166/PEP207-EmailIndicationHandler.htm">PEP |
|
207</a> for details. <br> |
|
</div> |
|
<br> |
|
<br> |
|
<ol> |
|
</ol> |
|
<h2><a name="Relationship_to_CIMWBEM_Standards"></a>Relationship to |
|
CIM/WBEM Standards</h2> | CIM/WBEM Standards</h2> |
<p>Pegasus was designed and implemented to comply with the DMTF | <p>Pegasus was designed and implemented to comply with the DMTF |
specifications The following table defines the level of the DMTF |
CIM/WBEM specifications The following table defines the level of the |
specifications which which Pegasus conforms today.</p> |
DMTF specifications to which this version of Pegasus aims to conform |
<table id="AutoNumber1" border="1" cellspacing="1" width="100%"> |
today.</p> |
|
<table id="AutoNumber1" border="1" cellspacing="1" width="80%"> |
<tbody> | <tbody> |
<tr> | <tr> |
<td bgcolor="#00ffff" width="33%"><b>DMTF Specification</b></td> | <td bgcolor="#00ffff" width="33%"><b>DMTF Specification</b></td> |
<td bgcolor="#00ffff" width="33%"><b>Specification Version</b></td> | <td bgcolor="#00ffff" width="33%"><b>Specification Version</b></td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0004 CIM Specification</td> |
<td width="33%">DSP 0004 - CIM Infrastructure Specification</td> |
<td width="33%">Version 2.2 with Addendum</td> |
<td width="33%">Version 2.3 Final, 4 October 2005</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0200 - CIM Operations over HTTP</td> | <td width="33%">DSP 0200 - CIM Operations over HTTP</td> |
<td width="33%">1.1, final, 6 January 2002</td> |
<td width="33%">Version 1.2, Final, January 09, 2007</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0201 - Representation of CIM in XML</td> | <td width="33%">DSP 0201 - Representation of CIM in XML</td> |
<td width="33%">2.1, preliminary, May 2, 2002</td> |
<td width="33%">Version 2.2 Final, January 09, 2007</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0202 - CIM Query Language Specification</td> |
|
<td width="33%">1.0.0, preliminary, 9 December 2004</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0205 - WBEM Discovery using SLP</td> | <td width="33%">DSP 0205 - WBEM Discovery using SLP</td> |
<td width="33%">1.0, preliminary, 27 January 2004</td> | <td width="33%">1.0, preliminary, 27 January 2004</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">WBEM SLP Template</td> |
<td width="33%">DSP 0206 - WBEM SLP Template</td> |
<td width="33%">1.0.0</td> |
<td width="33%">1.0.0, Preliminary, January 2004</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">CIM Schema </td> | <td width="33%">CIM Schema </td> |
<td width="33%">2.9 Final, Jan. 2005</td> |
<td width="33%">2.22.1 Final, 22 Oct 2009( default) </td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<h2><b><span style="font-family: Times;"><a name="Supported Platforms">Supported |
<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. However, today there are a number of known |
|
differences. |
|
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. 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"> </font>For |
|
more information see the Pegasus CVS file:<a name="comtag_137"><font |
|
size="2"> </font><font face="Courier New" size="2"> 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> </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. |
|
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). </span> Pegasus |
|
today expects the provider to complete the qualifiers on instances in |
|
accordance with the specification and generally the interpretation is |
|
that Pegasus applies class level qualifiers when the includeInstance |
|
parameter is supplied on instance operations. However, Pegasus |
|
today is inconsistent in the return of qualifiers so that the user |
|
should NOT depend on Pegasus accurately honoring the includeQualifier |
|
parameter for instance operations. In the future it is expected |
|
that Pegasus will deprecate the use of qualifiers on instance |
|
operations completely. When Pegasus uses object normalization, |
|
the normalizer does apply qualifiers to returned instances if the |
|
includeQualifiers operation parameter is set.</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. </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. This behavior is documented |
|
in Pegasus bug <a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8773">8773</a> |
|
and there is a patch available for users. However, since the |
|
change is considered a change to behavior this will not be patched |
|
until pegasus does a major version update. NOTE: There are some |
|
documented bugs in Pegasus such as this that the OpenPegasus team feels |
|
cannot be modified until a major version update. These bugs are |
|
documented with the Bugzilla tag <big style="font-weight: bold;"><samp>"3.0_TARGET".</samp></big></li> |
|
<li><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> | Platforms</a></span></b></h2> |
<p>Each Pegasus release lists as 'active' platforms those |
<p align="left">Each OpenPegasus release lists as 'active' platforms |
|
those |
hardware/software platforms that have recognized ports for the Pegasus | hardware/software platforms that have recognized ports for the Pegasus |
code |
code base |
base including a maintainer for the platform that will be willing to |
including a maintainer for the platform that will be willing to |
regularly document issues and/or fix defects as the Pegasus |
regularly |
code base is changed. |
document issues and/or fix defects as the Pegasus code base is |
|
changed. |
Pegasus may be operable on other platforms (ex. Windows 98) but without | Pegasus may be operable on other platforms (ex. Windows 98) but without |
a group | a group |
to provide the role of test and maintenance, correct operation of | to provide the role of test and maintenance, correct operation of |
Pegasus cannot be |
Pegasus |
assured. In all cases, including the active platforms, it is the |
cannot be assured. In all cases, including the active platforms, |
|
it is the |
responsibility of the entity that packages and/or compiles OpenPegasus | responsibility of the entity that packages and/or compiles OpenPegasus |
for shipment or deployment, to read, and actively monitor the Pegasus |
for |
bugzilla database for a list of relevant defects that affect their |
shipment or deployment, to read, and actively monitor the Pegasus |
platform. The platforms that are considered 'active' for this |
bugzilla |
Pegasus release are:<br> |
database for a list of relevant defects that affect their |
<span class="norm"></span><br> |
platform. |
</p> |
The platforms that are considered ported are shown in the two tables |
<table class="MsoNormalTable" style="width: 302.25pt;" border="1" |
below. |
cellpadding="0" cellspacing="1" height="409" width="504"> |
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> | <tbody> |
<tr style=""> | <tr style=""> |
<td | <td |
style="padding: 0.75pt; background: rgb(153, 255, 153) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 126.75pt;" |
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" width="211"> |
height="26"> |
<p class="MsoNormal"><b><span style="color: black;">Platform and | <p class="MsoNormal"><b><span style="color: black;">Platform and |
OS</span></b><span style="color: black;"><o:p></o:p></span></p> | OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td | <td |
style="padding: 0.75pt; background: rgb(153, 255, 153) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 173.25pt;" |
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" width="289"> |
height="26"> |
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span | <p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span |
style="color: black;"><o:p></o:p></span></p> | style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" |
<td style="padding: 0.75pt;"> |
width="211"> |
<p class="MsoNormal"><span style="color: black;">HP-UX<o:p> |
<p class="MsoNormal"><span style="color: black;">HP-UX<o:p></o:p></span></p> |
PA_RISC and Itanium</o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" |
<td style="padding: 0.75pt;"> |
width="289"> |
|
<p class="MsoNormal"><span style="color: black;">HP <span | <p class="MsoNormal"><span style="color: black;">HP <span |
class="SpellE">aC</span>++ B3910B<o:p></o:p></span></p> | class="SpellE">aC</span>++ B3910B<o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" |
<td style="padding: 0.75pt;"> |
width="211"> |
|
<p class="MsoNormal"><span class="SpellE"><span | <p class="MsoNormal"><span class="SpellE"><span |
style="color: black;">Linux on Power</span></span><span | style="color: black;">Linux on Power</span></span><span |
style="color: black;"><o:p></o:p></span></p> | style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" |
<td style="padding: 0.75pt;"> |
width="289"> |
|
<p class="MsoNormal"><span class="SpellE"><span | <p class="MsoNormal"><span class="SpellE"><span |
style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> | style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" |
<td style="padding: 0.75pt;"> |
width="211"> |
|
<p class="MsoNormal"><span class="SpellE"><span | <p class="MsoNormal"><span class="SpellE"><span |
style="color: black;">zLinux</span></span><span style="color: black;"><o:p></o:p></span></p> | style="color: black;">zLinux</span></span><span style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" |
<td style="padding: 0.75pt;"> |
width="289"> |
|
<p class="MsoNormal"><span class="SpellE"><span | <p class="MsoNormal"><span class="SpellE"><span |
style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> | style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" |
<td style="padding: 0.75pt;"> |
width="211"> |
|
<p class="MsoNormal"><span style="color: black;">Linux Itanium<o:p></o:p></span></p> | <p class="MsoNormal"><span style="color: black;">Linux Itanium<o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" |
<td style="padding: 0.75pt;"> |
width="289"> |
|
<p class="MsoNormal"><span class="SpellE"><span | <p class="MsoNormal"><span class="SpellE"><span |
style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> | style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" |
<td style="padding: 0.75pt;"> <span style="color: black;"><font |
width="211"> |
size="3">Linux IA-32</font></span></td> |
<p class="MsoNormal"><span style="color: black;">Linux IA-32<o:p></o:p></span></p> |
<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> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" |
<td style="padding: 0.75pt;"> |
width="289"> |
|
<p class="MsoNormal"><span class="SpellE"><span | <p class="MsoNormal"><span class="SpellE"><span |
style="color: black;">gcc</span></span><span style="color: black;"> | style="color: black;">gcc</span></span><span style="color: black;"> |
(versions 2.9x and 3.xx)<o:p></o:p></span></p> |
(versions 3.xx, 4.xx)</span></p> |
</td> | </td> |
</tr> | </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> |
|
|
|
<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=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="91" |
<td |
width="211"> |
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;" |
<p class="MsoNormal"><span style="color: black;">Windows 2000<o:p></o:p></span></p> |
height="26"> |
</td> |
<p class="MsoNormal"><b><span style="color: black;">Platform and |
<td style="padding: 0.75pt; width: 173.25pt;" height="91" |
OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
width="289"> |
</td> |
<p class="MsoNormal"><span style="color: black;" lang="NL">Microsoft |
<td |
Visual C++ Ver 6 and Microsoft .Net compiler Version. </span><span |
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%;" |
style="color: black;">Works on VC .NET 2003 (<span class="SpellE">aka</span> |
height="26"> |
v7.1)<o:p></o:p></span></p> |
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="padding: 0.75pt; width: 126.75pt;" height="69" |
<td style="padding: 0.75pt;"> <font size="3">Windows XP</font> |
width="211"> |
<p></p> |
<p class="MsoNormal"><span style="color: black;">Windows XP<o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt; width: 173.25pt;" height="69" |
|
width="289"> |
|
<p class="MsoNormal"><span style="color: black;" lang="NL">Microsoft |
|
Visual C++ Ver. 6 and Microsoft .Net compiler Version </span>7.1<span |
|
style="color: black;" lang="NL"><o:p></o:p></span></p> |
|
</td> | </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> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="43" |
<td style="padding: 0.75pt;"> <font size="3">MacOS version 10.3 |
width="211"> <font size="3">MacOS version 10.2 and higher</font></td> |
and higher</font></td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="43" |
<td style="padding: 0.75pt;"> <font size="3">gcc 4.01</font></td> |
width="289"> <font size="3">gcc 3.3</font></td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big>HP OpenVMS Alpha<br> |
<td style="vertical-align: top;"><big><font color="RED"><span |
</big></td> |
style="color: rgb(0, 0, 0);">Solaris 8</span></font></big></td> |
<td style="vertical-align: top;"> <big><font |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
style="color: rgb(0, 0, 0);" color="RED">HP C++ V6.5-042 for OpenVMS |
CC compiler V 5.8. Note that the latest thread patch (108993) may be |
Alpha and above</font></big> </td> |
required. (see Pegasus bug 4632)</big><br> |
|
</td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);"> HP OpenVMS IA64</font></big></td> |
|
<td style="vertical-align: top;"><span class="norm"></span><big><font | <td style="vertical-align: top;"><span class="norm"></span><big><font |
style="color: rgb(0, 0, 0);">HP C++ V7.1-011 on OpenVMS IA64 and above</font></big> |
color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9</span></font></big></td> |
|
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
|
WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><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> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual |
|
C++ Ver. 6 and Microsoft .Net compiler version. Works on VC |
|
.NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being regularly |
|
tested.</font></td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><span class="norm"></span><big><font><font |
<td style="padding: 0.75pt;"> <font size="3">Windows 2003</font> |
color="RED"><span style="color: rgb(0, 0, 0);">Solaris 8<br> |
<p></p> |
* See below for additional info<br> |
|
</span> </font></font></big></td> |
|
<td style="vertical-align: top;"><big>GNU 2.95.3</big><br> |
|
</td> | </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> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<br> |
<p><b>Platform patches</b> |
<span style="font-weight: bold;">Solaris:</span> Solaris testing |
|
began late in the 2.5 release cycle, thus has not been thoroughly |
|
tested. In order for Pegasus 2.5 to function properly on that |
|
platform, changes documented in OpenPegasus Bugzilla 4179 must be |
|
applied. <span class="norm"><font color="RED"> |
|
</font></span> |
|
<h2><small><b><b>Platform patches</b></b></small></h2> |
|
<font style="color: rgb(0, 0, 0);">The following is a list of platform |
|
patches Pegasus requires.<br> |
|
<br> |
|
</font> |
|
<div style="margin-left: 40px;"><font style="color: rgb(0, 0, 0);">RHAS |
|
2.1 needs the update to fix Red Hat Bugzilla 98815.</font><br> |
|
</div> |
|
<br> |
|
<p>Further information regarding Pegasus support on IBM platforms can |
|
be |
|
found at: <a |
|
href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span |
|
style="text-decoration: underline; color: rgb(51, 51, 255);">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</span></a> |
|
</p> | </p> |
<p> <br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font |
Further information regarding Pegasus support on HP platforms can be |
style="color: rgb(0, 0, 0);">The following is a list known of platform |
found at: |
patches Pegasus requires.</font></p> |
<a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> |
<div style="margin-left: 40px;"> |
<p><o:p><br> |
|
</o:p></p> |
|
<h2><a name="Conformance with DMTF Specifications">Conformance with |
|
DMTF Specifications</a></h2> |
|
<p>It is a major goal |
|
of the OpenPegasus project to both drive and utilize the DMTF CIM/WBEM |
|
specifications. However, today there are a number of known |
|
differences. |
|
As of this release, some of the differences include the following:</p> |
|
<ol> | <ol> |
<li><b>Provider Registration</b> - Pegasus supports registration |
|
through a set of Pegasus Provider registration classes rather than |
|
support the DMTF defined Provider Qualifier. Pegasus will not support |
|
this qualifier in the future. See the readme for more information on |
|
provider registration.</li> |
|
<li> <b>Indications </b>-Today Pegasus supports process |
|
indications but does not |
|
include any specific support for lifecycle indications.</li> |
|
<li> |
|
<p class="MsoNormal"><span style="color: black;"> </span><font |
|
style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers |
|
option on Instance Operations</font><span style="color: black;"><b> </b> |
|
- |
|
The DMTF specifications are unclear regarding the inclusion of |
|
qualifiers on |
|
CIM instances. Some CIM Client implementations expect instances |
|
returned |
|
from the CIM Server to include the qualifiers defined in the class |
|
definition (such as KEY qualifiers on properties). </span> Pegasus |
|
today expects the provider to complete the qualifiers on instances in |
|
accordance with the specification and generally the interpretation is |
|
that Pegasus applies class level qualifiers when the includeInstance |
|
parameter is supplied on instance operations. However, Pegasus |
|
today is inconsistent in the return of qualifiers so that the user |
|
should NOT depend on Pegasus accurately honoring the includeQualifier |
|
parameter for instance operations. In the future it is expected |
|
that Pegasus will deprecate the use of qualifiers on instance |
|
operations completely.</p> |
|
</li> |
|
<li><b>LocalOnly option on instance |
|
Operations </b>- With the 1.1 version of Specification for CIM |
|
Operations over HTTP, the definition of the LocalOnly parameter for the |
|
GetInstance and EnumerateInstances operations was modified. This change |
|
was incorrect, resulted in reduced functionality and introduced a |
|
number of backward compatibility issues. As a result of issues |
|
introduced by this change, we strongly recommend that CIM Clients set |
|
LocalOnly = false and do not rely on the use of this parameter to |
|
filter the set of set of properties returned.</li> |
|
<li> | <li> |
<p class="MsoNormal"> <b>CIM MOF compiler function for |
<p style="margin-top: 0pt; margin-bottom: 0pt;"> <font |
instance aliasing</b> - The Pegasus MOF compiler does not today support |
style="color: rgb(0, 0, 0);">RHAS |
this function. This function is planned for a future version.</p> |
2.1 needs the update to fix Red Hat Bugzilla 98815.</font></p> |
</li> | </li> |
<li> | <li> |
<p class="MsoNormal"><b> MultiRequest Oprations</b> - Pegasus |
<p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4 |
does not support the DMTF defined MultiRequest Operation option.</p> |
multithreading bug in |
|
getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is |
|
fixed in |
|
RHEL 4.5</p> |
</li> | </li> |
<li> | <li> |
<p class="MsoNormal"><b>MOFCompiler namespace pragma</b> - The |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE |
Pegasus compiler does not support the namespace pragma.</p> |
Linux multiple versions - |
</li> |
multithreaded client intermittently fails connecting to IPv6 (Pegasus |
</ol> |
Bugzilla |
<h2><a name="Changes in This Release">Changes in This Release</a></h2> |
6586) (Red Hat bug 248052)<br> |
<p>The development and release of each version of Pegasus is defined |
|
and |
|
controlled through Pegasus PEP documents. PEP 180 is the |
|
controlling document |
|
this release and lists the original set of changes proposed and the |
|
status of |
|
each of those changes. Note that not all of the originally defined |
|
functionality was completed for this release.</p> |
|
<p>In general, the areas of development for this release were:</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Addition of CQL |
|
stage 1 support<br> |
|
</p> | </p> |
</li> | </li> |
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Refactoring of |
|
Object Normalizer function to improve performance. </p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Out of Process |
|
Provider user level request.<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Embedded Object |
|
support. </p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Command Line |
|
Utilities<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">CIMDateTime |
|
enhancements<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of |
|
AutoPtr enhancements. </p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Certificate |
|
management and user-based certificate authentication<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of HTTP |
|
chunking. <font style="color: rgb(51, 51, 255);" color="RED">Pegasus |
|
now supports HTTP V1.1 transfer encoding otherwise known as chunking .<a |
|
href="http://www.openpegasus.org/pp/uploads/40/5097/PEP140_ChunkedEncoding_4.3.html"> |
|
PEP 140</a> describes the implementation details.</font></p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;">Client side performance |
|
statistics</li> |
|
<li class="MsoNormal" style="color: black;">Syslog Indication handler.</li> |
|
<li class="MsoNormal" style="color: black;">Email Indication handler.</li> |
|
<li class="MsoNormal" style="color: black;">Port to OpenVMS.</li> |
|
</ol> | </ol> |
<p class="MsoNormal" style="margin-left: 0.5in;"> </p> |
</div> |
The complete set of <span class="SpellE">PEPs</span> defined for |
<p>Further information regarding Pegasus support on IBM platforms can |
this release is defined in PEP 180. |
be |
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus defects<br> |
found at: <a |
</a></span></h2> |
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 | <p>The Pegasus bugzilla database documents any defects found in Pegasus |
and is available through the following link: <a | and is available through the following link: <a |
href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla | href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla |
database</a>. <br> |
database</a>. |
</p> |
Effective with the start of the Pegasus 2.6 work, all changes to the |
<br> |
CVS tree are documented through bugs. Bugs reports are filed not |
|
only for bugs and |
|
their corresponding fixes but also as part of the process of committing |
|
new code |
|
representing the work on PEPs done for Pegasus 2.6 and all subsequent |
|
versions. Therefore, a search of |
|
the Open Pegasus bugzilla base for bugs with the tag for a particular |
|
version |
|
(ex. |
|
<a |
|
href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED">2.6.0_APPROVED</a>, |
|
<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> |
|
- Changes for this release (bugs Tagged |
|
2.11.0_APPROVED). The link is <a |
|
href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.11.0_APPROVED"> |
|
Pegasus 2.11.0_APPROVED bug list.</a></p> |
<h2><a | <h2><a |
name="Pegasus Release Control and Version Definition Documentation">Pegasus |
name="Pegasus Release Control and Version Definition Documentation">Release |
Release Control and Version Definition Documentation</a></h2> |
Control and Version Definition Documentation</a></h2> |
<p>The Pegasus project is controlled largely through a set of documents |
<p>The Pegasus project is controlled largely through the CVS repository |
(PEPs) that serve as the definition and review mechanism for new and |
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 | modified Pegasus functionality and for the definition and documentation |
of releases.</p> | of releases.</p> |
<p>Specifically the following PEPs define the characteristics of this |
The following documentation defines the characteristics of this Pegasus |
Pegasus release.</p> |
release. The documents are available in the OpenPegasus CVS |
<ol> |
repository. |
<li><a |
<br> |
href="http://www.openpegasus.org/pp/protected/upreviews/20/1682/PEP209_ExternalInterface2.5.htm">PEP |
<ul> |
209</a> - OpenPegaus 2.5 External Interfaces (as of this document |
<li><b> OpenPegasus Release Definition/Status -No PEP (See Wiki |
verion of PEP 230, PEP 209 is listed as draft status)<br> |
Section <a |
</li> |
href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_11_x">OpenPegasus |
<li><a |
2.11.x Release Status</a>) - <span style="font-weight: normal;">A |
href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502">PEP |
section in the Pegasus wiki is used |
200</a> - OpenPegaus 2.5 Build and Configuration |
|
Option for Selected |
|
Platforms</li> |
|
<li>PEP 230 - Pegasus 2.5 Release Notes (This document)</li> |
|
<li><a |
|
href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8503">PEP |
|
227</a> - Pegasus 2.5 Runtime Packaging Definition<br> |
|
</li> |
|
<li><a |
|
href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8466">PEP |
|
210</a> - OpenPegasus 2.5 SDK Packaging Definition</li> |
|
<li>PEP 235 - Pegasus readme.txt for 2.5 (also in the Pegasus |
|
source |
|
tree root directory).</li> |
|
<li><a |
|
href="http://www.openpegasus.org/pp/protected/revdoc.tpl?CALLER=revdocuments.tpl&grid=1411">PEP |
|
180</a> - OpenPegasus Release Definition - This PEP is used |
|
throughout the development of this version as the control point for | throughout the development of this version as the control point for |
functionality that will go into the release and points to all of the | functionality that will go into the release and points to all of the |
PEPs that represent the Pegasus 2.5 functionality changes. (as of |
PEPs that represent the Pegasus functionality changes for this |
this document verion of PEP 230, PEP 180 is listed as draft status)</li> |
version of Pegasus</span>. </b></li> |
</ol> |
<b> </b><span style="font-weight: bold;"></span><b>OpenPegasus |
<h2><a name="General Documentation">General Documentation</a></h2> |
Build and Configuration |
<p>The following documentation is available for the this Pegasus |
Options for Selected |
release:</p> |
Platforms - <span style="font-weight: normal;">In previous |
|
versions of Pegasus this information was released as a Pegasus |
|
PEP. Starting with Pegasus 2.9.0 the information is located in the |
|
OpenPegasus CVS repository as <big style="font-weight: bold;"> <span |
|
style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</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 </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 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> |
|
</b></li> |
|
<b> </b> <b> <li> Pegasus Runtime Packaging Definition |
|
- <span style="font-weight: normal;">Defines the recommended set |
|
of files for inclusion in this OpenPegasus |
|
release. Starting with Pegasus release 2.11.0, this 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> </li> |
|
</b> <b> <li>Pegasus Release Notes - <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"> | <ul style="margin-top: 0in;" type="disc"> |
<li class="MsoNormal" style="color: black;"><b>Utilities</b> - A |
<b> <li class="MsoNormal" style="color: black;"><b>Utilities</b> - </li> |
combination of help generally available with the -h option for each |
</b>A |
command and HTML documentation for most of the tools.<o:p></o:p></li> |
combination of help generally available with the --help option for each |
<li class="MsoNormal" style="color: black;"><b>API and usage |
command and HTML documentation for most of the tools.<o:p></o:p> <b> <li |
documentation</b> - See the header files and the HTML API |
class="MsoNormal" style="color: black;"><b>API and usage |
|
documentation</b> - </li> |
|
</b>See the header files and the HTML API |
documentation that is on the web site. The best API usage documentation | 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 | is the existing utilities and test programs and the examples in the API |
documentation. In particular the Common/tests unit tests contain | documentation. In particular the Common/tests unit tests contain |
extensive examples of the use of the Common APIs.</li> |
extensive examples of the use of the Common APIs. <b> <li |
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
class="MsoNormal" style="color: black;"><b>Building and Debugging |
Providers </b>- Readme.html in the Pegasus Root Directory, API |
Providers </b>- </li> |
|
</b>Readme.html in the Pegasus source tree Root Directory, API |
documentation, and documentation from the Pegasus Technical Workshop | documentation, and documentation from the Pegasus Technical Workshop |
which is available on the Pegasus web site.</li> |
which is available on the Pegasus web site. <b> <li class="MsoNormal" |
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
style="color: black;"><b>Building and Debugging |
Clients</b> - API documentation and the documentation on the Pegasus |
Clients</b> - </li> |
Technical Workshop which is available on the Pegasus web site.</li> |
</b>API documentation and the documentation on the Pegasus |
<li class="MsoNormal" style="color: black;"><b>Compiler operation and |
Technical Workshop which is available on the Pegasus web site. <b> <li |
commands</b> - compiler help (cimmofl -h)</li> |
class="MsoNormal" style="color: black;"><b>PEPs</b> - </li> |
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - The |
</b>The |
features of Pegasus that have been installed in this and the previous | features of Pegasus that have been installed in this and the previous |
few versions are defined by Pegasus PEPs that are available on the | few versions are defined by Pegasus PEPs that are available on the |
OpenPegasus web site. While these are the original design | OpenPegasus web site. While these are the original design |
documents largely and use in the process of defining and approving the | documents largely and use in the process of defining and approving the |
overall characteristics of new functionality, they serve as a guide to | overall characteristics of new functionality, they serve as a guide to |
the design and implementation of these features.</li> |
the design and implementation of these features. |
</ul> | </ul> |
|
<hr>Licensed to The Open Group (TOG) under one or more contributor |
<p class="MsoNormal" style="margin-left: 0.5in;"><span |
license |
style="color: black;"> <o:p></o:p></span></p> |
agreements. Refer to the OpenPegasusNOTICE.txt file distributed with |
<div class="MsoNormal" style="text-align: center;" align="center"><span |
this work for additional information regarding copyright ownership. |
style="color: black;"> |
Each contributor licenses this file to you under the OpenPegasus Open |
<hr align="center" color="#009900" noshade="noshade" size="2" |
Source License; you may not use this file except in compliance with the |
width="100%"></span></div> |
License. |
<p><i><font size="2">Copyright (c) 2005 EMC Corporation; |
<p>Permission is hereby granted, free of charge, to any person |
Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open Group; |
obtaining a |
VERITAS Software Corporation</font><br> |
copy of this software and associated documentation files (the |
<br> |
"Software"), |
</i><i><span style="font-size: 7.5pt;">Permission is hereby granted, |
to deal in the Software without restriction, including without |
free of |
limitation |
charge, to any person obtaining a copy of this software and |
the rights to use, copy, modify, merge, publish, distribute, |
associated |
sublicense, |
documentation files (the "Software"), to deal in the Software without |
and/or sell copies of the Software, and to permit persons to whom the |
restriction, including without limitation the rights to use, copy, |
Software is furnished to do so, subject to the following conditions:</p> |
modify, |
<p>The above copyright notice and this permission notice shall be |
merge, publish, distribute, sublicense, and/or sell copies of the |
included |
Software, and |
in all copies or substantial portions of the Software.</p> |
to permit persons to whom the Software is furnished to do so, subject |
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, |
to the |
EXPRESS |
following conditions:</span><br> |
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF |
</i><i><span style="font-size: 10pt;"><br> |
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. |
</span></i><i><span style="font-size: 7.5pt;">THE ABOVE COPYRIGHT |
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY |
NOTICE AND THIS |
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, |
PERMISSION NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL |
|
PORTIONS OF |
|
THE SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT |
|
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO |
|
THE |
|
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND |
|
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE |
|
LIABLE |
|
FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF |
|
CONTRACT, |
|
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE | TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE |
SOFTWARE OR |
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p> |
THE USE OR OTHER DEALINGS IN THE SOFTWARE.</span></i></p> |
|
<p> </p> |
|
</div> | </div> |
</body> | </body> |
</html> | </html> |