version 1.12, 2007/10/16 17:27:28
|
version 1.19, 2012/09/20 05:48:51
|
|
|
<!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"> | <html xmlns:v="urn:schemas-microsoft-com:vml"> |
<head> | <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" |
<link rel="Edit-Time-Data" href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso"> |
href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso"> |
|
<title>PEP</title> | <title>PEP</title> |
<o:smarttagtype |
|
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype> |
|
<o:smarttagtype |
|
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype |
|
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml> |
|
<o:DocumentProperties> |
|
<o:Author>IBM_User</o:Author> |
|
<o:LastAuthor> </o:LastAuthor> |
|
<o:Revision>4</o:Revision> |
|
<o:TotalTime>211</o:TotalTime> |
|
<o:Created>2004-04-05T14:13:00Z</o:Created> |
|
<o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> |
|
<o:Pages>1</o:Pages> |
|
<o:Words>5026</o:Words> |
|
<o:Characters>28651</o:Characters> |
|
<o:Company>IBM</o:Company> |
|
<o:Lines>238</o:Lines> |
|
<o:Paragraphs>67</o:Paragraphs> |
|
<o:CharactersWithSpaces>33610</o:CharactersWithSpaces> |
|
<o:Version>10.4219</o:Version> |
|
</o:DocumentProperties> |
|
</xml><![endif]--><!--[if gte mso 9]><xml> |
|
<w:WordDocument> |
|
<w:SpellingState>Clean</w:SpellingState> |
|
<w:GrammarState>Clean</w:GrammarState> |
|
<w:Compatibility> |
|
<w:ApplyBreakingRules/> |
|
</w:Compatibility> |
|
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> |
|
</w:WordDocument> |
|
</xml><![endif]--> |
|
</head> | </head> |
<body lang="EN-US" link="blue" vlink="blue"> |
<body lang="EN-US" link="blue" vlink="blue"><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
|
name="City"></o:smarttagtype> <o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
|
name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
|
name="date"></o:smarttagtype><!--[if gte mso 9]><xml> |
|
<o:DocumentProperties> <o:Author>IBM_User</o:Author> <o:LastAuthor> </o:LastAuthor> <o:Revision>4</o:Revision> <o:TotalTime>211</o:TotalTime> <o:Created>2004-04-05T14:13:00Z</o:Created> <o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>5026</o:Words> <o:Characters>28651</o:Characters> <o:Company>IBM</o:Company> <o:Lines>238</o:Lines> <o:Paragraphs>67</o:Paragraphs> <o:CharactersWithSpaces>33610</o:CharactersWithSpaces> <o:Version>10.4219</o:Version> </o:DocumentProperties></xml><![endif]--><!--[if gte mso 9]><xml> |
|
<w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:Compatibility> <w:ApplyBreakingRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument></xml><![endif]--> |
<div class="Section1"> | <div class="Section1"> |
<div class="MsoNormal" style="text-align: center;" align="center"><span |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
style="color: black;"> |
<hr color="#009900" align="center" noshade="noshade" size="2" width="100%"></span></div> |
<hr align="center" color="#009900" noshade="noshade" size="2" |
<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;" align="center"><b><span |
width="100%"></span></div> |
style="font-size: 13.5pt; color: black;">OpenPegasus Enhancement |
<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;" |
Proposal (PEP)<o:p></o:p></span></b></p> |
align="center"><b><span style="font-size: 13.5pt; color: black;">Pegasus |
|
Enhancement Proposal (PEP)<o:p></o:p></span></b></p> |
|
|
|
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"> | <p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"> |
|
|
<br> | <br> |
|
<b>PEP #:</b> 364<br> |
<b>PEP #:</b> 306<br> |
|
|
|
</span></p> | </span></p> |
|
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release |
Notes for OpenPegasus 2.7.0</p> |
Notes for OpenPegasus version 2.12.0</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 10 |
|
September 2012<br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 3 October 2007</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" height="155" |
<table class="MsoNormalTable" style="width: 100%;" border="1" cellpadding="0" cellspacing="1" width="100%" height="155" id="table1"> |
border="1" cellpadding="0" cellspacing="1" 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: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
height="27"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
</td> |
|
<td 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> |
|
</td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" |
|
height="27"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span |
|
style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
</td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" |
|
height="27"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span |
|
style="font-family: Arial; color: black;"><o:p> </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: 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> |
|
|
|
</td> |
|
|
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
|
</td> |
|
|
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
|
</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 |
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><font size="2"> 1.0</font><o:p></o:p></span></p> |
style="font-family: Arial; color: black;"><font size="2"> 1.0</font><o:p></o:p></span></p> |
|
|
</td> |
|
|
|
<td style="padding: 0.75pt;" align="left" height="22"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><o:p><font size="2"> </font></o:p></span><font size="2"><span style="font-family: Arial">3 |
|
October 2007</span></font></p> |
|
|
|
</td> | </td> |
|
<td style="padding: 0.75pt;" height="22" align="left"> |
<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;">10 September 2012<br> |
<p class="MsoNormal" style="text-align: center;" align="center"> |
</span></font></p> |
<span style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> |
</td> |
|
<td style="padding: 0.75pt;" height="22" align="left"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"> <span |
|
style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> |
</td> | </td> |
|
|
<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 |
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial |
size="2">Initial Submission <span style="color: red;"></span></font><o:p><font |
Submission</font><o:p><font size="2"> |
size="2"> </font></o:p></span></p> |
</font></o:p></span></p> |
|
|
|
</td> | </td> |
|
|
</tr> | </tr> |
|
|
<tr> | <tr> |
|
<td style="padding: 0.75pt;" height="21" align="center"> 1.01</td> |
<td style="padding: 0.75pt;" align="center" height="21">1.1</td> |
<td style="padding: 0.75pt;" height="21" align="center">10 September |
|
2012 <br> |
<td style="padding: 0.75pt;" align="center" height="21">8 October 2007</td> |
</td> |
|
<td style="padding: 0.75pt;" height="21" align="center">Karl |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td> |
Schopmeyer <br> |
|
</td> |
<td style="padding: 0.75pt;" height="21">Incorporate data from 2.6.1 |
<td style="padding: 0.75pt;" height="21"> Minor fixes and |
release notes. Fix per comments in 1.0</td> |
complete links to PEPs<br> |
|
</td> |
</tr> | </tr> |
|
|
<tr style=""> | <tr style=""> |
|
<td style="padding: 0.75pt;" height="21" align="center"> 1.1</td> |
<td style="padding: 0.75pt;" align="center" height="21">1.2</td> |
<td style="padding: 0.75pt;" height="21" align="center">11 September |
|
2012 <br> |
<td style="padding: 0.75pt;" align="center" height="21">11 October 2007</td> |
</td> |
|
<td style="padding: 0.75pt;" height="21" align="center">Karl |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td> |
Schopmeyer <br> |
|
</td> |
<td style="padding: 0.75pt;" height="21">Comments from V 1.1 and add |
<td style="padding: 0.75pt;" height="21"> Incorporate all |
existing document links. Add pep 302 to enhancements</td> |
comments from first review<br> |
|
</td> |
</tr> | </tr> |
|
|
<tr> | <tr> |
|
<td style="padding: 0.75pt;" height="21" align="center"> 1.2</td> |
<td style="padding: 0.75pt;" align="center" height="21">1.3</td> |
<td style="padding: 0.75pt;" height="21" align="center">18 September |
|
2012 <br> |
<td style="padding: 0.75pt;" align="center" height="21">15 October 2007</td> |
</td> |
|
<td style="padding: 0.75pt;" height="21" align="center">Karl |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td> |
Schopmeyer <br> |
|
</td> |
<td style="padding: 0.75pt;" height="21">Add final links</td> |
<td style="padding: 0.75pt;" height="21"> Fix comments on bug |
|
8830 (compatibility considerations) and bug 9172(repupgrade)<br> |
|
</td> |
</tr> | </tr> |
|
|
<tr style=""> | <tr style=""> |
|
<td style="padding: 0.75pt;" height="23" align="center"> </td> |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
<td style="padding: 0.75pt;" height="23" align="center"> </td> |
|
<td style="padding: 0.75pt;" height="23" align="center"> </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 |
<div class="MsoNormal" style="text-align: center;" align="center"> |
|
<span |
|
style="color: black;"> | style="color: black;"> |
<hr align="center" color="#009900" noshade="noshade" size="2" |
<hr color="#009900" align="center" noshade="noshade" size="2" width="100%"></span></div> |
width="100%"></span></div> |
<p><b>Abstract:</b> This document defines the release notes for the 2.12.0 |
<p><b>Abstract:</b> This document defines the release notes for the |
release of the OpenPegasus CIM Server. The purpose of this PEP is to |
2.7.0 release of the OpenPegasus CIM Server. The purpose of this PEP is |
summarize the characteristics of this release, point to other |
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. </p> |
<div class="MsoNormal" style="text-align: center;" align="center"> |
<div class="MsoNormal" style="text-align: center;" align="center"> <span |
<span |
|
style="color: black;"> | style="color: black;"> |
<hr align="center" color="#009900" noshade="noshade" size="2" |
<hr color="#009900" align="center" noshade="noshade" size="2" width="100%"></span></div> |
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="#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 |
<li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus |
href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus |
Release |
Release Control and Version Definition Documentation</a></li> |
Control and Version Definition Documentation</a></li> |
<li><a href="#General%20Documentation">General |
<li><a href="#General%20Documentation">General Documentation</a></li> |
Documentation</a></li> |
|
</ol> | </ol> |
<h2><span style="color: black;">Availability |
<h2><span style="color: black;">Availability of this Release</span></h2> |
of this Release</span></h2> |
|
<p>This release is available in a number of forms including:</p> | <p>This release is available in a number of forms including:</p> |
<ul> | <ul> |
<li><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 |
<li><b>OpenPegasus source RPMs</b> on the OpenPegasus web site.. A |
href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li> |
source RPM is available on the OpenPegasus web site that can be |
<li><b>OpenPegasus source RPMs</b> on the OpenPegasus web site.. A source RPM is available on the |
used to build binaries for most LSB-compliant RPM-based Linux |
OpenPegasus web site that can be used to build binaries for most LSB-compliant RPM-based Linux distributions and versions.</li> |
distributions and versions.</li> |
<li><b>The Pegasus CVS repository</b>. The CVS tags representing this |
<li><b>TheOpenPegasus CVS repository</b>. The CVS tags representing this |
release and |
release and subsequent snapshots that are made available in the |
subsequent snapshots that are made available in the Pegasus CVS are |
Pegasus CVS are defined on the OpenPegasus CVS repository web page |
defined on the OpenPegasus CVS repository web page (see the <a |
(see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus |
href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus |
CVS |
CVS page</a> for information) using the tags defined on the <a |
page</a> for information) using the tags defined on the <a href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release |
href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release |
snapshots |
snapshots page</a>.</li> |
page</a>.</li> |
</ul> | </ul> |
<p>The instructions for acquiring the released code are on the <a |
<p>The instructions for acquiring the released code are on the <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus |
href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus |
WEB |
WEB site</a>. |
site</a>. Installation instructions are part of the README in the root |
Installation instructions are part of the README in the root of the |
of the Pegasus source tree.</p> |
Pegasus source |
|
tree.</p> |
|
</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. |
using a simple color coded key (white, red, yellow, green) and a description of |
<p>OpenPegasus 2.12.0 is a major release, extending the previous Pegasus |
each feature.<p>Pegasus 2.7.0 |
release in selected areas as described in the Pegasus PEP defining |
is a major release, extending Pegasus 2.6 in selected |
this release . <br> |
areas as described in the Pegasus PEP defining this release |
</p> |
. </p> |
<p>NOTE: OpenPegasus releases are categorized as follows:</p> |
|
<ul> |
<p>The major areas of development for this release were as follows. For |
<li>First number of version changes (ex. 2.x.x to 3.0.0) - Major |
more information access the PEP for each change defined:</p> |
release includes major functionality change and incompatible |
|
behavior changes and/or incompatible public API changes, <br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font size="4"> |
</li> |
Table of Major Changes for this Release</font></p> |
<li>Second number changes (ex 2.11.0 2.12.0) - Minor Release and |
|
includes new functionality but maintains behavior and public API |
|
compatibility, <br> |
<TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666 |
</li> |
borderColorLight=#CCCCCC border=1 width="82%"> |
<li>3rd number changes (2.12.0 to 2.12.1) - Revision(also called point |
<TBODY> |
release) release and only includes bug fixes.</li> |
<TR align="center"> |
</ul> |
<TH bgColor=#00FFFF>PEP #</TH> |
<p><u><b>ALL</b></u> changes for each release are documented in the |
<TH bgColor=#00FFFF>Description of Change</TH> |
OpenPegasus bug data base by tagging each bug(keyword field of |
<TH bgColor=#00FFFF width="128">Posted PEP<br>Version</TH> |
bug). No change to Pegasus is committed with out this tag on the |
</TR> |
bug. Changes for this minor release are tagged 2.12.0_APPROVED. |
<TR align="center"> |
All changes for this minor release can be viewed through this link |
<TD width="7%">284</TD> |
to the OpenPegasus bugzilla <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.0_APPROVED"> |
<TD align="left" width="75%">Add Platform support IBM i5/PASE - Portable Application |
Pegasus 2.12.0_APPROVED bug list. Bugs. </a>Bugs marked as |
Solutions Environment (PASE)</TD> |
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.12.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=[Bug+creation]&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_severity&type0-0-0=equals&value0-0-0=enhancement">link |
<TD width="128"> |
to OpenPegasus bugzilla 2.12.0 enhancement bugs</a> . Bugs fixed |
<a href="http://www.openpegasus.org/pp/uploads/40/14901/PEP284_Porting_Pegasus_to_i5PASE_platform.html"> |
for subsequent revision releases (ex. 2.12.1) would also be viewed |
1.6</a></TD> |
through corresponding Bugzilla tags for each revisions (ex |
</TR> |
2.12.1_APPROVED).<br> |
<TR align="center"> |
</p> |
<TD width="7%">286</TD> |
<p>The major areas of development including both enhancements and bug |
<TD align="left" width="75%">Reduce the Amount of CIM Server code that runs Privileged |
fixes for this release were as follows. Note that the bugs listed |
(Privilege Separation)</TD> |
represent only those features incorporated in bugs without PEPS that are |
<TD width="128"> |
considered enhancements, not all bugs incorporated in the release. For |
<a href="http://www.openpegasus.org/pp/uploads/40/14414/PEP286_PrivilegeSeparation.htm"> |
more information access the PEP/BUG for each change defined below:</p> |
1.8</a></TD> |
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font |
</TR> |
style="font-weight: bold;" size="4"> Table of Major |
<TR align="center"> |
Changes for this Release</font></p> |
<TD width="7%">291</TD> |
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" |
<TD align="left" width="75%">Add Support for IPv6 - Stage 1 (Note: This functionality |
border="1" cellspacing="1" width="82%"> |
was made available but normally disabled |
<tbody> |
<span style="font-family: Arial">Pegasus 2.6.1)</span></TD> |
<tr align="center"> |
<TD width="128"> |
<th bgcolor="#00ffff">PEP/BUG #</th> |
<a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html"> |
<th bgcolor="#00ffff">Description of Change</th> |
1.2</a></TD> |
<th bgcolor="#00ffff" width="128">Posted PEP<br> |
</TR> |
Version</th> |
<TR align="center"> |
</tr> |
<TD width="7%">62</TD> |
<tr> |
<TD align="left" width="75%">Add IPV6 Support for SNMP Indication Handler |
<td align="left">PEP 360</td> |
and include NET-SNMP indication handler in Linux RPM </TD> |
<td>Provider Lifecycle Indications<br> |
<TD width="128"> |
</td> |
<a href="http://www.openpegasus.org/pp/uploads/40/3163/PEP062_SNMPMapper.pdf"> |
<td style="text-align: center;"><a href="https://collaboration.opengroup.org/pegasus/pp/documents/25003/PEP360_PLI_Ver1_2.html">Ver |
1.1</a></TD> |
1.2</a><br> |
</TR> |
</td> |
<TR align="center"> |
</tr> |
<TD width="7%">130</TD> |
<tr align="center"> |
<TD align="left" width="75%">Enable Remote CMPI for Windows</TD> |
<td align="left" width="7%">PEP 361</td> |
<TD width="128"> |
<td align="left" width="75%">cimcli support for embedded instances<br> |
<a href="http://www.openpegasus.org/pp/uploads/40/7775/RemoteCMPI1.2-PEP.html"> |
</td> |
1.2</a></TD> |
<td width="128"><a href="https://collaboration.opengroup.org/pegasus/pp/origrevdocuments/3195/PEP361_CIMCLIEmbeddedInstanceSupport.htm">Ver |
</TR> |
1.1</a><br> |
<TR align="center"> |
</td> |
<TD width="7%">302</TD> |
</tr> |
<TD align="left" width="75%">Enhanced Log File Support</TD> |
<tr> |
<TD width="128"> |
<td align="left" width="7%">PEP 304<br> |
<a href="http://www.openpegasus.org/pp/uploads/40/14902/PEP302_LogFileSupportFinal.html"> |
</td> |
1.0</a></TD> |
<td align="left" width="75%">Allow modification of name of interop |
</TR> |
namespace<br> |
<TR align="center"> |
</td> |
<TD width="7%">258</TD> |
<td style="text-align: center;" width="128"><a href="http://www.openpegasus.org/pp/uploads/40/23237/PEP_357_-_SNMP_v3_trap_generation_in_Pegasus_.htm"></a><a |
<TD align="left" width="75%">Add support for certificate-based authentication audit |
href="https://collaboration.opengroup.org/pegasus/pp/documents/24686/PEP304_NamespaceRenaming.htm">Ver |
logging</TD> |
1.5</a><br> |
<TD width="128"> |
</td> |
<a href="http://www.openpegasus.org/pp/uploads/40/14428/PEP258_AuditLogging.htm"> |
</tr> |
1.5</a></TD> |
<tr> |
</TR> |
<td align="left">PEP 358<br> |
<TR align="center"> |
</td> |
<TD width="7%">Bugzilla 6466</TD> |
<td>WSMan indication handling and subscription support<br> |
<TD align="left" width="75%">Add two new trace components to facilitate |
</td> |
triage of indication delivery issues</TD> |
<td align="center"><a href="https://collaboration.opengroup.org/pegasus/pp/documents/26240/PEP_358_-_WSMAN_Eventing_support_in_Pegasus_.htm">Ver |
<TD width="128"> |
1.1</a><br> |
<a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=6466"> |
</td> |
Bug 6466</a></TD> |
</tr> |
</TR> |
<tr> |
</TBODY> |
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8891">Bug |
</TABLE> |
8891</a><br> |
</html> |
</td> |
|
<td>Enhance cimsub to add operations to create filters, destinations |
|
and subscriptions<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" align="left" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=5667">Bug |
|
5667</a><br> |
|
</td> |
|
<td align="left" width="75%">Remove experimental form buildInstance |
|
and filter functions in CIMInstance class<br> |
|
</td> |
|
<td width="128"><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8952">Bug |
|
8952</a></td> |
|
<td> Support Configurable cipher suites in OpenPegasus</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8904">Bug |
|
8984</a></td> |
|
<td>Add support for indication deliver connection pooling</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9008">Bug |
|
9008</a></td> |
|
<td>Add new Indication runtime configuration variables: |
|
maxIndicaitonDeliveryRetry Attempts and |
|
minIndicationdeliveryRetryInterval</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" align="left" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9013">Bug |
|
9013</a><br> |
|
</td> |
|
<td align="left" width="75%"><span style="color: windowtext;"><span |
|
style=""></span></span>Enable ordered indication delivery from |
|
provider through CIMServer when |
|
PEGASUS_ENABLE_DMTF_INDICATION_PROFILE compile flag is set</td> |
|
<td width="128"> <a href="http://www.openpegasus.org/pp/uploads/40/22386/PEP_349_-_Improve_the_availability_of_the_CIMOM_by_better_isolation_from_faulty_providers.htm"></a><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;" align="left"> <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8800">Bug |
|
9080 </a></td> |
|
<td> <span class="norm"></span>Guaranteed provider lifecycle |
|
indication delivery during CIMServer shutdonw </td> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9112">Bug |
|
9112</a><br> |
|
</td> |
|
<td>Advertise IndicationService conformance to Indications Profileby |
|
imlementing CIM_ElementConformsToProfile when |
|
PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9114">Bug |
|
9114</a><br> |
|
</td> |
|
<td>Advertise DMTF Indications Profile (DSP1054) 1.1.0 conformance </td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9118">Bug |
|
9118</a><br> |
|
</td> |
|
<td>Add support for CIM_IndicationFilter.SourceNamespaces[] property<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9136">Bug |
|
9136</a></td> |
|
<td>Runtime configuration option to restrict cimserver to listen on |
|
selected network interfaces</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9155">Bug |
|
9155</a><br> |
|
</td> |
|
<td>Update to include CIM 2.31 Schema and set this as default schema<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9159">Bug |
|
9159</a></td> |
|
<td> |
|
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" |
|
border="1" cellspacing="1" width="82%"> |
|
<tbody> |
|
<tr> |
|
<td>Add SSL Support to Dynamic Listener<br> |
|
</td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9172">Bug |
|
9172</a><br> |
|
</td> |
|
<td>Add capability for administrator to override hostname used by |
|
providers. This adds new runtime configuration variable |
|
hostname and fullyQualifiedHostName. It is necessary to upgrade |
|
existing repositories using repupgrade utility when upgrading from |
|
OpenPegasus less that 2.12.0 and reusing an existing repository.<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9215">Bug |
|
9215</a><br> |
|
</td> |
|
<td>Add support of CQL query language to ExecQuery operation in |
|
general. When the server receives ExecQuery it executes |
|
enumerate instance for providers that do not support ExecQuery and |
|
filters result.<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9209">Bug |
|
9209 </a><br> |
|
</td> |
|
<td>Add operations for display class tree and counting instances to |
|
cimcli<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9227">Bug |
|
9227</a><br> |
|
</td> |
|
<td>Enhance cimsub for batches of subscription oriented operations<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9229">Bug |
|
9229</a><br> |
|
</td> |
|
<td><a name="comtag_197">Add gcc build support on hp-ux for the |
|
Common, Client and General libraries.</a></td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9236">Bug |
|
9236</a></td> |
|
<td>Support for clang/clang++ compiler on Linux. This version |
|
supports only X86 and X86_64 and requires clang version 3 or |
|
greater.<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
</tbody> |
|
</table> |
<p>The status of several components of Pegasus functionality change status | <p>The status of several components of Pegasus functionality change status |
between Pegasus versions. <span class="norm"><a name="comtag_116">Features that |
between Pegasus versions. <span class="norm"><a name="comtag_116">Features |
have changed status can be identified by a change in color from the previous |
that |
release to this release</a></span> on the |
have |
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>.</p> |
changed status can be identified by a change in color from the |
|
previous release to this release</a></span> on the <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature |
<p>Finally, a significant number of internal changes and corrections were made |
Status WEB Page</a>.</p> |
under the control of the Pegasus bugzilla bug system. See the bug section below |
<h3><b>Information on Interop namespace name (root/PG_InterOp) for |
for more information.</p> |
OpenPegasus 2.12<br> |
|
</b></h3> |
|
<p>Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable |
|
to define "root/PG_InterOp" as the name for the OpenPegasus namespace |
|
with no defined way to change this variable. Note that an |
|
unsupported method involving editing one file and rebuilding OpenPegasus |
|
was defined as a workaround in the <a href="%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus |
|
wiki faq</a>s. <br> |
|
</p> |
|
<p>However, since the definition of a standard name for this namespace in |
|
DMTF and SNIA specifications ("interop" or "root/interop" with "interop" |
|
being the preferred alternative) the use of "root/PG_InterOp" has |
|
become an issue.<br> |
|
</p> |
|
<p>Effective OpenPegasus 2.12.0 a new build variable has been |
|
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.<br> |
|
</p> |
|
<p>However, today OpenPegasus is committed to the single namespace defined |
|
at build "(root/PG_InterOp", "interop", or "root/interop"). However, a |
|
number of OpenPegasus installations are committed to the |
|
"root/PG_InterOp" name and must maintain their repositories through |
|
updates of OpenPegasus. While we are working on this issue today (which |
|
means that a running version of OpenPegasus must accept both the and new |
|
names and not confuse clients, listeners or providers that would use |
|
either name) the OpenPegasus team did not complete that work for this |
|
release. See bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9250">9250</a> |
|
for more information about possible solutions and our progress on a |
|
solution.<br> |
|
</p> |
|
<p>NOTE: If you redefine the interop namespace name with |
|
PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp" namespace |
|
will not connect with the updated version of OpenPegasus. <br> |
|
</p> |
|
<h3><font color="#000000"></font></h3> |
<h3><font color="#000000">Information on IPv6 Support (PEP 291)</font></h3> | <h3><font color="#000000">Information on IPv6 Support (PEP 291)</font></h3> |
<p style="color: rgb(153, 51, 153);"><font color="#000000">IPv6 is short for "Internet |
<p><b>NOTE:</b> This functionality was incorporated in OpenPegasus 2.7.0 |
Protocol |
but it was felt that the information below was worth repeating in |
Version 6". IPv6 is the "next generation" protocol designed by the IETF |
subsequent Release Notes</p> |
to replace the current version Internet Protocol, IP Version 4 |
<p style="color: rgb(153, 51, 153);"><font color="#000000">IPv6 is short |
("IPv4"). IPv6 Support for OpenPegasus is documented in </font> <a |
for "Internet Protocol Version 6". IPv6 is the "next generation" |
href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html"> |
protocol designed by the IETF to replace the current version Internet |
<font color="#3333FF">PEP |
Protocol, IP Version 4 ("IPv4"). IPv6 Support for OpenPegasus is |
291</font></a><font color="#000000">.</font></p> |
documented in </font> <a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html"> |
<p>The IPv6 support in OpenPegasus is |
<font color="#3333ff">PEP 291</font></a><font color="#000000">.</font></p> |
controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this |
<p>The IPv6 support in OpenPegasus is controlled by the |
variable is "true"; setting this to |
PEGASUS_ENABLE_IPV6 build variable. The default for this variable is |
'false' before building OpenPegasus will disable the IPv6 support.<br> |
"true"; setting this to 'false' before building OpenPegasus will disable |
|
the IPv6 support.<br> |
</p> | </p> |
<p>The following subsections provide |
<p>The following subsections provide some information on IPv6 support for |
some information on IPv6 support for the Linux and Windows platforms. |
the Linux and Windows platforms. Note that in the 2.6.1 release there is |
Note that in the 2.6.1 release there is no automatic run-time detection |
no automatic run-time detection of IPv6 support on a platform by |
of IPv6 support on a platform by OpenPegasus. If you build with |
OpenPegasus. If you build with PEGASUS_ENABLE_IPV6=true, your platform |
PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you will |
must support IPv6 or you will get a build failure (missing header |
get a build failure (missing header files), a run-time bind() failure, |
files), a run-time bind() failure, or possibly some other failure. This |
or possibly some other failure. This applies to both the CIM Server and |
applies to both the CIM Server and Listener components. For more |
Listener components. For more information on IPv6 support for your |
information on IPv6 support for your specific platform, refer to the |
specific platform, refer to the documentation for that platform.<br> |
documentation for that platform.<br> |
</p> | </p> |
<p>All OpenPegasus externals that |
<p>All OpenPegasus externals that support either a hostname or an IP |
support either a hostname or an IP address as input have been updated |
address as input have been updated to allow an IPv6 address to be |
to allow an IPv6 address to be specified. If the required input is just |
specified. If the required input is just an IP address (eg. no optional |
an IP address (eg. no optional or required port number), then the IPv6 |
or required port number), then the IPv6 address must be specified |
address must be specified without brackets. For example, the |
without brackets. For example, the OpenPegasus osinfo client (which |
OpenPegasus osinfo client (which returns information about the OS |
returns information about the OS running on a host system) takes |
running on a host system) takes separate host and port options. In this |
separate host and port options. In this case a host with an |
case a host with an IPv6-configured network interface would be |
IPv6-configured network interface would be specified as:<br> |
specified as:<br> |
|
</p> | </p> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);"><font color="#000000">osinfo -h |
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font |
3ffe:1:2:1 -p 5988</font></div> |
color="#000000">osinfo -h 3ffe:1:2:1 -p 5988</font></big></div> |
<p>But the cimcli command, which |
<p>But the cimcli command, which takes an optional "location" option |
takes |
including an optional port number, requires the IPv6 address to be |
an optional "location" option including an optional port number, |
delimited with brackets, for example:<br> |
requires the IPv6 address to be delimited with brackets, for example:<br> |
|
</p> | </p> |
<div style="margin-left: 40px;">cimcli ns -l [3ffe:1:2:1]</div> |
<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;">cimcli ns -l [3ffe:1:2:1]:5989<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 |
2373 - IP Version 6 Addressing Architecture</a> and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF |
href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP Version |
RFC 2732 - Format for Literal IPv6 Addresses in URL's</a>.<br> |
6 Addressing Architecture</a> |
|
and <a |
|
href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 - Format for |
|
Literal IPv6 Addresses in URL's</a>.<br> |
|
<h4><font color="#000000">IPv6 on Linux</font></h4> | <h4><font color="#000000">IPv6 on Linux</font></h4> |
<p>Modern Linux distributions already |
<p>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 |
IPv6 capability is generally compiled as a module, but it's possible |
this module is not loaded automatically on startup.</p> |
that this module is not loaded automatically on startup.</p> |
<p><span style="font-weight: bold;">Note: </span>you shouldn't use |
<p>Note: |
kernel series 2.2.x, because it's not IPv6-up-to-date anymore. Also the |
you shouldn't anymore use kernel series 2.2.x, because it's not |
IPv6 support in series 2.4.x is no longer improved according to |
IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no |
definitions in latest RFCs. It's recommend to use series 2.6.x now.<br> |
longer improved according to definitions in latest RFCs. It's recommend |
|
to use series 2.6.x now.<br> |
|
</p> | </p> |
<p>To check whether your current |
<p>To check whether your current running kernel supports IPv6, take a look |
running |
into your /proc filesystem. The entry /proc/net/if_inet6 must exist. A |
kernel supports IPv6, take a look into your /proc filesystem. The entry |
short automated test looks like:<br> |
/proc/net/if_inet6 must exist. A short automated test looks like:<br> |
|
</p> | </p> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);"><font color="#000000">test -f |
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font |
/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"</font></div> |
color="#000000">test -f /proc/net/if_inet6 && echo "Running |
<p>For more information on |
kernel is IPv6 ready"</font></big></div> |
enabling |
<p>For more information on enabling IPv6 in the Linux kernel and |
IPv6 in the Linux kernel and configuring network interfaces, refer to |
configuring network interfaces, refer to <a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The |
<a |
Linux Documentation Project's IPv6 HOWTO</a>.<br> |
href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux |
|
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 |
is seen intermittently on RHEL5 and SLES10 systems. This problem is |
on RHEL5 and SLES10 systems. This problem is described in <span style="color: rgb(153, 51, 153);"> |
described in <span |
<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
style="color: rgb(153, 51, 153);"> |
bug |
<a |
6586</a> </span>and<span style="color: rgb(153, 51, 153);"> <a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat |
href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
bug |
bug 6586</a> |
248052</a>, </span>and manifests itself as an intermittent IPv6 |
</span> |
socket failure. You should be aware that OpenPegasus with IPv6 enabled |
and<span |
may be significantly impacted in these environments.</p> |
style="color: rgb(153, 51, 153);"> |
|
<a |
|
href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat |
|
bug 248052</a>, |
|
</span> |
|
and manifests itself as an intermittent IPv6 socket failure. You should be aware |
|
that OpenPegasus with IPv6 enabled may be significantly impacted in these |
|
environments.</p> |
|
<h4><font color="#000000">IPv6 on Windows</font></h4> | <h4><font color="#000000">IPv6 on Windows</font></h4> |
<p>Microsoft provides supported IPv6 |
<p>Microsoft provides supported IPv6 implementations for Windows Server |
implementations for Windows Server |
2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service Pack |
2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service |
2 (SP2), and Windows CE .NET 4.1 and later.</p> |
Pack 2 (SP2), and Windows CE .NET 4.1 and later.</p> |
On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span> |
On Windows XP, you can use the <span |
tool to install, uninstall, and query your IPv6 configuration. For |
style="font-weight: bold; ">ipv6.exe</span> tool to install, uninstall, and |
example:<br> |
query |
|
your IPv6 configuration. For example:<br> |
|
<br> | <br> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);"><font color="#000000">ipv6 install<br> |
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font |
ipv6 if</font></div> |
color="#000000">ipv6 install<br> |
<p>Windows Vista |
ipv6 if</font></big></div> |
and Windows Server 2008 support an integrated |
<p>Windows Vista and Windows Server 2008 support an integrated IPv4 and |
IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack. |
IPv6 implementation known as the Next Generation TCP/IP stack. Note that |
Note that the OpenPegasus IPv6 support has not yet been tested |
the 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 |
installing, configuring, and using IPv6 on Windows platforms, refer to |
Windows platforms, refer to the document <a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"><font |
the document |
color="#000000">IPv6 for Microsoft Windows: Frequently Asked |
<a |
Questions</font></a>.<br> |
href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"> |
|
<font color="#000000">IPv6 |
|
for Microsoft Windows: Frequently Asked Questions</font></a>.<br> |
|
</p> | </p> |
<h4><font color="#000000">Testing your OpenPegasus IPv6 |
<h4><font color="#000000">Testing OpenPegasus IPv6 support</font></h4> |
support</font></h4> |
As part of the OpenPegasus automated tests, the TestClient, g11ntest, and |
As part of the OpenPegasus |
IndicationStressTest test clients were modified to run tests using the |
automated tests, the TestClient, g11ntest, and IndicationStressTest |
IPv6 loopback address (::1) if PEGASUS_ENABLE_IPV6=true.<br> |
test clients were modified to run tests using the IPv6 loopback address |
|
(::1) if PEGASUS_ENABLE_IPV6=true.<br> |
|
<br> | <br> |
You can also perform manual |
You can also perform manual tests using the IPv6 loopback or a real |
tests |
IPv6-configured network interface. For example, using the IPv6 loopback on |
using the IPv6 loopback or a real IPv6-configured network interface. |
a system with OpenPegasus running on the WBEM standard http port of 5988:<br> |
For example, using the IPv6 loopback on a system with OpenPegasus |
|
running on the WBEM standard http port of 5988:<br> |
|
<div style="margin-left: 40px;"><br> | <div style="margin-left: 40px;"><br> |
osinfo -h ::1</div> |
<big style="font-family: monospace;"> osinfo -h ::1</big></div> |
<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2> | <h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2> |
<p>Support for forward-compatibility is a fundamental design principle for the |
<p>Support for forward-compatibility is a fundamental design principle for |
OpenPegasus project. As a Community, our goal is for well-behaved OpenPegasus |
the OpenPegasus project. As a community, our goal is for well-behaved |
Providers or Clients, using only the externally defined OpenPegasus interface, |
OpenPegasus providers or clients, using only the externally defined |
to continue to work with a minor version upgrade of OpenPegasus. However, there |
OpenPegasus interface, to continue to work with a minor version upgrade |
are certain classes of errors (e.g., non-compliance with a standard that |
of OpenPegasus. However, there are certain classes of errors (e.g., |
significantly affects interoperability) that may require the Community to make |
non-compliance with a standard that significantly affects |
potentially incompatible changes. The following table contains a list of defect |
interoperability) that may require the community to make potentially |
fixes that MAY impact, even well-behaved, OpenPegasus Providers or Clients when |
incompatible changes. The following table contains a list of |
upgrading to OpenPegasus 2.7.0.</p> |
defects/fixes that MAY impact, even well-behaved, OpenPegasus providers |
<TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666 |
or clients when upgrading to this OpenPegasus release. <br> |
borderColorLight=#CCCCCC border=1 width="80%"> |
</p> |
<TBODY> |
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" |
<TR align="center"> |
border="1" cellspacing="1" width="80%"> |
<TH bgColor=#00FFFF width=10%>Bugzilla #</TH> |
<tbody> |
<TH bgColor=#00FFFF>Description</TH> |
<tr align="center"> |
</TR> |
<th bgcolor="#00ffff" width="10%">Bugzilla #</th> |
<TR align="center"> |
<th bgcolor="#00ffff">Description</th> |
<TD>6476</TD> |
</tr> |
<TD align="left"><font face="Times New Roman">HP-UX only: Introduction of the "explicit" keyword in CIMClass.h and CIMInstance.h may introduce |
<tr align="center"> |
a compile error in some code. Specifically, a compiler-supplied automatic conversion from CIMObject |
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8830">Bug |
type to CIMClass or CIMInstance has been removed. The cast operation must be explicitly specified. |
8830</a></td> |
</font> |
<td align="left">Starting with OpenPegasus 2.11.0 the requirement |
</TD> |
for providers (CMPI and C++) to filter properties from instances |
</TR> |
has been relieved. The server will do the filtering at the |
<TR align="center"> |
protocol adapter level. To avoid a negative impact on performance |
<TD>6608</TD> |
the CIMInstance::filter() and CMPIInstanceFT.setPropertyFilter() |
<TD> |
functions have been changed to a NOP. This may be a change in |
<p align="left">WIPCR00430 recommends an unquoted charset parameter in Content-type header. See the writeup in this bug for a discussion of the validation of the charset parameter in various OpenPegasus releases. In 2.7 we perform "extended" validation that should ignore differences based on whitespace or quotes. The CR recommendation is to not use quotes on the charset parameter, but only at a time when it is expected that all CIMOMs have been updated to accept the charset parameter with or without quotes.</TD> |
behavior for provider relying in some unknown way on the instance |
</TR> |
being filtered through these functions. To allow users to actually |
<TR align="center"> |
filter properties from an instance, new function |
<TD>6458/6770</TD> |
CIMInstance::filterInstance() will actually filter properties from |
<TD> |
an instance exactly as the CIMInstance::filter() did in previous |
<p align="left">The MOF Compiler now rejects some property values that are invalid according to the DMTF specification that it previously accepted.</TD> |
versions of Pegasus.</td> |
</TR> |
</tr> |
</TBODY> |
<tr align="center"> |
</TABLE> |
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9369">Bug |
</html> |
9369</a><br> |
|
</td> |
|
<td align="left">Reregistering of an indication provider requires |
<h2>OpenPegasus Relationship to |
that the cimserver be restarted to send the enableIndication |
CIM/WBEM Standards</h2> |
request to the providers. This issue has existed starting with |
<p>Pegasus was designed and implemented to comply with the DMTF |
OpenPegasus 2.10 to the current version. If the cimserver is not |
CIM/WBEM specifications The following table defines the level of the |
restarted the indication will not be enabled for the reregistered |
DMTF specifications to which this version of Pegasus aims to conform |
provider. </td> |
today.</p> |
</tr> |
|
</tbody> |
|
</table> |
|
<h2>OpenPegasus Relationship to CIM/WBEM Standards</h2> |
|
<p>Pegasus was designed and implemented to comply with the DMTF CIM/WBEM |
|
specifications The following table defines the level of the DMTF |
|
specifications to which this version of Pegasus aims to conform today.</p> |
<table id="AutoNumber1" border="1" cellspacing="1" width="80%"> | <table id="AutoNumber1" border="1" cellspacing="1" width="80%"> |
<tbody> | <tbody> |
<tr> | <tr> |
|
|
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0200 - CIM Operations over HTTP</td> | <td width="33%">DSP 0200 - CIM Operations over HTTP</td> |
<td width="33%">1.2.0, preliminary, 9 December 2004</td> |
<td width="33%">Version 1.2, Final, January 09, 2007</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0201 - Representation of CIM in XML</td> | <td width="33%">DSP 0201 - Representation of CIM in XML</td> |
<td width="33%">2.2.0, preliminary, December 2004</td> |
<td width="33%">Version 2.2 Final, January 09, 2007</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0202 - CIM Query Language Specification</td> | <td width="33%">DSP 0202 - CIM Query Language Specification</td> |
|
|
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">CIM Schema </td> | <td width="33%">CIM Schema </td> |
<td width="33%">2.13.1 Final, Jan. 2005 ( default) </td> |
<td width="33%">2.31.0 Final ( default) </td> |
|
</tr> |
|
<tr> |
|
<td>DSP0226 - Web Services for Management<br> |
|
</td> |
|
<td>Version 1.1.1<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td>DSP0227 - WS-Management CIM Binding Specification<br> |
|
</td> |
|
<td>Version 1.2.0<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td>DSP0230 - WS-CIM Mapping Specification </td> |
|
<td>Version 1.1.0<br> |
|
</td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<h2><a name="Conformance with DMTF Specifications">Conformance |
<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIS SMI |
Exceptions to |
Profiles Supported</h2> |
DMTF Specifications</a></h2> |
<p>Today OpenPegasus includes support for several DMTF profiles including |
<p>It is a major goal |
the ones defined below:</p> |
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 1.0.0</li> |
through a set of Pegasus Provider registration classes rather than |
<li>DMTF Indications 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 |
|
PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.<br> |
|
</li> |
|
<li>SNIA Profile Registration 1.0.0</li> |
|
<li>SNIA Server 1.1.0 & 1.2.0<br> |
|
</li> |
|
</ol> |
|
<h2><a name="Conformance with DMTF Specifications">Conformance Exceptions |
|
to DMTF Specifications</a></h2> |
|
<p>It is a major goal of the OpenPegasus project to both drive and utilize |
|
the DMTF CIM/WBEM specifications. However, today there are a |
|
number of known differences. As of this release, some of the |
|
differences include the following:</p> |
|
<ol> |
|
<li><b>Provider Registration</b> - Pegasus supports registration through |
|
a set of Pegasus Provider registration classes rather than support the |
|
DMTF defined Provider Qualifier. Pegasus will not support this |
|
qualifier in the future. See the readme for more information on |
provider registration. This is not a deviation from the | provider registration. This is not a deviation from the |
specifications but is a different method of registration than many CIM | specifications but is a different method of registration than many CIM |
Servers and means that the the provider qualifier is unused in Pegasus.</li> |
Servers and means that the the provider qualifier is unused in |
<li><b>Indications </b>-Today Pegasus supports process |
Pegasus.</li> |
|
<li><b>Lifecycle Indications </b>-Today Pegasus supports process |
indications and lifecycle indications when defined specifically by | indications 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 |
not defined by the provider or for changes to CIM Classes.<font color="#ff0000"> |
color="#ff0000"> </font><span class="norm"><font color="#ff0000"> </font>For |
</font><span class="norm"><font color="#ff0000"> </font>For more |
more information see the Pegasus CVS file:<a name="comtag_137"><font size="2"> |
information see the Pegasus CVS file:<a name="comtag_137"><font size="2"> |
</font><font |
</font><font face="Courier New" size="2"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a><font |
face="Courier New" size="2"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a><font size="2">.</font></span></li> |
size="2">.</font></span></li> |
<li> | <li> |
<p class="MsoNormal"><font |
<p class="MsoNormal"><font style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers |
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 Specification and |
instance operations with the 1.2 CIM Operations Specification. |
stated specifically that the client should NOT depend on the |
Some CIM Client implementations expect instances |
includeQualifiers parameter of the CIM/XML instance operations |
returned |
returning qualifiers. Some CIM Client implementations expect |
from the CIM Server to include the qualifiers defined in the class |
instances returned from the CIM Server to include the qualifiers |
definition (such as KEY qualifiers on properties). </span> Pegasus |
defined in the class definition (such as KEY qualifiers on |
today expects the provider to complete the qualifiers on instances in |
properties). </span> Pegasus today expects the |
accordance with the specification and generally the interpretation is |
provider to complete the qualifiers on instances in accordance with |
that Pegasus applies class level qualifiers when the includeInstance |
the specification and generally the interpretation is that Pegasus |
parameter is supplied on instance operations. However, Pegasus |
applies class level qualifiers when the includeInstance parameter is |
today is inconsistent in the return of qualifiers so that the user |
supplied on instance operations. However, Pegasus today is |
should NOT depend on Pegasus accurately honoring the includeQualifier |
inconsistent in the return of qualifiers so that the user should NOT |
parameter for instance operations. In the future it is expected |
depend on Pegasus accurately honoring the includeQualifier parameter |
that Pegasus will deprecate the use of qualifiers on instance |
for instance operations. In the future it is expected that |
operations completely.<font color="#ff0000"> </font></p> |
Pegasus will deprecate the use of qualifiers on instance operations |
|
completely. When Pegasus uses object normalization, the |
|
normalizer does apply qualifiers to returned instances if the |
|
includeQualifiers operation parameter is set.</p> |
</li> | </li> |
<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> |
<p class="MsoNormal"><b>MultiRequest Operations</b> - Pegasus |
<p class="MsoNormal"><b>MultiRequest Operations</b> - Pegasus does not |
does not support the DMTF defined MultiRequest Operation option.</p> |
support the DMTF defined MultiRequest Operation option.</p> |
</li> | </li> |
<li> | <li> |
<p class="MsoNormal"><b>MOF Compiler namespace pragma</b> - The | <p class="MsoNormal"><b>MOF Compiler namespace pragma</b> - The |
Pegasus compiler does not support the namespace pragma.</p> | Pegasus compiler does not support the namespace pragma.</p> |
</li> | </li> |
<li>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 |
1.2 final specification as a non-compatible change so that if chunking |
href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> for more details.<br> |
is used Pegasus is returning a noncompliant response to enumerate type |
|
requests. </li> |
|
<li><span style="font-weight: bold;">Whitespace in XML value Element</span> |
|
- Pegasus trims the leading and trailing whitespace from XML value |
|
elements that are of the Type String. This behavior is |
|
documented in Pegasus bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8773">8773</a> |
|
and there is a patch available for users. However, since the |
|
change is considered a change to behavior this will not be patched |
|
until pegasus does a major version update. NOTE: There are some |
|
documented bugs in Pegasus such as this that the OpenPegasus team |
|
feels cannot be incorporated into the code until a major version |
|
update. These bugs are documented with the Bugzilla tag <big style="font-weight: bold;"><samp>"3.0_TARGET".</samp></big></li> |
|
<li><span style="font-weight: bold;">modifyInstance operation behavior |
|
in the Pegasus repository does not match the DMTF specification</span>. |
|
Under some conditions (ex. if no propertyList is supplied) it modifies |
|
all properties rather than just the properties supplied with the |
|
request thereby Nulling out existing values. See bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8752">8752</a> |
|
for more information.</li> |
|
<li><b>OpenPegasus Interop Namespace</b> - The default interop namespace |
|
name in OpenPegasus is "root/PG_Interop". In versions of |
|
OpenPegasus prior to 2.12.0 this could be changed during build by |
|
modifying a string definition in the code. Effective version 2.12 |
|
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"<br> |
|
</li> |
|
<li><b>OpenPegasus WSMAN protocol on windows does not handle NaN, INF, |
|
or -INF</b> (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 |
<h2><b><span style="font-family: Times;">OpenPegasus <a name="Supported Platforms">Supported |
name="Supported Platforms">Supported |
|
Platforms</a></span></b></h2> | Platforms</a></span></b></h2> |
<p>Each OpenPegasus release lists as 'active' platforms those |
<p align="left">Each OpenPegasus release lists as 'active' platforms those |
hardware/software platforms that have recognized ports for the Pegasus | hardware/software platforms that have recognized ports for the Pegasus |
code |
code base including a maintainer for the platform that will be willing |
base including a maintainer for the platform that will be willing to |
to regularly document issues and/or fix defects as the Pegasus code base |
regularly document issues and/or fix defects as the Pegasus |
is changed. Pegasus may be operable on other platforms (ex. |
code base is changed. |
Windows 98) but without a group to provide the role of test and |
Pegasus may be operable on other platforms (ex. Windows 98) but without |
maintenance, correct operation of Pegasus cannot be assured. |
a group |
In all cases, including the active platforms, it is the responsibility |
to provide the role of test and maintenance, correct operation of |
of the entity that packages and/or compiles OpenPegasus for shipment or |
Pegasus cannot be |
deployment, to read, and actively monitor the Pegasus Bugzilla database |
assured. In all cases, including the active platforms, it is the |
for a list of relevant defects that affect their platform. |
responsibility of the entity that packages and/or compiles OpenPegasus |
The platforms that are considered ported are shown in the two tables |
for shipment or deployment, to read, and actively monitor the Pegasus |
below. The first table represents platform for which testing is |
bugzilla database for a list of relevant defects that affect their |
done on a regular basis and reported to the Pegasus Nightly Build Test |
platform. The platforms that are considered 'active' for this |
WEB Page. Those platforms which have been ported but do not have test |
Pegasus release are:<br> |
results that are current at the time of the release are reported in the |
</p> |
second table.</p> |
<table class="MsoNormalTable" style="width: 90%;" border="1" |
<b>Actively Supported Platforms (Nightly Tests Reported for this release)</b> |
cellpadding="0" cellspacing="1"> |
<table class="MsoNormalTable" style="width: 90%;" border="1" cellpadding="0" |
|
cellspacing="1"> |
<tbody> | <tbody> |
<tr style=""> | <tr style=""> |
<td |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;" |
style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;" |
|
height="26"> | height="26"> |
<p class="MsoNormal"><b><span style="color: black;">Platform and | <p class="MsoNormal"><b><span style="color: black;">Platform and |
OS</span></b><span style="color: black;"><o:p></o:p></span></p> | OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;" |
style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;" |
|
height="26"> | height="26"> |
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span | <p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span |
style="color: black;"><o:p></o:p></span></p> | style="color: black;"><o:p></o:p></span></p> |
|
|
</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></o:p></span></p> |
<p class="MsoNormal"><span style="color: black;">HP-UX<o:p> |
|
PA_RISC and Itanium</o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span style="color: black;">HP <span |
<p class="MsoNormal"><span style="color: black;">HP <span class="SpellE">aC</span>++ |
class="SpellE">aC</span>++ B3910B<o:p></o:p></span></p> |
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 |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">Linux |
style="color: black;">Linux on Power</span></span><span |
on Power</span></span><span style="color: black;"><o:p></o:p></span></p> |
style="color: black;"><o:p></o:p></span></p> |
|
</td> | </td> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span |
style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">zLinux</span></span><span |
style="color: black;">zLinux</span></span><span style="color: black;"><o:p></o:p></span></p> |
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span |
style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
|
|
<p class="MsoNormal"><span style="color: black;">Linux Itanium<o:p></o:p></span></p> | <p class="MsoNormal"><span style="color: black;">Linux Itanium<o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span |
style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; "> |
<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 |
<span class="SpellE"><span |
size="3">gcc</font></span></span><span style="color: black;"><font |
style="color: black;"><font size="3">gcc</font></span></span><span style="color: black;"><font size="3"> |
size="3"> (versions 3.xx, 4.xx) clang(The clang compiler usage |
(versions 2.9x, 3.xx, 4.xx)</font><o:p></o:p></span></td> |
is considered experimental and is not part of the nightly |
|
tests today)</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 |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span |
style="color: black;">gcc</span></span><span style="color: black;"> |
style="color: black;"> (versions 3.xx, 4.xx) </span><span style="color: black;"><font |
(versions 2.9x, 3.xx, 4.xx)</span></p> |
size="3">clang(The clang compiler usage is considered |
|
experimental and is not part of the nightly tests today)</font></span></p> |
</td> | </td> |
</tr> | </tr> |
|
<tr> |
|
<td style="vertical-align: top;"><font size="3">z/OS V1.7 and up</font></td> |
|
<td style="vertical-align: top;"><font size="3">XL C/C++ from z/OS |
|
Version 1.7 and up</font></td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
|
|
<p align="center"><b>Platforms not Actively supported for this release (No |
|
current Nightly Build Test Results</b></p> |
|
<table class="MsoNormalTable" style="width: 90%;" id="table2" border="1" cellpadding="0" |
|
cellspacing="1"> |
|
<tbody> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; "> |
<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;" |
<p class="MsoNormal"><span style="color: black;">Windows 2000</span></p> |
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Platform and |
|
OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;" |
|
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; "> |
|
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler version. Works on VC .NET 2003 v7.1). |
|
NOTE: Visual C++ Ver. 6 no longer being regularly tested.</font></td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="padding: 0.75pt; "> <font size="3">Windows XP, Windows 2003</span></font></p> |
<td style="padding: 0.75pt;"> <font size="3">Windows XP, Windows |
</td> |
Vista, Windows 7, Windows Server 2008</font> |
<td style="padding: 0.75pt; "> |
<p></p> |
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1. |
</td> |
Note: Visual C++ Ver. 6 no longer being regular tested. |
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
</font> |
Compilers 2003 - 2010.. Note: Visual C++ Ver. 6 no longer being |
</td> |
regular tested.Note that today there are some open issues with |
|
the Windows.</font> </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>HP OpenVMS 8.3 or later Alpha</big></td> |
<td style="vertical-align: top;"><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris |
<td style="vertical-align: top;"><font size="3"> </font><big><font |
8</span></font></big></td> |
style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun CC |
style="color: rgb(153, 51, 153);">7.3-009 or later required</span> for OpenVMS |
compiler V 5.8. Note that the latest thread patch (108993) may |
Alpha</font></big></td> |
be required. (see Pegasus bug 4632)</big><br> |
|
</td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later IA64</font></big></td> |
|
<td style="vertical-align: top;"><span class="norm"></span><big><font | <td style="vertical-align: top;"><span class="norm"></span><big><font |
style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 or |
color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9</span></font></big></td> |
later required</font><font |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun WorkShop |
style="color: rgb(0, 0, 0);"> on OpenVMS IA64</font></big></td> |
6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><big>HP OpenVMS 8.3 or later Alpha</big></td> |
|
<td><big><font style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span |
|
style="color: rgb(153, 51, 153);">7.3-009 or later required</span> |
|
for OpenVMS Alpha</font></big></td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><font color="RED"><span |
<td><big><font style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later |
style="color: rgb(0, 0, 0);">Solaris 8</span></font></big></td> |
IA64</font></big></td> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
<td><big><font style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 |
CC compiler V 5.8. Note that the latest thread patch (108993) may be |
or later required</font><font style="color: rgb(0, 0, 0);"> on |
required. (see Pegasus bug 4632)</big><br> |
OpenVMS IA64</font></big></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">Windows 2000</span></p> |
</td> | </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
|
Ver. 6 and Microsoft .Net compiler version. Works on |
|
VC .NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being |
|
regularly tested.</font></td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><span class="norm"></span><big><font |
<td style="padding: 0.75pt;"> <font size="3">Windows 2003</font> |
color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9</span></font></big></td> |
<p></p> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
|
WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
|
</td> | </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
|
Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++ |
|
Ver. 6 no longer being regular tested. </font> </td> |
|
</tr> |
|
<tr> |
|
<td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td> |
|
<td><big>CC Compiler Sun Studio 5.11</big></td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<br> |
<p><b>Platform patches</b> </p> |
<b>Platform patches</b> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font style="color: rgb(0, 0, 0);">The |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font |
following is a list known of platform patches Pegasus requires.</font></p> |
style="color: rgb(0, 0, 0);">The following is a list known of platform |
|
patches Pegasus requires.</font></p> |
|
<div style="margin-left: 40px;"> | <div style="margin-left: 40px;"> |
<ol> | <ol> |
<li> | <li> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"> <font style="color: rgb(0, 0, 0);">RHAS |
<font |
2.1 |
style="color: rgb(0, 0, 0);">RHAS |
needs the update to fix Red Hat Bugzilla 98815.</font></p> |
2.1 needs the update to fix Red Hat Bugzilla 98815.</font></p></li> |
</li> |
<li> | <li> |
<p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4 multithreading bug in |
<p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4 |
getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is fixed in |
multithreading bug in getpwuid-r could cause a CIM Server failure |
RHEL 4.5</p></li> |
(Bugzilla 6232). This is fixed in RHEL 4.5</p> |
|
</li> |
<li> | <li> |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE Linux |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE |
multiple versions - |
Linux multiple versions - multithreaded client intermittently |
multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla |
fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red Hat bug |
6586) (Red Hat bug 248052)<br></p></li> |
248052)<br> |
|
</p> |
|
</li> |
</ol> | </ol> |
</div> | </div> |
<p>Further information regarding Pegasus support on IBM platforms can |
<p>Further information regarding Pegasus support on IBM platforms can be |
be |
found at: <a href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span |
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> | style="text-decoration: underline; color: rgb(51, 51, 255);">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</span></a> |
</p> | </p> |
<p> Further information regarding Pegasus support on HP platforms can |
<p> Further information regarding Pegasus support on HP platforms can be |
be |
found at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> |
found at: |
|
<a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> |
|
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2> | <h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2> |
<p>The Pegasus bugzilla database documents any defects found in Pegasus |
<p>The OpenPegasus Bugzilla database documents any defects found in |
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla |
Pegasus 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 CVS tree |
OpenPegasus 2.6 work, all changes to the CVS tree are documented through |
were documented through bugs. Bugs reports were filed not only for bugs and |
bugs. Bugs reports are filed not only for bugs and their |
their corresponding fixes but also as part of the process of committing new code |
corresponding fixes but also as part of the process of committing new |
representing the work on PEPs done for Pegasus 2.6 and all subsequent versions. Therefore, a search of |
code representing the work on PEPs done for OpenPegasus 2.6 and all |
the Open Pegasus bugzilla base for bugs with the tag for a particular version |
subsequent versions. Therefore, a search of the OpenPegasus |
(ex. |
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"> |
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED">2.6.0_APPROVED</a>, |
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>) 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.</p> |
|
<p> - Changes for this release (bugs Tagged |
<p> |
2.12.0_APPROVED). The link is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.0_APPROVED"> |
- Changes for Pegasus 2.7.0 release (bugs Tagged |
Pegasus 2.12.0_APPROVED bug list.</a></p> |
2.7.0_APPROVED) |
<h2><a name="Pegasus Release Control and Version Definition Documentation">Release |
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">Pegasus 2.7.0_APPROVED bug list</a></p> |
Control |
|
and Version Definition Documentation</a></h2> |
<h2><a |
<p>The OpenPegasus project is controlled largely through the CVS |
name="Pegasus Release Control and Version Definition Documentation">Release Control and Version Definition Documentation</a></h2> |
repository and a set of documents (PEPs) that serve both as the |
|
definition and review mechanism for new and modified Pegasus |
<p>The Pegasus project is controlled largely through a set of documents |
functionality and for the definition and documentation of releases.</p> |
(PEPs) that serve both as the definition and review mechanism for new and |
The following documentation defines the characteristics of this Pegasus |
modified Pegasus functionality and for the definition and documentation |
release. The documents are available in the OpenPegasus CVS |
of releases. </p> |
repository. <br> |
|
<ul> |
<p>Specifically the following PEPs define the characteristics of this |
<li><b> OpenPegasus Release Definition/Status -No PEP (See Wiki Section |
Pegasus release. These PEPs are available at |
<a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_12_x">OpenPegasus |
<a href="http://www.openpegasus.org/pp/protected/documents.tpl?CALLER=index.tpl&gdc_docage=0&S=gdc_title&R=desc" style="color: blue; text-decoration: underline; text-underline: single"> |
2.12.x |
OpenPegasus Approved PEPs.</a></p> |
Release Status</a>) - <span style="font-weight: normal;">A |
|
section in the Pegasus wiki is used throughout the development of |
<b> |
this version as the control point for functionality that will go |
|
into the release and points to all of the PEPs that represent the |
<ol> |
Pegasus functionality changes for this version of Pegasus</span>. </b></li> |
|
<b> </b><span style="font-weight: bold;"></span><b>OpenPegasus |
<li> |
Build and Configuration Options for Selected Platforms - <span |
PEP 296 - OpenPegasus Release Definition - </b>This PEP is used |
style="font-weight: normal;">In previous versions of Pegasus this |
throughout the development of this version as the control point for |
information was released as a Pegasus PEP. Starting with |
functionality that will go into the release and points to all of the PEPs that |
Pegasus 2.9.0 the information is located in the OpenPegasus CVS |
represent the Pegasus functionality changes for this version of Pegasus.</li> |
repository as <big style="font-weight: bold;"> <span style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</span></big>.</span></b><b> |
|
<li> OpenPegasus External Interfaces -<span style="font-weight: normal;">The |
<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 |
<a href="http://www.openpegasus.org/pp/uploads/40/14873/PEP292_RecommendedReleaseOptions.htm">PEP 292</a> - OpenPegasus Build and Configuration |
continue to support these interfaces. Interfaces not explicitly |
Options for Selected |
listed in this document, should be considered as internal and |
Platforms</li> |
subject to change.In previous Pegasus releases this information |
|
was available as a separate PEP. Starting with Pegasus 2.9.0 this |
<li> |
information is integrated into the Pegasus repositoryas </span><small |
<a href="http://www.openpegasus.org/pp/uploads/40/14874/PEP293_ExternalInterface2.7.htm">PEP 293</a> - OpenPegasus 2.7 External Interfaces - </b>Lists the public |
style="font-weight: bold;"><font face="Courier New" size="4"><small>pegasus/doc/EnternalInterface.html</small></font></small><span |
interfaces for clients and providers that are considered external and |
style="font-weight: normal;">.</span></li> |
therefore "frozen".<b><br> |
</b> |
|
<li><b> OpenPegasus SDK Packaging Definition - <span style="font-weight: normal;">Defines |
</li> |
the recommended set of files for inclusion in the OpenPegasus SDK. |
|
Starting with Pegasus release 2.11.0, this document is available |
<li> |
in the Pegasus CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>. |
<a href="http://www.openpegasus.org/pp/uploads/40/14875/PEP294_SDKFile2.7.0.htm">PEP 294</a> - OpenPegasus SDK Packaging Definition - </b>Defines the |
In previous Pegasus releases this document was made available as s |
recommended set of files for inclusion in the OpenPegasus SDK</li> |
separate Pegasus PEP document rather than in the CVS repository.</span> |
|
</b></li> <b> </b> <b> |
<b> |
<li> 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 |
<a href="http://www.openpegasus.org/pp/uploads/40/14877/PEP295_RuntimePackaging2.7.0.htm">PEP 295</a> - Pegasus Runtime Packaging Definition - </b>Defines the |
contained in the CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/RuntimePackaging.html</samp></big>. |
recommended set of files for inclusion in this OpenPegasus release.</li> |
In previous releases this was made available as a seperate Pegasus |
|
PEP document rather than in the CVS repository. </span> </li> |
<b> |
</b> <b> |
|
<li>Pegasus Release Notes - <span style="font-weight: normal;"> </span>PEP |
<li>PEP 306 - Pegasus Release Notes (This document located in the |
364 - <span style="font-weight: normal;"> (This document is located |
approved PEP |
in the approved PEP repository and the OpenPegasus source tree |
repository and the OpenPegasus source tree root directory) <br> |
root directory (<big style="font-weight: bold;"><span style="font-family: monospace;">pegasus/ReleaseNotes.htm</span></big>)</span></li> |
|
</b> |
</li> |
</ul> |
|
<h2><b><a name="General Documentation">General Documentation</a></b></h2> |
</ol> |
<p><b>The following documentation is available for the this Pegasus |
|
release:</b></p> |
<h2><a name="General Documentation">General Documentation</a></h2> |
|
<p>The following documentation is available for the this Pegasus |
|
release:</p> |
|
<ul style="margin-top: 0in;" type="disc"> | <ul style="margin-top: 0in;" type="disc"> |
<li class="MsoNormal" style="color: black;"><b>Utilities</b> - </b>A |
|
combination of help generally available with the --help option for each |
|
command and HTML documentation for most of the tools.<o:p></o:p></li> |
|
|
|
<b> | <b> |
|
<li class="MsoNormal" style="color: black;"><b>Utilities</b> - </li> |
|
</b>A combination of help generally available with the --help option for |
|
each command and HTML documentation for most of the tools.<o:p></o:p> <b> |
<li class="MsoNormal" style="color: black;"><b>API and usage | <li class="MsoNormal" style="color: black;"><b>API and usage |
documentation</b> - </b>See the header files and the HTML API |
documentation</b> - </li> |
documentation that is on the web site. The best API usage documentation |
</b>See the header files and the HTML API documentation that is on |
is the existing utilities and test programs and the examples in the API |
the web site. The best API usage documentation is the existing utilities |
documentation. In particular the Common/tests unit tests contain |
and test programs and the examples in the API documentation. In |
extensive examples of the use of the Common APIs.</li> |
particular the Common/tests unit tests contain extensive examples of the |
|
use of the Common APIs. <b> |
<b> |
|
|
|
<li class="MsoNormal" style="color: black;"><b>Building and Debugging | <li class="MsoNormal" style="color: black;"><b>Building and Debugging |
Providers </b>- </b>Readme.html in the Pegasus source tree Root Directory, API |
Providers </b>- </li> |
|
</b>Readme.html in the Pegasus source tree Root Directory, API |
documentation, and documentation from the Pegasus Technical Workshop | documentation, and documentation from the Pegasus Technical Workshop |
which is available on the Pegasus web site.</li> |
which is available on the Pegasus web site. <b> |
|
|
<b> |
|
|
|
<li class="MsoNormal" style="color: black;"><b>Building and Debugging | <li class="MsoNormal" style="color: black;"><b>Building and Debugging |
Clients</b> - </b>API documentation and the documentation on the Pegasus |
Clients</b> - </li> |
Technical Workshop which is available on the Pegasus web site.</li> |
</b>API documentation and the documentation on the Pegasus Technical |
|
Workshop which is available on the Pegasus web site. <b> |
<b> |
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - </li> |
|
</b>The features of Pegasus that have been installed in this and the |
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - </b>The |
previous few versions are defined by Pegasus PEPs that are available on |
features of Pegasus that have been installed in this and the previous |
the OpenPegasus web site. While these are the original design |
few versions are defined by Pegasus PEPs that are available on the |
|
OpenPegasus web site. While these are the original design |
|
documents largely and use in the process of defining and approving the | documents largely and use in the process of defining and approving the |
overall characteristics of new functionality, they serve as a guide to | overall characteristics of new functionality, they serve as a guide to |
the design and implementation of these features.</li> |
the design and implementation of these features. |
</ul> | </ul> |
|
<hr>Licensed to The Open Group (TOG) under one or more contributor license |
<b> |
agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this |
|
work for additional information regarding copyright ownership. Each |
|
contributor licenses this file to you under the OpenPegasus Open Source |
<p class="MsoNormal" style="margin-left: 0.5in;"><span |
License; you may not use this file except in compliance with the License. |
style="color: black;"> <o:p></o:p></span></p> |
<p>Permission is hereby granted, free of charge, to any person obtaining a |
<div class="MsoNormal" style="text-align: center;" align="center"><span |
copy of this software and associated documentation files (the |
style="color: black;"> |
"Software"), to deal in the Software without restriction, including |
<hr align="center" color="#009900" noshade="noshade" size="2" |
without limitation the rights to use, copy, modify, merge, publish, |
width="100%"> |
distribute, sublicense, and/or sell copies of the Software, and to |
<p style="text-align: left;"><i><font size="2">Copyright (c) 2007 EMC |
permit persons to whom the Software is furnished to do so, subject to |
Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The |
the following conditions:</p> |
Open Group; VERITAS Software Corporation; Intel Corp.</font><br> |
<p>The above copyright notice and this permission notice shall be included |
<br> |
in all copies or substantial portions of the Software.</p> |
<font size="1">Permission is hereby granted, free of charge, to any |
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS |
person obtaining a copy of this software and associated |
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF |
documentation files (the "Software"), to deal in the Software without |
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. |
restriction, including without limitation the rights to use, copy, |
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY |
modify, merge, publish, distribute, sublicense, and/or sell copies of |
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, |
the Software, and to permit persons to whom the Software is furnished |
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE |
to do so, subject to the following conditions:</font><br> |
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p> |
<font size="2"><br> |
|
</font><font size="1">THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION |
|
NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE |
|
SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF |
|
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE |
|
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND |
|
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE |
|
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION |
|
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION |
|
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</font></i></p> |
|
</span></div> |
|
<p> </p> |
|
</div> | </div> |
</body> | </body> |
</html> | </html> |