version 1.5, 2005/08/26 16:19:50
|
version 1.21, 2015/03/18 17:07:01
|
|
|
<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> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> |
<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"><title>PEP</title></head><body lang="EN-US" link="blue" vlink="blue"><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype> <o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml> |
href="PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso"> |
<o:DocumentProperties> <o:Author>IBM_User</o:Author> <o:LastAuthor> </o:LastAuthor> <o:Revision>4</o:Revision> <o:TotalTime>211</o:TotalTime> <o:Created>2004-04-05T14:13:00Z</o:Created> <o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>5026</o:Words> <o:Characters>28651</o:Characters> <o:Company>IBM</o:Company> <o:Lines>238</o:Lines> <o:Paragraphs>67</o:Paragraphs> <o:CharactersWithSpaces>33610</o:CharactersWithSpaces> <o:Version>10.4219</o:Version> </o:DocumentProperties></xml><![endif]--><!--[if gte mso 9]><xml> |
<title>PEP</title> |
<w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:Compatibility> <w:ApplyBreakingRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument></xml><![endif]--> |
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
<div class="Section1"> |
name="City"/> |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
name="place"/> |
<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;" align="center"><b><span style="font-size: 13.5pt; color: black;">OpenPegasus Enhancement |
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
Proposal (PEP)<o:p></o:p></span></b></p> |
name="date"/> |
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"> |
<!--[if gte mso 9]><xml> |
<br> |
<o:DocumentProperties> |
<b>PEP #:</b> 368<br> |
<o:Author>IBM_User</o:Author> |
</span></p> |
<o:LastAuthor> </o:LastAuthor> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release |
<o:Revision>4</o:Revision> |
Notes for OpenPegasus version 2.14.0</p> |
<o:TotalTime>211</o:TotalTime> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 20 November 2014<br> |
<o:Created>2004-04-05T14:13:00Z</o:Created> |
</p> |
<o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Karl |
<o:Pages>1</o:Pages> |
Schopmeyer<br> |
<o:Words>5026</o:Words> |
</p> |
<o:Characters>28651</o:Characters> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>draft</p> |
<o:Company>IBM</o:Company> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p> |
<o:Lines>238</o:Lines> |
<table class="MsoNormalTable" style="width: 100%;" id="table1" border="1" cellpadding="0" cellspacing="1" height="155" width="100%"> |
<o:Paragraphs>67</o:Paragraphs> |
<tbody> |
<o:CharactersWithSpaces>33610</o:CharactersWithSpaces> |
<tr style=""> |
<o:Version>10.4219</o:Version> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
</o:DocumentProperties> |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
</xml><![endif]--><!--[if gte mso 9]><xml> |
</td> |
<w:WordDocument> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
<w:SpellingState>Clean</w:SpellingState> |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
<w:GrammarState>Clean</w:GrammarState> |
</td> |
<w:Compatibility> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
<w:ApplyBreakingRules/> |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
</w:Compatibility> |
</td> |
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
</w:WordDocument> |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
</xml><![endif]--> |
</td> |
|
</tr> |
<body lang=EN-US link=blue vlink=blue style='tab-interval:.5in'> |
<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"> 0.99</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;">12 Nov. 2014<br> |
|
</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 for review<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.00<br> |
|
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">14 March 2015<br> |
|
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer<br> |
|
</td> |
|
<td style="padding: 0.75pt;" height="21">Update to finish the document (approved as bug 9684)<br> |
|
</td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;" align="center" height="21"><br> |
|
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21"><br> |
|
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21"><br> |
|
</td> |
|
<td style="padding: 0.75pt;" height="21"><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;" align="center" height="21"><br> |
|
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21"><br> |
|
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21"><br> |
|
</td> |
|
<td style="padding: 0.75pt;" height="21"><br> |
|
</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> |
|
<br> |
|
<b>Abstract:</b> This document defines the release notes for the 2.14.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.<br> |
|
<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="#Notes_on_Specific_OpenPegasus">Notes on Specific |
|
OpenPegasus Functionality</a><br> |
|
</li> |
|
<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship to |
|
CIM/WBEM Standards</a></li> |
|
<li><a href="#Supported%20Platforms">OpenPegasus Supported Platforms</a></li> |
|
<li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance |
|
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> |
|
This release is available in a number of forms including:<br> |
|
<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>TheOpenPegasus 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> and the <a title="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus">OpenPegasus |
|
WIKI Release Status Page</a>.</li> |
|
</ul> |
|
<br> |
|
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> and the <a title="OpenPegasus WIKI" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">OpenPegasus |
|
WIKI</a>. Installation instructions are part of the README in the root |
|
of the Pegasus source tree.<br> |
|
</div> |
|
<div class="Section1"> |
|
<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 |
|
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 OpenPegasus using a simple color coded key |
|
(white, red, yellow, green) and a description of each feature. <br> |
|
<br> |
|
OpenPegasus 2.14.0 is a major release, extending the previous Pegasus |
|
release in selected areas as described in these release notes. <br> |
|
<br> |
|
NOTE: OpenPegasus releases are categorized as follows:<br> |
|
<ul> |
|
<li>First number of version changes (ex. 2.x.x to 3.0.0) - Major |
|
release includes major functionality change and incompatible |
|
behavior changes and/or incompatible public API changes, <br> |
|
</li> |
|
<li>Second number changes (ex 2.12.0 2.14.0) - Minor Release and |
|
includes new functionality but maintains behavior and public API |
|
compatibility, <br> |
|
</li> |
|
<li>3rd number changes (2.14.0 to 2.14.1) - Revision(also called point |
|
release) release and only includes bug fixes.</li> |
|
</ul> |
|
<br> |
|
<u><b>ALL</b></u> changes for each release are documented in the |
|
OpenPegasus bug data base by tagging each bug(keyword field of bug). |
|
No change to Pegasus is committed with out this tag on the bug. Changes |
|
for this minor release are tagged 2.14.0_APPROVED. All changes for |
|
this minor release can be viewed through this link to the |
|
OpenPegasus bugzilla <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.14.0_APPROVED"> |
|
Pegasus 2.14.0_APPROVED bug list. Bugs. </a>Bugs marked as |
|
enhancements can be reviewed through the this <a href="http://bugzilla.openpegasus.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=CIM+Server+Core&product=CIMClient+Application&product=CIMClient+DefaultCPlusPlus&product=CIMClient+Java-SNIA&product=CIMConsumer+DefaultCPlusPlus&product=CIMIndicationHandler&product=CIMListener+Dynamic&product=CIMListener+Standalone&product=CIMProvider+CMPI&product=CIMProvider+CMPIRemote&product=CIMProvider+DefaultCPlusPlus&product=CIMProvider+Instrumentation&product=CIMProvider+JMPI&product=CIMSchema&product=CIMServer+Administration&product=CIMServer+Administration+Command&product=CIMServer+Administration+Profiles&product=CIMServer+ProviderManagement&product=CIMServer+Repository&product=CIMServer+SLP&product=OpenPegasus+Build+System&product=OpenPegasus+Documentation&product=OpenPegasus+Security+Defects&product=OpenPegasusProject+Bugzilla&product=OpenPegasusProject+CVS&product=OpenPegasusProject+Website&product=PegasusCIMOM&product=PegasusGeneral&product=RPM+CIMServer&product=TestProduct&product=Unsupported&product=WMI+Mapper&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.14.0_APPROVED&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_severity&type0-0-0=equals&value0-0-0=enhancement">link |
|
to OpenPegasus bugzilla 2.14.0 enhancement bugs</a> . Bugs fixed |
|
for subsequent revision releases (ex. 2.14.1) would also be viewed through |
|
corresponding Bugzilla tags for each revisions (ex 2.14.1_APPROVED).<br> |
|
<br> |
|
The major areas of development including both enhancements and bug fixes |
|
for this release were as follows. Note that the bugs listed |
|
represent only those features incorporated in bugs without PEPS that are |
|
considered enhancements, not all bugs incorporated in the release. For |
|
more information access the PEP/BUG for each change defined below:<br> |
|
<br> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font style="font-weight: bold;" size="4"> Table of Major |
|
Changes this Release. Review Bugzilla 2.14.0 |
|
Enhancements and approved(above) for a complete list<br> |
|
</font></p> |
|
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="82%"> |
|
<tbody> |
|
<tr align="center"> |
|
<th bgcolor="#00ffff">BUG #</th> |
|
<th bgcolor="#00ffff">Description of Change</th> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9601">9601</a></td> |
|
<td>Support only TLS V1.2 Protocol for Security Compliance<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9676">9676</a>, <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9819">9819</a><br> |
|
</td> |
|
<td>Support DMTF defined Pull Operations (per DMTF |
|
specification DSP 0200 and 0201). This is a major extension to |
|
OpenPegasus and implements all of the DMTF defined pull operations with |
|
NO changes to providers. This includes extentions to both the server |
|
and client code as well as new operations implemented in cimcli to |
|
allow execution of pull operations and pull operations with FQL.<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9721">9721</a><br> |
|
</td> |
|
<td>Fix issue causing failures when cmpi returned |
|
instances that do not have a class. This was causing problems with the |
|
Jobs profiles which specifically return information for which there is |
|
no class.<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9724">9724</a><br> |
|
</td> |
|
<td>Dynamic disable of the reliable Indication feature<br> |
|
</td> |
|
|
|
</tr> |
| |
<div class=Section1> |
<tr> |
|
<td style="vertical-align: top; text-align: center;">9812<br> |
|
</td> |
|
<td style="vertical-align: top;">FootPrint Reduction<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top; text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9831">9831</a><br> |
|
</td> |
|
<td style="vertical-align: top;">Generate mini-CA and signed certificate instead of self-signed certificates</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9832">9832</a><br> |
|
</td> |
|
<td>Include cimcli in release packages<br> |
|
</td> |
| |
<div class=MsoNormal align=center style='text-align:center'><span |
</tr> |
style='color:black'> |
|
| |
<hr size=2 width="100%" noshade color="#009900" align=center> |
<tr> |
|
<td style="vertical-align: top; text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9883">9883</a><br> |
|
</td> |
|
<td style="vertical-align: top;">support HTTP Negotiate Authentication in OpenPegasus |
|
</td> |
| |
</span></div> |
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9892">9892</a><br> |
|
</td> |
|
<td>Reduce overhead of use of PAM by use of a |
|
SessionCookie. This also introduces a new runtime configuration |
|
parameter to control the session timeout<br> |
|
</td> |
| |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9828">9928</a><br> |
|
</td> |
|
<td>Incorporate FQL (Filter Query Language) support for the pull operations (Experimental)<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9880">9880</a>,<a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9778">9778</a><br> |
|
</td> |
|
<td>Several minor extension to the APIs (ex. extend String class methods)<br> |
|
</td> |
|
|
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9737">9737</a><br> |
|
</td> |
|
<td align="left" width="75%">Improve CLANG compiler support <br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9219">9219</a><br> |
|
</td> |
|
<td>Initial CIMRS and Web Admin support (This is Experimental and the CIMRS function will be modified for CIMRS V2 specification)<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9853">9853</a><br> |
|
</td> |
|
<td>Correct old error in the Memory Resident |
|
Repository logic. This logic did not work in several previous versions |
|
because of the issues documented in this bug.<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9926">9926</a><br> |
|
</td> |
|
<td>Update default CIM Schema to CIM 2.41<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td>Add scripts for load testing of OpenPegasus (see the directory src/Unsupported/Scripts/UinxLoadTests)<br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;" width="7%"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=10012">10012</a><br> |
|
</td> |
|
<td align="left" width="75%">Fix issue with the configuration parameters for numberOfTraceFiles and traceFileSizeKbytes. |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" width="7%"><br> |
|
</td> |
|
<td align="left" width="75%"><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
|
|
|
</tr> |
|
</tbody> |
|
</table> |
|
<br> |
|
The status of several components of Pegasus functionality change status |
|
between Pegasus versions. <span class="norm"><a name="comtag_116">Features |
|
that |
|
have |
|
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>.<br> |
|
<br> |
|
<h2><a name="Notes_on_Specific_OpenPegasus"></a>Notes on Specific |
|
OpenPegasus Functionality Changes</h2> |
|
This section documents specific issues that the OpenPegasus team feels are |
|
important to OpenPegasus users with the current release (and possibly |
|
older releases).<br> |
|
<br> |
|
<h3>Add new RunTime Variables to control trace file size and Rotation(OpenPegasus |
|
2.13.0)(bug 9550)</h3> |
|
As of OpenPegasus 2.14.0, several new runtime variables have been added that can be manipulated with the <span style="font-family: Courier New,Courier,monospace;">cimconfig</span> utility:<br> |
|
<br> |
|
* <span style="font-weight: bold;">pullOperationsMaxObjectCount </span>- |
|
Defines the maximum allowed value of the maxObjectCount argument on |
|
open and pull operation requests which defines the maximum number of |
|
instances or paths that will be returned in a single open or pull |
|
response. Requests that have a value higher than this configuration |
|
parameter will be rejected. The default is10000. This may be set to any |
|
value between 1 and 10000. <br> |
|
* <span style="font-weight: bold;">pullOperationsDefaultTimeout</span> |
|
- Defines the default timeout in seconds between the time a pull open |
|
response is sent by the server and a subsequent pull or close response |
|
received from the client if the value is not set by the client in the |
|
request. This can be set to any value between 1 and 90 seconds. |
|
Default=30<br> |
|
* <span style="font-weight: bold;">pullOperationsMaxTimeout</span> |
|
- Defines the maximum allowable value for the maxTimeout argument that |
|
is part of the pull open... (openEnumerationInstances, etc) requests. |
|
Any value higher than the value set in this configuration parameter |
|
will cause the request to be rejected by the CIMServer. The default=90 |
|
seconds. TODO - Explain more on all of these above<br> |
|
* <span style="font-weight: bold;">httpSessionTimeout </span>- |
|
Allows using a cookie to temporarily bypass the PAM authentication in |
|
favor of the cookie provided by the server during a single session.<br> |
|
This is a performance enhancement. If this variable is set to |
|
zero (default) the cookie bypass is disabled, the server will not send |
|
nor accept the id cookie. If set to<br> |
|
an integer, a client session will maintain the cookie for the number of |
|
seconds defined by the value of this variable. Enabled with a build |
|
parameter PEGASUS_ENABLE_SESSION_COOKIES.<br> |
|
* <span style="font-weight: bold;">sslBackwardCompatibility</span> |
|
- Limits OpenPegasus support to TLS 1.2/OpenSSL1.01. Can be set to |
|
allow backward compatibility with older versions of TLS/OpenSSL. <br> |
|
<br> |
|
The following sections describe in more detail some of the more |
|
significatn changes in this release as well as carrying forward some of |
|
the same information for the last release to be sure users are aware |
|
what these changes affect.<br> |
|
<br> |
|
<h3>DMTF Pull Client operations and FQL Query Language (OpenPegasus 2.14.0)</h3>As |
|
of DMTF DSP0200 version 1.4, new client operations (generally named the |
|
pull operations have been part of the CIM/XML protocol). This consists<br> |
|
of a set of new operations (open..., pull..., close) that allow getting |
|
enumerations, associations, references (and their corresponding name |
|
operations) as a sequence<br> |
|
of operations (an enumeration sequence) rather than a single monolithic operation.<br> |
|
<br> |
|
This will provider several advantages including:<br> |
|
1. Better control of client memory since the client can determine the size of each response.<br> |
|
2. Clearly separates the return of errors from data.<br> |
|
<br> |
|
Pegasus 2.14 supports all of these operations in both in the CIM/XML |
|
client and the server. For more information on the implementation and |
|
use of<br> |
|
these operation see the following documents:<br> |
|
<br> |
|
1. OpenPegasus <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:workgroups:pulloperationsupportworkgroup:pull_operation_support_work_group">Wiki page</a> for this project.<br> |
|
2. PEP documenting the Pull operations and FQL<br> |
|
<br> |
|
<h3>HTTP Sessions(OpenPegasus 2.14.0)</h3>Allows using a cookie to |
|
enhance performance of PAM. This function is enabled with the |
|
build varaible PEGASUS_ENABLE_SESSION_COOKIES. When<br> |
|
the option is enabled, the OpenPegasus CIM server will |
|
use HTTP cookies for session management (RFC 6265). |
|
<br> |
|
|
|
After a successful client authentication the client is given a cookie. The |
|
client is then not asked for re-authentication as long as it provides the |
|
same cookie in all subsequent requests and until the session expires. Session |
|
expiry is configurable using httpSessionTimeout configuration option. |
|
<br> |
|
|
|
Nothing changes for clients that do not support HTTP cookies (RFC 6465) - |
|
their requests are authenticated as usual, either using Basic or Negotiate |
|
authentication mechanisms. |
|
<br> |
|
<br> |
|
The timeout for a session is determined by the runtime parameter <span style="font-weight: bold;">httpSessionTimeout</span>. If this runtime parameter is set to zero the HTTP cookies option is disabled.<br> |
|
<br> |
|
This option has proven to represent a significant improvement in performance over using PAM for every client operation.<span style="font-family: Arial;"><span style="font-weight: bold;"> <br> |
|
</span></span><h3>WEBAdmin (OpenPegasus 2.14.0)</h3>OpenPegasus has |
|
included on an experimental basis a web server that acts as an |
|
adminstration tool to replace the command line tools. This option |
|
presents the<br> |
|
same information as the major command line tools as web pages so that |
|
parameters can be modified without using the command line tools. |
|
It is compiled by<br> |
|
default and may be disabled with the build option |
|
PEGASUS_ENABLE_PROTOCOL_WEB=false. See the file readme.webadmin in the |
|
OpenPegasus<br> |
|
source tree for more detailed information on using WEBAdmin.<br> |
|
<br> |
|
Note: This option is considered experimental for 2.14<br> |
|
<br> |
|
<h3>Using GCC 4.7 Compiler on Linux OS (OpenPegasus 2.13.0)<br> |
|
</h3> |
|
As of 2.14.0, OpenPegasus has been updated to replace the custom atomic |
|
operations with GCC built-in atomic operations if GCC version 4.7 or |
|
greater is used as the compiler. It is recommended that if possible |
|
this version of the GCC compiler be used since the change provides |
|
significant performance improvements.<br> |
|
<h2> </h2> |
|
<h3>OpenPegasus and OpenSLP V 2.0 (OpenPegasus 2.13.0)</h3> |
|
As of 2.13.0, OpenPegasus slp fully supports IPV6 and has been |
|
tested with OpenSLP 2.0 (Recently released by <a href="http://openslp.org">OpenSlp.org</a>)<br> |
|
<br> |
|
While testing OpenPegasus with OpenSLP 2.0 the OpenPegasus team found two |
|
issues with this version of OpenSLP. The patches documented below |
|
allow this version of OpenSLP to work with OpenPegasus<br> |
|
<br> |
|
1) SLPReg used TCP connection previously, but it now uses UDP. Therefore, |
|
a BUFFER_OVERFLOW exception occurs. This is because UDP cannot |
|
handle attribute size greater than network MTU size. In such cases, |
|
according to the specification, OpenSLP should automatically switch to |
|
TCP. Since this has not been implemented in OpenSlp 2.0, the |
|
workaround used by OpenPegasus to force use of TCP may be found at <a title="http://sourceforge.net/p/openslp/bugs/139/" href="http://sourceforge.net/p/openslp/bugs/139/">http://sourceforge.net/p/openslp/bugs/139/</a>.<br> |
|
<br> |
|
2) On Windows, slpd service fails to start when IPV6 is enabled and throws |
|
the error message "Error 1067: the process terminated unexpectedly". More |
|
details and the fix for this issue are in the bug <a href="http://sourceforge.net/p/openslp/bugs/140/">http://sourceforge.net/p/openslp/bugs/140/</a>.<br> |
|
<h3>Interop namespace name (OpenPegasus 2.13.0)</h3> |
|
Effective with the release of OpenPegasus 2.13 the "interop" |
|
namespace support for existing or |
|
older repositories which used |
|
"root/PG_InterOp" has been added via a new option in the "reupgrade" |
|
utility. Users with existing repositories may use this option to migrate |
|
the repository from "root/PG_InterOp" to |
|
"interop" namespace. See <span class="bz_closed"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9414" title="RESOLVED FIXED - enhance repupgrade to support "interop" namespace">bug |
|
9414</a></span> (PEP304) for |
|
details.<br> |
|
<br> |
|
For this to work, the build option "PEGASUS_INTEROP_NAMESPACE" has |
|
to be |
|
set to "interop". Only then will the "-i" option in repupgrade be enabled. |
|
Once the repository is upgraded with "-i" , the namespace |
|
"root/PG_InterOp" |
|
will cease to exsist. Clients using "root/PG_InterOp" must now use |
|
"interop".<br> |
|
<br> |
|
Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable to |
|
define "root/PG_InterOp" as the name for the OpenPegasus namespace with no |
|
defined way to change this variable. Note that an unsupported method |
|
involving editing one file and rebuilding OpenPegasus was defined as a |
|
workaround in the <a href="file:///home/kschopmeyer/dev/pgogbug9611releasenotes/pegasus/%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus |
|
wiki faq</a>s. <br> |
|
<br> |
|
However, since the definition of a standard name for this namespace in |
|
DMTF and SNIA specifications ("interop" or "root/interop" with "interop" |
|
being the preferred alternative) the use of "root/PG_InterOp" has |
|
become an issue. Support for forward-compatibility is a fundamental design |
|
principle for the OpenPegasus project. As a community, our goal is for |
|
well-behaved OpenPegasus providers or clients, using only the externally |
|
defined OpenPegasus interface, to continue to work with each version |
|
upgrade of OpenPegasus.<br> |
|
<br> |
|
Effective OpenPegasus 2.12.0 a new build variable was defined |
|
(PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus builder to define |
|
an alternate name for the Interop namespace to either "interop" or |
|
"root/interop" (ex. PEGASUS_INTEROP_NAMESPACE = interop). Once this |
|
build variable is defined and OpenPegasus compiled, the actual name of the |
|
interop namespace is what was defined in this varaible and all components |
|
of OpenPegasus use this as the interop namespace name include the complete |
|
OpenPegasus test suite. The only name for the interop namespace will |
|
be the name defined through this build variable. This is the logical |
|
approach for implementations starting a new repository.<br> |
|
<br> |
|
In order to supexport PEGASUS_CLIENT_TRACE=keyword:keywordport users with |
|
existing repositories, in 2.13.0, migration of existing repositories |
|
was integrated into the "repupgrade" utility to allow existing OpenPegasus |
|
environments to smoothly move the server from use of the old name |
|
for the interop namespace "root/PG_InterOp" to |
|
the prefered name "interop".<br> |
|
<br> |
|
<span style="font-weight: bold;">NOTE:</span> If the interop namespace |
|
name is redefined with PEGASUS_INTEROP_NAMESPACE clients using the |
|
"root/PG_InterOp" namespace will not connect with the updated version of |
|
OpenPegasus. The OpenPegasus team searched for a solution to the issue |
|
supporting the old and new name at the same time and concluded that there |
|
were so many issues that it could not effectively be done.<br> |
|
<h3>Configure Script to Control OpenPegasus Builds (OpenPegasus |
|
2.13.0)(Bug 9592)</h3> |
|
OpenPegasus is moving from the use of environment variables to a configure |
|
script to control build. This is both to make it easier to define |
|
the build variables, etc. and to be more compatibile with the Linux/Unix |
|
standard build environment. However, because OpenPegasus must build |
|
on a number of platforms that do not support the full Linux/Unix |
|
configuration tool set, this is an OpenPegasus defined configure |
|
script. The first very experimental version is part of OpenPegasu |
|
2.13.0 but this version has a number of limitations (see the OpenPegasus |
|
Bugzilla) and will be expanded in the next versions of OpenPegasus.<br> |
|
<br> |
|
The goal is to replace the setting of most of the OpenPegasus build |
|
environment variable with options in the pegasus/configure script where |
|
those options are comatible with the Linux standard for defining configure |
|
options and those options control the entire build process including placement |
|
of output and choice of build options.<br> |
|
<h3>Tracing Client Requests and Responses(OpenPegasus2.13.0)</h3> |
|
<p><span style="color: rgb(0, 102, 0);"><span style="font-family: "Times New Roman";"><span style="font-weight: bold;"></span></span></span></p> |
|
<span style="font-family: "Times New Roman";">OpenPegasus has |
|
long contained a hidden build controlled function to allow tracing at |
|
the client through an environment variable |
|
(PEGASUS_CLIENT_TRACE_ON). In 2.13.0 this was a) make a permanent |
|
part of of the environment (Bug 9564) and the calling convention</span><br> |
|
<span style="font-family: "Times New Roman";">slightly changed |
|
to make it simpler to use. </span>The original format for the |
|
environment variable was:<br> |
|
<pre class="bz_comment_text" id="comment_text_1">export PEGASUS_CLIENT_TRACE=keyword:keyword<br>where the keyword was "con" | "log" | "both"<br>This was changed to:<br> keyword:keyword separately define Client input and output<br> keyword: Client Input only<br> :keyword Client Output Only<br> keyword Client Input and output defined by keyword</pre> |
|
so that the normal setup for a console output trace would be<br> |
|
<pre> export PEGASUS_CLIENT_TRACE=con</pre> |
|
<h3>Information on IPV6 Support and OpenPegasus(PEP 291)(OpenPegasus |
|
2.7.0)</h3> |
|
<b>NOTE:</b> This functionality was incorporated in OpenPegasus 2.7.0 but |
|
it was felt that the information below was worth repeating in subsequent |
|
Release Notes<br> |
|
<br> |
|
<font color="#000000">IPv6 Support for OpenPegasus is documented in </font> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html"> |
|
<font color="#3333ff">PEP 291</font></a><font color="#000000">.</font><br> |
|
<br> |
|
The IPv6 support in OpenPegasus is controlled by the PEGASUS_ENABLE_IPV6 |
|
build variable. The default for this variable is "true"; setting this to |
|
'false' before building OpenPegasus will disable the IPv6 support.<br> |
|
<br> |
|
The following subsections provide some information on IPv6 support for the |
|
Linux and Windows platforms. Note that in the 2.6.1 release there is no |
|
automatic run-time detection of IPv6 support on a platform by OpenPegasus. |
|
If you build with PEGASUS_ENABLE_IPV6=true, your platform must support |
|
IPv6 or you will get a build failure (missing header files), a run-time |
|
bind() failure, or possibly some other failure. This applies to both the |
|
CIM Server and Listener components. For more information on IPv6 support |
|
for your specific platform, refer to the documentation for that platform.<br> |
|
<br> |
|
All OpenPegasus externals that support eitcompilerher a hostname or an IP |
|
address as input have been updated to allow an IPv6 address to be |
|
specified. If the required input is just an IP address (eg. no optional or |
|
required port number), then the IPv6 address must be specified without |
|
brackets. For example, the OpenPegasus osinfo client (which returns |
|
information about the OS running on a host system) takes separate host and |
|
port options. In this case a host with an IPv6-configured network |
|
interface would be specified as:<br> |
|
<br> |
|
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">osinfo -h 3ffe:1:2:1 -p 5988</font></big></div> |
|
<br> |
|
But the cimcli command, which takes an optional "location" option |
|
including an optional port number, requires the IPv6 address to be |
|
delimited with brackets, for example:<br> |
|
<br> |
|
<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns -l |
|
[3ffe:1:2:1]</big></div> |
|
<p>or</p> |
|
<div style="margin-left: 40px;"><big><span style="font-family: monospace;">cimcli |
|
ns -l [3ffe:1:2:1]:5989</span></big><br> |
</div> | </div> |
|
<br> |
|
For more information on specifying IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF |
|
RFC |
|
2373 - IP Version 6 Addressing Architecture</a> and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF |
|
RFC 2732 - Format for Literal IPv6 Addresses in URL's</a>.<br> |
|
<h4><font color="#000000">IPv6 on Linux</font></h4> |
|
Modern Linux distributions already contain IPv6-ready kernels, the IPv6 |
|
capability is generally compiled as a module, but it's possible that this |
|
module is not loaded automatically on startup.<br> |
|
<br> |
|
<span style="font-weight: bold;">Note: </span>you shouldn't use |
|
kernel series 2.2.x, because it's not IPv6-up-to-date anymore. Also the |
|
IPv6 support in series 2.4.x is no longer improved according to |
|
definitions in latest RFCs. It's recommend to use series 2.6.x now.<br> |
|
<br> |
|
To check whether your current running kernel supports IPv6, take a look |
|
into your /proc filesystem. The entry /proc/net/if_inet6 must exist. A |
|
short automated test looks like:<br> |
|
<br> |
|
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">test -f /proc/net/if_inet6 && echo "Running |
|
kernel is IPv6 ready"</font></big></div> |
|
<br> |
|
For more iSchema version default update to CIM 2.36nformation on enabling |
|
IPv6 in the Linux kernel and configuring network interfaces, refer to <a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux |
|
Documentation Project's IPv6 HOWTO</a>.<br> |
|
<br> |
|
<span style="font-weight: bold;">Warning</span>: There is currently an |
|
open issue with RedHat to address a problem that is seen intermittently on |
|
RHEL5 and SLES10 systems. This problem is described in <span style="color: rgb(153, 51, 153);"> |
|
<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
|
bug 6586</a> </span>and<span style="color: rgb(153, 51, 153);"> <a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat |
|
bug |
|
248052</a>, </span>and manifests itself as an intermittent IPv6 |
|
socket failure. You should be aware that OpenPegasus with IPv6 enabled may |
|
be significantly impacted in these environments.<br> |
|
<h4><font color="#000000">IPv6 on Windows</font></h4> |
|
<br> |
|
Microsoft provides supported IPv6 implementations for Windows Server 2003, |
|
Windows XP with Service Pack 1 (SP1), Windows XP with Service Pack 2 |
|
(SP2), and Windows CE .NET 4.1 and later.<br> |
|
<br> |
|
On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span> |
|
tool to install, uninstall, and query your IPv6 configuration. For |
|
example:<br> |
|
<br> |
|
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">ipv6 install<br> |
|
ipv6 if</font></big></div> |
|
<br> |
|
Windows Vista and Windows Server 2008 support an integrated IPv4 and IPv6 |
|
implementation known as the Next Generation TCP/IP stack. Note that the |
|
OpenPegasus IPv6 support has not yet been tested on Windows Vista or |
|
Windows Server 2008.<br> |
|
<br> |
|
For more information on installing, configuring, and using IPv6 on Windows |
|
platforms, refer to the document <a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"><font color="#000000">IPv6 for Microsoft Windows: Frequently Asked Questions</font></a>.<br> |
|
<br> |
|
<h4><font color="#000000">Testing OpenPegasus IPv6 support</font></h4> |
|
As part of the OpenPegasus automated tests, the TestClient, g11ntest, and |
|
IndicationStressTest test clients were modified to run tests using the |
|
IPv6 loopback address (::1) if PEGASUS_ENABLE_IPV6=true.<br> |
|
<br> |
|
You can also perform manual tests using the IPv6 loopback or a real |
|
IPv6-configured network interface. For example, using the IPv6 loopback on |
|
a system with OpenPegasus running on the WBEM standard http port of 5988:<br> |
|
<div style="margin-left: 40px;"><br> |
|
<big style="font-family: monospace;"> osinfo -h ::1</big></div> |
|
<h2><a name="Compatibility_Considerations_">OpenPegasus Compatibility |
|
Considerations</a></h2> |
|
Support for forward-compatibility is a fundamental design principle for |
|
the OpenPegasus project. As a community, our goal is for well-behaved |
|
OpenPegasus providers or clients, using only the externally defined |
|
OpenPegasus interface, to continue to work with a minor version upgrade of |
|
OpenPegasus. However, there are certain classes of errors (e.g., |
|
non-compliance with a standard that significantly affects |
|
interoperability) that may require the community to make potentially |
|
incompatible changes. The following table contains a list of defects/fixes |
|
that MAY impact, even well-behaved, OpenPegasus providers or clients when |
|
upgrading to this OpenPegasus release. <br> |
|
<br> |
|
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="80%"> |
|
<tbody> |
|
<tr align="center"> |
|
<th bgcolor="#00ffff" width="10%">Bugzilla #</th> |
|
<th bgcolor="#00ffff">Description</th> |
|
</tr> |
|
<tr align="center"> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8830">Bug |
|
8830</a></td> |
|
<td align="left">Starting |
|
with OpenPegasus 2.11.0 the requirement for providers (CMPI and C++) to |
|
filter properties from instances has been relieved. The server will do |
|
the filtering at the protocol adapter level. To avoid a negative impact |
|
on performance the CIMInstance::filter() and |
|
CMPIInstanceFT.setPropertyFilter() functions have been changed to a |
|
NOP. This may be a change in behavior for provider relying in some |
|
unknown way on the instance being filtered through these functions. To |
|
allow users to actually filter properties from an instance in a |
|
provider, a new function (CIMInstance::filterInstance()) will actually |
|
filter properties from an instance exactly as the CIMInstance::filter() |
|
did in previous versions of Pegasus. This is not required since the |
|
CIMServer will do the filtering but allows the provider to prefilter |
|
properties if it so desires, in particular where properties might be |
|
very large or there would be a significant number of properties.<br> |
|
</td> |
|
</tr> |
|
<tr align="center"> |
|
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9369">Bug |
|
9369</a><br> |
|
</td> |
|
<td align="left"><span style="font-weight: bold;">NOTE: This bug |
|
fixed in OpenPegasus 2.13.0. </span>Reregistering of an |
|
indication provider requires that the cimserver be restarted |
|
to send the enableIndication request to the providers. This issue |
|
has existed starting with OpenPegasus 2.10 to version 2.12. |
|
If the cimserver is not restarted the indication will not be |
|
enabled for the reregistered provider. </td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
<h2>OpenPegasus Relationship to CIM/WBEM Standards</h2> |
|
Pegasus was designed and implemented to comply with the DMTF CIM/WBEM |
|
specifications The following table defines the level of the DMTF |
|
specifications to which this version of Pegasus aims to conform today.<br> |
|
<br> |
|
<table id="AutoNumber1" border="1" cellspacing="1" width="80%"> |
|
<tbody> |
|
<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.4, 26 August 2013<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0201 - Representation of CIM in XML</td> |
|
<td width="33%">Version 2.4.0 16 January 2014<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0202 - CIM Query Language Specification</td> |
|
<td width="33%">1.0.0, preliminary, 9 December 2004</td> |
|
</tr> |
|
<tr> |
|
<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.36.0 Final ( default build Schema) </td> |
|
</tr> |
|
<tr> |
|
<td>DSP0226 - Web Services for Management<br> |
|
</td> |
|
<td>Version 1.1.1<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td>DSP0227 - WS-Management CIM Binding Specification<br> |
|
</td> |
|
<td>Version 1.2.0<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td>DSP0230 - WS-CIM Mapping Specification </td> |
|
<td>Version 1.1.0<br> |
|
</td> |
|
</tr><tr> |
|
<td style="vertical-align: top;">DSP0212 - Filter Query Language<br> |
|
</td> |
|
<td style="vertical-align: top;">Version 1.0.1, 22 August 2013<br> |
|
</td> |
|
</tr> |
| |
<p>This is a place-holder for the 2.5 Release Notes which be added just before |
</tbody> |
the release.</p> |
</table> |
<p>Earlier versions can be downloaded from CVS, or from among the Release PEPS |
<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIA SMI |
<a href="http://www.openpegasus.org/pp/documents.tpl?gdc_category=14&gdc_docage=0&grouped=Y&S=gdc_title&R=desc"> |
Profiles Supported</h2> |
here</a>.</p> |
<br> |
<span |
Today OpenPegasus includes support for several DMTF profiles including:<br> |
style='color:black'> |
<ol> |
|
<li>DMTF ProfileRegistration Version DSP 1033, Version 1.0.0</li> |
|
<li>DMTF Indications DSP 1054, Version 1.1.0. Since this is effectively the same as the |
|
SNIA SMI Indication profile it also supports this profile. This |
|
profile is enabled by compiling OpenPegasus with the buld variable |
|
PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.<br> |
|
</li> |
|
<li>SNIA Profile Registration 1.0.0<br> |
|
</li> |
|
<li>SNIA Server 1.1.0 & 1.2.0<br> |
|
</li> |
|
</ol> |
|
<h2><a name="Conformance with DMTF Specifications">Conformance Exceptions |
|
to DMTF Specifications</a></h2> |
|
It is a major goal of the OpenPegasus project to both drive and utilize |
|
the DMTF CIM/WBEM specifications. However, today there are a number |
|
of known differences. As of this release, some of the differences |
|
include the following:<br> |
|
<ol> |
|
<li><b>Provider Registration</b> |
|
- Pegasus supports registration through a set of Pegasus Provider |
|
registration classes rather than support the DMTF defined Provider |
|
Qualifier. Pegasus will not support this qualifier in the future. See |
|
the readme for more information on provider registration. This is |
|
not really a deviation from the specifications since there is no |
|
specification or profile for provider registration today but is a |
|
different method of registration than many CIM Servers and means that |
|
the the provider qualifier is unused in Pegasus.</li> |
|
<li><b>Lifecycle Indications </b>-Today Pegasus supports process |
|
iPegasusndications and lifecycle indications when defined specifically by |
|
providers. Pegasus does not support lifecycle indications if they are |
|
not defined by the provider or for changes to CIM Classes.<font color="#ff0000"> |
|
</font><span class="norm"><font color="#ff0000"> </font>For more |
|
information see the Pegasus CVS file:<a name="comtag_137"><font size="2"> |
|
</font><font face="Courier New" size="2"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a><font size="2">.</font></span></li> |
|
<li> <font style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers |
|
option |
|
on Instance Operations</font><span style="color: black;"><b> </b> |
|
- The DMTF specifications have deprecated the use of qualifiers on |
|
instance operations with the 1.2 CIM Operations Over HTTP Specification (DSP0200) and |
|
stated specifically that the client should NOT depend on the |
|
includeQualifiers parameter of the CIM/XML instance operations |
|
returning qualifiers. Some CIM Client implementations expect |
|
instances returned from the CIM Server to include the qualifiers |
|
defined in the class definition (such as KEY qualifiers on |
|
properties). Pegasus today expects the provider to |
|
complete the qualifiers on instances in accordance with the |
|
specification and generally the interpretation is that Pegasus |
|
applies class level qualifiers when the includeInstance parameter is |
|
supplied on instance operations. However, Pegasus today is |
|
inconsistent in the return of qualifiers so that the user should NOT |
|
depend on Pegasus accurately honoring the includeQualifier parameter |
|
for instance operations. In the future it is expected that |
|
Pegasus will deprecate the use of qualifiers on instance operations |
|
completely. When Pegasus uses object normalization, the |
|
normalizer does apply qualifiers to returned instances if the |
|
includeQualifiers operation parameter is set.</span></li> |
|
<li><b>LocalOnly option on instance Operations </b>- With the 1.1 |
|
version of Specification for CIM Operations over HTTP, the definition |
|
of the LocalOnly parameter for the GetInstance and Enumerate Instances |
|
operations was modified. This change was incorrect, resulted in |
|
reduced functionality and introduced a number of backward |
|
compatibility issues. As a result of issues introduced by this change, |
|
we strongly recommend that CIM Clients set LocalOnly = false and do |
|
not rely on the use of this parameter to filter the set of set of |
|
properties returned. See Appendix C of this specification for more |
|
information.</li> |
|
<li><span style="font-weight: bold;">MultiRequest CIM/XML Option</span> |
|
- Pegasus does not support the DMTF defined MultiRequest |
|
Operation option (See DSP0200).<br> |
|
</li> |
|
<li><span style="font-weight: bold;">MOF Namespace Pragma</span> -The |
|
Pegasus compiler does not support the namespace pragma defined in DSP |
|
0004. Namespaces for the OpenPegasus repository are defined through |
|
arguments for the MOF Compiler<br> |
|
</li> |
|
<li><b>CIMOperation Trailer </b>- Pegasus implements chunking based on |
|
the DSP0200 1.2.0 preliminary spec. including the operation trailer |
|
defined in that specification Refer to bug <a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> |
|
for more details. This trailer was completely removed from the DSP0200 |
|
1.2 final specification as a non-compatible change so that if chunking |
|
is used Pegasus is returning a noncompliant response to enumerate type |
|
requests. </li> |
|
<li><span style="font-weight: bold;">Whitespace in XML value Element</span> |
|
- Pegasus trims the leading and trailing whitespace from XML value |
|
elements that are of the Type String. This behavior is |
|
documented in Pegasus bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8773">8773</a> |
|
and there is a patch available for users. However, since the |
|
change is considered a change to behavior this will not be patched |
|
until pegasus does a major version update. NOTE: There are some |
|
documented bugs in Pegasus such as this that the OpenPegasus team |
|
feels cannot be incorporated into the code until a major version |
|
update. These bugs are documented with the Bugzilla tag <big style="font-weight: bold;"><samp>"3.0_TARGET".</samp></big></li> |
|
<li><span style="font-weight: bold;">modifyInstance operation behavior |
|
in the Pegasus repository does not match the DMTF specification</span>. |
|
Under some conditions (ex. if no propertyList is supplied) it modifies |
|
all properties rather than just the properties supplied with the |
|
request thereby Nulling out existing values. See bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8752">8752</a> |
|
for more information.</li> |
|
<li><b>OpenPegasus Interop Namespace</b> |
|
- The default interop namespace name in OpenPegasus is |
|
"root/PG_Interop". In versions of OpenPegasus prior to 2.12.0 |
|
this could be changed during build by modifying a string definition in |
|
the code. Effective version 2.12.0 this has become a build option |
|
with the build configuraton environment variable |
|
PEGASUS_INTEROP_NAMESPACE = <name for this namespace> however, |
|
the default if built without this change is still "root/PG_InterOp". |
|
Effective with OpenPegasus 2.13.0 the reupgrade utility has been |
|
extended to allow existing repositories to be converted from the use of |
|
"root/PG_Interop" to "interop" (See discussion above). The |
|
default in the CVS source code is still "root/PG_InterOp".<br> |
|
</li> |
|
<li><b>OpenPegasus WSMAN protocol on windows does not handle NaN, INF, |
|
or -INF</b>However, t (bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>) |
|
- If requests or responses include properties or parameters with |
|
floating point property types (Real32 or Real64) with the special |
|
states NaN, INF, or -INF on a Windows platform, the input is not |
|
accepted because these special strings are not understood by the |
|
decoder on Windows.</li> |
|
<li><b>OpenPegasus outputs Nan, INF, -INF special values for Real32 and |
|
Real64 property and Parameter types for the CIM/XML protocol</b> - |
|
(bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9392">9392</a>). |
|
Today the DMTF Specification DSP0201 allows only numeric information |
|
in the format definition for this type and does not all the special |
|
strings Nan, etc. However, OpenPegasus actually outputs the special |
|
strings if that is what is defined in the internal values. |
|
OpenPegasus does not allow these special Strings on input however,</li> |
|
<li><b>OpenPegasus does not handle covered properties</b> - (bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">3571</a>) |
|
Covered properties (properties which have the same name in a |
|
superclass and subclass without overridding the property in the |
|
superclass) are not allowed in OpenPegasus. While the requirement for |
|
this functionality was added to DSP0004 subsequent to version 2.4, the |
|
general agreement is that the requirement itself is not supportable |
|
and particularly not with the existing OpenPegasus APIs. |
|
Further, the requirement is expected to be removed in the future (i.e |
|
CIM 3.0).</li> |
|
<li><span style="font-weight: bold;">FQL Query Language</span> |
|
(bug 9956) incorporated has some limitations with respect to the DMTF |
|
defined Query Language (does not support full regex defined in the |
|
specification and does not support embedded instance comparison).<br> |
|
</li> |
| |
<hr size=2 width="100%" noshade color="#009900" align=center> |
</ol> |
| |
</span> |
<h2><b><span style="font-family: Times;">OpenPegasus <a name="Supported Platforms">Supported |
<p> </p> |
Platforms</a></span></b></h2> |
| |
</body> |
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 for 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.<br> |
|
<br> |
|
<b>Actively Supported Platforms (Nightly Tests Reported for this release)</b> |
|
<table class="MsoNormalTable" style="width: 90%;" border="1" cellpadding="0" cellspacing="1"> |
|
<tbody> |
|
<tr style=""> |
|
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 240px;" height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Platform and |
|
OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 75%;" height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">HP-UX<o:p> |
|
PA_RISC and Itanium</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 3.xx, 4.7) clang(The clang compiler usage |
|
is considered production effective OpenPegasus 2.13.0)</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 3.xx, 4.7) </span><span style="color: black;"><font size="3">clang(The clang compiler usage is considered </font></span><span style="color: black;"><font size="3"><span style="color: black;"><font size="3">production effective OpenPegasus 2.13.0</font></span>)</font></span></p> |
|
</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 not Actively supported for this release (No |
|
current Nightly Build Test Results)</b></p> |
|
<table class="MsoNormalTable" style="width: 90%;" id="table2" border="1" cellpadding="0" cellspacing="1"> |
|
<tbody> |
|
<tr style=""> |
|
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 240px;" height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Platform and |
|
OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 75%;" height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span style="color: black;"><o:p></o:p></span></p> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;"> <font size="3">Windows XP, Windows |
|
Vista, Windows 7, Windows Server 2008</font> </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
|
Compilers 2003 - 2010.. Note: Visual C++ Ver. 6 no longer being |
|
regular tested.Note that today there are some open issues with |
|
the Windows.</font> </td> |
|
</tr> |
|
<tr style=""> |
|
<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>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> |
|
<td><big><font style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later |
|
IA64</font></big></td> |
|
<td><big><font style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 |
|
or later required</font><font style="color: rgb(0, 0, 0);"> on |
|
OpenVMS IA64</font></big></td> |
|
</tr> |
|
<tr> |
|
<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> </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> |
|
</tbody> |
|
</table> |
|
<h3><b>Platform patches</b> </h3> |
|
<br> |
|
<font style="color: rgb(0, 0, 0);">The following is a list known of |
|
platform patches Pegasus requires.</font><br> |
|
<div style="margin-left: 40px;"> |
|
<ol> |
|
<li> <font style="color: rgb(0, 0, 0);">RHAS 2.1 needs the update to |
|
fix Red Hat Bugzilla 98815.</font><br> |
|
</li> |
|
<li> RHEL 4.4 multithreading bug in getpwuid-r could cause a CIM |
|
Server failure (Bugzilla 6232). This is fixed in RHEL 4.5<br> |
|
</li> |
|
<li> Red Hat and SUSE Linux multiple versions - multithreaded client |
|
intermittently fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red |
|
Hat bug 248052)</li> |
|
<li> OpenSLP Version 2.0 - This release of OpenSLP requires the |
|
patches for OpenSLP version 2.0 documented above.</li> |
|
</ol> |
|
</div> |
|
<br> |
|
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> |
|
<br> |
|
<br> |
|
Further information regarding Pegasus support on HP platforms can be found |
|
at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.<br> |
|
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2> |
|
The OpenPegasus Bugzilla database documents defects found in Pegasus |
|
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus |
|
bugzilla database</a>. Effective with the start of the |
|
OpenPegasus 2.6 work, ALL changes to the OpenPegasus CVS tree are |
|
documented through bugs. Therefore all source code changes to OpenPegasus |
|
are documented through bugs providing a complete history of changes and |
|
the reasons for those changes. Bugs reports are 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 OpenPegasus 2.6 |
|
and all subsequent versions. Therefore, a search of the OpenPegasus |
|
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>, |
|
etc) will yield all changes to the Pegasus CVS tree for that OpenPegasus |
|
release.<br> |
|
<br> |
|
- Changes for this release (bugs Tagged |
|
2.14.0_APPROVED). The link is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.13.0_APPROVED"> |
|
Pegasus 2.13.0_APPROVED bug list.</a><br> |
|
<h2><a name="Pegasus Release Control and Version Definition Documentation">Release |
|
Control |
|
and Version Definition Documentation</a></h2> |
|
The OpenPegasus project is controlled largely through the CVS repository |
|
and 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.<br> |
|
<br> |
|
The following documentation defines the characteristics of this Pegasus |
|
release. The documents are available in the OpenPegasus CVS |
|
repository. <br> |
|
<ul> |
|
<li><b> OpenPegasus Release Definition/Status - (See Wiki Section <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_12_x">OpenPegasus |
|
2.13.x |
|
Release Status</a>) - <span style="font-weight: normal;">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>. </b></li> |
|
<b> </b><span style="font-weight: bold;"></span><b>OpenPegasus |
|
Build and Configuration Options for Selected Platforms - <span style="font-weight: normal;">In previous versions of Pegasus this |
|
information was released as a Pegasus PEP. Starting with |
|
Pegasus 2.9.0 the information is located in the OpenPegasus CVS |
|
repository as <big style="font-weight: bold;"> <span style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</span></big>.</span></b><b> |
|
</b> |
|
<li><b> OpenPegasus External Interfaces -<span style="font-weight: normal;">The |
|
list of the OpenPegasus interfaces that are considered external |
|
and therefore "frozen". Unless an exception is explicitly approved |
|
by the Steering Committee all subsequent releases of Pegasus MUST |
|
continue to support these interfaces. Interfaces not explicitly |
|
listed in this document, should be considered as internal and |
|
subject to change.In previous Pegasus releases this information |
|
was available as a separate PEP. Starting with Pegasus 2.9.0 this |
|
information is integrated into the Pegasus repositoryas </span><small style="font-weight: bold;"><font face="Courier New" size="4"><small>pegasus/doc/EnternalInterface.html</small></font></small><span style="font-weight: normal;">.</span></b></li> |
|
<b> </b> |
|
<li><b> OpenPegasus SDK Packaging Definition - <span style="font-weight: normal;">Defines |
|
the recommended set of files for inclusion in the OpenPegasus SDK. |
|
Starting with Pegasus release 2.11.0, this document is available |
|
in the Pegasus CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>. |
|
In previous Pegasus releases this document was made available as s |
|
separate Pegasus PEP document rather than in the CVS repository.</span> |
|
</b></li> <b> </b> <b> </b> |
|
<li><b> Pegasus Runtime Packaging Definition - <span style="font-weight: normal;">Defines |
|
the recommended set of files for inclusion in this OpenPegasus |
|
release. Starting with Pegasus release 2.11.0, this idocument |
|
contained in the CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/RuntimePackaging.html</samp></big>. |
|
In previous releases this was made available as a seperate Pegasus |
|
PEP document rather than in the CVS repository. </span> </b></li> |
|
<b> </b> <b> </b> |
|
<li><b>Pegasus Release Notes - <span style="font-weight: normal;"> |
|
</span>PEP 368 - <span style="font-weight: normal;"> (This document |
|
is located in the approved PEP repository and the OpenPegasus |
|
source tree root directory </span></b><span style="font-weight: normal;">(<big><span style="font-family: monospace;">pegasus/ReleaseNotes.htm</span></big>)</span></li> |
|
<b> </b> |
|
</ul> |
|
<h2><b><a name="General Documentation">General OpenPegasus Documentation</a></b></h2> |
|
<br> |
|
The following documentation is available for the this Pegasus release:<br> |
|
<ul style="margin-top: 0in;" type="disc"> |
|
<b> </b> |
|
<li class="MsoNormal" style="color: black;"><b><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> |
|
<b> </b> </li> |
|
<li class="MsoNormal" style="color: black;"><b><b>API and usage |
|
documentation</b> - </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> </b> </li> |
|
<li class="MsoNormal" style="color: black;"><b><b>Building and Debugging |
|
Providers </b>- </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> </b> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"><b><b>Building and Debugging |
|
Clients</b> -</b>API documentation and the documentation on the |
|
Pegasus Technical Workshop which is available on the Pegasus web site. |
|
<b> </b> </li> |
|
<li class="MsoNormal" style="color: black;"><b><b>PEPs</b> -</b>The |
|
features of Pegasus that have been installed in this and the previous |
|
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. </li> |
|
<li class="MsoNormal" style="color: black;"><span style="font-weight: bold;">OpenPegasus |
|
WIKI</span> - This WIKI is maintained both for the use of the |
|
development team and as a user information resource. The wiki |
|
can be accessed at <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start</a></li> |
|
</ul> |
|
<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> |
| |
</html> |
|
|
</body></html> |