version 1.7, 2006/03/28 19:58:13
|
version 1.13, 2008/07/30 16:39:55
|
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
<html xmlns:v="urn:schemas-microsoft-com:vml"><head> |
<html xmlns:v="urn:schemas-microsoft-com:vml"> |
|
<head> |
|
|
<style> | <style> |
st1\:*{behavior:url(#ieooui) } | st1\:*{behavior:url(#ieooui) } |
</style> | </style> |
|
|
font-size:10.0pt; | font-size:10.0pt; |
font-family:"Times New Roman"} | font-family:"Times New Roman"} |
</style> | </style> |
<link rel="Edit-Time-Data" href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso"><title>PEP</title> |
<link rel="Edit-Time-Data" |
|
href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso"> |
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype> |
<title>PEP</title> |
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml> |
<o:smarttagtype |
|
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype> |
|
<o:smarttagtype |
|
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype |
|
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml> |
<o:DocumentProperties> | <o:DocumentProperties> |
<o:Author>IBM_User</o:Author> | <o:Author>IBM_User</o:Author> |
<o:LastAuthor> </o:LastAuthor> | <o:LastAuthor> </o:LastAuthor> |
|
|
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> | <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> |
</w:WordDocument> | </w:WordDocument> |
</xml><![endif]--> | </xml><![endif]--> |
|
</head> |
|
<body lang="EN-US" link="blue" vlink="blue"> |
|
<div class="Section1"> |
|
<div class="MsoNormal" style="text-align: center;" align="center"><span |
|
style="color: black;"> |
|
<hr align="center" color="#009900" noshade="noshade" size="2" |
|
width="100%"></span></div> |
|
<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;" |
|
align="center"><b><span style="font-size: 13.5pt; color: black;">Pegasus |
|
Enhancement Proposal (PEP)<o:p></o:p></span></b></p> |
| |
|
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"> |
| |
|
<br> |
| |
|
<b>PEP #:</b> 332<br> |
| |
<script language="javascript" src="ReleaseNotes_files/js_002.js"></script> |
|
|
|
<script language="javascript" src="ReleaseNotes_files/js.js"></script></head><body lang="EN-US" link="blue" vlink="blue"> |
|
<div class="Section1"> |
|
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
|
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
|
<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;" align="center"><b><span style="font-size: 13.5pt; color: black;">Pegasus |
|
Enhancement Proposal (PEP)<o:p></o:p></span></b></p> |
|
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"><br> |
|
<br> |
|
<b>PEP #:</b> 249<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.1</p> |
Notes for OpenPegasus 2.8.0</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version: </b>1.0</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> <st1:date year="2004" day="23" month="3">1 March 2006</st1:date></p> |
|
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 21 June 2008</p> |
|
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Karl Schopmeyer<br> | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>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" cellpadding="0" cellspacing="1" width="100%"> |
|
|
<table class="MsoNormalTable" style="width: 100%;" border="1" cellpadding="0" cellspacing="1" width="100%" height="155" id="table1"> |
|
|
<tbody> | <tbody> |
|
|
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"> |
|
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"> |
|
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"> |
|
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"> |
|
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span 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 style="font-family: Arial; color: black;"><font size="2"> 1.0</font><o:p></o:p></span></p> | <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> |
|
|
</td> | </td> |
<td style="padding: 0.75pt;" align="left"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><o:p><font size="2"> 1 March |
<td style="padding: 0.75pt;" align="left" height="22"> |
2006</font></o:p></span></p> |
|
|
<p class="MsoNormal" style="text-align: center;" align="center"> |
|
<font size="2"><span style="font-family: Arial">21 June 2008</span></font></p> |
|
|
</td> | </td> |
<td style="padding: 0.75pt;" align="left"> |
|
|
<td style="padding: 0.75pt;" align="left" height="22"> |
|
|
<p class="MsoNormal" style="text-align: center;" align="center"> | <p class="MsoNormal" style="text-align: center;" align="center"> |
<span style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> | <span style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> |
|
|
</td> | </td> |
<td style="padding: 0.75pt;"> |
|
|
<td style="padding: 0.75pt;" height="22"> |
|
|
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial | <p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial |
Submission</font><o:p><font size="2"> | Submission</font><o:p><font size="2"> |
</font></o:p></span></p> | </font></o:p></span></p> |
|
|
</td> | </td> |
|
|
</tr> | </tr> |
|
|
<tr> | <tr> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.1</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">2 March 2006</font></td> |
<td style="padding: 0.75pt;" align="center" height="21">1.1</td> |
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">Karl Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial" size="2">Fix editorial errors</font></td> |
<td style="padding: 0.75pt;" align="center" height="21">6 July 2008</td> |
|
|
|
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td> |
|
|
|
<td style="padding: 0.75pt;" height="21">Incorporate initial comments</td> |
|
|
</tr> | </tr> |
|
|
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.2</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">20 March 2006</font></td> |
<td style="padding: 0.75pt;" align="center" height="21">1.2</td> |
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">Karl Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial" size="2">Incorporate comments from |
<td style="padding: 0.75pt;" align="center" height="21">11 July 2008</td> |
Review week of 12 March 2006</font></td> |
|
</tr> |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td> |
<tr> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.3</font></td> |
<td style="padding: 0.75pt;" height="21">Incorporate All Comments to date |
<td style="padding: 0.75pt;" align="center"><font face="Arial">22 March |
(See discussion for list of changes)</td> |
2006</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
|
Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial">Incorporate comments form |
|
Review 21 March 06 and bring into line with Feature status page</font></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.4</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">28 March |
|
2006</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
|
Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial">Remove all statements |
|
concerning status and point to the Feature Status Page.</font></td> |
|
</tr> | </tr> |
|
|
<tr> | <tr> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.5</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">28 March |
<td style="padding: 0.75pt;" align="center" height="21">1.3</td> |
2006</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
<td style="padding: 0.75pt;" align="center" height="21">23 July 2008</td> |
Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial">Remove references to |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td> |
status "experimental" for certain features</font></td> |
|
|
<td style="padding: 0.75pt;" height="21">Add bug 7501 to compatibility |
|
issues table. Remove temp change list section</td> |
|
|
</tr> | </tr> |
|
|
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.6</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">28 March |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
2006</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial">Typos</font></td> |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
|
|
|
<td style="padding: 0.75pt;" height="23"> </td> |
|
|
</tr> | </tr> |
|
|
|
|
</tbody> | </tbody> |
</table> | </table> |
<p><o:p> </o:p></p> |
|
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
<div class="MsoNormal" style="text-align: center;" align="center"> |
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
<span |
<p><b>Abstract:</b> This document defines the release notes for the 2.5.1 |
style="color: black;"> |
version of the Pegasus CIM Server. <span class="norm1"><span style="font-size: 9pt;"><a href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35" target="_self"><br> |
<hr align="center" color="#009900" noshade="noshade" size="2" |
</a></span></span></p> |
width="100%"></span></div> |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
<p><b>Abstract:</b> This document defines the release notes for the |
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
2.8.0 release of the OpenPegasus CIM Server. The purpose of this PEP is |
<h2 style="margin-bottom: 1px;"><b><o:p><font size="4"> Contents<br> |
to summarize the characteristics of this release, point to other |
</font></o:p></b></h2> |
documentation that defines the release in more detail, and provide |
|
additional information about this release that is not available in the |
|
other Pegasus documentation. </p> |
|
<div class="MsoNormal" style="text-align: center;" align="center"> |
|
<span |
|
style="color: black;"> |
|
<hr align="center" color="#009900" noshade="noshade" size="2" |
|
width="100%"></span></div> |
|
<h2 style="margin-bottom: 1px;"><b><o:p><font size="5"> Contents</font></o:p></b></h2> |
<ol> | <ol> |
<li><a href="#Availability_of_this_Release_">Availability of this Release</a></li> |
<li><a href="#Availability_of_this_Release_">Availability of this |
<li><a href="#Functionality_of_This_Release">Functionality of |
Release</a></li> |
This Release</a></li> |
<li><a href="#Functionality_of_This_Release">OpenPegasus |
|
Functionality of This Release</a></li> |
|
<li><a href="#Compatibility_Considerations_">Compatibility Considerations</a></li> |
<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship | <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 |
<li><a href="#PEGASUS%20Bugs">PEGASUS |
href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus |
Bugs</a></li> |
|
<li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">Pegasus |
|
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> |
|
|
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 href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a></li> |
site at <a |
<li>OpenPegasus 2.5.1 binaries are available for Red Hat Enterprise |
href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li> |
Linux 3.0 and 4.2 and SUSE LINUX Enterprise Server 9.0. A Source RPM is |
<li><b>OpenPegasus source RPMs</b> on the OpenPegasus web site.. 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><b>The Pegasus CVS repository</b>. The CVS tags representing this |
<li>The Pegasus CVS. The CVS tags representing this release and |
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 href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus |
defined on the OpenPegasus CVS repository web page (see the <a |
CVS page</a> for information) using the tags defined on the <a href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release |
href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus |
|
CVS page</a> for information) using the tags defined on the <a |
|
href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release |
snapshots page</a>.</li> | snapshots page</a>.</li> |
</ul> | </ul> |
<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 |
<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 |
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.</p></div> |
tree.</p> |
|
</div> |
<div class="Section1"> | <div class="Section1"> |
<h2><span style="color: black;">Functionality of This Release</span></h2> |
<h2><span style="color: black;">OpenPegasus Functionality for This Release</span></h2> |
|
|
Pegasus overall status by release is defined by a | Pegasus overall status by release is defined by a |
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a> | <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a> |
that is available on the OpenPegasus web site . That |
that is available on the OpenPegasus web site . That web page shows the |
web page shows the Pegasus users and developers |
Pegasus users and developers the status of the various features found in Pegasus |
the status of the various features found in Pegasus using a simple color coded |
using a simple color coded key (white, red, yellow, green) and a description of |
key (white, red, yellow, green). Pegasus 2.5.1 is a minor release, extending Pegasus 2.5.0 in selected |
each feature.<p>Pegasus 2.8.0 |
areas primarily for bug fixes. However, there were some signification |
is a major release, extending the previous Pegasus release in selected |
changes in the feature status for selected functions in 2.5.1 (moving selected |
areas as described in the Pegasus PEP defining this release |
functions closer to production-capable status).<p>The following paragraphs list the functionality in this release. In many cases these features and interfaces |
. </p> |
are conditionally compiled with special environment variables. <span style="color: rgb(51, 102, 255);"><span style="text-decoration: underline;"> |
|
<a style="color: blue; text-decoration: underline;" href="http://www.openpegasus.org/pp/uploads/40/10083/PEP237_RecommendedReleaseOptions.htm">PEP 237</a></span><a href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502" style="color: blue; text-decoration: underline;"> </a></span> |
<p>The major areas of development for this release were as follows. For |
provides more detailed information on how to enable |
more information access the PEP for each change defined:</p> |
functionality that is conditionally compiled in this release.</p> |
|
<p><font color="#ff0000"><b>NOTE: </b>For current information and history on the status of each feature, |
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font size="4"> |
please access the</font> |
Table of Major Changes for this Release</font></p> |
<a href="http://www.openpegasus.org/page.tpl?ggid=799" style="color: blue; text-decoration: underline;"> |
|
OpenPegasus Feature Status WEB Page</a>. <font color="#ff0000">Please see |
|
the Feature status page for the quality/status of each feature because not all |
<TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666 |
of the features listed below are production ready.</font></p> |
borderColorLight=#CCCCCC border=1 width="82%"> |
<h3><b>CIM Server Functionality</b></h3> |
<TBODY> |
<blockquote> |
<TR align="center"> |
<h4><b>CIM Operations over HTTP support</b></h4> |
<TH bgColor=#00FFFF>PEP #</TH> |
<ol> |
<TH bgColor=#00FFFF>Description of Change</TH> |
<li>Class Operations (<span class="SpellE">getClass</span>, <span class="SpellE">deleteClass</span>, <span class="SpellE">modifyClass</span>, |
<TH bgColor=#00FFFF width="128">Posted PEP<br>Version</TH> |
<span class="SpellE">enumerateClass</span>, <span class="SpellE">enumerateClassNames</span>)</li> |
</TR> |
<li>Qualifier Operations (getQualifier, setQualifier, |
<TR align="center"> |
deleteQualifier) </li> |
<TD width="7%">307</TD> |
<li>Instance Operations (<span class="SpellE">getInstance</span>, <span class="SpellE">deleteInstance</span>, <span class="SpellE">modifyInstance</span>, |
<TD align="left" width="75%">Memory Resident Repository</TD> |
<span class="SpellE">enumerateInstance</span>, <span class="SpellE">enumerateInstanceNames</span>, <span class="SpellE">getProperty</span>, |
<TD width="128"> |
<span class="SpellE">setProperty</span>)</li> |
<a href="https://www.openpegasus.org/pp/uploads/40/16769/PEP307_DisklessRepository.htm"> |
<li>Association Operations (references, <span class="SpellE">referencenames</span>, |
1.3.1</a></TD> |
<span class="SpellE">associators</span>, <span class="SpellE">associatornames)</span></li> |
</TR> |
<li>Methods Operations (invokeMethod)</li> |
<tr> |
<li>Query operation - Support for ExecQuery was added in 2.4 with |
<TD width="7%"> |
WQL as query language and is defined in PEP 119. This feature is |
<p align="center">311</TD> |
considered at alpha quality because it has only been contributor |
<TD align="left" width="75%">WS-Management Support in CIM Server</TD> |
tested. Additional tests have been added in 2.5 for ExecQuery. Pegasus |
<TD width="128"> |
today does not support the ExecuteQuery operation defined as the Query |
<p align="center"> |
operation for CQL.<br> |
<a href="http://www.openpegasus.org/pp/uploads/40/16744/PEP311_WSManSupportInCIMServer_1_4.htm" style="color: blue; text-decoration: underline; text-underline: single"> |
</li> |
1.4</a></TD> |
</ol> |
</tr> |
</blockquote> |
<TR align="center"> |
</div> |
<TD width="7%">313</TD> |
<blockquote> |
<TD align="left" width="75%">Pluggable Provider Managers - Enhancement</TD> |
<h4><b>Indication Processing</b></h4> |
<TD width="128"> |
<ol> |
<a href="http://www.openpegasus.org/pp/uploads/40/16698/PEP_313_PluggableProviderManagers.html"> |
<li>Process indications - Process indications are operational in |
1.2</a></TD> |
the |
</TR> |
Server. This includes support |
<TR align="center"> |
for subscriptions, filters, and indication handlers, the provider API |
<TD width="7%">315</TD> |
for |
<TD align="left" width="75%">Tracing in OpenPegasus - Enhancement</TD> |
indications and the CIMXML indication handler.</li> |
<TD width="128"> |
<li>Lifecycle indications - With the support for embedded objects, |
<a href="https://www.openpegasus.org/pp/uploads/40/16768/PEP_315_-Tracing_in_OpenPegasus.htm"> |
lifecycle indications (ie. those |
1.0</a></TD> |
classes of indications derived from CIM_ClassIndication and |
</TR> |
CIM_InstIndication) can now be created. Pegasus 2.5 provides some |
<TR align="center"> |
enablement for the generation of lifecycle indications. For more |
<TD width="7%">319</TD> |
details, refer to |
<TD align="left" width="75%">Profile Registration Profile Support</TD> |
<src/Unsupported/LifecycleIndicationProvider/readme.LifecycleIndications.htm>.</li> |
<TD width="128"> |
</ol> |
<a href="http://www.openpegasus.org/pp/uploads/40/16888/PEP319_DMTF_PRP_1_3.htm"> |
<h4><b>Query Language</b></h4> |
1.3</a></TD> |
<p>Pegasus includes the WQL query language which is implemented and |
</TR> |
used for filters and in version 2.4 for execQuery. <br> |
<TR align="center"> |
|
<TD width="7%">322</TD> |
|
<TD align="left" width="75%">Track Generated Indications Data</TD> |
|
<TD width="128"> |
|
<a href="https://www.openpegasus.org/pp/uploads/40/16767/PEP322_IndStatisticData.htm"> |
|
1.2</a></TD> |
|
</TR> |
|
<TR align="center"> |
|
<TD width="7%">323</TD> |
|
<TD align="left" width="75%">DMTf Indication Profile Implementation, Stage |
|
1 (DMTF DSP 1054)</TD> |
|
<TD width="128"> |
|
<a href="https://www.openpegasus.org/pp/uploads/40/16770/PEP323_DMTF_Indication_Profile_stage_1.htm"> |
|
1.0</a></TD> |
|
</TR> |
|
<TR align="center"> |
|
<TD width="7%">322</TD> |
|
<TD align="left" width="75%">Track Generated Indications Data</TD> |
|
<TD width="128"> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/16873/PEP322_IndStatisticData.htm"> |
|
1.2</a></TD> |
|
</TR> |
|
</TBODY> |
|
</TABLE> |
|
</html> |
|
<p>The status of several components of Pegasus functionality change status |
|
between Pegasus versions. <span class="norm"><a name="comtag_116">Features that |
|
have changed status can be identified by a change in color from the previous |
|
release to this release</a></span> on the |
|
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>.</p> |
|
|
|
<p>Finally, a significant number of internal changes and corrections were made |
|
under the control of the Pegasus bugzilla bug system. See the bug section below |
|
for more information.</p> |
|
|
|
<h3><font color="#000000">Information on IPv6 Support (PEP 291)</font></h3> |
|
<p><b>NOTE:</b> This functionality was incorporated in OpenPegasus 2.7.0 but it |
|
was felt that the information below was worth repeating in the 2.8.0 Release |
|
Notes</p> |
|
<p style="color: rgb(153, 51, 153);"><font color="#000000">IPv6 is short for "Internet |
|
Protocol |
|
Version 6". IPv6 is the "next generation" protocol designed by the IETF |
|
to replace the current version Internet Protocol, IP Version 4 |
|
("IPv4"). IPv6 Support for OpenPegasus is documented in </font> <a |
|
href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html"> |
|
<font color="#3333FF">PEP |
|
291</font></a><font color="#000000">.</font></p> |
|
<p>The IPv6 support in OpenPegasus is |
|
controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this |
|
variable is "true"; setting this to |
|
'false' before building OpenPegasus will disable the IPv6 support.<br> |
</p> | </p> |
<p>CQL Stage 1 has been added for Pegasus 2.5. PEPs 138, 193, 205 |
<p>The following subsections provide |
combine to describe the CQL functionality supported.</p> |
some information on IPv6 support for the Linux and Windows platforms. |
<h4>Object Normalization</h4> |
Note that in the 2.6.1 release there is no automatic run-time detection |
The Object Normalizer is an entity introduced in Pegasus 2.4 that |
of IPv6 support on a platform by OpenPegasus. If you build with |
ensures |
PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you will |
objects delivered from providers are complete and accurate. Two major |
get a build failure (missing header files), a run-time bind() failure, |
issues were identified with the initial implementation: 1) the Object |
or possibly some other failure. This applies to both the CIM Server and |
Normalizer droped instances it considered bad, and 2) the Object |
Listener components. For more information on IPv6 support for your |
Normalizer code slowed performance. These issues are now addressed by |
specific platform, refer to the documentation for that platform.<br> |
moving the Object Normalizer from the Dispatcher to the Response |
</p> |
Handler (or equivalent) and optimizing the existing implementation. The |
<p>All OpenPegasus externals that |
move allows errors to be reported to the provider at the point of |
support either a hostname or an IP address as input have been updated |
delivery and ensures that only a single copy is made to preserve the |
to allow an IPv6 address to be specified. If the required input is just |
CIMOM/provider boundary.<br> |
an IP address (eg. no optional or required port number), then the IPv6 |
<h4>Embedded Object Support</h4> |
address must be specified without brackets. For example, the |
Pegasus 2.5 provides embedded object support. The proposed solution |
OpenPegasus osinfo client (which returns information about the OS |
is restricted to the following:<ul> |
running on a host system) takes separate host and port options. In this |
<li>The only representation for embedded objects supported by this |
case a host with an IPv6-configured network interface would be |
PEP is CIM-XML (i.e. id does not support MOF encoded objects). </li> |
specified as:<br> |
<li>CIMObject is implemented as a new CIMValue type. This type will be used |
</p> |
internally to represent embedded objects. When externalized (via |
<div style="margin-left: 40px; color: rgb(153, 51, 153);"><font color="#000000">osinfo -h |
CIM-XML) these objects will be converted to strings representing valid |
3ffe:1:2:1 -p 5988</font></div> |
INSTANCE or CLASS elements, in accordance with the CIM Infrastructure |
<p>But the cimcli command, which |
Specification. Embedded instances will also carry the |
takes |
EmbeddedObject attribute with |
an optional "location" option including an optional port number, |
the value "object", as specified by CR Interop-00217.001. |
requires the IPv6 address to be delimited with brackets, for example:<br> |
</li> |
|
</ul> |
|
<h3>Pegasus Repositories<br> |
|
</h3> |
|
<p class="MsoNormal"> </p> |
|
</blockquote> |
|
<div class="Section1"> |
|
<blockquote> |
|
<h4><b>Schema Repository</b></h4> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">By default, Pegasus uses an XML-based |
|
schema repository. A binary encoding option is also available for the repository.<span style="font-family: "times new roman";"><br> |
|
</span></p> |
|
<div style="margin-left: 40px;"> |
|
<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></div> |
|
<p>Further information on the use of the binary repository is in the |
|
readme.binaryrepository file in the Pegasus source root directory.</p> |
|
<h4><b>Instance Repository</b></h4> |
|
<p><font style="color: rgb(0, 0, 0);">The |
|
Pegasus schema repository may also be configured to hold instance |
|
data. Although instances may be place in the |
|
repository |
|
it was not designed as a |
|
high volume data store</font><span style="color: rgb(0, 0, 0);">.</span></p> |
|
<h4><b><b>Compressed Repository Feature</b></b></h4> |
|
<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). Note |
|
that the tests for this feature are in the test suite but not |
|
activated for |
|
automatic tests.</font><p style="margin-bottom: 0pt;">Further information on the use of the compressed |
|
repository is in the readme.compressedrepository file in the Pegasus source |
|
root directory<span style="color: rgb(51, 102, 255);">.</span></p> |
|
<h4><b>Pegasus MOF Compilers</b></h4> |
|
<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). |
|
</p> | </p> |
<h3><b><b>Security Considerations</b></b></h3> |
<div style="margin-left: 40px;">cimcli ns -l [3ffe:1:2:1]</div> |
<font style="color: rgb(0, 0, 0);" color="RED">OpenPegasus 2.5 (and |
<p>or</p> |
prior versions) contains several mechanisms to perform authorization, but none |
<div style="margin-left: 40px;">cimcli ns -l [3ffe:1:2:1]:5989<br> |
of these authorization checks are performed by default. |
|
By registering any provider which fails to do appropriate authorization |
|
checks, the consequences may include information leakage, data |
|
corruption, or unintended elevation of privilege. Please ensure that |
|
one of the following mechanisms is used to ensure appropriate access to |
|
your systems and data:</font><p style="margin-bottom: 0pt;"> |
|
<font style="color: rgb(0, 0, 0);" color="RED">1. Only install/register providers which perform authorization |
|
appropriate for your environment.</font></p> |
|
<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 in the source repository at: </span>pegasus/doc/PegasusSSLGuidelines.htm<br> |
specifying |
<h4><b>Server Security</b></h4> |
IPv6 addresses, refer to <a |
<ol style="margin-top: 0in;" start="1" type="1"> |
href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP Version |
<li class="MsoNormal" style="color: black;">Basic Authentication |
6 Addressing Architecture</a> |
(Note that Digest based security is not implemented in Pegasus)</li> |
and <a |
<li class="MsoNormal" style="color: black;">PAM authentication <o:p></o:p></li> |
href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 - 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 class="SpellE">OpenSSL</span>. . This release of Pegasus was tested |
contain IPv6-ready kernels, the |
with multiple versions of OpenSSL versions |
IPv6 capability is generally compiled as a module, but it's possible |
0.9.7 and 0.9.8. Effective with Pegasus 2.5.1 the Open SSL version |
that this module is not loaded automatically on startup.</p> |
0.9.6 is no longer supported. See <a href="http://www.openpegasus.org/pp/uploads/40/Application%20Data/Microsoft/Word/www.openssl.org">openssl.org</a> |
<p>Note: |
for <span class="SpellE">OpenSSL</span> release information<o:p>.</o:p></li> |
you shouldn't anymore use kernel series 2.2.x, because it's not |
<li class="MsoNormal" style="color: black;">SSL levels - <font style="color: rgb(0, 0, 0);">SSLv3 |
IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no |
and TLSv1 by default. SSLv2 is |
longer improved according to definitions in latest RFCs. It's recommend |
disabled by default and only enabled by a compile time option</font>. |
to use series 2.6.x now.<br> |
See<a href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502"> |
|
PEP 237</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> |
|
<b>Certificate management |
|
and User-based certificate authentication .</b> 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.</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>).</li> |
|
<li class="MsoNormal" style="color: black;">Out-of-process providers - See PEP 072 for more information on use of |
|
this feature </li> |
|
<li class="MsoNormal" style="color: black;">Shared class namespaces - 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 - 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 237</a> describes the environment variable (PEGASUS_ENABLE_SLP) to |
|
enable or disable this code. Effective with Pegasus 2.5.1, support has |
|
been added for the use of OpenSLP as the Service Agent (SA) in addition to the |
|
internal to the Service Agent. This is controlled through an additional |
|
environment variable (PEGASUS_HAS_OPENSLP) 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 (either the |
|
internal agent or OpenSLP) 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.</p> |
|
<h4><b>Indication Handlers</b></h4> |
|
<blockquote> |
|
<h5>System Log Indication Handler<br> |
|
</h5> |
|
<p>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> |
|
</p> |
|
<p>Each syslog file entry has a tag 'CIM Indication' to distinguish |
|
an entry made by Syslog Indication Handler.</p> |
|
<p>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.</p> |
|
<p>See |
|
<a href="http://www.openpegasus.org/pp/uploads/40/7165/PEP206-SystemLogIndicationHandler.htm" style="color: blue; text-decoration: underline;">PEP |
|
206</a> for details.</p> |
|
<h5>Email Indication Handler<br> |
|
</h5> |
|
<p>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" style="color: blue; text-decoration: underline;">PEP |
|
207</a> for details. </p> |
|
</blockquote> |
|
<h4>Pegasus Provider Interfaces</h4> |
|
<p>Pegasus is designed to support multiple Provider Managers to allow |
|
multiple provider interfaces to the CIMOM. The two default |
|
provider managers are the Pegasus C++ Interface and Common |
|
Manageability Programming Interface (CMPI) Interface.</p> |
|
<blockquote> |
|
<h5>C++ Provider Interface</h5> |
|
<p class="norm"><font face="Times New Roman" size="3">This is the original |
|
interface defined for OpenPegasus Providers. It provides an interface |
|
for both operations and indications. Many of the sample and test providers are |
|
written to this interface. This interface includes a callback into the |
|
CIMOM (CIMOMHandle).</font><br> |
|
</p> | </p> |
<h5><b style="">CMPI C interface Provider Manager<o:p></o:p></b></h5> |
<p>To check whether your current |
<span style="font-family: "times new roman";">Pegasus 2.5 includes |
running |
a provider manager for the CMPI C interfaces. This C interface is the |
kernel supports IPv6, take a look into your /proc filesystem. The entry |
result of a project by the IBM SBLIM team (see |
/proc/net/if_inet6 must exist. A short automated test looks like:<br> |
http://sblim.sourceforge.net) and is written to the Common |
|
Manageability Programming Interface, which is an OpenGroup standard. |
|
The CMPI |
|
specification is available at: |
|
http://www.opengroup.org/bookstore/catalog/c051.htm. This provides a |
|
standardized C level interface for creating providers that can be |
|
registered with the Pegasus CIM Server in the same manner as the |
|
current C++ providers. </span><span style="font-family: "times new roman";"><span class="norm"></span></span>The |
|
ability for CMPI providers to do user authorization is now available in |
|
Pegasus 2.5.1.<br> |
|
<span style="font-family: "times new roman";"> <br> |
|
Information on writing providers with the CMPI interface is available |
|
in the specification today (see above) and in the following documents |
|
(http://sblim.sourceforge.net/whitepaper.html and |
|
http://sblim.sourceforge.net/presentations.html) and readme.cmpi in the |
|
Pegasus source root directory.</span><p> |
|
<span style="font-family: times new roman;">NOTE: See the Feature status page |
|
for exact status of the CMPI provider manager for different Pegasus |
|
platforms.</span><br> |
|
</p> | </p> |
<h5>JMPI Java Interface Provider Manager</h5> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);"><font color="#000000">test -f |
<p>Pegasus |
/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"</font></div> |
includes a provider manager for Java |
<p>For more information on |
provider interfaces based on the SNIA provider interface |
enabling |
definitions. This provider manager is considered alpha |
IPv6 in the Linux kernel and configuring network interfaces, refer to |
quality and is not compiled in the default build. See |
<a |
readme.jmpi in the Pegasus source root directory for more information.</p> |
href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux |
</blockquote> |
Documentation Project's IPv6 HOWTO</a>.<br> |
</blockquote> |
|
<h3><b> Providers</b></h3> |
|
<div style="margin-left: 40px;">New for 2.5 is the ability of Providers |
|
to run out of process at |
|
request user- level and running CMPI providers remotely or out of |
|
process space.<br> |
|
<br> | <br> |
<span class="norm"></span>Administrators should check the providers to |
<span style="font-weight: bold;">Warning</span>: |
ensure that the provider vendor |
There is currently an open issue with RedHat to address a problem that |
has made use of available authorization capability.<br> |
is seen intermittently on RHEL5 and SLES10 systems. This problem is |
</div> |
described in <span |
<p style="margin-left: 40px;">There are a number of providers available |
style="color: rgb(153, 51, 153);"> |
in the Pegasus release. |
<a |
This includes providers in the following categories:</p> |
href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;"> |
bug 6586</a> |
<h4>Pegasus Internal Providers</h4> |
</span> |
<p>Pegasus provides a set of "internal" providers that have direct |
and<span |
access to the CIMOM for information and provide information and |
style="color: rgb(153, 51, 153);"> |
services to support the CIMOM and its administration. The |
<a |
providers in this category are mostly defined in the directory |
href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat |
src/pegasus/controlproviders and include support for the following |
bug 248052</a>, |
classes:</p> |
</span> |
<ul> |
and manifests itself as an intermittent IPv6 socket failure. You should be aware |
<li>DMTF Interop classes including __Namespace, <span class="SpellE">CIM_Namespace</span>, <span class="SpellE">CIM_ObjectManager</span>, |
that OpenPegasus with IPv6 enabled may be significantly impacted in these |
<span class="SpellE">CIM_CommunicationMechanism, and |
environments.</p> |
CIMOMStatistics.</span></li> |
<h4><font color="#000000">IPv6 on Windows</font></h4> |
</ul> |
<p>Microsoft provides supported IPv6 |
<h4><span class="SpellE">CMPI Remote Providers</span></h4> |
implementations for Windows Server |
<span class="SpellE">Pegasus includes an support for |
2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service |
running CMPI providers to be run on remote systems without the need for |
Pack 2 (SP2), and Windows CE .NET 4.1 and later.</p> |
an extra CIMOM. It uses a special proxying provider to relay requests |
On Windows XP, you can use the <span |
to a remote location using so-called communication layers. The remote |
style="font-weight: bold; ">ipv6.exe</span> tool to install, uninstall, and |
side has to start a CMPIRDaemon process, which accepts remote requests |
query |
and passes them on to CMPI style providers.</span><h3> |
your IPv6 configuration. For example:<br> |
<b>Generic Providers</b></h3> |
<br> |
<p>These are providers that support multiple pegauss platforms and include the Generic <span class="SpellE">OperatingSystem</span> provider. See |
<div style="margin-left: 40px; color: rgb(153, 51, 153);"><font color="#000000">ipv6 install<br> |
the |
ipv6 if</font></div> |
directory <span class="SpellE">src</span>/Providers/generic.</p> |
<p>Windows Vista |
<h4><b>Test/Sample Providers</b></h4> |
and Windows Server 2008 support an integrated |
<p>See the directories <span class="SpellE">src/Providers/TestProviders</span> |
IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack. |
and <span class="SpellE">src</span>/Providers/sample for more |
Note that the OpenPegasus IPv6 support has not yet been tested |
information about test and |
on Windows Vista or Windows Server 2008.<br> |
sample providers.</p> |
<br> |
<h4><b>Managed System Providers</b></h4> |
For more information on |
<p><span class="SpellE">ComputerSystem</span>, <span class="SpellE">DNSAdmin</span>, |
installing, configuring, and using IPv6 on Windows platforms, refer to |
<span class="SpellE">DNSService</span>, Operating System, Process, |
the document |
Processor. For |
<a |
more information on these providers see the documentation for each |
href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"> |
provider in |
<font color="#000000">IPv6 |
the directory <span class="SpellE">src/Providers/ManagedSystem</span></p> |
for Microsoft Windows: Frequently Asked Questions</font></a>.<br> |
<h4><span class="SpellE">Server Statistics Provider<br> |
|
</span></h4> |
|
CIM Server statistics, based on the DMTF 'CIM_StatisticalData' class, |
|
are implemented in this release. The statistics gathering is compiled |
|
by default but it is disabled through a property in the singleton |
|
CIM_ObjectManager class. It may be enabled or disabled by performing a |
|
ModifyInstance operation on the '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><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)</span></p> |
|
</blockquote> |
|
<h2><b>Pegasus Indication Listeners</b></h2> |
|
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;"> |
|
<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. |
|
</p> | </p> |
<p class="MsoNormal">Pegasus includes 3 separate Indication Listeners.</p> |
<h4><font color="#000000">Testing your OpenPegasus IPv6 |
<h3>Embedded CIMListener</h3> |
support</font></h4> |
<p class="MsoNormal">This listener is embedded in the CIMServer and allows the |
As part of the OpenPegasus |
server to accept indications and route them.</p> |
automated tests, the TestClient, g11ntest, and IndicationStressTest |
<h3>Standalone Static CIMListener</h3> |
test clients were modified to run tests using the IPv6 loopback address |
<p class="MsoNormal">This is a standalone listener that combines the functions |
(::1) if PEGASUS_ENABLE_IPV6=true.<br> |
of listener and consumer into a single element.</p> |
<br> |
<h3>Standalone Dynamic Listener</h3> |
You can also perform manual |
<p class="MsoNormal"> |
tests |
<font style="color: rgb(0, 0, 0);" color="#330099">Pegasus 2.5 |
using the IPv6 loopback or a real IPv6-configured network interface. |
includes a new standalone dynamic listener that is separate |
For example, using the IPv6 loopback on a system with OpenPegasus |
from the current standalone CIMListener and the ExportServer listener |
running on the WBEM standard http port of 5988:<br> |
in the CIM server. |
<div style="margin-left: 40px;"><br> |
The use model that this listener fits is the following: |
osinfo -h ::1</div> |
</font></p> |
<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2> |
<font style="color: rgb(0, 0, 0);" color="#330099"> </font><ul> |
<p>Support for forward-compatibility is a fundamental design principle for the |
<font style="color: rgb(0, 0, 0);" color="#330099"> <li> The listener may be packaged as |
OpenPegasus project. As a Community, our goal is for well-behaved OpenPegasus |
part of the CIMOM or it may be packaged independently as part of |
Providers or Clients, using only the externally defined OpenPegasus interface, |
another application. </li> |
to continue to work with a minor version upgrade of OpenPegasus. However, there |
<li> Consumers |
are certain classes of errors (e.g., non-compliance with a standard that |
are developed independently of the listener and may be shipped with the |
significantly affects interoperability) that may require the Community to make |
listener or added to an installed listener at a future time. </li> |
potentially incompatible changes. The following table contains a list of defect |
</font></ul> |
fixes that MAY impact, even well-behaved, OpenPegasus Providers or Clients when |
<font style="color: rgb(0, 0, 0);" color="#330099"> </font> |
upgrading to OpenPegasus 2.8.0.</p> |
<p></p> |
<TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666 |
<p><span style="color: rgb(0, 0, 0);"> </span><font color="#330099"><span style="color: rgb(0, 0, 0);">This |
borderColorLight=#CCCCCC border=1 width="80%"> |
dynamic listener provides a solution for the above use model. It |
<TBODY> |
is essentially a lightweight, pluggable listener that |
<TR align="center"> |
provides a small set of management features. The DynamicListener can be |
<TH bgColor=#00FFFF width=10%>Bugzilla #</TH> |
run inside a daemon or a service. It is easily configurable and |
<TH bgColor=#00FFFF>Description</TH> |
bypasses traditional registration procedures. See |
</TR> |
<a href="http://www.openpegasus.org/pp/protected/upreviews/20/1303/PEP195_CIMListenerEnhancementsv1_6.htm" style="color: blue; text-decoration: underline;"><span style="color: rgb(51, 51, 255); text-decoration: underline;">PEP 195</span></a> <span style="color: rgb(255, 0, 0);"> </span>for |
<TR align="center"> |
details.</span> </font></p> |
<TD><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=6812">6812</a></TD> |
</blockquote> |
<TD align="left">In Pegasus 2.8, the behavior of the setName() method is |
<h3><span class="SpellE"><b>CIM_Schema</b></span></h3> |
changed in the Pegasus C++ interface for the CIM data type model. For |
|
data types that use a shared representation model, the setName() method |
|
now throws an Exception when the object is "contained" by another CIM |
|
data object. <br> |
|
Specifically, setName() may throw the new exception in these cases: <br> |
|
<u>CIMProperty</u> contained by CIMClass, CIMInstance, and CIMObject <br> |
|
<u>CIMQualifier</u> contained by CIMClass, CIMInstance, CIMObject, |
|
CIMProperty, CIMParameter, and CIMMethod <br> |
|
<u>CIMMethod</u> contained by CIMClass <br> |
|
<u>CIMParameter</u> contained by CIMMethod</TD> |
|
</TR> |
|
<TR align="center"> |
|
<TD><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7453">7453</a></TD> |
|
<TD> |
|
<p align="left">In Pegasus 2.8, the C++ CMPI IndicationMI function |
|
signatures have been changed to fit the CMPIIndicationMIFT definitions. |
|
<br> |
|
The CmpiResult parameter in CmpiIndicationMI authorizeFilter, mustPoll, |
|
activateFilter and deActivateFilter have been removed cause it does not |
|
exist in the CMPIIndicationMIFT definitions. <br> |
|
The missing CmpiContext parameter and CMPIStatus have been added to |
|
enableIndications and disableIndications.</TD> |
|
</TR> |
|
<TR align="center"> |
|
<TD><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7488">7488</a></TD> |
|
<TD> |
|
<p align="left">In Pegasus 2.8, the CMPI property filter handling has |
|
been improved in performance. <br> |
|
Two things have changed in the behaviour of the property filter |
|
handling: <br> |
|
* Repeated applying of property filters onto the same instance will now |
|
only leave the properties which build the most common dominator on the |
|
instance. <br> |
|
* It is not possible anymore to add properties not defined for the |
|
corresponding class to an instance.</TD> |
|
</TR> |
|
<TR align="center"> |
|
<TD><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7624">7624</a></TD> |
|
<TD> |
|
<p align="left">In Pegasus 2.8, the algorithm used by the MessageLoader |
|
to search the accept language list to determine which message file to |
|
open was changed. Before Pegasus 2.8, the Message Loader used the |
|
following algorithm: </p> |
<blockquote> | <blockquote> |
<p>The default <span class="SpellE">CIM_Schema</span> loaded with this |
<p align="left">1.) The Message Loader will search the accept |
release is |
language list for an exact match. The first exact match found will |
the DMTF CIM 2.9, final release. In addition, Pegasus includes |
be returned.<br> |
a number of |
2.) If an exact match does not exist, the Message Loader will return |
local classes defined for Pegasus. These are defined in the pegasus/Schemas |
an ICU "fallback" match for the first entry in accept language list.<br> |
directory. <span style=""></span>There are also a |
3.) If an ICU "fallback" match does not exist for the first entry, |
number of older schema available in the CVS. Further, the CIM 2.10 and CIM |
it will return the ROOT resource bundle.</p> |
2.11 schemas are available in the CVS repository and the Pegasus is compatible |
|
with these Schemas.</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> |
|
</blockquote> | </blockquote> |
<h3><b>Pegasus CIM Server <span class="SpellE">Administration</span></b></h3> |
<p align="left">With the release of Pegasus 2.8, the Message Loader will |
<ol style="margin-top: 0in;" start="1" type="1"> |
not longer return ICU "fallback" matches. In addition, it will give |
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">cimuser</span></b> |
preference to the default process locale over the ROOT resource bundle. |
- Manage Pegasus CIM Server Users.<o:p></o:p></li> |
In Pegasus 2.8, the Message Loader has been modified to use the |
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">cimconfig</span></b> |
following algorithm: </p> |
- Manage the Pegasus CIM Server configuration parameters.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">cimauth</span></b> |
|
- Manage the CIM Server authorization characteristics. Today this is |
|
authorizing users to namespaces.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">cimprovider</span></b> |
|
- Manage information about the providers .</li> |
|
</ol> |
|
<br> |
|
<span style="font-weight: bold;">Server admin |
|
note:</span><br> |
|
<div style="margin-left: 40px;">The default behavior for determining |
|
the CIM server's HTTP and HTTPS ports has changed. In previous |
|
releases, any value in /etc/services would override a port explicitly |
|
specified in the configuration. The new order for determining the |
|
CIM server's HTTP and HTTPS ports is as follows:<br> |
|
1) An explicitly specified port value takes precedence over any other |
|
values.<br> |
|
</div> |
|
<div style="margin-left: 40px;">2) If no port is specified, the value |
|
in /etc/services is used.<br> |
|
3) If no value is specified in /etc/services, the default WBEM port is |
|
used.<br> |
|
</div> |
|
<h3><b>Information client tools</b></h3> |
|
<p>These tools provide information on the objects managed by the server.</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">tomof</span> |
|
</b>- output classes and/or instance information from the Pegasus |
|
repository in MOF or XML format.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">dnsinfo</span></b> |
|
- Generate a set of standard information on the <span class="SpellE">Domain</span> |
|
Name System (DNS) configuration from CIM Classes. Note that the |
|
information generated is dependent on the information available from |
|
providers and differs from system to system.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">ipinfo</span></b> |
|
- Generates a set of standard information from the Network |
|
Schema. Information generated varies by system because of the |
|
level of provider support.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">osinfo</span></b> |
|
- Generate a set of standard information on the Operating System from |
|
CIM Classes. Note that the information generated is dependent on the |
|
information available from providers and differs from system to system<o:p></o:p></li> |
|
</ol> |
|
<h3><b>Test support Tools</b></h3> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Pegasus unit tests |
|
(available through the "tests" option on the Pegasus make files) these |
|
tests are defined throughout the Pegasus source tree typically in |
|
"tests" directories. <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">The Pegasus test suite |
|
(see the pegasus/tests directory<span class="SpellE"></span>)<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">TestClient</span> |
|
</b>- Basic client for overall platform operation testing. <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">wbemexec</span></b> |
|
- Test tool that sends/receives XML from XML input.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b>CLI</b> - Command line |
|
interface for Client commands.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b>Benchmark Test</b> - A |
|
benchmark test environment is provided which includes both a client and |
|
provider component. See <span class="SpellE">src/clients/benchmarkTest</span> |
|
for more information.</li> |
|
<li class="MsoNormal" style="color: black;"><b>cimperf - </b>Lightweight statistics are implemented for |
|
the |
|
client. The client statistics surfaces the elapsed time spent in the |
|
client, |
|
and the |
|
elapsed time spent on the network between client and server.</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. |
|
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> | <ul> |
<li><font size="2">New CIM Listener now provides selective |
<p align="left">1.) The Message Loader will search the accept |
indication delivery.</font><br> |
language list for an exact match. The first exact match found will |
</li> |
be returned.<br> |
<li><font size="2">New CIM Listener |
2.) If an exact match does not exist, the Message Loader will return |
keeps all consumer libraries in memory for the duration of its |
an exact match for the default process locale.<br> |
execution.</font><br> |
3.) If an exact match for the default process locale is not found, |
</li> |
it will return the ROOT resource bundle.</p> |
<li><font size="2">New CIM Listener |
|
is now pluggable.</font></li> |
|
<li><font size="2">New CIM Listener |
|
now provides reliable indication delivery.</font></li> |
|
</ul> |
|
</ul> | </ul> |
<li class="MsoNormal" style="color: black;"><span lang="da">SLP |
</TD> |
Client (User Agent) APIs which are extensions to the Client APIs</span></li> |
</TR> |
</ol> |
<TR align="center"> |
<p class="MsoNormal"><span style="color: black;"><o:p> </o:p></span></p> |
<TD><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7501"> |
<p class="MsoNormal"><span style="color: black;">The APIs are |
7501</a></TD> |
documented in |
<TD> |
their respective header files and in HTML documentation based on |
<p align="left">Since OpenPegasus 2.7.2 the way CMPI_chars are added to |
the information |
arrays was corrected to follow the CMPI specification. Following the |
in the header files extracted with the doc++ tool will be available on |
CMPI specification means that CMPI_chars are not to be dereferenced, |
the |
contrary to all other subtypes of CMPIValues.<br> |
OpenPegasus web site.<br> |
If you experience an error since switching over to OpenPegasus 2.8 |
</span></p> |
saying "The byte sequence starting at offset xx is not valid UTF-8 |
<p class="MsoNormal"><b>WMI <span class="SpellE">Mapper</span></b></p> |
encoding", this is an indication for a missing update in the provider |
<p>The WBEM to WMI <span class="SpellE">Mapper</span> provides a way |
code.<br> |
to access |
<br> |
WMI data from Windows platform systems. It converts incoming XML/CIM |
The update for a C CMPI provider using arrays of CMPI_chars is to use a |
requests |
char* now as input parameter instead of a char**.<br> |
to Microsoft WMI requests, executes the requests, converts the results |
<u>CMPI Example:</u><br> |
to |
char* role = "Unknown";<br> |
XML/CIM and returns the results to the client. WMI <span class="SpellE">Mapper</span> |
array = CMNewArray(_broker,1,CMPI_chars,rc);<br> |
receives an HTTP message containing the XML/CIM request. It decodes the |
<i>from:</i><br> |
XML |
CMSetArrayElementAt(array,0,(CMPIValue*)<b>&</b>role,CMPI_chars);<br> |
message and extracts from the HTTP message header the user credentials |
<i>to:</i><br> |
provided |
CMSetArrayElementAt(array,0,(CMPIValue*)role,CMPI_chars);</TD> |
on the connection (username and password). The WMI <span class="SpellE">Mapper</span> |
</TR> |
authenticates these credentials, verifying if the provided credentials |
</TBODY> |
have |
</TABLE> |
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 |
</html> |
account with |
|
administrative rights (which has all access to WMI data). Because of |
|
this, the |
<h2>OpenPegasus Relationship to |
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> |
|
<ol> |
|
</ol> |
|
<h2>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 specifications |
CIM/WBEM specifications The following table defines the level of the |
to which this version of 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.17.1 Final, 14 Dec 2007( 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. |
|
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.<font color="#ff0000"> </font></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. <br> |
|
</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 base |
code |
including a maintainer for the platform that will be willing to regularly |
base including a maintainer for the platform that will be willing to |
document issues and/or fix defects as the Pegasus code base is changed. |
regularly document issues and/or fix defects as the Pegasus |
Pegasus may be operable on other platforms (ex. Windows 98) but without a group |
code base is changed. |
to provide the role of test and maintenance, correct operation of Pegasus |
Pegasus may be operable on other platforms (ex. Windows 98) but without |
cannot be assured. In all cases, including the active platforms, it is the |
a group |
responsibility of the entity that packages and/or compiles OpenPegasus for |
to provide the role of test and maintenance, correct operation of |
shipment or deployment, to read, and actively monitor the Pegasus bugzilla |
Pegasus cannot be |
database for a list of relevant defects that affect their platform. |
assured. In all cases, including the active platforms, it is the |
The platforms that are considered ported are shown in the two tables below. |
responsibility of the entity that packages and/or compiles OpenPegasus |
The first table represents platform sofr which testing is done on a regular |
for shipment or deployment, to read, and actively monitor the Pegasus |
basis and reported to the Pegasus Nightly Build Test WEB Page. Those platforms |
bugzilla database for a list of relevant defects that affect their |
which have been ported but do not have test results that are current at the time |
platform. The platforms that are considered 'active' for this |
of the release are reported in the second table</p> |
Pegasus release are:<br> |
<p align="center"><br> |
<span class="norm"></span><br> |
<b>Actively Supported Platforms (Nightly Tests Reported for this release</b></p> |
</p> |
<table class="MsoNormalTable" style="width: 90%;" border="1" |
<table class="MsoNormalTable" style="width: 302.25pt;" border="1" cellpadding="0" cellspacing="1" height="409" width="504"> |
cellpadding="0" cellspacing="1"> |
<tbody> | <tbody> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; background: rgb(153, 255, 153) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 126.75pt;" height="26" width="211"> |
<td |
|
style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;" |
|
height="26"> |
<p class="MsoNormal"><b><span style="color: black;">Platform and | <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 style="padding: 0.75pt; background: rgb(153, 255, 153) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 173.25pt;" height="26" width="289"> |
<td |
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span style="color: black;"><o:p></o:p></span></p> |
style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;" |
|
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" width="211"> |
<td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span style="color: black;">HP-UX<o:p></o:p></span></p> | <p class="MsoNormal"><span style="color: black;">HP-UX<o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" width="289"> |
<td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span style="color: black;">HP <span class="SpellE">aC</span>++ B3910B<o:p></o:p></span></p> |
<p class="MsoNormal"><span style="color: black;">HP <span |
|
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" width="211"> |
<td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">Linux on Power</span></span><span style="color: black;"><o:p></o:p></span></p> |
<p class="MsoNormal"><span class="SpellE"><span |
|
style="color: black;">Linux on Power</span></span><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" width="289"> |
<td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
<p class="MsoNormal"><span class="SpellE"><span |
|
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" width="211"> |
<td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">zLinux</span></span><span style="color: black;"><o:p></o:p></span></p> |
<p class="MsoNormal"><span class="SpellE"><span |
|
style="color: black;">zLinux</span></span><span style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" width="289"> |
<td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
<p class="MsoNormal"><span class="SpellE"><span |
|
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" width="211"> |
<td style="padding: 0.75pt; "> |
<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" width="289"> |
<td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
<p class="MsoNormal"><span class="SpellE"><span |
|
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" width="211"> |
<td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span style="color: black;">Linux IA-32<o:p></o:p></span></p> |
<span style="color: black;"><font size="3">Linux IA-32</font></span></td> |
|
<td style="padding: 0.75pt; "> |
|
<span class="SpellE"><span |
|
style="color: black;"><font size="3">gcc</font></span></span><span style="color: black;"><font size="3"> |
|
(versions 2.9x, 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" width="289"> |
<td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"> |
<p class="MsoNormal"><span class="SpellE"><span |
(versions 2.9x and 3.xx)<o:p></o:p></span></p> |
style="color: black;">gcc</span></span><span style="color: black;"> |
|
(versions 2.9x, 3.xx, 4.xx)</span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="91" width="211"> |
<td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span style="color: black;">Windows 2000<o:p></o:p></span></p> |
<p class="MsoNormal"><span style="color: black;">Windows 2000</span></p> |
</td> |
|
<td style="padding: 0.75pt; width: 173.25pt;" height="91" width="289"> |
|
<p class="MsoNormal"><span style="color: black;" lang="NL">Microsoft |
|
Visual C++ Ver 6 and Microsoft .Net compiler Version. </span><span style="color: black;">Works on VC .NET 2003 (<span class="SpellE">aka</span> |
|
v7.1)<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. 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="padding: 0.75pt; width: 126.75pt;" height="69" width="211"> |
<td style="padding: 0.75pt; "> <font size="3">Windows 2003</span></font></p> |
<p class="MsoNormal"><span style="color: black;">Windows XP<o:p>, Windows |
</td> |
2003</o:p></span></p> |
<td style="padding: 0.75pt; "> |
</td> |
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1. |
<td style="padding: 0.75pt; width: 173.25pt;" height="69" width="289"> |
Note: Visual C++ Ver. 6 no longer being regular tested. |
<p class="MsoNormal"><span style="color: black;" lang="NL">Microsoft |
</font> |
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> |
</tr> | </tr> |
<tr style=""> |
<tr> |
<td style="padding: 0.75pt; width: 126.75pt;" height="43" width="211"> <font size="3">MacOS version 10.2 and higher</font></td> |
<td style="vertical-align: top;"><big>HP OpenVMS 8.3 or later Alpha</big></td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="43" width="289"> <font size="3">gcc 3.3</font></td> |
<td style="vertical-align: top;"><font size="3"> </font><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> |
<tr> | <tr> |
<td style="vertical-align: top;"><big>HP OpenVMS Alpha<br> |
<td style="vertical-align: top;"><big><span class="norm"></span><font |
</big></td> |
style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later IA64</font></big></td> |
<td style="vertical-align: top;"> <big><font style="color: rgb(0, 0, 0);" color="RED">HP C++ V6.5-042 for OpenVMS |
<td style="vertical-align: top;"><span class="norm"></span><big><font |
Alpha and above</font></big> </td> |
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> |
<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;"><font size="3">z/OS V1.7 and up</font></td> |
<td style="vertical-align: top;"><span class="norm"></span><big><font style="color: rgb(0, 0, 0);">HP C++ V7.1-011 on OpenVMS IA64 and above</font></big> |
<td 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 no Actively supported for this release (No |
|
current Nightly Build Test Results</b></p> |
|
<table class="MsoNormalTable" style="width: 90%;" border="1" |
|
cellpadding="0" cellspacing="1" id="table2"> |
|
<tbody> |
|
<tr style=""> |
|
<td |
|
style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;" |
|
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Platform and |
|
OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
<td |
|
style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;" |
|
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span |
|
style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt; "> <font size="3">Windows XP</font></p> |
|
</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> | </td> |
</tr> | </tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt; "> <font size="3">MacOS version 10.3 and higher</font></td> |
|
<td style="padding: 0.75pt; "> <font size="3">gcc 4.01</font></td> |
|
</tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 8<br> |
<td style="vertical-align: top;"><big><font color="RED"><span |
</span></font></big></td> |
style="color: rgb(0, 0, 0);">Solaris 8</span></font></big></td> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun CC |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
compiler V 5.8. Note that the latest thread patch (108993) may be |
CC compiler V 5.8. Note that the latest thread patch (108993) may be |
required. (see Pegasus bug 4632)</big><br> | required. (see Pegasus bug 4632)</big><br> |
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><span class="norm"></span><big><font><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9<br> |
<td style="vertical-align: top;"><span class="norm"></span><big><font |
</span></font></font></big></td> |
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 |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
</td> | </td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<br> |
<p><b>Platform patches</b> |
<b>Platform patches</b><p style="margin-top: 0pt; margin-bottom: 0pt;"> |
|
<font style="color: rgb(0, 0, 0);">The following is a list of platform |
|
patches Pegasus requires.<br> |
|
</font> |
|
</p> | </p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font |
|
style="color: rgb(0, 0, 0);">The following is a list known of platform |
|
patches Pegasus requires.</font></p> |
<div style="margin-left: 40px;"> | <div style="margin-left: 40px;"> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font style="color: rgb(0, 0, 0);">RHAS |
|
2.1 needs the update to fix Red Hat Bugzilla 98815.</font><br> |
|
</p></div> |
|
<br> |
|
<p>Further information regarding Pegasus support on IBM platforms can |
|
be |
|
found at: <a href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span style="text-decoration: underline; color: rgb(51, 51, 255);">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</span></a> |
|
</p> |
|
<p> <br> |
|
Further information regarding Pegasus support on HP platforms can be |
|
found at: |
|
<a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> |
|
<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;"> |
instance aliasing</b> - The Pegasus MOF compiler does not today support |
<font |
this function. This function is planned for a future version.</p> |
style="color: rgb(0, 0, 0);">RHAS |
</li> |
2.1 needs the update to fix Red Hat Bugzilla 98815.</font></p></li> |
<li> | <li> |
<p class="MsoNormal"><b> MultiRequest Oprations</b> - Pegasus |
<p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4 multithreading bug in |
does not support the DMTF defined MultiRequest Operation option.</p> |
getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is fixed in |
</li> |
RHEL 4.5</p></li> |
<li> | <li> |
<p class="MsoNormal"><b>MOFCompiler namespace pragma</b> - The |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE Linux |
Pegasus compiler does not support the namespace pragma.</p> |
multiple versions - |
</li> |
multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla |
|
6586) (Red Hat bug 248052)<br></p></li> |
</ol> | </ol> |
<h2><a name="Changes in This Release">Changes in This Release</a></h2> |
</div> |
<p>The development and release of each version of Pegasus is defined |
<p>Further information regarding Pegasus support on IBM platforms can |
and |
be |
controlled through Pegasus PEP documents. PEP 180 is the |
found at: <a |
controlling document for Pegasus 2.5.0 and PEP 239 is the controlling |
href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span |
document for this release. These PEPs list the original set of changes proposed and the |
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> |
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 release 2.5.0 were:</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Addition of CQL |
|
stage 1 support<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Refactoring of |
|
Object Normalizer function to improve performance. </p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Out of Process |
|
Provider user level request.<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Embedded Object |
|
support. </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> | </p> |
</li> |
<p> Further information regarding Pegasus support on HP platforms can |
<li class="MsoNormal" style="color: black;"> |
be |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of HTTP |
found at: |
chunking. Pegasus |
<a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> |
now supports HTTP V1.1 transfer encoding otherwise known as chunking .<font style="color: rgb(51, 51, 255);" color="RED"><a href="http://www.openpegasus.org/pp/uploads/40/5097/PEP140_ChunkedEncoding_4.3.html"> |
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2> |
PEP 140</a></font> describes the implementation details.</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;">Client side performance |
|
statistics</li> |
|
<li class="MsoNormal" style="color: black;">Syslog Indication handler.</li> |
|
<li class="MsoNormal" style="color: black;">Email Indication handler.</li> |
|
<li class="MsoNormal" style="color: black;">Port to OpenVMS.</li> |
|
</ol> |
|
<p>For release 2.5.1, a number of additional changes were made( See PEP 239 for |
|
more details):.</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li>Significant performance improvements ( better than 10 to 1 for operations |
|
and 3 to 1 for indications). (bug 4225)</li> |
|
<li>Improved support for the several platforms (Solaris, MacOS, HardHat Linux)</li> |
|
<li>Modified Makefile targets for easier usage.</li> |
|
<li>Extended and reorganized unit and end-end tests.</li> |
|
<li>Completed implementation of statistics gathering for operations.</li> |
|
<li>Further integrated CMPI and added additional tests.</li> |
|
<li>Consolidate some of the compile-time variables. Largely this meant moving |
|
from separate variables for DISABLE and ENABLE to a single variable where the |
|
value representes the state.</li> |
|
<li>Corrected error where Pegasus could not maintain general whitespace in |
|
strings (bug 4624).</li> |
|
<li>SLP extended to allow optional use of OpenSLP as the Service Agent (SA) in place of |
|
the Pegasus internal SA.</li> |
|
<li>Changes to align OpenPegasus and Red Hat RPM packaging and configuration |
|
options.</li> |
|
<li>Additonal testing and integration of the JMPI provider manager.</li> |
|
</ol> |
|
<p>Specifically the status of several components of Pegasus functionality were |
|
moved in status on the Feature Status Page as follows:</p> |
|
<ol> |
|
<li>Binary Repository move to green (production capable). (see bug 4388)</li> |
|
<li>Out of Process providers</li> |
|
<li>Pegasus Provider Interfaces, User Context for Linux and Unix</li> |
|
</ol> |
|
<p class="MsoNormal" style="margin-left: 0.5in;"> </p> |
|
The complete set of <span class="SpellE">changes </span>defined for this release |
|
is defined in PEP 239 |
|
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus defects<br> |
|
</a></span></h2> |
|
<p>The Pegasus bugzilla database documents any defects found in Pegasus | <p>The Pegasus bugzilla database documents any defects found in Pegasus |
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla | and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla |
database</a>. Note that bugs committed for Pegasus 2.5.1 have been marked |
database</a>. |
with the keyword <font face="Courier New"><b>2.5.1_APPROVED</b></font> so that |
Effective with the start of the Pegasus 2.6 work, all changes to the CVS tree |
all bug fixes for this release can be found with the following bug search. |
were documented through bugs. Bugs reports were filed not only for bugs and |
Note that since this was a minor release all of the fixes were documented as |
their corresponding fixes but also as part of the process of committing new code |
bugs so that even the changes listed in the previous section are listed as bugs.</p> |
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>) will yield all changes to |
|
the Pegasus CVS tree for that Pegasus release.</p> |
|
|
<p> | <p> |
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVEDhttp://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVED"> |
- Changes for Pegasus 2.8.0 release (bugs Tagged |
http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVED</a><br> |
2.8.0_APPROVED) <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.8.0_APPROVED"> |
</p> |
Pegasus 2.8.0_APPROVED bug list</a></p> |
<h2><a name="Pegasus Release Control and Version Definition Documentation">Pegasus |
|
Release Control and Version Definition Documentation</a></h2> |
<h2><a |
|
name="Pegasus Release Control and Version Definition Documentation">Release Control and Version Definition Documentation</a></h2> |
|
|
<p>The Pegasus project is controlled largely through a set of documents | <p>The Pegasus project is controlled largely through a set of documents |
(PEPs) that serve as the definition and review mechanism for new and |
(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 | <p>Specifically the following PEPs define the characteristics of this |
Pegasus release.</p> |
Pegasus release. These PEPs are available at |
|
<a href="http://www.openpegasus.org/pp/protected/documents.tpl?CALLER=index.tpl&gdc_docage=0&S=gdc_title&R=desc" style="color: blue; text-decoration: underline; text-underline: single"> |
|
OpenPegasus Approved PEPs.</a></p> |
|
|
|
<b> |
|
|
<ol> | <ol> |
|
|
<li> | <li> |
<a href="http://www.openpegasus.org/pp/uploads/40/8568/PEP209_ExternalInterface2.5.htm">PEP 209</a> - OpenPegaus 2.5 External Interfaces.<br> |
PEP 333 - OpenPegasus Release Definition - </b>This PEP ( and a corresponding |
</li> |
section in the Pegasus wiki) is used |
|
throughout the development of this version as the control point for |
|
functionality that will go into the release and points to all of the PEPs that |
|
represent the Pegasus functionality changes for this version of Pegasus.</li> |
|
|
|
<b> |
|
|
<li> | <li> |
<a href="http://www.openpegasus.org/pp/uploads/40/10083/PEP237_RecommendedReleaseOptions.htm">PEP 237</a> - OpenPegaus 2.5.1 Build and Configuration |
<a href="http://www.openpegasus.org/pp/uploads/40/16781/PEP308_RecommendedReleaseOptions.htm"> |
Option for Selected |
PEP 308</a> - OpenPegasus Build and Configuration |
|
Options for Selected |
Platforms</li> | Platforms</li> |
<li>PEP 249 - Pegasus 2.5.1 Release Notes (This document located in the PEP |
|
repository and the Pegasus source tree root directory)</li> |
|
<li> | <li> |
<a href="http://www.openpegasus.org/pp/uploads/40/9825/PEP242_RuntimePackaging2.5.1.htm">PEP 242</a> - Pegasus 2.5.1 Runtime Packaging Definition<br> |
<a href="http://www.openpegasus.org/pp/uploads/40/16780/PEP329_ExternalInterface2.8.htm"> |
|
PEP 329</a> - OpenPegasus 2.8 External Interfaces - </b>Lists the public |
|
interfaces for clients and providers that are considered external and |
|
therefore "frozen".<b><br> |
|
|
</li> | </li> |
|
|
<li> | <li> |
<a href="http://www.openpegasus.org/pp/uploads/40/9820/PEP243_SDKFile2.5.1.htm">PEP 243</a> - OpenPegasus 2.5.1 SDK Packaging Definition</li> |
<a href="http://www.openpegasus.org/pp/uploads/40/16779/PEP330_SDKFile2.8.0.htm"> |
<li>PEP 251 - Pegasus readme.txt for 2.5.1 (Located in PEP repository |
PEP 330</a> - OpenPegasus SDK Packaging Definition - </b>Defines the |
and also in the Pegasus |
recommended set of files for inclusion in the OpenPegasus SDK</li> |
source |
|
tree root directory).</li> |
<b> |
|
|
<li> | <li> |
<a href="http://www.openpegasus.org/pp/uploads/40/10067/PEP239_2_5_1ReleaseDefinition.htm">PEP 239</a> - OpenPegasus Release Definition - This PEP is used |
<a href="http://www.openpegasus.org/pp/uploads/40/16778/PEP331_RuntimePackaging2.8.0.htm"> |
throughout the development of this version as the control point for |
PEP 331</a> - Pegasus Runtime Packaging Definition - </b>Defines the |
functionality that will go into the release and points to all of the |
recommended set of files for inclusion in this OpenPegasus release.</li> |
PEPs that represent the Pegasus 2.5 functionality changes. (as of |
|
this document verion of PEP 230, PEP 180 is listed as draft status)</li> |
<b> |
|
|
|
<li>PEP 332 - Pegasus Release Notes (This document located in the |
|
approved PEP |
|
repository and the OpenPegasus source tree root directory) <br> |
|
|
|
</li> |
|
|
</ol> | </ol> |
|
|
<h2><a name="General Documentation">General Documentation</a></h2> | <h2><a name="General Documentation">General Documentation</a></h2> |
<p>The following documentation is available for the this Pegasus | <p>The following documentation is available for the this Pegasus |
release:</p> | release:</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 |
<li class="MsoNormal" style="color: black;"><b>Utilities</b> - </b>A |
combination of help generally available with the -h option for each |
combination of help generally available with the --help option for each |
command and HTML documentation for most of the tools.<o:p></o:p></li> | command and HTML documentation for most of the tools.<o:p></o:p></li> |
|
|
|
<b> |
|
|
<li class="MsoNormal" style="color: black;"><b>API and usage | <li class="MsoNormal" style="color: black;"><b>API and usage |
documentation</b> - See the header files and the HTML API |
documentation</b> - </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.</li> |
|
|
|
<b> |
|
|
<li class="MsoNormal" style="color: black;"><b>Building and Debugging | <li class="MsoNormal" style="color: black;"><b>Building and Debugging |
Providers </b>- Readme.html in the Pegasus Root Directory, API |
Providers </b>- </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.</li> |
|
|
|
<b> |
|
|
<li class="MsoNormal" style="color: black;"><b>Building and Debugging | <li class="MsoNormal" style="color: black;"><b>Building and Debugging |
Clients</b> - API documentation and the documentation on the Pegasus |
Clients</b> - </b>API documentation and the documentation on the Pegasus |
Technical Workshop which is available on the Pegasus web site.</li> | Technical Workshop which is available on the Pegasus web site.</li> |
<li class="MsoNormal" style="color: black;"><b>Compiler operation and |
|
commands</b> - compiler help (cimmofl -h)</li> |
<b> |
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - The |
|
|
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - </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 |
|
|
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.</li> |
</ul> | </ul> |
|
|
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="color: black;"> <o:p></o:p></span></p> |
<b> |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
|
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"> |
<p class="MsoNormal" style="margin-left: 0.5in;"><span |
<p style="text-align: left;"><i><font size="2">Copyright (c) 2006 EMC |
style="color: black;"> <o:p></o:p></span></p> |
Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open |
<div class="MsoNormal" style="text-align: center;" align="center"><span |
Group; VERITAS Software Corporation; Intel Corp.</font><br> |
style="color: black;"> |
|
<hr align="center" color="#009900" noshade="noshade" size="2" |
|
width="100%"> |
|
<p style="text-align: left;"><i><font size="2">Copyright (c) 2007 EMC |
|
Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The |
|
Open Group; VERITAS Software Corporation; Intel Corp.</font><br> |
<br> | <br> |
<font size="1">Permission is hereby granted, free of charge, to any person |
<font size="1">Permission is hereby granted, free of charge, to any |
obtaining a copy of this software and associated documentation files (the |
person obtaining a copy of this software and associated |
"Software"), to deal in the Software without restriction, including without |
documentation files (the "Software"), to deal in the Software without |
limitation the rights to use, copy, modify, merge, publish, distribute, |
restriction, including without limitation the rights to use, copy, |
sublicense, and/or sell copies of the Software, and to permit persons to whom |
modify, merge, publish, distribute, sublicense, and/or sell copies of |
the Software is furnished to do so, subject to the following conditions:</font><br> |
the Software, and to permit persons to whom the Software is furnished |
|
to do so, subject to the following conditions:</font><br> |
<font size="2"><br> | <font size="2"><br> |
</font><font size="1">THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE |
</font><font size="1">THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION |
SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE |
NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE |
SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR |
SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF |
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, |
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE |
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE |
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND |
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER |
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE |
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, |
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION |
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE |
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION |
SOFTWARE.</font></i></p></span></div> |
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</font></i></p> |
|
</span></div> |
<p> </p> | <p> </p> |
</div> | </div> |
<script language="javascript">postamble();</script> |
|
<script language="javascript">postamble();</script> |
|
</body></html> |
|
|
</body> |
|
</html> |