version 1.17, 2010/03/26 13:20:35
|
version 1.17.4.3, 2013/07/20 18:32:34
|
|
|
<!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"> |
<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> |
<title>PEP</title><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]--></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;"> | <p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"> |
|
|
<br> | <br> |
|
<b>PEP #:</b> 366<br> |
<b>PEP #:</b> 355<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 version 2.10.0</p> |
Notes for OpenPegasus version 2.13.0</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 18 July |
|
2013<br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 21 January 2010</p> |
</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Karl |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Karl Schopmeyer<br> |
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%;" id="table1" border="1" cellpadding="0" cellspacing="1" height="155" 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;" height="27"> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
|
|
</tr> | </tr> |
|
|
<tr style=""> | <tr style=""> |
|
|
<td style="padding: 0.75pt;" height="22"> | <td style="padding: 0.75pt;" height="22"> |
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><font size="2"> 1.0</font><o:p></o:p></span></p> | <p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><font size="2"> 1.0</font><o:p></o:p></span></p> |
|
|
</td> | </td> |
|
|
<td style="padding: 0.75pt;" align="left" height="22"> | <td style="padding: 0.75pt;" align="left" height="22"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"> <font size="2"><span style="font-family: Arial;">11 July 2013<br> |
<p class="MsoNormal" style="text-align: center;" align="center"> |
</span></font></p> |
<font size="2"><span style="font-family: Arial;">21 January 2010</span></font></p> |
|
|
|
</td> | </td> |
|
|
<td style="padding: 0.75pt;" align="left" height="22"> | <td style="padding: 0.75pt;" align="left" height="22"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"> <span style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> |
<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;" height="22"> | <td style="padding: 0.75pt;" height="22"> |
|
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial Submission <span style="color: red;"></span></font><o:p><font size="2"> </font></o:p></span></p> |
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial |
|
Submission <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" height="21">1.01<br> |
<td style="padding: 0.75pt;" align="center" height="21">1.1<br></td> |
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">11 July 2013<br> |
<td style="padding: 0.75pt;" align="center" height="21">10 Feb 2010</td> |
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">Karl |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td> |
Schopmeyer<br> |
|
</td> |
<td style="padding: 0.75pt;" height="21"> Remove PEP 353 and 354 from |
<td style="padding: 0.75pt;" height="21">Minor editorial updates |
list and point to repository.<p>Clean up PEP list</td> |
before review<br> |
|
</td> |
</tr> | </tr> |
|
|
<tr style=""> | <tr style=""> |
|
<td style="padding: 0.75pt;" align="center" height="21">1.02<br> |
<td style="padding: 0.75pt;" align="center" height="21">1.2</td> |
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">16 July 2013<br> |
<td style="padding: 0.75pt;" align="center" height="21">18 Mar 2010</td> |
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">Karl |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td> |
Schopmeyer<br> |
|
</td> |
<td style="padding: 0.75pt;" height="21"></td> |
<td style="padding: 0.75pt;" height="21">Update with comments from |
|
1.01. See bug 9611. Add new section"Notes on SpecificOpenPegasus |
|
Functionality"<br> |
|
</td> |
</tr> | </tr> |
|
|
<tr> | <tr> |
|
<td style="padding: 0.75pt;" align="center" height="21">1.03<br> |
<td style="padding: 0.75pt;" align="center" height="21">1.3</td> |
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">18 July 2013<br> |
<td style="padding: 0.75pt;" align="center" height="21">25 March 2010</td> |
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer<br> |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td> |
</td> |
|
<td style="padding: 0.75pt;" height="21">Respond to HP comment about some confusion with the comment to bug 8830 in the compatibility Considerations section<br> |
<td style="padding: 0.75pt;" height="21">Incorporate comments from Vote on |
</td> |
this PEP - This version approved</td> |
|
|
|
</tr> | </tr> |
|
|
<tr style=""> | <tr style=""> |
|
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
|
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
<td style="padding: 0.75pt;" height="23"> </td> |
|
|
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
|
|
|
<td style="padding: 0.75pt;" height="23"> </td> |
|
|
|
</tr> | </tr> |
|
|
|
|
</tbody> | </tbody> |
</table> | </table> |
|
<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 |
<br> |
2.10.0 release of the OpenPegasus CIM Server. The purpose of this PEP is |
<b>Abstract:</b> This document defines the release notes for the 2.13.0 |
to summarize the characteristics of this release, point to other |
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 | documentation that defines the release in more detail, and provide |
additional information about this release that is not available in the | additional information about this release that is not available in the |
other Pegasus documentation.</p> |
other Pegasus documentation.<br> |
<div class="MsoNormal" style="text-align: center;" align="center"> |
<div class="MsoNormal" style="text-align: center;" align="center"> <span style="color: black;"> |
<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="5"> Contents</font></o:p></b></h2> | <h2 style="margin-bottom: 1px;"><b><o:p><font size="5"> Contents</font></o:p></b></h2> |
<ol> | <ol> |
<li><a href="#Availability_of_this_Release_">Availability of this | <li><a href="#Availability_of_this_Release_">Availability of this |
Release</a></li> | Release</a></li> |
<li><a href="#Functionality_of_This_Release">OpenPegasus |
<li><a href="#Functionality_of_This_Release">OpenPegasus Functionality |
Functionality of This Release</a></li> |
of This Release</a></li> |
<li><a href="#Compatibility_Considerations_">Compatibility Considerations</a></li> |
<li><a href="#Compatibility_Considerations_">Compatibility |
<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship |
Considerations</a></li> |
to CIM/WBEM Standards</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="#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="#PEGASUS%20Bugs">OpenPegasus Bugs</a></li> | <li><a href="#PEGASUS%20Bugs">OpenPegasus Bugs</a></li> |
<li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus | <li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus |
Release Control and Version Definition Documentation</a></li> |
Release |
<li><a href="#General%20Documentation">General |
Control and Version Definition Documentation</a></li> |
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><b>Source release</b> in both ZIP (and ZIP EXE) and TAR formats. | <li><b>Source release</b> in both ZIP (and ZIP EXE) and TAR formats. |
These can be |
These can be downloaded from the <span class="SpellE">OpenPegasus</span> |
downloaded from the <span class="SpellE">OpenPegasus</span> Web |
Web site at <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li> |
site at <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li> |
<li><b>OpenPegasus source RPMs</b> on the OpenPegasus web site.. A |
<li><b>OpenPegasus source RPMs</b> on the OpenPegasus web site.. A source RPM is available on the |
source RPM is available on the OpenPegasus web site that can be |
OpenPegasus web site that can be used to build binaries for most LSB-compliant RPM-based Linux distributions and versions.</li> |
used to build binaries for most LSB-compliant RPM-based Linux |
<li><b>The Pegasus CVS repository</b>. The CVS tags representing this |
distributions and versions.</li> |
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> |
WIKI</a>. Installation instructions are part of the README in the root |
|
of the Pegasus source tree.<br> |
</div> | </div> |
<div class="Section1"> | <div class="Section1"> |
<h2><span style="color: black;">OpenPegasus Functionality for This Release</span></h2> |
<h2><span style="color: black;">OpenPegasus Functionality for this Release</span></h2> |
|
OpenPegasus overall status by release is defined by a <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature |
Pegasus overall status by release is defined by a |
Status WEB Page</a> that is available on the OpenPegasus web site |
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a> |
. That web page shows the Pegasus users and developers the status of |
that is available on the OpenPegasus web site . That web page shows the |
the various features found in OpenPegasus using a simple color coded key |
Pegasus users and developers the status of the various features found in Pegasus |
(white, red, yellow, green) and a description of each feature. <br> |
using a simple color coded key (white, red, yellow, green) and a description of |
<br> |
each feature.<p>Pegasus 2.10.0 |
OpenPegasus 2.13.0 is a major release, extending the previous Pegasus |
is a major release, extending the previous Pegasus release in selected |
release in selected areas as described in the Pegasus PEP defining |
areas as described in the Pegasus PEP defining this release |
this release . <br> |
. </p> |
<br> |
|
NOTE: OpenPegasus releases are categorized as follows:<br> |
<p>The major areas of development for this release were as follows. For |
<ul> |
more information access the PEP for each change defined:</p> |
<li>First number of version changes (ex. 2.x.x to 3.0.0) - Major |
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font style="font-weight: bold;" size="4"> |
release includes major functionality change and incompatible |
Table of Major Changes for this Release</font></p> |
behavior changes and/or incompatible public API changes, <br> |
|
</li> |
|
<li>Second number changes (ex 2.12.0 2.13.0) - Minor Release and |
|
includes new functionality but maintains behavior and public API |
|
compatibility, <br> |
|
</li> |
|
<li>3rd number changes (2.13.0 to 2.13.1) - Revision(also called point |
|
release) release and only includes bug fixes.</li> |
|
</ul> |
|
<br> |
|
<u><b>ALL</b></u> changes for each release are documented in the |
|
OpenPegasus bug data base by tagging each bug(keyword field of bug). |
|
No change to Pegasus is committed with out this tag on the bug. Changes |
|
for this minor release are tagged 2.13.0_APPROVED. All changes for |
|
this minor release can be viewed through this link to the |
|
OpenPegasus bugzilla <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.13.0_APPROVED"> |
|
Pegasus 2.13.0_APPROVED bug list. Bugs. </a>Bugs marked as |
|
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.13.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 |
|
to OpenPegasus bugzilla 2.13.0 enhancement bugs</a> . Bugs fixed |
|
for subsequent revision releases (ex. 2.13.1) would also be viewed through |
|
corresponding Bugzilla tags for each revisions (ex 2.13.1_APPROVED).<br> |
|
<br> |
|
The major areas of development including both enhancements and bug fixes |
|
for this release were as follows. Note that the bugs listed |
|
represent only those features incorporated in bugs without PEPS that are |
|
considered enhancements, not all bugs incorporated in the release. For |
|
more information access the PEP/BUG for each change defined below:<br> |
|
<br> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font style="font-weight: bold;" size="4"> Table of Major |
|
Changes for this Release. Please review Bugzilla 2.13.0 |
|
Enhancements and approved(above) for a complete list<br> |
|
</font></p> |
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="82%"> | <table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="82%"> |
<tbody> | <tbody> |
<tr align="center"> | <tr align="center"> |
<th bgcolor="#00ffff">PEP/BUG #</th> |
<th bgcolor="#00ffff">BUG #</th> |
<th bgcolor="#00ffff">Description of Change</th> | <th bgcolor="#00ffff">Description of Change</th> |
<th bgcolor="#00ffff" width="128">Posted PEP<br>Version</th> |
<th bgcolor="#00ffff" width="128">Posted PEP<br> |
|
Version</th> |
</tr> | </tr> |
<tr align="center"> |
<tr> |
<td style="text-align: center;" width="7%">PEP 311</td> |
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=133">133</a></td> |
<td align="left" width="75%">WS-Management Support in CIM Server - Phase II. |
<td>Fixed issues where Pegasus compiler converted Schema Qualifer |
NOTE: This is an update of the same PEP number that incorporated |
decl to CLASS</td> |
WS_Management changes to Pegasus 2.9.0 to incorporate more WS_Management |
<td><br> |
functionality.</td> |
</td> |
<td width="128"> |
</tr> |
<a href="http://www.openpegasus.org/pp/uploads/40/21402/PEP-311V2-2.html"> |
<tr> |
2.2</a><br></td> |
<td style="text-align: center;"> <span style="color: blue;"><span style="text-decoration: underline;">5904</span></span><br> |
|
</td> |
|
<td>Fixed issue that could cause server error if providers |
|
return associator or ref responses with no keys in path</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9373" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9373">9373</a><br> |
|
</td> |
|
<td>Support Writing indications to local file. Note that this is |
|
primarily a development and debug extension.<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9406" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9406">9406</a></td> |
|
<td>Remove the PEGASUS_VENDOR_HP build variable</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9414" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9414">9414</a><br> |
|
</td> |
|
<td>Enhance repupgrade utility to support "interop" namespace (see |
|
note below)<br> |
|
</td> |
|
<td><a href="https://collaboration.opengroup.org/pegasus/pp/documents/24686/PEP304.htm">PEP |
|
304, Version 1.6</a><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9455" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9455">9455</a><br> |
|
</td> |
|
<td>Support clang compiler in Production Build<br> |
|
</td> |
|
<td><br> |
|
</td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="text-align: center;" width="7%">PEP 283</td> |
<td style="text-align: center;"><a title="9456" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9456">9456</a><br> |
<td align="left" width="75%">Extend CIMCLI to create/modify instances with other features</td> |
</td> |
<td style="text-align: center;" width="128"><a href="http://www.openpegasus.org/pp/uploads/40/21271/PEP283_cimcliV1_5.html">1.5</a></td> |
<td>Add more supplemental help info to cimconfig CLI tool that views |
|
and sets runtime parameters<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top; text-align: center;"><a title="9478" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9478">9478 |
|
</a>and others<br> |
|
</td> |
|
<td style="vertical-align: top;">Fixed issues involving compiled |
|
unused variable warnings and set compiler defaults to make these |
|
warnings a build error.<br> |
|
</td> |
|
<td style="vertical-align: top;"><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9506" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9506">9506</a><br> |
|
</td> |
|
<td>Clean up issues with building with static libraries<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9530" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9530">9530</a><span style="color: blue;"><span style="text-decoration: underline;"><br> |
|
</span></span> </td> |
|
<td>Reduce static code size (Note: several bug fixes contributed to |
|
this reduction) (see 9555, 9560, 9557, 9558, 9580)<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9550" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9550">9550</a><br> |
|
</td> |
|
<td>Log rotation configuration variable to set max file size (see |
|
below for more info)<br> |
|
</td> |
|
<td><br> |
|
</td> |
</tr> | </tr> |
<tr align="center"> | <tr align="center"> |
<td style="text-align: center;" width="7%">PEP 348</td> |
<td style="text-align: center;" width="7%"><a title="9564" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9564">9564</a><br> |
<td align="left" width="75%">Single-Memory-Object for CMPI structure</td> |
</td> |
<td width="128"><a href="http://www.openpegasus.org/pp/uploads/40/21210/PEP_348.pdf">1.1</a></td> |
<td align="left" width="75%">Remove compile option |
|
PEGASUS_CLIENT_TRACE_ENABLE (now always compiles) </td> |
|
<td width="128"><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9591" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9591">9591</a><br> |
|
</td> |
|
<td>Fix issues requiring restart of cimserver if indication |
|
provider reregistered<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9592" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9592">9592</a><br> |
|
</td> |
|
<td>Initial configure script for OpenPegasus (Experimental, see below)<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9600" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9600">9600</a><br> |
|
</td> |
|
<td>Update env_var_LINUX.status and env_var_HPUX.status to change |
|
some build defaults<br> |
|
</td> |
|
<td align="center"><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9632" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9632">9632</a></td> |
|
<td>Modify environment variable definition that controls client |
|
tracing (See below)</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;" width="7%"><a style="" title="9637" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9637">9637</a><br> |
|
</td> |
|
<td align="left" width="75%">Add support for PUSH_WITH_ACK delivery |
|
mode for WSMAN indications<br> |
|
</td> |
|
<td style="text-align: center;" width="128">PEP 365<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9645" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9645">9645</a></td> |
|
<td>Change default Schema version to use CIM Schema 2.36</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9646" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9646">9646</a><br> |
|
</td> |
|
<td>Replace custom atomic operations with GCC built-in atomic |
|
operations(see below for more comments)<br> |
|
</td> |
|
<td><br> |
|
</td> |
</tr> | </tr> |
<tr align="center"> | <tr align="center"> |
<td style="text-align: center;" width="7%">PEP 347</td> |
<td style="text-align: center;" width="7%"><a title="9635" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9635">9635</a>, |
<td align="left" width="75%">Separate Internal Modules from Common Library</td> |
<a title="9636" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9636">9637</a><br> |
|
</td> |
|
<td align="left" width="75%">IPV6 support for OpenPegasus slp using |
|
OpenSLP 2.0 (See OpenSLP 2.0 issues documented below)<br> |
|
</td> |
<td width="128"> | <td width="128"> |
<a href="http://www.openpegasus.org/pp/uploads/40/19229/PEP-347-SplitCommon.html"> |
<br> |
1.1</a></td> |
</td> |
</tr> | </tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9663" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9663">9663</a><br> |
<tr><td style="text-align: center;">PEP 350</td><td>Multi CIMOM support on |
</td> |
same OS<br></td><td style="text-align: center;"> |
<td>Support for ARM 64 CPU by adding platform definition |
<a href="http://www.openpegasus.org/pp/uploads/40/21277/PEP350_MultiCIMOM.htm"> |
(Experimental because of limited testing)<br> |
1.0</a></td></tr><tr><td style="text-align: center;"> |
</td> |
<a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8525">Bug 8525</a></td><td> |
<td style="text-align: center;"><br> |
<span class="norm"><a name="comtag_90">repupgrade utility enhancement to |
</td> |
update SystemName property in indication filter/handler and |
|
ObjectManager instances</a></span><br></td><td style="text-align: center;"><br></td></tr><tr align="center"> |
|
<td style="text-align: center;" width="7%"> |
|
<a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8406">Bug 8406</a> </td><td align="left" width="75%"> |
|
<span class="norm"><a name="comtag_95">Indication service can be |
|
disabled/enabled dynamically</a></span><br></td> |
|
|
|
<td width="128"><br></td> |
|
</tr> | </tr> |
<tr align="center"> |
<tr> |
<td style="text-align: center;" width="7%"> </td><td align="left" width="75%"> </td> |
<td style="text-align: center;"><a title="9604" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9604">9604</a><br> |
|
</td> |
<td width="128"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8171"><br></a></td> |
<td>Fix connection between indication handlers and IndicationService |
|
so that OnFatalErrorPolicy works<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9639" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9639">9639</a><br> |
|
</td> |
|
<td>Expand reporting of errors from PAM so detailed PAM errors reported.<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9641" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9641">9641</a><br> |
|
</td> |
|
<td>Allow remote update of expired user password for PAM session |
|
based authentication<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a title="9643" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9643">9643</a><br> |
|
</td> |
|
<td>Role-based authorization extension for CMPI providers<br> |
|
</td> |
|
<td><br> |
|
</td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<p>The status of several components of Pegasus functionality change status |
<br> |
between Pegasus versions. <span class="norm"><a name="comtag_116">Features that |
The status of several components of Pegasus functionality change status |
have changed status can be identified by a change in color from the previous |
between Pegasus versions. <span class="norm"><a name="comtag_116">Features |
release to this release</a></span> on the |
that |
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>.</p> |
have |
|
changed status can be identified by a change in color from the |
<p>Finally, a significant number of internal changes and corrections were made |
previous release to this release</a></span> on the <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature |
under the control of the Pegasus bugzilla bug system. See the bug section below |
Status WEB Page</a>.<br> |
for more information.</p> |
<br> |
|
<h2><a name="Notes_on_Specific_OpenPegasus"></a>Notes on Specific |
<h3><font color="#000000">Information on IPv6 Support (PEP 291)</font></h3> |
OpenPegasus Functionality Changes</h2> |
<p><b>NOTE:</b> This functionality was incorporated in OpenPegasus 2.7.0 but it |
This section documents specific issues that the OpenPegasus team feels are |
was felt that the information below was worth repeating in subsequent Release |
important to OpenPegasus users with the current release (and possibly |
Notes</p> |
older releases).<br> |
<p style="color: rgb(153, 51, 153);"><font color="#000000">IPv6 is short for "Internet |
<br> |
Protocol |
<h3>Add new RunTime Variables to control trace file size and Rotation(OpenPegasus |
Version 6". IPv6 is the "next generation" protocol designed by the IETF |
2.13.0)(bug 9550)</h3> |
to replace the current version Internet Protocol, IP Version 4 |
As of OpenPegasus 2.13.0, two new runtime variables have been added:<br> |
("IPv4"). IPv6 Support for OpenPegasus is documented in </font> <a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html"> |
<br> |
<font color="#3333ff">PEP |
* traceFileSizeKBytes - Defines the size of the |
291</font></a><font color="#000000">.</font></p> |
tracefile in kilobytes. The trace file will be rolled once its size |
<p>The IPv6 support in OpenPegasus is |
exceeds the specified size.<br> |
controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this |
* numberOfTraceFiles - Specifies the number of the tracefiles |
variable is "true"; setting this to |
for rolling where the default is 3. <br> |
|
<br> |
|
<h3>Using GCC 4.7 Compiler on Linux OS (OpenPegasus 2.13.0)<br> |
|
</h3> |
|
As of 2.13.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> | 'false' before building OpenPegasus will disable the IPv6 support.<br> |
</p> |
<br> |
<p>The following subsections provide |
The following subsections provide some information on IPv6 support for the |
some information on IPv6 support for the Linux and Windows platforms. |
Linux and Windows platforms. Note that in the 2.6.1 release there is no |
Note that in the 2.6.1 release there is no automatic run-time detection |
automatic run-time detection of IPv6 support on a platform by OpenPegasus. |
of IPv6 support on a platform by OpenPegasus. If you build with |
If you build with PEGASUS_ENABLE_IPV6=true, your platform must support |
PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you will |
IPv6 or you will get a build failure (missing header files), a run-time |
get a build failure (missing header files), a run-time bind() failure, |
bind() failure, or possibly some other failure. This applies to both the |
or possibly some other failure. This applies to both the CIM Server and |
CIM Server and Listener components. For more information on IPv6 support |
Listener components. For more information on IPv6 support for your |
for your specific platform, refer to the documentation for that platform.<br> |
specific platform, refer to the documentation for that platform.<br> |
<br> |
</p> |
All OpenPegasus externals that support eitcompilerher a hostname or an IP |
<p>All OpenPegasus externals that |
address as input have been updated to allow an IPv6 address to be |
support either a hostname or an IP address as input have been updated |
specified. If the required input is just an IP address (eg. no optional or |
to allow an IPv6 address to be specified. If the required input is just |
required port number), then the IPv6 address must be specified without |
an IP address (eg. no optional or required port number), then the IPv6 |
brackets. For example, the OpenPegasus osinfo client (which returns |
address must be specified without brackets. For example, the |
information about the OS running on a host system) takes separate host and |
OpenPegasus osinfo client (which returns information about the OS |
port options. In this case a host with an IPv6-configured network |
running on a host system) takes separate host and port options. In this |
interface would be specified as:<br> |
case a host with an IPv6-configured network interface would be |
<br> |
specified as:<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> |
</p> |
<br> |
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">osinfo -h |
But the cimcli command, which takes an optional "location" option |
3ffe:1:2:1 -p 5988</font></big></div> |
including an optional port number, requires the IPv6 address to be |
<p>But the cimcli command, which |
delimited with brackets, for example:<br> |
takes |
<br> |
an optional "location" option including an optional port number, |
<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns -l |
requires the IPv6 address to be delimited with brackets, for example:<br> |
[3ffe:1:2:1]</big></div> |
</p> |
|
<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns -l [3ffe:1:2:1]</big></div> |
|
<p>or</p> | <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 style="margin-left: 40px;"><big><span style="font-family: monospace;">cimcli |
|
ns -l [3ffe:1:2:1]:5989</span></big><br> |
</div> | </div> |
<br> | <br> |
For more information on |
For more information on specifying IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF |
specifying |
RFC |
IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP Version |
2373 - IP Version 6 Addressing Architecture</a> and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF |
6 Addressing Architecture</a> |
RFC 2732 - Format for Literal IPv6 Addresses in URL's</a>.<br> |
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> | <h4><font color="#000000">IPv6 on Linux</font></h4> |
<p>Modern Linux distributions already |
Modern Linux distributions already contain IPv6-ready kernels, the IPv6 |
contain IPv6-ready kernels, the |
capability is generally compiled as a module, but it's possible that this |
IPv6 capability is generally compiled as a module, but it's possible |
module is not loaded automatically on startup.<br> |
that this module is not loaded automatically on startup.</p> |
<br> |
<p><span style="font-weight: bold;">Note: |
<span style="font-weight: bold;">Note: </span>you shouldn't use |
</span>you shouldn't use kernel series 2.2.x, because it's not |
kernel series 2.2.x, because it's not IPv6-up-to-date anymore. Also the |
IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no |
IPv6 support in series 2.4.x is no longer improved according to |
longer improved according to definitions in latest RFCs. It's recommend |
definitions in latest RFCs. It's recommend to use series 2.6.x now.<br> |
to use series 2.6.x now.<br> |
<br> |
</p> |
To check whether your current running kernel supports IPv6, take a look |
<p>To check whether your current |
into your /proc filesystem. The entry /proc/net/if_inet6 must exist. A |
running |
short automated test looks like:<br> |
kernel supports IPv6, take a look into your /proc filesystem. The entry |
<br> |
/proc/net/if_inet6 must exist. A short automated test looks like:<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 |
</p> |
kernel is IPv6 ready"</font></big></div> |
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">test -f |
<br> |
/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"</font></big></div> |
For more iSchema version default update to CIM 2.36nformation on enabling |
<p>For more information on |
IPv6 in the Linux kernel and configuring network interfaces, refer to <a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux |
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> | Documentation Project's IPv6 HOWTO</a>.<br> |
<br> | <br> |
<span style="font-weight: bold;">Warning</span>: |
<span style="font-weight: bold;">Warning</span>: There is currently an |
There is currently an open issue with RedHat to address a problem that |
open issue with RedHat to address a problem that is seen intermittently on |
is seen intermittently on RHEL5 and SLES10 systems. This problem is |
RHEL5 and SLES10 systems. This problem is described in <span style="color: rgb(153, 51, 153);"> |
described in <span style="color: rgb(153, 51, 153);"> |
|
<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus | <a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
bug 6586</a> |
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 |
</span> |
bug |
and<span style="color: rgb(153, 51, 153);"> |
248052</a>, </span>and manifests itself as an intermittent IPv6 |
<a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat |
socket failure. You should be aware that OpenPegasus with IPv6 enabled may |
bug 248052</a>, |
be significantly impacted in these environments.<br> |
</span> |
|
and manifests itself as an intermittent IPv6 socket failure. You should be aware |
|
that OpenPegasus with IPv6 enabled may be significantly impacted in these |
|
environments.</p> |
|
<h4><font color="#000000">IPv6 on Windows</font></h4> | <h4><font color="#000000">IPv6 on Windows</font></h4> |
<p>Microsoft provides supported IPv6 |
<br> |
implementations for Windows Server |
Microsoft provides supported IPv6 implementations for Windows Server 2003, |
2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service |
Windows XP with Service Pack 1 (SP1), Windows XP with Service Pack 2 |
Pack 2 (SP2), and Windows CE .NET 4.1 and later.</p> |
(SP2), and Windows CE .NET 4.1 and later.<br> |
On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span> tool to install, uninstall, and |
<br> |
query |
On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span> |
your IPv6 configuration. For example:<br> |
tool to install, uninstall, and query your IPv6 configuration. For |
|
example:<br> |
<br> | <br> |
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">ipv6 install<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> | ipv6 if</font></big></div> |
<p>Windows Vista |
<br> |
and Windows Server 2008 support an integrated |
Windows Vista and Windows Server 2008 support an integrated IPv4 and IPv6 |
IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack. |
implementation known as the Next Generation TCP/IP stack. Note that the |
Note that the OpenPegasus IPv6 support has not yet been tested |
OpenPegasus IPv6 support has not yet been tested on Windows Vista or |
on Windows Vista or Windows Server 2008.<br> |
Windows Server 2008.<br> |
<br> |
<br> |
For more information on |
For more information on installing, configuring, and using IPv6 on Windows |
installing, configuring, and using IPv6 on Windows platforms, refer to |
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> |
the document |
<br> |
<a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"> |
<h4><font color="#000000">Testing OpenPegasus IPv6 support</font></h4> |
<font color="#000000">IPv6 |
As part of the OpenPegasus automated tests, the TestClient, g11ntest, and |
for Microsoft Windows: Frequently Asked Questions</font></a>.<br> |
IndicationStressTest test clients were modified to run tests using the |
</p> |
IPv6 loopback address (::1) if PEGASUS_ENABLE_IPV6=true.<br> |
<h4><font color="#000000">Testing your OpenPegasus IPv6 |
<br> |
support</font></h4> |
You can also perform manual tests using the IPv6 loopback or a real |
As part of the OpenPegasus |
IPv6-configured network interface. For example, using the IPv6 loopback on |
automated tests, the TestClient, g11ntest, and IndicationStressTest |
a system with OpenPegasus running on the WBEM standard http port of 5988:<br> |
test clients were modified to run tests using the IPv6 loopback address |
<div style="margin-left: 40px;"><br> |
(::1) if PEGASUS_ENABLE_IPV6=true.<br> |
<big style="font-family: monospace;"> osinfo -h ::1</big></div> |
<br> |
<h2><a name="Compatibility_Considerations_">OpenPegasus Compatibility |
You can also perform manual |
Considerations</a></h2> |
tests |
Support for forward-compatibility is a fundamental design principle for |
using the IPv6 loopback or a real IPv6-configured network interface. |
the OpenPegasus project. As a community, our goal is for well-behaved |
For example, using the IPv6 loopback on a system with OpenPegasus |
OpenPegasus providers or clients, using only the externally defined |
running on the WBEM standard http port of 5988:<br> |
OpenPegasus interface, to continue to work with a minor version upgrade of |
<div style="margin-left: 40px;"><br><big style="font-family: monospace;"> |
OpenPegasus. However, there are certain classes of errors (e.g., |
osinfo -h ::1</big></div> |
non-compliance with a standard that significantly affects |
<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2> |
interoperability) that may require the community to make potentially |
<p>Support for forward-compatibility is a fundamental design principle for the |
incompatible changes. The following table contains a list of defects/fixes |
OpenPegasus project. As a Community, our goal is for well-behaved OpenPegasus |
that MAY impact, even well-behaved, OpenPegasus providers or clients when |
Providers or Clients, using only the externally defined OpenPegasus interface, |
upgrading to this OpenPegasus release. <br> |
to continue to work with a minor version upgrade of OpenPegasus. However, there |
<br> |
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 defect |
|
fixes that MAY impact, even well-behaved, OpenPegasus Providers or Clients when |
|
upgrading to this OpenPegasus release.</p><p> </p> |
|
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="80%"> | <table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="80%"> |
<tbody> | <tbody> |
<tr align="center"> | <tr align="center"> |
<th bgcolor="#00ffff" width="10%">Bugzilla #</th> | <th bgcolor="#00ffff" width="10%">Bugzilla #</th> |
<th bgcolor="#00ffff">Description</th> | <th bgcolor="#00ffff">Description</th> |
</tr> | </tr> |
<tr><td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8229"><br></a></td><td><br></td></tr><tr align="center"> |
|
<td></td> |
|
<td align="left"></td> |
|
</tr> |
|
<tr align="center"> |
|
<td></td> |
|
<td></td> |
|
</tr> |
|
<tr align="center"> | <tr align="center"> |
<td></td> |
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8830">Bug |
<td></td> |
8830</a></td> |
</tr> |
<td align="left">Starting |
<tr align="center"> |
with OpenPegasus 2.11.0 the requirement for providers (CMPI and C++) to |
<td></td> |
filter properties from instances has been relieved. The server will do |
<td></td> |
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> |
<tr align="center"> | <tr align="center"> |
<td></td> |
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9369">Bug |
<td></td> |
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> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<h2>OpenPegasus Relationship to |
<h2>OpenPegasus Relationship to CIM/WBEM Standards</h2> |
CIM/WBEM Standards</h2> |
Pegasus was designed and implemented to comply with the DMTF CIM/WBEM |
<p>Pegasus was designed and implemented to comply with the DMTF |
specifications The following table defines the level of the DMTF |
CIM/WBEM specifications The following table defines the level of the |
specifications to which this version of Pegasus aims to conform today.<br> |
DMTF specifications to which this version of Pegasus aims to conform |
<br> |
today.</p> |
|
<table id="AutoNumber1" border="1" cellspacing="1" width="80%"> | <table id="AutoNumber1" border="1" cellspacing="1" width="80%"> |
<tbody> | <tbody> |
<tr> | <tr> |
|
|
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">CIM Schema </td> | <td width="33%">CIM Schema </td> |
<td width="33%">2.22.1 Final, 22 Oct 2009( default) </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> |
|
<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> |
</tbody> | </tbody> |
</table> | </table> |
<h2><a name="Conformance with DMTF Specifications">Conformance |
<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIA SMI |
Exceptions to |
Profiles Supported</h2> |
DMTF Specifications</a></h2> |
<br> |
<p>It is a major goal |
Today OpenPegasus includes support for several DMTF profiles including:<br> |
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>DMTF ProfileRegistration Version DSP 1033, Version 1.0.0</li> |
through a set of Pegasus Provider registration classes rather than |
<li>DMTF Indications DSP 1054, Version 1.1.0. Since this is effectively the same as the |
support the DMTF defined Provider Qualifier. Pegasus will not support |
SNIA SMI Indication profile it also supports this profile. This |
this qualifier in the future. See the readme for more information on |
profile is enabled by compiling OpenPegasus with the buld variable |
provider registration. This is not a deviation from the |
PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.<br> |
specifications but is a different method of registration than many CIM |
</li> |
Servers and means that the the provider qualifier is unused in Pegasus.</li> |
<li>SNIA Profile Registration 1.0.0<br> |
<li><b>Indications </b>-Today Pegasus supports process |
</li> |
indications and lifecycle indications when defined specifically by |
<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 | 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 |
not defined by the provider or for changes to CIM Classes.<font color="#ff0000"> |
more information see the Pegasus CVS file:<a name="comtag_137"><font size="2"> |
</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> | </font><font face="Courier New" size="2"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a><font size="2">.</font></span></li> |
<li> |
<li> <font style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers |
<p class="MsoNormal"><font style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers |
option |
option on Instance Operations</font><span style="color: black;"><b> </b> |
on Instance Operations</font><span style="color: black;"><b> </b> |
- |
- The DMTF specifications have deprecated the use of qualifiers on |
The DMTF specifications have deprecated the use of qualifiers on |
instance operations with the 1.2 CIM Operations Over HTTP Specification (DSP0200) and |
instance operations with the 1.2 CIM Operations Specification and |
|
stated specifically that the client should NOT depend on the | stated specifically that the client should NOT depend on the |
includeQualifiers parameter of the CIM/XML instance operations | includeQualifiers parameter of the CIM/XML instance operations |
returning qualifiers. |
returning qualifiers. Some CIM Client implementations expect |
Some CIM Client implementations expect instances |
instances returned from the CIM Server to include the qualifiers |
returned |
defined in the class definition (such as KEY qualifiers on |
from the CIM Server to include the qualifiers defined in the class |
properties). Pegasus today expects the provider to |
definition (such as KEY qualifiers on properties). </span> Pegasus |
complete the qualifiers on instances in accordance with the |
today expects the provider to complete the qualifiers on instances in |
specification and generally the interpretation is that Pegasus |
accordance with the specification and generally the interpretation is |
applies class level qualifiers when the includeInstance parameter is |
that Pegasus applies class level qualifiers when the includeInstance |
supplied on instance operations. However, Pegasus today is |
parameter is supplied on instance operations. However, Pegasus |
inconsistent in the return of qualifiers so that the user should NOT |
today is inconsistent in the return of qualifiers so that the user |
depend on Pegasus accurately honoring the includeQualifier parameter |
should NOT depend on Pegasus accurately honoring the includeQualifier |
for instance operations. In the future it is expected that |
parameter for instance operations. In the future it is expected |
Pegasus will deprecate the use of qualifiers on instance operations |
that Pegasus will deprecate the use of qualifiers on instance |
completely. When Pegasus uses object normalization, the |
operations completely. When Pegasus uses object normalization, |
normalizer does apply qualifiers to returned instances if the |
the normalizer does apply qualifiers to returned instances if the |
includeQualifiers operation parameter is set.</span></li> |
includeQualifiers operation parameter is set.</p></li><li><b>LocalOnly option on instance |
<li><b>LocalOnly option on instance Operations </b>- With the 1.1 |
Operations </b>- With the 1.1 version of Specification for CIM |
version of Specification for CIM Operations over HTTP, the definition |
Operations over HTTP, the definition of the LocalOnly parameter for the |
of the LocalOnly parameter for the GetInstance and Enumerate Instances |
GetInstance and Enumerate Instances operations was modified. This change |
operations was modified. This change was incorrect, resulted in |
was incorrect, resulted in reduced functionality and introduced a |
reduced functionality and introduced a number of backward |
number of backward compatibility issues. As a result of issues |
compatibility issues. As a result of issues introduced by this change, |
introduced by this change, we strongly recommend that CIM Clients set |
we strongly recommend that CIM Clients set LocalOnly = false and do |
LocalOnly = false and do not rely on the use of this parameter to |
not rely on the use of this parameter to filter the set of set of |
filter the set of set of properties returned. See Appendix C of this |
properties returned. See Appendix C of this specification for more |
specification for more information.</li> |
information.</li> |
<li> |
<li><span style="font-weight: bold;">MultiRequest CIM/XML Option</span> |
<p class="MsoNormal"><b>MultiRequest Operations</b> - Pegasus |
- Pegasus does not support the DMTF defined MultiRequest |
does not support the DMTF defined MultiRequest Operation option.</p> |
Operation option (See DSP0200).<br> |
</li> | </li> |
<li> |
<li><span style="font-weight: bold;">MOF Namespace Pragma</span> -The |
<p class="MsoNormal"><b>MOF Compiler namespace pragma</b> - The |
Pegasus compiler does not support the namespace pragma defined in DSP |
Pegasus compiler does not support the namespace pragma.</p> |
0004. Namespaces for the OpenPegasus repository are defined through |
|
arguments for the MOF Compiler<br> |
</li> | </li> |
<li><b>CIMOperation Trailer </b>- Pegasus implements |
<li><b>CIMOperation Trailer </b>- Pegasus implements chunking based on |
chunking |
the DSP0200 1.2.0 preliminary spec. including the operation trailer |
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> |
defined in that specification Refer to bug |
for more details. This trailer was completely removed from the DSP0200 |
<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> for more details. |
1.2 final specification as a non-compatible change so that if chunking |
This trailer was completely removed from the DSP0200 1.2 final specification |
is used Pegasus is returning a noncompliant response to enumerate type |
as a non-compatible change so that if chunking is used Pegasus is returning |
requests. </li> |
a noncompliant response to enumerate type requests. <br> |
<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).<br> |
</li> | </li> |
</ol> | </ol> |
<h2><b><span style="font-family: Times;">OpenPegasus <a name="Supported Platforms">Supported | <h2><b><span style="font-family: Times;">OpenPegasus <a name="Supported Platforms">Supported |
Platforms</a></span></b></h2> | Platforms</a></span></b></h2> |
<p align="left">Each OpenPegasus release lists as 'active' platforms those |
Each OpenPegasus release lists as 'active' platforms those |
hardware/software platforms that have recognized ports for the Pegasus code base |
hardware/software platforms that have recognized ports for the Pegasus |
including a maintainer for the platform that will be willing to regularly |
code base including a maintainer for the platform that will be willing to |
document issues and/or fix defects as the Pegasus code base is changed. |
regularly document issues and/or fix defects as the Pegasus code base is |
Pegasus may be operable on other platforms (ex. Windows 98) but without a group |
changed. Pegasus may be operable on other platforms (ex. Windows 98) |
to provide the role of test and maintenance, correct operation of Pegasus |
but without a group to provide the role of test and maintenance, correct |
cannot be assured. In all cases, including the active platforms, it is the |
operation of Pegasus cannot be assured. In all cases, |
responsibility of the entity that packages and/or compiles OpenPegasus for |
including the active platforms, it is the responsibility of the entity |
shipment or deployment, to read, and actively monitor the Pegasus bugzilla |
that packages and/or compiles OpenPegasus for shipment or deployment, to |
database for a list of relevant defects that affect their platform. |
read, and actively monitor the Pegasus Bugzilla database for a list of |
The platforms that are considered ported are shown in the two tables below. |
relevant defects that affect their platform. The platforms |
The first table represents platform sofr which testing is done on a regular |
that are considered ported are shown in the two tables below. The |
basis and reported to the Pegasus Nightly Build Test WEB Page. Those platforms |
first table represents platform for which testing is done on a regular |
which have been ported but do not have test results that are current at the time |
basis and reported to the Pegasus Nightly Build Test WEB Page. Those |
of the release are reported in the second table.</p><b>Actively Supported Platforms (Nightly Tests Reported for this release)</b> |
platforms which have been ported but do not have test results that are |
|
current at the time of the release are reported in the second table.<br> |
|
<br> |
|
<b>Actively Supported Platforms (Nightly Tests Reported for this release)</b> |
<table class="MsoNormalTable" style="width: 90%;" border="1" cellpadding="0" cellspacing="1"> | <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(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;" height="26"> |
<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(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;" height="26"> |
<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;"> | <td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span style="color: black;">HP-UX<o:p> PA_RISC and |
<p class="MsoNormal"><span style="color: black;">HP-UX<o:p> |
Itanium</o:p></span></p> |
PA_RISC and Itanium</o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt;"> | <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;"> | <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;"> | <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;"> |
<td style="padding: 0.75pt;"> <span style="color: black;"><font size="3">Linux |
<span style="color: black;"><font size="3">Linux IA-32</font></span></td> |
IA-32</font></span></td> |
<td style="padding: 0.75pt;"> |
<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 |
<span class="SpellE"><span style="color: black;"><font size="3">gcc</font></span></span><span style="color: black;"><font size="3"> |
is considered production effective OpenPegasus 2.13.0)</font><o:p></o:p></span></td> |
(versions 3.xx, 4.xx)</font><o:p></o:p></span></td> |
|
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt;"> | <td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span style="color: black;">Linux X86_64<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;"> | <td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"> |
<p class="MsoNormal"><span class="SpellE"><span 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> |
(versions 3.xx, 4.xx)</span></p> |
|
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><font size="3">z/OS V1.7 and up</font></td> | <td style="vertical-align: top;"><font size="3">z/OS V1.7 and up</font></td> |
<td style="vertical-align: top;"><font size="3">XL C/C++ from z/OS Version |
<td style="vertical-align: top;"><font size="3">XL C/C++ from z/OS |
1.7 and up</font></td> |
Version 1.7 and up</font></td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<p align="center"><b>Platforms not Actively supported for this release (No |
|
current Nightly Build Test Results</b></p> |
<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"> | <table class="MsoNormalTable" style="width: 90%;" id="table2" border="1" cellpadding="0" cellspacing="1"> |
<tbody> | <tbody> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;" height="26"> |
<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(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;" height="26"> |
<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> | <tr> |
<td style="padding: 0.75pt;"> <font size="3">Windows XP</font><p></p> |
<td style="padding: 0.75pt;"> <font size="3">Windows XP, Windows |
</td> |
Vista, Windows 7, Windows Server 2008</font> </td> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1. |
Compilers 2003 - 2010.. Note: Visual C++ Ver. 6 no longer being |
Note: Visual C++ Ver. 6 no longer being regular tested. |
regular tested.Note that today there are some open issues with |
</font> |
the Windows.</font> </td> |
</td> |
|
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt;"> <font size="3">MacOS version 10.3 and higher</font></td> |
<td style="padding: 0.75pt;"> <font size="3">MacOS version 10.3 and |
|
higher</font></td> |
<td style="padding: 0.75pt;"> <font size="3">gcc 4.01</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><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 8</span></font></big></td> |
<td style="vertical-align: top;"><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
8</span></font></big></td> |
CC compiler V 5.8. Note that the latest thread patch (108993) may be |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun CC |
required. (see Pegasus bug 4632)</big><br> |
compiler V 5.8. Note that the latest thread patch (108993) may |
|
be required. (see Pegasus bug 4632)</big><br> |
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><span class="norm"></span><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9</span></font></big></td> | <td style="vertical-align: top;"><span class="norm"></span><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9</span></font></big></td> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun WorkShop |
WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
</td> | </td> |
</tr><tr><td><big>HP OpenVMS 8.3 or later Alpha</big></td><td><big><font style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span style="color: rgb(153, 51, 153);">7.3-009 or later required</span> for OpenVMS |
</tr> |
Alpha</font></big></td></tr> |
<tr> |
<tr><td><big><font style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later IA64</font></big></td><td><big><font style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 or |
<td><big>HP OpenVMS 8.3 or later Alpha</big></td> |
later required</font><font style="color: rgb(0, 0, 0);"> on OpenVMS IA64</font></big></td></tr> |
<td><big><font style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span style="color: rgb(153, 51, 153);">7.3-009 or later required</span> |
|
for OpenVMS Alpha</font></big></td> |
|
</tr> |
|
<tr> |
|
<td><big><font style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later |
|
IA64</font></big></td> |
|
<td><big><font style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 |
|
or later required</font><font style="color: rgb(0, 0, 0);"> on |
|
OpenVMS IA64</font></big></td> |
|
</tr> |
<tr> | <tr> |
<td style="padding: 0.75pt;"> | <td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span style="color: black;">Windows 2000</span></p> | <p class="MsoNormal"><span style="color: black;">Windows 2000</span></p> |
</td> | </td> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler version. Works on VC .NET 2003 v7.1). |
Ver. 6 and Microsoft .Net compiler version. Works on |
NOTE: Visual C++ Ver. 6 no longer being regularly tested.</font></td> |
VC .NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being |
|
regularly tested.</font></td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="padding: 0.75pt;"> <font size="3">Windows 2003</font><p></p> |
<td style="padding: 0.75pt;"> <font size="3">Windows 2003</font> </td> |
</td> |
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
<td style="padding: 0.75pt;"> |
Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++ |
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1. |
Ver. 6 no longer being regular tested. </font> </td> |
Note: Visual C++ Ver. 6 no longer being regular tested. |
</tr> |
</font> |
<tr> |
</td> |
<td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td> |
|
<td><big>CC Compiler Sun Studio 5.11</big></td> |
</tr> | </tr> |
<tr><td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td><td><big>CC Compiler Sun Studio 5.11</big></td></tr> |
|
</tbody> | </tbody> |
</table> | </table> |
<p><b>Platform patches</b> |
<h3><b>Platform patches</b> </h3> |
</p> |
<br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font style="color: rgb(0, 0, 0);">The following is a list known of platform |
<font style="color: rgb(0, 0, 0);">The following is a list known of |
patches Pegasus requires.</font></p> |
platform patches Pegasus requires.</font><br> |
<div style="margin-left: 40px;"> | <div style="margin-left: 40px;"> |
<ol> | <ol> |
<li> |
<li> <font style="color: rgb(0, 0, 0);">RHAS 2.1 needs the update to |
<p style="margin-top: 0pt; margin-bottom: 0pt;"> |
fix Red Hat Bugzilla 98815.</font><br> |
<font style="color: rgb(0, 0, 0);">RHAS |
</li> |
2.1 needs the update to fix Red Hat Bugzilla 98815.</font></p></li> |
<li> RHEL 4.4 multithreading bug in getpwuid-r could cause a CIM |
<li> |
Server failure (Bugzilla 6232). This is fixed in RHEL 4.5<br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4 multithreading bug in |
</li> |
getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is fixed in |
<li> Red Hat and SUSE Linux multiple versions - multithreaded client |
RHEL 4.5</p></li> |
intermittently fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red |
<li> |
Hat bug 248052)</li> |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE Linux |
<li> OpenSLP Version 2.0 - This release of OpenSLP requires the |
multiple versions - |
patches for OpenSLP version 2.0 documented above.</li> |
multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla |
|
6586) (Red Hat bug 248052)<br></p></li> |
|
</ol> | </ol> |
</div> | </div> |
<p>Further information regarding Pegasus support on IBM platforms can |
<br> |
be |
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> | 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> |
<br> |
<p> Further information regarding Pegasus support on HP platforms can |
<br> |
be |
Further information regarding Pegasus support on HP platforms can be found |
found at: |
at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.<br> |
<a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> |
|
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2> | <h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2> |
<p>The Pegasus bugzilla database documents any defects found in Pegasus |
The OpenPegasus Bugzilla database documents defects found in Pegasus |
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla |
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus |
database</a>. |
bugzilla database</a>. Effective with the start of the |
Effective with the start of the Pegasus 2.6 work, all changes to the |
OpenPegasus 2.6 work, ALL changes to the OpenPegasus CVS tree are |
CVS tree are documented through bugs. Bugs reports are filed not |
documented through bugs. Therefore all source code changes to OpenPegasus |
only for bugs and |
are documented through bugs providing a complete history of changes and |
their corresponding fixes but also as part of the process of committing |
the reasons for those changes. Bugs reports are filed not only for |
new code |
bugs and their corresponding fixes but also as part of the process of |
representing the work on PEPs done for Pegasus 2.6 and all subsequent |
committing new code representing the work on PEPs done for OpenPegasus 2.6 |
versions. Therefore, a search of |
and all subsequent versions. Therefore, a search of the OpenPegasus |
the Open Pegasus bugzilla base for bugs with the tag for a particular |
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>, |
version |
|
(ex. |
|
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED"> |
|
2.6.0_APPROVED</a>, |
|
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED"> | <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED"> |
2.6.1_APPROVED</a>, |
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>, |
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>, etc) will yield all changes to |
etc) will yield all changes to the Pegasus CVS tree for that OpenPegasus |
the Pegasus CVS tree for that Pegasus release.</p> |
release.<br> |
|
<br> |
<p> |
|
- Changes for this release (bugs Tagged | - Changes for this release (bugs Tagged |
2.10.0_APPROVED). The link is <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.10.0_APPROVED"> |
2.13.0_APPROVED). The link is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.13.0_APPROVED"> |
Pegasus 2.10.0_APPROVED bug list.</a></p> |
Pegasus 2.13.0_APPROVED bug list.</a><br> |
|
<h2><a name="Pegasus Release Control and Version Definition Documentation">Release |
<h2><a name="Pegasus Release Control and Version Definition Documentation">Release Control and Version Definition Documentation</a></h2> |
Control |
|
and Version Definition Documentation</a></h2> |
<p>The Pegasus project is controlled largely through the CVS repository and a set of documents |
The OpenPegasus project is controlled largely through the CVS repository |
(PEPs) that serve both as the definition and review mechanism for new and |
and a set of documents (PEPs) that serve both as the definition and review |
modified Pegasus functionality and for the definition and documentation |
mechanism for new and modified Pegasus functionality and for the |
of releases.</p>The following documentation defines the characteristics of this |
definition and documentation of releases.<br> |
Pegasus release. The PEPs are available at |
<br> |
<a href="http://www.openpegasus.org/pp/protected/documents.tpl?CALLER=index.tpl&gdc_docage=0&S=gdc_title&R=desc" style="color: blue; text-decoration: underline;"> |
The following documentation defines the characteristics of this Pegasus |
OpenPegasus Approved PEPs.</a><ol> |
release. The documents are available in the OpenPegasus CVS |
|
repository. <br> |
<b> <li> |
<ul> |
OpenPegasus Release Definition/Status - </li>No PEP (See Wiki Section <a href="http://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_9_x">OpenPegasus 2.10.x Release Status</a>) - </b>A |
<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 |
section in the Pegasus wiki is used |
2.13.x |
throughout the development of this version as the control point for |
Release Status</a>) - <span style="font-weight: normal;">A |
functionality that will go into the release and points to all of the PEPs that |
section in the Pegasus wiki is used throughout the development of |
represent the Pegasus functionality changes for this version of Pegasus<span style="font-weight: bold;">.<br></span> |
this version as the control point for functionality that will go |
<b> |
into the release and points to all of the PEPs that represent the |
|
Pegasus functionality changes for this version of Pegasus</span>. </b></li> |
OpenPegasus Build and Configuration |
<b> </b><span style="font-weight: bold;"></span><b>OpenPegasus |
Options for Selected |
Build and Configuration Options for Selected Platforms - <span style="font-weight: normal;">In previous versions of Pegasus this |
Platforms -<span style="font-weight: normal;"> </span> |
information was released as a Pegasus PEP. Starting with |
<a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/*checkout*/pegasus/doc/BuildAndReleaseOptions.html?rev=1.18">CVS Respository Build And Release Options Document</a> - |
Pegasus 2.9.0 the information is located in the OpenPegasus CVS |
<span style="font-weight: normal;">In previous versions of Pegasus this |
repository as <big style="font-weight: bold;"> <span style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</span></big>.</span></b><b> |
information was releases as a Pegasus PEP. Starting with Pegasus 2.9.0 |
</b> |
the information is located in the OpenPegasus CVS repository as <big> |
<li><b> OpenPegasus External Interfaces -<span style="font-weight: normal;">The |
<span style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</span></big>.</span></li></b><b> |
list of the OpenPegasus interfaces that are considered external |
|
and therefore "frozen". Unless an exception is explicitly approved |
<li> |
by the Steering Committee all subsequent releases of Pegasus MUST |
OpenPegasus External Interfaces - |
continue to support these interfaces. Interfaces not explicitly |
<a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/*checkout*/pegasus/doc/ExternalInterface.html?rev=1.3"> |
listed in this document, should be considered as internal and |
CVS Repository External Interfaces Document</a>- </b>THE list of the |
subject to change.In previous Pegasus releases this information |
OpenPegasus interfaces that are considered external and therefore "frozen". |
was available as a separate PEP. Starting with Pegasus 2.9.0 this |
Unless an exception is explicitly approved by the Steering Committee all |
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> |
subsequent releases of Pegasus MUST continue to support these interfaces. |
<b> </b> |
Interfaces not explicitly listed in this document, should be considered as |
<li><b> OpenPegasus SDK Packaging Definition - <span style="font-weight: normal;">Defines |
internal and subject to change.<b> |
the recommended set of files for inclusion in the OpenPegasus SDK. |
|
Starting with Pegasus release 2.11.0, this document is available |
</b>In previous Pegasus releases this information was available as a separate |
in the Pegasus CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>. |
PEP. Starting with Pegasus 2.9.0 this information is integrated into the |
In previous Pegasus releases this document was made available as s |
Pegasus repository<b> </b>as <font face="Courier New" size="4">pegasus/doc/EnternalInterface.html</font>.<b><br> |
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 |
<li> |
release. Starting with Pegasus release 2.11.0, this idocument |
OpenPegasus SDK Packaging Definition - </li> |
contained in the CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/RuntimePackaging.html</samp></big>. |
<a href="http://www.openpegasus.org/pp/uploads/40/16779/PEP330_SDKFile2.8.0.htm"> |
In previous releases this was made available as a seperate Pegasus |
PEP 352</a> - </b>Defines the |
PEP document rather than in the CVS repository. </span> </b></li> |
recommended set of files for inclusion in the OpenPegasus SDK |
<b> </b> <b> </b> |
|
<li><b>Pegasus Release Notes - <span style="font-weight: normal;"> |
<b> |
</span>PEP 364 - <span style="font-weight: normal;"> (This document |
|
is located in the approved PEP repository and the OpenPegasus |
<li> |
source tree root directory </span></b><span style="font-weight: normal;">(<big><span style="font-family: monospace;">pegasus/ReleaseNotes.htm</span></big>)</span></li> |
Pegasus Runtime Packaging Definition - |
<b> </b> |
<a href="http://www.openpegasus.org/pp/uploads/40/18247/PEP341_RuntimePackaging2.9.0.htm"> |
</ul> |
PEP 351</a> - </li></b>Defines the |
<h2><b><a name="General Documentation">General OpenPegasus Documentation</a></b></h2> |
recommended set of files for inclusion in this OpenPegasus release. |
<br> |
|
The following documentation is available for the this Pegasus release:<br> |
<b> |
|
|
|
<li>Pegasus Release Notes - <span style="font-weight: normal;"> </span>PEP 355 |
|
- <span style="font-weight: normal;"> (This document is located in the |
|
approved PEP |
|
repository and the OpenPegasus source tree root directory (<big><span style="font-family: monospace;">pegasus/ReleaseNotes.htm</span></big>)</span><br> |
|
|
|
</li> |
|
|
|
</b></ol> |
|
|
|
<h2><b><a name="General Documentation">General Documentation</a></b></h2> |
|
<p><b>The following documentation is available for the this Pegasus |
|
release:</b></p> |
|
<ul style="margin-top: 0in;" type="disc"> | <ul style="margin-top: 0in;" type="disc"> |
<b> <li class="MsoNormal" style="color: black;"><b>Utilities</b> - </li></b>A |
<b> </b> |
combination of help generally available with the --help 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> |
combination of help generally available with the --help option for |
|
each command and HTML documentation for most of the tools.<o:p></o:p> |
<b> |
<b> </b> </li> |
|
<li class="MsoNormal" style="color: black;"><b><b>API and usage |
<li class="MsoNormal" style="color: black;"><b>API and usage |
documentation</b> - </b>See the header files and the HTML |
documentation</b> - </li></b>See the header files and the HTML API |
API documentation that is on the web site. The best API usage |
documentation that is on the web site. The best API usage documentation |
documentation is the existing utilities and test programs and the |
is the existing utilities and test programs and the examples in the API |
examples in the API documentation. In particular the |
documentation. In particular the Common/tests unit tests contain |
Common/tests unit tests contain extensive examples of the use of the |
extensive examples of the use of the Common APIs. |
Common APIs. <b> </b> </li> |
|
<li class="MsoNormal" style="color: black;"><b><b>Building and Debugging |
<b> |
Providers </b>- </b>Readme.html in the Pegasus source tree Root |
|
Directory, API documentation, and documentation from the Pegasus |
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
Technical Workshop which is available on the Pegasus web site. <b> </b> |
Providers </b>- </li></b>Readme.html in the Pegasus source tree Root Directory, API |
</li> |
documentation, and documentation from the Pegasus Technical Workshop |
<li class="MsoNormal" style="color: black;"><b><b>Building and Debugging |
which is available on the Pegasus web site. |
Clients</b> -</b>API documentation and the documentation on the |
|
Pegasus Technical Workshop which is available on the Pegasus web site. |
<b> |
<b> </b> </li> |
|
<li class="MsoNormal" style="color: black;"><b><b>PEPs</b> -</b>The |
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
|
Clients</b> - </li></b>API documentation and the documentation on the Pegasus |
|
Technical Workshop which is available on the Pegasus web site. |
|
|
|
<b> |
|
|
|
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - </li></b>The |
|
features of Pegasus that have been installed in this and the previous | 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. |
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 | <hr>Licensed to The Open Group (TOG) under one or more contributor license |
agreements. Refer to the OpenPegasusNOTICE.txt file distributed with |
agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this |
this work for additional information regarding copyright ownership. |
work for additional information regarding copyright ownership. Each |
Each contributor licenses this file to you under the OpenPegasus Open |
contributor licenses this file to you under the OpenPegasus Open Source |
Source License; you may not use this file except in compliance with the |
License; you may not use this file except in compliance with the License. |
License. |
|
<p>Permission is hereby granted, free of charge, to any person obtaining a | <p>Permission is hereby granted, free of charge, to any person obtaining a |
copy of this software and associated documentation files (the "Software"), |
copy of this software and associated documentation files (the |
to deal in the Software without restriction, including without limitation |
"Software"), to deal in the Software without restriction, including |
the rights to use, copy, modify, merge, publish, distribute, sublicense, |
without limitation the rights to use, copy, modify, merge, publish, |
and/or sell copies of the Software, and to permit persons to whom the |
distribute, sublicense, and/or sell copies of the Software, and to |
Software is furnished to do so, subject to the following conditions:</p> |
permit persons to whom the Software is furnished to do so, subject to |
|
the following conditions:</p> |
<p>The above copyright notice and this permission notice shall be included | <p>The above copyright notice and this permission notice shall be included |
in all copies or substantial portions of the Software.</p> | in all copies or substantial portions of the Software.</p> |
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS | <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS |
|
|
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE | TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE |
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p> | SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p> |
</div> | </div> |
|
|
</body></html> | </body></html> |