version 1.7, 2006/03/28 19:58:13
|
version 1.21.2.1, 2015/03/31 22:41:07
|
|
|
<!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> |
| |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> |
<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"><title>PEP</title></head><body lang="EN-US" link="blue" vlink="blue"><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype> <o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml> |
|
<o:DocumentProperties> <o:Author>IBM_User</o:Author> <o:LastAuthor> </o:LastAuthor> <o:Revision>4</o:Revision> <o:TotalTime>211</o:TotalTime> <o:Created>2004-04-05T14:13:00Z</o:Created> <o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>5026</o:Words> <o:Characters>28651</o:Characters> <o:Company>IBM</o:Company> <o:Lines>238</o:Lines> <o:Paragraphs>67</o:Paragraphs> <o:CharactersWithSpaces>33610</o:CharactersWithSpaces> <o:Version>10.4219</o:Version> </o:DocumentProperties></xml><![endif]--><!--[if gte mso 9]><xml> |
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype> |
<w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:Compatibility> <w:ApplyBreakingRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument></xml><![endif]--> |
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml> |
|
<o:DocumentProperties> |
|
<o:Author>IBM_User</o:Author> |
|
<o:LastAuthor> </o:LastAuthor> |
|
<o:Revision>4</o:Revision> |
|
<o:TotalTime>211</o:TotalTime> |
|
<o:Created>2004-04-05T14:13:00Z</o:Created> |
|
<o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> |
|
<o:Pages>1</o:Pages> |
|
<o:Words>5026</o:Words> |
|
<o:Characters>28651</o:Characters> |
|
<o:Company>IBM</o:Company> |
|
<o:Lines>238</o:Lines> |
|
<o:Paragraphs>67</o:Paragraphs> |
|
<o:CharactersWithSpaces>33610</o:CharactersWithSpaces> |
|
<o:Version>10.4219</o:Version> |
|
</o:DocumentProperties> |
|
</xml><![endif]--><!--[if gte mso 9]><xml> |
|
<w:WordDocument> |
|
<w:SpellingState>Clean</w:SpellingState> |
|
<w:GrammarState>Clean</w:GrammarState> |
|
<w:Compatibility> |
|
<w:ApplyBreakingRules/> |
|
</w:Compatibility> |
|
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> |
|
</w:WordDocument> |
|
</xml><![endif]--> |
|
|
|
|
|
|
|
|
|
<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="Section1"> |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> | <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> | <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 |
<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;" align="center"><b><span style="font-size: 13.5pt; color: black;">OpenPegasus Enhancement |
Enhancement Proposal (PEP)<o:p></o:p></span></b></p> |
Proposal (PEP)<o:p></o:p></span></b></p> |
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"><br> |
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"> |
<br> | <br> |
<b>PEP #:</b> 249<br> |
<b>PEP #:</b> 368<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 version 2.14.x</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> 20 November 2014<br> |
<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> |
<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%;" id="table1" border="1" cellpadding="0" cellspacing="1" height="155" width="100%"> |
<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: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-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: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-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: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-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: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-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"> 0.99</font><o:p></o:p></span></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"><span style="font-family: Arial; color: black;"><o:p><font size="2"> 1 March |
<p class="MsoNormal" style="text-align: center;" align="center"> <font size="2"><span style="font-family: Arial;">12 Nov. 2014<br> |
2006</font></o:p></span></p> |
</span></font></p> |
</td> |
|
<td style="padding: 0.75pt;" align="left"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"> |
|
<span style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> |
|
</td> | </td> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" align="left" height="22"> |
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial |
<p class="MsoNormal" style="text-align: center;" align="center"> <span style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> |
Submission</font><o:p><font size="2"> |
</td> |
</font></o:p></span></p> |
<td style="padding: 0.75pt;" height="22"> |
|
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial Submission for review<span style="color: red;"></span></font><o:p><font size="2"> </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" height="21">1.00<br> |
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">2 March 2006</font></td> |
</td> |
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">Karl Schopmeyer</font></td> |
<td style="padding: 0.75pt;" align="center" height="21">14 March 2015<br> |
<td style="padding: 0.75pt;"><font face="Arial" size="2">Fix editorial errors</font></td> |
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer<br> |
|
</td> |
|
<td style="padding: 0.75pt;" height="21">Update to finish the document (approved as bug 9684)<br> |
|
</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" height="21">1.01<br> |
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">20 March 2006</font></td> |
</td> |
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">Karl Schopmeyer</font></td> |
<td style="padding: 0.75pt;" align="center" height="21">31 March 2015<br> |
<td style="padding: 0.75pt;"><font face="Arial" size="2">Incorporate comments from |
</td> |
Review week of 12 March 2006</font></td> |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer<br> |
</tr> |
</td> |
<tr> |
<td style="padding: 0.75pt;" height="21">Update to reflect changes for 2.14.1<br> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.3</font></td> |
</td> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">22 March |
</tr> |
2006</font></td> |
<tr> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
<td style="padding: 0.75pt;" align="center" height="21"><br> |
Schopmeyer</font></td> |
</td> |
<td style="padding: 0.75pt;"><font face="Arial">Incorporate comments form |
<td style="padding: 0.75pt;" align="center" height="21"><br> |
Review 21 March 06 and bring into line with Feature status page</font></td> |
</td> |
</tr> |
<td style="padding: 0.75pt;" align="center" height="21"><br> |
<tr> |
</td> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.4</font></td> |
<td style="padding: 0.75pt;" height="21"><br> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">28 March |
</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">Remove all statements |
|
concerning status and point to the Feature Status Page.</font></td> |
|
</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 |
|
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 references to |
|
status "experimental" for certain features</font></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" height="23"> </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" height="23"> </td> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
<td style="padding: 0.75pt;" height="23"> </td> |
Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial">Typos</font></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"><span style="color: black;"> |
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> | <hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
<p><b>Abstract:</b> This document defines the release notes for the 2.5.1 |
<br> |
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> |
<b>Abstract:</b> This document defines the release notes for the 2.14.0 |
</a></span></span></p> |
release of the OpenPegasus CIM Server. The purpose of this PEP is to |
|
summarize the characteristics of this release, point to other |
|
documentation that defines the release in more detail, and provide |
|
additional information about this release that is not available in the |
|
other Pegasus documentation.<br> |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> | <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> | <hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
<h2 style="margin-bottom: 1px;"><b><o:p><font size="4"> Contents<br> |
<h2 style="margin-bottom: 1px;"><b><o:p><font size="5"> Contents</font></o:p></b></h2> |
</font></o:p></b></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 |
<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship |
of This Release</a></li> |
to CIM/WBEM Standards</a></li> |
<li><a href="#Compatibility_Considerations_">Compatibility |
<li><a href="#Supported%20Platforms">Supported |
Considerations</a></li> |
Platforms</a></li> |
<li><a href="#Notes_on_Specific_OpenPegasus">Notes on Specific |
|
OpenPegasus Functionality</a><br> |
|
</li> |
|
<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship to |
|
CIM/WBEM Standards</a></li> |
|
<li><a href="#Supported%20Platforms">OpenPegasus Supported Platforms</a></li> |
<li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance | <li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance |
with DMTF Specifications</a></li> | with DMTF Specifications</a></li> |
<li><a href="#Changes%20in%20This%20Release">Changes |
<li><a href="#PEGASUS%20Bugs">OpenPegasus Bugs</a></li> |
in This Release</a></li> |
<li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus |
<li><a href="#PEGASUS%20Bugs">PEGASUS |
Release |
Bugs</a></li> |
Control and Version Definition Documentation</a></li> |
<li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">Pegasus |
<li><a href="#General%20Documentation">General Documentation</a></li> |
Release Control and Version Definition Documentation</a></li> |
|
<li><a href="#General%20Documentation">General |
|
Documentation</a></li> |
|
</ol> | </ol> |
<h2><span style="color: black;">Availability |
<h2><span style="color: black;">Availability of this Release</span></h2> |
of this Release</span></h2> |
This release is available in a number of forms including:<br> |
<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. |
downloaded from the <span class="SpellE">OpenPegasus</span> Web |
These can be downloaded from the <span class="SpellE">OpenPegasus</span> |
site at <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a></li> |
Web site at <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li> |
<li>OpenPegasus 2.5.1 binaries are available for Red Hat Enterprise |
<li><b>OpenPegasus source RPMs</b> on the OpenPegasus web site.. A |
Linux 3.0 and 4.2 and SUSE LINUX Enterprise Server 9.0. A Source RPM is |
source RPM is available on the OpenPegasus web site that can be |
also available that can be used to build binaries for most |
used to build binaries for most LSB-compliant RPM-based Linux |
LSB-compliant RPM-based Linux distributions and versions.</li> |
distributions and versions.</li> |
<li>The Pegasus CVS. The CVS tags representing this release and |
<li><b>TheOpenPegasus CVS repository</b>. The CVS tags representing this |
subsequent snapshots that are made available in the Pegasus CVS are |
release and subsequent snapshots that are made available in the |
defined on the OpenPegasus CVS repository web page (see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus |
Pegasus CVS are defined on the OpenPegasus CVS repository web page |
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 |
(see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus |
snapshots page</a>.</li> |
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> and the <a title="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus">OpenPegasus |
|
WIKI Release Status 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 |
<br> |
WEB site</a>. |
The instructions for acquiring the released code are on the <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus |
Installation instructions are part of the README in the root of the |
WEB |
Pegasus source |
site</a> and the <a title="OpenPegasus WIKI" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">OpenPegasus |
tree.</p></div> |
WIKI</a>. Installation instructions are part of the README in the root |
<div class="Section1"> |
of the Pegasus source tree.<br> |
<h2><span style="color: black;">Functionality of This Release</span></h2> |
|
Pegasus overall status by release is defined by a |
|
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a> |
|
that is available on the OpenPegasus web site . That |
|
web page shows the Pegasus users and developers |
|
the status of the various features found in Pegasus using a simple color coded |
|
key (white, red, yellow, green). Pegasus 2.5.1 is a minor release, extending Pegasus 2.5.0 in selected |
|
areas primarily for bug fixes. However, there were some signification |
|
changes in the feature status for selected functions in 2.5.1 (moving selected |
|
functions closer to production-capable status).<p>The following paragraphs list the functionality in this release. In many cases these features and interfaces |
|
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> |
|
provides more detailed information on how to enable |
|
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, |
|
please access the</font> |
|
<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 |
|
of the features listed below are production ready.</font></p> |
|
<h3><b>CIM Server Functionality</b></h3> |
|
<blockquote> |
|
<h4><b>CIM Operations over HTTP support</b></h4> |
|
<ol> |
|
<li>Class Operations (<span class="SpellE">getClass</span>, <span class="SpellE">deleteClass</span>, <span class="SpellE">modifyClass</span>, |
|
<span class="SpellE">enumerateClass</span>, <span class="SpellE">enumerateClassNames</span>)</li> |
|
<li>Qualifier Operations (getQualifier, setQualifier, |
|
deleteQualifier) </li> |
|
<li>Instance Operations (<span class="SpellE">getInstance</span>, <span class="SpellE">deleteInstance</span>, <span class="SpellE">modifyInstance</span>, |
|
<span class="SpellE">enumerateInstance</span>, <span class="SpellE">enumerateInstanceNames</span>, <span class="SpellE">getProperty</span>, |
|
<span class="SpellE">setProperty</span>)</li> |
|
<li>Association Operations (references, <span class="SpellE">referencenames</span>, |
|
<span class="SpellE">associators</span>, <span class="SpellE">associatornames)</span></li> |
|
<li>Methods Operations (invokeMethod)</li> |
|
<li>Query operation - Support for ExecQuery was added in 2.4 with |
|
WQL as query language and is defined in PEP 119. This feature is |
|
considered at alpha quality because it has only been contributor |
|
tested. Additional tests have been added in 2.5 for ExecQuery. Pegasus |
|
today does not support the ExecuteQuery operation defined as the Query |
|
operation for CQL.<br> |
|
</li> |
|
</ol> |
|
</blockquote> |
|
</div> | </div> |
<blockquote> |
|
<h4><b>Indication Processing</b></h4> |
|
<ol> |
|
<li>Process indications - Process indications are operational in |
|
the |
|
Server. This includes support |
|
for subscriptions, filters, and indication handlers, the provider API |
|
for |
|
indications and the CIMXML indication handler.</li> |
|
<li>Lifecycle indications - With the support for embedded objects, |
|
lifecycle indications (ie. those |
|
classes of indications derived from CIM_ClassIndication and |
|
CIM_InstIndication) can now be created. Pegasus 2.5 provides some |
|
enablement for the generation of lifecycle indications. For more |
|
details, refer to |
|
<src/Unsupported/LifecycleIndicationProvider/readme.LifecycleIndications.htm>.</li> |
|
</ol> |
|
<h4><b>Query Language</b></h4> |
|
<p>Pegasus includes the WQL query language which is implemented and |
|
used for filters and in version 2.4 for execQuery. <br> |
|
</p> |
|
<p>CQL Stage 1 has been added for Pegasus 2.5. PEPs 138, 193, 205 |
|
combine to describe the CQL functionality supported.</p> |
|
<h4>Object Normalization</h4> |
|
The Object Normalizer is an entity introduced in Pegasus 2.4 that |
|
ensures |
|
objects delivered from providers are complete and accurate. Two major |
|
issues were identified with the initial implementation: 1) the Object |
|
Normalizer droped instances it considered bad, and 2) the Object |
|
Normalizer code slowed performance. These issues are now addressed by |
|
moving the Object Normalizer from the Dispatcher to the Response |
|
Handler (or equivalent) and optimizing the existing implementation. The |
|
move allows errors to be reported to the provider at the point of |
|
delivery and ensures that only a single copy is made to preserve the |
|
CIMOM/provider boundary.<br> |
|
<h4>Embedded Object Support</h4> |
|
Pegasus 2.5 provides embedded object support. The proposed solution |
|
is restricted to the following:<ul> |
|
<li>The only representation for embedded objects supported by this |
|
PEP is CIM-XML (i.e. id does not support MOF encoded objects). </li> |
|
<li>CIMObject is implemented as a new CIMValue type. This type will be used |
|
internally to represent embedded objects. When externalized (via |
|
CIM-XML) these objects will be converted to strings representing valid |
|
INSTANCE or CLASS elements, in accordance with the CIM Infrastructure |
|
Specification. Embedded instances will also carry the |
|
EmbeddedObject attribute with |
|
the value "object", as specified by CR Interop-00217.001. |
|
</li> |
|
</ul> |
|
<h3>Pegasus Repositories<br> |
|
</h3> |
|
<p class="MsoNormal"> </p> |
|
</blockquote> |
|
<div class="Section1"> | <div class="Section1"> |
<blockquote> |
<h2><span style="color: black;">OpenPegasus Functionality for this Release</span></h2> |
<h4><b>Schema Repository</b></h4> |
OpenPegasus overall status by release is defined by a <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature |
<p style="margin-top: 0pt; margin-bottom: 0pt;">By default, Pegasus uses an XML-based |
Status WEB Page</a> that is available on the OpenPegasus web site |
schema repository. A binary encoding option is also available for the repository.<span style="font-family: "times new roman";"><br> |
. That web page shows the Pegasus users and developers the status of |
</span></p> |
the various features found in OpenPegasus using a simple color coded key |
<div style="margin-left: 40px;"> |
(white, red, yellow, green) and a description of each feature. <br> |
<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> |
|
<h3><b><b>Security Considerations</b></b></h3> |
|
<font style="color: rgb(0, 0, 0);" color="RED">OpenPegasus 2.5 (and |
|
prior versions) contains several mechanisms to perform authorization, but none |
|
of these authorization checks are performed by default. |
|
By registering any provider which fails to do appropriate authorization |
|
checks, the consequences may include information leakage, data |
|
corruption, or unintended elevation of privilege. Please ensure that |
|
one of the following mechanisms is used to ensure appropriate access to |
|
your systems and data:</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> |
|
<font style="color: rgb(0, 0, 0);" color="RED">2. Restrict users with |
|
access to Pegasus to a specific authorized user group of trusted |
|
individuals.<br> |
|
3. Namespace authorization is also available.<br> |
|
<br> |
|
</font><span class="norm">For administration issues please refer to |
|
the SSL Admin Guide found in the source repository at: </span>pegasus/doc/PegasusSSLGuidelines.htm<br> |
|
<h4><b>Server Security</b></h4> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Basic Authentication |
|
(Note that Digest based security is not implemented in Pegasus)</li> |
|
<li class="MsoNormal" style="color: black;">PAM authentication <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">SSL support - SSL is |
|
implemented in Pegasus using the <span class="SpellE">OpenSSL</span> |
|
libraries. Pegasus does not provide the <span class="SpellE">OpenSSL</span> |
|
libraries but SSL can be used on any platform supported by <span class="SpellE">OpenSSL</span>. . This release of Pegasus was tested |
|
with multiple versions of OpenSSL versions |
|
0.9.7 and 0.9.8. Effective with Pegasus 2.5.1 the Open SSL version |
|
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> |
|
for <span class="SpellE">OpenSSL</span> release information<o:p>.</o:p></li> |
|
<li class="MsoNormal" style="color: black;">SSL levels - <font style="color: rgb(0, 0, 0);">SSLv3 |
|
and TLSv1 by default. SSLv2 is |
|
disabled by default and only enabled by a compile time option</font>. |
|
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> |
|
<h5><b style="">CMPI C interface Provider Manager<o:p></o:p></b></h5> |
|
<span style="font-family: "times new roman";">Pegasus 2.5 includes |
|
a provider manager for the CMPI C interfaces. This C interface is the |
|
result of a project by the IBM SBLIM team (see |
|
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> |
|
<h5>JMPI Java Interface Provider Manager</h5> |
|
<p>Pegasus |
|
includes a provider manager for Java |
|
provider interfaces based on the SNIA provider interface |
|
definitions. This provider manager is considered alpha |
|
quality and is not compiled in the default build. See |
|
readme.jmpi in the Pegasus source root directory for more information.</p> |
|
</blockquote> |
|
</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> |
|
<span class="norm"></span>Administrators should check the providers to |
|
ensure that the provider vendor |
|
has made use of available authorization capability.<br> |
|
</div> |
|
<p style="margin-left: 40px;">There are a number of providers available |
|
in the Pegasus release. |
|
This includes providers in the following categories:</p> |
|
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;"> |
|
<h4>Pegasus Internal Providers</h4> |
|
<p>Pegasus provides a set of "internal" providers that have direct |
|
access to the CIMOM for information and provide information and |
|
services to support the CIMOM and its administration. The |
|
providers in this category are mostly defined in the directory |
|
src/pegasus/controlproviders and include support for the following |
|
classes:</p> |
|
<ul> |
|
<li>DMTF Interop classes including __Namespace, <span class="SpellE">CIM_Namespace</span>, <span class="SpellE">CIM_ObjectManager</span>, |
|
<span class="SpellE">CIM_CommunicationMechanism, and |
|
CIMOMStatistics.</span></li> |
|
</ul> |
|
<h4><span class="SpellE">CMPI Remote Providers</span></h4> |
|
<span class="SpellE">Pegasus includes an support for |
|
running CMPI providers to be run on remote systems without the need for |
|
an extra CIMOM. It uses a special proxying provider to relay requests |
|
to a remote location using so-called communication layers. The remote |
|
side has to start a CMPIRDaemon process, which accepts remote requests |
|
and passes them on to CMPI style providers.</span><h3> |
|
<b>Generic Providers</b></h3> |
|
<p>These are providers that support multiple pegauss platforms and include the Generic <span class="SpellE">OperatingSystem</span> provider. See |
|
the |
|
directory <span class="SpellE">src</span>/Providers/generic.</p> |
|
<h4><b>Test/Sample Providers</b></h4> |
|
<p>See the directories <span class="SpellE">src/Providers/TestProviders</span> |
|
and <span class="SpellE">src</span>/Providers/sample for more |
|
information about test and |
|
sample providers.</p> |
|
<h4><b>Managed System Providers</b></h4> |
|
<p><span class="SpellE">ComputerSystem</span>, <span class="SpellE">DNSAdmin</span>, |
|
<span class="SpellE">DNSService</span>, Operating System, Process, |
|
Processor. For |
|
more information on these providers see the documentation for each |
|
provider in |
|
the directory <span class="SpellE">src/Providers/ManagedSystem</span></p> |
|
<h4><span class="SpellE">Server Statistics 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 class="MsoNormal">Pegasus includes 3 separate Indication Listeners.</p> |
|
<h3>Embedded CIMListener</h3> |
|
<p class="MsoNormal">This listener is embedded in the CIMServer and allows the |
|
server to accept indications and route them.</p> |
|
<h3>Standalone Static CIMListener</h3> |
|
<p class="MsoNormal">This is a standalone listener that combines the functions |
|
of listener and consumer into a single element.</p> |
|
<h3>Standalone Dynamic Listener</h3> |
|
<p class="MsoNormal"> |
|
<font style="color: rgb(0, 0, 0);" color="#330099">Pegasus 2.5 |
|
includes a new standalone dynamic listener that is separate |
|
from the current standalone CIMListener and the ExportServer listener |
|
in the CIM server. |
|
The use model that this listener fits is the following: |
|
</font></p> |
|
<font style="color: rgb(0, 0, 0);" color="#330099"> </font><ul> |
|
<font style="color: rgb(0, 0, 0);" color="#330099"> <li> The listener may be packaged as |
|
part of the CIMOM or it may be packaged independently as part of |
|
another application. </li> |
|
<li> Consumers |
|
are developed independently of the listener and may be shipped with the |
|
listener or added to an installed listener at a future time. </li> |
|
</font></ul> |
|
<font style="color: rgb(0, 0, 0);" color="#330099"> </font> |
|
<p></p> |
|
<p><span style="color: rgb(0, 0, 0);"> </span><font color="#330099"><span style="color: rgb(0, 0, 0);">This |
|
dynamic listener provides a solution for the above use model. It |
|
is essentially a lightweight, pluggable listener that |
|
provides a small set of management features. The DynamicListener can be |
|
run inside a daemon or a service. It is easily configurable and |
|
bypasses traditional registration procedures. See |
|
<a href="http://www.openpegasus.org/pp/protected/upreviews/20/1303/PEP195_CIMListenerEnhancementsv1_6.htm" 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 |
|
details.</span> </font></p> |
|
</blockquote> |
|
<h3><span class="SpellE"><b>CIM_Schema</b></span></h3> |
|
<blockquote> |
|
<p>The default <span class="SpellE">CIM_Schema</span> loaded with this |
|
release is |
|
the DMTF CIM 2.9, final release. In addition, Pegasus includes |
|
a number of |
|
local classes defined for Pegasus. These are defined in the pegasus/Schemas |
|
directory. <span style=""></span>There are also a |
|
number of older schema available in the CVS. Further, the CIM 2.10 and CIM |
|
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> |
|
<h3><b>Pegasus CIM Server <span class="SpellE">Administration</span></b></h3> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">cimuser</span></b> |
|
- Manage Pegasus CIM Server Users.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">cimconfig</span></b> |
|
- 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> | <br> |
<span style="font-weight: bold;">Server admin |
OpenPegasus 2.14.0 is a major release, extending the previous Pegasus |
note:</span><br> |
release in selected areas as described in these release notes. <br> |
<div style="margin-left: 40px;">The default behavior for determining |
<br> |
the CIM server's HTTP and HTTPS ports has changed. In previous |
OpenPegasus 2.14.1 is a minor release that corrects an issue where the |
releases, any value in /etc/services would override a port explicitly |
certificate used for testing OpenPegasus expired shortly after the |
specified in the configuration. The new order for determining the |
release of 2.14.0. There<br> |
CIM server's HTTP and HTTPS ports is as follows:<br> |
are NO functional changes. To see differences between this version and |
1) An explicitly specified port value takes precedence over any other |
the either previous or later versions please review the bugs for both |
values.<br> |
2.14.0 and<br> |
</div> |
2.14.1.<br> |
<div style="margin-left: 40px;">2) If no port is specified, the value |
<br> |
in /etc/services is used.<br> |
NOTE: OpenPegasus releases are categorized as follows:<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 |
<li>First number of version changes (ex. 2.x.x to 3.0.0) - Major |
indication delivery.</font><br> |
release includes major functionality change and incompatible |
</li> |
behavior changes and/or incompatible public API changes, <br> |
<li><font size="2">New CIM Listener |
</li> |
keeps all consumer libraries in memory for the duration of its |
<li>Second number changes (ex 2.12.0 2.14.0) - Minor Release and |
execution.</font><br> |
includes new functionality but maintains behavior and public API |
|
compatibility, <br> |
</li> | </li> |
<li><font size="2">New CIM Listener |
<li>3rd number changes (2.14.0 to 2.14.1) - Revision(also called point |
is now pluggable.</font></li> |
release) release and only includes bug fixes.</li> |
<li><font size="2">New CIM Listener |
|
now provides reliable indication delivery.</font></li> |
|
</ul> | </ul> |
</ul> |
<br> |
<li class="MsoNormal" style="color: black;"><span lang="da">SLP |
<u><b>ALL</b></u> changes for each release are documented in the |
Client (User Agent) APIs which are extensions to the Client APIs</span></li> |
OpenPegasus bug data base by tagging each bug(keyword field of bug). |
</ol> |
No change to Pegasus is committed with out this tag on the bug. Changes |
<p class="MsoNormal"><span style="color: black;"><o:p> </o:p></span></p> |
for this minor release are tagged 2.14.0_APPROVED. All changes for |
<p class="MsoNormal"><span style="color: black;">The APIs are |
this minor release can be viewed through this link to the |
documented in |
OpenPegasus bugzilla <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.14.0_APPROVED"> |
their respective header files and in HTML documentation based on |
Pegasus 2.14.0_APPROVED bug list. Bugs. </a>Bugs marked as |
the information |
enhancements can be reviewed through the this <a href="http://bugzilla.openpegasus.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=CIM+Server+Core&product=CIMClient+Application&product=CIMClient+DefaultCPlusPlus&product=CIMClient+Java-SNIA&product=CIMConsumer+DefaultCPlusPlus&product=CIMIndicationHandler&product=CIMListener+Dynamic&product=CIMListener+Standalone&product=CIMProvider+CMPI&product=CIMProvider+CMPIRemote&product=CIMProvider+DefaultCPlusPlus&product=CIMProvider+Instrumentation&product=CIMProvider+JMPI&product=CIMSchema&product=CIMServer+Administration&product=CIMServer+Administration+Command&product=CIMServer+Administration+Profiles&product=CIMServer+ProviderManagement&product=CIMServer+Repository&product=CIMServer+SLP&product=OpenPegasus+Build+System&product=OpenPegasus+Documentation&product=OpenPegasus+Security+Defects&product=OpenPegasusProject+Bugzilla&product=OpenPegasusProject+CVS&product=OpenPegasusProject+Website&product=PegasusCIMOM&product=PegasusGeneral&product=RPM+CIMServer&product=TestProduct&product=Unsupported&product=WMI+Mapper&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.14.0_APPROVED&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_severity&type0-0-0=equals&value0-0-0=enhancement">link |
in the header files extracted with the doc++ tool will be available on |
to OpenPegasus bugzilla 2.14.0 enhancement bugs</a> . Bugs fixed |
the |
for subsequent revision releases (ex. 2.14.2) would also be viewed through |
OpenPegasus web site.<br> |
corresponding Bugzilla tags for each revisions (ex 2.14.1_APPROVED).<br> |
</span></p> |
<br> |
<p class="MsoNormal"><b>WMI <span class="SpellE">Mapper</span></b></p> |
The major areas of development including both enhancements and bug fixes |
<p>The WBEM to WMI <span class="SpellE">Mapper</span> provides a way |
for this release were as follows. Note that the bugs listed |
to access |
represent only those features incorporated in bugs without PEPS that are |
WMI data from Windows platform systems. It converts incoming XML/CIM |
considered enhancements, not all bugs incorporated in the release. For |
requests |
more information access the PEP/BUG for each change defined below:<br> |
to Microsoft WMI requests, executes the requests, converts the results |
<br> |
to |
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font style="font-weight: bold;" size="4"> Table of Major |
XML/CIM and returns the results to the client. WMI <span class="SpellE">Mapper</span> |
Changes this Release. Review Bugzilla 2.14.0 |
receives an HTTP message containing the XML/CIM request. It decodes the |
Enhancements and approved(above) for a complete list<br> |
XML |
</font></p> |
message and extracts from the HTTP message header the user credentials |
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="82%"> |
provided |
<tbody> |
on the connection (username and password). The WMI <span class="SpellE">Mapper</span> |
<tr align="center"> |
authenticates these credentials, verifying if the provided credentials |
<th bgcolor="#00ffff">BUG #</th> |
|
<th bgcolor="#00ffff">Description of Change</th> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9601">9601</a></td> |
|
<td>Support only TLS V1.2 Protocol for Security Compliance<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9676">9676</a>, <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9819">9819</a><br> |
|
</td> |
|
<td>Support DMTF defined Pull Operations (per DMTF |
|
specification DSP 0200 and 0201). This is a major extension to |
|
OpenPegasus and implements all of the DMTF defined pull operations with |
|
NO changes to providers. This includes extentions to both the server |
|
and client code as well as new operations implemented in cimcli to |
|
allow execution of pull operations and pull operations with FQL.<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9721">9721</a><br> |
|
</td> |
|
<td>Fix issue causing failures when cmpi returned |
|
instances that do not have a class. This was causing problems with the |
|
Jobs profiles which specifically return information for which there is |
|
no class.<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9724">9724</a><br> |
|
</td> |
|
<td>Dynamic disable of the reliable Indication feature<br> |
|
</td> |
|
|
|
</tr> |
|
|
|
<tr> |
|
<td style="vertical-align: top; text-align: center;">9812<br> |
|
</td> |
|
<td style="vertical-align: top;">FootPrint Reduction<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top; text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9831">9831</a><br> |
|
</td> |
|
<td style="vertical-align: top;">Generate mini-CA and signed certificate instead of self-signed certificates</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9832">9832</a><br> |
|
</td> |
|
<td>Include cimcli in release packages<br> |
|
</td> |
|
|
|
</tr> |
|
|
|
<tr> |
|
<td style="vertical-align: top; text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9883">9883</a><br> |
|
</td> |
|
<td style="vertical-align: top;">support HTTP Negotiate Authentication in OpenPegasus |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9892">9892</a><br> |
|
</td> |
|
<td>Reduce overhead of use of PAM by use of a |
|
SessionCookie. This also introduces a new runtime configuration |
|
parameter to control the session timeout<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9828">9928</a><br> |
|
</td> |
|
<td>Incorporate FQL (Filter Query Language) support for the pull operations (Experimental)<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9880">9880</a>,<a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9778">9778</a><br> |
|
</td> |
|
<td>Several minor extension to the APIs (ex. extend String class methods)<br> |
|
</td> |
|
|
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9737">9737</a><br> |
|
</td> |
|
<td align="left" width="75%">Improve CLANG compiler support <br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9219">9219</a><br> |
|
</td> |
|
<td>Initial CIMRS and Web Admin support (This is Experimental and the CIMRS function will be modified for CIMRS V2 specification)<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9853">9853</a><br> |
|
</td> |
|
<td>Correct old error in the Memory Resident |
|
Repository logic. This logic did not work in several previous versions |
|
because of the issues documented in this bug.<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9926">9926</a><br> |
|
</td> |
|
<td>Update default CIM Schema to CIM 2.41<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td>Add scripts for load testing of OpenPegasus (see the directory src/Unsupported/Scripts/UinxLoadTests)<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=10012">10012</a><br> |
|
</td> |
|
<td align="left" width="75%">Fix issue with the configuration parameters for numberOfTraceFiles and traceFileSizeKbytes. |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" width="7%"><br> |
|
</td> |
|
<td align="left" width="75%"><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
</tbody> |
|
</table> |
|
<br> |
|
The status of several components of Pegasus functionality change status |
|
between Pegasus versions. <span class="norm"><a name="comtag_116">Features |
|
that |
have | have |
access to the desired WMI data. This is done because the WMI <span class="SpellE">Mapper</span> runs as a service, logged on using an |
changed status can be identified by a change in color from the |
account with |
previous release to this release</a></span> on the <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature |
administrative rights (which has all access to WMI data). Because of |
Status WEB Page</a>.<br> |
this, the |
<br> |
WMI <span class="SpellE">Mapper</span> impersonates the user |
<h2><a name="Notes_on_Specific_OpenPegasus"></a>Notes on Specific |
credentials provided |
OpenPegasus Functionality Changes</h2> |
on the HTTP message to ensure that the calling user has rights to |
This section documents specific issues that the OpenPegasus team feels are |
browse WMI |
important to OpenPegasus users with the current release (and possibly |
data. Hence, ALL requests made to the WMI <span class="SpellE">Mapper</span> |
older releases).<br> |
MUST |
<br> |
contain user credentials.<br> |
<h3>Add new RunTime Variables to control trace file size and Rotation(OpenPegasus |
</p> |
2.13.0)(bug 9550)</h3> |
<ol> |
As of OpenPegasus 2.14.0, several new runtime variables have been added that can be manipulated with the <span style="font-family: Courier New,Courier,monospace;">cimconfig</span> utility:<br> |
</ol> |
<br> |
<h2>Relationship to |
* <span style="font-weight: bold;">pullOperationsMaxObjectCount </span>- |
CIM/WBEM Standards</h2> |
Defines the maximum allowed value of the maxObjectCount argument on |
<p>Pegasus was designed and implemented to comply with the DMTF |
open and pull operation requests which defines the maximum number of |
specifications The following table defines the level of the DMTF specifications |
instances or paths that will be returned in a single open or pull |
to which this version of Pegasus conforms today.</p> |
response. Requests that have a value higher than this configuration |
<table id="AutoNumber1" border="1" cellspacing="1" width="100%"> |
parameter will be rejected. The default is10000. This may be set to any |
|
value between 1 and 10000. <br> |
|
* <span style="font-weight: bold;">pullOperationsDefaultTimeout</span> |
|
- Defines the default timeout in seconds between the time a pull open |
|
response is sent by the server and a subsequent pull or close response |
|
received from the client if the value is not set by the client in the |
|
request. This can be set to any value between 1 and 90 seconds. |
|
Default=30<br> |
|
* <span style="font-weight: bold;">pullOperationsMaxTimeout</span> |
|
- Defines the maximum allowable value for the maxTimeout argument that |
|
is part of the pull open... (openEnumerationInstances, etc) requests. |
|
Any value higher than the value set in this configuration parameter |
|
will cause the request to be rejected by the CIMServer. The default=90 |
|
seconds. TODO - Explain more on all of these above<br> |
|
* <span style="font-weight: bold;">httpSessionTimeout </span>- |
|
Allows using a cookie to temporarily bypass the PAM authentication in |
|
favor of the cookie provided by the server during a single session.<br> |
|
This is a performance enhancement. If this variable is set to |
|
zero (default) the cookie bypass is disabled, the server will not send |
|
nor accept the id cookie. If set to<br> |
|
an integer, a client session will maintain the cookie for the number of |
|
seconds defined by the value of this variable. Enabled with a build |
|
parameter PEGASUS_ENABLE_SESSION_COOKIES.<br> |
|
* <span style="font-weight: bold;">sslBackwardCompatibility</span> |
|
- Limits OpenPegasus support to TLS 1.2/OpenSSL1.01. Can be set to |
|
allow backward compatibility with older versions of TLS/OpenSSL. <br> |
|
<br> |
|
The following sections describe in more detail some of the more |
|
significatn changes in this release as well as carrying forward some of |
|
the same information for the last release to be sure users are aware |
|
what these changes affect.<br> |
|
<br> |
|
<h3>DMTF Pull Client operations and FQL Query Language (OpenPegasus 2.14.0)</h3>As |
|
of DMTF DSP0200 version 1.4, new client operations (generally named the |
|
pull operations have been part of the CIM/XML protocol). This consists<br> |
|
of a set of new operations (open..., pull..., close) that allow getting |
|
enumerations, associations, references (and their corresponding name |
|
operations) as a sequence<br> |
|
of operations (an enumeration sequence) rather than a single monolithic operation.<br> |
|
<br> |
|
This will provider several advantages including:<br> |
|
1. Better control of client memory since the client can determine the size of each response.<br> |
|
2. Clearly separates the return of errors from data.<br> |
|
<br> |
|
Pegasus 2.14 supports all of these operations in both in the CIM/XML |
|
client and the server. For more information on the implementation and |
|
use of<br> |
|
these operation see the following documents:<br> |
|
<br> |
|
1. OpenPegasus <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:workgroups:pulloperationsupportworkgroup:pull_operation_support_work_group">Wiki page</a> for this project.<br> |
|
2. PEP documenting the Pull operations and FQL<br> |
|
<br> |
|
<h3>HTTP Sessions(OpenPegasus 2.14.0)</h3>Allows using a cookie to |
|
enhance performance of PAM. This function is enabled with the |
|
build varaible PEGASUS_ENABLE_SESSION_COOKIES. When<br> |
|
the option is enabled, the OpenPegasus CIM server will |
|
use HTTP cookies for session management (RFC 6265). |
|
<br> |
|
|
|
After a successful client authentication the client is given a cookie. The |
|
client is then not asked for re-authentication as long as it provides the |
|
same cookie in all subsequent requests and until the session expires. Session |
|
expiry is configurable using httpSessionTimeout configuration option. |
|
<br> |
|
|
|
Nothing changes for clients that do not support HTTP cookies (RFC 6465) - |
|
their requests are authenticated as usual, either using Basic or Negotiate |
|
authentication mechanisms. |
|
<br> |
|
<br> |
|
The timeout for a session is determined by the runtime parameter <span style="font-weight: bold;">httpSessionTimeout</span>. If this runtime parameter is set to zero the HTTP cookies option is disabled.<br> |
|
<br> |
|
This option has proven to represent a significant improvement in performance over using PAM for every client operation.<span style="font-family: Arial;"><span style="font-weight: bold;"> <br> |
|
</span></span><h3>WEBAdmin (OpenPegasus 2.14.0)</h3>OpenPegasus has |
|
included on an experimental basis a web server that acts as an |
|
adminstration tool to replace the command line tools. This option |
|
presents the<br> |
|
same information as the major command line tools as web pages so that |
|
parameters can be modified without using the command line tools. |
|
It is compiled by<br> |
|
default and may be disabled with the build option |
|
PEGASUS_ENABLE_PROTOCOL_WEB=false. See the file readme.webadmin in the |
|
OpenPegasus<br> |
|
source tree for more detailed information on using WEBAdmin.<br> |
|
<br> |
|
Note: This option is considered experimental for 2.14<br> |
|
<br> |
|
<h3>Using GCC 4.7 Compiler on Linux OS (OpenPegasus 2.13.0)<br> |
|
</h3> |
|
As of 2.14.0, OpenPegasus has been updated to replace the custom atomic |
|
operations with GCC built-in atomic operations if GCC version 4.7 or |
|
greater is used as the compiler. It is recommended that if possible |
|
this version of the GCC compiler be used since the change provides |
|
significant performance improvements.<br> |
|
<h2> </h2> |
|
<h3>OpenPegasus and OpenSLP V 2.0 (OpenPegasus 2.13.0)</h3> |
|
As of 2.13.0, OpenPegasus slp fully supports IPV6 and has been |
|
tested with OpenSLP 2.0 (Recently released by <a href="http://openslp.org">OpenSlp.org</a>)<br> |
|
<br> |
|
While testing OpenPegasus with OpenSLP 2.0 the OpenPegasus team found two |
|
issues with this version of OpenSLP. The patches documented below |
|
allow this version of OpenSLP to work with OpenPegasus<br> |
|
<br> |
|
1) SLPReg used TCP connection previously, but it now uses UDP. Therefore, |
|
a BUFFER_OVERFLOW exception occurs. This is because UDP cannot |
|
handle attribute size greater than network MTU size. In such cases, |
|
according to the specification, OpenSLP should automatically switch to |
|
TCP. Since this has not been implemented in OpenSlp 2.0, the |
|
workaround used by OpenPegasus to force use of TCP may be found at <a title="http://sourceforge.net/p/openslp/bugs/139/" href="http://sourceforge.net/p/openslp/bugs/139/">http://sourceforge.net/p/openslp/bugs/139/</a>.<br> |
|
<br> |
|
2) On Windows, slpd service fails to start when IPV6 is enabled and throws |
|
the error message "Error 1067: the process terminated unexpectedly". More |
|
details and the fix for this issue are in the bug <a href="http://sourceforge.net/p/openslp/bugs/140/">http://sourceforge.net/p/openslp/bugs/140/</a>.<br> |
|
<h3>Interop namespace name (OpenPegasus 2.13.0)</h3> |
|
Effective with the release of OpenPegasus 2.13 the "interop" |
|
namespace support for existing or |
|
older repositories which used |
|
"root/PG_InterOp" has been added via a new option in the "reupgrade" |
|
utility. Users with existing repositories may use this option to migrate |
|
the repository from "root/PG_InterOp" to |
|
"interop" namespace. See <span class="bz_closed"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9414" title="RESOLVED FIXED - enhance repupgrade to support "interop" namespace">bug |
|
9414</a></span> (PEP304) for |
|
details.<br> |
|
<br> |
|
For this to work, the build option "PEGASUS_INTEROP_NAMESPACE" has |
|
to be |
|
set to "interop". Only then will the "-i" option in repupgrade be enabled. |
|
Once the repository is upgraded with "-i" , the namespace |
|
"root/PG_InterOp" |
|
will cease to exsist. Clients using "root/PG_InterOp" must now use |
|
"interop".<br> |
|
<br> |
|
Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable to |
|
define "root/PG_InterOp" as the name for the OpenPegasus namespace with no |
|
defined way to change this variable. Note that an unsupported method |
|
involving editing one file and rebuilding OpenPegasus was defined as a |
|
workaround in the <a href="file:///home/kschopmeyer/dev/pgogbug9611releasenotes/pegasus/%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus |
|
wiki faq</a>s. <br> |
|
<br> |
|
However, since the definition of a standard name for this namespace in |
|
DMTF and SNIA specifications ("interop" or "root/interop" with "interop" |
|
being the preferred alternative) the use of "root/PG_InterOp" has |
|
become an issue. Support for forward-compatibility is a fundamental design |
|
principle for the OpenPegasus project. As a community, our goal is for |
|
well-behaved OpenPegasus providers or clients, using only the externally |
|
defined OpenPegasus interface, to continue to work with each version |
|
upgrade of OpenPegasus.<br> |
|
<br> |
|
Effective OpenPegasus 2.12.0 a new build variable was defined |
|
(PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus builder to define |
|
an alternate name for the Interop namespace to either "interop" or |
|
"root/interop" (ex. PEGASUS_INTEROP_NAMESPACE = interop). Once this |
|
build variable is defined and OpenPegasus compiled, the actual name of the |
|
interop namespace is what was defined in this varaible and all components |
|
of OpenPegasus use this as the interop namespace name include the complete |
|
OpenPegasus test suite. The only name for the interop namespace will |
|
be the name defined through this build variable. This is the logical |
|
approach for implementations starting a new repository.<br> |
|
<br> |
|
In order to supexport PEGASUS_CLIENT_TRACE=keyword:keywordport users with |
|
existing repositories, in 2.13.0, migration of existing repositories |
|
was integrated into the "repupgrade" utility to allow existing OpenPegasus |
|
environments to smoothly move the server from use of the old name |
|
for the interop namespace "root/PG_InterOp" to |
|
the prefered name "interop".<br> |
|
<br> |
|
<span style="font-weight: bold;">NOTE:</span> If the interop namespace |
|
name is redefined with PEGASUS_INTEROP_NAMESPACE clients using the |
|
"root/PG_InterOp" namespace will not connect with the updated version of |
|
OpenPegasus. The OpenPegasus team searched for a solution to the issue |
|
supporting the old and new name at the same time and concluded that there |
|
were so many issues that it could not effectively be done.<br> |
|
<h3>Configure Script to Control OpenPegasus Builds (OpenPegasus |
|
2.13.0)(Bug 9592)</h3> |
|
OpenPegasus is moving from the use of environment variables to a configure |
|
script to control build. This is both to make it easier to define |
|
the build variables, etc. and to be more compatibile with the Linux/Unix |
|
standard build environment. However, because OpenPegasus must build |
|
on a number of platforms that do not support the full Linux/Unix |
|
configuration tool set, this is an OpenPegasus defined configure |
|
script. The first very experimental version is part of OpenPegasu |
|
2.13.0 but this version has a number of limitations (see the OpenPegasus |
|
Bugzilla) and will be expanded in the next versions of OpenPegasus.<br> |
|
<br> |
|
The goal is to replace the setting of most of the OpenPegasus build |
|
environment variable with options in the pegasus/configure script where |
|
those options are comatible with the Linux standard for defining configure |
|
options and those options control the entire build process including placement |
|
of output and choice of build options.<br> |
|
<h3>Tracing Client Requests and Responses(OpenPegasus2.13.0)</h3> |
|
<p><span style="color: rgb(0, 102, 0);"><span style="font-family: "Times New Roman";"><span style="font-weight: bold;"></span></span></span></p> |
|
<span style="font-family: "Times New Roman";">OpenPegasus has |
|
long contained a hidden build controlled function to allow tracing at |
|
the client through an environment variable |
|
(PEGASUS_CLIENT_TRACE_ON). In 2.13.0 this was a) make a permanent |
|
part of of the environment (Bug 9564) and the calling convention</span><br> |
|
<span style="font-family: "Times New Roman";">slightly changed |
|
to make it simpler to use. </span>The original format for the |
|
environment variable was:<br> |
|
<pre class="bz_comment_text" id="comment_text_1">export PEGASUS_CLIENT_TRACE=keyword:keyword<br>where the keyword was "con" | "log" | "both"<br>This was changed to:<br> keyword:keyword separately define Client input and output<br> keyword: Client Input only<br> :keyword Client Output Only<br> keyword Client Input and output defined by keyword</pre> |
|
so that the normal setup for a console output trace would be<br> |
|
<pre> export PEGASUS_CLIENT_TRACE=con</pre> |
|
<h3>Information on IPV6 Support and OpenPegasus(PEP 291)(OpenPegasus |
|
2.7.0)</h3> |
|
<b>NOTE:</b> This functionality was incorporated in OpenPegasus 2.7.0 but |
|
it was felt that the information below was worth repeating in subsequent |
|
Release Notes<br> |
|
<br> |
|
<font color="#000000">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><br> |
|
<br> |
|
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> |
|
<br> |
|
The following subsections provide some information on IPv6 support for the |
|
Linux and Windows platforms. Note that in the 2.6.1 release there is no |
|
automatic run-time detection of IPv6 support on a platform by OpenPegasus. |
|
If you build with PEGASUS_ENABLE_IPV6=true, your platform must support |
|
IPv6 or you will get a build failure (missing header files), a run-time |
|
bind() failure, or possibly some other failure. This applies to both the |
|
CIM Server and Listener components. For more information on IPv6 support |
|
for your specific platform, refer to the documentation for that platform.<br> |
|
<br> |
|
All OpenPegasus externals that support eitcompilerher a hostname or an IP |
|
address as input have been updated to allow an IPv6 address to be |
|
specified. If the required input is just an IP address (eg. no optional or |
|
required port number), then the IPv6 address must be specified without |
|
brackets. For example, the OpenPegasus osinfo client (which returns |
|
information about the OS running on a host system) takes separate host and |
|
port options. In this case a host with an IPv6-configured network |
|
interface would be specified as:<br> |
|
<br> |
|
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">osinfo -h 3ffe:1:2:1 -p 5988</font></big></div> |
|
<br> |
|
But the cimcli command, which takes an optional "location" option |
|
including an optional port number, requires the IPv6 address to be |
|
delimited with brackets, for example:<br> |
|
<br> |
|
<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns -l |
|
[3ffe:1:2:1]</big></div> |
|
<p>or</p> |
|
<div style="margin-left: 40px;"><big><span style="font-family: monospace;">cimcli |
|
ns -l [3ffe:1:2:1]:5989</span></big><br> |
|
</div> |
|
<br> |
|
For more information on specifying IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF |
|
RFC |
|
2373 - IP Version 6 Addressing Architecture</a> and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF |
|
RFC 2732 - Format for Literal IPv6 Addresses in URL's</a>.<br> |
|
<h4><font color="#000000">IPv6 on Linux</font></h4> |
|
Modern Linux distributions already contain IPv6-ready kernels, the IPv6 |
|
capability is generally compiled as a module, but it's possible that this |
|
module is not loaded automatically on startup.<br> |
|
<br> |
|
<span style="font-weight: bold;">Note: </span>you shouldn't use |
|
kernel series 2.2.x, because it's not IPv6-up-to-date anymore. Also the |
|
IPv6 support in series 2.4.x is no longer improved according to |
|
definitions in latest RFCs. It's recommend to use series 2.6.x now.<br> |
|
<br> |
|
To check whether your current running kernel supports IPv6, take a look |
|
into your /proc filesystem. The entry /proc/net/if_inet6 must exist. A |
|
short automated test looks like:<br> |
|
<br> |
|
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">test -f /proc/net/if_inet6 && echo "Running |
|
kernel is IPv6 ready"</font></big></div> |
|
<br> |
|
For more iSchema version default update to CIM 2.36nformation on enabling |
|
IPv6 in the Linux kernel and configuring network interfaces, refer to <a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux |
|
Documentation Project's IPv6 HOWTO</a>.<br> |
|
<br> |
|
<span style="font-weight: bold;">Warning</span>: There is currently an |
|
open issue with RedHat to address a problem that is seen intermittently on |
|
RHEL5 and SLES10 systems. This problem is described in <span style="color: rgb(153, 51, 153);"> |
|
<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
|
bug 6586</a> </span>and<span style="color: rgb(153, 51, 153);"> <a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat |
|
bug |
|
248052</a>, </span>and manifests itself as an intermittent IPv6 |
|
socket failure. You should be aware that OpenPegasus with IPv6 enabled may |
|
be significantly impacted in these environments.<br> |
|
<h4><font color="#000000">IPv6 on Windows</font></h4> |
|
<br> |
|
Microsoft provides supported IPv6 implementations for Windows Server 2003, |
|
Windows XP with Service Pack 1 (SP1), Windows XP with Service Pack 2 |
|
(SP2), and Windows CE .NET 4.1 and later.<br> |
|
<br> |
|
On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span> |
|
tool to install, uninstall, and query your IPv6 configuration. For |
|
example:<br> |
|
<br> |
|
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">ipv6 install<br> |
|
ipv6 if</font></big></div> |
|
<br> |
|
Windows Vista and Windows Server 2008 support an integrated IPv4 and IPv6 |
|
implementation known as the Next Generation TCP/IP stack. Note that the |
|
OpenPegasus IPv6 support has not yet been tested on Windows Vista or |
|
Windows Server 2008.<br> |
|
<br> |
|
For more information on installing, configuring, and using IPv6 on Windows |
|
platforms, refer to the document <a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"><font color="#000000">IPv6 for Microsoft Windows: Frequently Asked Questions</font></a>.<br> |
|
<br> |
|
<h4><font color="#000000">Testing OpenPegasus IPv6 support</font></h4> |
|
As part of the OpenPegasus automated tests, the TestClient, g11ntest, and |
|
IndicationStressTest test clients were modified to run tests using the |
|
IPv6 loopback address (::1) if PEGASUS_ENABLE_IPV6=true.<br> |
|
<br> |
|
You can also perform manual tests using the IPv6 loopback or a real |
|
IPv6-configured network interface. For example, using the IPv6 loopback on |
|
a system with OpenPegasus running on the WBEM standard http port of 5988:<br> |
|
<div style="margin-left: 40px;"><br> |
|
<big style="font-family: monospace;"> osinfo -h ::1</big></div> |
|
<h2><a name="Compatibility_Considerations_">OpenPegasus Compatibility |
|
Considerations</a></h2> |
|
Support for forward-compatibility is a fundamental design principle for |
|
the OpenPegasus project. As a community, our goal is for well-behaved |
|
OpenPegasus providers or clients, using only the externally defined |
|
OpenPegasus interface, to continue to work with a minor version upgrade of |
|
OpenPegasus. However, there are certain classes of errors (e.g., |
|
non-compliance with a standard that significantly affects |
|
interoperability) that may require the community to make potentially |
|
incompatible changes. The following table contains a list of defects/fixes |
|
that MAY impact, even well-behaved, OpenPegasus providers or clients when |
|
upgrading to this OpenPegasus release. <br> |
|
<br> |
|
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="80%"> |
|
<tbody> |
|
<tr align="center"> |
|
<th bgcolor="#00ffff" width="10%">Bugzilla #</th> |
|
<th bgcolor="#00ffff">Description</th> |
|
</tr> |
|
<tr align="center"> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8830">Bug |
|
8830</a></td> |
|
<td align="left">Starting |
|
with OpenPegasus 2.11.0 the requirement for providers (CMPI and C++) to |
|
filter properties from instances has been relieved. The server will do |
|
the filtering at the protocol adapter level. To avoid a negative impact |
|
on performance the CIMInstance::filter() and |
|
CMPIInstanceFT.setPropertyFilter() functions have been changed to a |
|
NOP. This may be a change in behavior for provider relying in some |
|
unknown way on the instance being filtered through these functions. To |
|
allow users to actually filter properties from an instance in a |
|
provider, a new function (CIMInstance::filterInstance()) will actually |
|
filter properties from an instance exactly as the CIMInstance::filter() |
|
did in previous versions of Pegasus. This is not required since the |
|
CIMServer will do the filtering but allows the provider to prefilter |
|
properties if it so desires, in particular where properties might be |
|
very large or there would be a significant number of properties.<br> |
|
</td> |
|
</tr> |
|
<tr align="center"> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9369">Bug |
|
9369</a><br> |
|
</td> |
|
<td align="left"><span style="font-weight: bold;">NOTE: This bug |
|
fixed in OpenPegasus 2.13.0. </span>Reregistering of an |
|
indication provider requires that the cimserver be restarted |
|
to send the enableIndication request to the providers. This issue |
|
has existed starting with OpenPegasus 2.10 to version 2.12. |
|
If the cimserver is not restarted the indication will not be |
|
enabled for the reregistered provider. </td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
<h2>OpenPegasus Relationship to CIM/WBEM Standards</h2> |
|
Pegasus was designed and implemented to comply with the DMTF CIM/WBEM |
|
specifications The following table defines the level of the DMTF |
|
specifications to which this version of Pegasus aims to conform today.<br> |
|
<br> |
|
<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.4, 26 August 2013<br> |
|
</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.4.0 16 January 2014<br> |
|
</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.36.0 Final ( default build Schema) </td> |
|
</tr> |
|
<tr> |
|
<td>DSP0226 - Web Services for Management<br> |
|
</td> |
|
<td>Version 1.1.1<br> |
|
</td> |
</tr> | </tr> |
|
<tr> |
|
<td>DSP0227 - WS-Management CIM Binding Specification<br> |
|
</td> |
|
<td>Version 1.2.0<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td>DSP0230 - WS-CIM Mapping Specification </td> |
|
<td>Version 1.1.0<br> |
|
</td> |
|
</tr><tr> |
|
<td style="vertical-align: top;">DSP0212 - Filter Query Language<br> |
|
</td> |
|
<td style="vertical-align: top;">Version 1.0.1, 22 August 2013<br> |
|
</td> |
|
</tr> |
|
|
</tbody> | </tbody> |
</table> | </table> |
<h2><b><span style="font-family: Times;"><a name="Supported Platforms">Supported |
<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIA SMI |
|
Profiles Supported</h2> |
|
<br> |
|
Today OpenPegasus includes support for several DMTF profiles including:<br> |
|
<ol> |
|
<li>DMTF ProfileRegistration Version DSP 1033, Version 1.0.0</li> |
|
<li>DMTF Indications DSP 1054, Version 1.1.0. Since this is effectively the same as the |
|
SNIA SMI Indication profile it also supports this profile. This |
|
profile is enabled by compiling OpenPegasus with the buld variable |
|
PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.<br> |
|
</li> |
|
<li>SNIA Profile Registration 1.0.0<br> |
|
</li> |
|
<li>SNIA Server 1.1.0 & 1.2.0<br> |
|
</li> |
|
</ol> |
|
<h2><a name="Conformance with DMTF Specifications">Conformance Exceptions |
|
to DMTF Specifications</a></h2> |
|
It is a major goal of the OpenPegasus project to both drive and utilize |
|
the DMTF CIM/WBEM specifications. However, today there are a number |
|
of known differences. As of this release, some of the differences |
|
include the following:<br> |
|
<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 really a deviation from the specifications since there is no |
|
specification or profile for provider registration today but is a |
|
different method of registration than many CIM Servers and means that |
|
the the provider qualifier is unused in Pegasus.</li> |
|
<li><b>Lifecycle Indications </b>-Today Pegasus supports process |
|
iPegasusndications 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> <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 Over HTTP Specification (DSP0200) and |
|
stated specifically that the client should NOT depend on the |
|
includeQualifiers parameter of the CIM/XML instance operations |
|
returning qualifiers. Some CIM Client implementations expect |
|
instances returned from the CIM Server to include the qualifiers |
|
defined in the class definition (such as KEY qualifiers on |
|
properties). Pegasus today expects the provider to |
|
complete the qualifiers on instances in accordance with the |
|
specification and generally the interpretation is that Pegasus |
|
applies class level qualifiers when the includeInstance parameter is |
|
supplied on instance operations. However, Pegasus today is |
|
inconsistent in the return of qualifiers so that the user should NOT |
|
depend on Pegasus accurately honoring the includeQualifier parameter |
|
for instance operations. In the future it is expected that |
|
Pegasus will deprecate the use of qualifiers on instance operations |
|
completely. When Pegasus uses object normalization, the |
|
normalizer does apply qualifiers to returned instances if the |
|
includeQualifiers operation parameter is set.</span></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><span style="font-weight: bold;">MultiRequest CIM/XML Option</span> |
|
- Pegasus does not support the DMTF defined MultiRequest |
|
Operation option (See DSP0200).<br> |
|
</li> |
|
<li><span style="font-weight: bold;">MOF Namespace Pragma</span> -The |
|
Pegasus compiler does not support the namespace pragma defined in DSP |
|
0004. Namespaces for the OpenPegasus repository are defined through |
|
arguments for the MOF Compiler<br> |
|
</li> |
|
<li><b>CIMOperation Trailer </b>- Pegasus implements chunking based on |
|
the DSP0200 1.2.0 preliminary spec. including the operation trailer |
|
defined in that specification Refer to bug <a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> |
|
for more details. This trailer was completely removed from the DSP0200 |
|
1.2 final specification as a non-compatible change so that if chunking |
|
is used Pegasus is returning a noncompliant response to enumerate type |
|
requests. </li> |
|
<li><span style="font-weight: bold;">Whitespace in XML value Element</span> |
|
- Pegasus trims the leading and trailing whitespace from XML value |
|
elements that are of the Type String. This behavior is |
|
documented in Pegasus bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8773">8773</a> |
|
and there is a patch available for users. However, since the |
|
change is considered a change to behavior this will not be patched |
|
until pegasus does a major version update. NOTE: There are some |
|
documented bugs in Pegasus such as this that the OpenPegasus team |
|
feels cannot be incorporated into the code until a major version |
|
update. These bugs are documented with the Bugzilla tag <big style="font-weight: bold;"><samp>"3.0_TARGET".</samp></big></li> |
|
<li><span style="font-weight: bold;">modifyInstance operation behavior |
|
in the Pegasus repository does not match the DMTF specification</span>. |
|
Under some conditions (ex. if no propertyList is supplied) it modifies |
|
all properties rather than just the properties supplied with the |
|
request thereby Nulling out existing values. See bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8752">8752</a> |
|
for more information.</li> |
|
<li><b>OpenPegasus Interop Namespace</b> |
|
- The default interop namespace name in OpenPegasus is |
|
"root/PG_Interop". In versions of OpenPegasus prior to 2.12.0 |
|
this could be changed during build by modifying a string definition in |
|
the code. Effective version 2.12.0 this has become a build option |
|
with the build configuraton environment variable |
|
PEGASUS_INTEROP_NAMESPACE = <name for this namespace> however, |
|
the default if built without this change is still "root/PG_InterOp". |
|
Effective with OpenPegasus 2.13.0 the reupgrade utility has been |
|
extended to allow existing repositories to be converted from the use of |
|
"root/PG_Interop" to "interop" (See discussion above). The |
|
default in the CVS source code is still "root/PG_InterOp".<br> |
|
</li> |
|
<li><b>OpenPegasus WSMAN protocol on windows does not handle NaN, INF, |
|
or -INF</b>However, t (bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>) |
|
- If requests or responses include properties or parameters with |
|
floating point property types (Real32 or Real64) with the special |
|
states NaN, INF, or -INF on a Windows platform, the input is not |
|
accepted because these special strings are not understood by the |
|
decoder on Windows.</li> |
|
<li><b>OpenPegasus outputs Nan, INF, -INF special values for Real32 and |
|
Real64 property and Parameter types for the CIM/XML protocol</b> - |
|
(bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9392">9392</a>). |
|
Today the DMTF Specification DSP0201 allows only numeric information |
|
in the format definition for this type and does not all the special |
|
strings Nan, etc. However, OpenPegasus actually outputs the special |
|
strings if that is what is defined in the internal values. |
|
OpenPegasus does not allow these special Strings on input however,</li> |
|
<li><b>OpenPegasus does not handle covered properties</b> - (bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">3571</a>) |
|
Covered properties (properties which have the same name in a |
|
superclass and subclass without overridding the property in the |
|
superclass) are not allowed in OpenPegasus. While the requirement for |
|
this functionality was added to DSP0004 subsequent to version 2.4, the |
|
general agreement is that the requirement itself is not supportable |
|
and particularly not with the existing OpenPegasus APIs. |
|
Further, the requirement is expected to be removed in the future (i.e |
|
CIM 3.0).</li> |
|
<li><span style="font-weight: bold;">FQL Query Language</span> |
|
(bug 9956) incorporated has some limitations with respect to the DMTF |
|
defined Query Language (does not support full regex defined in the |
|
specification and does not support embedded instance comparison).<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 |
|
|
Each OpenPegasus release lists as 'active' platforms those |
hardware/software platforms that have recognized ports for the Pegasus | hardware/software platforms that have recognized ports for the Pegasus |
code |
code base including a maintainer for the platform that will be willing to |
base including a maintainer for the platform that will be willing to |
regularly document issues and/or fix defects as the Pegasus code base is |
regularly document issues and/or fix defects as the Pegasus |
changed. Pegasus may be operable on other platforms (ex. Windows 98) |
code base is changed. |
but without a group to provide the role of test and maintenance, correct |
Pegasus may be operable on other platforms (ex. Windows 98) but without |
operation of Pegasus cannot be assured. In all cases, |
a group |
including the active platforms, it is the responsibility of the entity |
to provide the role of test and maintenance, correct operation of |
that packages and/or compiles OpenPegasus for shipment or deployment, to |
Pegasus cannot be |
read, and actively monitor the Pegasus Bugzilla database for a list of |
assured. In all cases, including the active platforms, it is the |
relevant defects that affect their platform. The platforms |
responsibility of the entity that packages and/or compiles OpenPegasus |
that are considered ported are shown in the two tables below. The |
for shipment or deployment, to read, and actively monitor the Pegasus |
first table represents platform for which testing is done on a regular |
bugzilla database for a list of relevant defects that affect their |
basis and reported to the Pegasus Nightly Build Test WEB Page. Those |
platform. The platforms that are considered 'active' for this |
platforms which have been ported but do not have test results that are |
Pegasus release are:<br> |
current at the time of the release are reported in the second table.<br> |
<span class="norm"></span><br> |
<br> |
</p> |
<b>Actively Supported Platforms (Nightly Tests Reported for this release)</b> |
<table class="MsoNormalTable" style="width: 302.25pt;" border="1" cellpadding="0" cellspacing="1" height="409" width="504"> |
<table class="MsoNormalTable" style="width: 90%;" border="1" 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: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-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 style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-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> | <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> |
|
PA_RISC and Itanium</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;"> <span style="color: black;"><font size="3">Linux |
<p class="MsoNormal"><span style="color: black;">Linux IA-32<o:p></o:p></span></p> |
IA-32</font></span></td> |
</td> |
<td style="padding: 0.75pt;"> <span class="SpellE"><span style="color: black;"><font size="3">gcc</font></span></span><span style="color: black;"><font size="3"> (versions 3.xx, 4.7) clang(The clang compiler usage |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" width="289"> |
is considered production effective OpenPegasus 2.13.0)</font><o:p></o:p></span></td> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"> |
|
(versions 2.9x and 3.xx)<o:p></o:p></span></p> |
|
</td> |
|
</tr> | </tr> |
<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;">Linux X86_64<o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="91" width="289"> |
<td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span style="color: black;" lang="NL">Microsoft |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"> (versions 3.xx, 4.7) </span><span style="color: black;"><font size="3">clang(The clang compiler usage is considered </font></span><span style="color: black;"><font size="3"><span style="color: black;"><font size="3">production effective OpenPegasus 2.13.0</font></span>)</font></span></p> |
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> |
</tr> | </tr> |
<tr> | <tr> |
<td style="padding: 0.75pt; width: 126.75pt;" height="69" width="211"> |
<td style="vertical-align: top;"><font size="3">z/OS V1.7 and up</font></td> |
<p class="MsoNormal"><span style="color: black;">Windows XP<o:p>, Windows |
<td style="vertical-align: top;"><font size="3">XL C/C++ from z/OS |
2003</o:p></span></p> |
Version 1.7 and up</font></td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
|
|
<p align="center"><b>Platforms not Actively supported for this release (No |
|
current Nightly Build Test Results)</b></p> |
|
<table class="MsoNormalTable" style="width: 90%;" id="table2" border="1" cellpadding="0" cellspacing="1"> |
|
<tbody> |
|
<tr style=""> |
|
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-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> |
<td style="padding: 0.75pt; width: 173.25pt;" height="69" width="289"> |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 75%;" height="26"> |
<p class="MsoNormal"><span style="color: black;" lang="NL">Microsoft |
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span style="color: black;"><o:p></o:p></span></p> |
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> |
|
<td style="padding: 0.75pt;"> <font size="3">Windows XP, Windows |
|
Vista, Windows 7, Windows Server 2008</font> </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
|
Compilers 2003 - 2010.. Note: Visual C++ Ver. 6 no longer being |
|
regular tested.Note that today there are some open issues with |
|
the Windows.</font> </td> |
|
</tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="43" width="211"> <font size="3">MacOS version 10.2 and higher</font></td> |
<td style="padding: 0.75pt;"> <font size="3">MacOS version 10.3 and |
<td style="padding: 0.75pt; width: 173.25pt;" height="43" width="289"> <font size="3">gcc 3.3</font></td> |
higher</font></td> |
|
<td style="padding: 0.75pt;"> <font size="3">gcc 4.01</font></td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big>HP OpenVMS Alpha<br> |
<td style="vertical-align: top;"><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris |
</big></td> |
8</span></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;"><big>GNU 2.95.3, Sun CC |
Alpha and above</font></big> </td> |
compiler V 5.8. Note that the latest thread patch (108993) may |
|
be required. (see Pegasus bug 4632)</big><br> |
|
</td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><span class="norm"></span><font style="color: rgb(0, 0, 0);"> HP OpenVMS IA64</font></big></td> |
<td style="vertical-align: top;"><span class="norm"></span><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9</span></font></big></td> |
<td style="vertical-align: top;"><span class="norm"></span><big><font style="color: rgb(0, 0, 0);">HP C++ V7.1-011 on OpenVMS IA64 and above</font></big> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun WorkShop |
|
6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 8<br> |
<td><big>HP OpenVMS 8.3 or later Alpha</big></td> |
</span></font></big></td> |
<td><big><font style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span style="color: rgb(153, 51, 153);">7.3-009 or later required</span> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun CC |
for OpenVMS Alpha</font></big></td> |
compiler V 5.8. Note that the latest thread patch (108993) may be |
|
required. (see Pegasus bug 4632)</big><br> |
|
</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><big><font style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later |
</span></font></font></big></td> |
IA64</font></big></td> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun WorkShop 6 |
<td><big><font style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 |
update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
or later required</font><font style="color: rgb(0, 0, 0);"> on |
|
OpenVMS IA64</font></big></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">Windows 2000</span></p> |
</td> | </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
|
Ver. 6 and Microsoft .Net compiler version. Works on |
|
VC .NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being |
|
regularly tested.</font></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;"> <font size="3">Windows 2003</font> </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
|
Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++ |
|
Ver. 6 no longer being regular tested. </font> </td> |
|
</tr> |
|
<tr> |
|
<td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td> |
|
<td><big>CC Compiler Sun Studio 5.11</big></td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
|
<h3><b>Platform patches</b> </h3> |
<br> | <br> |
<b>Platform patches</b><p style="margin-top: 0pt; margin-bottom: 0pt;"> |
<font style="color: rgb(0, 0, 0);">The following is a list known of |
<font style="color: rgb(0, 0, 0);">The following is a list of platform |
platform patches Pegasus requires.</font><br> |
patches Pegasus requires.<br> |
|
</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 |
<li> <font style="color: rgb(0, 0, 0);">RHAS 2.1 needs the update to |
through a set of Pegasus Provider registration classes rather than |
fix Red Hat Bugzilla 98815.</font><br> |
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> |
|
<p class="MsoNormal"> <b>CIM MOF compiler function for |
|
instance aliasing</b> - The Pegasus MOF compiler does not today support |
|
this function. This function is planned for a future version.</p> |
|
</li> |
|
<li> |
|
<p class="MsoNormal"><b> MultiRequest Oprations</b> - Pegasus |
|
does not support the DMTF defined MultiRequest Operation option.</p> |
|
</li> |
|
<li> |
|
<p class="MsoNormal"><b>MOFCompiler namespace pragma</b> - The |
|
Pegasus compiler does not support the namespace pragma.</p> |
|
</li> |
|
</ol> |
|
<h2><a name="Changes in This Release">Changes in This Release</a></h2> |
|
<p>The development and release of each version of Pegasus is defined |
|
and |
|
controlled through Pegasus PEP documents. PEP 180 is the |
|
controlling document for Pegasus 2.5.0 and PEP 239 is the controlling |
|
document for this release. These PEPs list the original set of changes proposed and the |
|
status of |
|
each of those changes. Note that not all of the originally defined |
|
functionality was completed for this release.</p> |
|
<p>In general, the areas of development for 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> |
<li class="MsoNormal" style="color: black;"> |
<li> RHEL 4.4 multithreading bug in getpwuid-r could cause a CIM |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Refactoring of |
Server failure (Bugzilla 6232). This is fixed in RHEL 4.5<br> |
Object Normalizer function to improve performance. </p> |
|
</li> | </li> |
<li class="MsoNormal" style="color: black;"> |
<li> Red Hat and SUSE Linux multiple versions - multithreaded client |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Out of Process |
intermittently fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red |
Provider user level request.<br> |
Hat bug 248052)</li> |
</p> |
<li> OpenSLP Version 2.0 - This release of OpenSLP requires the |
</li> |
patches for OpenSLP version 2.0 documented above.</li> |
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Embedded Object |
|
support. </p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Command Line |
|
Utilities<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">CIMDateTime |
|
enhancements<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of |
|
AutoPtr enhancements. </p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Certificate |
|
management and user-based certificate authentication<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of HTTP |
|
chunking. Pegasus |
|
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"> |
|
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> | </ol> |
<p>Specifically the status of several components of Pegasus functionality were |
</div> |
moved in status on the Feature Status Page as follows:</p> |
<br> |
<ol> |
Further information regarding Pegasus support on IBM platforms can be |
<li>Binary Repository move to green (production capable). (see bug 4388)</li> |
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> |
<li>Out of Process providers</li> |
<br> |
<li>Pegasus Provider Interfaces, User Context for Linux and Unix</li> |
<br> |
</ol> |
Further information regarding Pegasus support on HP platforms can be found |
<p class="MsoNormal" style="margin-left: 0.5in;"> </p> |
at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.<br> |
The complete set of <span class="SpellE">changes </span>defined for this release |
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2> |
is defined in PEP 239 |
The OpenPegasus Bugzilla database documents defects found in Pegasus |
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus defects<br> |
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus |
</a></span></h2> |
bugzilla database</a>. Effective with the start of the |
<p>The Pegasus bugzilla database documents any defects found in Pegasus |
OpenPegasus 2.6 work, ALL changes to the OpenPegasus CVS tree are |
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla |
documented through bugs. Therefore all source code changes to OpenPegasus |
database</a>. Note that bugs committed for Pegasus 2.5.1 have been marked |
are documented through bugs providing a complete history of changes and |
with the keyword <font face="Courier New"><b>2.5.1_APPROVED</b></font> so that |
the reasons for those changes. Bugs reports are filed not only for |
all bug fixes for this release can be found with the following bug search. |
bugs and their corresponding fixes but also as part of the process of |
Note that since this was a minor release all of the fixes were documented as |
committing new code representing the work on PEPs done for OpenPegasus 2.6 |
bugs so that even the changes listed in the previous section are listed as bugs.</p> |
and all subsequent versions. Therefore, a search of the OpenPegasus |
<p> |
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.5.1_APPROVEDhttp://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVED"> |
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED"> |
http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVED</a><br> |
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>, |
</p> |
etc) will yield all changes to the Pegasus CVS tree for that OpenPegasus |
<h2><a name="Pegasus Release Control and Version Definition Documentation">Pegasus |
release.<br> |
Release Control and Version Definition Documentation</a></h2> |
<br> |
<p>The Pegasus project is controlled largely through a set of documents |
- Changes for this release (bugs Tagged |
(PEPs) that serve as the definition and review mechanism for new and |
2.14.0_APPROVED). The link is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.13.0_APPROVED"> |
modified Pegasus functionality and for the definition and documentation |
Pegasus 2.13.0_APPROVED bug list.</a><br> |
of releases.</p> |
<h2><a name="Pegasus Release Control and Version Definition Documentation">Release |
<p>Specifically the following PEPs define the characteristics of this |
Control |
Pegasus release.</p> |
and Version Definition Documentation</a></h2> |
<ol> |
The OpenPegasus project is controlled largely through the CVS repository |
<li> |
and a set of documents (PEPs) that serve both as the definition and review |
<a href="http://www.openpegasus.org/pp/uploads/40/8568/PEP209_ExternalInterface2.5.htm">PEP 209</a> - OpenPegaus 2.5 External Interfaces.<br> |
mechanism for new and modified Pegasus functionality and for the |
</li> |
definition and documentation of releases.<br> |
<li> |
<br> |
<a href="http://www.openpegasus.org/pp/uploads/40/10083/PEP237_RecommendedReleaseOptions.htm">PEP 237</a> - OpenPegaus 2.5.1 Build and Configuration |
The following documentation defines the characteristics of this Pegasus |
Option for Selected |
release. The documents are available in the OpenPegasus CVS |
Platforms</li> |
repository. <br> |
<li>PEP 249 - Pegasus 2.5.1 Release Notes (This document located in the PEP |
<ul> |
repository and the Pegasus source tree root directory)</li> |
<li><b> OpenPegasus Release Definition/Status - (See Wiki Section <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_12_x">OpenPegasus |
<li> |
2.13.x |
<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> |
Release Status</a>) - <span style="font-weight: normal;">A |
</li> |
section in the Pegasus wiki is used throughout the development of |
<li> |
this version as the control point for functionality that will go |
<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> |
into the release and points to all of the PEPs that represent the |
<li>PEP 251 - Pegasus readme.txt for 2.5.1 (Located in PEP repository |
Pegasus functionality changes for this version of Pegasus</span>. </b></li> |
and also in the Pegasus |
<b> </b><span style="font-weight: bold;"></span><b>OpenPegasus |
source |
Build and Configuration Options for Selected Platforms - <span style="font-weight: normal;">In previous versions of Pegasus this |
tree root directory).</li> |
information was released as a Pegasus PEP. Starting with |
<li> |
Pegasus 2.9.0 the information is located in the OpenPegasus CVS |
<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 |
repository as <big style="font-weight: bold;"> <span style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</span></big>.</span></b><b> |
throughout the development of this version as the control point for |
</b> |
functionality that will go into the release and points to all of the |
<li><b> OpenPegasus External Interfaces -<span style="font-weight: normal;">The |
PEPs that represent the Pegasus 2.5 functionality changes. (as of |
list of the OpenPegasus interfaces that are considered external |
this document verion of PEP 230, PEP 180 is listed as draft status)</li> |
and therefore "frozen". Unless an exception is explicitly approved |
</ol> |
by the Steering Committee all subsequent releases of Pegasus MUST |
<h2><a name="General Documentation">General Documentation</a></h2> |
continue to support these interfaces. Interfaces not explicitly |
<p>The following documentation is available for the this Pegasus |
listed in this document, should be considered as internal and |
release:</p> |
subject to change.In previous Pegasus releases this information |
|
was available as a separate PEP. Starting with Pegasus 2.9.0 this |
|
information is integrated into the Pegasus repositoryas </span><small style="font-weight: bold;"><font face="Courier New" size="4"><small>pegasus/doc/EnternalInterface.html</small></font></small><span style="font-weight: normal;">.</span></b></li> |
|
<b> </b> |
|
<li><b> OpenPegasus SDK Packaging Definition - <span style="font-weight: normal;">Defines |
|
the recommended set of files for inclusion in the OpenPegasus SDK. |
|
Starting with Pegasus release 2.11.0, this document is available |
|
in the Pegasus CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>. |
|
In previous Pegasus releases this document was made available as s |
|
separate Pegasus PEP document rather than in the CVS repository.</span> |
|
</b></li> <b> </b> <b> </b> |
|
<li><b> Pegasus Runtime Packaging Definition - <span style="font-weight: normal;">Defines |
|
the recommended set of files for inclusion in this OpenPegasus |
|
release. Starting with Pegasus release 2.11.0, this idocument |
|
contained in the CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/RuntimePackaging.html</samp></big>. |
|
In previous releases this was made available as a seperate Pegasus |
|
PEP document rather than in the CVS repository. </span> </b></li> |
|
<b> </b> <b> </b> |
|
<li><b>Pegasus Release Notes - <span style="font-weight: normal;"> |
|
</span>PEP 368 - <span style="font-weight: normal;"> (This document |
|
is located in the approved PEP repository and the OpenPegasus |
|
source tree root directory </span></b><span style="font-weight: normal;">(<big><span style="font-family: monospace;">pegasus/ReleaseNotes.htm</span></big>)</span></li> |
|
<b> </b> |
|
</ul> |
|
<h2><b><a name="General Documentation">General OpenPegasus Documentation</a></b></h2> |
|
<br> |
|
The following documentation is available for the this Pegasus release:<br> |
<ul style="margin-top: 0in;" type="disc"> | <ul style="margin-top: 0in;" type="disc"> |
<li class="MsoNormal" style="color: black;"><b>Utilities</b> - A |
<b> </b> |
combination of help generally available with the -h option for each |
<li class="MsoNormal" style="color: black;"><b><b>Utilities</b> - </b>A |
command and HTML documentation for most of the tools.<o:p></o:p></li> |
combination of help generally available with the --help option for |
<li class="MsoNormal" style="color: black;"><b>API and usage |
each command and HTML documentation for most of the tools.<o:p></o:p> |
documentation</b> - See the header files and the HTML API |
<b> </b> </li> |
documentation that is on the web site. The best API usage documentation |
<li class="MsoNormal" style="color: black;"><b><b>API and usage |
is the existing utilities and test programs and the examples in the API |
documentation</b> - </b>See the header files and the HTML |
documentation. In particular the Common/tests unit tests contain |
API documentation that is on the web site. The best API usage |
extensive examples of the use of the Common APIs.</li> |
documentation is the existing utilities and test programs and the |
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
examples in the API documentation. In particular the |
Providers </b>- Readme.html in the Pegasus Root Directory, API |
Common/tests unit tests contain extensive examples of the use of the |
documentation, and documentation from the Pegasus Technical Workshop |
Common APIs. <b> </b> </li> |
which is available on the Pegasus web site.</li> |
<li class="MsoNormal" style="color: black;"><b><b>Building and Debugging |
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
Providers </b>- </b>Readme.html in the Pegasus source tree Root |
Clients</b> - API documentation and the documentation on the Pegasus |
Directory, API documentation, and documentation from the Pegasus |
Technical Workshop which is available on the Pegasus web site.</li> |
Technical Workshop which is available on the Pegasus web site. <b> </b> |
<li class="MsoNormal" style="color: black;"><b>Compiler operation and |
</li> |
commands</b> - compiler help (cimmofl -h)</li> |
<li class="MsoNormal" style="color: black;"><b><b>Building and Debugging |
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - The |
Clients</b> -</b>API documentation and the documentation on the |
|
Pegasus Technical Workshop which is available on the Pegasus web site. |
|
<b> </b> </li> |
|
<li class="MsoNormal" style="color: black;"><b><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 |
documents largely and use in the process of defining and approving the | documents largely and use in the process of defining and approving the |
overall characteristics of new functionality, they serve as a guide to | overall characteristics of new functionality, they serve as a guide to |
the design and implementation of these features.</li> | the design and implementation of these features.</li> |
|
<li class="MsoNormal" style="color: black;"><span style="font-weight: bold;">OpenPegasus |
|
WIKI</span> - This WIKI is maintained both for the use of the |
|
development team and as a user information resource. The wiki |
|
can be accessed at <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start</a></li> |
</ul> | </ul> |
|
<hr>Licensed to The Open Group (TOG) under one or more contributor license |
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="color: black;"> <o:p></o:p></span></p> |
agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
work for additional information regarding copyright ownership. Each |
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"> |
contributor licenses this file to you under the OpenPegasus Open Source |
<p style="text-align: left;"><i><font size="2">Copyright (c) 2006 EMC |
License; you may not use this file except in compliance with the License. |
Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open |
<p>Permission is hereby granted, free of charge, to any person obtaining a |
Group; VERITAS Software Corporation; Intel Corp.</font><br> |
copy of this software and associated documentation files (the |
<br> |
"Software"), to deal in the Software without restriction, including |
<font size="1">Permission is hereby granted, free of charge, to any person |
without limitation the rights to use, copy, modify, merge, publish, |
obtaining a copy of this software and associated documentation files (the |
distribute, sublicense, and/or sell copies of the Software, and to |
"Software"), to deal in the Software without restriction, including without |
permit persons to whom the Software is furnished to do so, subject to |
limitation the rights to use, copy, modify, merge, publish, distribute, |
the following conditions:</p> |
sublicense, and/or sell copies of the Software, and to permit persons to whom |
<p>The above copyright notice and this permission notice shall be included |
the Software is furnished to do so, subject to the following conditions:</font><br> |
in all copies or substantial portions of the Software.</p> |
<font size="2"><br> |
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS |
</font><font size="1">THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE |
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF |
SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE |
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. |
SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR |
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY |
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, |
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, |
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE |
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE |
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER |
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p> |
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, |
|
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE |
|
SOFTWARE.</font></i></p></span></div> |
|
<p> </p> |
|
</div> | </div> |
<script language="javascript">postamble();</script> |
|
<script language="javascript">postamble();</script> |
|
</body></html> | </body></html> |