version 1.12, 2007/10/16 17:27:28
|
version 1.21, 2015/03/18 17:07:01
|
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
<html xmlns:v="urn:schemas-microsoft-com:vml"> |
<html xmlns:v="urn:schemas-microsoft-com:vml"><head> |
<head> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> |
<style> | <style> |
st1\:*{behavior:url(#ieooui) } | st1\:*{behavior:url(#ieooui) } |
</style> | </style> |
|
|
font-size:10.0pt; | font-size:10.0pt; |
font-family:"Times New Roman"} | font-family:"Times New Roman"} |
</style> | </style> |
<link rel="Edit-Time-Data" |
<link rel="Edit-Time-Data" href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso"><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="http://www.openpegasus.org/pp/uploads/40/6165/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" name="City"></o:smarttagtype> |
|
<o:smarttagtype |
|
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype |
|
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml> |
|
<o:DocumentProperties> |
|
<o:Author>IBM_User</o:Author> |
|
<o:LastAuthor> </o:LastAuthor> |
|
<o:Revision>4</o:Revision> |
|
<o:TotalTime>211</o:TotalTime> |
|
<o:Created>2004-04-05T14:13:00Z</o:Created> |
|
<o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> |
|
<o:Pages>1</o:Pages> |
|
<o:Words>5026</o:Words> |
|
<o:Characters>28651</o:Characters> |
|
<o:Company>IBM</o:Company> |
|
<o:Lines>238</o:Lines> |
|
<o:Paragraphs>67</o:Paragraphs> |
|
<o:CharactersWithSpaces>33610</o:CharactersWithSpaces> |
|
<o:Version>10.4219</o:Version> |
|
</o:DocumentProperties> |
|
</xml><![endif]--><!--[if gte mso 9]><xml> |
|
<w:WordDocument> |
|
<w:SpellingState>Clean</w:SpellingState> |
|
<w:GrammarState>Clean</w:GrammarState> |
|
<w:Compatibility> |
|
<w:ApplyBreakingRules/> |
|
</w:Compatibility> |
|
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> |
|
</w:WordDocument> |
|
</xml><![endif]--> |
|
</head> |
|
<body lang="EN-US" link="blue" vlink="blue"> |
|
<div class="Section1"> | <div class="Section1"> |
<div class="MsoNormal" style="text-align: center;" align="center"><span |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
style="color: black;"> |
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
<hr align="center" color="#009900" noshade="noshade" size="2" |
<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;" align="center"><b><span style="font-size: 13.5pt; color: black;">OpenPegasus Enhancement |
width="100%"></span></div> |
Proposal (PEP)<o:p></o:p></span></b></p> |
<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;"> | <p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"> |
|
|
<br> | <br> |
|
<b>PEP #:</b> 368<br> |
<b>PEP #:</b> 306<br> |
|
|
|
</span></p> | </span></p> |
|
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release |
Notes for OpenPegasus 2.7.0</p> |
Notes for OpenPegasus version 2.14.0</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 20 November 2014<br> |
|
</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 3 October 2007</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Karl |
|
Schopmeyer<br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Karl Schopmeyer<br> |
|
|
|
</p> | </p> |
|
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>draft</p> | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>draft</p> |
|
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p> | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p> |
|
<table class="MsoNormalTable" style="width: 100%;" id="table1" border="1" cellpadding="0" cellspacing="1" height="155" width="100%"> |
<table class="MsoNormalTable" style="width: 100%;" border="1" cellpadding="0" cellspacing="1" width="100%" height="155" id="table1"> |
|
|
|
<tbody> | <tbody> |
|
|
<tr style=""> | <tr style=""> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" height="27"> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27"> |
|
|
|
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> | <p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
|
|
</td> | </td> |
|
|
</tr> | </tr> |
|
|
<tr style=""> | <tr style=""> |
|
|
<td style="padding: 0.75pt;" height="22"> | <td style="padding: 0.75pt;" height="22"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><font size="2"> 0.99</font><o:p></o:p></span></p> |
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><font size="2"> 1.0</font><o:p></o:p></span></p> |
|
|
|
</td> | </td> |
|
|
<td style="padding: 0.75pt;" align="left" height="22"> | <td style="padding: 0.75pt;" align="left" height="22"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"> <font size="2"><span style="font-family: Arial;">12 Nov. 2014<br> |
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><o:p><font size="2"> </font></o:p></span><font size="2"><span style="font-family: Arial">3 |
</span></font></p> |
October 2007</span></font></p> |
|
|
|
</td> | </td> |
|
|
<td style="padding: 0.75pt;" align="left" height="22"> | <td style="padding: 0.75pt;" align="left" height="22"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"> <span style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> |
<p class="MsoNormal" style="text-align: center;" align="center"> |
|
<span style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> |
|
|
|
</td> | </td> |
|
|
<td style="padding: 0.75pt;" height="22"> | <td style="padding: 0.75pt;" height="22"> |
|
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial Submission for review<span style="color: red;"></span></font><o:p><font size="2"> </font></o:p></span></p> |
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial |
|
Submission</font><o:p><font size="2"> |
|
</font></o:p></span></p> |
|
|
|
</td> | </td> |
|
|
</tr> | </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> | <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> |
| |
<td style="padding: 0.75pt;" align="center" height="21">1.1</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> |
| |
<td style="padding: 0.75pt;" align="center" height="21">8 October 2007</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> |
| |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</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> |
| |
<td style="padding: 0.75pt;" height="21">Incorporate data from 2.6.1 |
</tr> |
release notes. Fix per comments in 1.0</td> |
|
| |
|
<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> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9832">9832</a><br> |
|
</td> |
|
<td>Include cimcli in release packages<br> |
|
</td> |
| |
<tr style=""> |
</tr> |
| |
<td style="padding: 0.75pt;" align="center" height="21">1.2</td> |
<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> |
| |
<td style="padding: 0.75pt;" align="center" height="21">11 October 2007</td> |
</tr> |
|
<tr> |
|
<td style="text-align: center;"><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9892">9892</a><br> |
|
</td> |
|
<td>Reduce overhead of use of PAM by use of a |
|
SessionCookie. This also introduces a new runtime configuration |
|
parameter to control the session timeout<br> |
|
</td> |
| |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</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> |
| |
<td style="padding: 0.75pt;" height="21">Comments from V 1.1 and add |
</tr> |
existing document links. Add pep 302 to enhancements</td> |
<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> |
|
<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> | <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> |
| |
<td style="padding: 0.75pt;" align="center" height="21">1.3</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> |
| |
<td style="padding: 0.75pt;" align="center" height="21">15 October 2007</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> |
| |
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</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> |
| |
<td style="padding: 0.75pt;" height="21">Add final links</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> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
| |
<tr style=""> |
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
| |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" width="7%"><br> |
|
</td> |
|
<td align="left" width="75%"><br> |
|
</td> |
| |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
| |
<td style="padding: 0.75pt;" align="center" height="23"> </td> |
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
| |
<td style="padding: 0.75pt;" height="23"> </td> |
</tr> |
|
<tr> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
<td><br> |
|
</td> |
| |
</tr> | </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> | </tbody> |
</table> | </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> |
| |
<div class="MsoNormal" style="text-align: center;" align="center"> |
After a successful client authentication the client is given a cookie. The |
<span |
client is then not asked for re-authentication as long as it provides the |
style="color: black;"> |
same cookie in all subsequent requests and until the session expires. Session |
<hr align="center" color="#009900" noshade="noshade" size="2" |
expiry is configurable using httpSessionTimeout configuration option. |
width="100%"></span></div> |
<br> |
<p><b>Abstract:</b> This document defines the release notes for the |
|
2.7.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 class="Section1"> |
|
<h2><span style="color: black;">OpenPegasus Functionality for This Release</span></h2> |
|
| |
Pegasus overall status by release is defined by a |
Nothing changes for clients that do not support HTTP cookies (RFC 6465) - |
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a> |
their requests are authenticated as usual, either using Basic or Negotiate |
that is available on the OpenPegasus web site . That web page shows the |
authentication mechanisms. |
Pegasus users and developers the status of the various features found in Pegasus |
<br> |
using a simple color coded key (white, red, yellow, green) and a description of |
<br> |
each feature.<p>Pegasus 2.7.0 |
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> |
is a major release, extending Pegasus 2.6 in selected |
<br> |
areas as described in the Pegasus PEP defining this release |
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> |
. </p> |
</span></span><h3>WEBAdmin (OpenPegasus 2.14.0)</h3>OpenPegasus has |
|
included on an experimental basis a web server that acts as an |
<p>The major areas of development for this release were as follows. For |
adminstration tool to replace the command line tools. This option |
more information access the PEP for each change defined:</p> |
presents the<br> |
|
same information as the major command line tools as web pages so that |
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font size="4"> |
parameters can be modified without using the command line tools. |
Table of Major Changes for this Release</font></p> |
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 |
<TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666 |
OpenPegasus<br> |
borderColorLight=#CCCCCC border=1 width="82%"> |
source tree for more detailed information on using WEBAdmin.<br> |
<TBODY> |
<br> |
<TR align="center"> |
Note: This option is considered experimental for 2.14<br> |
<TH bgColor=#00FFFF>PEP #</TH> |
<br> |
<TH bgColor=#00FFFF>Description of Change</TH> |
<h3>Using GCC 4.7 Compiler on Linux OS (OpenPegasus 2.13.0)<br> |
<TH bgColor=#00FFFF width="128">Posted PEP<br>Version</TH> |
</h3> |
</TR> |
As of 2.14.0, OpenPegasus has been updated to replace the custom atomic |
<TR align="center"> |
operations with GCC built-in atomic operations if GCC version 4.7 or |
<TD width="7%">284</TD> |
greater is used as the compiler. It is recommended that if possible |
<TD align="left" width="75%">Add Platform support IBM i5/PASE - Portable Application |
this version of the GCC compiler be used since the change provides |
Solutions Environment (PASE)</TD> |
significant performance improvements.<br> |
<TD width="128"> |
<h2> </h2> |
<a href="http://www.openpegasus.org/pp/uploads/40/14901/PEP284_Porting_Pegasus_to_i5PASE_platform.html"> |
<h3>OpenPegasus and OpenSLP V 2.0 (OpenPegasus 2.13.0)</h3> |
1.6</a></TD> |
As of 2.13.0, OpenPegasus slp fully supports IPV6 and has been |
</TR> |
tested with OpenSLP 2.0 (Recently released by <a href="http://openslp.org">OpenSlp.org</a>)<br> |
<TR align="center"> |
<br> |
<TD width="7%">286</TD> |
While testing OpenPegasus with OpenSLP 2.0 the OpenPegasus team found two |
<TD align="left" width="75%">Reduce the Amount of CIM Server code that runs Privileged |
issues with this version of OpenSLP. The patches documented below |
(Privilege Separation)</TD> |
allow this version of OpenSLP to work with OpenPegasus<br> |
<TD width="128"> |
<br> |
<a href="http://www.openpegasus.org/pp/uploads/40/14414/PEP286_PrivilegeSeparation.htm"> |
1) SLPReg used TCP connection previously, but it now uses UDP. Therefore, |
1.8</a></TD> |
a BUFFER_OVERFLOW exception occurs. This is because UDP cannot |
</TR> |
handle attribute size greater than network MTU size. In such cases, |
<TR align="center"> |
according to the specification, OpenSLP should automatically switch to |
<TD width="7%">291</TD> |
TCP. Since this has not been implemented in OpenSlp 2.0, the |
<TD align="left" width="75%">Add Support for IPv6 - Stage 1 (Note: This functionality |
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> |
was made available but normally disabled |
<br> |
<span style="font-family: Arial">Pegasus 2.6.1)</span></TD> |
2) On Windows, slpd service fails to start when IPV6 is enabled and throws |
<TD width="128"> |
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"> | <a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html"> |
1.2</a></TD> |
<font color="#3333ff">PEP 291</font></a><font color="#000000">.</font><br> |
</TR> |
<br> |
<TR align="center"> |
The IPv6 support in OpenPegasus is controlled by the PEGASUS_ENABLE_IPV6 |
<TD width="7%">62</TD> |
build variable. The default for this variable is "true"; setting this to |
<TD align="left" width="75%">Add IPV6 Support for SNMP Indication Handler |
|
and include NET-SNMP indication handler in Linux RPM </TD> |
|
<TD width="128"> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/3163/PEP062_SNMPMapper.pdf"> |
|
1.1</a></TD> |
|
</TR> |
|
<TR align="center"> |
|
<TD width="7%">130</TD> |
|
<TD align="left" width="75%">Enable Remote CMPI for Windows</TD> |
|
<TD width="128"> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/7775/RemoteCMPI1.2-PEP.html"> |
|
1.2</a></TD> |
|
</TR> |
|
<TR align="center"> |
|
<TD width="7%">302</TD> |
|
<TD align="left" width="75%">Enhanced Log File Support</TD> |
|
<TD width="128"> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/14902/PEP302_LogFileSupportFinal.html"> |
|
1.0</a></TD> |
|
</TR> |
|
<TR align="center"> |
|
<TD width="7%">258</TD> |
|
<TD align="left" width="75%">Add support for certificate-based authentication audit |
|
logging</TD> |
|
<TD width="128"> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/14428/PEP258_AuditLogging.htm"> |
|
1.5</a></TD> |
|
</TR> |
|
<TR align="center"> |
|
<TD width="7%">Bugzilla 6466</TD> |
|
<TD align="left" width="75%">Add two new trace components to facilitate |
|
triage of indication delivery issues</TD> |
|
<TD width="128"> |
|
<a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=6466"> |
|
Bug 6466</a></TD> |
|
</TR> |
|
</TBODY> |
|
</TABLE> |
|
</html> |
|
<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 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> | 'false' before building OpenPegasus will disable the IPv6 support.<br> |
</p> |
<br> |
<p>The following subsections provide |
The following subsections provide some information on IPv6 support for the |
some information on IPv6 support for the Linux and Windows platforms. |
Linux and Windows platforms. Note that in the 2.6.1 release there is no |
Note that in the 2.6.1 release there is no automatic run-time detection |
automatic run-time detection of IPv6 support on a platform by OpenPegasus. |
of IPv6 support on a platform by OpenPegasus. If you build with |
If you build with PEGASUS_ENABLE_IPV6=true, your platform must support |
PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you will |
IPv6 or you will get a build failure (missing header files), a run-time |
get a build failure (missing header files), a run-time bind() failure, |
bind() failure, or possibly some other failure. This applies to both the |
or possibly some other failure. This applies to both the CIM Server and |
CIM Server and Listener components. For more information on IPv6 support |
Listener components. For more information on IPv6 support for your |
for your specific platform, refer to the documentation for that platform.<br> |
specific platform, refer to the documentation for that platform.<br> |
<br> |
</p> |
All OpenPegasus externals that support eitcompilerher a hostname or an IP |
<p>All OpenPegasus externals that |
address as input have been updated to allow an IPv6 address to be |
support either a hostname or an IP address as input have been updated |
specified. If the required input is just an IP address (eg. no optional or |
to allow an IPv6 address to be specified. If the required input is just |
required port number), then the IPv6 address must be specified without |
an IP address (eg. no optional or required port number), then the IPv6 |
brackets. For example, the OpenPegasus osinfo client (which returns |
address must be specified without brackets. For example, the |
information about the OS running on a host system) takes separate host and |
OpenPegasus osinfo client (which returns information about the OS |
port options. In this case a host with an IPv6-configured network |
running on a host system) takes separate host and port options. In this |
interface would be specified as:<br> |
case a host with an IPv6-configured network interface would be |
<br> |
specified as:<br> |
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">osinfo -h 3ffe:1:2:1 -p 5988</font></big></div> |
</p> |
<br> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);"><font color="#000000">osinfo -h |
But the cimcli command, which takes an optional "location" option |
3ffe:1:2:1 -p 5988</font></div> |
including an optional port number, requires the IPv6 address to be |
<p>But the cimcli command, which |
delimited with brackets, for example:<br> |
takes |
<br> |
an optional "location" option including an optional port number, |
<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns -l |
requires the IPv6 address to be delimited with brackets, for example:<br> |
[3ffe:1:2:1]</big></div> |
</p> |
|
<div style="margin-left: 40px;">cimcli ns -l [3ffe:1:2:1]</div> |
|
<p>or</p> | <p>or</p> |
<div style="margin-left: 40px;">cimcli ns -l [3ffe:1:2:1]:5989<br> |
<div style="margin-left: 40px;"><big><span style="font-family: monospace;">cimcli |
|
ns -l [3ffe:1:2:1]:5989</span></big><br> |
</div> | </div> |
<br> | <br> |
For more information on |
For more information on specifying IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF |
specifying |
RFC |
IPv6 addresses, refer to <a |
2373 - IP Version 6 Addressing Architecture</a> and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF |
href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP Version |
RFC 2732 - Format for Literal IPv6 Addresses in URL's</a>.<br> |
6 Addressing Architecture</a> |
|
and <a |
|
href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 - Format for |
|
Literal IPv6 Addresses in URL's</a>.<br> |
|
<h4><font color="#000000">IPv6 on Linux</font></h4> | <h4><font color="#000000">IPv6 on Linux</font></h4> |
<p>Modern Linux distributions already |
Modern Linux distributions already contain IPv6-ready kernels, the IPv6 |
contain IPv6-ready kernels, the |
capability is generally compiled as a module, but it's possible that this |
IPv6 capability is generally compiled as a module, but it's possible |
module is not loaded automatically on startup.<br> |
that this module is not loaded automatically on startup.</p> |
<br> |
<p>Note: |
<span style="font-weight: bold;">Note: </span>you shouldn't use |
you shouldn't anymore use kernel series 2.2.x, because it's not |
kernel series 2.2.x, because it's not IPv6-up-to-date anymore. Also the |
IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no |
IPv6 support in series 2.4.x is no longer improved according to |
longer improved according to definitions in latest RFCs. It's recommend |
definitions in latest RFCs. It's recommend to use series 2.6.x now.<br> |
to use series 2.6.x now.<br> |
<br> |
</p> |
To check whether your current running kernel supports IPv6, take a look |
<p>To check whether your current |
into your /proc filesystem. The entry /proc/net/if_inet6 must exist. A |
running |
short automated test looks like:<br> |
kernel supports IPv6, take a look into your /proc filesystem. The entry |
<br> |
/proc/net/if_inet6 must exist. A short automated test looks like:<br> |
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">test -f /proc/net/if_inet6 && echo "Running |
</p> |
kernel is IPv6 ready"</font></big></div> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);"><font color="#000000">test -f |
<br> |
/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"</font></div> |
For more iSchema version default update to CIM 2.36nformation on enabling |
<p>For more information on |
IPv6 in the Linux kernel and configuring network interfaces, refer to <a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux |
enabling |
|
IPv6 in the Linux kernel and configuring network interfaces, refer to |
|
<a |
|
href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux |
|
Documentation Project's IPv6 HOWTO</a>.<br> | Documentation Project's IPv6 HOWTO</a>.<br> |
<br> | <br> |
<span style="font-weight: bold;">Warning</span>: |
<span style="font-weight: bold;">Warning</span>: There is currently an |
There is currently an open issue with RedHat to address a problem that |
open issue with RedHat to address a problem that is seen intermittently on |
is seen intermittently on RHEL5 and SLES10 systems. This problem is |
RHEL5 and SLES10 systems. This problem is described in <span style="color: rgb(153, 51, 153);"> |
described in <span |
<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
style="color: rgb(153, 51, 153);"> |
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 |
<a |
bug |
href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
248052</a>, </span>and manifests itself as an intermittent IPv6 |
bug 6586</a> |
socket failure. You should be aware that OpenPegasus with IPv6 enabled may |
</span> |
be significantly impacted in these environments.<br> |
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.</p> |
|
<h4><font color="#000000">IPv6 on Windows</font></h4> | <h4><font color="#000000">IPv6 on Windows</font></h4> |
<p>Microsoft provides supported IPv6 |
<br> |
implementations for Windows Server |
Microsoft provides supported IPv6 implementations for Windows Server 2003, |
2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service |
Windows XP with Service Pack 1 (SP1), Windows XP with Service Pack 2 |
Pack 2 (SP2), and Windows CE .NET 4.1 and later.</p> |
(SP2), and Windows CE .NET 4.1 and later.<br> |
On Windows XP, you can use the <span |
<br> |
style="font-weight: bold; ">ipv6.exe</span> tool to install, uninstall, and |
On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span> |
query |
tool to install, uninstall, and query your IPv6 configuration. For |
your IPv6 configuration. For example:<br> |
example:<br> |
<br> |
<br> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);"><font color="#000000">ipv6 install<br> |
<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big><font color="#000000">ipv6 install<br> |
ipv6 if</font></div> |
ipv6 if</font></big></div> |
<p>Windows Vista |
<br> |
and Windows Server 2008 support an integrated |
Windows Vista and Windows Server 2008 support an integrated IPv4 and IPv6 |
IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack. |
implementation known as the Next Generation TCP/IP stack. Note that the |
Note that the OpenPegasus IPv6 support has not yet been tested |
OpenPegasus IPv6 support has not yet been tested on Windows Vista or |
on Windows Vista or Windows Server 2008.<br> |
Windows Server 2008.<br> |
<br> |
<br> |
For more information on |
For more information on installing, configuring, and using IPv6 on Windows |
installing, configuring, and using IPv6 on Windows platforms, refer to |
platforms, refer to the document <a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"><font color="#000000">IPv6 for Microsoft Windows: Frequently Asked Questions</font></a>.<br> |
the document |
<br> |
<a |
<h4><font color="#000000">Testing OpenPegasus IPv6 support</font></h4> |
href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"> |
As part of the OpenPegasus automated tests, the TestClient, g11ntest, and |
<font color="#000000">IPv6 |
IndicationStressTest test clients were modified to run tests using the |
for Microsoft Windows: Frequently Asked Questions</font></a>.<br> |
IPv6 loopback address (::1) if PEGASUS_ENABLE_IPV6=true.<br> |
</p> |
<br> |
<h4><font color="#000000">Testing your OpenPegasus IPv6 |
You can also perform manual tests using the IPv6 loopback or a real |
support</font></h4> |
IPv6-configured network interface. For example, using the IPv6 loopback on |
As part of the OpenPegasus |
a system with OpenPegasus running on the WBEM standard http port of 5988:<br> |
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> | <div style="margin-left: 40px;"><br> |
osinfo -h ::1</div> |
<big style="font-family: monospace;"> osinfo -h ::1</big></div> |
<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2> |
<h2><a name="Compatibility_Considerations_">OpenPegasus Compatibility |
<p>Support for forward-compatibility is a fundamental design principle for the |
Considerations</a></h2> |
OpenPegasus project. As a Community, our goal is for well-behaved OpenPegasus |
Support for forward-compatibility is a fundamental design principle for |
Providers or Clients, using only the externally defined OpenPegasus interface, |
the OpenPegasus project. As a community, our goal is for well-behaved |
to continue to work with a minor version upgrade of OpenPegasus. However, there |
OpenPegasus providers or clients, using only the externally defined |
are certain classes of errors (e.g., non-compliance with a standard that |
OpenPegasus interface, to continue to work with a minor version upgrade of |
significantly affects interoperability) that may require the Community to make |
OpenPegasus. However, there are certain classes of errors (e.g., |
potentially incompatible changes. The following table contains a list of defect |
non-compliance with a standard that significantly affects |
fixes that MAY impact, even well-behaved, OpenPegasus Providers or Clients when |
interoperability) that may require the community to make potentially |
upgrading to OpenPegasus 2.7.0.</p> |
incompatible changes. The following table contains a list of defects/fixes |
<TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666 |
that MAY impact, even well-behaved, OpenPegasus providers or clients when |
borderColorLight=#CCCCCC border=1 width="80%"> |
upgrading to this OpenPegasus release. <br> |
<TBODY> |
<br> |
<TR align="center"> |
<table style="font-family: Arial;" bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="80%"> |
<TH bgColor=#00FFFF width=10%>Bugzilla #</TH> |
<tbody> |
<TH bgColor=#00FFFF>Description</TH> |
<tr align="center"> |
</TR> |
<th bgcolor="#00ffff" width="10%">Bugzilla #</th> |
<TR align="center"> |
<th bgcolor="#00ffff">Description</th> |
<TD>6476</TD> |
</tr> |
<TD align="left"><font face="Times New Roman">HP-UX only: Introduction of the "explicit" keyword in CIMClass.h and CIMInstance.h may introduce |
<tr align="center"> |
a compile error in some code. Specifically, a compiler-supplied automatic conversion from CIMObject |
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8830">Bug |
type to CIMClass or CIMInstance has been removed. The cast operation must be explicitly specified. |
8830</a></td> |
</font> |
<td align="left">Starting |
</TD> |
with OpenPegasus 2.11.0 the requirement for providers (CMPI and C++) to |
</TR> |
filter properties from instances has been relieved. The server will do |
<TR align="center"> |
the filtering at the protocol adapter level. To avoid a negative impact |
<TD>6608</TD> |
on performance the CIMInstance::filter() and |
<TD> |
CMPIInstanceFT.setPropertyFilter() functions have been changed to a |
<p align="left">WIPCR00430 recommends an unquoted charset parameter in Content-type header. See the writeup in this bug for a discussion of the validation of the charset parameter in various OpenPegasus releases. In 2.7 we perform "extended" validation that should ignore differences based on whitespace or quotes. The CR recommendation is to not use quotes on the charset parameter, but only at a time when it is expected that all CIMOMs have been updated to accept the charset parameter with or without quotes.</TD> |
NOP. This may be a change in behavior for provider relying in some |
</TR> |
unknown way on the instance being filtered through these functions. To |
<TR align="center"> |
allow users to actually filter properties from an instance in a |
<TD>6458/6770</TD> |
provider, a new function (CIMInstance::filterInstance()) will actually |
<TD> |
filter properties from an instance exactly as the CIMInstance::filter() |
<p align="left">The MOF Compiler now rejects some property values that are invalid according to the DMTF specification that it previously accepted.</TD> |
did in previous versions of Pegasus. This is not required since the |
</TR> |
CIMServer will do the filtering but allows the provider to prefilter |
</TBODY> |
properties if it so desires, in particular where properties might be |
</TABLE> |
very large or there would be a significant number of properties.<br> |
</html> |
</td> |
|
</tr> |
|
<tr align="center"> |
<h2>OpenPegasus Relationship to |
<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9369">Bug |
CIM/WBEM Standards</h2> |
9369</a><br> |
<p>Pegasus was designed and implemented to comply with the DMTF |
</td> |
CIM/WBEM specifications The following table defines the level of the |
<td align="left"><span style="font-weight: bold;">NOTE: This bug |
DMTF specifications to which this version of Pegasus aims to conform |
fixed in OpenPegasus 2.13.0. </span>Reregistering of an |
today.</p> |
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%"> | <table id="AutoNumber1" border="1" cellspacing="1" width="80%"> |
<tbody> | <tbody> |
<tr> | <tr> |
|
|
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0200 - CIM Operations over HTTP</td> | <td width="33%">DSP 0200 - CIM Operations over HTTP</td> |
<td width="33%">1.2.0, preliminary, 9 December 2004</td> |
<td width="33%">Version 1.4, 26 August 2013<br> |
|
</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0201 - Representation of CIM in XML</td> | <td width="33%">DSP 0201 - Representation of CIM in XML</td> |
<td width="33%">2.2.0, preliminary, December 2004</td> |
<td width="33%">Version 2.4.0 16 January 2014<br> |
|
</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0202 - CIM Query Language Specification</td> | <td width="33%">DSP 0202 - CIM Query Language Specification</td> |
|
|
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">CIM Schema </td> | <td width="33%">CIM Schema </td> |
<td width="33%">2.13.1 Final, Jan. 2005 ( default) </td> |
<td width="33%">2.36.0 Final ( default build Schema) </td> |
</tr> | </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> |
|
|
</tbody> | </tbody> |
</table> | </table> |
<h2><a name="Conformance with DMTF Specifications">Conformance |
<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIA SMI |
Exceptions to |
Profiles Supported</h2> |
DMTF Specifications</a></h2> |
<br> |
<p>It is a major goal |
Today OpenPegasus includes support for several DMTF profiles including:<br> |
of the OpenPegasus project to both drive and utilize the DMTF CIM/WBEM |
<ol> |
specifications. However, today there are a number of known |
<li>DMTF ProfileRegistration Version DSP 1033, Version 1.0.0</li> |
differences. |
<li>DMTF Indications DSP 1054, Version 1.1.0. Since this is effectively the same as the |
As of this release, some of the differences include the following:</p> |
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> | <ol> |
<li><b>Provider Registration</b> - Pegasus supports registration |
<li><b>Provider Registration</b> |
through a set of Pegasus Provider registration classes rather than |
- Pegasus supports registration through a set of Pegasus Provider |
support the DMTF defined Provider Qualifier. Pegasus will not support |
registration classes rather than support the DMTF defined Provider |
this qualifier in the future. See the readme for more information on |
Qualifier. Pegasus will not support this qualifier in the future. See |
provider registration. This is not a deviation from the |
the readme for more information on provider registration. This is |
specifications but is a different method of registration than many CIM |
not really a deviation from the specifications since there is no |
Servers and means that the the provider qualifier is unused in Pegasus.</li> |
specification or profile for provider registration today but is a |
<li><b>Indications </b>-Today Pegasus supports process |
different method of registration than many CIM Servers and means that |
indications and lifecycle indications when defined specifically by |
the the provider qualifier is unused in Pegasus.</li> |
|
<li><b>Lifecycle Indications </b>-Today Pegasus supports process |
|
iPegasusndications and lifecycle indications when defined specifically by |
providers. Pegasus does not support lifecycle indications if they are | providers. Pegasus does not support lifecycle indications if they are |
not defined by the provider or for changes to CIM Classes.<font |
not defined by the provider or for changes to CIM Classes.<font color="#ff0000"> |
color="#ff0000"> </font><span class="norm"><font color="#ff0000"> </font>For |
</font><span class="norm"><font color="#ff0000"> </font>For more |
more information see the Pegasus CVS file:<a name="comtag_137"><font size="2"> |
information see the Pegasus CVS file:<a name="comtag_137"><font size="2"> |
</font><font |
</font><font face="Courier New" size="2"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a><font size="2">.</font></span></li> |
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 |
<li> |
option |
<p class="MsoNormal"><font |
on Instance Operations</font><span style="color: black;"><b> </b> |
style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers |
- The DMTF specifications have deprecated the use of qualifiers on |
option on Instance Operations</font><span style="color: black;"><b> </b> |
instance operations with the 1.2 CIM Operations Over HTTP Specification (DSP0200) and |
- |
stated specifically that the client should NOT depend on the |
The DMTF specifications have deprecated the use of qualifiers on |
includeQualifiers parameter of the CIM/XML instance operations |
instance operations with the 1.2 CIM Operations Specification. |
returning qualifiers. Some CIM Client implementations expect |
Some CIM Client implementations expect instances |
instances returned from the CIM Server to include the qualifiers |
returned |
defined in the class definition (such as KEY qualifiers on |
from the CIM Server to include the qualifiers defined in the class |
properties). Pegasus today expects the provider to |
definition (such as KEY qualifiers on properties). </span> Pegasus |
complete the qualifiers on instances in accordance with the |
today expects the provider to complete the qualifiers on instances in |
specification and generally the interpretation is that Pegasus |
accordance with the specification and generally the interpretation is |
applies class level qualifiers when the includeInstance parameter is |
that Pegasus applies class level qualifiers when the includeInstance |
supplied on instance operations. However, Pegasus today is |
parameter is supplied on instance operations. However, Pegasus |
inconsistent in the return of qualifiers so that the user should NOT |
today is inconsistent in the return of qualifiers so that the user |
depend on Pegasus accurately honoring the includeQualifier parameter |
should NOT depend on Pegasus accurately honoring the includeQualifier |
for instance operations. In the future it is expected that |
parameter for instance operations. In the future it is expected |
Pegasus will deprecate the use of qualifiers on instance operations |
that Pegasus will deprecate the use of qualifiers on instance |
completely. When Pegasus uses object normalization, the |
operations completely.<font color="#ff0000"> </font></p> |
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> |
<li><b>LocalOnly option on instance |
<li><span style="font-weight: bold;">MOF Namespace Pragma</span> -The |
Operations </b>- With the 1.1 version of Specification for CIM |
Pegasus compiler does not support the namespace pragma defined in DSP |
Operations over HTTP, the definition of the LocalOnly parameter for the |
0004. Namespaces for the OpenPegasus repository are defined through |
GetInstance and Enumerate Instances operations was modified. This change |
arguments for the MOF Compiler<br> |
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> |
<li> |
<li><b>CIMOperation Trailer </b>- Pegasus implements chunking based on |
<p class="MsoNormal"><b>MOF Compiler namespace pragma</b> - The |
the DSP0200 1.2.0 preliminary spec. including the operation trailer |
Pegasus compiler does not support the namespace pragma.</p> |
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> |
<li>Pegasus implements |
<li><b>OpenPegasus WSMAN protocol on windows does not handle NaN, INF, |
chunking |
or -INF</b>However, t (bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>) |
based on the DSP0200 1.2.0 preliminary spec. including the operation trailer |
- If requests or responses include properties or parameters with |
defined in that specification Refer to bug |
floating point property types (Real32 or Real64) with the special |
<a |
states NaN, INF, or -INF on a Windows platform, the input is not |
href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> for more details.<br> |
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> | </li> |
|
|
</ol> | </ol> |
<h2><b><span style="font-family: Times;">OpenPegasus <a |
|
name="Supported Platforms">Supported |
<h2><b><span style="font-family: Times;">OpenPegasus <a name="Supported Platforms">Supported |
Platforms</a></span></b></h2> | Platforms</a></span></b></h2> |
<p>Each OpenPegasus release lists as 'active' platforms those |
|
|
Each OpenPegasus release lists as 'active' platforms those |
hardware/software platforms that have recognized ports for the Pegasus | hardware/software platforms that have recognized ports for the Pegasus |
code |
code base including a maintainer for the platform that will be willing to |
base including a maintainer for the platform that will be willing to |
regularly document issues and/or fix defects as the Pegasus code base is |
regularly document issues and/or fix defects as the Pegasus |
changed. Pegasus may be operable on other platforms (ex. Windows 98) |
code base is changed. |
but without a group to provide the role of test and maintenance, correct |
Pegasus may be operable on other platforms (ex. Windows 98) but without |
operation of Pegasus cannot be assured. In all cases, |
a group |
including the active platforms, it is the responsibility of the entity |
to provide the role of test and maintenance, correct operation of |
that packages and/or compiles OpenPegasus for shipment or deployment, to |
Pegasus cannot be |
read, and actively monitor the Pegasus Bugzilla database for a list of |
assured. In all cases, including the active platforms, it is the |
relevant defects that affect their platform. The platforms |
responsibility of the entity that packages and/or compiles OpenPegasus |
that are considered ported are shown in the two tables below. The |
for shipment or deployment, to read, and actively monitor the Pegasus |
first table represents platform for which testing is done on a regular |
bugzilla database for a list of relevant defects that affect their |
basis and reported to the Pegasus Nightly Build Test WEB Page. Those |
platform. The platforms that are considered 'active' for this |
platforms which have been ported but do not have test results that are |
Pegasus release are:<br> |
current at the time of the release are reported in the second table.<br> |
</p> |
<br> |
<table class="MsoNormalTable" style="width: 90%;" border="1" |
<b>Actively Supported Platforms (Nightly Tests Reported for this release)</b> |
cellpadding="0" cellspacing="1"> |
<table class="MsoNormalTable" style="width: 90%;" border="1" cellpadding="0" cellspacing="1"> |
<tbody> | <tbody> |
<tr style=""> | <tr style=""> |
<td |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 240px;" height="26"> |
style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 240px;" |
|
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Platform and | <p class="MsoNormal"><b><span style="color: black;">Platform and |
OS</span></b><span style="color: black;"><o:p></o:p></span></p> | OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 75%;" height="26"> |
style="padding: 0.75pt; background: #00FFFF 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 75%;" |
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span style="color: black;"><o:p></o:p></span></p> |
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span |
|
style="color: black;"><o:p></o:p></span></p> |
|
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span style="color: black;">HP-UX<o:p></o:p></span></p> |
<p class="MsoNormal"><span style="color: black;">HP-UX<o:p> |
|
PA_RISC and Itanium</o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span style="color: black;">HP <span |
<p class="MsoNormal"><span style="color: black;">HP <span class="SpellE">aC</span>++ |
class="SpellE">aC</span>++ B3910B<o:p></o:p></span></p> |
B3910B<o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">Linux |
style="color: black;">Linux on Power</span></span><span |
on Power</span></span><span style="color: black;"><o:p></o:p></span></p> |
style="color: black;"><o:p></o:p></span></p> |
|
</td> | </td> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
|
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">zLinux</span></span><span style="color: black;"><o:p></o:p></span></p> |
style="color: black;">zLinux</span></span><span style="color: black;"><o:p></o:p></span></p> |
|
</td> | </td> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
|
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
|
|
<p class="MsoNormal"><span style="color: black;">Linux Itanium<o:p></o:p></span></p> | <p class="MsoNormal"><span style="color: black;">Linux Itanium<o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
|
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; "> |
<td style="padding: 0.75pt;"> <span style="color: black;"><font size="3">Linux |
<span style="color: black;"><font size="3">Linux IA-32</font></span></td> |
IA-32</font></span></td> |
<td style="padding: 0.75pt; "> |
<td style="padding: 0.75pt;"> <span class="SpellE"><span style="color: black;"><font size="3">gcc</font></span></span><span style="color: black;"><font size="3"> (versions 3.xx, 4.7) clang(The clang compiler usage |
<span class="SpellE"><span |
is considered production effective OpenPegasus 2.13.0)</font><o:p></o:p></span></td> |
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> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span style="color: black;">Linux X86_64<o:p></o:p></span></p> | <p class="MsoNormal"><span style="color: black;">Linux X86_64<o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; "> | <td style="padding: 0.75pt; "> |
<p class="MsoNormal"><span class="SpellE"><span |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"> (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> |
style="color: black;">gcc</span></span><span style="color: black;"> |
|
(versions 2.9x, 3.xx, 4.xx)</span></p> |
|
</td> | </td> |
</tr> | </tr> |
|
<tr> |
|
<td style="vertical-align: top;"><font size="3">z/OS V1.7 and up</font></td> |
|
<td style="vertical-align: top;"><font size="3">XL C/C++ from z/OS |
|
Version 1.7 and up</font></td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
|
|
<p align="center"><b>Platforms not Actively supported for this release (No |
|
current Nightly Build Test Results)</b></p> |
|
<table class="MsoNormalTable" style="width: 90%;" id="table2" border="1" cellpadding="0" cellspacing="1"> |
|
<tbody> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; "> |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 240px;" height="26"> |
<p class="MsoNormal"><span style="color: black;">Windows 2000</span></p> |
<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> | </td> |
<td style="padding: 0.75pt; "> |
|
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler version. Works on VC .NET 2003 v7.1). |
|
NOTE: Visual C++ Ver. 6 no longer being regularly tested.</font></td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="padding: 0.75pt; "> <font size="3">Windows XP, Windows 2003</span></font></p> |
<td style="padding: 0.75pt;"> <font size="3">Windows XP, Windows |
</td> |
Vista, Windows 7, Windows Server 2008</font> </td> |
<td style="padding: 0.75pt; "> |
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
<font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1. |
Compilers 2003 - 2010.. Note: Visual C++ Ver. 6 no longer being |
Note: Visual C++ Ver. 6 no longer being regular tested. |
regular tested.Note that today there are some open issues with |
</font> |
the Windows.</font> </td> |
</td> |
|
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; "> <font size="3">MacOS version 10.3 and higher</font></td> |
<td style="padding: 0.75pt;"> <font size="3">MacOS version 10.3 and |
|
higher</font></td> |
<td style="padding: 0.75pt; "> <font size="3">gcc 4.01</font></td> | <td style="padding: 0.75pt; "> <font size="3">gcc 4.01</font></td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big>HP OpenVMS 8.3 or later Alpha</big></td> |
<td style="vertical-align: top;"><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris |
<td style="vertical-align: top;"><font size="3"> </font><big><font |
8</span></font></big></td> |
style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun CC |
style="color: rgb(153, 51, 153);">7.3-009 or later required</span> for OpenVMS |
compiler V 5.8. Note that the latest thread patch (108993) may |
Alpha</font></big></td> |
be required. (see Pegasus bug 4632)</big><br> |
|
</td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><span class="norm"></span><font |
<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> |
style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later IA64</font></big></td> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun WorkShop |
<td style="vertical-align: top;"><span class="norm"></span><big><font |
6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 or |
</td> |
later required</font><font |
|
style="color: rgb(0, 0, 0);"> on OpenVMS IA64</font></big></td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><font color="RED"><span |
<td><big>HP OpenVMS 8.3 or later Alpha</big></td> |
style="color: rgb(0, 0, 0);">Solaris 8</span></font></big></td> |
<td><big><font style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span style="color: rgb(153, 51, 153);">7.3-009 or later required</span> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
for OpenVMS Alpha</font></big></td> |
CC compiler V 5.8. Note that the latest thread patch (108993) may be |
|
required. (see Pegasus bug 4632)</big><br> |
|
</td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><span class="norm"></span><big><font |
<td><big><font style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later |
color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9</span></font></big></td> |
IA64</font></big></td> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
<td><big><font style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 |
WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
or later required</font><font style="color: rgb(0, 0, 0);"> on |
|
OpenVMS IA64</font></big></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">Windows 2000</span></p> |
</td> | </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
|
Ver. 6 and Microsoft .Net compiler version. Works on |
|
VC .NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being |
|
regularly tested.</font></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;"> <font size="3">Windows 2003</font> </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft Visual C++ |
|
Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++ |
|
Ver. 6 no longer being regular tested. </font> </td> |
|
</tr> |
|
<tr> |
|
<td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td> |
|
<td><big>CC Compiler Sun Studio 5.11</big></td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
|
<h3><b>Platform patches</b> </h3> |
<br> | <br> |
<b>Platform patches</b> |
<font style="color: rgb(0, 0, 0);">The following is a list known of |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font |
platform patches Pegasus requires.</font><br> |
style="color: rgb(0, 0, 0);">The following is a list known of platform |
|
patches Pegasus requires.</font></p> |
|
<div style="margin-left: 40px;"> | <div style="margin-left: 40px;"> |
<ol> | <ol> |
<li> |
<li> <font style="color: rgb(0, 0, 0);">RHAS 2.1 needs the update to |
<p style="margin-top: 0pt; margin-bottom: 0pt;"> |
fix Red Hat Bugzilla 98815.</font><br> |
<font |
</li> |
style="color: rgb(0, 0, 0);">RHAS |
<li> RHEL 4.4 multithreading bug in getpwuid-r could cause a CIM |
2.1 needs the update to fix Red Hat Bugzilla 98815.</font></p></li> |
Server failure (Bugzilla 6232). This is fixed in RHEL 4.5<br> |
<li> |
</li> |
<p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4 multithreading bug in |
<li> Red Hat and SUSE Linux multiple versions - multithreaded client |
getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is fixed in |
intermittently fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red |
RHEL 4.5</p></li> |
Hat bug 248052)</li> |
<li> |
<li> OpenSLP Version 2.0 - This release of OpenSLP requires the |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE Linux |
patches for OpenSLP version 2.0 documented above.</li> |
multiple versions - |
|
multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla |
|
6586) (Red Hat bug 248052)<br></p></li> |
|
</ol> | </ol> |
</div> | </div> |
<p>Further information regarding Pegasus support on IBM platforms can |
<br> |
be |
Further information regarding Pegasus support on IBM platforms can be |
found at: <a |
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> |
href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span |
<br> |
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> |
</p> |
Further information regarding Pegasus support on HP platforms can be found |
<p> Further information regarding Pegasus support on HP platforms can |
at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.<br> |
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> | <h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2> |
<p>The Pegasus bugzilla database documents any defects found in Pegasus |
The OpenPegasus Bugzilla database documents defects found in Pegasus |
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla |
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus |
database</a>. |
bugzilla database</a>. Effective with the start of the |
Effective with the start of the Pegasus 2.6 work, all changes to the CVS tree |
OpenPegasus 2.6 work, ALL changes to the OpenPegasus CVS tree are |
were documented through bugs. Bugs reports were filed not only for bugs and |
documented through bugs. Therefore all source code changes to OpenPegasus |
their corresponding fixes but also as part of the process of committing new code |
are documented through bugs providing a complete history of changes and |
representing the work on PEPs done for Pegasus 2.6 and all subsequent versions. Therefore, a search of |
the reasons for those changes. Bugs reports are filed not only for |
the Open Pegasus bugzilla base for bugs with the tag for a particular version |
bugs and their corresponding fixes but also as part of the process of |
(ex. |
committing new code representing the work on PEPs done for OpenPegasus 2.6 |
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED"> |
and all subsequent versions. Therefore, a search of the OpenPegasus |
2.6.0_APPROVED</a>, |
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"> | <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED"> |
2.6.1_APPROVED</a>, |
2.6.1_APPROVED</a>, <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>, |
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>) will yield all changes to |
etc) will yield all changes to the Pegasus CVS tree for that OpenPegasus |
the Pegasus CVS tree for that Pegasus release.</p> |
release.<br> |
|
<br> |
<p> |
- Changes for this release (bugs Tagged |
- Changes for Pegasus 2.7.0 release (bugs Tagged |
2.14.0_APPROVED). The link is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.13.0_APPROVED"> |
2.7.0_APPROVED) |
Pegasus 2.13.0_APPROVED bug list.</a><br> |
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">Pegasus 2.7.0_APPROVED bug list</a></p> |
<h2><a name="Pegasus Release Control and Version Definition Documentation">Release |
|
Control |
<h2><a |
and Version Definition Documentation</a></h2> |
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 |
<p>The Pegasus project is controlled largely through a set of documents |
mechanism for new and modified Pegasus functionality and for the |
(PEPs) that serve both as the definition and review mechanism for new and |
definition and documentation of releases.<br> |
modified Pegasus functionality and for the definition and documentation |
<br> |
of releases. </p> |
The following documentation defines the characteristics of this Pegasus |
|
release. The documents are available in the OpenPegasus CVS |
<p>Specifically the following PEPs define the characteristics of this |
repository. <br> |
Pegasus release. These PEPs are available at |
<ul> |
<a href="http://www.openpegasus.org/pp/protected/documents.tpl?CALLER=index.tpl&gdc_docage=0&S=gdc_title&R=desc" style="color: blue; text-decoration: underline; text-underline: single"> |
<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 |
OpenPegasus Approved PEPs.</a></p> |
2.13.x |
|
Release Status</a>) - <span style="font-weight: normal;">A |
<b> |
section in the Pegasus wiki is used throughout the development of |
|
this version as the control point for functionality that will go |
<ol> |
into the release and points to all of the PEPs that represent the |
|
Pegasus functionality changes for this version of Pegasus</span>. </b></li> |
<li> |
<b> </b><span style="font-weight: bold;"></span><b>OpenPegasus |
PEP 296 - OpenPegasus Release Definition - </b>This PEP is used |
Build and Configuration Options for Selected Platforms - <span style="font-weight: normal;">In previous versions of Pegasus this |
throughout the development of this version as the control point for |
information was released as a Pegasus PEP. Starting with |
functionality that will go into the release and points to all of the PEPs that |
Pegasus 2.9.0 the information is located in the OpenPegasus CVS |
represent the Pegasus functionality changes for this version of Pegasus.</li> |
repository as <big style="font-weight: bold;"> <span style="font-family: monospace;">pegasus/doc/BuildAndReleaseOptions.html</span></big>.</span></b><b> |
|
</b> |
<b> |
<li><b> OpenPegasus External Interfaces -<span style="font-weight: normal;">The |
|
list of the OpenPegasus interfaces that are considered external |
<li> |
and therefore "frozen". Unless an exception is explicitly approved |
<a href="http://www.openpegasus.org/pp/uploads/40/14873/PEP292_RecommendedReleaseOptions.htm">PEP 292</a> - OpenPegasus Build and Configuration |
by the Steering Committee all subsequent releases of Pegasus MUST |
Options for Selected |
continue to support these interfaces. Interfaces not explicitly |
Platforms</li> |
listed in this document, should be considered as internal and |
|
subject to change.In previous Pegasus releases this information |
<li> |
was available as a separate PEP. Starting with Pegasus 2.9.0 this |
<a href="http://www.openpegasus.org/pp/uploads/40/14874/PEP293_ExternalInterface2.7.htm">PEP 293</a> - OpenPegasus 2.7 External Interfaces - </b>Lists the public |
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> |
interfaces for clients and providers that are considered external and |
<b> </b> |
therefore "frozen".<b><br> |
<li><b> OpenPegasus SDK Packaging Definition - <span style="font-weight: normal;">Defines |
|
the recommended set of files for inclusion in the OpenPegasus SDK. |
</li> |
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>. |
<li> |
In previous Pegasus releases this document was made available as s |
<a href="http://www.openpegasus.org/pp/uploads/40/14875/PEP294_SDKFile2.7.0.htm">PEP 294</a> - OpenPegasus SDK Packaging Definition - </b>Defines the |
separate Pegasus PEP document rather than in the CVS repository.</span> |
recommended set of files for inclusion in the OpenPegasus SDK</li> |
</b></li> <b> </b> <b> </b> |
|
<li><b> Pegasus Runtime Packaging Definition - <span style="font-weight: normal;">Defines |
<b> |
the recommended set of files for inclusion in this OpenPegasus |
|
release. Starting with Pegasus release 2.11.0, this idocument |
<li> |
contained in the CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/RuntimePackaging.html</samp></big>. |
<a href="http://www.openpegasus.org/pp/uploads/40/14877/PEP295_RuntimePackaging2.7.0.htm">PEP 295</a> - Pegasus Runtime Packaging Definition - </b>Defines the |
In previous releases this was made available as a seperate Pegasus |
recommended set of files for inclusion in this OpenPegasus release.</li> |
PEP document rather than in the CVS repository. </span> </b></li> |
|
<b> </b> <b> </b> |
<b> |
<li><b>Pegasus Release Notes - <span style="font-weight: normal;"> |
|
</span>PEP 368 - <span style="font-weight: normal;"> (This document |
<li>PEP 306 - Pegasus Release Notes (This document located in the |
is located in the approved PEP repository and the OpenPegasus |
approved PEP |
source tree root directory </span></b><span style="font-weight: normal;">(<big><span style="font-family: monospace;">pegasus/ReleaseNotes.htm</span></big>)</span></li> |
repository and the OpenPegasus source tree root directory) <br> |
<b> </b> |
|
</ul> |
</li> |
<h2><b><a name="General Documentation">General OpenPegasus Documentation</a></b></h2> |
|
<br> |
</ol> |
The following documentation is available for the this Pegasus release:<br> |
|
|
<h2><a name="General Documentation">General Documentation</a></h2> |
|
<p>The following documentation is available for the this Pegasus |
|
release:</p> |
|
<ul style="margin-top: 0in;" type="disc"> | <ul style="margin-top: 0in;" type="disc"> |
<li class="MsoNormal" style="color: black;"><b>Utilities</b> - </b>A |
<b> </b> |
combination of help generally available with the --help option for each |
<li class="MsoNormal" style="color: black;"><b><b>Utilities</b> - </b>A |
command and HTML documentation for most of the tools.<o:p></o:p></li> |
combination of help generally available with the --help option for |
|
each command and HTML documentation for most of the tools.<o:p></o:p> |
<b> |
<b> </b> </li> |
|
<li class="MsoNormal" style="color: black;"><b><b>API and usage |
<li class="MsoNormal" style="color: black;"><b>API and usage |
documentation</b> - </b>See the header files and the HTML |
documentation</b> - </b>See the header files and the HTML API |
API documentation that is on the web site. The best API usage |
documentation that is on the web site. The best API usage documentation |
documentation is the existing utilities and test programs and the |
is the existing utilities and test programs and the examples in the API |
examples in the API documentation. In particular the |
documentation. In particular the Common/tests unit tests contain |
Common/tests unit tests contain extensive examples of the use of the |
extensive examples of the use of the Common APIs.</li> |
Common APIs. <b> </b> </li> |
|
<li class="MsoNormal" style="color: black;"><b><b>Building and Debugging |
<b> |
Providers </b>- </b>Readme.html in the Pegasus source tree Root |
|
Directory, API documentation, and documentation from the Pegasus |
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
Technical Workshop which is available on the Pegasus web site. <b> </b> |
Providers </b>- </b>Readme.html in the Pegasus source tree Root Directory, API |
</li> |
documentation, and documentation from the Pegasus Technical Workshop |
<li class="MsoNormal" style="color: black;"><b><b>Building and Debugging |
which is available on the Pegasus web site.</li> |
Clients</b> -</b>API documentation and the documentation on the |
|
Pegasus Technical Workshop which is available on the Pegasus web site. |
<b> |
<b> </b> </li> |
|
<li class="MsoNormal" style="color: black;"><b><b>PEPs</b> -</b>The |
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
|
Clients</b> - </b>API documentation and the documentation on the Pegasus |
|
Technical Workshop which is available on the Pegasus web site.</li> |
|
|
|
<b> |
|
|
|
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - </b>The |
|
features of Pegasus that have been installed in this and the previous | features of Pegasus that have been installed in this and the previous |
few versions are defined by Pegasus PEPs that are available on the | few versions are defined by Pegasus PEPs that are available on the |
OpenPegasus web site. While these are the original design | OpenPegasus web site. While these are the original design |
documents largely and use in the process of defining and approving the | documents largely and use in the process of defining and approving the |
overall characteristics of new functionality, they serve as a guide to | overall characteristics of new functionality, they serve as a guide to |
the design and implementation of these features.</li> | the design and implementation of these features.</li> |
|
<li class="MsoNormal" style="color: black;"><span style="font-weight: bold;">OpenPegasus |
|
WIKI</span> - This WIKI is maintained both for the use of the |
|
development team and as a user information resource. The wiki |
|
can be accessed at <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start</a></li> |
</ul> | </ul> |
|
<hr>Licensed to The Open Group (TOG) under one or more contributor license |
<b> |
agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this |
|
work for additional information regarding copyright ownership. Each |
|
contributor licenses this file to you under the OpenPegasus Open Source |
<p class="MsoNormal" style="margin-left: 0.5in;"><span |
License; you may not use this file except in compliance with the License. |
style="color: black;"> <o:p></o:p></span></p> |
<p>Permission is hereby granted, free of charge, to any person obtaining a |
<div class="MsoNormal" style="text-align: center;" align="center"><span |
copy of this software and associated documentation files (the |
style="color: black;"> |
"Software"), to deal in the Software without restriction, including |
<hr align="center" color="#009900" noshade="noshade" size="2" |
without limitation the rights to use, copy, modify, merge, publish, |
width="100%"> |
distribute, sublicense, and/or sell copies of the Software, and to |
<p style="text-align: left;"><i><font size="2">Copyright (c) 2007 EMC |
permit persons to whom the Software is furnished to do so, subject to |
Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The |
the following conditions:</p> |
Open Group; VERITAS Software Corporation; Intel Corp.</font><br> |
<p>The above copyright notice and this permission notice shall be included |
<br> |
in all copies or substantial portions of the Software.</p> |
<font size="1">Permission is hereby granted, free of charge, to any |
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS |
person obtaining a copy of this software and associated |
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF |
documentation files (the "Software"), to deal in the Software without |
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. |
restriction, including without limitation the rights to use, copy, |
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY |
modify, merge, publish, distribute, sublicense, and/or sell copies of |
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, |
the Software, and to permit persons to whom the Software is furnished |
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE |
to do so, subject to the following conditions:</font><br> |
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p> |
<font size="2"><br> |
|
</font><font size="1">THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION |
|
NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE |
|
SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF |
|
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE |
|
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND |
|
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE |
|
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION |
|
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION |
|
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</font></i></p> |
|
</span></div> |
|
<p> </p> |
|
</div> | </div> |
</body> |
|
</html> |
</body></html> |