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