version 1.6, 2005/09/26 15:41:17
|
version 1.11, 2007/08/08 21:20:13
|
|
|
margin:1.0in 1.25in 1.0in 1.25in; | margin:1.0in 1.25in 1.0in 1.25in; |
mso-header-margin:.5in; | mso-header-margin:.5in; |
mso-footer-margin:.5in; | mso-footer-margin:.5in; |
|
|
mso-paper-source:0;} | mso-paper-source:0;} |
div.Section1 | div.Section1 |
{page:Section1;} | {page:Section1;} |
|
|
text-indent:-.25in;} | text-indent:-.25in;} |
@list l4:level7 | @list l4:level7 |
{mso-level-tab-stop:3.5in; | {mso-level-tab-stop:3.5in; |
|
|
mso-level-number-position:left; | mso-level-number-position:left; |
text-indent:-.25in;} | text-indent:-.25in;} |
@list l4:level8 | @list l4:level8 |
|
|
text-indent:-.25in;} | text-indent:-.25in;} |
@list l19 | @list l19 |
{mso-list-id:1902863286; | {mso-list-id:1902863286; |
|
|
mso-list-template-ids:740079056;} | mso-list-template-ids:740079056;} |
@list l19:level1 | @list l19:level1 |
{mso-level-number-format:bullet; | {mso-level-number-format:bullet; |
|
|
</w:WordDocument> | </w:WordDocument> |
</xml><![endif]--> | </xml><![endif]--> |
</head> | </head> |
<body style="" lang="EN-US" link="blue" vlink="blue"> |
<body lang="EN-US" link="blue" vlink="blue"> |
<div class="Section1"> | <div class="Section1"> |
<div class="MsoNormal" style="text-align: center;" align="center"><span | <div class="MsoNormal" style="text-align: center;" align="center"><span |
style="color: black;"> | style="color: black;"> |
|
|
<p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span | <p class="MsoNormal" style="margin-bottom: 0pt; margin-top: 0pt;"><span |
style="color: black;"><br> | style="color: black;"><br> |
<br> | <br> |
<b>PEP #:</b> 230<br> |
<b>PEP #:</b> 305<br> |
</span></p> | </span></p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>Release |
Notes for OpenPegasus 2.5</p> |
Notes for OpenPegasus 2.6.1</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version: </b>1.8</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> <st1:date | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> <st1:date |
year="2004" day="23" month="3">1 April 2005</st1:date></p> |
year="2004" day="23" month="3">3 August 2007<br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Warren |
</st1:date></p> |
Grunbok, Karl Schopmeyer<br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Dave |
|
Sudlik<br> |
</p> | </p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>draft</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>approved</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p> | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p> |
<table class="MsoNormalTable" style="width: 100%;" border="1" |
<table class="MsoNormalTable" style="width: 868px; height: 54px;" |
cellpadding="0" cellspacing="1" width="100%"> |
border="1" cellpadding="0" cellspacing="1"> |
<tbody> | <tbody> |
<tr style=""> | <tr style=""> |
<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;"> |
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 | <p class="MsoNormal" style="text-align: center;" align="center"><b><span |
style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
style="font-family: Arial; color: black;"><o:p>Version </o:p></span></b></p> |
</td> | </td> |
<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;"> |
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 | <p class="MsoNormal" style="text-align: center;" align="center"><b><span |
style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
style="font-family: Arial; color: black;"><o:p>Date </o:p></span></b></p> |
</td> | </td> |
<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;"> |
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 | <p class="MsoNormal" style="text-align: center;" align="center"><b><span |
style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
style="font-family: Arial; color: black;"><o:p> Author</o:p></span></b></p> |
</td> | </td> |
<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;"> |
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 | <p class="MsoNormal" style="text-align: center;" align="center"><b><span |
style="font-family: Arial; color: black;"><o:p> </o:p></span></b></p> |
style="font-family: Arial; color: black;"><o:p> Change Description<br> |
|
</o:p></span></b></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" height="22"> |
<p class="MsoNormal" style="text-align: center;" align="center"><span | <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> | style="font-family: Arial; color: black;"><font size="2"> 1.0</font><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" align="left" height="22"> |
<p class="MsoNormal" style="text-align: center;" align="center"><span | <p class="MsoNormal" style="text-align: center;" align="center"><span |
style="font-family: Arial; color: black;"><o:p> <font size="2">1,April |
style="font-family: Arial; color: black;"><o:p><font size="2"> 3 |
2005<br> |
August 2007<br> |
</font></o:p></span></p> | </font></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" align="left" height="22"> |
<p class="MsoNormal" style="text-align: center;" align="center"><span | <p class="MsoNormal" style="text-align: center;" align="center"><span |
style="font-family: Arial; color: black;"><o:p>Warren Grunbok<br> |
style="font-family: Arial;"><font size="2">Dave Sudlik<br> |
</o:p></span></p> |
</font></span></p> |
</td> | </td> |
<td style="padding: 0.75pt;"> |
<td style="padding: 0.75pt;" height="22"> |
<p class="MsoNormal"><span | <p class="MsoNormal"><span |
style="font-family: Arial; color: black;"><font size="1">Initial |
style="font-family: Arial; color: black;"><font size="2">Initial |
Submission</font><o:p><font size="1"> <br> |
Submission. Updates for 2.6.1 (from 2.6) are highlighted <span |
</font></o:p></span></p> |
style="color: rgb(255, 0, 0);"><span style="color: rgb(153, 51, 153);">in |
</td> |
this color. </span><span style="color: rgb(0, 0, 0);"></span></span></font><o:p><font |
</tr> |
size="2"> </font></o:p></span></p> |
<tr style=""> |
|
<td style="padding: 0.75pt;" align="center"> 1.1</td> |
|
<td style="padding: 0.75pt;" align="center">26, June 2005 <br> |
|
</td> |
|
<td style="padding: 0.75pt;">Warren Grunbok<br> |
|
</td> |
|
<td style="padding: 0.75pt;">revisions based on Comments <br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.2<br> |
|
</td> |
|
<td style="vertical-align: top;">22, July 2005<br> |
|
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">fixed some broken links, added |
|
security notes. <br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.3<br> |
|
</td> |
|
<td style="vertical-align: top;">23, Aug 2005<br> |
|
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">Revisions based on comments<br> |
|
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;">1.4<br> |
<td style="vertical-align: top; text-align: center;">1.1<br> |
</td> | </td> |
<td style="vertical-align: top;">30.Aug 2005<br> |
<td style="vertical-align: top; text-align: center;">8 August 2007<br> |
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">More revisions based on Aug 26 |
|
review in Architecture meeting<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.5<br> |
|
</td> |
|
<td style="vertical-align: top;">12, Sept 2005<br> |
|
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">Minor comment updates from 1.4 |
|
version (balloted version)<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.6<br> |
|
</td> |
|
<td style="vertical-align: top;">14,Sept 2005<br> |
|
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">additional comments from review<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.7<br> |
|
</td> | </td> |
<td style="vertical-align: top;">20, Sept 2005<br> |
<td style="vertical-align: top; text-align: center;">Dave Sudlik<br> |
</td> | </td> |
<td style="vertical-align: top;">Warren Grunbok<br> |
<td style="vertical-align: top;">Updates from review <span |
</td> |
style="color: rgb(255, 0, 0);"></span><br> |
<td style="vertical-align: top;">Added Solaris back in, corrected |
|
Provider security statement, and clarified Solaris support for 2.5<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.8<br> |
|
</td> |
|
<td style="vertical-align: top;">21, Sept 2005<br> |
|
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">Clarified SLP enablement |
|
Paragraph and correction of Power on Linux in platform table<br> |
|
</td> | </td> |
</tr> | </tr> |
</tbody> | </tbody> |
|
|
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><b>Abstract:</b> This document defines the release notes for the 2.5 |
<p><b>Abstract:</b> This document defines the release notes for the |
version of the Pegasus CIM Server. <span class="norm1"><span |
2.6.1 release of the OpenPegasus CIM Server. The purpose of this PEP is |
|
simply 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. <span class="norm1"><span |
style="font-size: 9pt;"><a | style="font-size: 9pt;"><a |
href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35" | href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35" |
target="_self"><br> | target="_self"><br> |
|
|
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><b><o:p><font size="4"> Contents<br> |
<h2 style="margin-bottom: 1px;"><b><o:p><font size="4"> Contents<br> |
</font></o:p></b></p> |
</font></o:p></b></h2> |
<ol> | <ol> |
<li><a href="#Availability_of_this_Release_">Availability of |
<li><a href="#Availability_of_this_Release_">Availability of this |
this Release</a></li> |
Release</a></li> |
<li><a href="#Functionality_of_This_Release">Functionality of |
<li><a href="#Functionality_of_This_Release">OpenPegasus |
This Release</a></li> |
Functionality of This Release</a></li> |
<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship | <li><a href="#Relationship_to_CIMWBEM_Standards">Relationship |
to CIM/WBEM Standards</a></li> | to CIM/WBEM Standards</a></li> |
<li><a href="#Supported%20Platforms">Supported |
<li><a href="#Supported%20Platforms">OpenPegasus Supported Platforms</a></li> |
Platforms</a></li> |
|
<li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance | <li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance |
with DMTF Specifications</a></li> | with DMTF Specifications</a></li> |
<li><a href="#Changes%20in%20This%20Release">Changes |
<li><a href="#PEGASUS%20Bugs">OpenPegasus Bugs</a></li> |
in This Release</a></li> |
|
<li><a href="#PEGASUS%20Bugs">PEGASUS |
|
Bugs</a></li> |
|
<li> <a | <li> <a |
href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">Pegasus |
href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus |
Release Control and Version Definition Documentation</a></li> | Release Control and Version Definition Documentation</a></li> |
<li><a href="#General%20Documentation">General | <li><a href="#General%20Documentation">General |
Documentation</a></li> | Documentation</a></li> |
</ol> | </ol> |
<h2><a name="Availability_of_this_Release_"></a><span |
<h2><span style="color: black;">Availability |
style="color: black;"><a name="Availability_of_this_Release"></a>Availability |
|
of this Release</span></h2> | of this Release</span></h2> |
<p>This release is available in a number of forms including:</p> | <p>This release is available in a number of forms including:</p> |
<ul> | <ul> |
<li>Source release in both ZIP and TAR formats. These can be |
<li><b>Source release</b> in both ZIP (and ZIP EXE) and TAR formats. |
|
These can be |
downloaded from the <span class="SpellE">OpenPegasus</span> Web | downloaded from the <span class="SpellE">OpenPegasus</span> Web |
site at <a | site at <a |
href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a></li> |
href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li> |
<li>OpenPegasus 2.5 binaries are available for Red Hat Enterprise |
<li><b>OpenPegasus binary and source RPMs</b> on the |
Linux 3.0 and 4.2 and SUSE LINUX Enterprise Server 9.0. A Source RPM is |
OpenPegasus web site.. The source RPM is available on the |
also available that can be used to build binaries for most |
OpenPegasus web site that can be used to build binaries for most |
LSB-compliant RPM-based Linux distributions and versions.</li> | LSB-compliant RPM-based Linux distributions and versions.</li> |
<li>The Pegasus CVS. The CVS tags representing this release and |
<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 | subsequent snapshots that are made available in the Pegasus CVS are |
defined on the OpenPegasus CVS repository web page (see the <a | defined on the OpenPegasus CVS repository web page (see the <a |
href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus | href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus |
|
|
href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release | href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release |
snapshots page</a>.</li> | snapshots page</a>.</li> |
</ul> | </ul> |
<>The instructions for acquiring the released code are on the <a |
<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 | href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus |
WEB site</a>. | WEB site</a>. |
Installation instructions are part of the README in the root of the | Installation instructions are part of the README in the root of the |
Pegasus source | Pegasus source |
tree.<br> |
tree.</p> |
<br> |
</div> |
<span class="norm">Instructions for building the Linux RPMs: <span |
<div class="Section1"> |
style="color: rgb(255, 0, 0);"></span><br> |
<h2><span style="color: black;">OpenPegasus Functionality for This |
</span></> |
Release</span></h2> |
<ol> |
Pegasus overall status by release is defined by a <a |
<li><span class="norm"><span style="font-weight: bold;">Download</span> |
href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB |
tog-pegasus-2.5.0-1.src.rpm. </span></li> |
Page</a> that is available on the OpenPegasus web site . That web |
<li><span class="norm"><span style="font-weight: bold;">rpm</span> |
page shows the Pegasus users and developers the status of the various |
-ih tog-pegasus-2.5.0-1.src.rpm </span></li> |
features found in Pegasus using a simple color coded key (white, red, |
<li> |
yellow, green) and a description of each feature. |
<p style="margin-top: 0pt; margin-bottom: 0pt; font-weight: bold;"><span |
<p><span style="color: rgb(153, 51, 153);">Pegasus 2.6.1 is a "point" |
class="norm">Build |
release, extending Pegasus 2.6 in |
the rpms:</span></p> |
selected areas. Normally an OpenPegasus "point" release does not |
</li> |
contain major new pieces of functionality, but in this case one new PEP |
</ol> |
was added for IPv6 support, the description of which has been added to |
<span class="norm"></span> |
these Release Notes.</span><br> |
<table |
</p> |
style="margin-left: auto; margin-right: auto; text-align: left; width: 712px; height: 116px;" |
<p>The major areas of development for this release were as |
border="1" cellpadding="2" cellspacing="2"> |
follows. For more information access the documented PEP:</p> |
<tbody> |
<p style="margin-top: 0pt; margin-bottom: 0pt;" align="left"> |
<tr> |
Table of Major Changes for this Release</p> |
<td |
<table style="font-family: Arial;" bordercolordark="#666666" |
style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Distro</td> |
bordercolorlight="#cccccc" border="1" cellspacing="1"> |
<td |
|
style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Command<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top; text-align: center;">RHEL3<br> |
|
</td> |
|
<td style="vertical-align: top; text-align: center;"><span |
|
class="norm">rpmbuild -bb /usr/src/redhat/SPECS/tog-pegasus- |
|
2.5.0-1.spec</span></td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top; text-align: center;">RHEL4<br> |
|
</td> |
|
<td style="vertical-align: top; text-align: center;"><span |
|
class="norm">rpmbuild -bb /usr/src/redhat/SPECS/tog-pegasus- |
|
2.5.0-1.spec</span></td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top; text-align: center;">SLES 9 <br> |
|
</td> |
|
<td style="vertical-align: top; text-align: center;"><span |
|
class="norm"> rpmbuild -bb /usr/src/packages/SPECS/tog-pegasus- |
|
2.5.0-1.spe</span></td> |
|
</tr> |
|
</tbody> |
|
</table> |
|
<span class="norm"></span> |
|
<ol start="4"> |
|
<span class="norm"><br> |
|
</span><li style="font-weight: bold;"><span class="norm">After |
|
the build the rpms will be in the |
|
following locations:</span></li> |
|
<span class="norm"></span> |
|
<table style="width: 100%; text-align: left;" border="1" |
|
cellpadding="2" cellspacing="2"> |
|
<tbody> | <tbody> |
<tr> |
<tr align="center"> |
<td |
<th bgcolor="#e0e8ef">PEP</th> |
style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Distro<br> |
<th bgcolor="#e0e8ef">Description</th> |
</td> |
<th bgcolor="#e0e8ef">Posted PEP<br> |
<td |
Version</th> |
style="vertical-align: top; text-align: center; background-color: rgb(204, 204, 204);">Location |
</tr> |
of RPMs after the build is complete<br> |
<tr align="center"> |
</td> |
<td style="color: rgb(153, 51, 153);">291</td> |
</tr> |
<td style="color: rgb(153, 51, 153);" align="left">OpenPegasus |
<tr> |
Support for IPv6: Stage 1<br> |
<td style="vertical-align: top; text-align: center;">RHEL3<br> |
|
</td> |
|
<td style="vertical-align: top; text-align: center;"><span |
|
class="norm">/usr/src/redhat/RPMS/[arch]/tog-pegasus- |
|
2.5.0-1.[arch].rpm |
|
/usr/src/redhat/RPMS/[arch]/tog-pegasus-sdk- 2.5.0-1.[arch].rpm.<span |
|
style="font-family: "times new roman";"></span><span |
|
style="font-family: "times new roman";"></span></span><span |
|
class="norm"> </span></td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top; text-align: center;">RHEL4<br> |
|
</td> | </td> |
<td style="vertical-align: top; text-align: center;"><span |
<td style="color: rgb(0, 153, 0);"> <a |
class="norm">/usr/src/redhat/RPMS/[arch]/tog-pegasus- |
href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">1.2</a> |
2.5.0-1.[arch].rpm |
|
/usr/src/redhat/RPMS/[arch]/tog-pegasus-sdk- 2.5.0-1.[arch].rpm.</span></td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top; text-align: center;">SLES9<br> |
|
</td> | </td> |
<td style="vertical-align: top; text-align: center;"><span |
|
class="norm">/usr/src/packages/RPMS/[arch]/tog-pegasus- |
|
2.5.0-1.[arch].rpm |
|
/usr/src/packages/RPMS/[arch]/tog-pegasus-sdk- 2.5.01-.[arch].rpm.</span></td> |
|
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<span class="norm"></span><span class="norm"></span> |
<p>The status of several components of Pegasus functionality change |
</ol> |
status between Pegasus versions. <span class="norm"><a |
<span class="norm"> |
name="comtag_116">Features that have changed status can be identified |
</span><span class="norm"></span> |
by a change in color from the previous release to this release</a></span> |
<h2><a name="Functionality_of_This_Release"></a><span |
on the <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature |
style="color: black;">Functionality of This Release</span></h2> |
Status WEB Page</a>.</p> |
New for the Pegasus 2.5 release is a Feature Maturity Dashboard. |
<p>Finally, a significant number of internal changes and corrections |
This document shows the Pegasus users and developers the maturity of |
were made under the control of the Pegasus bugzilla bug system. See the |
the various features found in Pegasus using a simple color coded |
bug section below for more information.<br> |
key. That document can be found here: <a |
|
href="http://www.openpegasus.org/page.tpl?ggid=799">Feature |
|
Maturity Link</a><br> |
|
<span style="font-family: "times new roman";"><br> |
|
</span>The overall level of functionality in the Pegasus environment |
|
effective with |
|
this release is as follows: |
|
<h3><b>CIM Server Functionality</b></h3> |
|
<p>The following paragraphs list the functions in this release. |
|
All functions are considered community tested and operational unless |
|
specifically noted below. Features that are marked alpha or beta are |
|
not generally of the quality or completeness for production |
|
usage. Interfaces that are part of the Pegasus public |
|
interface definitions but that the Pegasus team feels may change are |
|
marked experimental. In many cases these features and interfaces |
|
are conditionally compiled with special environment variables. <a |
|
href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502"><span |
|
style="color: rgb(255, 0, 0);"><span style="color: rgb(51, 102, 255);"><span |
|
style="text-decoration: underline;">PEP 200</span> </span></span></a> |
|
provides more detailed information on how to enable |
|
functionality that is conditionally compiled in this release.</p> |
|
<blockquote> |
|
<h4><b>CIM Operations over HTTP support</b></h4> |
|
<ol> |
|
<li>Class Operations (<span class="SpellE">getClass</span>, <span |
|
class="SpellE">deleteClass</span>, <span class="SpellE">modifyClass</span>, |
|
<span class="SpellE">enumerateClass</span>, <span class="SpellE">enumerateClassNames</span>)</li> |
|
<li>Qualifier Operations (getQualifier, setQualifier, |
|
deleteQualifier) </li> |
|
<li>Instance Operations (<span class="SpellE">getInstance</span>, <span |
|
class="SpellE">deleteInstance</span>, <span class="SpellE">modifyInstance</span>, |
|
<span class="SpellE">enumerateInstance</span>, <span |
|
class="SpellE">enumerateInstanceNames</span>, <span class="SpellE">getProperty</span>, |
|
<span class="SpellE">setProperty</span>)</li> |
|
<li>Association Operations (references, <span class="SpellE">referencenames</span>, |
|
<span class="SpellE">associators</span>, <span class="SpellE">associatornames)</span></li> |
|
<li>Methods Operations (invokeMethod)</li> |
|
<li>Query operation - Support for ExecQuery was added in 2.4 with |
|
WQL as query language and is defined in PEP 119. This feature is |
|
considered at alpha quality because it has only been contributor |
|
tested. Additional tests have been added in 2.5 for ExecQuery.<br> |
|
</li> |
|
</ol> |
|
</blockquote> |
|
</div> |
|
<blockquote> |
|
<h4><b>Indications</b></h4> |
|
<ul> |
|
<li>Process indications - Process indications are operational in |
|
the |
|
Server. This includes support |
|
for subscriptions, filters, and indication handlers, the provider API |
|
for |
|
indications and the CIMXML indication handler.</li> |
|
<li>Lifecycle indications - With the support for embedded objects, |
|
lifecycle indications (ie. those |
|
classes of indications derived from CIM_ClassIndication and |
|
CIM_InstIndication) can now be created. Pegasus 2.5 provides some |
|
enablement for the generation of lifecycle indications. For more |
|
details, refer to |
|
<src/Unsupported/LifecycleIndicationProvider/readme.LifecycleIndications.htm>.</li> |
|
</ul> |
|
<h4><b>Indication Listener</b></h4> |
|
<p class="MsoNormal">The generic components for a CIM Listener and a |
|
listener API are operational. This includes the functions for |
|
HTTP, XML indication input and response, and consumers of indications. |
|
This code can be used to define a separate listener package and is used |
|
as an indication listener in the Pegasus server. <br> |
|
</p> | </p> |
<p class="MsoNormal"><br> |
<h3 style="color: rgb(153, 51, 153);">IPv6 Support<br> |
<font style="color: rgb(0, 0, 0);" color="#330099">Pegasus 2.5 |
</h3> |
includes a new standalone listener that is separate |
<p style="color: rgb(153, 51, 153);">IPv6 is short for "Internet |
from the current standalone CIMListener and the ExportServer listener |
Protocol |
in the CIM server. |
Version 6". IPv6 is the "next generation" protocol designed by the IETF |
The use model that this listener fits is the following: |
to replace the current version Internet Protocol, IP Version 4 |
<ul> |
("IPv4"). IPv6 Support for OpenPegasus is documented in <a |
<li><span class="norm"></span> The listener may be packaged as |
href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">PEP |
part of the CIMOM or it may be packaged independently as part of |
291</a>.<br> |
another application. </li> |
|
<li><span class="norm"></span> Consumers |
|
are developed independently of the listener and may be shipped with the |
|
listener or added to an installed listener at a future time. </li> |
|
</ul> |
|
</font> </p> |
|
<p><span style="color: rgb(0, 0, 0);" class="norm"></span><span |
|
style="color: rgb(0, 0, 0);"> </span><font color="#330099"><span |
|
style="color: rgb(0, 0, 0);">This |
|
new "Dynamic Listener" provides a solution for the above use model. It |
|
is essentially a lightweight, pluggable listener that |
|
provides a small set of management features. The DynamicListener can be |
|
run inside a daemon or a service. It is easily configurable and |
|
bypasses traditional registration procedures. See <a |
|
href="http://www.openpegasus.org/pp/protected/upreviews/20/1303/PEP195_CIMListenerEnhancementsv1_6.htm"><span |
|
style="color: rgb(51, 51, 255); text-decoration: underline;">PEP 195</span></a> <span |
|
style="color: rgb(255, 0, 0);"> </span>for |
|
details.</span> </font></p> |
|
<h4>Object Normalization</h4> |
|
The Object Normalizer is an entity introduced in Pegasus 2.4 that |
|
ensures |
|
objects delivered from providers are complete and accurate. Two major |
|
issues were identified with the initial implementation: 1) the Object |
|
Normalizer drops instances it considers bad, and 2) the Object |
|
Normalizer code slows performance. These issues are now addressed by |
|
moving the Object Normalizer from the Dispatcher to the Response |
|
Handler (or equivalent) and optimizing the existing implementation. The |
|
move allows errors to be reported to the provider at the point of |
|
delivery and ensures that only a single copy is made to preserve the |
|
CIMOM/provider boundary.<br> |
|
Two new configuration properties were added to control object |
|
normalization.<br> |
|
<ol> |
|
<li>enableNormalization (true|false) - Enables or disables object |
|
normalization for provider objects.</li> |
|
<li>excludeModulesFromNormalization (colon delimited list of |
|
provider modules) - List the provider modules by name (as specified in |
|
PG_ProviderModule.Name) to exclude from normalization. Keep in mind |
|
that all objects managed by all providers will be excluded from |
|
normalization if its module name appears in this list.<br> |
|
</li> |
|
</ol> |
|
<br> |
|
<h4>Embedded Object support</h4> |
|
Pegasus 2.5 now provides embedded object support. The proposed solution |
|
is restricted to the following:<br> |
|
The only representation for embedded objects supported by this |
|
PEP is CIM-XML. <br> |
|
CIMObject is implemented as a new CIMValue type. This type will be used |
|
internally to represent embedded objects. When externalized (via |
|
CIM-XML) these objects will be converted to strings representing valid |
|
INSTANCE or CLASS elements, in accordance with the CIM Infrastructure |
|
Specification. Embedded instances will also carry the |
|
EmbeddedObject attribute with |
|
the value "object", as specified by CR Interop-00217.001. <br> |
|
<br> |
|
<p class="MsoNormal"> </p> |
|
</blockquote> |
|
<div class="Section1"> |
|
<blockquote> |
|
<h4><b>Query Language</b></h4> |
|
<p>The query language today is based on WQL and is implemented and |
|
used for filters and in 2.4 for execQuery. <br> |
|
</p> | </p> |
<p>CQL Stage 1 has been included for Pegasus 2.5. PEPs 138, |
<p style="color: rgb(153, 51, 153);">The IPv6 support in OpenPegasus is |
193, 205 combine to describe the function submitted.<br> |
controlled by the PEGASUS_ENABLE_IPV6 build variable. Setting this to |
|
'true' before building OpenPegasus will enable the IPv6 support. In |
|
2.6.1 this variable will default to 'false' to omit the IPv6 support.<br> |
</p> | </p> |
<h4><b>Schema Repository</b></h4> |
<p style="color: rgb(153, 51, 153);">The following subsections provide |
<span class="norm"></span>By default, Pegasus uses an XML-based |
some information on IPv6 support for the Linux and Windows platforms. |
schema repository. A binary encoding option is also available.<span |
Note that in the 2.6.1 release there is no automatic run-time detection |
style="font-family: "times new roman";"><br> |
of IPv6 support on a platform by OpenPegasus. If you build with |
<br> |
PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you will |
</span>To use the binary encoding feature a new configuration |
get a build failure (missing header files), a run-time bind() failure, |
properties was |
or possibly some other failure. This applies to both the CIM Server and |
added:<br> |
Listener components. For more information on IPv6 support for your |
<p> enableBinaryRepository (true|false) - Enables |
specific platform, refer to the documentation for that platform.<br> |
or |
|
disables binary repository.<br> |
|
</p> | </p> |
<div style="margin-left: 40px;"> In addition to the binary |
<p style="color: rgb(153, 51, 153);">All OpenPegasus externals that |
repository, the compressed repository |
support either a hostname or an IP address as input have been updated |
functionality has |
to allow an IPv6 address to be specified. If the required input is just |
been added as a build time conditional compile. It defaults to not |
an IP address (eg. no optional or required port number), then the IPv6 |
support |
address must be specified without brackets. For example, the |
compression. When enabled the zlib library, used for the compression |
OpenPegasus osinfo client (which returns information about the OS |
algorithims, must be installed on the build and target systems. With |
running on a host system) takes separate host and port options. In this |
compression enabled records are always written compressed but both |
case a host with an IPv6-configured network interface would be |
compressed |
specified as:<br> |
and non-compressed records can be read allowing an easy migration path.<br> |
|
<br> |
|
<span style="color: rgb(51, 102, 255);">Note: </span><span |
|
class="norm"></span><span style="color: rgb(51, 102, 255);">Note: |
|
Users may experience an incompatibility moving a binary repository from |
|
Pegasus 2.4 to 2.5. In Pegasus 2.5, measures have been taken to improve |
|
the ability to maintain compatibility with subsequent releases. (See |
|
bugzilla 3642 for details.)</span><font><font color="RED"> </font></font><span |
|
style="color: rgb(51, 102, 255);">See bugzilla 3642 for details.<br> |
|
</span></div> |
|
<h4><b><b>Compressed Repository</b></b></h4> |
|
<div style="margin-left: 40px;"><span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);" color="RED">A compressed repository |
|
feature has been added for |
|
pegasus 2.5 that compresses the repository written to disk. This allows |
|
the |
|
repository to be as much as 50% smaller on disk. It uses an external |
|
compression library (zlib) and has been tested with zlib 1.2.2. This |
|
feature is |
|
documented in PEP 214 and also in a Readme |
|
(readme.compressed_repository). It is |
|
considered experimental today because it is not in the automated tests. |
|
Note |
|
that the tests for this feature are in the test suite but not |
|
activiated for |
|
automatic tests.</font><br> |
|
<span style="color: rgb(51, 102, 255);"><br> |
|
</span><font><font color="RED"> </font></font></div> |
|
<p> </p> |
|
<h4><b>Instance Repository</b></h4> |
|
<p><span class="norm"></span><font style="color: rgb(0, 0, 0);">The |
|
Pegasus schema repository may also be configured to hold instance |
|
data. </font><span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);">Although instances may be place in the |
|
repository |
|
it was </font><font style="color: rgb(0, 0, 0);">not designed as a |
|
high volume data store</font><span style="color: rgb(0, 0, 0);">. </span><br> |
|
<br> |
|
</p> | </p> |
<h4><b><b>Security Considerations<br> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);">osinfo -h |
</b></b></h4> |
3ffe:1:2:1 -p 5988<br> |
<font style="color: rgb(0, 0, 0);" color="RED">OpenPegasus 2.5 (and |
|
prior) contains several mechanisms to perform authorization, but none |
|
of these authorization checks are performed by default. |
|
By registering any provider which fails to do appropriate authorization |
|
checks, the consequences may include information leakage, data |
|
corruption, or unintended elevation of privilege. Please ensure that |
|
one of the following mechanisms is used to ensure appropriate access to |
|
your systems and data:<br> |
|
1. Only install/register providers which perform authorization |
|
appropriate for your environment.<br> |
|
</font> |
|
<div style="margin-left: 40px;"><font style="color: rgb(0, 0, 0);" |
|
color="RED">a. For providers, this may include registering to |
|
'Run-as-requestor' (not available prior to Pegasus 2.5) and/or |
|
performing authorization checks within the provider.<br> |
|
b. For administrators, ensure that the providers you have registered in |
|
your environment have performed sufficient authorization checks. Also, |
|
monitor announcements of security defects in those providers and follow |
|
the recommendations in those announcements as soon as possible. <br> |
|
c. For distributors of Pegasus or providers, ensure that the providers |
|
you are shipping have performed appropriate authorization checks, and |
|
relay announcements of discovered security defects to your users.</font><br> |
|
</div> | </div> |
<font style="color: rgb(0, 0, 0);" color="RED">2. Restrict users with |
<p style="color: rgb(153, 51, 153);">But the cimcli command, which |
access to Pegasus to a specific authorized user group of trusted |
takes |
individuals.<br> |
an optional "location" option including an optional port number, |
3. Namespace authorization is also available.<br> |
requires the IPv6 address to be delimited with brackets, for example:<br> |
<br> |
|
</font><span class="norm">For administration issues please refer to |
|
the SSL Admin Guide found at: </span>pegasus/doc/PegasusSSLGuidelines.htm<br> |
|
<h4><b>Server Security</b></h4> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Basic Authentication |
|
(Note that Digest based security is not implemented)</li> |
|
<li class="MsoNormal" style="color: black;">PAM authentication <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">SSL support - SSL is |
|
implemented in Pegasus using the <span class="SpellE">OpenSSL</span> |
|
libraries. Pegasus does not provide the <span class="SpellE">OpenSSL</span> |
|
libraries but SSL can be used on any platform supported by <span |
|
class="SpellE">OpenSSL</span>. Minimum level known to work |
|
is 0.9.6c . This release of Pegasus was tested with |
|
0.9.6k. See <a |
|
href="http://www.openpegasus.org/pp/uploads/40/Application%20Data/Microsoft/Word/www.openssl.org">openssl.org</a> |
|
for <span class="SpellE">OpenSSL</span> release information<o:p>.</o:p></li> |
|
<li class="MsoNormal" style="color: black;">SSL levels<br> |
|
<span class="norm"></span><font style="color: rgb(0, 0, 0);">SSLv3 |
|
and TLSv1 by default. SSLv2 is |
|
disabled by default and only enabled by a compile time option</font>. |
|
See<a |
|
href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502"> |
|
PEP 200</a> for details on |
|
configuration.<br> |
|
</li> |
|
</ol> |
|
<b> </b> |
|
<h4><b>Client Security</b><span style="font-family: times new roman;"><span |
|
style="font-style: italic;"><span style="font-weight: bold;"></span></span></span></h4> |
|
Certificate management |
|
and User-based certificate authentication . A new control provider and |
|
CLI for certificate management tasks. It expands upon the existing SSL |
|
client verification support by providing a robust solution to managing |
|
client certificates and certificate revocation lists via standard CIM |
|
operations. It allows certificates to be associated with particular |
|
system users for enhanced authorization capabilities.<br> |
|
<span class="norm"></span><font style="color: rgb(0, 0, 0);">CN/ Host |
|
name checks are not performed as a function of SSL or client libraries |
|
and are the responsibility of the client to implement on their |
|
own. See the SSL guide found in the /pegasus/doc directory for |
|
more details on client security.</font><br> |
|
Note: <span class="norm"><font><font color="RED"><span |
|
style="color: rgb(0, 0, 0);">WBEM clients are responsible for SSL |
|
certificate verification using Pegasus and/or SSL libraries as |
|
appropriate. Consequences of not doing so include leakage of |
|
authentication credentials to unauthorized parties.</span> </font></font></span> |
|
<h4><b>Platform Management Functions</b></h4> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Configuration through |
|
the defined configuration parameters (cimconfig) and server command |
|
line options.<span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);" color="RED"> NOTE: When installed |
|
as a service on Windows, setting the run-time config option |
|
enableAuthentication to true can result in improper operation of the |
|
SLP |
|
provider and other providers. In order to circumvent this defect, an |
|
Administrator should change the user that the service runs under from |
|
the Local |
|
System user to a local, privileged user (e.g. Administrator). |
|
See bugzilla 4142 for details.</font> <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">Daemon/service |
|
operation of the Pegasus CIM Server on all supported platforms<o:p> |
|
with the exception of HP OpenVMS.<br> |
|
</o:p></li> |
|
<li class="MsoNormal" style="color: black;">Operation statistics |
|
capture using the <span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);">CIM_StatisticalData </font>classes in |
|
the DMTF Interop model. This |
|
function is considered alpha quality and conditionally compiled. <br> |
|
</li> |
|
<li class="MsoNormal" style="color: black;">Multiple |
|
pluggable provider managers. Provider managers are provided for |
|
the Pegasus C++ provider interface, the CMPI C provider interface and |
|
an alpha quality Java provider interface (JMPI).</li> |
|
<li class="MsoNormal" style="color: black;">Platform Globalization |
|
- Pegasus includes support for unicode data transfers and includes a |
|
mechanism for message support in multiple languages using the open |
|
source ICU libraries (<a href="http://oss.software.ibm.com/icu/">http://oss.software.ibm.com/icu/</a>). |
|
Note that this is still marked experimental.</li> |
|
<li class="MsoNormal" style="color: black;">Out-of-process |
|
providers (Experimental) - See PEP 072 for more information on use of |
|
this feature </li> |
|
<li class="MsoNormal" style="color: black;">Shared class namespaces |
|
(Experimental) - See PEP 129 for more information on use of this feature</li> |
|
<li class="MsoNormal" style="color: black;">Remote providers for |
|
the CMPI provider interface (Experimental) - See PEP 130 for more |
|
information on use of this feature</li> |
|
</ol> |
|
<h4><b>SLP Discovery</b></h4> |
|
<p>SLP support is included but is conditionally compiled in or out on |
|
a platform basis. <a |
|
href="http://www.openpegasus.org/pp/uploads/40/8502/PEP200_RecommendedReleaseOptions.htm"> |
|
PEP 200</a> describes the use of proper environment variable use to |
|
enable or disable this code. PEGASUS_DISABLE_SLP and |
|
PEGASUS_ENABLE_SLP are the environment variables that control inclusion |
|
of this feature. Once compiled, SLP |
|
support is enabled with the slp configuration parameter (slp=true). SLP |
|
support includes an SLP service agent in the Pegasus CIM sever and |
|
generates SLP advertisements compatible with the DMTF slp template |
|
specification. The SLP support also includes extensions to the |
|
CIM Client libraries to execute SLP User Agent requests and analyze the |
|
results (note that these interfaces are not yet part of the Pegasus |
|
public SDK).<br> |
|
Note: Pegasus on Windows is built with SLP support on by default and to |
|
exclude it from the build, then PEGASUS_DISABLE_SLP must be set.<br> |
|
</p> | </p> |
<h4>Provider Managers</h4> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);">cimcli ns -l |
<p>Pegasus is designed to support multiple Provider Managers to allow |
[3ffe:1:2:1]</div> |
multiple provider interfaces to the CIMOM. The two default |
<p style="color: rgb(153, 51, 153);">or<br> |
provider managers are the Pegasus C++ Interface and Common |
|
Manageability Programming Interface (CMPI) Interface.<br> |
|
</p> | </p> |
<blockquote> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);">cimcli ns -l |
<h5><b style="">CMPI C interface Provider Manager<o:p></o:p></b></h5> |
[3ffe:1:2:1]:5989<br> |
<span style="font-family: "times new roman";">Pegasus 2.5 includes |
|
a provider manager for the CMPI C interfaces. This C interface is the |
|
result of a project by the IBM SBLIM team (see |
|
http://sblim.sourceforge.net) and is written to the Common |
|
Manageability Programming Interface, which is an OpenGroup standard. |
|
The CMPI |
|
specification is available at: |
|
http://www.opengroup.org/bookstore/catalog/c051.htm. This provides a |
|
standardized C level interface for creating providers that can be |
|
registered with the Pegasus CIM Server in the same manner as the |
|
current C++ providers. </span><span |
|
style="font-family: "times new roman";"><span class="norm"></span></span>The |
|
ability for CMPI providers to do user authorization is now available in |
|
Pegasus 2.5.<br> |
|
<span style="font-family: "times new roman";"> <br> |
|
Information on writing providers with the CMPI interface is available |
|
in the specification today (see above) and in the following documents |
|
(http://sblim.sourceforge.net/whitepaper.html and |
|
http://sblim.sourceforge.net/presentations.html) and readme.cmpi in the |
|
Pegasus source root directory.</span><br> |
|
<h5>JMPI Java Interface Provider Manager</h5> |
|
<p>Pegasus includes an experimental provider manager for Java |
|
provider interfaces based on the SNIA provider interface |
|
definitions. This provider manager is considered alpha |
|
quality and is not compiled in the default build. See |
|
readme.jmpi in the Pegasus source root directory for more information.</p> |
|
</blockquote> |
|
</blockquote> |
|
<h3><b> Providers</b></h3> |
|
<div style="margin-left: 40px;">New for 2.5 is the ability of Providers |
|
to run out of process at |
|
request user- level and running CMPI providers remotely or out of |
|
process space.<br> |
|
<br> |
|
<span class="norm"></span>Administrators should check the providers to |
|
ensure that the provider vendor |
|
has made use of available authorization capability.<br> |
|
</div> | </div> |
<p style="margin-left: 40px;">There are a number of providers available |
<br style="color: rgb(153, 51, 153);"> |
in the Pegasus release. |
<span style="color: rgb(153, 51, 153);">For more information on |
This includes providers in the following categories:</p> |
specifying |
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;"> |
IPv6 addresses, refer to </span><a style="color: rgb(153, 51, 153);" |
<h4>Pegasus Internal Providers</h4> |
href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP Version |
<p>Pegasus provides a set of "internal" providers that have direct |
6 Addressing Architecture</a><span style="color: rgb(153, 51, 153);"> |
access to the CIMOM for information and provide information and |
and </span><a style="color: rgb(153, 51, 153);" |
services to support the CIMOM and its administration. The |
href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 - Format for |
providers in this category are mostly defined in the directory |
Literal IPv6 Addresses in URL's</a><span |
src/pegasus/controlproviders and include support for the following |
style="color: rgb(153, 51, 153);">.</span><br |
classes:</p> |
style="color: rgb(153, 51, 153);"> |
<ul> |
<h4 style="color: rgb(153, 51, 153);">IPv6 on Linux<br> |
<li>DMTF Interop classes including __Namespace, <span |
</h4> |
class="SpellE">CIM_Namespace</span>, <span class="SpellE">CIM_ObjectManager</span>, |
<p style="color: rgb(153, 51, 153);">Modern Linux distributions already |
<span class="SpellE">CIM_CommunicationMechanism, and |
contain IPv6-ready kernels, the |
CIMOMStatistics.</span></li> |
IPv6 capability is generally compiled as a module, but it's possible |
</ul> |
that this module is not loaded automatically on startup.</p> |
<h4><span class="SpellE">CMPI Remote</span></h4> |
<p style="color: rgb(153, 51, 153);">Note: |
<h4><span class="SpellE"></span></h4> |
you shouldn't anymore use kernel series 2.2.x, because it's not |
<span class="SpellE">Pegasus includes an experimental support for |
IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no |
running CMPI providers to be run on remote systems without the need for |
longer improved according to definitions in latest RFCs. It's recommend |
an extra CIMOM. It uses a special proxying provider to relay requests |
to use series 2.6.x now.<br> |
to a remote location using so-called communication layers. The remote |
|
side has to start a CMPIRDaemon process, which accepts remote requests |
|
and passes them on to CMPI style providers.<br> |
|
</span><span class="SpellE"></span><span class="SpellE"><br> |
|
</span> |
|
<h4><b>Generic Providers</b></h4> |
|
<p>Generic <span class="SpellE">OperatingSystem</span> provider. See |
|
the |
|
directory <span class="SpellE">src</span>/Providers/generic.</p> |
|
<h4><b>Test/Sample Providers</b></h4> |
|
<p>See the directories <span class="SpellE">src/Providers/TestProviders</span> |
|
and <span class="SpellE">src</span>/Providers/Sample for more |
|
information about test and |
|
sample providers.</p> |
|
<h4><b>Managed System Providers</b></h4> |
|
<p><span class="SpellE">ComputerSystem</span>, <span class="SpellE">DNSAdmin</span>, |
|
<span class="SpellE">DNSService</span>, Operating System, Process, |
|
Processor. For |
|
more information on these providers see the documentation for each |
|
provider in |
|
the directory <span class="SpellE">src/Providers/ManagedSystem</span></p> |
|
<h4><span class="SpellE">Server Statistics<br> |
|
</span></h4> |
|
CIM Server statistics, based on the DMTF 'CIM_StatisticalData' class, |
|
are implemented in this release. The statistics gathering is disabled |
|
by default. It may be enabled or disabled by performing a |
|
ModifyInstance operation on the singleton 'CIM_ObjectManager' instance |
|
in the 'PG_InterOp' namespace to set the GatherStatisticalData property |
|
to 'true' or 'false'. This property setting is persistent across CIM |
|
Server restarts. A statistics display test tool, cimperf, is available |
|
from the Pegasus CVS repository. |
|
<h4><br> |
|
<span class="SpellE"></span></h4> |
|
<h4><span class="SpellE">SLP Provider</span></h4> |
|
<p><span class="SpellE">This provider acts as the definer of |
|
SLP information for SLP registration and also controls the Pegasus SLP |
|
Service Agent. It is treated as a normal provider rather than a control |
|
provider because it does not use internal functions of the CIMOM to |
|
generate any of its information today. (conditionally compiled today)<br> |
|
</span></p> |
|
<br> |
|
<br> |
|
</blockquote> |
|
<h3><span class="SpellE"><b>CIM_Schema</b></span></h3> |
|
<p>The default <span class="SpellE">CIM_Schema</span> loaded with this |
|
release is |
|
the DMTF CIM 2.9, Final release. In addition, Pegasus includes |
|
a number of |
|
local classes defined for Pegasus. These are defined in the |
|
pegasus/Schemas |
|
directory. <span style=""></span>There are also a |
|
number of older schema available in the CVS.</p> |
|
<p>The mechanism to install other schemas than the default is defined |
|
in the mak/config.mak</p> |
|
<p style="margin-bottom: 12pt;"><b>NOTE:</b> The CIM 2.5 schema is |
|
maintained in the |
|
CVS repository because it remains the basis for parts of the Pegasus |
|
test |
|
environment.</p> |
|
<h3><b>Pegasus MOF Compilers</b></h3> |
|
<p>Pegasus implements a MOF compiler that can operate either at the |
|
client |
|
interface to the Pegasus CIM Server (<span class="SpellE">cimmof</span>) |
|
or directly interfacing with a CIM |
|
repository (<span class="SpellE">cimmofl</span>).</p> |
|
<p>The direct interface compiler is used primarily to provide an |
|
initial |
|
class/instance repository. <font color="#ff0000"><b>WARNING:</b></font> |
|
the use of <span class="SpellE">cimmofl</span> |
|
to manipulate instances in the repository bypasses any provider that is |
|
registered to serve these instances and simply installs the |
|
instances in the |
|
instance repository; this may result in 1) bad data in the repository |
|
if there are registered providers, 2) corruption of the repository if |
|
the CIM Server is running or, 3) MOF data that is loaded but not |
|
available until the server is stopped and restarted in some |
|
cases. Use of <span class="SpellE">cimmofl in general is |
|
discouraged and particularly </span> to manipulate |
|
instances served by a registered providers (ex. Provider registration). |
|
<br> |
|
</p> | </p> |
<h3><b>Client Tools</b></h3> |
<p style="color: rgb(153, 51, 153);">To check whether your current |
Lightweight statistics are now implemented for |
running |
the |
kernel supports IPv6, take a look into your /proc filesystem. The entry |
client. The client statistics surfaces the elapsed time spent in the |
/proc/net/if_inet6 must exist. A short automated test looks like:<br> |
client, |
|
and the |
|
elapsed time spent on the network between client and server.<br> |
|
<br> |
|
<h3><b>Pegasus CIM Server <span class="SpellE">Administration</span></b></h3> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;"><span class="SpellE">cimuser</span> |
|
- Manage Pegasus CIM Server Users.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><span class="SpellE">cimconfig</span> |
|
- Manage the Pegasus CIM Server configuration parameters.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><span class="SpellE">cimauth</span> |
|
- Manage the CIM Server authorization characteristics. Today this is |
|
authorizing users to namespaces.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><span class="SpellE">cimprovider</span> |
|
- Manage information about the providers .</li> |
|
</ol> |
|
<br> |
|
<span style="font-weight: bold;">Server admin |
|
note:</span><br> |
|
<div style="margin-left: 40px;">The default behavior for determining |
|
the CIM server's HTTP and HTTPS ports has changed. In previous |
|
releases, any value in /etc/services would override a port explicitly |
|
specified in the configuration. The new order for determining the |
|
CIM server's HTTP and HTTPS ports is as follows:<br> |
|
1) An explicitly specified port value takes precedence over any other |
|
values.<br> |
|
</div> |
|
<div style="margin-left: 40px;">2) If no port is specified, the value |
|
in /etc/services is used.<br> |
|
3) If no value is specified in /etc/services, the default WBEM port is |
|
used.<br> |
|
</div> |
|
<h3><b>Information client tools</b></h3> |
|
<p>These tools provide information on the objects managed by the server.</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;"><span class="SpellE">tomof</span> |
|
- output classes and/or instance information from the Pegasus |
|
repository in MOF or XML format.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><span class="SpellE">dnsinfo</span> |
|
- Generate a set of standard information on the <span class="SpellE">Domain</span> |
|
Name System (DNS) configuration from CIM Classes. Note that the |
|
information generated is dependent on the information available from |
|
providers and differs from system to system.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><span class="SpellE">ipinfo</span> |
|
- Generates a set of standard information from the Network |
|
Schema. Information generated varies by system because of the |
|
level of provider support.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><span class="SpellE">osinfo</span> |
|
- Generate a set of standard information on the Operating System from |
|
CIM Classes. Note that the information generated is dependent on the |
|
information available from providers and differs from system to system<o:p></o:p></li> |
|
</ol> |
|
<h3><b>Test support Tools</b></h3> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Pegasus unit tests |
|
(available through the "tests" option on the Pegasus make files) these |
|
tests are defined throughout the Pegasus source tree typically in |
|
"tests" directories. <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">The Pegasus test suite |
|
(see the pegasus/tests directory<span class="SpellE"></span>)<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">TestClient</span> |
|
</b>- Basic client for overall platform operation testing. <o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b><span class="SpellE">wbemexec</span></b> |
|
- Test tool that sends/receives XML from XML input.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b>CLI</b> - Command line |
|
interface for Client commands.<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;"><b>Benchmark Test</b> - A |
|
benchmark test environment is provided which includes both a client and |
|
provider component. See <span class="SpellE">src/clients/benchmarkTest</span> |
|
for more information.<o:p></o:p></li> |
|
</ol> |
|
<h3><b>Pegasus Interface APIs</b></h3> |
|
<p>Details of the Pegasus public interfaces for this release are listed |
|
in PEP 209 |
|
available from the web <span class="GramE">site(</span><a |
|
href="http://www.openpegasus.org/pp/uploads/40/Administrator/My%20Documents/processes/www.openpegasus.org">www.openpegasus.org</a>). |
|
That document is the <span class="SpellE">authorative</span> source |
|
for the list of publicly supported Pegasus APIs. The Client |
|
and Provider API were originally frozen at the Pegasus version 2.1 |
|
release. The interfaces in the release of Pegasus 2.1 are forward |
|
compatible to this release. Well-behaved clients and providers compiled |
|
to the Pegasus 2.1 or 2.2 interfaces should be compatible with this |
|
release without compilation. There have been extensions and new |
|
interfaces added for this release and these are marked as experimental. |
|
The Pegasus public |
|
interfaces includes the following major functions</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;">Client APIs<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">Provider APIs<o:p></o:p></li> |
|
<li class="MsoNormal" style="color: black;">CIM Object and System |
|
function APIs</li> |
|
</ol> |
|
<p>In addition, there are other client interfaces which are not today |
|
in the public SDK including:</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: rgb(0, 0, 0);"><span style="" |
|
lang="DA">CIM Listener APIs</span></li> |
|
<ul style="color: rgb(0, 0, 0);"> |
|
<li class="MsoNormal">CIM Listener |
|
is a component that can be used to consume indications without a |
|
dependency on the Pegasus CIMOM. In environments where no CIMOM is |
|
running or a physical separation between the indication listener and |
|
the CIMOM is desired, CIM Listener fits the bill. Still, there are |
|
several enhancements that are necessary to make CIM Listener scalable. <font |
|
style="color: rgb(0, 0, 0);">Enhancements were deemed significant |
|
enough to propose a new listener that builds off CIMListener's |
|
basic capabilities, yet allows the existing CIMListener to remain the |
|
same.</font></li> |
|
<ul> |
|
<li><font size="2"><b>New CIM Listener now provides selective |
|
indication delivery.</b><span class="norm"></span></font><br> |
|
</li> |
|
<li><span class="norm"></span><font size="2"><b>New CIM Listener |
|
keeps all consumer libraries in memory for the duration of its |
|
execution.</b><span class="norm"></span></font><br> |
|
</li> |
|
<li><span class="norm"></span><font size="2"><b>New CIM Listener |
|
is now pluggable.</b><br> |
|
<span class="norm"></span></font></li> |
|
<li><span class="norm"></span><font size="2"><b>New CIM Listener |
|
now provides reliable indication delivery.</b></font></li> |
|
</ul> |
|
</ul> |
|
<li class="MsoNormal" style="color: black;"><span lang="da">SLP |
|
Client (User Agent) APIs which are extensions to the Client APIs</span></li> |
|
</ol> |
|
<p class="MsoNormal"><span style="color: black;"><o:p> </o:p></span></p> |
|
<p class="MsoNormal"><span style="color: black;">The APIs are |
|
documented in |
|
their respective header files and in HTML documentation based on |
|
the information |
|
in the header files extracted with the doc++ tool will be available on |
|
the |
|
OpenPegasus web site.<br> |
|
<o:p></o:p></span></p> |
|
<h3><b>WMI <span class="SpellE">Mapper</span></b></h3> |
|
<p>The WBEM to WMI <span class="SpellE">Mapper</span> provides a way |
|
to access |
|
WMI data from Windows platform systems. It converts incoming XML/CIM |
|
requests |
|
to Microsoft WMI requests, executes the requests, converts the results |
|
to |
|
XML/CIM and returns the results to the client. WMI <span class="SpellE">Mapper</span> |
|
receives an HTTP message containing the XML/CIM request. It decodes the |
|
XML |
|
message and extracts from the HTTP message header the user credentials |
|
provided |
|
on the connection (username and password). The WMI <span class="SpellE">Mapper</span> |
|
authenticates these credentials, verifying if the provided credentials |
|
have |
|
access to the desired WMI data. This is done because the WMI <span |
|
class="SpellE">Mapper</span> runs as a service, logged on using an |
|
account with |
|
administrative rights (which has all access to WMI data). Because of |
|
this, the |
|
WMI <span class="SpellE">Mapper</span> impersonates the user |
|
credentials provided |
|
on the HTTP message to ensure that the calling user has rights to |
|
browse WMI |
|
data. Hence, ALL requests made to the WMI <span class="SpellE">Mapper</span> |
|
MUST |
|
contain user credentials.<br> |
|
</p> | </p> |
<h3><b><b>Indication Handlers</b></b></h3> |
<div style="margin-left: 40px; color: rgb(153, 51, 153);">test -f |
System Log Indication Handler<br> |
/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"<br> |
<div style="margin-left: 40px;">The SysLog Indication Handler is a new |
|
for 2.5 |
|
type of Indication Handler which allows CIM Indications to be delivered |
|
to the system syslog file. It has following features:<br> |
|
</div> | </div> |
<ul> |
<br style="color: rgb(153, 51, 153);"> |
<li>Each syslog file entry has a tag 'CIM Indication' to distinguish |
<span style="color: rgb(153, 51, 153);">For more information on |
an entry made by Syslog Indication Handler.</li> |
enabling |
</ul> |
IPv6 in the Linux kernel and configuring network interfaces, refer to </span><a |
<ul> |
style="color: rgb(153, 51, 153);" |
<li>If a subscriber includes PerceivedSeverity property in the SELECT |
href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux |
list of the filter condition for the indication, the PerceivedSeverity |
Documentation Project's IPv6 HOWTO</a><span |
will be mapped to syslog error severity. Otherwise, syslog error |
style="color: rgb(153, 51, 153);">.<br> |
severity 'LOG_INFO' is used.</li> |
<br> |
<li>See <a |
<span style="color: rgb(153, 51, 153);"><span style="font-weight: bold;">Warning</span>: |
href="http://www.openpegasus.org/pp/uploads/40/7165/PEP206-SystemLogIndicationHandler.htm">PEP |
There is currently an open issue with RedHat to address a problem that |
206</a> for details.<br> |
is seen intermittently on RHEL5 and SLES10 systems. This problem is |
</li> |
described in </span><a style="color: rgb(153, 51, 153);" |
</ul> |
href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus |
<br> |
bug 6586</a><span style="color: rgb(153, 51, 153);"> and </span><a |
Email Indicaiton Handler<br> |
style="color: rgb(153, 51, 153);" |
<div style="margin-left: 40px;">The Email Indication Handler is a new |
href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat |
for 2.5 |
bug 248052</a><span style="color: rgb(153, 51, 153);">, and manifests |
type of Indication Handler that allows CIM Indications to be delivered |
itself as an intermittent IPv6 socket failure. You should be aware that |
to a specified e-mail address. See <a |
OpenPegasus with IPv6 enabled may be |
href="http://www.openpegasus.org/pp/uploads/40/7166/PEP207-EmailIndicationHandler.htm">PEP |
significantly impacted in these environments.</span><br |
207</a> for details. <br> |
style="color: rgb(153, 51, 153);"> |
|
</span> |
|
<h4 style="color: rgb(153, 51, 153);">IPv6 on Windows</h4> |
|
<p style="color: rgb(153, 51, 153);">Microsoft provides supported IPv6 |
|
implementations for Windows Server |
|
2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service |
|
Pack 2 (SP2), and Windows CE .NET 4.1 and later.</p> |
|
<span style="color: rgb(153, 51, 153);">On Windows XP, you can use the </span><span |
|
style="font-weight: bold; color: rgb(153, 51, 153);">ipv6.exe</span><span |
|
style="color: rgb(153, 51, 153);"> tool to install, uninstall, and |
|
query |
|
your IPv6 configuration. For example:</span><br |
|
style="color: rgb(153, 51, 153);"> |
|
<br style="color: rgb(153, 51, 153);"> |
|
<div style="margin-left: 40px; color: rgb(153, 51, 153);">ipv6 install<br> |
|
ipv6 if<br> |
</div> | </div> |
<br> |
<br style="color: rgb(153, 51, 153);"> |
<br> |
<span style="color: rgb(153, 51, 153);">Windows Vista |
|
and Windows Server 2008 support an integrated |
|
IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack. |
|
Note that the OpenPegasus IPv6 support in 2.6.1 has not yet been tested |
|
on Windows Vista or Windows Server 2008.</span><br |
|
style="color: rgb(153, 51, 153);"> |
|
<br style="color: rgb(153, 51, 153);"> |
|
<span style="color: rgb(153, 51, 153);">For more information on |
|
installing, configuring, and using IPv6 on Windows platforms, refer to |
|
the document </span><a style="color: rgb(153, 51, 153);" |
|
href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx">IPv6 |
|
for Microsoft Windows: Frequently Asked Questions</a><span |
|
style="color: rgb(153, 51, 153);">.</span><br |
|
style="color: rgb(153, 51, 153);"> |
|
<h4 style="color: rgb(153, 51, 153);">Testing your OpenPegasus IPv6 |
|
support</h4> |
|
<span style="color: rgb(153, 51, 153);">As part of the OpenPegasus |
|
automated tests, the TestClient, g11ntest, and IndicationStressTest |
|
test clients were modified to run tests using the IPv6 loopback address |
|
(::1) if PEGASUS_ENABLE_IPV6=true.</span><br |
|
style="color: rgb(153, 51, 153);"> |
|
<br style="color: rgb(153, 51, 153);"> |
|
<span style="color: rgb(153, 51, 153);">You can also perform manual |
|
tests |
|
using the IPv6 loopback or a real IPv6-configured network interface. |
|
For example, using the IPv6 loopback on a system with OpenPegasus |
|
running on the wbem standard http port of 5988:</span><br |
|
style="color: rgb(153, 51, 153);"> |
|
<div style="margin-left: 40px;"><br style="color: rgb(153, 51, 153);"> |
|
<span style="color: rgb(153, 51, 153);">osinfo -h ::1</span><br> |
|
</div> |
|
<p></p> |
<ol> | <ol> |
</ol> | </ol> |
<h2><a name="Relationship_to_CIMWBEM_Standards"></a>Relationship to |
<h2>OpenPegasus Relationship to |
CIM/WBEM Standards</h2> | CIM/WBEM Standards</h2> |
<p>Pegasus was designed and implemented to comply with the DMTF | <p>Pegasus was designed and implemented to comply with the DMTF |
specifications The following table defines the level of the DMTF |
CIM/WBEM specifications The following table defines the level of the |
specifications which which Pegasus conforms today.</p> |
DMTF specifications to which this version of Pegasus aims to conform |
|
today.</p> |
<table id="AutoNumber1" border="1" cellspacing="1" width="100%"> | <table id="AutoNumber1" border="1" cellspacing="1" width="100%"> |
<tbody> | <tbody> |
<tr> | <tr> |
|
|
<td bgcolor="#00ffff" width="33%"><b>Specification Version</b></td> | <td bgcolor="#00ffff" width="33%"><b>Specification Version</b></td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0004 CIM Specification</td> |
<td width="33%">DSP 0004 - CIM Infrastructure Specification</td> |
<td width="33%">Version 2.2 with Addendum</td> |
<td width="33%">Version 2.3 Final, 4 October 2005</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0200 - CIM Operations over HTTP</td> | <td width="33%">DSP 0200 - CIM Operations over HTTP</td> |
<td width="33%">1.1, final, 6 January 2002</td> |
<td width="33%">1.2.0, preliminary, 9 December 2004</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0201 - Representation of CIM in XML</td> | <td width="33%">DSP 0201 - Representation of CIM in XML</td> |
<td width="33%">2.1, preliminary, May 2, 2002</td> |
<td width="33%">2.2.0, preliminary, December 2004</td> |
|
</tr> |
|
<tr> |
|
<td width="33%">DSP 0202 - CIM Query Language Specification</td> |
|
<td width="33%">1.0.0, preliminary, 9 December 2004</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">DSP 0205 - WBEM Discovery using SLP</td> | <td width="33%">DSP 0205 - WBEM Discovery using SLP</td> |
<td width="33%">1.0, preliminary, 27 January 2004</td> | <td width="33%">1.0, preliminary, 27 January 2004</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">WBEM SLP Template</td> |
<td width="33%">DSP 0206 - WBEM SLP Template</td> |
<td width="33%">1.0.0</td> |
<td width="33%">1.0.0, Preliminary, January 2004</td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="33%">CIM Schema </td> | <td width="33%">CIM Schema </td> |
<td width="33%">2.9 Final, Jan. 2005</td> |
<td width="33%">2.9 Final, Jan. 2005 ( default) 2.13.1 (available |
|
in pegasus CVS)</td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<h2><b><span style="font-family: Times;"><a name="Supported Platforms">Supported |
<h2><a name="Conformance with DMTF Specifications">Conformance |
|
Exceptions to |
|
DMTF Specifications</a></h2> |
|
<p>It is a major goal |
|
of the OpenPegasus project to both drive and utilize the DMTF CIM/WBEM |
|
specifications. However, today there are a number of known |
|
differences. |
|
As of this release, some of the differences include the following:</p> |
|
<ol> |
|
<li><b>Provider Registration</b> - Pegasus supports registration |
|
through a set of Pegasus Provider registration classes rather than |
|
support the DMTF defined Provider Qualifier. Pegasus will not support |
|
this qualifier in the future. See the readme for more information on |
|
provider registration. This is not a deviation from the |
|
specifications but is a different method of registration than many CIM |
|
Servers and means that the the provider qualifier is unused in Pegasus.</li> |
|
<li> <b>Indications </b>-Today Pegasus supports process |
|
indications and lifecycle indications when defined specifically by |
|
providers. Pegasus does not support lifecycle indications if they are |
|
not defined by the provider or for changes to CIM Classes.<font |
|
color="#ff0000"> </font><span class="norm"> <font color="#ff0000"> </font>For |
|
more information see the Pegasus CVS file <a name="comtag_137"> <font |
|
face="Courier New">pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a>.</span></li> |
|
<li> |
|
<p class="MsoNormal"><span style="color: black;"> </span><font |
|
style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers |
|
option on Instance Operations</font><span style="color: black;"><b> </b> |
|
- |
|
The DMTF specifications have deprecated the use of qualifiers on |
|
instance operations with the 1.2 CIM Operations Specification. |
|
Some CIM Client implementations expect instances |
|
returned |
|
from the CIM Server to include the qualifiers defined in the class |
|
definition (such as KEY qualifiers on properties). </span> Pegasus |
|
today expects the provider to complete the qualifiers on instances in |
|
accordance with the specification and generally the interpretation is |
|
that Pegasus applies class level qualifiers when the includeInstance |
|
parameter is supplied on instance operations. However, Pegasus |
|
today is inconsistent in the return of qualifiers so that the user |
|
should NOT depend on Pegasus accurately honoring the includeQualifier |
|
parameter for instance operations. In the future it is expected |
|
that Pegasus will deprecate the use of qualifiers on instance |
|
operations completely.<font color="#ff0000"> </font></p> |
|
</li> |
|
<li><b>LocalOnly option on instance |
|
Operations </b>- With the 1.1 version of Specification for CIM |
|
Operations over HTTP, the definition of the LocalOnly parameter for the |
|
GetInstance and EnumerateInstances operations was modified. This change |
|
was incorrect, resulted in reduced functionality and introduced a |
|
number of backward compatibility issues. As a result of issues |
|
introduced by this change, we strongly recommend that CIM Clients set |
|
LocalOnly = false and do not rely on the use of this parameter to |
|
filter the set of set of properties returned. See Appendix C of this |
|
specification for more information.</li> |
|
<li> |
|
<p class="MsoNormal"><b>MultiRequest Oprations</b> - Pegasus |
|
does not support the DMTF defined MultiRequest Operation option.</p> |
|
</li> |
|
<li> |
|
<p class="MsoNormal"><b>MOFCompiler namespace pragma</b> - The |
|
Pegasus compiler does not support the namespace pragma.</p> |
|
</li> |
|
<li><span style="color: rgb(153, 51, 153);">Pegasus implements |
|
chunking |
|
based on the DSP0200 1.2.0 preliminary spec. Refer to bug </span><a |
|
style="color: rgb(153, 51, 153);" |
|
href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a><span |
|
style="color: rgb(153, 51, 153);"> for more details.</span><br> |
|
</li> |
|
</ol> |
|
<h2><b><span style="font-family: Times;">OpenPegasus <a |
|
name="Supported Platforms">Supported |
Platforms</a></span></b></h2> | Platforms</a></span></b></h2> |
<p>Each Pegasus release lists as 'active' platforms those |
<p>Each OpenPegasus release lists as 'active' platforms those |
hardware/software platforms that have recognized ports for the Pegasus | hardware/software platforms that have recognized ports for the Pegasus |
code | code |
base including a maintainer for the platform that will be willing to | base including a maintainer for the platform that will be willing to |
|
|
bugzilla database for a list of relevant defects that affect their | bugzilla database for a list of relevant defects that affect their |
platform. The platforms that are considered 'active' for this | platform. The platforms that are considered 'active' for this |
Pegasus release are:<br> | Pegasus release are:<br> |
<span class="norm"></span><br> |
</p> |
</p> |
|
<table class="MsoNormalTable" style="width: 302.25pt;" border="1" | <table class="MsoNormalTable" style="width: 302.25pt;" border="1" |
cellpadding="0" cellspacing="1" height="409" width="504"> | cellpadding="0" cellspacing="1" height="409" width="504"> |
<tbody> | <tbody> |
|
|
<tr style=""> | <tr style=""> |
<td style="padding: 0.75pt; width: 126.75pt;" height="25" | <td style="padding: 0.75pt; width: 126.75pt;" height="25" |
width="211"> | width="211"> |
<p class="MsoNormal"><span style="color: black;">Linux IA-32<o:p></o:p></span></p> |
<p class="MsoNormal"><span style="color: black;">Linux IA-32, <span |
|
style="color: rgb(153, 51, 153);">X86_64</span><o:p></o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="25" | <td style="padding: 0.75pt; width: 173.25pt;" height="25" |
width="289"> | width="289"> |
<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 style="color: black;"> |
(versions 2.9x and 3.xx)<o:p></o:p></span></p> |
(versions 2.9x, 3.xx, <span style="color: rgb(153, 51, 153);">4.xx</span>)<o:p></o:p></span></p> |
</td> | </td> |
</tr> | </tr> |
<tr style=""> | <tr style=""> |
|
|
<tr> | <tr> |
<td style="padding: 0.75pt; width: 126.75pt;" height="69" | <td style="padding: 0.75pt; width: 126.75pt;" height="69" |
width="211"> | width="211"> |
<p class="MsoNormal"><span style="color: black;">Windows XP<o:p></o:p></span></p> |
<p class="MsoNormal"><span style="color: black;">Windows XP<o:p>, |
|
Windows 2003</o:p></span></p> |
</td> | </td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="69" | <td style="padding: 0.75pt; width: 173.25pt;" height="69" |
width="289"> | width="289"> |
|
|
<td style="padding: 0.75pt; width: 126.75pt;" height="43" | <td style="padding: 0.75pt; width: 126.75pt;" height="43" |
width="211"> <font size="3">MacOS version 10.2 and higher</font></td> | width="211"> <font size="3">MacOS version 10.2 and higher</font></td> |
<td style="padding: 0.75pt; width: 173.25pt;" height="43" | <td style="padding: 0.75pt; width: 173.25pt;" height="43" |
width="289"> <font size="3">gcc 3.3</font></td> |
width="289"> <font size="3">gcc 3.3, gcc 4.01</font></td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big>HP OpenVMS Alpha<br> | <td style="vertical-align: top;"><big>HP OpenVMS Alpha<br> |
</big></td> | </big></td> |
<td style="vertical-align: top;"> <big><font | <td style="vertical-align: top;"> <big><font |
style="color: rgb(0, 0, 0);" color="RED">HP C++ V6.5-042 for OpenVMS |
style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span |
|
style="color: rgb(153, 51, 153);">7.3-009</span> for OpenVMS |
Alpha and above</font></big> </td> | Alpha and above</font></big> </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><big><span class="norm"></span><font | <td style="vertical-align: top;"><big><span class="norm"></span><font |
style="color: rgb(0, 0, 0);"> HP OpenVMS IA64</font></big></td> | style="color: rgb(0, 0, 0);"> HP OpenVMS IA64</font></big></td> |
<td style="vertical-align: top;"><span class="norm"></span><big><font | <td style="vertical-align: top;"><span class="norm"></span><big><font |
style="color: rgb(0, 0, 0);">HP C++ V7.1-011 on OpenVMS IA64 and above</font></big> |
style="color: rgb(0, 0, 0);">HP C++ V7.<span |
|
style="color: rgb(153, 51, 153);">2-021</span> on OpenVMS IA64 and |
|
above</font></big> </td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;"><big><font color="RED"><span |
|
style="color: rgb(0, 0, 0);">Solaris 8<br> |
|
</span></font></big></td> |
|
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
|
CC compiler V 5.8. Note that the latest thread patch (108993) may be |
|
required. (see Pegasus bug 4632)</big><br> |
</td> | </td> |
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;"><span class="norm"></span><big><font><font | <td style="vertical-align: top;"><span class="norm"></span><big><font><font |
color="RED"><span style="color: rgb(0, 0, 0);">Solaris 8<br> |
color="RED"><span style="color: rgb(0, 0, 0);">Solaris 9<br> |
* See below for additional info<br> |
</span></font></font></big></td> |
</span> </font></font></big></td> |
<td style="vertical-align: top;"><big>GNU 2.95.3, Sun |
<td style="vertical-align: top;"><big>GNU 2.95.3</big><br> |
WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big><br> |
</td> | </td> |
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<br> | <br> |
<span style="font-weight: bold;">Solaris:</span> Solaris testing |
<b>Platform patches</b> |
began late in the 2.5 release cycle, thus has not been thoroughly |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font |
tested. In order for Pegasus 2.5 to function properly on that |
style="color: rgb(0, 0, 0);">The following is a list of platform |
platform, changes documented in OpenPegasus Bugzilla 4179 must be |
|
applied. <span class="norm"><font color="RED"> |
|
</font></span> |
|
<h2><small><b><b>Platform patches</b></b></small></h2> |
|
<font style="color: rgb(0, 0, 0);">The following is a list of platform |
|
patches Pegasus requires.<br> | patches Pegasus requires.<br> |
<br> |
|
</font> | </font> |
<div style="margin-left: 40px;"><font style="color: rgb(0, 0, 0);">RHAS |
</p> |
|
<div style="margin-left: 40px;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font |
|
style="color: rgb(0, 0, 0);">RHAS |
2.1 needs the update to fix Red Hat Bugzilla 98815.</font><br> | 2.1 needs the update to fix Red Hat Bugzilla 98815.</font><br> |
|
</p> |
</div> | </div> |
<br> |
|
<p>Further information regarding Pegasus support on IBM platforms can | <p>Further information regarding Pegasus support on IBM platforms can |
be | 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> <br> |
<p> Further information regarding Pegasus support on HP platforms can |
Further information regarding Pegasus support on HP platforms can be |
be |
found at: | found at: |
<a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> | <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.</p> |
<p><o:p><br> |
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2> |
</o:p></p> |
|
<h2><a name="Conformance with DMTF Specifications">Conformance with |
|
DMTF Specifications</a></h2> |
|
<p>It is a major goal |
|
of the OpenPegasus project to both drive and utilize the DMTF CIM/WBEM |
|
specifications. However, today there are a number of known |
|
differences. |
|
As of this release, some of the differences include the following:</p> |
|
<ol> |
|
<li><b>Provider Registration</b> - Pegasus supports registration |
|
through a set of Pegasus Provider registration classes rather than |
|
support the DMTF defined Provider Qualifier. Pegasus will not support |
|
this qualifier in the future. See the readme for more information on |
|
provider registration.</li> |
|
<li> <b>Indications </b>-Today Pegasus supports process |
|
indications but does not |
|
include any specific support for lifecycle indications.</li> |
|
<li> |
|
<p class="MsoNormal"><span style="color: black;"> </span><font |
|
style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers |
|
option on Instance Operations</font><span style="color: black;"><b> </b> |
|
- |
|
The DMTF specifications are unclear regarding the inclusion of |
|
qualifiers on |
|
CIM instances. Some CIM Client implementations expect instances |
|
returned |
|
from the CIM Server to include the qualifiers defined in the class |
|
definition (such as KEY qualifiers on properties). </span> Pegasus |
|
today expects the provider to complete the qualifiers on instances in |
|
accordance with the specification and generally the interpretation is |
|
that Pegasus applies class level qualifiers when the includeInstance |
|
parameter is supplied on instance operations. However, Pegasus |
|
today is inconsistent in the return of qualifiers so that the user |
|
should NOT depend on Pegasus accurately honoring the includeQualifier |
|
parameter for instance operations. In the future it is expected |
|
that Pegasus will deprecate the use of qualifiers on instance |
|
operations completely.</p> |
|
</li> |
|
<li><b>LocalOnly option on instance |
|
Operations </b>- With the 1.1 version of Specification for CIM |
|
Operations over HTTP, the definition of the LocalOnly parameter for the |
|
GetInstance and EnumerateInstances operations was modified. This change |
|
was incorrect, resulted in reduced functionality and introduced a |
|
number of backward compatibility issues. As a result of issues |
|
introduced by this change, we strongly recommend that CIM Clients set |
|
LocalOnly = false and do not rely on the use of this parameter to |
|
filter the set of set of properties returned.</li> |
|
<li> |
|
<p class="MsoNormal"> <b>CIM MOF compiler function for |
|
instance aliasing</b> - The Pegasus MOF compiler does not today support |
|
this function. This function is planned for a future version.</p> |
|
</li> |
|
<li> |
|
<p class="MsoNormal"><b> MultiRequest Oprations</b> - Pegasus |
|
does not support the DMTF defined MultiRequest Operation option.</p> |
|
</li> |
|
<li> |
|
<p class="MsoNormal"><b>MOFCompiler namespace pragma</b> - The |
|
Pegasus compiler does not support the namespace pragma.</p> |
|
</li> |
|
</ol> |
|
<h2><a name="Changes in This Release">Changes in This Release</a></h2> |
|
<p>The development and release of each version of Pegasus is defined |
|
and |
|
controlled through Pegasus PEP documents. PEP 180 is the |
|
controlling document |
|
this release and lists the original set of changes proposed and the |
|
status of |
|
each of those changes. Note that not all of the originally defined |
|
functionality was completed for this release.</p> |
|
<p>In general, the areas of development for this release were:</p> |
|
<ol style="margin-top: 0in;" start="1" type="1"> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Addition of CQL |
|
stage 1 support<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Refactoring of |
|
Object Normalizer function to improve performance. </p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Out of Process |
|
Provider user level request.<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Embedded Object |
|
support. </p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Command Line |
|
Utilities<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">CIMDateTime |
|
enhancements<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of |
|
AutoPtr enhancements. </p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Certificate |
|
management and user-based certificate authentication<br> |
|
</p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;"> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;">Completion of HTTP |
|
chunking. <font style="color: rgb(51, 51, 255);" color="RED">Pegasus |
|
now supports HTTP V1.1 transfer encoding otherwise known as chunking .<a |
|
href="http://www.openpegasus.org/pp/uploads/40/5097/PEP140_ChunkedEncoding_4.3.html"> |
|
PEP 140</a> describes the implementation details.</font></p> |
|
</li> |
|
<li class="MsoNormal" style="color: black;">Client side performance |
|
statistics</li> |
|
<li class="MsoNormal" style="color: black;">Syslog Indication handler.</li> |
|
<li class="MsoNormal" style="color: black;">Email Indication handler.</li> |
|
<li class="MsoNormal" style="color: black;">Port to OpenVMS.</li> |
|
</ol> |
|
<p class="MsoNormal" style="margin-left: 0.5in;"> </p> |
|
The complete set of <span class="SpellE">PEPs</span> defined for |
|
this release is defined in PEP 180. |
|
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus defects<br> |
|
</a></span></h2> |
|
<p>The Pegasus bugzilla database documents any defects found in Pegasus | <p>The Pegasus bugzilla database documents any defects found in Pegasus |
and is available through the following link: <a | and is available through the following link: <a |
href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla | href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla |
database</a>. <br> |
database</a>. Note that all changes committed for this |
|
release have been marked with the keyword <font face="Courier New"><b>2.6.<span |
|
style="color: rgb(153, 51, 153);">1</span>_APPROVED</b></font> |
|
so that all changes for this release can be found with the following |
|
bug search. Effective with the start of the Pegasus 2.6 work, all |
|
changes to the CVS tree were documented through bugs. Thus bugs |
|
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. Therefore, a search of the bugzilla |
|
base for bugs with the tag <font face="Courier New"><b>2.6.<span |
|
style="color: rgb(153, 51, 153);">1</span>_APPROVED</b></font> will |
|
yield |
|
all changes to the |
|
Pegasus <span style="color: rgb(153, 51, 153);">RELEASE_2_6-branch</span> |
|
CVS <span style="color: rgb(153, 51, 153);">branch since</span> |
|
Pegasus 2.6.0.</p> |
|
<p> |
|
- Changes for Pegasus 2.6.<span |
|
style="color: rgb(153, 51, 153);">1 point</span> release (bugs Tagged <font |
|
face="Courier New"><b>2.6.<span style="color: rgb(153, 51, 153);">1</span>_APPROVED</b></font>) |
|
<a |
|
href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.6.1_APPROVED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Pegasus |
|
2.6.1_APPROVED bug list</a><br> |
</p> | </p> |
<br> |
<h4>2.6.1 bugs of special interest:<br> |
|
</h4> |
|
<ul> |
|
<li><a style="color: rgb(153, 51, 153);" |
|
href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6643">Bug 6643</a><span |
|
style="color: rgb(153, 51, 153);"> changed the way OpenPegasus loads |
|
libraries (such as providers) in a POSIX environment. The dlopen() call |
|
was changed to include the RTLD_GLOBAL option for all POSIX platforms |
|
except VMS.</span><br> |
|
</li> |
|
</ul> |
<h2><a | <h2><a |
name="Pegasus Release Control and Version Definition Documentation">Pegasus | name="Pegasus Release Control and Version Definition Documentation">Pegasus |
Release Control and Version Definition Documentation</a></h2> | Release Control and Version Definition Documentation</a></h2> |
|
|
(PEPs) that serve as the definition and review mechanism for new and | (PEPs) that serve as the definition and review mechanism for new and |
modified Pegasus functionality and for the definition and documentation | modified Pegasus functionality and for the definition and documentation |
of releases.</p> | of releases.</p> |
<p>Specifically the following PEPs define the characteristics of this |
<p>Specifically the following PEPs define the characteristics of the |
Pegasus release.</p> |
Pegasus 2.6 release. These PEPs are available as |
|
<a |
|
href="http://www.openpegasus.org/pp/protected/documents.tpl?CALLER=index.tpl&gdc_docage=0&S=gdc_title&R=desc">OpenPegasus |
|
Approved PEPs.</a><br> |
|
<span style="color: rgb(153, 51, 153);">For this 2.6.1 point release, |
|
only |
|
this document, the 2.6.1 Release Notes, was updated. All other |
|
references should be back to the 2.6 release PEPs.</span><br> |
|
</p> |
<ol> | <ol> |
<li><a |
<li> <b>PEP 218 - OpenPegasus 2.6 Release Definition</b> - This PEP |
href="http://www.openpegasus.org/pp/protected/upreviews/20/1682/PEP209_ExternalInterface2.5.htm">PEP |
is |
209</a> - OpenPegaus 2.5 External Interfaces (as of this document |
used |
verion of PEP 230, PEP 209 is listed as draft status)<br> |
throughout the development of this version as the control point for |
</li> |
functionality that will go into the release and points to all of the |
<li><a |
PEPs that represent the Pegasus functionality changes for this |
href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8502">PEP |
version of Pegasus.</li> |
200</a> - OpenPegaus 2.5 Build and Configuration |
<li> <b>PEP 277 - OpenPegasus 2.6 Build and Configuration |
Option for Selected |
Options</b> for Selected |
Platforms</li> | Platforms</li> |
<li>PEP 230 - Pegasus 2.5 Release Notes (This document)</li> |
<li> <b>PEP 278 OpenPegaus 2.6 External Interfaces</b> - Lists the |
<li><a |
public interfaces for clients and providers that are considered |
href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8503">PEP |
external and therefore "frozen".<br> |
227</a> - Pegasus 2.5 Runtime Packaging Definition<br> |
</li> |
|
<li> <b>PEP 279 - OpenPegasus 2.6 SDK Packaging Definition - </b>Defines |
|
the recommended set of files for inclusion in the OpenPegasus SDK</li> |
|
<li><b>PEP 280 - Pegasus 2.6 Runtime Packaging Definition </b>- |
|
Defines the recommended set of files for inclusion in this OpenPegasus |
|
release.</li> |
|
<li><b style="color: rgb(153, 51, 153);">PEP 305 - Pegasus 2.6.1 |
|
Release |
|
Notes</b> (This document located in |
|
the approved PEP repository and the OpenPegasus source tree root |
|
directory)<br> |
</li> | </li> |
<li><a |
<li><b>PEP 289 - Pegasus 2.6 readme.txt </b>(Located in PEP |
href="http://www.openpegasus.org/pp/protected/doc.tpl?CALLER=index.tpl&gdid=8466">PEP |
repository and also in the OpenPegasus |
210</a> - OpenPegasus 2.5 SDK Packaging Definition</li> |
|
<li>PEP 235 - Pegasus readme.txt for 2.5 (also in the Pegasus |
|
source | source |
tree root directory).</li> | tree root directory).</li> |
<li><a |
|
href="http://www.openpegasus.org/pp/protected/revdoc.tpl?CALLER=revdocuments.tpl&grid=1411">PEP |
|
180</a> - OpenPegasus Release Definition - This PEP is used |
|
throughout the development of this version as the control point for |
|
functionality that will go into the release and points to all of the |
|
PEPs that represent the Pegasus 2.5 functionality changes. (as of |
|
this document verion of PEP 230, PEP 180 is listed as draft status)</li> |
|
</ol> | </ol> |
<h2><a name="General Documentation">General Documentation</a></h2> | <h2><a name="General Documentation">General Documentation</a></h2> |
<p>The following documentation is available for the this Pegasus | <p>The following documentation is available for the this Pegasus |
|
|
<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%"> |
<p><i><font size="2">Copyright (c) 2005 EMC Corporation; |
<p style="text-align: left;"><i><font size="2">Copyright (c) 2006 EMC |
Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open Group; |
Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The |
VERITAS Software Corporation</font><br> |
Open Group; VERITAS Software Corporation; Intel Corp.</font><br> |
<br> | <br> |
</i><i><span style="font-size: 7.5pt;">Permission is hereby granted, |
<font size="1">Permission is hereby granted, free of charge, to any |
free of |
person obtaining a copy of this software and associated |
charge, to any person obtaining a copy of this software and |
|
associated |
|
documentation files (the "Software"), to deal in the Software without | documentation files (the "Software"), to deal in the Software without |
restriction, including without limitation the rights to use, copy, | restriction, including without limitation the rights to use, copy, |
modify, |
modify, merge, publish, distribute, sublicense, and/or sell copies of |
merge, publish, distribute, sublicense, and/or sell copies of the |
the Software, and to permit persons to whom the Software is furnished |
Software, and |
to do so, subject to the following conditions:</font><br> |
to permit persons to whom the Software is furnished to do so, subject |
<font size="2"><br> |
to the |
</font><font size="1">THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION |
following conditions:</span><br> |
NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE |
</i><i><span style="font-size: 10pt;"><br> |
SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF |
</span></i><i><span style="font-size: 7.5pt;">THE ABOVE COPYRIGHT |
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE |
NOTICE AND THIS |
|
PERMISSION NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL |
|
PORTIONS OF |
|
THE SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT |
|
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO |
|
THE |
|
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND | WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND |
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE | NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE |
LIABLE |
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION |
FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF |
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION |
CONTRACT, |
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</font></i></p> |
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE |
</span></div> |
SOFTWARE OR |
|
THE USE OR OTHER DEALINGS IN THE SOFTWARE.</span></i></p> |
|
<p> </p> | <p> </p> |
</div> | </div> |
</body> | </body> |