version 1.6.12.2, 2006/07/12 19:53:48
|
version 1.19.2.1, 2013/03/18 14:15:54
|
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
<html xmlns:v="urn:schemas-microsoft-com:vml"><head> |
<html xmlns:v="urn:schemas-microsoft-com:vml"> |
|
<head> |
|
<meta content="text/html; charset=ISO-8859-1" |
|
http-equiv="Content-Type"> |
<style> | <style> |
st1\:*{behavior:url(#ieooui) } | st1\:*{behavior:url(#ieooui) } |
</style> | </style> |
|
|
font-size:10.0pt; | font-size:10.0pt; |
font-family:"Times New Roman"} | font-family:"Times New Roman"} |
</style> | </style> |
<link rel="Edit-Time-Data" href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso"><title>PEP</title> |
<link rel="Edit-Time-Data" |
|
href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso"> |
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype> |
<title>PEP</title> |
<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> |
</head> |
<o:DocumentProperties> |
<body lang="EN-US" link="blue" vlink="blue"> |
<o:Author>IBM_User</o:Author> |
<o:smarttagtype |
<o:LastAuthor> </o:LastAuthor> |
namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
<o:Revision>4</o:Revision> |
name="City"></o:smarttagtype> <o:smarttagtype |
<o:TotalTime>211</o:TotalTime> |
namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
<o:Created>2004-04-05T14:13:00Z</o:Created> |
name="place"></o:smarttagtype><o:smarttagtype |
<o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> |
namespaceuri="urn:schemas-microsoft-com:office:smarttags" |
<o:Pages>1</o:Pages> |
name="date"></o:smarttagtype><!--[if gte mso 9]><xml> |
<o:Words>5026</o:Words> |
<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> |
<o:Characters>28651</o:Characters> |
<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:Company>IBM</o:Company> |
<div class="Section1"> |
<o:Lines>238</o:Lines> |
<div class="MsoNormal" style="text-align: center;" align="center"><span |
<o:Paragraphs>67</o:Paragraphs> |
style="color: black;"> |
<o:CharactersWithSpaces>33610</o:CharactersWithSpaces> |
<hr align="center" color="#009900" noshade="noshade" size="2" |
<o:Version>10.4219</o:Version> |
width="100%"></span></div> |
</o:DocumentProperties> |
<p class="MsoNormal" style="margin-bottom: 12pt; text-align: |
</xml><![endif]--><!--[if gte mso 9]><xml> |
center;" align="center"><b><span style="font-size: 13.5pt; |
<w:WordDocument> |
color: black;">OpenPegasus Enhancement Proposal (PEP)<o:p></o:p></span></b></p> |
<w:SpellingState>Clean</w:SpellingState> |
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span |
<w:GrammarState>Clean</w:GrammarState> |
style="color: black;"> <br> |
<w:Compatibility> |
<b>PEP #:</b> 364<br> |
<w:ApplyBreakingRules/> |
</span></p> |
</w:Compatibility> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release |
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> |
|
</w:WordDocument> |
|
</xml><![endif]--> |
|
|
|
|
|
|
|
|
|
|
|
| |
| |
| |
<script language="javascript" src="ReleaseNotes251_files/js.js"></script> |
Notes for OpenPegasus version 2.12.1</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 10 |
|
September 2012<br> |
|
</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Karl |
| |
<script language="javascript" src="ReleaseNotes251_files/js"></script> |
|
| |
<script language="javascript" src="ReleaseNotes251_files/js_002.htm"></script> |
|
| |
<script language="javascript" src="ReleaseNotes251_files/js.htm"></script></head><body lang="EN-US" link="blue" vlink="blue"> |
Schopmeyer, Marek Szermutzky<br> |
<div class="Section1"> |
|
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
|
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
|
<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;" align="center"><b><span style="font-size: 13.5pt; color: black;">Pegasus |
|
Enhancement Proposal (PEP)<o:p></o:p></span></b></p> |
|
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span style="color: black;"><br> |
|
<br> |
|
</span></p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release |
|
Notes for OpenPegasus 2.5.1 and Subsequent 2.5 minor releases</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version: </b>1.7</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> <st1:date year="2004" day="23" month="3">1 March 2006</st1:date></p> |
|
<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 |
<table class="MsoNormalTable" style="width: 100%;" border="1" cellpadding="0" cellspacing="1" width="100%"> |
History:</b></p> |
|
<table class="MsoNormalTable" style="width: 100%;" id="table1" |
|
border="1" cellpadding="0" cellspacing="1" height="155" |
|
width="100%"> |
<tbody> | <tbody> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"> |
<td style="padding: 0.75pt; background: rgb(202, 230, 202) |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
none repeat scroll 0% 50%; -moz-background-clip: initial; |
|
-moz-background-origin: initial; |
|
-moz-background-inline-policy: initial;" height="27"> |
|
<p class="MsoNormal" style="text-align: center;" |
|
align="center"><b><span style="font-family: Arial; |
|
color: black;"><o:p> </o:p></span></b></p> |
|
</td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) |
|
none repeat scroll 0% 50%; -moz-background-clip: initial; |
|
-moz-background-origin: initial; |
|
-moz-background-inline-policy: initial;" height="27"> |
|
<p class="MsoNormal" style="text-align: center;" |
|
align="center"><b><span style="font-family: Arial; |
|
color: black;"><o:p> </o:p></span></b></p> |
|
</td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) |
|
none repeat scroll 0% 50%; -moz-background-clip: initial; |
|
-moz-background-origin: initial; |
|
-moz-background-inline-policy: initial;" height="27"> |
|
<p class="MsoNormal" style="text-align: center;" |
|
align="center"><b><span style="font-family: Arial; |
|
color: black;"><o:p> </o:p></span></b></p> |
|
</td> |
|
<td style="padding: 0.75pt; background: rgb(202, 230, 202) |
|
none repeat scroll 0% 50%; -moz-background-clip: initial; |
|
-moz-background-origin: initial; |
|
-moz-background-inline-policy: initial;" height="27"> |
|
<p class="MsoNormal" style="text-align: center;" |
|
align="center"><b><span style="font-family: Arial; |
|
color: black;"><o:p> </o:p></span></b></p> |
</td> | </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;"> |
</tr> |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
<tr style=""> |
|
<td style="padding: 0.75pt;" height="22"> |
|
<p class="MsoNormal" style="text-align: center;" |
|
align="center"><span style="font-family: Arial; color: |
|
black;"><font size="2"> 1.0</font><o:p></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt;" align="left" height="22"> |
|
<p class="MsoNormal" style="text-align: center;" |
|
align="center"> <font size="2"><span |
|
style="font-family: Arial;">10 September 2012<br> |
|
</span></font></p> |
|
</td> |
|
<td style="padding: 0.75pt;" align="left" height="22"> |
|
<p class="MsoNormal" style="text-align: center;" |
|
align="center"> <span style="font-family: Arial;"><font |
|
size="2">Karl Schopmeyer</font></span></p> |
|
</td> |
|
<td style="padding: 0.75pt;" height="22"> |
|
<p class="MsoNormal"><span style="font-family: Arial; |
|
color: black;"><font size="2">Initial Submission <span |
|
style="color: red;"></span></font><o:p><font |
|
size="2"> </font></o:p></span></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;"> |
</tr> |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
<tr> |
|
<td style="padding: 0.75pt;" align="center" height="21"> 1.01</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">10 |
|
September 2012 <br> |
|
</td> |
|
<td style="padding: 0.75pt;" align="center" height="21">Karl |
|
Schopmeyer <br> |
</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;"> |
<td style="padding: 0.75pt;" height="21"> Minor fixes |
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
and complete links to PEPs<br> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" align="center" height="21"> 1.1</td> |
<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 style="padding: 0.75pt;" align="center" height="21">11 |
|
September 2012 <br> |
</td> | </td> |
<td style="padding: 0.75pt;" align="left"> |
<td style="padding: 0.75pt;" align="center" height="21">Karl |
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><o:p><font size="2"> 1 March |
Schopmeyer <br> |
2006</font></o:p></span></p> |
|
</td> |
|
<td style="padding: 0.75pt;" align="left"> |
|
<p class="MsoNormal" style="text-align: center;" align="center"> |
|
<span style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p> |
|
</td> | </td> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" height="21"> Incorporate |
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial |
all comments from first review<br> |
Submission</font><o:p><font size="2"> |
|
</font></o:p></span></p> |
|
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.1</font></td> |
<td style="padding: 0.75pt;" align="center" height="21"> 1.2</td> |
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">2 March 2006</font></td> |
<td style="padding: 0.75pt;" align="center" height="21">18 |
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">Karl Schopmeyer</font></td> |
September 2012 <br> |
<td style="padding: 0.75pt;"><font face="Arial" size="2">Fix editorial errors</font></td> |
</td> |
</tr> |
<td style="padding: 0.75pt;" align="center" height="21">Karl |
<tr style=""> |
Schopmeyer <br> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.2</font></td> |
</td> |
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">20 March 2006</font></td> |
<td style="padding: 0.75pt;" height="21"> Fix comments |
<td style="padding: 0.75pt;" align="center"><font face="Arial" size="2">Karl Schopmeyer</font></td> |
on bug 8830 (compatibility considerations) and bug |
<td style="padding: 0.75pt;"><font face="Arial" size="2">Incorporate comments from |
9172(repupgrade)<br> |
Review week of 12 March 2006</font></td> |
</td> |
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.3</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">22 March |
|
2006</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
|
Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial">Incorporate comments form |
|
Review 21 March 06 and bring into line with Feature status page</font></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.4</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">28 March |
|
2006</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
|
Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial">Remove all statements |
|
concerning status and point to the Feature Status Page.</font></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.5</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">28 March |
|
2006</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
|
Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial">Remove references to |
|
status "experimental" for certain features</font></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.6</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">28 March |
|
2006</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
|
Schopmeyer</font></td> |
|
<td style="padding: 0.75pt;"><font face="Arial">Typos - Approved by |
|
architecture group</font></td> |
|
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">1.7</font></td> |
<td style="padding: 0.75pt;" align="center" height="23"> |
<td style="padding: 0.75pt;" align="center"><font face="Arial">12 July |
|
2006</font></td> |
|
<td style="padding: 0.75pt;" align="center"><font face="Arial">Karl |
1.3<br> |
Schopmeyer</font></td> |
</td> |
<td style="padding: 0.75pt;"><font face="Arial">Update to reflect Pegasus |
<td style="padding: 0.75pt;" align="center" height="23">14 |
2.5.2 release</font></td> |
March 2013 <br> |
|
</td> |
|
<td style="padding: 0.75pt;" align="center" height="23">Marek |
|
|
|
|
|
Szermutzky <br> |
|
</td> |
|
<td style="padding: 0.75pt;" height="23">Update for 2.12.1 |
|
Release<br> |
|
</td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<p><o:p> </o:p></p> |
<div class="MsoNormal" style="text-align: center;" align="center"> |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
<span style="color: black;"> |
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
<hr align="center" color="#009900" noshade="noshade" size="2" |
<p><b>Abstract:</b> This document defines the release notes for the 2.5.1 |
width="100%"></span></div> |
and subsequent 2.5 minor releases of the Pegasus CIM Server. <span class="norm1"><span style="font-size: 9pt;"><a href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35" target="_self"><br> |
<p><b>Abstract:</b> This document defines the release notes for |
</a></span></span></p> |
the 2.12.1 release of the OpenPegasus CIM Server. The purpose of |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
this PEP is to summarize the characteristics of this release, |
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"></span></div> |
point to other documentation that defines the release in more |
<h2 style="margin-bottom: 1px;"><b><o:p><font size="4"> Contents<br> |
detail, and provide additional information about this release |
</font></o:p></b></h2> |
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> | <ol> |
<li><a href="#Availability_of_this_Release_">Availability of this Release</a></li> |
<li><a href="#Availability_of_this_Release_">Availability of |
<li><a href="#Functionality_of_This_Release">Functionality of |
this Release</a></li> |
This Release</a></li> |
<li><a href="#Functionality_of_This_Release">OpenPegasus |
<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship |
Functionality of This Release</a></li> |
to CIM/WBEM Standards</a></li> |
<li><a href="#Compatibility_Considerations_">Compatibility |
<li><a href="#Supported%20Platforms">Supported |
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> | Platforms</a></li> |
<li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance | <li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance |
|
|
|
|
|
|
with DMTF Specifications</a></li> | with DMTF Specifications</a></li> |
<li><a href="#Changes%20in%20This%20Release">Changes |
<li><a href="#PEGASUS%20Bugs">OpenPegasus Bugs</a></li> |
in This Release</a></li> |
<li> <a |
<li><a href="#PEGASUS%20Bugs">PEGASUS |
href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus |
Bugs</a></li> |
Release |
<li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">Pegasus |
|
Release Control and Version Definition Documentation</a></li> |
|
<li><a href="#General%20Documentation">General |
|
Documentation</a></li> |
Control and Version Definition Documentation</a></li> |
|
<li><a href="#General%20Documentation">General Documentation</a></li> |
</ol> | </ol> |
<h2><span style="color: black;">Availability |
<h2><span style="color: black;">Availability of this Release</span></h2> |
of this Release</span></h2> |
<p><span style="font-weight: bold;">NOTE:</span> This document |
|
defines the OpenPegasus 2.12.0 minor version release with |
|
comments added to define the 2.12.1 revision to that minor |
|
release. OpenPegasus 2.12.1 is a bug fix revision to |
|
OpenPegasus 2.12.0. The complete list of changes (total of 12 |
|
bugs fixed) is defined in OpenPegasus bugzilla with the <a |
|
href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.1_APPROVED">2.12.1_APPROVED |
|
|
|
|
|
bugs</a> query. We recommend that all users of 2.12.0 |
|
review this list. OpenPegasus tries to execute only bug fixes |
|
for revision releases and not include enhancements. The |
|
OpenPegasus team recommends that users of Pegasus 2.12.0 update |
|
to Pegasus 2.12.1. Note that in OpenPegasus ALL changes |
|
including enhancements are defined as bugs and committed only |
|
when the APPROVED keyword is set so that the list in the query |
|
above defines ALL changes between 2.11.0 and 2.11.1.</p> |
<p>This release is available in a number of forms including:</p> | <p>This release is available in a number of forms including:</p> |
<ul> | <ul> |
<li>Source release in both ZIP and TAR formats. These can be |
<li><b>Source release</b> in both ZIP (and ZIP EXE) and TAR |
downloaded from the <span class="SpellE">OpenPegasus</span> Web |
formats. These can be downloaded from the <span |
site at <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a></li> |
class="SpellE">OpenPegasus</span> Web site at <a |
<li>OpenPegasus 2.5.x binaries are available for Red Hat Enterprise |
href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li> |
Linux 3.0 and 4.2 and SUSE LINUX Enterprise Server 9.0. A Source RPM is |
<li><b>OpenPegasus source RPMs</b> on the OpenPegasus web |
also available that can be used to build binaries for most |
site.. A source RPM is available on the OpenPegasus web |
LSB-compliant RPM-based Linux distributions and versions.</li> |
site that can be used to build binaries for most LSB-compliant |
<li>The Pegasus CVS. The CVS tags representing this release and |
RPM-based Linux distributions and versions.</li> |
subsequent snapshots that are made available in the Pegasus CVS are |
<li><b>The OpenPegasus CVS repository</b>. The CVS tags |
defined on the OpenPegasus CVS repository web page (see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus |
representing this release and subsequent snapshots that are |
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 |
made available in the Pegasus CVS are defined on the |
snapshots page</a>.</li> |
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> | </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 |
<p>The instructions for acquiring the released code are on the <a |
WEB site</a>. |
href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus |
Installation instructions are part of the README in the root of the |
WEB |
Pegasus source |
|
tree.</p></div> |
|
<div class="Section1"> |
|
<h2><span style="color: black;">Functionality of This Release</span></h2> |
site</a>. Installation instructions are part of the README in |
Pegasus overall status by release is defined by a |
the root of the Pegasus source tree.</p> |
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a> |
|
that is available on the OpenPegasus web site . That |
|
web page shows the Pegasus users and developers |
|
the status of the various features found in Pegasus using a simple color coded |
|
key (white, red, yellow, green). Pegasus 2.5.1 is a minor release, extending Pegasus 2.5.0 in selected |
|
areas primarily for bug fixes. However, there were some signification |
|
changes in the feature status for selected functions in 2.5.1 (moving selected |
|
functions closer to production-capable status). Pegasus 2.5.2 is a minor release |
|
providing changes that have been defined through pegasus bugs.<p>The following paragraphs list the functionality in this release. In many cases these features and interfaces |
|
are conditionally compiled with special environment variables. <span style="color: rgb(51, 102, 255);"><span style="text-decoration: underline;"> |
|
<a style="color: blue; text-decoration: underline;" href="http://www.openpegasus.org/pp/uploads/40/10083/PEP237_RecommendedReleaseOptions.htm">PEP 237</a></span><a href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502" style="color: blue; text-decoration: underline;"> </a></span> |
|
provides more detailed information on how to enable |
|
functionality that is conditionally compiled in this release.</p> |
|
<p><font color="#ff0000"><b>NOTE: </b>For current information and history on the status of each feature, |
|
please access the</font> |
|
<a href="http://www.openpegasus.org/page.tpl?ggid=799" style="color: blue; text-decoration: underline;"> |
|
OpenPegasus Feature Status WEB Page</a>. <font color="#ff0000">Please see |
|
the Feature status page for the quality/status of each feature because not all |
|
of the features listed below are production ready.</font></p> |
|
<h3><b>CIM Server Functionality</b></h3> |
|
<blockquote> |
|
<h4><b>CIM Operations over HTTP support</b></h4> |
|
<ol> |
|
<li>Class Operations (<span class="SpellE">getClass</span>, <span class="SpellE">deleteClass</span>, <span class="SpellE">modifyClass</span>, |
|
<span class="SpellE">enumerateClass</span>, <span class="SpellE">enumerateClassNames</span>)</li> |
|
<li>Qualifier Operations (getQualifier, setQualifier, |
|
deleteQualifier) </li> |
|
<li>Instance Operations (<span class="SpellE">getInstance</span>, <span class="SpellE">deleteInstance</span>, <span class="SpellE">modifyInstance</span>, |
|
<span class="SpellE">enumerateInstance</span>, <span class="SpellE">enumerateInstanceNames</span>, <span class="SpellE">getProperty</span>, |
|
<span class="SpellE">setProperty</span>)</li> |
|
<li>Association Operations (references, <span class="SpellE">referencenames</span>, |
|
<span class="SpellE">associators</span>, <span class="SpellE">associatornames)</span></li> |
|
<li>Methods Operations (invokeMethod)</li> |
|
<li>Query operation - Support for ExecQuery was added in 2.4 with |
|
WQL as query language and is defined in PEP 119. This feature is |
|
considered at alpha quality because it has only been contributor |
|
tested. Additional tests have been added in 2.5 for ExecQuery. Pegasus |
|
today does not support the ExecuteQuery operation defined as the Query |
|
operation for CQL.<br> |
|
</li> |
|
</ol> |
|
</blockquote> |
|
</div> | </div> |
<blockquote> |
<div class="Section1"> |
<h4><b>Indication Processing</b></h4> |
<h2><span style="color: black;">OpenPegasus Functionality in 2.12 |
<ol> |
Release</span></h2> |
<li>Process indications - Process indications are operational in |
OpenPegasus overall status by release is defined by a <a |
the |
href="http://www.openpegasus.org/page.tpl?ggid=799">Feature |
Server. This includes support |
Status WEB Page</a> that is available on the OpenPegasus web |
for subscriptions, filters, and indication handlers, the provider API |
site . That web page shows the Pegasus users and developers |
for |
the status of the various features found in OpenPegasus using a |
indications and the CIMXML indication handler.</li> |
simple color coded key (white, red, yellow, green) and a |
<li>Lifecycle indications - With the support for embedded objects, |
description of each feature. |
lifecycle indications (ie. those |
<p>OpenPegasus 2.12.1 is a Revision release.<br> |
classes of indications derived from CIM_ClassIndication and |
|
CIM_InstIndication) can now be created. Pegasus 2.5 provides some |
|
enablement for the generation of lifecycle indications. For more |
|
details, refer to |
|
<src/Unsupported/LifecycleIndicationProvider/readme.LifecycleIndications.htm>.</li> |
|
</ol> |
|
<h4><b>Query Language</b></h4> |
|
<p>Pegasus includes the WQL query language which is implemented and |
|
used for filters and in version 2.4 for execQuery. <br> |
|
</p> | </p> |
<p>CQL Stage 1 has been added for Pegasus 2.5. PEPs 138, 193, 205 |
<p>NOTE: OpenPegasus releases are categorized as follows:</p> |
combine to describe the CQL functionality supported.</p> |
<ul> |
<h4>Object Normalization</h4> |
<li>First number of version changes (ex. 2.x.x to 3.0.0) - |
The Object Normalizer is an entity introduced in Pegasus 2.4 that |
Major release includes major functionality change and |
ensures |
incompatible behavior changes and/or incompatible public API |
objects delivered from providers are complete and accurate. Two major |
changes, <br> |
issues were identified with the initial implementation: 1) the Object |
</li> |
Normalizer droped instances it considered bad, and 2) the Object |
<li>Second number changes (ex 2.11.0 2.12.0) - Minor |
Normalizer code slowed performance. These issues are now addressed by |
Release and includes new functionality but maintains behavior |
moving the Object Normalizer from the Dispatcher to the Response |
and public API compatibility, <br> |
Handler (or equivalent) and optimizing the existing implementation. The |
|
move allows errors to be reported to the provider at the point of |
|
delivery and ensures that only a single copy is made to preserve the |
|
CIMOM/provider boundary.<br> |
|
<h4>Embedded Object Support</h4> |
|
Pegasus 2.5 provides embedded object support. The proposed solution |
|
is restricted to the following:<ul> |
|
<li>The only representation for embedded objects supported by this |
|
PEP is CIM-XML (i.e. id does not support MOF encoded objects). </li> |
|
<li>CIMObject is implemented as a new CIMValue type. This type will be used |
|
internally to represent embedded objects. When externalized (via |
|
CIM-XML) these objects will be converted to strings representing valid |
|
INSTANCE or CLASS elements, in accordance with the CIM Infrastructure |
|
Specification. Embedded instances will also carry the |
|
EmbeddedObject attribute with |
|
the value "object", as specified by CR Interop-00217.001. |
|
</li> | </li> |
|
<li>3rd number changes (2.12.0 to 2.12.1) - Revision(also called |
|
point release) release and only includes bug fixes.</li> |
</ul> | </ul> |
<h3>Pegasus Repositories<br> |
<br> |
</h3> |
The major areas of development including both enhancements and bug |
<p class="MsoNormal"> </p> |
fixes for the minor release 2.12 were as follows. Note that the |
</blockquote> |
bugs listed represent only those features incorporated in bugs |
<div class="Section1"> |
without PEPS that are considered enhancements, not all bugs |
<blockquote> |
incorporated in the release. For more information access the |
<h4><b>Schema Repository</b></h4> |
PEP/BUG for each change defined below: |
<p style="margin-top: 0pt; margin-bottom: 0pt;">By default, Pegasus uses an XML-based |
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> <font |
schema repository. A binary encoding option is also available for the repository.<span style="font-family: "times new roman";"><br> |
style="font-weight: bold;" size="4"> Table |
</span></p> |
of Major Changes for this Release</font></p> |
<div style="margin-left: 40px;"> |
<table style="font-family: Arial;" bordercolordark="#666666" |
<span style="color: rgb(51, 102, 255);">Note: Users may experience an incompatibility moving a binary repository from |
bordercolorlight="#CCCCCC" border="1" cellspacing="1" |
Pegasus 2.4 to 2.5. In Pegasus 2.5, measures have been taken to improve |
width="82%"> |
the ability to maintain compatibility with subsequent releases. (See bugzilla 3642 for details.)</span></div> |
<tbody> |
<p>Further information on the use of the binary repository is in the |
<tr align="center"> |
readme.binaryrepository file in the Pegasus source root directory.</p> |
<th bgcolor="#00ffff">PEP/BUG #</th> |
<h4><b>Instance Repository</b></h4> |
<th bgcolor="#00ffff">Description of Change</th> |
<p><font style="color: rgb(0, 0, 0);">The |
<th bgcolor="#00ffff" width="128">Posted PEP<br> |
Pegasus schema repository may also be configured to hold instance |
Version</th> |
data. Although instances may be place in the |
</tr> |
repository |
<tr> |
it was not designed as a |
<td align="left">PEP 360</td> |
high volume data store</font><span style="color: rgb(0, 0, 0);">.</span></p> |
<td>Provider Lifecycle Indications<br> |
<h4><b><b>Compressed Repository Feature</b></b></h4> |
</td> |
<span class="norm"></span><font style="color: rgb(0, 0, 0);" color="RED">A compressed repository |
<td style="text-align: center;"><a |
feature has been added for |
href="https://collaboration.opengroup.org/pegasus/pp/documents/25003/PEP360_PLI_Ver1_2.html">Ver |
pegasus 2.5 that compresses the repository written to disk. This allows |
|
the |
|
repository to be as much as 50% smaller on disk. It uses an external |
|
compression library (zlib) and has been tested with zlib 1.2.2. This |
1.2</a><br> |
feature is |
</td> |
documented in PEP 214 and also in a Readme |
</tr> |
(readme.compressed_repository). Note |
<tr align="center"> |
that the tests for this feature are in the test suite but not |
<td align="left" width="7%">PEP 361</td> |
activated for |
<td align="left" width="75%">cimcli support for embedded |
automatic tests.</font><p style="margin-bottom: 0pt;">Further information on the use of the compressed |
instances<br> |
repository is in the readme.compressedrepository file in the Pegasus source |
</td> |
root directory<span style="color: rgb(51, 102, 255);">.</span></p> |
<td width="128"><a |
<h4><b>Pegasus MOF Compilers</b></h4> |
href="https://collaboration.opengroup.org/pegasus/pp/origrevdocuments/3195/PEP361_CIMCLIEmbeddedInstanceSupport.htm">Ver |
<p>Pegasus implements a MOF compiler that can operate either at the |
|
client |
|
interface to the Pegasus CIM Server (<span class="SpellE">cimmof</span>) |
|
or directly interfacing with a CIM |
1.1</a><br> |
repository (<span class="SpellE">cimmofl</span>).</p> |
</td> |
<p>The direct interface compiler is used primarily to provide an |
</tr> |
initial |
<tr> |
class/instance repository. <font color="#ff0000"><b>WARNING:</b></font> |
<td align="left" width="7%">PEP 304<br> |
The use of <span class="SpellE">cimmofl</span> |
</td> |
to manipulate instances in the repository bypasses any provider that is |
<td align="left" width="75%">Allow modification of name of |
registered to serve these instances and simply installs the |
interop namespace<br> |
instances in the |
</td> |
instance repository; this may result in 1) bad data in the repository |
<td style="text-align: center;" width="128"><a |
if there are registered providers, 2) corruption of the repository if |
href="http://www.openpegasus.org/pp/uploads/40/23237/PEP_357_-_SNMP_v3_trap_generation_in_Pegasus_.htm"></a><a |
the CIM Server is running or, 3) MOF data that is loaded but not |
href="https://collaboration.opengroup.org/pegasus/pp/documents/24686/PEP304_NamespaceRenaming.htm">Ver |
available until the server is stopped and restarted in some |
|
cases. Use of <span class="SpellE">cimmofl in general is |
|
discouraged and particularly </span> to manipulate |
|
instances served by a registered providers (ex. Provider registration). |
1.5</a><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td align="left">PEP 358<br> |
|
</td> |
|
<td>WSMan indication handling and subscription support<br> |
|
</td> |
|
<td align="center"><a |
|
href="https://collaboration.opengroup.org/pegasus/pp/documents/26240/PEP_358_-_WSMAN_Eventing_support_in_Pegasus_.htm">Ver |
|
|
|
|
|
|
|
1.1</a><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8891">Bug |
|
|
|
|
|
|
|
8891</a><br> |
|
</td> |
|
<td>Enhance cimsub to add operations to create filters, |
|
destinations and subscriptions<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" align="left" width="7%"><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=5667">Bug |
|
|
|
|
|
|
|
5667</a><br> |
|
</td> |
|
<td align="left" width="75%">Remove experimental from |
|
buildInstance and filter functions in CIMInstance class<br> |
|
</td> |
|
<td width="128"><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8952">Bug |
|
|
|
|
|
|
|
8952</a></td> |
|
<td> Support Configurable cipher suites in OpenPegasus</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8904">Bug |
|
|
|
|
|
|
|
8984</a></td> |
|
<td>Add support for indication deliver connection pooling</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9008">Bug |
|
|
|
|
|
|
|
9008</a></td> |
|
<td>Add new Indication runtime configuration variables: |
|
maxIndicaitonDeliveryRetry Attempts and |
|
minIndicationdeliveryRetryInterval</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr align="center"> |
|
<td style="text-align: center;" align="left" width="7%"><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9013">Bug |
|
|
|
|
|
|
|
9013</a><br> |
|
</td> |
|
<td align="left" width="75%"><span style="color: |
|
windowtext;"><span style=""></span></span>Enable ordered |
|
indication delivery from provider through CIMServer when |
|
PEGASUS_ENABLE_DMTF_INDICATION_PROFILE compile flag is set</td> |
|
<td width="128"> <a |
|
href="http://www.openpegasus.org/pp/uploads/40/22386/PEP_349_-_Improve_the_availability_of_the_CIMOM_by_better_isolation_from_faulty_providers.htm"></a><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="text-align: center;" align="left"> <a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8800">Bug |
|
|
|
|
|
|
|
9080 </a></td> |
|
<td> <span class="norm"></span>Guaranteed provider |
|
lifecycle indication delivery during CIMServer shutdown </td> |
|
<td style="text-align: center;"><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9112">Bug |
|
|
|
|
|
|
|
9112</a><br> |
|
</td> |
|
<td>Advertise IndicationService conformance to Indications |
|
Profile by imlementing CIM_ElementConformsToProfile when |
|
PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT defined </td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9114">Bug |
|
|
|
|
|
|
|
9114</a><br> |
|
</td> |
|
<td>Advertise DMTF Indications Profile (DSP1054) 1.1.0 |
|
conformance </td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9118">Bug |
|
|
|
|
|
|
|
9118</a><br> |
|
</td> |
|
<td>Add support for CIM_IndicationFilter.SourceNamespaces[] |
|
property<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9136">Bug |
|
|
|
|
|
|
|
9136</a></td> |
|
<td>Runtime configuration option to restrict cimserver to |
|
listen on selected network interfaces</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9155">Bug |
|
|
|
|
|
|
|
9155</a><br> |
|
</td> |
|
<td>Update to include CIM 2.31 Schema and set this as |
|
default schema<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9159">Bug |
|
|
|
|
|
|
|
9159</a></td> |
|
<td> |
|
<table style="font-family: Arial;" |
|
bordercolordark="#666666" bordercolorlight="#CCCCCC" |
|
border="1" cellspacing="1" width="82%"> |
|
<tbody> |
|
<tr> |
|
<td>Add SSL Support to Dynamic Listener<br> |
|
</td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9172">Bug |
|
|
|
|
|
|
|
9172</a><br> |
|
</td> |
|
<td>Add capability for administrator to override hostname |
|
used by providers. This adds new runtime |
|
configuration variable hostname and |
|
fullyQualifiedHostName. It is necessary to upgrade |
|
existing repositories using repupgrade utility when |
|
upgrading from OpenPegasus less than 2.12.0 and reusing an |
|
existing repository.<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9215">Bug |
|
|
|
|
|
|
|
9215</a><br> |
|
</td> |
|
<td>Add support of CQL query language to ExecQuery operation |
|
in general. When the server receives ExecQuery it |
|
executes enumerate instance for providers that do not |
|
support ExecQuery and filters result.<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9209">Bug |
|
|
|
|
|
|
|
9209 </a><br> |
|
</td> |
|
<td>Add operations for display class tree and counting |
|
instances to cimcli<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9227">Bug |
|
|
|
|
|
|
|
9227</a><br> |
|
</td> |
|
<td>Enhance cimsub for batches of subscription oriented |
|
operations<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9229">Bug |
|
|
|
|
|
|
|
9229</a><br> |
|
</td> |
|
<td><a name="comtag_197">Add gcc build support on hp-ux for |
|
the Common, Client and General libraries.</a></td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9236">Bug |
|
|
|
|
|
|
|
9236</a></td> |
|
<td>Support for clang/clang++ compiler on Linux. This |
|
version supports only X86 and X86_64 and requires clang |
|
version 3 or greater.<br> |
|
</td> |
|
<td><br> |
|
</td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
<p>The status of several components of Pegasus functionality |
|
change status 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> |
|
<h3><b>Information on Interop namespace name (root/PG_InterOp) for |
|
OpenPegasus 2.12<br> |
|
</b></h3> |
|
<p>Prior to version 2.12 OpenPegasus used an OpenPegasus internal |
|
variable to define "root/PG_InterOp" as the name for the |
|
OpenPegasus namespace with no defined way to change this |
|
variable. Note that an unsupported method involving |
|
editing one file and rebuilding OpenPegasus was defined as a |
|
workaround in the <a |
|
href="%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus |
|
|
|
|
|
|
|
wiki faq</a>s. <br> |
|
</p> |
|
<p>However, since the definition of a standard name for this |
|
namespace in DMTF and SNIA specifications ("interop" or |
|
"root/interop" with "interop" being the preferred alternative) |
|
the use of "root/PG_InterOp" has become an issue.<br> |
|
</p> |
|
<p>Effective OpenPegasus 2.12.0 a new build variable has been |
|
defined (PEGASUS_INTEROP_NAMESPACE) which allows an |
|
OpenPegasus builder to define an alternate name for the Interop |
|
namespace to either "interop" or "root/interop" (ex. |
|
PEGASUS_INTEROP_NAMESPACE = interop). Once this build |
|
variable is defined and OpenPegasus compiled, the actual name of |
|
the interop namespace is what was defined in this variable and |
|
all components of OpenPegasus use this as the interop namespace |
|
name include the complete OpenPegasus test suite. The only |
|
name for the interop namespace will be the name defined through |
|
this build variable.<br> |
|
</p> |
|
<p>However, today OpenPegasus is committed to the single namespace |
|
defined at build "(root/PG_InterOp", "interop", or |
|
"root/interop"). However, a number of OpenPegasus |
|
installations are committed to the "root/PG_InterOp" name and |
|
must maintain their repositories through updates of OpenPegasus. |
|
While we are working on this issue today (which means that a |
|
running version of OpenPegasus must accept both the and new |
|
names and not confuse clients, listeners or providers that would |
|
use either name) the OpenPegasus team did not complete that work |
|
for this release. See bug <a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9250">9250</a> |
|
for more information about possible solutions and our progress |
|
on a solution.<br> |
|
</p> |
|
<p>NOTE: If you redefine the interop namespace name with |
|
PEGASUS_INTEROP_NAMESPACE clients using the "root/PG_InterOp" |
|
namespace will not connect with the updated version of |
|
OpenPegasus. <br> |
|
</p> |
|
<h3><font color="#000000"></font></h3> |
|
<h3><font color="#000000">Information on IPv6 Support (PEP |
|
291)</font></h3> |
|
<p><b>NOTE:</b> This functionality was incorporated in OpenPegasus |
|
2.7.0 but it was felt that the information below was worth |
|
repeating in subsequent Release Notes</p> |
|
<p style="color: rgb(153, 51, 153);"><font color="#000000">IPv6 is |
|
short for "Internet Protocol Version 6". IPv6 is the "next |
|
generation" protocol designed by the IETF to replace the |
|
current version Internet Protocol, IP Version 4 ("IPv4"). IPv6 |
|
Support for OpenPegasus is documented in </font> <a |
|
href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html"> |
|
<font color="#3333ff">PEP 291</font></a><font color="#000000">.</font></p> |
|
<p>The IPv6 support in OpenPegasus is controlled by the |
|
PEGASUS_ENABLE_IPV6 build variable. The default for this |
|
variable is "true"; setting this to 'false' before building |
|
OpenPegasus will disable the IPv6 support.<br> |
|
</p> |
|
<p>The following subsections provide some information on IPv6 |
|
support for the Linux and Windows platforms. Note that in the |
|
2.6.1 release there is no automatic run-time detection of IPv6 |
|
support on a platform by OpenPegasus. If you build with |
|
PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you |
|
will get a build failure (missing header files), a run-time |
|
bind() failure, or possibly some other failure. This applies to |
|
both the CIM Server and Listener components. For more |
|
information on IPv6 support for your specific platform, refer to |
|
the documentation for that platform.<br> |
|
</p> |
|
<p>All OpenPegasus externals that support either a hostname or an |
|
IP address as input have been updated to allow an IPv6 address |
|
to be specified. If the required input is just an IP address |
|
(eg. no optional or required port number), then the IPv6 address |
|
must be specified without brackets. For example, the OpenPegasus |
|
osinfo client (which returns information about the OS running on |
|
a host system) takes separate host and port options. In this |
|
case a host with an IPv6-configured network interface would be |
|
specified as:<br> |
</p> | </p> |
<h3><b><b>Security Considerations</b></b></h3> |
<div style="margin-left: 40px; color: rgb(153, 51, 153); |
<font style="color: rgb(0, 0, 0);" color="RED">OpenPegasus 2.5 (and |
font-family: monospace;"><big><font color="#000000">osinfo -h |
prior versions) contains several mechanisms to perform authorization, but none |
3ffe:1:2:1 -p 5988</font></big></div> |
of these authorization checks are performed by default. |
<p>But the cimcli command, which takes an optional "location" |
By registering any provider which fails to do appropriate authorization |
option including an optional port number, requires the IPv6 |
checks, the consequences may include information leakage, data |
address to be delimited with brackets, for example:<br> |
corruption, or unintended elevation of privilege. Please ensure that |
</p> |
one of the following mechanisms is used to ensure appropriate access to |
<div style="margin-left: 40px; font-family: monospace;"><big>cimcli |
your systems and data:</font><p style="margin-bottom: 0pt;"> |
|
<font style="color: rgb(0, 0, 0);" color="RED">1. Only install/register providers which perform authorization |
|
appropriate for your environment.</font></p> |
ns -l [3ffe:1:2:1]</big></div> |
<div style="margin-left: 40px;"><font style="color: rgb(0, 0, 0);" color="RED">a. For providers, this may include registering to |
<p>or</p> |
'Run-as-requestor' (not available prior to Pegasus 2.5) and/or |
<div style="margin-left: 40px;"><big><span style="font-family: |
performing authorization checks within the provider.<br> |
monospace;">cimcli ns -l [3ffe:1:2:1]:5989</span></big><br> |
b. For administrators, ensure that the providers you have registered in |
|
your environment have performed sufficient authorization checks. Also, |
|
monitor announcements of security defects in those providers and follow |
|
the recommendations in those announcements as soon as possible. <br> |
|
c. For distributors of Pegasus or providers, ensure that the providers |
|
you are shipping have performed appropriate authorization checks, and |
|
relay announcements of discovered security defects to your users.</font><br> |
|
</div> | </div> |
<font style="color: rgb(0, 0, 0);" color="RED">2. Restrict users with |
|
access to Pegasus to a specific authorized user group of trusted |
|
individuals.<br> |
|
3. Namespace authorization is also available.<br> |
|
<br> | <br> |
</font><span class="norm">For administration issues please refer to |
For more information on specifying IPv6 addresses, refer to <a |
the SSL Admin Guide found in the source repository at: </span>pegasus/doc/PegasusSSLGuidelines.htm<br> |
href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP |
<h4><b>Server Security</b></h4> |
Version 6 Addressing Architecture</a> and <a |
<ol style="margin-top: 0in;" start="1" type="1"> |
href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 - |
<li class="MsoNormal" style="color: black;">Basic Authentication |
Format for Literal IPv6 Addresses in URL's</a>.<br> |
(Note that Digest based security is not implemented in Pegasus)</li> |
<h4><font color="#000000">IPv6 on Linux</font></h4> |
<li class="MsoNormal" style="color: black;">PAM authentication <o:p></o:p></li> |
<p>Modern Linux distributions already contain IPv6-ready kernels, |
<li class="MsoNormal" style="color: black;">SSL support - SSL is |
the IPv6 capability is generally compiled as a module, but it's |
implemented in Pegasus using the <span class="SpellE">OpenSSL</span> |
possible that this module is not loaded automatically on |
libraries. Pegasus does not provide the <span class="SpellE">OpenSSL</span> |
startup.</p> |
libraries but SSL can be used on any platform supported by <span class="SpellE">OpenSSL</span>. . This release of Pegasus was tested |
<p><span style="font-weight: bold;">Note: </span>you |
with multiple versions of OpenSSL versions |
shouldn't use kernel series 2.2.x, because it's not |
0.9.7 and 0.9.8. Effective with Pegasus 2.5.1 the Open SSL version |
IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x |
0.9.6 is no longer supported. See <a href="http://www.openpegasus.org/pp/uploads/40/Application%20Data/Microsoft/Word/www.openssl.org">openssl.org</a> |
is no longer improved according to definitions in latest RFCs. |
for <span class="SpellE">OpenSSL</span> release information<o:p>.</o:p></li> |
It's recommend to use series 2.6.x now.<br> |
<li class="MsoNormal" style="color: black;">SSL levels - <font style="color: rgb(0, 0, 0);">SSLv3 |
|
and TLSv1 by default. SSLv2 is |
|
disabled by default and only enabled by a compile time option</font>. |
|
See<a href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502"> |
|
PEP 237</a> for details on |
|
configuration.<br> |
|
</li> |
|
</ol> |
|
<b> </b> |
|
<h4><b>Client Security</b><span style="font-family: times new roman;"><span style="font-style: italic;"><span style="font-weight: bold;"></span></span></span></h4> |
|
<b>Certificate management |
|
and User-based certificate authentication .</b> A new control provider and CLI for certificate management tasks. It expands upon the existing SSL |
|
client verification support by providing a robust solution to managing |
|
client certificates and certificate revocation lists via standard CIM |
|
operations. It allows certificates to be associated with particular |
|
system users for enhanced authorization capabilities.<br> |
|
<span class="norm"></span><font style="color: rgb(0, 0, 0);">CN/ Host |
|
name checks are not performed as a function of SSL or client libraries |
|
and are the responsibility of the client to implement on their |
|
own. See the SSL guide found in the /pegasus/doc directory for |
|
more details on client security.</font><br> |
|
Note: <span class="norm"><font><font color="RED"><span style="color: rgb(0, 0, 0);">WBEM clients are responsible for SSL |
|
certificate verification using Pegasus and/or SSL libraries as |
|
appropriate. Consequences of not doing so include leakage of |
|
authentication credentials to unauthorized parties.</span> </font></font></span> |
|
<h4><b>Platform Management Functions</b></h4> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Configuration through |
|
the defined configuration parameters (cimconfig) and server command |
|
line options.<span class="norm"></span><font style="color: rgb(0, 0, 0);" color="RED"> NOTE: When installed |
|
as a service on Windows, setting the run-time config option |
|
enableAuthentication to true can result in improper operation of the |
|
SLP |
|
provider and other providers. In order to circumvent this defect, an |
|
Administrator should change the user that the service runs under from |
|
the Local |
|
System user to a local, privileged user (e.g. Administrator). |
|
See bugzilla 4142 for details.</font> <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">Daemon/service |
|
operation of the Pegasus CIM Server on all supported platforms<o:p> |
|
with the exception of HP OpenVMS.</o:p></li> |
|
<li class="MsoNormal" style="color: black;">Operation statistics |
|
capture using the <span class="norm"></span><font style="color: rgb(0, 0, 0);">CIM_StatisticalData </font>classes in |
|
the DMTF Interop model. This |
|
function is considered alpha quality and conditionally compiled. <br> |
|
</li> |
|
<li class="MsoNormal" style="color: black;">Multiple |
|
pluggable provider managers. Provider managers are provided for |
|
the Pegasus C++ provider interface, the CMPI C provider interface and |
|
an alpha quality Java provider interface (JMPI).</li> |
|
<li class="MsoNormal" style="color: black;">Platform Globalization |
|
- Pegasus includes support for unicode data transfers and includes a |
|
mechanism for message support in multiple languages using the open |
|
source ICU libraries (<a href="http://oss.software.ibm.com/icu/">http://oss.software.ibm.com/icu/</a>).</li> |
|
<li class="MsoNormal" style="color: black;">Out-of-process providers - See PEP 072 for more information on use of |
|
this feature </li> |
|
<li class="MsoNormal" style="color: black;">Shared class namespaces - See PEP 129 for more information on use of this feature.</li> |
|
<li class="MsoNormal" style="color: black;">Remote providers for |
|
the CMPI provider interface - See PEP 130 for more |
|
information on use of this feature.</li> |
|
</ol> |
|
<h4><b>SLP Discovery</b></h4> |
|
<p>SLP support is included but is conditionally compiled in or out on |
|
a platform basis. <a href="http://www.openpegasus.org/pp/uploads/40/8502/PEP200_RecommendedReleaseOptions.htm"> |
|
PEP 237</a> describes the environment variable (PEGASUS_ENABLE_SLP) to |
|
enable or disable this code. Effective with Pegasus 2.5.1, support has |
|
been added for the use of OpenSLP as the Service Agent (SA) in addition to the |
|
internal to the Service Agent. This is controlled through an additional |
|
environment variable (PEGASUS_HAS_OPENSLP) Once compiled, SLP |
|
support is enabled with the slp configuration parameter (slp=true). SLP |
|
support includes an SLP service agent in the Pegasus CIM sever (either the |
|
internal agent or OpenSLP) and |
|
generates SLP advertisements compatible with the DMTF slp template |
|
specification. The SLP support also includes extensions to the |
|
CIM Client libraries to execute SLP User Agent requests and analyze the |
|
results (note that these interfaces are not yet part of the Pegasus |
|
public SDK).<br> |
|
Note: Pegasus on Windows is built with SLP support on by default.</p> |
|
<h4><b>Indication Handlers</b></h4> |
|
<blockquote> |
|
<h5>System Log Indication Handler<br> |
|
</h5> |
|
<p>The SysLog Indication Handler is a new |
|
for 2.5 |
|
type of Indication Handler which allows CIM Indications to be delivered |
|
to the system syslog file. It has following features:<br> |
|
</p> | </p> |
<p>Each syslog file entry has a tag 'CIM Indication' to distinguish |
<p>To check whether your current running kernel supports IPv6, |
an entry made by Syslog Indication Handler.</p> |
take a look into your /proc filesystem. The entry |
<p>If a subscriber includes PerceivedSeverity property in the SELECT |
/proc/net/if_inet6 must exist. A short automated test looks |
list of the filter condition for the indication, the PerceivedSeverity |
like:<br> |
will be mapped to syslog error severity. Otherwise, syslog error |
|
severity 'LOG_INFO' is used.</p> |
|
<p>See |
|
<a href="http://www.openpegasus.org/pp/uploads/40/7165/PEP206-SystemLogIndicationHandler.htm" style="color: blue; text-decoration: underline;">PEP |
|
206</a> for details.</p> |
|
<h5>Email Indication Handler<br> |
|
</h5> |
|
<p>The Email Indication Handler is a new |
|
for 2.5 |
|
type of Indication Handler that allows CIM Indications to be delivered |
|
to a specified e-mail address. See |
|
<a href="http://www.openpegasus.org/pp/uploads/40/7166/PEP207-EmailIndicationHandler.htm" style="color: blue; text-decoration: underline;">PEP |
|
207</a> for details. </p> |
|
</blockquote> |
|
<h4>Pegasus Provider Interfaces</h4> |
|
<p>Pegasus is designed to support multiple Provider Managers to allow |
|
multiple provider interfaces to the CIMOM. The two default |
|
provider managers are the Pegasus C++ Interface and Common |
|
Manageability Programming Interface (CMPI) Interface.</p> |
|
<blockquote> |
|
<h5>C++ Provider Interface</h5> |
|
<p class="norm"><font face="Times New Roman" size="3">This is the original |
|
interface defined for OpenPegasus Providers. It provides an interface |
|
for both operations and indications. Many of the sample and test providers are |
|
written to this interface. This interface includes a callback into the |
|
CIMOM (CIMOMHandle).</font><br> |
|
</p> | </p> |
<h5><b style="">CMPI C interface Provider Manager<o:p></o:p></b></h5> |
<div style="margin-left: 40px; color: rgb(153, 51, 153); |
<span style="font-family: "times new roman";">Pegasus 2.5 includes |
font-family: monospace;"><big><font color="#000000">test -f |
a provider manager for the CMPI C interfaces. This C interface is the |
/proc/net/if_inet6 && echo "Running kernel is IPv6 |
result of a project by the IBM SBLIM team (see |
ready"</font></big></div> |
http://sblim.sourceforge.net) and is written to the Common |
<p>For more information on enabling IPv6 in the Linux kernel and |
Manageability Programming Interface, which is an OpenGroup standard. |
configuring network interfaces, refer to <a |
The CMPI |
href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The |
specification is available at: |
Linux Documentation Project's IPv6 HOWTO</a>.<br> |
http://www.opengroup.org/bookstore/catalog/c051.htm. This provides a |
|
standardized C level interface for creating providers that can be |
|
registered with the Pegasus CIM Server in the same manner as the |
|
current C++ providers. </span><span style="font-family: "times new roman";"><span class="norm"></span></span>The |
|
ability for CMPI providers to do user authorization is now available in |
|
Pegasus 2.5.1.<br> |
|
<span style="font-family: "times new roman";"> <br> |
|
Information on writing providers with the CMPI interface is available |
|
in the specification today (see above) and in the following documents |
|
(http://sblim.sourceforge.net/whitepaper.html and |
|
http://sblim.sourceforge.net/presentations.html) and readme.cmpi in the |
|
Pegasus source root directory.</span><p> |
|
<span style="font-family: times new roman;">NOTE: See the Feature status page |
|
for exact status of the CMPI provider manager for different Pegasus |
|
platforms.</span><br> |
|
</p> |
|
<h5>JMPI Java Interface Provider Manager</h5> |
|
<p>Pegasus |
|
includes a provider manager for Java |
|
provider interfaces based on the SNIA provider interface |
|
definitions. This provider manager is considered alpha |
|
quality and is not compiled in the default build. See |
|
readme.jmpi in the Pegasus source root directory for more information.</p> |
|
</blockquote> |
|
</blockquote> |
|
<h3><b> Providers</b></h3> |
|
<div style="margin-left: 40px;">New for 2.5 is the ability of Providers |
|
to run out of process at |
|
request user- level and running CMPI providers remotely or out of |
|
process space.<br> |
|
<br> | <br> |
<span class="norm"></span>Administrators should check the providers to |
<span style="font-weight: bold;">Warning</span>: There is |
ensure that the provider vendor |
currently an open issue with RedHat to address a problem that is |
has made use of available authorization capability.<br> |
seen intermittently on RHEL5 and SLES10 systems. This problem is |
</div> |
described in <span style="color: rgb(153, 51, 153);"> <a |
<p style="margin-left: 40px;">There are a number of providers available |
href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
in the Pegasus release. |
bug |
This includes providers in the following categories:</p> |
|
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;"> |
|
<h4>Pegasus Internal Providers</h4> |
|
<p>Pegasus provides a set of "internal" providers that have direct |
6586</a> </span>and<span style="color: rgb(153, 51, 153);"> |
access to the CIMOM for information and provide information and |
<a |
services to support the CIMOM and its administration. The |
href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat |
providers in this category are mostly defined in the directory |
bug |
src/pegasus/controlproviders and include support for the following |
|
classes:</p> |
|
<ul> |
|
<li>DMTF Interop classes including __Namespace, <span class="SpellE">CIM_Namespace</span>, <span class="SpellE">CIM_ObjectManager</span>, |
248052</a>, </span>and manifests itself as an intermittent |
<span class="SpellE">CIM_CommunicationMechanism, and |
IPv6 socket failure. You should be aware that OpenPegasus with |
CIMOMStatistics.</span></li> |
IPv6 enabled may be significantly impacted in these |
</ul> |
environments.</p> |
<h4><span class="SpellE">CMPI Remote Providers</span></h4> |
<h4><font color="#000000">IPv6 on Windows</font></h4> |
<span class="SpellE">Pegasus includes an support for |
<p>Microsoft provides supported IPv6 implementations for Windows |
running CMPI providers to be run on remote systems without the need for |
Server 2003, Windows XP with Service Pack 1 (SP1), Windows XP |
an extra CIMOM. It uses a special proxying provider to relay requests |
with Service Pack 2 (SP2), and Windows CE .NET 4.1 and later.</p> |
to a remote location using so-called communication layers. The remote |
On Windows XP, you can use the <span style="font-weight: bold;">ipv6.exe</span> |
side has to start a CMPIRDaemon process, which accepts remote requests |
tool to install, uninstall, and query your IPv6 configuration. For |
and passes them on to CMPI style providers.</span><h3> |
example:<br> |
<b>Generic Providers</b></h3> |
<br> |
<p>These are providers that support multiple pegauss platforms and include the Generic <span class="SpellE">OperatingSystem</span> provider. See |
<div style="margin-left: 40px; color: rgb(153, 51, 153); |
the |
font-family: monospace;"><big><font color="#000000">ipv6 install<br> |
directory <span class="SpellE">src</span>/Providers/generic.</p> |
ipv6 if</font></big></div> |
<h4><b>Test/Sample Providers</b></h4> |
<p>Windows Vista and Windows Server 2008 support an integrated |
<p>See the directories <span class="SpellE">src/Providers/TestProviders</span> |
IPv4 and IPv6 implementation known as the Next Generation TCP/IP |
and <span class="SpellE">src</span>/Providers/sample for more |
stack. Note that the OpenPegasus IPv6 support has not yet been |
information about test and |
tested on Windows Vista or Windows Server 2008.<br> |
sample providers.</p> |
<br> |
<h4><b>Managed System Providers</b></h4> |
For more information on installing, configuring, and using IPv6 |
<p><span class="SpellE">ComputerSystem</span>, <span class="SpellE">DNSAdmin</span>, |
on Windows platforms, refer to the document <a |
<span class="SpellE">DNSService</span>, Operating System, Process, |
href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx"><font |
Processor. For |
color="#000000">IPv6 for Microsoft Windows: Frequently Asked |
more information on these providers see the documentation for each |
Questions</font></a>.<br> |
provider in |
|
the directory <span class="SpellE">src/Providers/ManagedSystem</span></p> |
|
<h4><span class="SpellE">Server Statistics Provider<br> |
|
</span></h4> |
|
CIM Server statistics, based on the DMTF 'CIM_StatisticalData' class, |
|
are implemented in this release. The statistics gathering is compiled |
|
by default but it is disabled through a property in the singleton |
|
CIM_ObjectManager class. It may be enabled or disabled by performing a |
|
ModifyInstance operation on the 'CIM_ObjectManager instance |
|
in the 'PG_InterOp' namespace to set the GatherStatisticalData property |
|
to 'true' or 'false'. This property setting is persistent across CIM |
|
Server restarts. A statistics display test tool, cimperf, is available |
|
from the Pegasus CVS repository. <h4><span class="SpellE">SLP Provider</span></h4> |
|
<p><span class="SpellE">This provider acts as the definer of |
|
SLP information for SLP registration and also controls the Pegasus SLP |
|
Service Agent. It is treated as a normal provider rather than a control |
|
provider because it does not use internal functions of the CIMOM to |
|
generate any of its information today. (conditionally compiled today)</span></p> |
|
</blockquote> |
|
<h2><b>Pegasus Indication Listeners</b></h2> |
|
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;"> |
|
<p class="MsoNormal">The generic components for a CIM Listener and a |
|
listener API are operational. This includes the functions for |
|
HTTP, XML indication input and response, and consumers of indications. |
|
This code can be used to define a separate listener package and is used |
|
as an indication listener in the Pegasus server. |
|
</p> | </p> |
<p class="MsoNormal">Pegasus includes 3 separate Indication Listeners.</p> |
<h4><font color="#000000">Testing OpenPegasus IPv6 support</font></h4> |
<h3>Embedded CIMListener</h3> |
As part of the OpenPegasus automated tests, the TestClient, |
<p class="MsoNormal">This listener is embedded in the CIMServer and allows the |
g11ntest, and IndicationStressTest test clients were modified to |
server to accept indications and route them.</p> |
run tests using the IPv6 loopback address (::1) if |
<h3>Standalone Static CIMListener</h3> |
PEGASUS_ENABLE_IPV6=true.<br> |
<p class="MsoNormal">This is a standalone listener that combines the functions |
|
of listener and consumer into a single element.</p> |
|
<h3>Standalone Dynamic Listener</h3> |
|
<p class="MsoNormal"> |
|
<font style="color: rgb(0, 0, 0);" color="#330099">Pegasus 2.5 |
|
includes a new standalone dynamic listener that is separate |
|
from the current standalone CIMListener and the ExportServer listener |
|
in the CIM server. |
|
The use model that this listener fits is the following: |
|
</font></p> |
|
<font style="color: rgb(0, 0, 0);" color="#330099"> </font><ul> |
|
<font style="color: rgb(0, 0, 0);" color="#330099"> <li> The listener may be packaged as |
|
part of the CIMOM or it may be packaged independently as part of |
|
another application. </li> |
|
<li> Consumers |
|
are developed independently of the listener and may be shipped with the |
|
listener or added to an installed listener at a future time. </li> |
|
</font></ul> |
|
<font style="color: rgb(0, 0, 0);" color="#330099"> </font> |
|
<p></p> |
|
<p><span style="color: rgb(0, 0, 0);"> </span><font color="#330099"><span style="color: rgb(0, 0, 0);">This |
|
dynamic listener provides a solution for the above use model. It |
|
is essentially a lightweight, pluggable listener that |
|
provides a small set of management features. The DynamicListener can be |
|
run inside a daemon or a service. It is easily configurable and |
|
bypasses traditional registration procedures. See |
|
<a href="http://www.openpegasus.org/pp/protected/upreviews/20/1303/PEP195_CIMListenerEnhancementsv1_6.htm" style="color: blue; text-decoration: underline;"><span style="color: rgb(51, 51, 255); text-decoration: underline;">PEP 195</span></a> <span style="color: rgb(255, 0, 0);"> </span>for |
|
details.</span> </font></p> |
|
</blockquote> |
|
<h3><span class="SpellE"><b>CIM_Schema</b></span></h3> |
|
<blockquote> |
|
<p>The default <span class="SpellE">CIM_Schema</span> loaded with this |
|
release is |
|
the DMTF CIM 2.9, final release. In addition, Pegasus includes |
|
a number of |
|
local classes defined for Pegasus. These are defined in the pegasus/Schemas |
|
directory. <span style=""></span>There are also a |
|
number of older schema available in the CVS. Further, the CIM 2.10 and CIM |
|
2.11 schemas are available in the CVS repository and the Pegasus is compatible |
|
with these Schemas.</p> |
|
<p>The mechanism to install other schemas than the default is defined |
|
in the mak/config.mak</p> |
|
<p style="margin-bottom: 12pt;"><b>NOTE:</b> The CIM 2.5 schema is |
|
maintained in the |
|
CVS repository because it remains the basis for parts of the Pegasus |
|
test |
|
environment.</p> |
|
</blockquote> |
|
<h3><b>Pegasus CIM Server <span class="SpellE">Administration</span></b></h3> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">cimuser</span></b> |
|
- Manage Pegasus CIM Server Users.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">cimconfig</span></b> |
|
- Manage the Pegasus CIM Server configuration parameters.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">cimauth</span></b> |
|
- Manage the CIM Server authorization characteristics. Today this is |
|
authorizing users to namespaces.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">cimprovider</span></b> |
|
- Manage information about the providers .</li> |
|
</ol> |
|
<br> | <br> |
<span style="font-weight: bold;">Server admin |
You can also perform manual tests using the IPv6 loopback or a |
note:</span><br> |
real IPv6-configured network interface. For example, using the |
<div style="margin-left: 40px;">The default behavior for determining |
IPv6 loopback on a system with OpenPegasus running on the WBEM |
the CIM server's HTTP and HTTPS ports has changed. In previous |
standard http port of 5988:<br> |
releases, any value in /etc/services would override a port explicitly |
<div style="margin-left: 40px;"><br> |
specified in the configuration. The new order for determining the |
<big style="font-family: monospace;"> osinfo -h ::1</big></div> |
CIM server's HTTP and HTTPS ports is as follows:<br> |
<h2><a name="Compatibility_Considerations_">Compatibility |
1) An explicitly specified port value takes precedence over any other |
Considerations</a></h2> |
values.<br> |
<p>Support for forward-compatibility is a fundamental design |
</div> |
principle for the OpenPegasus project. As a community, our goal |
<div style="margin-left: 40px;">2) If no port is specified, the value |
is for well-behaved OpenPegasus providers or clients, using only |
in /etc/services is used.<br> |
the externally defined OpenPegasus interface, to continue to |
3) If no value is specified in /etc/services, the default WBEM port is |
work with a minor version upgrade of OpenPegasus. However, there |
used.<br> |
are certain classes of errors (e.g., non-compliance with a |
</div> |
standard that significantly affects interoperability) that may |
<h3><b>Information client tools</b></h3> |
require the community to make potentially incompatible changes. |
<p>These tools provide information on the objects managed by the server.</p> |
The following table contains a list of defects/fixes that MAY |
<ol style="margin-top: 0in;" start="1" type="1"> |
impact, even well-behaved, OpenPegasus providers or clients when |
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">tomof</span> |
upgrading to this OpenPegasus release. <br> |
</b>- output classes and/or instance information from the Pegasus |
|
repository in MOF or XML format.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">dnsinfo</span></b> |
|
- Generate a set of standard information on the <span class="SpellE">Domain</span> |
|
Name System (DNS) configuration from CIM Classes. Note that the |
|
information generated is dependent on the information available from |
|
providers and differs from system to system.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">ipinfo</span></b> |
|
- Generates a set of standard information from the Network |
|
Schema. Information generated varies by system because of the |
|
level of provider support.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">osinfo</span></b> |
|
- Generate a set of standard information on the Operating System from |
|
CIM Classes. Note that the information generated is dependent on the |
|
information available from providers and differs from system to system<o:p></o:p></li> |
|
</ol> |
|
<h3><b>Test support Tools</b></h3> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Pegasus unit tests |
|
(available through the "tests" option on the Pegasus make files) these |
|
tests are defined throughout the Pegasus source tree typically in |
|
"tests" directories. <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">The Pegasus test suite |
|
(see the pegasus/tests directory<span class="SpellE"></span>)<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">TestClient</span> |
|
</b>- Basic client for overall platform operation testing. <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">wbemexec</span></b> |
|
- Test tool that sends/receives XML from XML input.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b>CLI</b> - Command line |
|
interface for Client commands.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b>Benchmark Test</b> - A |
|
benchmark test environment is provided which includes both a client and |
|
provider component. See <span class="SpellE">src/clients/benchmarkTest</span> |
|
for more information.</li> |
|
<li class="MsoNormal" style="color: black;"><b>cimperf - </b>Lightweight statistics are implemented for |
|
the |
|
client. The client statistics surfaces the elapsed time spent in the |
|
client, |
|
and the |
|
elapsed time spent on the network between client and server.</li> |
|
</ol> |
|
<h3><b>Pegasus Interface APIs</b></h3> |
|
<p>Details of the Pegasus public interfaces for this release are listed |
|
in PEP 209 |
|
available from the web <span class="GramE">site(</span><a href="http://www.openpegasus.org/pp/uploads/40/Administrator/My%20Documents/processes/www.openpegasus.org">www.openpegasus.org</a>). |
|
That document is the <span class="SpellE">authorative</span> source for the list |
|
of publicly supported Pegasus APIs. The Client and Provider API were |
|
originally frozen at the Pegasus version 2.1 release. The interfaces in the |
|
release of Pegasus 2.1 are forward compatible to this release. Well-behaved |
|
clients and providers compiled to the Pegasus 2.1 or 2.2 interfaces should be |
|
compatible with this release without compilation. There have been |
|
extensions and new interfaces added for this release. |
|
The Pegasus public |
|
interfaces includes the following major functions</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Client APIs<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">Provider APIs<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">CIM Object and System |
|
function APIs</li> |
|
</ol> |
|
<p>In addition, there are other client interfaces which are not today |
|
in the public SDK including:</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: rgb(0, 0, 0);"><span style="" lang="DA">CIM Listener APIs</span></li> |
|
<ul style="color: rgb(0, 0, 0);"> |
|
<li class="MsoNormal">CIM Listener |
|
is a component that can be used to consume indications without a |
|
dependency on the Pegasus CIMOM. In environments where no CIMOM is |
|
running or a physical separation between the indication listener and |
|
the CIMOM is desired, CIM Listener fits the bill. Still, there are |
|
several enhancements that are necessary to make CIM Listener scalable. <font style="color: rgb(0, 0, 0);">Enhancements were deemed significant |
|
enough to propose a new listener that builds off CIMListener's |
|
basic capabilities, yet allows the existing CIMListener to remain the |
|
same.</font></li> |
|
<ul> |
|
<li><font size="2">New CIM Listener now provides selective |
|
indication delivery.</font><br> |
|
</li> |
|
<li><font size="2">New CIM Listener |
|
keeps all consumer libraries in memory for the duration of its |
|
execution.</font><br> |
|
</li> |
|
<li><font size="2">New CIM Listener |
|
is now pluggable.</font></li> |
|
<li><font size="2">New CIM Listener |
|
now provides reliable indication delivery.</font></li> |
|
</ul> |
|
</ul> |
|
<li class="MsoNormal" style="color: black;"><span lang="da">SLP |
|
Client (User Agent) APIs which are extensions to the Client APIs</span></li> |
|
</ol> |
|
<p class="MsoNormal"><span style="color: black;"><o:p> </o:p></span></p> |
|
<p class="MsoNormal"><span style="color: black;">The APIs are |
|
documented in |
|
their respective header files and in HTML documentation based on |
|
the information |
|
in the header files extracted with the doc++ tool will be available on |
|
the |
|
OpenPegasus web site.<br> |
|
</span></p> |
|
<p class="MsoNormal"><b>WMI <span class="SpellE">Mapper</span></b></p> |
|
<p>The WBEM to WMI <span class="SpellE">Mapper</span> provides a way |
|
to access |
|
WMI data from Windows platform systems. It converts incoming XML/CIM |
|
requests |
|
to Microsoft WMI requests, executes the requests, converts the results |
|
to |
|
XML/CIM and returns the results to the client. WMI <span class="SpellE">Mapper</span> |
|
receives an HTTP message containing the XML/CIM request. It decodes the |
|
XML |
|
message and extracts from the HTTP message header the user credentials |
|
provided |
|
on the connection (username and password). The WMI <span class="SpellE">Mapper</span> |
|
authenticates these credentials, verifying if the provided credentials |
|
have |
|
access to the desired WMI data. This is done because the WMI <span class="SpellE">Mapper</span> runs as a service, logged on using an |
|
account with |
|
administrative rights (which has all access to WMI data). Because of |
|
this, the |
|
WMI <span class="SpellE">Mapper</span> impersonates the user |
|
credentials provided |
|
on the HTTP message to ensure that the calling user has rights to |
|
browse WMI |
|
data. Hence, ALL requests made to the WMI <span class="SpellE">Mapper</span> |
|
MUST |
|
contain user credentials.<br> |
|
</p> | </p> |
<ol> |
<table style="font-family: Arial;" bordercolordark="#666666" |
</ol> |
bordercolorlight="#CCCCCC" border="1" cellspacing="1" |
<h2>Relationship to |
width="80%"> |
CIM/WBEM Standards</h2> |
<tbody> |
|
<tr align="center"> |
|
<th bgcolor="#00ffff" width="10%">Bugzilla #</th> |
|
<th bgcolor="#00ffff">Description</th> |
|
</tr> |
|
<tr align="center"> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8830">Bug |
|
|
|
|
|
|
|
8830</a></td> |
|
<td align="left">Starting with OpenPegasus 2.11.0 the |
|
requirement for providers (CMPI and C++) to filter |
|
properties from instances has been relieved. The server |
|
will do the filtering at the protocol adapter level. To |
|
avoid a negative impact on performance the |
|
CIMInstance::filter() and |
|
CMPIInstanceFT.setPropertyFilter() functions have been |
|
changed to a NOP. This may be a change in behavior for |
|
provider relying in some unknown way on the instance being |
|
filtered through these functions. To allow users to |
|
actually filter properties from an instance, new function |
|
CIMInstance::filterInstance() will actually filter |
|
properties from an instance exactly as the |
|
CIMInstance::filter() did in previous versions of Pegasus.</td> |
|
</tr> |
|
<tr align="center"> |
|
<td><a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9369">Bug |
|
|
|
|
|
|
|
9369</a><br> |
|
</td> |
|
<td align="left">Reregistering of an indication provider |
|
requires that the cimserver be restarted to send the |
|
enableIndication request to the providers. This issue has |
|
existed starting with OpenPegasus 2.10 to the current |
|
version. 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> |
<p>Pegasus was designed and implemented to comply with the DMTF | <p>Pegasus was designed and implemented to comply with the DMTF |
specifications The following table defines the level of the DMTF specifications |
CIM/WBEM specifications The following table defines the level of |
to which this version of Pegasus conforms today.</p> |
the DMTF specifications to which this version of Pegasus aims to |
<table id="AutoNumber1" border="1" cellspacing="1" width="100%"> |
conform today.</p> |
|
<table id="AutoNumber1" border="1" cellspacing="1" width="80%"> |
<tbody> | <tbody> |
<tr> | <tr> |
<td bgcolor="#00ffff" width="33%"><b>DMTF Specification</b></td> | <td bgcolor="#00ffff" width="33%"><b>DMTF Specification</b></td> |
<td bgcolor="#00ffff" width="33%"><b>Specification Version</b></td> | <td bgcolor="#00ffff" width="33%"><b>Specification Version</b></td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0004 CIM Specification</td> |
<td width="33%">DSP 0004 - CIM Infrastructure Specification</td> |
<td width="33%">Version 2.2 with Addendum</td> |
<td width="33%">Version 2.3 Final, 4 October 2005</td> |
</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.1, final, 6 January 2002</td> |
<td width="33%">Version 1.2, Final, January 09, 2007</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0201 - Representation of CIM in XML</td> | <td width="33%">DSP 0201 - Representation of CIM in XML</td> |
<td width="33%">2.1, preliminary, May 2, 2002</td> |
<td width="33%">Version 2.2 Final, January 09, 2007</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0202 - CIM Query Language Specification</td> |
|
<td width="33%">1.0.0, preliminary, 9 December 2004</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0205 - WBEM Discovery using SLP</td> | <td width="33%">DSP 0205 - WBEM Discovery using SLP</td> |
<td width="33%">1.0, preliminary, 27 January 2004</td> | <td width="33%">1.0, preliminary, 27 January 2004</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">WBEM SLP Template</td> |
<td width="33%">DSP 0206 - WBEM SLP Template</td> |
<td width="33%">1.0.0</td> |
<td width="33%">1.0.0, Preliminary, January 2004</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">CIM Schema </td> | <td width="33%">CIM Schema </td> |
<td width="33%">2.9 Final, Jan. 2005</td> |
<td width="33%">2.31.0 Final ( default) </td> |
|
</tr> |
|
<tr> |
|
<td>DSP0226 - Web Services for Management<br> |
|
</td> |
|
<td>Version 1.1.1<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td>DSP0227 - WS-Management CIM Binding Specification<br> |
|
</td> |
|
<td>Version 1.2.0<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td>DSP0230 - WS-CIM Mapping Specification </td> |
|
<td>Version 1.1.0<br> |
|
</td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<h2><b><span style="font-family: Times;"><a name="Supported Platforms">Supported |
<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIS |
Platforms</a></span></b></h2> |
SMI Profiles Supported</h2> |
<p>Each Pegasus release lists as 'active' platforms those |
<p>Today OpenPegasus includes support for several DMTF profiles |
hardware/software platforms that have recognized ports for the Pegasus |
including the ones defined below:</p> |
code |
<ol> |
base including a maintainer for the platform that will be willing to |
<li>DMTF ProfileRegistration Version 1.0.0</li> |
regularly document issues and/or fix defects as the Pegasus |
<li>DMTF Indications 1.1.0. Since this is effectively the same |
code base is changed. |
as the SNIA SMI Indication profile it also supports this |
Pegasus may be operable on other platforms (ex. Windows 98) but without |
profile. This profile is enabled by compiling OpenPegasus with |
a group |
the build variable PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.<br> |
to provide the role of test and maintenance, correct operation of |
</li> |
Pegasus cannot be |
<li>SNIA Profile Registration 1.0.0</li> |
assured. In all cases, including the active platforms, it is the |
<li>SNIA Server 1.1.0 & 1.2.0<br> |
responsibility of the entity that packages and/or compiles OpenPegasus |
</li> |
for shipment or deployment, to read, and actively monitor the Pegasus |
</ol> |
bugzilla database for a list of relevant defects that affect their |
<h2><a name="Conformance with DMTF Specifications">Conformance |
platform. The platforms that are considered 'active' for this |
Exceptions to DMTF Specifications</a></h2> |
Pegasus release are:<br> |
<p>It is a major goal of the OpenPegasus project to both drive and |
<span class="norm"></span><br> |
utilize the DMTF CIM/WBEM specifications. However, today |
</p> |
there are a number of known differences. As of this |
<table class="MsoNormalTable" style="width: 302.25pt;" border="1" cellpadding="0" cellspacing="1" height="409" width="504"> |
release, some of the differences include the following:</p> |
|
<ol> |
|
<li><b>Provider Registration</b> - Pegasus supports registration |
|
through a set of Pegasus Provider registration classes rather |
|
than support the DMTF defined Provider Qualifier. Pegasus will |
|
not support this qualifier in the future. See the readme for |
|
more information on provider registration. This is not a |
|
deviation from the specifications but is a different method of |
|
registration than many CIM Servers and means that the the |
|
provider qualifier is unused in Pegasus.</li> |
|
<li><b>Lifecycle Indications </b>-Today Pegasus supports |
|
process indications and lifecycle indications when defined |
|
specifically by providers. Pegasus does not support lifecycle |
|
indications if they are not defined by the provider or for |
|
changes to CIM Classes.<font color="#ff0000"> </font><span |
|
class="norm"><font color="#ff0000"> </font>For more |
|
information see the Pegasus CVS file:<a name="comtag_137"><font |
|
size="2"> </font><font face="Courier New" size="2"> pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a><font |
|
size="2">.</font></span></li> |
|
<li> |
|
<p class="MsoNormal"><font style="color: rgb(0, 0, 0); |
|
font-weight: bold;">IncludeQualifiers option on Instance |
|
Operations</font><span style="color: black;"><b> </b> |
|
- The DMTF specifications have deprecated the use of |
|
qualifiers on instance operations with the 1.2 CIM |
|
Operations Specification and stated specifically that the |
|
client should NOT depend on the includeQualifiers |
|
parameter of the CIM/XML instance operations returning |
|
qualifiers. Some CIM Client implementations expect |
|
instances returned from the CIM Server to include the |
|
qualifiers defined in the class definition (such as KEY |
|
qualifiers on properties). </span> Pegasus |
|
today expects the provider to complete the qualifiers on |
|
instances in accordance with the specification and generally |
|
the interpretation is that Pegasus applies class level |
|
qualifiers when the includeInstance parameter is supplied on |
|
instance operations. However, Pegasus today is |
|
inconsistent in the return of qualifiers so that the user |
|
should NOT depend on Pegasus accurately honoring the |
|
includeQualifier parameter for instance operations. In |
|
the future it is expected that Pegasus will deprecate the |
|
use of qualifiers on instance operations completely. |
|
When Pegasus uses object normalization, the normalizer |
|
does apply qualifiers to returned instances if the |
|
includeQualifiers operation parameter is set.</p> |
|
</li> |
|
<li><b>LocalOnly option on instance Operations </b>- With the |
|
1.1 version of Specification for CIM Operations over HTTP, the |
|
definition of the LocalOnly parameter for the GetInstance and |
|
Enumerate Instances operations was modified. This change was |
|
incorrect, resulted in reduced functionality and introduced a |
|
number of backward compatibility issues. As a result of issues |
|
introduced by this change, we strongly recommend that CIM |
|
Clients set LocalOnly = false and do not rely on the use of |
|
this parameter to filter the set of set of properties |
|
returned. See Appendix C of this specification for more |
|
information.</li> |
|
<li> |
|
<p class="MsoNormal"><b>MultiRequest Operations</b> - Pegasus |
|
does not support the DMTF defined MultiRequest Operation |
|
option.</p> |
|
</li> |
|
<li> |
|
<p class="MsoNormal"><b>MOF Compiler namespace pragma</b> - |
|
The Pegasus compiler does not support the namespace pragma.</p> |
|
</li> |
|
<li><b>CIMOperation Trailer </b>- Pegasus implements chunking |
|
based on the DSP0200 1.2.0 preliminary spec. including the |
|
operation trailer defined in that specification Refer to bug <a |
|
href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> |
|
for more details. This trailer was completely removed from the |
|
DSP0200 1.2 final specification as a non-compatible change so |
|
that if chunking is used Pegasus is returning a noncompliant |
|
response to enumerate type requests. </li> |
|
<li><span style="font-weight: bold;">Whitespace in XML value |
|
Element</span> - Pegasus trims the leading and trailing |
|
whitespace from XML value elements that are of the Type |
|
String. This behavior is documented in Pegasus bug <a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8773">8773</a> |
|
and there is a patch available for users. However, since |
|
the change is considered a change to behavior this will not be |
|
patched until pegasus does a major version update. NOTE: There |
|
are some documented bugs in Pegasus such as this that the |
|
OpenPegasus team feels cannot be incorporated into the code |
|
until a major version update. These bugs are documented |
|
with the Bugzilla tag <big style="font-weight: bold;"><samp>"3.0_TARGET".</samp></big></li> |
|
<li><span style="font-weight: bold;">modifyInstance operation |
|
behavior in the Pegasus repository does not match the DMTF |
|
specification</span>. Under some conditions (ex. if no |
|
propertyList is supplied) it modifies all properties rather |
|
than just the properties supplied with the request thereby |
|
Nulling out existing values. See bug <a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8752">8752</a> |
|
for more information.</li> |
|
<li><b>OpenPegasus Interop Namespace</b> - The default interop |
|
namespace name in OpenPegasus is "root/PG_Interop". In |
|
versions of OpenPegasus prior to 2.12.0 this could be changed |
|
during build by modifying a string definition in the code. |
|
Effective version 2.12 this has become a build option |
|
with the build configuration environment variable |
|
PEGASUS_INTEROP_NAMESPACE = <name for this namespace> |
|
however, the default if built without this change is still |
|
"root/PG_InterOp"<br> |
|
</li> |
|
<li><b>OpenPegasus WSMAN protocol on windows does not handle |
|
NaN, INF, or -INF</b> (bug <a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>) |
|
- If requests or responses include properties or parameters |
|
with floating point property types (Real32 or Real64) with the |
|
special states NaN, INF, or -INF on a Windows platform, the |
|
input is not accepted because these special strings are not |
|
understood by the decoder on Windows.</li> |
|
<li><b>OpenPegasus outputs Nan, INF, -INF special values for |
|
Real32 and Real64 property and Parameter types for the |
|
CIM/XML protocol</b> - (bug <a |
|
href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9392">9392</a>). |
|
|
|
|
|
|
|
Today the DMTF Specification DSP0201 allows only numeric |
|
information in the format definition for this type and does |
|
not all the special strings Nan, etc. However, OpenPegasus |
|
actually outputs the special strings if that is what is |
|
defined in the internal values. OpenPegasus does not |
|
allow these special Strings on input however,</li> |
|
<li><b>OpenPegasus does not handle covered properties</b> - (bug |
|
<a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">3571</a>) |
|
Covered properties (properties which have the same name in a |
|
superclass and subclass without overridding the property in |
|
the superclass) are not allowed in OpenPegasus. While the |
|
requirement for this functionality was added to DSP0004 |
|
subsequent to version 2.4, the general agreement is that the |
|
requirement itself is not supportable and particularly not |
|
with the existing OpenPegasus APIs. Further, the |
|
requirement is expected to be removed in the future (i.e CIM |
|
3.0).<br> |
|
</li> |
|
</ol> |
|
<h2><b><span style="font-family: Times;">OpenPegasus <a |
|
name="Supported Platforms">Supported Platforms</a></span></b></h2> |
|
<p align="left">Each OpenPegasus release lists as 'active' |
|
platforms those hardware/software platforms that have recognized |
|
ports for the Pegasus code base including a maintainer for the |
|
platform that will be willing to regularly document issues |
|
and/or fix defects as the Pegasus code base is changed. |
|
Pegasus may be operable on other platforms (ex. Windows 98) but |
|
without a group to provide the role of test and maintenance, |
|
correct operation of Pegasus cannot be assured. In |
|
all cases, including the active platforms, it is the |
|
responsibility of the entity that packages and/or compiles |
|
OpenPegasus for shipment or deployment, to read, and actively |
|
monitor the Pegasus Bugzilla database for a list of relevant |
|
defects that affect their platform. The platforms |
|
that are considered ported are shown in the two tables |
|
below. The first table represents platform for which |
|
testing is done on a regular basis and reported to the Pegasus |
|
Nightly Build Test WEB Page. Those platforms which have been |
|
ported but do not have test results that are current at the time |
|
of the release are reported in the second table.</p> |
|
<b>Actively Supported Platforms (Nightly Tests Reported for this |
|
release)</b> |
|
<table class="MsoNormalTable" style="width: 90%;" border="1" |
|
cellpadding="0" cellspacing="1"> |
<tbody> | <tbody> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; background: rgb(153, 255, 153) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 126.75pt;" height="26" width="211"> |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) |
<p class="MsoNormal"><b><span style="color: black;">Platform and |
none repeat scroll 0% 50%; -moz-background-clip: initial; |
OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
-moz-background-origin: initial; |
|
-moz-background-inline-policy: initial; width: 240px;" |
|
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Platform |
|
|
|
|
|
and OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; background: rgb(153, 255, 153) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; width: 173.25pt;" height="26" width="289"> |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) |
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span style="color: black;"><o:p></o:p></span></p> |
none repeat scroll 0% 50%; -moz-background-clip: initial; |
|
-moz-background-origin: initial; |
|
-moz-background-inline-policy: initial; width: 75%;" |
|
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" width="211"> |
<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; width: 173.25pt;" height="25" width="289"> |
<td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span style="color: black;">HP <span class="SpellE">aC</span>++ B3910B<o:p></o:p></span></p> |
<p class="MsoNormal"><span style="color: black;">HP <span |
|
class="SpellE">aC</span>++ B3910B<o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" width="211"> |
<td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">Linux on Power</span></span><span style="color: black;"><o:p></o:p></span></p> |
<p class="MsoNormal"><span class="SpellE"><span |
|
style="color: black;">Linux on Power</span></span><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" width="289"> |
<td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
<p class="MsoNormal"><span class="SpellE"><span |
|
style="color: black;">gcc</span></span><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" width="211"> |
<td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">zLinux</span></span><span style="color: black;"><o:p></o:p></span></p> |
<p class="MsoNormal"><span class="SpellE"><span |
|
style="color: black;">zLinux</span></span><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" width="289"> |
<td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
<p class="MsoNormal"><span class="SpellE"><span |
|
style="color: black;">gcc</span></span><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" width="211"> |
<td style="padding: 0.75pt;"> |
<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; width: 173.25pt;" height="25" width="289"> |
<td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"><o:p></o:p></span></p> |
<p class="MsoNormal"><span class="SpellE"><span |
|
style="color: black;">gcc</span></span><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" width="211"> |
<td style="padding: 0.75pt;"> <span style="color: black;"><font |
<p class="MsoNormal"><span style="color: black;">Linux IA-32<o:p></o:p></span></p> |
size="3">Linux IA-32</font></span></td> |
|
<td style="padding: 0.75pt;"> <span class="SpellE"><span |
|
style="color: black;"><font size="3">gcc</font></span></span><span |
|
style="color: black;"><font size="3"> (versions 3.xx, |
|
4.xx) clang(The clang compiler usage is considered |
|
experimental and is not part of the nightly tests |
|
today)</font><o:p></o:p></span></td> |
|
</tr> |
|
<tr style=""> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">Linux |
|
X86_64<o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" width="289"> |
<td style="padding: 0.75pt;"> |
<p class="MsoNormal"><span class="SpellE"><span style="color: black;">gcc</span></span><span style="color: black;"> |
<p class="MsoNormal"><span class="SpellE"><span |
(versions 2.9x and 3.xx)<o:p></o:p></span></p> |
style="color: black;">gcc</span></span><span |
|
style="color: black;"> (versions 3.xx, 4.xx) </span><span |
|
style="color: black;"><font size="3">clang(The clang |
|
compiler usage is considered experimental and is not |
|
part of the nightly tests today)</font></span></p> |
</td> | </td> |
</tr> | </tr> |
|
<tr> |
|
<td style="vertical-align: top;"><font size="3">z/OS V1.7 |
|
and up</font></td> |
|
<td style="vertical-align: top;"><font size="3">XL C/C++ |
|
from z/OS Version 1.7 and up</font></td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
|
|
<p align="center"><b>Platforms not Actively supported for this |
|
release (No current Nightly Build Test Results</b></p> |
|
<table class="MsoNormalTable" style="width: 90%;" id="table2" |
|
border="1" cellpadding="0" cellspacing="1"> |
|
<tbody> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="91" width="211"> |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) |
<p class="MsoNormal"><span style="color: black;">Windows 2000<o:p></o:p></span></p> |
none repeat scroll 0% 50%; -moz-background-clip: initial; |
|
-moz-background-origin: initial; |
|
-moz-background-inline-policy: initial; width: 240px;" |
|
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Platform |
|
|
|
|
|
and OS</span></b><span style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="91" width="289"> |
<td style="padding: 0.75pt; background: rgb(0, 255, 255) |
<p class="MsoNormal"><span style="color: black;" lang="NL">Microsoft |
none repeat scroll 0% 50%; -moz-background-clip: initial; |
Visual C++ Ver 6 and Microsoft .Net compiler Version. </span><span style="color: black;">Works on VC .NET 2003 (<span class="SpellE">aka</span> |
-moz-background-origin: initial; |
v7.1)<o:p></o:p></span></p> |
-moz-background-inline-policy: initial; width: 75%;" |
|
height="26"> |
|
<p class="MsoNormal"><b><span style="color: black;">Compilers</span></b><span |
|
style="color: black;"><o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="padding: 0.75pt; width: 126.75pt;" height="69" width="211"> |
<td style="padding: 0.75pt;"> <font size="3">Windows XP, |
<p class="MsoNormal"><span style="color: black;">Windows XP<o:p>, Windows |
Windows Vista, Windows 7, Windows Server 2008</font> |
2003</o:p></span></p> |
<p></p> |
</td> |
|
<td style="padding: 0.75pt; width: 173.25pt;" height="69" width="289"> |
|
<p class="MsoNormal"><span style="color: black;" lang="NL">Microsoft |
|
Visual C++ Ver. 6 and Microsoft .Net compiler Version </span>7.1<span style="color: black;" lang="NL"><o:p></o:p></span></p> |
|
</td> | </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft |
|
Visual C++ Compilers 2003 - 2010.. Note: Visual C++ Ver. |
|
6 no longer being regular tested.Note that today there |
|
are some open issues with the Windows.</font> </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="43" width="211"> <font size="3">MacOS version 10.2 and higher</font></td> |
<td style="padding: 0.75pt;"> <font size="3">MacOS version |
<td style="padding: 0.75pt; width: 173.25pt;" height="43" width="289"> <font size="3">gcc 3.3</font></td> |
10.3 and higher</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 Alpha<br> |
<td style="vertical-align: top;"><big><font color="RED"><span |
</big></td> |
style="color: rgb(0, 0, 0);">Solaris 8</span></font></big></td> |
<td style="vertical-align: top;"> <big><font style="color: rgb(0, 0, 0);" color="RED">HP C++ V6.5-042 for OpenVMS |
<td style="vertical-align: top;"><big>GNU |
Alpha and above</font></big> </td> |
2.95.3, Sun CC compiler V 5.8. Note that the |
|
latest thread patch (108993) may be required. (see |
|
Pegasus bug 4632)</big><br> |
|
</td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><span class="norm"></span><font style="color: rgb(0, 0, 0);"> HP OpenVMS IA64</font></big></td> |
<td style="vertical-align: top;"><span class="norm"></span><big><font |
<td style="vertical-align: top;"><span class="norm"></span><big><font style="color: rgb(0, 0, 0);">HP C++ V7.1-011 on OpenVMS IA64 and above</font></big> |
color="RED"><span style="color: rgb(0, 0, 0);">Solaris |
|
9</span></font></big></td> |
|
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
|
WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 8<br> |
<td><big>HP OpenVMS 8.3 or later Alpha</big></td> |
</span></font></big></td> |
<td><big><font style="color: rgb(0, 0, 0);" color="RED">HP |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun CC |
C++ V<span style="color: rgb(153, 51, 153);">7.3-009 |
compiler V 5.8. Note that the latest thread patch (108993) may be |
or later required</span> for OpenVMS Alpha</font></big></td> |
required. (see Pegasus bug 4632)</big><br> |
</tr> |
|
<tr> |
|
<td><big><font style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 |
|
or later IA64</font></big></td> |
|
<td><big><font style="color: rgb(0, 0, 0);">HP C++ V7.</font><font |
|
color="#993399">3-023 or later required</font><font |
|
style="color: rgb(0, 0, 0);"> on OpenVMS IA64</font></big></td> |
|
</tr> |
|
<tr> |
|
<td style="padding: 0.75pt;"> |
|
<p class="MsoNormal"><span style="color: black;">Windows |
|
2000</span></p> |
</td> | </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft |
|
Visual C++ Ver. 6 and Microsoft .Net compiler |
|
version. Works on VC .NET 2003 v7.1). NOTE: Visual |
|
C++ Ver. 6 no longer being regularly tested.</font></td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><span class="norm"></span><big><font><font color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9<br> |
<td style="padding: 0.75pt;"> <font size="3">Windows 2003</font> |
</span></font></font></big></td> |
<p></p> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun WorkShop 6 |
|
update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
|
</td> | </td> |
|
<td style="padding: 0.75pt;"> <font size="3">Microsoft |
|
Visual C++ Ver. 6 and Microsoft .Net compiler Version |
|
7.1. Note: Visual C++ Ver. 6 no longer being regular |
|
tested. </font> </td> |
|
</tr> |
|
<tr> |
|
<td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc |
|
and IX86)</big></td> |
|
<td><big>CC Compiler Sun Studio 5.11</big></td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<br> |
<p><b>Platform patches</b> </p> |
<b>Platform patches</b><p style="margin-top: 0pt; margin-bottom: 0pt;"> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font |
<font style="color: rgb(0, 0, 0);">The following is a list of platform |
style="color: rgb(0, 0, 0);">The following is a list known of |
patches Pegasus requires.<br> |
platform patches Pegasus requires.</font></p> |
</font> |
|
</p> |
|
<div style="margin-left: 40px;"> | <div style="margin-left: 40px;"> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font style="color: rgb(0, 0, 0);">RHAS |
|
2.1 needs the update to fix Red Hat Bugzilla 98815.</font><br> |
|
</p></div> |
|
<br> |
|
<p>Further information regarding Pegasus support on IBM platforms can |
|
be |
|
found at: <a href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span style="text-decoration: underline; color: rgb(51, 51, 255);">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</span></a> |
|
</p> |
|
<p> <br> |
|
Further information regarding Pegasus support on HP platforms can be |
|
found at: |
|
<a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> |
|
<h2><a name="Conformance with DMTF Specifications">Conformance with |
|
DMTF Specifications</a></h2> |
|
<p>It is a major goal |
|
of the OpenPegasus project to both drive and utilize the DMTF CIM/WBEM |
|
specifications. However, today there are a number of known |
|
differences. |
|
As of this release, some of the differences include the following:</p> |
|
<ol> | <ol> |
<li><b>Provider Registration</b> - Pegasus supports registration |
|
through a set of Pegasus Provider registration classes rather than |
|
support the DMTF defined Provider Qualifier. Pegasus will not support |
|
this qualifier in the future. See the readme for more information on |
|
provider registration.</li> |
|
<li> <b>Indications </b>-Today Pegasus supports process |
|
indications but does not |
|
include any specific support for lifecycle indications.</li> |
|
<li> |
|
<p class="MsoNormal"><span style="color: black;"> </span><font style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers |
|
option on Instance Operations</font><span style="color: black;"><b> </b> |
|
- |
|
The DMTF specifications are unclear regarding the inclusion of |
|
qualifiers on |
|
CIM instances. Some CIM Client implementations expect instances |
|
returned |
|
from the CIM Server to include the qualifiers defined in the class |
|
definition (such as KEY qualifiers on properties). </span> Pegasus |
|
today expects the provider to complete the qualifiers on instances in |
|
accordance with the specification and generally the interpretation is |
|
that Pegasus applies class level qualifiers when the includeInstance |
|
parameter is supplied on instance operations. However, Pegasus |
|
today is inconsistent in the return of qualifiers so that the user |
|
should NOT depend on Pegasus accurately honoring the includeQualifier |
|
parameter for instance operations. In the future it is expected |
|
that Pegasus will deprecate the use of qualifiers on instance |
|
operations completely.</p> |
|
</li> |
|
<li><b>LocalOnly option on instance |
|
Operations </b>- With the 1.1 version of Specification for CIM |
|
Operations over HTTP, the definition of the LocalOnly parameter for the |
|
GetInstance and EnumerateInstances 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.</li> |
|
<li> | <li> |
<p class="MsoNormal"> <b>CIM MOF compiler function for |
<p style="margin-top: 0pt; margin-bottom: 0pt;"> <font |
instance aliasing</b> - The Pegasus MOF compiler does not today support |
style="color: rgb(0, 0, 0);">RHAS 2.1 needs the update |
this function. This function is planned for a future version.</p> |
to fix Red Hat Bugzilla 98815.</font></p> |
</li> | </li> |
<li> | <li> |
<p class="MsoNormal"><b> MultiRequest Oprations</b> - Pegasus |
<p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4 |
does not support the DMTF defined MultiRequest Operation option.</p> |
multithreading bug in getpwuid-r could cause a CIM Server |
|
failure (Bugzilla 6232). This is fixed in RHEL 4.5</p> |
</li> | </li> |
<li> | <li> |
<p class="MsoNormal"><b>MOFCompiler namespace pragma</b> - The |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and |
Pegasus compiler does not support the namespace pragma.</p> |
SUSE Linux multiple versions - multithreaded client |
</li> |
intermittently fails connecting to IPv6 (Pegasus Bugzilla |
</ol> |
6586) (Red Hat bug 248052)<br> |
<h2><a name="Changes in This Release">Changes in This Release</a></h2> |
|
<p>The development and release of each version of Pegasus is defined |
|
and |
|
controlled through Pegasus PEP documents. PEP 180 is the |
|
controlling document for Pegasus 2.5.0 and PEP 239 is the controlling |
|
document for this release. These PEPs list the original set of changes proposed and the |
|
status of |
|
each of those changes. Note that not all of the originally defined |
|
functionality was completed for this release.</p> |
|
<p>In general, the areas of development for release 2.5.0 were:</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Addition of CQL |
|
stage 1 support<br> |
|
</p> | </p> |
</li> | </li> |
<li class="MsoNormal" style="color: black;"> |
</ol> |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Refactoring of |
</div> |
Object Normalizer function to improve performance. </p> |
<p>Further information regarding Pegasus support on IBM platforms |
</li> |
can be found at: <a |
<li class="MsoNormal" style="color: black;"> |
href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Out of Process |
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> |
Provider user level request.<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Embedded Object |
|
support. </p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Command Line |
|
Utilities<br> |
|
</p> | </p> |
</li> |
<p> Further information regarding Pegasus support on HP platforms |
<li class="MsoNormal" style="color: black;"> |
can be found at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;">CIMDateTime |
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus |
enhancements<br> |
Defects</a></span></h2> |
|
<p>The OpenPegasus Bugzilla database documents any defects found |
|
in Pegasus and is available through the following |
|
link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus |
|
|
|
|
|
|
|
bugzilla database</a>. Effective with the start of |
|
the OpenPegasus 2.6 work, all changes to the CVS tree are |
|
documented through bugs. Bugs reports are filed not only |
|
for bugs and their corresponding fixes but also as part of the |
|
process of committing new code representing the work on PEPs |
|
done for OpenPegasus 2.6 and all subsequent versions. |
|
Therefore, a search of the OpenPegasus Bugzilla base for bugs |
|
with the tag for a particular version (ex. <a |
|
href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED">2.6.0_APPROVED</a>, |
|
<a |
|
href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED"> |
|
2.6.1_APPROVED</a>, <a |
|
href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>, |
|
etc) will yield all changes to the Pegasus CVS tree for that |
|
OpenPegasus release.</p> |
|
<p> - Changes between the 2.12.0 release |
|
and 2.12.1 revision are defined in bugs tagged |
|
(2.12.1.APPROVED). The complete list of 12 bugs is <a |
|
href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.1_APPROVED">2.12.1_APPROVED |
|
|
|
|
|
bugs</a><br> |
</p> | </p> |
</li> |
<p> - Changes that were made in the minor |
<li class="MsoNormal" style="color: black;"> |
release 2.12 are in bugs Tagged 2.12.0_APPROVED. The link |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of |
is <a |
AutoPtr enhancements. </p> |
href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.12.0_APPROVED"> |
</li> |
Pegasus 2.12.0_APPROVED bug list.</a><br> |
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Certificate |
|
management and user-based certificate authentication<br> |
|
</p> | </p> |
</li> |
<h2><a name="Pegasus Release Control and Version Definition |
<li class="MsoNormal" style="color: black;"> |
Documentation">Release Control and Version Definition |
<p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of HTTP |
Documentation</a></h2> |
chunking. Pegasus |
<p>The OpenPegasus project is controlled largely through the CVS |
now supports HTTP V1.1 transfer encoding otherwise known as chunking .<font style="color: rgb(51, 51, 255);" color="RED"><a href="http://www.openpegasus.org/pp/uploads/40/5097/PEP140_ChunkedEncoding_4.3.html"> |
repository and a set of documents (PEPs) that serve both as the |
PEP 140</a></font> describes the implementation details.</p> |
definition and review mechanism for new and modified Pegasus |
</li> |
functionality and for the definition and documentation of |
<li class="MsoNormal" style="color: black;">Client side performance |
releases.</p> |
statistics</li> |
The following documentation defines the characteristics of this |
<li class="MsoNormal" style="color: black;">Syslog Indication handler.</li> |
Pegasus release. The documents are available in the |
<li class="MsoNormal" style="color: black;">Email Indication handler.</li> |
OpenPegasus CVS repository. <br> |
<li class="MsoNormal" style="color: black;">Port to OpenVMS.</li> |
<ul> |
</ol> |
<li><b> OpenPegasus Release Definition/Status -No PEP (See Wiki |
<p>For release 2.5.1, a number of additional changes were made( See PEP 239 for |
Section <a |
more details) Note: there was no PEP controlling Pegasus 2.5.2 changes, simply |
href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2.12_x">OpenPegasus |
approved bugs:.</p> |
2.12.x |
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li>Significant performance improvements ( better than 10 to 1 for operations |
|
and 3 to 1 for indications). (bug 4225)</li> |
|
<li>Improved support for the several platforms (Solaris, MacOS, HardHat Linux)</li> |
Release Status</a>) - <span style="font-weight: normal;">A |
<li>Modified Makefile targets for easier usage.</li> |
|
<li>Extended and reorganized unit and end-end tests.</li> |
|
<li>Completed implementation of statistics gathering for operations.</li> |
|
<li>Further integrated CMPI and added additional tests.</li> |
section in the Pegasus wiki is used throughout the |
<li>Consolidate some of the compile-time variables. Largely this meant moving |
development of this version as the control point for |
from separate variables for DISABLE and ENABLE to a single variable where the |
functionality that will go into the release and points to |
value representes the state.</li> |
all of the PEPs that represent the Pegasus |
<li>Corrected error where Pegasus could not maintain general whitespace in |
functionality changes for this version of Pegasus</span>. </b></li> |
strings (bug 4624).</li> |
<b> </b><span style="font-weight: bold;"></span><b>OpenPegasus |
<li>SLP extended to allow optional use of OpenSLP as the Service Agent (SA) in place of |
|
the Pegasus internal SA.</li> |
|
<li>Changes to align OpenPegasus and Red Hat RPM packaging and configuration |
|
options.</li> |
Build and Configuration Options for Selected Platforms |
<li>Additonal testing and integration of the JMPI provider manager.</li> |
- <span style="font-weight: normal;">In previous |
</ol> |
versions of Pegasus this information was released as a |
<p>Specifically the status of several components of Pegasus functionality were |
Pegasus PEP. Starting with Pegasus 2.9.0 the information is |
moved in status on the Feature Status Page as follows:</p> |
located in the OpenPegasus CVS repository as <big |
<ol> |
style="font-weight: bold;"> <span style="font-family: |
<li>Binary Repository move to green (production capable). (see bug 4388)</li> |
monospace;">pegasus/doc/BuildAndReleaseOptions.html</span></big>.</span></b><b> |
<li>Out of Process providers</li> |
<li> OpenPegasus External Interfaces -<span |
<li>Pegasus Provider Interfaces, User Context for Linux and Unix</li> |
style="font-weight: normal;">The list of the OpenPegasus |
</ol> |
interfaces that are considered external and therefore |
<p class="MsoNormal" style="margin-left: 0.5in;"> </p> |
"frozen". Unless an exception is explicitly approved by |
The complete set of <span class="SpellE">changes </span>defined for this release |
the Steering Committee all subsequent releases of Pegasus |
is defined in PEP 239 |
MUST continue to support these interfaces. Interfaces not |
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus defects<br> |
explicitly listed in this document, should be considered |
</a></span></h2> |
as internal and subject to change.In previous Pegasus |
<p>The Pegasus bugzilla database documents any defects found in Pegasus |
releases this information was available as a separate PEP. |
and is available through the following link: <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla |
Starting with Pegasus 2.9.0 this information is integrated |
database</a>. Note that bugs committed for Pegasus 2.5.1 have been marked |
into the Pegasus repositoryas </span><small |
with the keyword <font face="Courier New"><b>2.5.1_APPROVED</b></font> so that |
style="font-weight: bold;"><font face="Courier New" |
all bug fixes for this release can be found with the following bug search. |
size="4"><small>pegasus/doc/EnternalInterface.html</small></font></small><span |
changes between Pegasus 2.5.1 and 2.5.2 are documented in bugs with the keyword |
style="font-weight: normal;">.</span></li> |
<b>2.5.2_APPROVED</b>. These are a minor release all of the fixes were documented as |
</b> |
bugs so that even the changes listed in the previous section are listed as bugs. |
<li><b> OpenPegasus SDK Packaging Definition - <span |
The following links provide a list of the bugs for each version</p> |
style="font-weight: normal;">Defines the recommended set |
<p> |
of files for inclusion in the OpenPegasus SDK. Starting |
- Changes for Pegasus 2.5.1 release (bugs Tagged |
with Pegasus release 2.11.0, this document is available in |
2.5.1_APPROVED) |
the Pegasus CVS repository as <big style="font-weight: |
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVEDhttp://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVED"> |
bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>. |
http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVED</a></p> |
In previous Pegasus releases this document was made |
<p> |
available as s separate Pegasus PEP document rather than |
- Changes for Pegasus 2.5.2 release (bugs Tagged |
in the CVS repository.</span> </b></li> |
2.5.2_APPROVED)<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&"> |
<b> </b> <b> |
</a> <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.2_APPROVEDhttp://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.1_APPROVED">http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.5.2_APPROVED</a><br> |
<li> Pegasus Runtime Packaging Definition - <span |
</p> |
style="font-weight: normal;">Defines the recommended set |
<h2><a name="Pegasus Release Control and Version Definition Documentation">Pegasus |
of files for inclusion in this OpenPegasus release. |
Release Control and Version Definition Documentation</a></h2> |
Starting with Pegasus release 2.11.0, this document is |
<p>The Pegasus project is controlled largely through a set of documents |
contained in the CVS repository as <big |
(PEPs) that serve as the definition and review mechanism for new and |
style="font-weight: bold;"><samp>pegasus/doc/RuntimePackaging.html</samp></big>. |
modified Pegasus functionality and for the definition and documentation |
In previous releases this was made available as a seperate |
of releases.</p> |
Pegasus PEP document rather than in the CVS repository. </span> </li> |
<p>Specifically the following PEPs define the characteristics of this |
</b> <b> |
Pegasus release.</p> |
<li>Pegasus Release Notes - <span style="font-weight: |
<ol> |
normal;"> </span>PEP 364 - <span style="font-weight: |
<li> |
normal;"> (This document is located in the approved PEP |
<a href="http://www.openpegasus.org/pp/uploads/40/8568/PEP209_ExternalInterface2.5.htm">PEP 209</a> - OpenPegaus 2.5 External Interfaces.<br> |
repository and the OpenPegasus source tree root directory |
</li> |
(<big style="font-weight: bold;"><span style="font-family: |
<li> |
monospace;">pegasus/ReleaseNotes.htm</span></big>)</span></li> |
<a href="http://www.openpegasus.org/pp/uploads/40/10083/PEP237_RecommendedReleaseOptions.htm">PEP 237</a> - OpenPegasus Build and Configuration |
</b> |
Option for Selected |
</ul> |
Platforms</li> |
<h2><b><a name="General Documentation">General Documentation</a></b></h2> |
<li>PEP 249 - Pegasus Release Notes (This document located in the PEP |
<p><b>The following documentation is available for the this |
repository and the Pegasus source tree root directory)</li> |
Pegasus release:</b></p> |
<li> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/9825/PEP242_RuntimePackaging2.5.1.htm">PEP 242</a> - Pegasus Runtime Packaging Definition<br> |
|
</li> |
|
<li> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/9820/PEP243_SDKFile2.5.1.htm">PEP 243</a> - OpenPegasus SDK Packaging Definition</li> |
|
<li>PEP 251 - Pegasus readme.txt for (Located in PEP repository |
|
and also in the Pegasus |
|
source |
|
tree root directory).</li> |
|
<li> |
|
<a href="http://www.openpegasus.org/pp/uploads/40/10067/PEP239_2_5_1ReleaseDefinition.htm">PEP 239</a> - OpenPegasus Release Definition - This PEP is used |
|
throughout the development of this version as the control point for |
|
functionality that will go into the release and points to all of the |
|
PEPs that represent the Pegasus 2.5 functionality changes. (as of |
|
this document verion of PEP 230, PEP 180 is listed as draft status)</li> |
|
</ol> |
|
<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> - A |
<b> |
combination of help generally available with the -h option for each |
<li class="MsoNormal" style="color: black;"><b>Utilities</b> - |
command and HTML documentation for most of the tools.<o:p></o:p></li> |
</li> |
<li class="MsoNormal" style="color: black;"><b>API and usage |
</b>A combination of help generally available with the --help |
documentation</b> - See the header files and the HTML API |
option for each command and HTML documentation for most of the |
documentation that is on the web site. The best API usage documentation |
tools.<o:p></o:p> <b> |
is the existing utilities and test programs and the examples in the API |
<li class="MsoNormal" style="color: black;"><b>API and |
documentation. In particular the Common/tests unit tests contain |
usage documentation</b> - </li> |
extensive examples of the use of the Common APIs.</li> |
</b>See the header files and the HTML API documentation |
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
that is on the web site. The best API usage documentation is the |
Providers </b>- Readme.html in the Pegasus Root Directory, API |
existing utilities and test programs and the examples in the API |
documentation, and documentation from the Pegasus Technical Workshop |
documentation. In particular the Common/tests unit tests |
which is available on the Pegasus web site.</li> |
contain extensive examples of the use of the Common APIs. <b> |
<li class="MsoNormal" style="color: black;"><b>Building and Debugging |
<li class="MsoNormal" style="color: black;"><b>Building and |
Clients</b> - API documentation and the documentation on the Pegasus |
Debugging Providers </b>- </li> |
Technical Workshop which is available on the Pegasus web site.</li> |
</b>Readme.html in the Pegasus source tree Root Directory, API |
<li class="MsoNormal" style="color: black;"><b>Compiler operation and |
documentation, and documentation from the Pegasus Technical |
commands</b> - compiler help (cimmofl -h)</li> |
Workshop which is available on the Pegasus web site. <b> |
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - The |
<li class="MsoNormal" style="color: black;"><b>Building and |
features of Pegasus that have been installed in this and the previous |
Debugging Clients</b> - </li> |
few versions are defined by Pegasus PEPs that are available on the |
</b>API documentation and the documentation on the Pegasus |
OpenPegasus web site. While these are the original design |
Technical Workshop which is available on the Pegasus web site. <b> |
documents largely and use in the process of defining and approving the |
<li class="MsoNormal" style="color: black;"><b>PEPs</b> - </li> |
overall characteristics of new functionality, they serve as a guide to |
</b>The features of Pegasus that have been installed in this and |
the design and implementation of these features.</li> |
the previous few versions are defined by Pegasus PEPs that are |
|
available on the OpenPegasus web site. While these are the |
|
original design documents largely and use in the process of |
|
defining and approving the overall characteristics of new |
|
functionality, they serve as a guide to the design and |
|
implementation of these features. |
</ul> | </ul> |
|
<hr>Licensed to The Open Group (TOG) under one or more contributor |
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="color: black;"> <o:p></o:p></span></p> |
license agreements. Refer to the OpenPegasusNOTICE.txt file |
<div class="MsoNormal" style="text-align: center;" align="center"><span style="color: black;"> |
distributed with this work for additional information regarding |
<hr align="center" color="#009900" noshade="noshade" size="2" width="100%"> |
copyright ownership. Each contributor licenses this file to you |
<p style="text-align: left;"><i><font size="2">Copyright (c) 2006 EMC |
under the OpenPegasus Open Source License; you may not use this |
Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open |
file except in compliance with the License. |
Group; VERITAS Software Corporation; Intel Corp.</font><br> |
<p>Permission is hereby granted, free of charge, to any person |
<br> |
obtaining a copy of this software and associated documentation |
<font size="1">Permission is hereby granted, free of charge, to any person |
files (the "Software"), to deal in the Software without |
obtaining a copy of this software and associated documentation files (the |
restriction, including without limitation the rights to use, |
"Software"), to deal in the Software without restriction, including without |
copy, modify, merge, publish, distribute, sublicense, and/or |
limitation the rights to use, copy, modify, merge, publish, distribute, |
sell copies of the Software, and to permit persons to whom the |
sublicense, and/or sell copies of the Software, and to permit persons to whom |
Software is furnished to do so, subject to the following |
the Software is furnished to do so, subject to the following conditions:</font><br> |
conditions:</p> |
<font size="2"><br> |
<p>The above copyright notice and this permission notice shall be |
</font><font size="1">THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE |
included in all copies or substantial portions of the Software.</p> |
SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE |
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, |
SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR |
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES |
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, |
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND |
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE |
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT |
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER |
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, |
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, |
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING |
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE |
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR |
SOFTWARE.</font></i></p></span></div> |
OTHER DEALINGS IN THE SOFTWARE.</p> |
<p> </p> |
|
</div> | </div> |
<script language="javascript">postamble();</script> |
|
<script language="javascript">postamble();</script> |
|
<script language="javascript">postamble();</script> |
|
|
|
<script language="javascript">postamble();</script> |
|
</body></html> |
|
|
</body> |
|
</html> |