version 1.5, 2005/08/26 16:19:50
|
version 1.16, 2009/01/28 16:20:14
|
|
|
<html xmlns:v="urn:schemas-microsoft-com:vml" |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
|
<html xmlns:v="urn:schemas-microsoft-com:vml"><head> |
<head> |
|
<style> | <style> |
st1\:*{behavior:url(#ieooui) } | st1\:*{behavior:url(#ieooui) } |
</style> | </style> |
|
|
margin:1.0in 1.25in 1.0in 1.25in; | margin:1.0in 1.25in 1.0in 1.25in; |
mso-header-margin:.5in; | mso-header-margin:.5in; |
mso-footer-margin:.5in; | mso-footer-margin:.5in; |
|
|
mso-paper-source:0;} | mso-paper-source:0;} |
div.Section1 | div.Section1 |
{page:Section1;} | {page:Section1;} |
|
|
text-indent:-.25in;} | text-indent:-.25in;} |
@list l4:level7 | @list l4:level7 |
{mso-level-tab-stop:3.5in; | {mso-level-tab-stop:3.5in; |
|
|
mso-level-number-position:left; | mso-level-number-position:left; |
text-indent:-.25in;} | text-indent:-.25in;} |
@list l4:level8 | @list l4:level8 |
|
|
{mso-level-tab-stop:2.0in; | {mso-level-tab-stop:2.0in; |
mso-level-number-position:left; | mso-level-number-position:left; |
text-indent:-.25in;} | text-indent:-.25in;} |
|
|
@list l5:level5 | @list l5:level5 |
{mso-level-tab-stop:2.5in; | {mso-level-tab-stop:2.5in; |
mso-level-number-position:left; | mso-level-number-position:left; |
|
|
text-indent:-.25in;} | text-indent:-.25in;} |
@list l19 | @list l19 |
{mso-list-id:1902863286; | {mso-list-id:1902863286; |
|
|
mso-list-template-ids:740079056;} | mso-list-template-ids:740079056;} |
@list l19:level1 | @list l19:level1 |
{mso-level-number-format:bullet; | {mso-level-number-format:bullet; |
|
|
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="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" |
<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> |
name="City"/> |
|
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
|
name="place"/> |
|
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
|
name="date"/> |
|
<!--[if gte mso 9]><xml> |
|
<o:DocumentProperties> | <o:DocumentProperties> |
<o:Author>IBM_User</o:Author> | <o:Author>IBM_User</o:Author> |
<o:LastAuthor> </o:LastAuthor> | <o:LastAuthor> </o:LastAuthor> |
|
|
</w:Compatibility> | </w:Compatibility> |
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> | <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> |
</w:WordDocument> | </w:WordDocument> |
</xml><![endif]--> |
</xml><![endif]--></head> |
|
<body lang="EN-US" link="blue" vlink="blue"> |
|
<div class="Section1"> |
|
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
|
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
|
<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;" align="center"><b><span style="font-size: 13.5pt; color: black;">Pegasus |
|
Enhancement Proposal (PEP)<o:p></o:p></span></b></p> |
|
|
|
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"> |
|
|
|
<br> |
|
|
|
<b>PEP #:</b> 345<br> |
|
|
|
</span></p> |
|
|
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release |
|
Notes for OpenPegasus 2.9.0</p> |
|
|
|
|
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 05 January 2009</p> |
|
|
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Karl Schopmeyer<br> |
|
|
|
</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> |
|
|
|
<table class="MsoNormalTable" style="width: 100%;" id="table1" border="1" cellpadding="0" cellspacing="1" height="155" width="100%"> |
|
|
|
<tbody> |
|
|
|
<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;" 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 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 style=""> |
|
|
|
<td style="padding: 0.75pt;" height="22"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><font size="2"> 1.0</font><o:p></o:p></span></p> |
|
|
|
</td> |
|
|
|
<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;">05 January 2009</span></font></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;"><font size="2">Karl Schopmeyer</font></span></p> |
|
|
|
</td> |
|
|
|
<td style="padding: 0.75pt;" height="22"> |
|
|
|
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial |
|
Submission <span style="color: red;"></span></font><o:p><font size="2"> |
|
</font></o:p></span></p> |
|
|
|
</td> |
|
|
|
</tr> |
|
|
|
<tr> |
|
|
|
<td style="padding: 0.75pt;" align="center" height="21">1.1</td> |
|
|
|
<td style="padding: 0.75pt;" align="center" height="21">16 Jananuary 2008</td> |
|
|
|
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td> |
|
|
|
<td style="padding: 0.75pt;" height="21">Update with comments from 1.0 incorporated.</td> |
| |
<body lang=EN-US link=blue vlink=blue style='tab-interval:.5in'> |
</tr> |
| |
<div class=Section1> |
<tr style=""> |
| |
<div class=MsoNormal align=center style='text-align:center'><span |
<td style="padding: 0.75pt;" align="center" height="21"></td> |
style='color:black'> |
|
| |
<hr size=2 width="100%" noshade color="#009900" align=center> |
<td style="padding: 0.75pt;" align="center" height="21"></td> |
| |
</span></div> |
<td style="padding: 0.75pt;" align="center" height="21"></td> |
| |
|
<td style="padding: 0.75pt;" height="21"></td> |
|
|
|
</tr> |
|
|
|
<tr> |
|
|
|
<td style="padding: 0.75pt;" align="center" height="21"></td> |
|
|
|
<td style="padding: 0.75pt;" align="center" height="21"></td> |
|
|
|
<td style="padding: 0.75pt;" align="center" height="21"></td> |
|
|
|
<td style="padding: 0.75pt;" height="21"></td> |
|
|
|
</tr> |
|
|
|
<tr style=""> |
|
|
|
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
|
|
|
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
|
|
|
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
|
|
|
<td style="padding: 0.75pt;" height="23"> </td> |
|
|
|
</tr> |
|
|
|
|
|
</tbody> |
|
</table> |
|
|
|
<div class="MsoNormal" style="text-align: center;" align="center"> |
|
<span style="color: black;"> |
|
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
|
<p><b>Abstract:</b> This document defines the release notes for the |
|
2.9.0 release of the OpenPegasus CIM Server. The purpose of this PEP is |
|
to summarize the characteristics of this release, point to other |
|
documentation that defines the release in more detail, and provide |
|
additional information about this release that is not available in the |
|
other Pegasus documentation. </p> |
|
<div class="MsoNormal" style="text-align: center;" align="center"> |
|
<span style="color: black;"> |
|
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
|
<h2 style="margin-bottom: 1px;"><b><o:p><font size="5"> Contents</font></o:p></b></h2> |
|
<ol> |
|
<li><a href="#Availability_of_this_Release_">Availability of this |
|
Release</a></li> |
|
<li><a href="#Functionality_of_This_Release">OpenPegasus |
|
Functionality of This Release</a></li> |
|
<li><a href="#Compatibility_Considerations_">Compatibility Considerations</a></li> |
|
<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship |
|
to CIM/WBEM Standards</a></li> |
|
<li><a href="#Supported%20Platforms">OpenPegasus Supported Platforms</a></li> |
|
<li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance |
|
with DMTF Specifications</a></li> |
|
<li><a href="#PEGASUS%20Bugs">OpenPegasus Bugs</a></li> |
|
<li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus |
|
Release Control and Version Definition Documentation</a></li> |
|
<li><a href="#General%20Documentation">General |
|
Documentation</a></li> |
|
</ol> |
|
<h2><span style="color: black;">Availability |
|
of this Release</span></h2> |
|
<p>This release is available in a number of forms including:</p> |
|
<ul> |
|
<li><b>Source release</b> in both ZIP (and ZIP EXE) and TAR formats. |
|
These can be |
|
downloaded from the <span class="SpellE">OpenPegasus</span> Web |
|
site at <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li> |
|
<li><b>OpenPegasus source RPMs</b> on the OpenPegasus web site.. A source RPM is available on the |
|
OpenPegasus web site that can be used to build binaries for most LSB-compliant RPM-based Linux distributions and versions.</li> |
|
<li><b>The Pegasus CVS repository</b>. The CVS tags representing this |
|
release and |
|
subsequent snapshots that are made available in the Pegasus CVS are |
|
defined on the OpenPegasus CVS repository web page (see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus |
|
CVS page</a> for information) using the tags defined on the <a href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release |
|
snapshots page</a>.</li> |
|
</ul> |
|
<p>The instructions for acquiring the released code are on the <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus |
|
WEB site</a>. |
|
Installation instructions are part of the README in the root of the |
|
Pegasus source |
|
tree.</p> |
</div> | </div> |
|
<div class="Section1"> |
|
<h2><span style="color: black;">OpenPegasus Functionality for This Release</span></h2> |
|
|
|
Pegasus overall status by release is defined by a |
|
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a> |
|
that is available on the OpenPegasus web site . That web page shows the |
|
Pegasus users and developers the status of the various features found in Pegasus |
|
using a simple color coded key (white, red, yellow, green) and a description of |
|
each feature.<p>Pegasus 2.9.0 |
|
is a major release, extending the previous Pegasus release in selected |
|
areas as described in the Pegasus PEP defining this release |
|
. </p> |
|
|
|
<p>The major areas of development for this release were as follows. For |
|
more information access the PEP for each change defined:</p> |
|
|
|
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font style="font-weight: bold;" size="4"> |
|
Table of Major Changes for this Release</font></p> |
|
|
| |
<p>This is a place-holder for the 2.5 Release Notes which be added just before |
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="82%"> |
the release.</p> |
<tbody> |
<p>Earlier versions can be downloaded from CVS, or from among the Release PEPS |
<tr align="center"> |
<a href="http://www.openpegasus.org/pp/documents.tpl?gdc_category=14&gdc_docage=0&grouped=Y&S=gdc_title&R=desc"> |
<th bgcolor="#00ffff">PEP/BUG #</th> |
here</a>.</p> |
<th bgcolor="#00ffff">Description of Change</th> |
<span |
<th bgcolor="#00ffff" width="128">Posted PEP<br>Version</th> |
style='color:black'> |
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" width="7%">PEP 311</td> |
|
<td align="left" width="75%">WS-Management Support in CIM Server - Phase II</td> |
|
<td width="128"><a href="http://www.openpegasus.org/pp/uploads/40/17656/PEP311_WSManSupportInCIMServer_2_1.htm">2.1</a></td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;" width="7%">PEP 314</td> |
|
<td align="left" width="75%">SQLite Repository</td> |
|
<td style="text-align: center;" width="128"><a href="http://www.openpegasus.org/pp/uploads/40/18018/PEP314_SQLiteRepository_2_3.htm">2.3</a></td> |
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" width="7%">PEP 316</td> |
|
<td align="left" width="75%">In-Memory-Tracing</td> |
|
<td width="128"><a href="http://www.openpegasus.org/pp/uploads/40/17360/PEP_316-In-Memory_Tracing.htm">1.1</a></td> |
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" width="7%">PEP 328</td> |
|
<td align="left" width="75%">Solaris 11 (Nevada) support for CC compiler and IX86</td> |
|
<td width="128"><a href="http://www.openpegasus.org/pp/uploads/40/18239/PEP328_SolarisIX86Port.htm">1.2</a></td> |
|
</tr> |
| |
<hr size=2 width="100%" noshade color="#009900" align=center> |
|
| |
|
<tr><td style="text-align: center;">Bug 7902</td><td>Allow modifyClass on non-leaf class</td><td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=7902">7902</a></td></tr><tr><td style="text-align: center;">Bug 7996</td><td>64 bit platform support for z;/OS</td><td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=7996">7996</a></td></tr><tr align="center"> |
|
<td style="text-align: center;" width="7%">Bug 8074 </td><td align="left" width="75%">Significant performance enhancement in out-of-process providers (~ 300%) through binary protocol</td> |
|
|
|
<td width="128"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8074">8074</a></td> |
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" width="7%">Bug 8171</td><td align="left" width="75%">Access to binary protocol for clients </td> |
|
|
|
<td width="128"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8171">8171</a></td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
<p>The status of several components of Pegasus functionality change status |
|
between Pegasus versions. <span class="norm"><a name="comtag_116">Features that |
|
have changed status can be identified by a change in color from the previous |
|
release to this release</a></span> on the |
|
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>.</p> |
|
|
|
<p>Finally, a significant number of internal changes and corrections were made |
|
under the control of the Pegasus bugzilla bug system. See the bug section below |
|
for more information.</p> |
|
|
|
<h3><font color="#000000">Information on IPv6 Support (PEP 291)</font></h3> |
|
<p><b>NOTE:</b> This functionality was incorporated in OpenPegasus 2.7.0 but it |
|
was felt that the information below was worth repeating in subsequent Release |
|
Notes</p> |
|
<p style="color: rgb(153, 51, 153);"><font color="#000000">IPv6 is short for "Internet |
|
Protocol |
|
Version 6". IPv6 is the "next generation" protocol designed by the IETF |
|
to replace the current version Internet Protocol, IP Version 4 |
|
("IPv4"). IPv6 Support for OpenPegasus is documented in </font> <a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html"> |
|
<font color="#3333ff">PEP |
|
291</font></a><font color="#000000">.</font></p> |
|
<p>The IPv6 support in OpenPegasus is |
|
controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this |
|
variable is "true"; setting this to |
|
'false' before building OpenPegasus will disable the IPv6 support.<br> |
|
</p> |
|
<p>The following subsections provide |
|
some information on IPv6 support for the Linux and Windows platforms. |
|
Note that in the 2.6.1 release there is no automatic run-time detection |
|
of IPv6 support on a platform by OpenPegasus. If you build with |
|
PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you will |
|
get a build failure (missing header files), a run-time bind() failure, |
|
or possibly some other failure. This applies to both the CIM Server and |
|
Listener components. For more information on IPv6 support for your |
|
specific platform, refer to the documentation for that platform.<br> |
|
</p> |
|
<p>All OpenPegasus externals that |
|
support either a hostname or an IP address as input have been updated |
|
to allow an IPv6 address to be specified. If the required input is just |
|
an IP address (eg. no optional or required port number), then the IPv6 |
|
address must be specified without brackets. For example, the |
|
OpenPegasus osinfo client (which returns information about the OS |
|
running on a host system) takes separate host and port options. In this |
|
case a host with an IPv6-configured network interface would be |
|
specified as:<br> |
|
</p> |
|
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">osinfo -h |
|
3ffe:1:2:1 -p 5988</font></big></div> |
|
<p>But the cimcli command, which |
|
takes |
|
an optional "location" option including an optional port number, |
|
requires the IPv6 address to be delimited with brackets, for example:<br> |
|
</p> |
|
<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns -l [3ffe:1:2:1]</big></div> |
|
<p>or</p> |
|
<div style="margin-left: 40px;"><big><span style="font-family: monospace;">cimcli ns -l [3ffe:1:2:1]:5989</span></big><br> |
|
</div> |
|
<br> |
|
For more information on |
|
specifying |
|
IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP Version |
|
6 Addressing Architecture</a> |
|
and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 - Format for |
|
Literal IPv6 Addresses in URL's</a>.<br> |
|
<h4><font color="#000000">IPv6 on Linux</font></h4> |
|
<p>Modern Linux distributions already |
|
contain IPv6-ready kernels, the |
|
IPv6 capability is generally compiled as a module, but it's possible |
|
that this module is not loaded automatically on startup.</p> |
|
<p><span style="font-weight: bold;">Note: |
|
</span>you shouldn't use kernel series 2.2.x, because it's not |
|
IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no |
|
longer improved according to definitions in latest RFCs. It's recommend |
|
to use series 2.6.x now.<br> |
|
</p> |
|
<p>To check whether your current |
|
running |
|
kernel supports IPv6, take a look into your /proc filesystem. The entry |
|
/proc/net/if_inet6 must exist. A short automated test looks like:<br> |
|
</p> |
|
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">test -f |
|
/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"</font></big></div> |
|
<p>For more information on |
|
enabling |
|
IPv6 in the Linux kernel and configuring network interfaces, refer to |
|
<a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux |
|
Documentation Project's IPv6 HOWTO</a>.<br> |
|
<br> |
|
<span style="font-weight: bold;">Warning</span>: |
|
There is currently an open issue with RedHat to address a problem that |
|
is seen intermittently on RHEL5 and SLES10 systems. This problem is |
|
described in <span style="color: rgb(153, 51, 153);"> |
|
<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
|
bug 6586</a> |
|
</span> |
|
and<span style="color: rgb(153, 51, 153);"> |
|
<a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat |
|
bug 248052</a>, |
</span> | </span> |
<p> </p> |
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> |
|
<p>Microsoft provides supported IPv6 |
|
implementations for Windows Server |
|
2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service |
|
Pack 2 (SP2), and Windows CE .NET 4.1 and later.</p> |
|
On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span> tool to install, uninstall, and |
|
query |
|
your IPv6 configuration. For example:<br> |
|
<br> |
|
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">ipv6 install<br> |
|
ipv6 if</font></big></div> |
|
<p>Windows Vista |
|
and Windows Server 2008 support an integrated |
|
IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack. |
|
Note that the OpenPegasus IPv6 support has not yet been tested |
|
on Windows Vista or Windows Server 2008.<br> |
|
<br> |
|
For more information on |
|
installing, configuring, and using IPv6 on Windows platforms, refer to |
|
the document |
|
<a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"> |
|
<font color="#000000">IPv6 |
|
for Microsoft Windows: Frequently Asked Questions</font></a>.<br> |
|
</p> |
|
<h4><font color="#000000">Testing your OpenPegasus IPv6 |
|
support</font></h4> |
|
As part of the OpenPegasus |
|
automated tests, the TestClient, g11ntest, and IndicationStressTest |
|
test clients were modified to run tests using the IPv6 loopback address |
|
(::1) if PEGASUS_ENABLE_IPV6=true.<br> |
|
<br> |
|
You can also perform manual |
|
tests |
|
using the IPv6 loopback or a real IPv6-configured network interface. |
|
For example, using the IPv6 loopback on a system with OpenPegasus |
|
running on the WBEM standard http port of 5988:<br> |
|
<div style="margin-left: 40px;"><br><big style="font-family: monospace;"> |
|
osinfo -h ::1</big></div> |
|
<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2> |
|
<p>Support for forward-compatibility is a fundamental design principle for the |
|
OpenPegasus project. As a Community, our goal is for well-behaved OpenPegasus |
|
Providers or Clients, using only the externally defined OpenPegasus interface, |
|
to continue to work with a minor version upgrade of OpenPegasus. However, there |
|
are certain classes of errors (e.g., non-compliance with a standard that |
|
significantly affects interoperability) that may require the Community to make |
|
potentially incompatible changes. The following table contains a list of defect |
|
fixes that MAY impact, even well-behaved, OpenPegasus Providers or Clients when |
|
upgrading to this OpenPegasus release.</p> |
|
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="80%"> |
|
<tbody> |
|
<tr align="center"> |
|
<th bgcolor="#00ffff" width="10%">Bugzilla #</th> |
|
<th bgcolor="#00ffff">Description</th> |
|
</tr> |
|
<tr><td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8229">8229</a></td><td>The Common Information Model (CIM) Infrastructure Specification (DSP0004) |
|
version 2.3 contains this statement in section 3.2: "If the specification |
|
references a class without defining it first, the server must reject it as |
|
invalid if it does not already have a definition of that class." |
|
Previously, this check was only performed for derived classes. In |
|
Pegasus 2.9, the check is also done for base classes. This may cause a |
|
MOF file that previously loaded without problem to generate an error if it |
|
contains a forward reference. Note that the CIM 2.13.1 schema in the |
|
Pegasus source repository contained such an error in Pegasus 2.8, which is |
|
also corrected in Pegasus 2.9.</td></tr><tr align="center"> |
|
<td><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=6812">6812</a></td> |
|
<td align="left">In Pegasus 2.8, the behavior of the setName() method was |
|
changed in the Pegasus C++ interface for the CIM data type model. For |
|
data types that use a shared representation model, the setName() method |
|
now throws an Exception when the object is "contained" by another CIM |
|
data object. <br> |
|
Specifically, setName() may throw the new exception in these cases: <br> |
|
<u>CIMProperty</u> contained by CIMClass, CIMInstance, and CIMObject <br> |
|
<u>CIMQualifier</u> contained by CIMClass, CIMInstance, CIMObject, |
|
CIMProperty, CIMParameter, and CIMMethod <br> |
|
<u>CIMMethod</u> contained by CIMClass <br> |
|
<u>CIMParameter</u> contained by CIMMethod</td> |
|
</tr> |
|
<tr align="center"> |
|
<td><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7453">7453</a></td> |
|
<td> |
|
<p align="left">In Pegasus 2.8, the C++ CMPI IndicationMI function |
|
signatures were changed to fit the CMPIIndicationMIFT definitions. |
|
<br> |
|
The CmpiResult parameter in CmpiIndicationMI authorizeFilter, mustPoll, |
|
activateFilter and deActivateFilter have been removed cause it does not |
|
exist in the CMPIIndicationMIFT definitions. <br> |
|
The missing CmpiContext parameter and CMPIStatus have been added to |
|
enableIndications and disableIndications.</p></td> |
|
</tr> |
|
<tr align="center"> |
|
<td><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7488">7488</a></td> |
|
<td> |
|
<p align="left">In Pegasus 2.8, the CMPI property filter handling performance was improved. <br> |
|
Two things have changed in the behaviour of the property filter |
|
handling: <br> |
|
* Repeated applying of property filters onto the same instance will now |
|
only leave the properties which build the most common dominator on the |
|
instance. <br> |
|
* It is not possible anymore to add properties not defined for the |
|
corresponding class to an instance.</p></td> |
|
</tr> |
|
<tr align="center"> |
|
<td><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7624">7624</a></td> |
|
<td> |
|
<p align="left">In Pegasus 2.8, the algorithm used by the MessageLoader |
|
to search the accept language list to determine which message file to |
|
open was changed. Before Pegasus 2.8, the Message Loader used the |
|
following algorithm: </p> |
|
<blockquote> |
|
<p align="left">1.) The Message Loader will search the accept |
|
language list for an exact match. The first exact match found will |
|
be returned.<br> |
|
2.) If an exact match does not exist, the Message Loader will return |
|
an ICU "fallback" match for the first entry in accept language list.<br> |
|
3.) If an ICU "fallback" match does not exist for the first entry, |
|
it will return the ROOT resource bundle.</p> |
|
</blockquote> |
|
<p align="left">With the release of Pegasus 2.8, the Message Loader no longer returns ICU "fallback" matches. In addition, it gives |
|
preference to the default process locale over the ROOT resource bundle. |
|
In Pegasus 2.8, the Message Loader was modified to use the |
|
following algorithm: </p> |
|
<ul> |
|
<p align="left">1.) The Message Loader will search the accept |
|
language list for an exact match. The first exact match found will |
|
be returned.<br> |
|
2.) If an exact match does not exist, the Message Loader will return |
|
an exact match for the default process locale.<br> |
|
3.) If an exact match for the default process locale is not found, |
|
it will return the ROOT resource bundle.</p> |
|
</ul> |
|
</td> |
|
</tr> |
|
<tr align="center"> |
|
<td><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7501"> |
|
7501</a></td> |
|
<td> |
|
<p align="left">Since OpenPegasus 2.7.2 the way CMPI_chars are added to |
|
arrays was corrected to follow the CMPI specification. Following the |
|
CMPI specification means that CMPI_chars are not to be dereferenced, |
|
contrary to all other subtypes of CMPIValues.<br> |
|
If you experience an error since switching over to OpenPegasus 2.8 |
|
saying "The byte sequence starting at offset xx is not valid UTF-8 |
|
encoding", this is an indication for a missing update in the provider |
|
code.<br> |
|
<br> |
|
The update for a C CMPI provider using arrays of CMPI_chars is to use a |
|
char* now as input parameter instead of a char**.<br> |
|
<u>CMPI Example:</u><br> |
|
char* role = "Unknown";<br> |
|
array = CMNewArray(_broker,1,CMPI_chars,rc);<br> |
|
<i>from:</i><br> |
|
CMSetArrayElementAt(array,0,(CMPIValue*)<b>&</b>role,CMPI_chars);<br> |
|
<i>to:</i><br> |
|
CMSetArrayElementAt(array,0,(CMPIValue*)role,CMPI_chars);</p></td> |
|
</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%"> |
|
<tbody> |
|
<tr> |
|
<td bgcolor="#00ffff" width="33%"><b>DMTF Specification</b></td> |
|
<td bgcolor="#00ffff" width="33%"><b>Specification Version</b></td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0004 - CIM Infrastructure Specification</td> |
|
<td width="33%">Version 2.3 Final, 4 October 2005</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0200 - CIM Operations over HTTP</td> |
|
<td width="33%">Version 1.2, Final, January 09, 2007</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0201 - Representation of CIM in XML</td> |
|
<td width="33%">Version 2.2 Final, January 09, 2007</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0202 - CIM Query Language Specification</td> |
|
<td width="33%">1.0.0, preliminary, 9 December 2004</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0205 - WBEM Discovery using SLP</td> |
|
<td width="33%">1.0, preliminary, 27 January 2004</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0206 - WBEM SLP Template</td> |
|
<td width="33%">1.0.0, Preliminary, January 2004</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">CIM Schema </td> |
|
<td width="33%">2.17.1 Final, 14 Dec 2007( default) </td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
<h2><a name="Conformance with DMTF Specifications">Conformance |
|
Exceptions to |
|
DMTF Specifications</a></h2> |
|
<p>It is a major goal |
|
of the OpenPegasus project to both drive and utilize the DMTF CIM/WBEM |
|
specifications. However, today there are a number of known |
|
differences. |
|
As of this release, some of the differences include the following:</p> |
|
<ol> |
|
<li><b>Provider Registration</b> - Pegasus supports registration |
|
through a set of Pegasus Provider registration classes rather than |
|
support the DMTF defined Provider Qualifier. Pegasus will not support |
|
this qualifier in the future. See the readme for more information on |
|
provider registration. This is not a deviation from the |
|
specifications but is a different method of registration than many CIM |
|
Servers and means that the the provider qualifier is unused in Pegasus.</li> |
|
<li><b>Indications </b>-Today Pegasus supports process |
|
indications and lifecycle indications when defined specifically by |
|
providers. Pegasus does not support lifecycle indications if they are |
|
not defined by the provider or for changes to CIM Classes.<font color="#ff0000"> </font><span class="norm"><font color="#ff0000"> </font>For |
|
more information see the Pegasus CVS file:<a name="comtag_137"><font size="2"> |
|
</font><font face="Courier New" size="2"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a><font size="2">.</font></span></li> |
|
<li> |
|
<p class="MsoNormal"><font style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers |
|
option on Instance Operations</font><span style="color: black;"><b> </b> |
|
- |
|
The DMTF specifications have deprecated the use of qualifiers on |
|
instance operations with the 1.2 CIM Operations Specification. |
|
Some CIM Client implementations expect instances |
|
returned |
|
from the CIM Server to include the qualifiers defined in the class |
|
definition (such as KEY qualifiers on properties). </span> Pegasus |
|
today expects the provider to complete the qualifiers on instances in |
|
accordance with the specification and generally the interpretation is |
|
that Pegasus applies class level qualifiers when the includeInstance |
|
parameter is supplied on instance operations. However, Pegasus |
|
today is inconsistent in the return of qualifiers so that the user |
|
should NOT depend on Pegasus accurately honoring the includeQualifier |
|
parameter for instance operations. In the future it is expected |
|
that Pegasus will deprecate the use of qualifiers on instance |
|
operations completely.<font color="#ff0000"> </font></p> |
|
</li> |
|
<li><b>LocalOnly option on instance |
|
Operations </b>- With the 1.1 version of Specification for CIM |
|
Operations over HTTP, the definition of the LocalOnly parameter for the |
|
GetInstance and Enumerate Instances operations was modified. This change |
|
was incorrect, resulted in reduced functionality and introduced a |
|
number of backward compatibility issues. As a result of issues |
|
introduced by this change, we strongly recommend that CIM Clients set |
|
LocalOnly = false and do not rely on the use of this parameter to |
|
filter the set of set of properties returned. See Appendix C of this |
|
specification for more information.</li> |
|
<li> |
|
<p class="MsoNormal"><b>MultiRequest Operations</b> - Pegasus |
|
does not support the DMTF defined MultiRequest Operation option.</p> |
|
</li> |
|
<li> |
|
<p class="MsoNormal"><b>MOF Compiler namespace pragma</b> - The |
|
Pegasus compiler does not support the namespace pragma.</p> |
|
</li> |
|
<li><b>CIMOperation Trailer </b>- Pegasus implements |
|
chunking |
|
based on the DSP0200 1.2.0 preliminary spec. including the operation trailer |
|
defined in that specification Refer to bug |
|
<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> for more details. |
|
This trailer was completely removed from the DSP0200 1.2 final specification |
|
as a non-compatible change so that if chunking is used Pegasus is returning |
|
a noncompliant response to enumerate type requests. <br> |
|
</li> |
|
</ol> |
|
<h2><b><span style="font-family: Times;">OpenPegasus <a name="Supported Platforms">Supported |
|
Platforms</a></span></b></h2> |
|
<p align="left">Each OpenPegasus release lists as 'active' platforms those |
|
hardware/software platforms that have recognized ports for the Pegasus code base |
|
including a maintainer for the platform that will be willing to regularly |
|
document issues and/or fix defects as the Pegasus code base is changed. |
|
Pegasus may be operable on other platforms (ex. Windows 98) but without a group |
|
to provide the role of test and maintenance, correct operation of Pegasus |
|
cannot be assured. In all cases, including the active platforms, it is the |
|
responsibility of the entity that packages and/or compiles OpenPegasus for |
|
shipment or deployment, to read, and actively monitor the Pegasus bugzilla |
|
database for a list of relevant defects that affect their platform. |
|
The platforms that are considered ported are shown in the two tables below. |
|
The first table represents platform sofr which testing is done on a regular |
|
basis and reported to the Pegasus Nightly Build Test WEB Page. Those platforms |
|
which have been ported but do not have test results that are current at the time |
|
of the release are reported in the second table.</p><b>Actively Supported Platforms (Nightly Tests Reported for this release)</b> |
|
<table class="MsoNormalTable" style="width: 90%;" border="1" cellpadding="0" cellspacing="1"> |
|
<tbody> |
|
<tr style=""> |
|
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;" height="26"> |
|
<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> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">HP-UX<o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">HP <span class="SpellE">aC</span>++ B3910B<o:p></o:p></span></p> |
|
</td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">Linux on Power</span></span><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">zLinux</span></span><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">Linux Itanium<o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;"> |
|
<span style="color: black;"><font size="3">Linux IA-32</font></span></td> |
|
<td style="padding: 0.75pt;"> |
|
<span class="SpellE"><span style="color: black;"><font size="3">gcc</font></span></span><span style="color: black;"><font size="3"> |
|
(versions 2.9x, 3.xx, 4.xx)</font><o:p></o:p></span></td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">Linux X86_64<o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"> |
|
(versions 2.9x, 3.xx, 4.xx)</span></p> |
|
</td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">Windows 2000</span></p> |
|
</td> |
|
<td style="padding: 0.75pt;"> |
|
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler version. Works on VC .NET 2003 v7.1). |
|
NOTE: Visual C++ Ver. 6 no longer being regularly tested.</font></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;"> <font size="3">Windows 2003</font><p></p> |
|
</td> |
|
<td style="padding: 0.75pt;"> |
|
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1. |
|
Note: Visual C++ Ver. 6 no longer being regular tested. |
|
</font> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;"><big>HP OpenVMS 8.3 or later Alpha</big></td> |
|
<td style="vertical-align: top;"><font size="3"> </font><big><font style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span style="color: rgb(153, 51, 153);">7.3-009 or later required</span> for OpenVMS |
|
Alpha</font></big></td> |
|
</tr> |
|
<tr> |
|
<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 style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 or |
|
later required</font><font style="color: rgb(0, 0, 0);"> on OpenVMS IA64</font></big></td> |
|
</tr> |
|
<tr> |
|
<td style="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 no Actively supported for this release (No |
|
current Nightly Build Test Results</b></p> |
|
<table class="MsoNormalTable" style="width: 90%;" id="table2" border="1" cellpadding="0" cellspacing="1"> |
|
<tbody> |
|
<tr style=""> |
|
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;" height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Platform and |
|
OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt; background: 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> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;"> <font size="3">Windows XP</font><p></p> |
|
</td> |
|
<td style="padding: 0.75pt;"> |
|
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1. |
|
Note: Visual C++ Ver. 6 no longer being regular tested. |
|
</font> |
|
</td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;"> <font size="3">MacOS version 10.3 and higher</font></td> |
|
<td style="padding: 0.75pt;"> <font size="3">gcc 4.01</font></td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;"><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 8</span></font></big></td> |
|
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
|
CC compiler V 5.8. Note that the latest thread patch (108993) may be |
|
required. (see Pegasus bug 4632)</big><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;"><span class="norm"></span><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9</span></font></big></td> |
|
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
|
WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
|
</td> |
|
</tr><tr><td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td><td><big>CC Compiler Sun Studio 5.11</big></td></tr> |
|
</tbody> |
|
</table> |
|
<p><b>Platform patches</b> |
|
</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font style="color: rgb(0, 0, 0);">The following is a list known of platform |
|
patches Pegasus requires.</font></p> |
|
<div style="margin-left: 40px;"> |
|
<ol> |
|
<li> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"> |
|
<font style="color: rgb(0, 0, 0);">RHAS |
|
2.1 needs the update to fix Red Hat Bugzilla 98815.</font></p></li> |
|
<li> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4 multithreading bug in |
|
getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is fixed in |
|
RHEL 4.5</p></li> |
|
<li> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE Linux |
|
multiple versions - |
|
multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla |
|
6586) (Red Hat bug 248052)<br></p></li> |
|
</ol> |
|
</div> |
|
<p>Further information regarding Pegasus support on IBM platforms can |
|
be |
|
found at: <a href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span style="text-decoration: underline; color: rgb(51, 51, 255);">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</span></a> |
|
</p> |
|
<p> Further information regarding Pegasus support on HP platforms can |
|
be |
|
found at: |
|
<a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> |
|
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2> |
|
<p>The Pegasus bugzilla database documents any defects found in Pegasus |
|
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla |
|
database</a>. |
|
Effective with the start of the Pegasus 2.6 work, all changes to the CVS tree |
|
were documented through bugs. Bugs reports were filed not only for bugs and |
|
their corresponding fixes but also as part of the process of committing new code |
|
representing the work on PEPs done for Pegasus 2.6 and all subsequent versions. Therefore, a search of |
|
the Open Pegasus bugzilla base for bugs with the tag for a particular version |
|
(ex. |
|
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED"> |
|
2.6.0_APPROVED</a>, |
|
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED"> |
|
2.6.1_APPROVED</a>, |
|
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>) will yield all changes to |
|
the Pegasus CVS tree for that Pegasus release.</p> |
|
|
|
<p> |
|
- Changes for Pegasus 2.9.0 release (bugs Tagged |
|
2.9.0_APPROVED). The link is <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.9.0_APPROVED"> |
|
Pegasus 2.9.0_APPROVED bug list.</a></p> |
|
|
|
<h2><a name="Pegasus Release Control and Version Definition Documentation">Release Control and Version Definition Documentation</a></h2> |
|
|
|
<p>The Pegasus project is controlled largely through a set of documents |
|
(PEPs) that serve both as the definition and review mechanism for new and |
|
modified Pegasus functionality and for the definition and documentation |
|
of releases.</p>The following PEPs define the characteristics of this |
|
Pegasus release. These PEPs are available at |
|
<a href="http://www.openpegasus.org/pp/protected/documents.tpl?CALLER=index.tpl&gdc_docage=0&S=gdc_title&R=desc" style="color: blue; text-decoration: underline;"> |
|
OpenPegasus Approved PEPs.</a><ol> |
|
|
|
<b> <li> |
|
No PEP (See Wiki Section <a href="http://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_9_x">OpenPegasus 2.9.x Release Status</a>) - OpenPegasus Release Definition/Status - </li></b>A |
|
section in the Pegasus wiki is used |
|
throughout the development of this version as the control point for |
|
functionality that will go into the release and points to all of the PEPs that |
|
represent the Pegasus functionality changes for this version of Pegasus<span style="font-weight: bold;">.</span> |
|
|
|
<b> |
|
|
|
<li> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/18245/PEP343_RecommendedReleaseOption2.9.htm"> |
|
PEP 343</a> - OpenPegasus Build and Configuration |
|
Options for Selected |
|
Platforms -<span style="font-weight: normal;"> Also located in the OpenPegasus CVS repository as <big><span style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</span></big>.</span></li></b><b> |
|
|
|
<li> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/18244/PEP344_ExternalInterface2.9.htm"> |
|
PEP 344</a> - OpenPegasus 2.8 External Interfaces - </li></b>Lists the public |
|
interfaces for clients and providers that are considered external and |
|
therefore "frozen".<b><br> |
|
|
|
|
|
|
|
<li> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/16779/PEP330_SDKFile2.8.0.htm"> |
|
PEP 342</a> - OpenPegasus SDK Packaging Definition - </li></b>Defines the |
|
recommended set of files for inclusion in the OpenPegasus SDK |
|
|
|
<b> |
|
|
|
<li> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/18247/PEP341_RuntimePackaging2.9.0.htm"> |
|
PEP 341</a> - Pegasus Runtime Packaging Definition - </li></b>Defines the |
|
recommended set of files for inclusion in this OpenPegasus release. |
| |
</body> |
<b> |
| |
</html> |
|
|
<li>PEP 345 - Pegasus Release Notes - <span style="font-weight: normal;"> (This document located in the |
|
approved PEP |
|
repository and the OpenPegasus source tree root directory (<big><span style="font-family: monospace;">pegasus/ReleaseNotes.html</span></big>)</span><br> |
|
|
|
</li> |
|
|
|
</b></ol> |
|
|
|
<h2><b><a name="General Documentation">General Documentation</a></b></h2> |
|
<p><b>The following documentation is available for the this Pegasus |
|
release:</b></p> |
|
<ul style="margin-top: 0in;" type="disc"> |
|
<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 |
|
documentation</b> - </li></b>See the header files and the HTML API |
|
documentation that is on the web site. The best API usage documentation |
|
is the existing utilities and test programs and the examples in the API |
|
documentation. In particular the Common/tests unit tests contain |
|
extensive examples of the use of the Common APIs. |
|
|
|
<b> |
|
|
|
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
|
Providers </b>- </li></b>Readme.html in the Pegasus source tree Root Directory, API |
|
documentation, and documentation from the Pegasus Technical Workshop |
|
which is available on the Pegasus web site. |
|
|
|
<b> |
|
|
|
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
|
Clients</b> - </li></b>API documentation and the documentation on the Pegasus |
|
Technical Workshop which is available on the Pegasus web site. |
|
|
|
<b> |
|
|
|
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - </li></b>The |
|
features of Pegasus that have been installed in this and the previous |
|
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 |
|
overall characteristics of new functionality, they serve as a guide to |
|
the design and implementation of these features. |
|
</ul> |
|
|
|
<hr>Licensed to The Open Group (TOG) under one or more contributor license |
|
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 License; you may not use this file except in compliance with the |
|
License. |
|
<p>Permission is hereby granted, free of charge, to any person obtaining a |
|
copy of this software and associated documentation files (the "Software"), |
|
to deal in the Software without restriction, including without limitation |
|
the rights to use, copy, modify, merge, publish, distribute, sublicense, |
|
and/or sell copies of the Software, and to permit persons to whom the |
|
Software is furnished to do so, subject to the following conditions:</p> |
|
<p>The above copyright notice and this permission notice shall be included |
|
in all copies or substantial portions of the Software.</p> |
|
<p>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.</p> |
|
</div> |
|
</body></html> |