pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.1 and 1.21

version 1.1, 2005/08/26 15:53:40

version 1.21, 2015/03/18 17:07:01

Line 1

<html>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<head>

</head>

<body>

<hr>

Pegasus Enhancement Proposal (PEP)

PEP #: 098

Title: Release Notes Pegasus 2.3

Version: 1.1

Created: 10 October 2003

Authors: Karl Schopmeyer

Status:  Approved

<style>

Version History:

st1\:*{behavior:url(#ieooui) }

</style>

<table border="1" cellspacing="1" bordercolordark="#666666" bordercolorlight="#CCCCCC"

<style>

width="100%" style="font-size=10.0pt;font-family:Arial">

<!--

<tr>

/* Font Definitions */

<th bgcolor="#CAE6CA">Version</th>

@font-face

{font-family:Courier;

<th bgcolor="#CAE6CA">Author</th>

panose-1:2 7 4 9 2 2 5 2 4 4;

<th bgcolor="#CAE6CA">Change Description</th>

mso-font-charset:0;

</tr>

mso-generic-font-family:modern;

<tr>

mso-font-format:other;

mso-font-pitch:fixed;

<td align="center">10 October 2003</td>

mso-font-signature:3 0 0 0 1 0;}

@font-face

<td>Initial Submission</td>

{font-family:SimSun;

</tr>

panose-1:2 1 6 0 3 1 1 1 1 1;

<tr>

mso-font-alt:\5B8B\4F53;

mso-font-charset:134;

<td align="center">31 October 2003</td>

mso-generic-font-family:auto;

<td align="center">K. Schopmeyer</td>

mso-font-pitch:variable;

<td>Update to integrate comments and complete table of PEPs</td>

mso-font-signature:3 135135232 16 0 262145 0;}

</tr>

@font-face

<tr>

{font-family:Verdana;

panose-1:2 11 6 4 3 5 4 4 2 4;

<td align="center">19 November 2003</td>

mso-font-charset:0;

<td align="center">K. Schopmeyer</td>

mso-generic-font-family:swiss;

<td>Update to reflect comments from review Nov 2003. Approved with comments</td>

mso-font-pitch:variable;

mso-font-signature:536871559 0 0 0 415 0;}

@font-face

{font-family:Times;

panose-1:2 2 6 3 5 4 5 2 3 4;

mso-font-charset:0;

mso-generic-font-family:roman;

mso-font-pitch:variable;

mso-font-signature:536902279 -2147483648 8 0 511 0;}

@font-face

{font-family:"\@SimSun";

panose-1:2 1 6 0 3 1 1 1 1 1;

mso-font-charset:134;

mso-generic-font-family:auto;

mso-font-pitch:variable;

mso-font-signature:3 135135232 16 0 262145 0;}

/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal

{mso-style-parent:"";

margin-bottom:.0001pt;

mso-pagination:widow-orphan;

font-size:12.0pt;

font-family:"Times New Roman";

mso-fareast-font-family:SimSun;

color:windowtext; margin-left:0in; margin-right:0in; margin-top:0in}

{mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

mso-outline-level:1;

font-size:20.0pt;

font-family:Arial;

mso-fareast-font-family:"Times New Roman";

color:#006600;

font-weight:bold;}

{mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

mso-outline-level:2;

font-size:18.0pt;

font-family:"Times New Roman";

mso-fareast-font-family:"Times New Roman";

color:#006600;

font-weight:bold;}

{mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

mso-outline-level:3;

font-size:12.0pt;

font-family:Arial;

mso-fareast-font-family:"Times New Roman";

color:#006600;

font-weight:bold;}

{mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

mso-outline-level:4;

font-size:11.0pt;

font-family:Arial;

mso-fareast-font-family:"Times New Roman";

color:#006600;

font-weight:bold;

font-style:italic;}

{mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

mso-outline-level:5;

font-size:10.0pt;

font-family:Arial;

mso-fareast-font-family:"Times New Roman";

color:#006600;

font-weight:bold;}

{mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

mso-outline-level:6;

font-size:9.0pt;

font-family:Arial;

mso-fareast-font-family:"Times New Roman";

color:#006666;

font-weight:bold;}

a:link, span.MsoHyperlink

{color:blue;

text-decoration:underline;

text-underline:single;}

a:visited, span.MsoHyperlinkFollowed

{color:blue;

text-decoration:underline;

text-underline:single;}

{mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:12.0pt;

font-family:"Times New Roman";

mso-fareast-font-family:SimSun;

color:black;}

code

{mso-ansi-font-size:6.0pt;

mso-bidi-font-size:6.0pt;

font-family:Courier;

mso-ascii-font-family:Courier;

mso-fareast-font-family:"Times New Roman";

mso-hansi-font-family:Courier;

mso-bidi-font-family:"Courier New";

color:navy;}

p.certificate, li.certificate, div.certificate

{mso-style-name:certificate;

mso-margin-top-alt:auto;

margin-right:30.6pt;

mso-margin-bottom-alt:auto;

margin-left:30.6pt;

mso-pagination:widow-orphan;

font-size:12.0pt;

font-family:"Courier New";

mso-fareast-font-family:SimSun;

color:black;}

p.smalltext, li.smalltext, div.smalltext

{mso-style-name:smalltext;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:6.5pt;

font-family:Verdana;

mso-fareast-font-family:SimSun;

mso-bidi-font-family:"Times New Roman";

color:black;}

p.smallgreen, li.smallgreen, div.smallgreen

{mso-style-name:smallgreen;

margin-top:0in;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:8.0pt;

font-family:Verdana;

mso-fareast-font-family:SimSun;

mso-bidi-font-family:"Times New Roman";

color:#006600;}

p.small, li.small, div.small

{mso-style-name:small;

margin-top:0in;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:8.0pt;

font-family:Verdana;

mso-fareast-font-family:SimSun;

mso-bidi-font-family:"Times New Roman";

color:black;}

p.biggreen, li.biggreen, div.biggreen

{mso-style-name:biggreen;

margin-top:0in;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:11.0pt;

font-family:Verdana;

mso-fareast-font-family:SimSun;

mso-bidi-font-family:"Times New Roman";

color:#006600;}

p.norm, li.norm, div.norm

{mso-style-name:norm;

margin-top:0in;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:9.0pt;

font-family:Verdana;

mso-fareast-font-family:SimSun;

mso-bidi-font-family:"Times New Roman";

color:black;}

p.green, li.green, div.green

{mso-style-name:green;

margin-top:0in;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:9.0pt;

font-family:Verdana;

mso-fareast-font-family:SimSun;

mso-bidi-font-family:"Times New Roman";

color:#006600;}

p.red, li.red, div.red

{mso-style-name:red;

margin-top:0in;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:9.0pt;

font-family:Verdana;

mso-fareast-font-family:SimSun;

mso-bidi-font-family:"Times New Roman";

color:red;}

p.blue, li.blue, div.blue

{mso-style-name:blue;

margin-top:0in;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:9.0pt;

font-family:Verdana;

mso-fareast-font-family:SimSun;

mso-bidi-font-family:"Times New Roman";

color:blue;}

p.greenback, li.greenback, div.greenback

{mso-style-name:greenback;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

background:#99FF99;

font-size:12.0pt;

font-family:"Times New Roman";

mso-fareast-font-family:SimSun;

color:black;}

p.blueback, li.blueback, div.blueback

{mso-style-name:blueback;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

background:#CCCCFF;

font-size:12.0pt;

font-family:"Times New Roman";

mso-fareast-font-family:SimSun;

color:black;}

p.whiteback, li.whiteback, div.whiteback

{mso-style-name:whiteback;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

background:white;

font-size:12.0pt;

font-family:"Times New Roman";

mso-fareast-font-family:SimSun;

color:black;}

p.mandatory, li.mandatory, div.mandatory

{mso-style-name:mandatory;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:12.0pt;

font-family:"Times New Roman";

mso-fareast-font-family:SimSun;

color:red;}

p.indexsmall, li.indexsmall, div.indexsmall

{mso-style-name:indexsmall;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:6.0pt;

font-family:Arial;

mso-fareast-font-family:SimSun;

color:black;}

p.indexhead, li.indexhead, div.indexhead

{mso-style-name:indexhead;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:12.0pt;

font-family:Arial;

mso-fareast-font-family:SimSun;

color:#006600;

font-weight:bold;}

p.indexhead2, li.indexhead2, div.indexhead2

{mso-style-name:indexhead2;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:10.0pt;

font-family:Arial;

mso-fareast-font-family:SimSun;

color:#006600;

font-weight:bold;

font-style:italic;}

p.h1, li.h1, div.h1

{mso-style-name:h1;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:20.0pt;

font-family:Arial;

mso-fareast-font-family:SimSun;

color:#006600;

font-weight:bold;}

p.h2, li.h2, div.h2

{mso-style-name:h2;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:15.0pt;

font-family:Arial;

mso-fareast-font-family:SimSun;

color:#006600;

font-weight:bold;}

p.h3, li.h3, div.h3

{mso-style-name:h3;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:12.0pt;

font-family:Arial;

mso-fareast-font-family:SimSun;

color:#006600;

font-weight:bold;}

p.h4, li.h4, div.h4

{mso-style-name:h4;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:11.0pt;

font-family:Arial;

mso-fareast-font-family:SimSun;

color:#006600;

font-weight:bold;

font-style:italic;}

p.h5, li.h5, div.h5

{mso-style-name:h5;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:10.0pt;

font-family:Arial;

mso-fareast-font-family:SimSun;

color:#006600;

font-weight:bold;}

p.h6, li.h6, div.h6

{mso-style-name:h6;

mso-margin-top-alt:auto;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:9.0pt;

font-family:Arial;

mso-fareast-font-family:SimSun;

color:#006600;

font-weight:bold;}

p.arialred, li.arialred, div.arialred

{mso-style-name:arialred;

margin-top:0in;

margin-right:0in;

mso-margin-bottom-alt:auto;

margin-left:0in;

mso-pagination:widow-orphan;

font-size:10.0pt;

font-family:Arial;

mso-fareast-font-family:SimSun;

color:red;

font-weight:bold;}

span.norm1

{mso-style-name:norm1;

mso-ansi-font-size:9.0pt;

mso-bidi-font-size:9.0pt;

font-family:Verdana;

mso-ascii-font-family:Verdana;

mso-hansi-font-family:Verdana;

color:black;

font-weight:normal;}

span.SpellE

{mso-style-name:"";

mso-spl-e:yes}

span.GramE

{mso-style-name:"";

mso-gram-e:yes}

@page Section1

{size:8.5in 11.0in;

margin:1.0in 1.25in 1.0in 1.25in;

mso-header-margin:.5in;

mso-footer-margin:.5in;

mso-paper-source:0;}

div.Section1

{page:Section1;}

/* List Definitions */

@list l0

{mso-list-id:116876382;

mso-list-template-ids:-1942592548;}

@list l0:level1

{mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l0:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l0:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l0:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l0:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l0:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l0:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l0:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l0:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l1

{mso-list-id:438066119;

mso-list-template-ids:1442736534;}

@list l2

{mso-list-id:478041462;

mso-list-template-ids:-1398738630;}

@list l2:level1

{mso-level-number-format:bullet;

mso-level-text:\F0B7;

mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;

mso-ansi-font-size:10.0pt;

font-family:Symbol;}

@list l2:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l2:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l2:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l2:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l2:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l2:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l2:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l2:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l3

{mso-list-id:581336569;

mso-list-template-ids:-47290090;}

@list l4

{mso-list-id:788007822;

mso-list-template-ids:-478512566;}

@list l4:level1

{mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l4:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l5

{mso-list-id:900554225;

mso-list-template-ids:1027139964;}

@list l5:level1

{mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l5:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l5:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l5:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l5:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l5:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l5:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l5:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l5:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l6

{mso-list-id:1035543589;

mso-list-template-ids:-809847532;}

@list l7

{mso-list-id:1132556220;

mso-list-template-ids:-1914386832;}

@list l8

{mso-list-id:1290891611;

mso-list-template-ids:-295510440;}

@list l8:level1

{mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l8:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l8:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l8:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l8:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l8:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l8:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l8:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l8:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l9

{mso-list-id:1382944425;

mso-list-template-ids:1475271118;}

@list l10

{mso-list-id:1420448336;

mso-list-template-ids:22684130;}

@list l10:level1

{mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l10:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l10:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l10:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l10:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l10:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l10:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l10:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l10:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l11

{mso-list-id:1463235193;

mso-list-template-ids:165843270;}

@list l11:level1

{mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l11:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l11:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l11:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l11:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l11:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l11:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l11:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l11:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l12

{mso-list-id:1468551459;

mso-list-template-ids:-645106998;}

@list l13

{mso-list-id:1584679131;

mso-list-template-ids:2141624586;}

@list l13:level1

{mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l13:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l13:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l13:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l13:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l13:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l13:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l13:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l13:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l14

{mso-list-id:1608466576;

mso-list-template-ids:1223095538;}

@list l14:level1

{mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l14:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l14:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l14:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l14:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l14:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l14:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l14:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l14:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l15

{mso-list-id:1617366807;

mso-list-template-ids:508488734;}

@list l16

{mso-list-id:1698385733;

mso-list-template-ids:-1236913794;}

@list l17

{mso-list-id:1727339069;

mso-list-template-ids:-1375449252;}

@list l17:level1

{mso-level-number-format:bullet;

mso-level-text:\F0B7;

mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;

mso-ansi-font-size:10.0pt;

font-family:Symbol;}

@list l18

{mso-list-id:1816868350;

mso-list-template-ids:1107616030;}

@list l18:level1

{mso-level-number-format:bullet;

mso-level-text:\F0B7;

mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;

mso-ansi-font-size:10.0pt;

font-family:Symbol;}

@list l18:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l18:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l18:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l18:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l18:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l18:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l18:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l18:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l19

{mso-list-id:1902863286;

mso-list-template-ids:740079056;}

@list l19:level1

{mso-level-number-format:bullet;

mso-level-text:\F0B7;

mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;

mso-ansi-font-size:10.0pt;

font-family:Symbol;}

@list l20

{mso-list-id:2009823496;

mso-list-template-ids:429947952;}

@list l21

{mso-list-id:2077123861;

mso-list-template-ids:641873498;}

@list l21:level1

{mso-level-tab-stop:.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l21:level2

{mso-level-tab-stop:1.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l21:level3

{mso-level-tab-stop:1.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l21:level4

{mso-level-tab-stop:2.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l21:level5

{mso-level-tab-stop:2.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l21:level6

{mso-level-tab-stop:3.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l21:level7

{mso-level-tab-stop:3.5in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l21:level8

{mso-level-tab-stop:4.0in;

mso-level-number-position:left;

text-indent:-.25in;}

@list l21:level9

{mso-level-tab-stop:4.5in;

mso-level-number-position:left;

text-indent:-.25in;}

{margin-bottom:0in;}

-->

</style>

<style>

/* Style Definitions */

table.MsoNormalTable

{mso-style-name:"Table Normal";

mso-tstyle-rowband-size:0;

mso-tstyle-colband-size:0;

mso-style-noshow:yes;

mso-style-parent:"";

mso-padding-alt:0in 5.4pt 0in 5.4pt;

mso-para-margin:0in;

mso-para-margin-bottom:.0001pt;

mso-pagination:widow-orphan;

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

<o:DocumentProperties> <o:Author>IBM_User</o:Author> <o:LastAuthor> </o:LastAuthor> <o:Revision>4</o:Revision> <o:TotalTime>211</o:TotalTime> <o:Created>2004-04-05T14:13:00Z</o:Created> <o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>5026</o:Words> <o:Characters>28651</o:Characters> <o:Company>IBM</o:Company> <o:Lines>238</o:Lines> <o:Paragraphs>67</o:Paragraphs> <o:CharactersWithSpaces>33610</o:CharactersWithSpaces> <o:Version>10.4219</o:Version> </o:DocumentProperties></xml><![endif]--><!--[if gte mso 9]><xml>

<w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:Compatibility> <w:ApplyBreakingRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument></xml><![endif]-->

OpenPegasus Enhancement

Proposal (PEP)<o:p></o:p>

PEP #: 368

Title: Release

Notes for OpenPegasus version 2.14.0

Created: 20 November 2014

Authors: Karl

Schopmeyer

Status:  draft

Version History:

<tbody>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

<o:p> </o:p>

</td>

</tr>

0.99<o:p></o:p>

</td>

12 Nov. 2014

</td>

Karl Schopmeyer

</td>

Initial Submission for review<o:p> </o:p>

</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center" height="21">1.00

</td>

<td style="padding: 0.75pt;" align="center" height="21">14 March 2015

</td>

<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer

</td>

<td style="padding: 0.75pt;" height="21">Update to finish the document (approved as bug 9684)

</td>

</tr>

</td>

</td>

</td>

</td>

</tr>

<tr>

</td>

</td>

</td>

</td>

</tr>

</tr>

</tbody>

</table>

<hr>

Abstract: This document defines the release notes that support release 2.3.0 of

the Pegasus platform

<hr>

<h2>Availability of the Release</h2>

The Pegasus 2.3 release is available as a source release in both ZIP and TAR formats.

The release can be downloaded from the OpenPegaus Web site at www.openpegasus.org.

In addition, the release is available through Pegasus CVS as the branch tag

Abstract: This document defines the release notes for the 2.14.0

RELEASE_2_3_0-branch. This defines the current released version of Pegasus 2.3 . In

release of the OpenPegasus CIM Server. The purpose of this PEP is to

addition, the following tags exist for the release. RELEASE_2_3_0-root which defines the

summarize the characteristics of this release, point to other

initial release point of Pegasus 2.3 and the point at which it branched from the trunk..

documentation that defines the release in more detail, and provide

Other tags may exist to mark release candidate snapshots, etc. These will be announced on

additional information about this release that is not available in the

the web site and the Pegasus mailing list.

other Pegasus documentation.

<h2 style="margin-bottom: 1px;"><o:p> Contents</o:p></h2>

<ol>

<li><a href="#Availability_of_this_Release_">Availability of this

Release</a></li>

<li><a href="#Functionality_of_This_Release">OpenPegasus Functionality

of This Release</a></li>

<li><a href="#Compatibility_Considerations_">Compatibility

Considerations</a></li>

<li><a href="#Notes_on_Specific_OpenPegasus">Notes on Specific

OpenPegasus Functionality</a>

</li>

<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship to

CIM/WBEM Standards</a></li>

<li><a href="#Supported%20Platforms">OpenPegasus Supported Platforms</a></li>

<li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance

with DMTF Specifications</a></li>

<li><a href="#PEGASUS%20Bugs">OpenPegasus Bugs</a></li>

<li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus

Release

Control and Version Definition Documentation</a></li>

<li><a href="#General%20Documentation">General Documentation</a></li>

</ol>

<h2>Availability of this Release</h2>

This release is available in a number of forms including:

<ul>

<li>Source release in both ZIP (and ZIP EXE) and TAR formats.

These can be downloaded from the OpenPegasus

Web site at <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li>

<li>OpenPegasus source RPMs on the OpenPegasus web site.. A

source RPM is  available on the OpenPegasus web site that can be

used to build binaries for most LSB-compliant RPM-based Linux

distributions and versions.</li>

<li>TheOpenPegasus CVS repository. The CVS tags representing this

release and subsequent snapshots that are made available in the

Pegasus CVS are defined on the OpenPegasus CVS repository web page

(see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

CVS

page</a> for information) using the tags defined on the <a href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release

snapshots

page</a> and the <a title="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:openpegasusreleasestatus">OpenPegasus

WIKI Release Status Page</a>.</li>

</ul>

The instructions for acquiring the released code are on the WEB site. Installation

The instructions for acquiring the released code are on the <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus

instructions are part of the readme in the root of the source tree.

WEB

site</a> and the <a title="OpenPegasus WIKI" href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">OpenPegasus

WIKI</a>. Installation instructions are part of the README in the root

of the Pegasus source tree.

</div>

<h2>OpenPegasus Functionality for this Release</h2>

OpenPegasus overall status by release is defined by  a <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature

Status WEB Page</a> that is available on the OpenPegasus web site

.  That web page shows the Pegasus users and developers the status of

the various features found in OpenPegasus using a simple color coded key

(white, red, yellow, green) and a description of each feature.

The OpenPegasus project is currently not providing binary releases. However, binary

OpenPegasus 2.14.0 is a major release, extending the previous Pegasus

releases may be available of selected ports and are documented on the OpenPegasus web

release in selected areas as described in these release notes.

site.

There may be point releases to the Pegasus 2.3 release and these will be announced on the

NOTE: OpenPegasus releases are categorized as follows:

Pegasus web site.

<ul>

<li>First number of version changes (ex. 2.x.x to 3.0.0) -  Major

release includes major functionality change and  incompatible

behavior changes and/or incompatible public API changes,

<h2>Functionality of This Release</h2>

</li>

<li>Second number changes (ex 2.12.0 2.14.0) -  Minor Release and

The overall level of functionality in the Pegasus environment effective with this

includes new functionality but maintains behavior and public API

release is as follows:

compatibility,

</li>

CIM Server

<li>3rd number changes (2.14.0 to 2.14.1) - Revision(also called point

release) release and only includes bug fixes.</li>

CIM Operations over HTTP<ol>

<li>    Class Operations (getClass, deleteClass, modifyClass, enumerateClass,

enuerateClassNames) - Operational</li>

<li>    Qualifier Operations - Operational</li>

<li>    Instance Operations (getInstance, deleteInstance, modifyInstance,

enumerateInstance, enumerateInstanceNames, getProperty, setProperty) - Operational</li>

<li>    Association Operations (references, referencenames, associators,

associatornames - Operational </li>

<li>    Methods- Operational</li>

<li>    Query operation (Not Operational)</li>

</ol>

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. The Pegasus sever can be used as an Indication client. 

The Client indication  API support is complete but the interfaces are marked

experimental for version 2.3 because this is the first version of Pegasus in which these

APIs were available.

Query Language

The query language today is based on WQL and is implemented and used for filters.

However, the executeQuery operation has not been implemented pending the availability of a

standard DMTF Query language.

Class Repository

XML based file/directory Class repository.

Instance Repository

XML based file/directory Instance repository.  The instance repository is used as

the default repository unless a flag is set disabling this repository for client

operations.

Security<ol>

<li>Basic Security (Note that Digest based security is not implemented)</li>

<li>SSL support - SSL is implemented in Pegasus using the OpenSSL libraries. Pegasus does

not provide the OpenSSL libraries but SSL can be used on any platform supported by

OpenSSL.</li>

</ol>

Platform Management Functions<ol>

<li>Configuration through the defined configuration parameters.</li>

<li>Daemon operation on all supported platforms</li>

<li>User management utilities</li>

<li>Provider management. The CIM Server provides dynamic registration of providers and

automatic load and unload functionality.</li>

</ol>

SLP Discovery

SLP support is enabled in the platform but is conditionally compiled with the default

to not compile it today pending further testing.

</blockquote>

Providers

There are a number of standard providers available in Pegasus release. This

includes providers in the following categories:

Internal Providers<ul>

<li>__Namespace provider - Serves the __Namespace class to allow manipulation of namespaces.</li>

<li>Subscription Classes Providers - These provide subscription, filter, and indication

handler processing.</li>

<li>Provider registration Providers - This provide registration of providers using the

PG_Provider classes.</li>

<li>ConfigProvider - Manages Pegasus configuraton information.</li>

<li>UserAuthProvider - Manages password, etc.</li>

<li>ShutdownProvider - Provides support for Pegasus shutdown.</li>

<li>Interop Provider - Supports many of the DMTF Interop Schema Classes including

CIM_Namespace, CIM_ObjectManager, etc. (Note that this provider is part of the SLP work

package so is not compiled as part of the default compile)</li>

</ul>

Generic Providers

Generic OperatingSystem provider. See the directory src/Providers/generic.

ALL changes for each release are documented in the

Test/Sample Providers

OpenPegasus bug data base by tagging each bug(keyword field of bug). 

See the directories src/Providers/TestProviders and src/Sample for more information

No change to Pegasus is committed with out this tag on the bug. Changes

about test and sample providers.

for this minor release are  tagged 2.14.0_APPROVED. All changes for

Managed System Providers

this minor release can be viewed through  this link to the

ComputerSystem, DNSAdmin, DNSService, Operating System, Process, Processor. For more

OpenPegasus bugzilla <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.14.0_APPROVED">

information on these providers see the documentation for each provider in the directory

Pegasus 2.14.0_APPROVED bug list. Bugs.  </a>Bugs marked as

src/Providers/ManagedSystem

enhancements can be reviewed through the this <a href="http://bugzilla.openpegasus.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=CIM+Server+Core&product=CIMClient+Application&product=CIMClient+DefaultCPlusPlus&product=CIMClient+Java-SNIA&product=CIMConsumer+DefaultCPlusPlus&product=CIMIndicationHandler&product=CIMListener+Dynamic&product=CIMListener+Standalone&product=CIMProvider+CMPI&product=CIMProvider+CMPIRemote&product=CIMProvider+DefaultCPlusPlus&product=CIMProvider+Instrumentation&product=CIMProvider+JMPI&product=CIMSchema&product=CIMServer+Administration&product=CIMServer+Administration+Command&product=CIMServer+Administration+Profiles&product=CIMServer+ProviderManagement&product=CIMServer+Repository&product=CIMServer+SLP&product=OpenPegasus+Build+System&product=OpenPegasus+Documentation&product=OpenPegasus+Security+Defects&product=OpenPegasusProject+Bugzilla&product=OpenPegasusProject+CVS&product=OpenPegasusProject+Website&product=PegasusCIMOM&product=PegasusGeneral&product=RPM+CIMServer&product=TestProduct&product=Unsupported&product=WMI+Mapper&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.14.0_APPROVED&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_severity&type0-0-0=equals&value0-0-0=enhancement">link

CIMOM Statistics Providers

to OpenPegasus bugzilla 2.14.0 enhancement bugs</a> .  Bugs fixed

IBMStatisticalData - This is an early version of the work that became

for subsequent revision releases (ex. 2.14.1) would also be viewed through

CIM_StatisticalData. It is similar to CIM_StatisticalData and provides the same data but

corresponding Bugzilla tags for each revisions (ex 2.14.1_APPROVED).

the structure of the Classes is slightly different.

</blockquote>

The major areas of development including both enhancements and bug fixes

for this release  were as follows. Note that the bugs listed

Linux Specific Providers

represent only those features incorporated in bugs without PEPS that are

considered enhancements, not all bugs incorporated in the release. For

more information access the PEP/BUG for each change defined below:

There are a number of providers in this category including DiskDrive, CDROMDrive,

Interrupt, IOPOrt, IPROute, NetworkAdapter, Operating System, PCI Controller, Processor,

Table of Major

ProviderData, ProviderSupport, SoftwareElement.  For more information about these

Changes this Release. Review  Bugzilla 2.14.0

providers see the documentation in the directory src/Providers/linux

Enhancements and approved(above) for a complete list

</blockquote>

CIM_Schema

<tbody>

The default CIM_Schema loaded with the Pegasus 2.2 release is the DMTF CIM 2.7 Final

release.  In addition, Pegasus includes a number of local classes defined for

<th bgcolor="#00ffff">Description of Change</th>

Pegasus.  These are visible in the Schemas directory.

Pegasus MOF Compiler

Pegasus implements a MOF compiler that can operate either at the client interface

(cimmof) or directly interfacing with a CIM repository (cimmofl).

The direct interface compiler is used primarily to provide an initial class/instance

repository. Note that use of cimmofl to manipulate instances in the repository bypasses

any provider that is registered to serve the instances and simply installs the instances

in the instance repository; this may result in corruption if providers are using the

repository.  Use of cimmofl to manipulate instances served by a registered providers

is therefore discouraged. Use of cimmof rather that cimmofl is encouraged.

Client Tools

Pegasus CIM Server Adminstration

<ol>

<li>cimuser - Manage Pegasus CIM server Users</li>

<li>cimconfig - Manage the Pegasus CIM Server configuration parameters</li>

<li>cimauth - Manage the CIM Server authorization characteristics. Today this is authorizing

users to namespaces.</li>

<li>cimprovider - Manage information about the providers.</li>

</ol>

Information client tools

These tools provide information on the objects managed by the

server.

<ol>

<li>tomof - output Classes and/or instance information in MOF or XML format.</li>

<li>dnsinfo - </li>

<li>ipinfo - Generates a set of standard information from the Network Schema.

Information generated varies by system because of the level of provider support.</li>

<li>osinfo - 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 differes from system to system</li>

</ol>

Test support Tools

<ol>

<li>Pegasus Unit tests (available through the "tests" option on the Pegasus make

files        </li>

<li>The Pegasus Test Suite (see the tests directory and the Pegasus/TestBuildMakeFile)</li>

<li>TestClient - Basic client for overall platform operation testing. </li>

<li>CGICLient - This client has not been completely update to version 2.2.</li>

<li>wbemexec - Test tool that sends/receives XML from XML input.</li>

<li>CLI - Command line interface for Client commands.</li>

<li>Benchmark Test - Introduced with Pegasus 2.3, a benchmark test environment is not

provided which includes both a client and provider component. See

src/clients/benchmarkTest for more information.</li>

</ol>

Pegasus Interface APIs

Details of the Pegasus public interfaces for release 2.3 is listed in PEP 96 available

from the web site(www.openpegasus.org). This document is the authorative 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 release 2.3 (clients and providers compiled to

the Pegasus 2.1 or 2.2 interfaces should be compatible with Pegasus 2.3 without

compilation)  but there have been extensions and new interfaces added for release 2.3

  The public interfaces includes the following major functions

<ol>

<li>Client APIs</li>

<li>Provider APIs</li>

<li>CIM Objects</li>

<li>CIM Listener (experimental for Pegasus 2.3). These are compiled only if the

PEGASUS_USE_EXPERIMENTAL_INTERFACES flag is set.</li>

<li>SLP Client (experimental for Pegasus 2.3). These are compiled only if the

PEGASUS_USE_EXPERIMENTAL_INTERFACES flag is set.</li>

</ol>

The functions are documented in their respective header files and HTML documentation

based on the information in the header files extracted with the doc++ tool will be

available on the OpenPegasus web site.

WMI Mapper

A version of of the Pegasus platform that specifically communicates with Microsoft WMI

implementations and interfaces with WMI object is provided as a separately compilable code

set in the CVS.

<h2>Supported Platforms</h2>

Each Pegasus release lists as supported platforms those hardware/software platforms

that have recognized ports for the Pegasus code base including a maintainer for the

platform that will be willing to regularly assure that the port is maintained as the

Pegasus code base is changed.  Pegasus may be operable on other platforms (ex.

Windows 98) but without a group to provide the role of test and maintenance, the Pegasus

project cannot assure operation. The supported platforms for current release are:

<tr>

<td width="169" bgcolor="#99FF99">Platform and OS</td>

<td width="231" bgcolor="#99FF99">Compilers</td>

</tr>

<tr>

<td width="231">VisualAge C++ Version 5.0.2.3</td>

</tr>

<tr>

<td>Support only TLS V1.2 Protocol for Security Compliance

</tr>

</td>

<tr>

<td width="169">Linux Itanium</td>

</tr>

<tr>

<td width="169">Linux IA-32</td>

<td width="231">gcc (versions 2.9x and 3.xx)</td>

</tr>

<tr>

<td width="169">Windows 2000</td>

<td width="231">Microsoft Visual C++ Ver 6 and Microsoft .Net compiler Version V7 and 7.1</td>

</td>

<td>Support DMTF defined Pull Operations (per DMTF

specification DSP 0200 and 0201). This is a major extension to

OpenPegasus and implements all of the DMTF defined pull operations with

NO changes to providers. This includes extentions to both the server

and client code as well as new operations implemented in cimcli to

allow execution of pull operations and pull operations with FQL.

</td>

</tr>

<tr>

<td width="169">Windows XP</td>

<td width="231">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version V7 and 7.1</td>

</td>

<td>Fix issue causing failures when cmpi returned

instances that do not have a class. This was causing problems with the

Jobs profiles which specifically return information for which there is

no class.

</td>

</tr>

<tr>

<td width="169">Mac OS X/Darwin PPC</td>

<td width="231">gcc (version 3.3)</td>

</td>

</tr>

<td>Dynamic disable of the reliable Indication feature

</table>

</td>

Further information regarding Pegasus support on IBM platforms can be found at: <a

href="http://publib.boulder.ibm.com/eserver/v1r1/en_US/info/ciminf%20o/eicahkickoff.htm">http://publib.boulder.ibm.com/eserver/v1r1/en_US/info/ciminf

o/eicahkickoff.htm</a>. This site is expected to have information available starting in

December.

Further information regarding Pegasus support on HP platforms can be found at: <a

href="http://www.hp.com/large/infrastructure/management/wbem/">http://www.hp.com/large/infrastructure/management/wbem/</a>.

<h2>Conformance with DMTF Specifications</h2>

Pegasus tries to conform to the CIM specifications.  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 differences.  As of Pegasus 2.3, some of the

differences include the following:

1. Provider Registration - Pegasus supports registration through a set of Provider

registration classes  similar to the CIM Classes defined as experimental in the CIM

2.8 preliminary Schema release and does not support the Provider Qualifier. Note that

there are differences that must still be worked out between the Pegasus PG provider

registration classes and the CIM classes as part of the move to release of the CIM

classes.

2. Indications -Pegasus supports process indications but does not include any specific

support for lifecycle indications.

3. Interop Schema - Today Pegasus provides alternatives to some of the classes in the

Interop Schema including CIM_StatisticalData.

4. execQuery operaiton - Today Pegasus does not support the execQuery pending the

availability of a standard for the query language.

5. Pegasus differs from some other implementations in the delivery of instance and

class qualifiers on some operations.

6. Pegasus has not implemented the alias functions defined in the CIM specification in

the MOF compiler.

<h2>Changes in this Release</h2>

The development and release of each version of Pegasus is defined and controlled

through Pegasus PEP documents.  PEP 57 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.

In general, the changes implemented for this release were:

<ol>

<li>Introduction of platform globalization. </li>

<li>Introduction of a listener API</li>

<li>Introduction of SLP (still experimental and by default not compiled in the 2.3.0

release)</li>

<li>Introduction of a new pluggable Provider Manager (still experimental and by default not

compiled in the 2.3.0 release)</li>

<li>Introduction of extensive changes to the HTTP monitor (still experimental and not

compiled in the 2.3.0 release)</li>

<li>Incorporation of a Java Client based on the SNIA code base.</li>

<li>Additional Indication Handlers (SNMP)</li>

<li>Improvements to indication handling.</li>

</ol>

Note that there were a number of objectives that were not completely achieved

including:

<ol>

<li>SLP integration - This code is in place but is compiled only with a conditional compile

flag. This code can be enabled by setting the environment variables PEGASUS_SLP_ENABLE and

PEGASUS_SLP_CLASSES and recompiling Pegasus.</li>

<li>Pluggable provider manager - This was a major objective but because the code changes

were extensive and released very late in the developement cycle of 2.3, both the old and

the new provider managers are maintained in the release AND the old provider manager is

defined as the default compile.  To compile and run with the new pluggable provider

manager functions the user must set a compile flag (ENABLE_PROVIDER_MANAGER2).  NOTE:

It is the intention of the Pegasus project to move to the new provider manager as soon as

possible.</li>

<li>HTTP Monitor enhancements - As with the Pluggable Provider Manager, it was the intention

to incorporate a number of enhancements to the HTTP monitor.  Again because the time

in the development phase when they were submitted, the project team elected to release 2.3

with the existing monitor as the default compile but with the code for both monitors. It

is the intention to move to the new monitor as soon as possible and users are free to work

with either implementation.  To compile and run with the new monitor use the flag

PEGASUS_MONITOR2.</li>

</ol>

The set of PEPs defined for this release is summarized below along with the final

implementation status because not all of the PEPs originally defined for this version were

implemented:

<tr>

<td width="25%" bgcolor="#00CC99" height="18">PEP Description</td>

<td width="25%" bgcolor="#00CC99" height="18">Status</td>

<td width="25%" bgcolor="#00CC99" height="18">Comments</td>

</tr>

<tr>

<td style="vertical-align: top; text-align: center;">9812

<td width="25%" height="18">Unicode Support in Infrastructure</td>

</td>

<td width="25%" height="18">Implemented</td>

<td style="vertical-align: top;">FootPrint Reduction

</td>

</tr>

<tr>

<td width="25%" height="18">Unicode Support in Infrastructure</td>

</td>

<td width="25%" height="18">Implemented</td>

<td style="vertical-align: top;">Generate mini-CA and signed certificate instead of self-signed certificates</td>

</tr>

<tr>

<td width="25%" height="18">Provider Manager Interface - Multiple provider support</td>

</td>

<td width="25%" height="18">Implemented - but requires compile flag to integrate.</td>

<td>Include cimcli in release packages

</td>

</tr>

<tr>

<td width="25%" height="18">Provider Manager Interface, Pluggable provider manager

</td>

configuration</td>

<td style="vertical-align: top;">support HTTP Negotiate Authentication in OpenPegasus

<td width="25%" height="18">Implemented - see above.</td>

</td>

</tr>

<tr>

<td width="25%" height="18">Provider Manager Interface, pluggable provider manager.</td>

</td>

<td width="25%" height="18">Implemented - see above.</td>

<td>Reduce overhead of use of PAM by use of a

SessionCookie.  This also introduces a new runtime configuration

parameter to control the session timeout

</td>

</tr>

<tr>

<td width="25%" height="18">Secure connections between CIM Listener and CIM server</td>

</td>

<td width="25%" height="18">Implemented</td>

<td>Incorporate FQL (Filter Query Language) support for the pull operations (Experimental)

</td>

</tr>

<tr>

<td width="25%" height="18">SNMP Mapper Indication Handler</td>

</td>

<td width="25%" height="18">Implemented</td>

<td>Several minor extension to the APIs (ex. extend String class methods)

</td>

</tr>

<tr>

<td width="25%" height="18">Indication Consumer registration</td>

</td>

<td align="left" width="75%">Improve CLANG compiler support

</td>

</tr>

<tr>

<td width="25%" height="18">CIM Listener Client API, Libraries, SDK</td>

</td>

<td width="25%" height="18">Implemented - Experimental</td>

<td>Initial CIMRS and Web Admin support (This is Experimental and the CIMRS function will be modified for CIMRS V2 specification)

</td>

</tr>

<tr>

<td width="25%" height="14">Indication Subscription Performance Enhancements</td>

</td>

<td width="25%" height="14">Implemented</td>

<td>Correct old error in the Memory Resident

Repository logic. This logic did not work in several previous versions

because of the issues documented in this bug.

</td>

</tr>

<tr>

<td width="25%" height="14">SLP support</td>

</td>

<td width="25%" height="14">Implemented - Optional compile</td>

<td>Update default CIM Schema to CIM 2.41

</td>

</tr>

<tr>

<td width="25%" height="14">Interop Schema provider support</td>

</td>

<td width="25%" height="14">Implemented - Optional compile</td>

<td>Add scripts for load testing of OpenPegasus (see the directory src/Unsupported/Scripts/UinxLoadTests)

</td>

</tr>

<tr>

<td width="25%" height="14">Change to use CIM_Statistics rather than IBM Statistics class

</td>

for Interop statistics</td>

<td align="left" width="75%">Fix issue with the configuration parameters for numberOfTraceFiles and traceFileSizeKbytes.

<td width="25%" height="14">Delayed for future work</td>

</td>

</tr>

<tr>

<td width="25%" height="14">Java implementation of CIM Client and Listener Interface</td>

</td>

<td width="25%" height="14">Included in Pegasus based SNIA OpenCimom Java Classes.</td>

<td>

</td>

</tr>

<tr>

<td width="25%" height="14">Benchmark test utility</td>

</td>

<td width="25%" height="14">Implemented</td>

<td>

</td>

</tr>

<tr>

<td width="25%" height="14">SSL certificate verification callback enhancement</td>

</td>

<td width="25%" height="14">Implemented</td>

</td>

</tr>

<tr>

<td width="25%" height="14">WMI mapper changes on authentication process</td>

</td>

<td width="25%" height="14">Implemented</td>

<td>

</td>

</tr>

<tr>

<td width="25%" height="14">Support CIM Schema 2.8 preliminary</td>

</td>

<td width="25%" height="14"> CIM 2.7 is the default tested schema but the code was

<td>

added to support 2.8 preliminary specifically becasue of requirements from SNIA.</td>

</td>

</tr>

<tr>

<td width="25%" height="14">WMI Mapper - local connection enhancements</td>

</td>

<td>

</td>

</tr>

<tr>

<td width="25%" height="14">Default instance provider</td>

</td>

<td width="25%" height="14">Implemented</td>

<td>

</td>

</tr>

<tr>

<td width="25%" height="14">Monitor Optimization</td>

</td>

<td width="25%" height="14">Implemented but with compile flag. Default is old monitor</td>

<td>

</td>

</tr>

<tr>

</tbody>

</table>

<td width="25%" height="14">Configuration Property Table Enhancement</td>

<td width="25%" height="14">Implemented</td>

The status of several components of Pegasus functionality change status

between Pegasus versions. <a name="comtag_116">Features

that

have

changed status can be identified by a change in color from the

previous release to this release</a> on the <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature

Status WEB Page</a>.

<h2><a name="Notes_on_Specific_OpenPegasus"></a>Notes on Specific

OpenPegasus Functionality Changes</h2>

This section documents specific issues that the OpenPegasus team feels are

important to OpenPegasus users with the current release (and possibly

older releases).

<h3>Add new RunTime Variables to control trace file size and Rotation(OpenPegasus

2.13.0)(bug 9550)</h3>

As of OpenPegasus 2.14.0, several new runtime variables have been added that can be manipulated with the cimconfig utility:

* pullOperationsMaxObjectCount -

Defines the maximum allowed value of the maxObjectCount argument on

open and pull operation requests which defines the maximum number of

instances or paths that will be returned in a single open or pull

response. Requests that have a value higher than this configuration

parameter will be rejected. The default is10000. This may be set to any

value between 1 and 10000.

* pullOperationsDefaultTimeout

- Defines the default timeout in seconds between the time a pull open

response is sent by the server and a subsequent pull or close response

received from the client if the value is not set by the client in the

request. This can be set to any value between 1 and 90 seconds.

Default=30

* pullOperationsMaxTimeout

- Defines the maximum allowable value for the maxTimeout argument that

is part of the pull open... (openEnumerationInstances, etc) requests.

Any value higher than the value set in this configuration parameter

will cause the request to be rejected by the CIMServer. The default=90

seconds. TODO - Explain more on all of these above

* httpSessionTimeout -

Allows using a cookie to temporarily bypass the PAM authentication in

favor of the cookie provided by the server during a single session.

This is a performance enhancement.  If this variable is set to

zero (default) the cookie bypass is disabled, the server will not send

nor accept the id cookie.  If set to

an integer, a client session will maintain the cookie for the number of

seconds defined by the value of this variable. Enabled with a build

parameter PEGASUS_ENABLE_SESSION_COOKIES.

* sslBackwardCompatibility

- Limits OpenPegasus support to TLS 1.2/OpenSSL1.01. Can be set to

allow backward compatibility with older versions of TLS/OpenSSL.

The following sections describe in more detail some of the more

significatn changes in this release as well as carrying forward some of

the same information for the last release to be sure users are aware

what these changes affect.

<h3>DMTF Pull Client operations and FQL Query Language (OpenPegasus 2.14.0)</h3>As

of DMTF DSP0200 version 1.4, new client operations (generally named the

pull operations have been part of the CIM/XML protocol). This consists

of a set of new operations (open..., pull..., close) that allow getting

enumerations, associations, references (and their corresponding name

operations) as a sequence

of operations (an enumeration sequence) rather than a single monolithic operation.

This will provider several advantages including:

1. Better control of client memory since the client can determine the size of each response.

2. Clearly separates the return of errors from data.

Pegasus 2.14 supports all of these operations in both in the CIM/XML

client and the server. For more information on the implementation and

use of

these operation see the following documents:

1. OpenPegasus <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:workgroups:pulloperationsupportworkgroup:pull_operation_support_work_group">Wiki page</a> for this project.

2. PEP documenting the Pull operations and FQL

<h3>HTTP Sessions(OpenPegasus 2.14.0)</h3>Allows using a cookie to

enhance performance of PAM.  This function is enabled with the

build varaible  PEGASUS_ENABLE_SESSION_COOKIES. When

the option is enabled, the OpenPegasus CIM server will

use HTTP cookies for session management (RFC 6265).

After a successful client authentication the client is given a cookie. The

client is then not asked for re-authentication as long as it provides the

same cookie in all subsequent requests and until the session expires. Session

expiry is configurable using httpSessionTimeout configuration option.

Nothing changes for clients that do not support HTTP cookies (RFC 6465) -

their requests are authenticated as usual, either using Basic or Negotiate

authentication mechanisms.

The timeout for a session is determined by the runtime parameter httpSessionTimeout. If this runtime parameter is set to zero the HTTP cookies option is disabled.

This option has proven to represent a significant improvement in performance over using PAM for every client operation.

<h3>WEBAdmin (OpenPegasus 2.14.0)</h3>OpenPegasus has

included on an experimental basis a web server that acts as an

adminstration tool to replace the command line tools.  This option

presents the

same information as the major command line tools as web pages so that

parameters can be modified without using the command line tools. 

It is compiled by

default and may be disabled with the build option

PEGASUS_ENABLE_PROTOCOL_WEB=false. See the file readme.webadmin in the

OpenPegasus

source tree for more detailed information on using WEBAdmin.

Note: This option is considered experimental for 2.14

<h3>Using GCC 4.7 Compiler on Linux OS (OpenPegasus 2.13.0)

</h3>

As of 2.14.0, OpenPegasus has been updated to replace the custom atomic

operations with GCC built-in atomic operations if GCC version 4.7 or

greater is used as the compiler.  It is recommended that if possible

this version of the GCC compiler be used since the change provides

significant performance improvements.

<h3>OpenPegasus and OpenSLP V 2.0 (OpenPegasus 2.13.0)</h3>

As of 2.13.0, OpenPegasus slp fully supports IPV6  and has been

tested with OpenSLP 2.0 (Recently released by <a href="http://openslp.org">OpenSlp.org</a>)

While testing OpenPegasus with OpenSLP 2.0 the OpenPegasus team found two

issues with this version of OpenSLP.  The patches documented below

allow this version of OpenSLP to work with OpenPegasus

1) SLPReg used TCP connection previously, but it now uses UDP. Therefore,

a BUFFER_OVERFLOW exception occurs.  This is because UDP cannot

handle attribute size greater than network MTU size. In such cases,

according to the specification, OpenSLP should automatically switch to

TCP.  Since this has not been implemented in OpenSlp 2.0, the

workaround used by OpenPegasus to force use of TCP may be found at <a title="http://sourceforge.net/p/openslp/bugs/139/" href="http://sourceforge.net/p/openslp/bugs/139/">http://sourceforge.net/p/openslp/bugs/139/</a>.

2) On Windows, slpd service fails to start when IPV6 is enabled and throws

the error message "Error 1067: the process terminated unexpectedly". More

details and the fix for this issue are in the bug <a href="http://sourceforge.net/p/openslp/bugs/140/">http://sourceforge.net/p/openslp/bugs/140/</a>.

<h3>Interop namespace name (OpenPegasus 2.13.0)</h3>

Effective with the release of OpenPegasus  2.13 the "interop"

namespace support for existing or

older repositories which used

"root/PG_InterOp" has been added via a new option in the "reupgrade"

utility. Users with existing repositories may use this option to migrate

the repository from "root/PG_InterOp" to

"interop" namespace.  See <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9414" title="RESOLVED FIXED - enhance repupgrade to support "interop" namespace">bug

9414</a> (PEP304) for

details.

For this to work, the build  option "PEGASUS_INTEROP_NAMESPACE" has

to be

set to "interop". Only then will the "-i" option in repupgrade be enabled.

Once the repository is upgraded with "-i" , the namespace

"root/PG_InterOp"

will cease to exsist. Clients using "root/PG_InterOp" must now use

"interop".

Prior to version 2.12 OpenPegasus used an OpenPegasus internal variable to

define "root/PG_InterOp" as the name for the OpenPegasus namespace with no

defined way to change this variable.  Note that an unsupported method

involving editing one file and rebuilding OpenPegasus was defined as a

workaround in the <a href="file:///home/kschopmeyer/dev/pgogbug9611releasenotes/pegasus/%20https://wiki.opengroup.org/pegasus-wiki/doku.php?id=faq:openpegasus_build_and_installing">OpenPegasus

wiki faq</a>s.

However, since the definition of a standard name for this namespace in

DMTF and SNIA specifications ("interop" or "root/interop" with "interop"

being the preferred alternative) the use of  "root/PG_InterOp" has

become an issue. Support for forward-compatibility is a fundamental design

principle for the OpenPegasus project. As a community, our goal is for

well-behaved OpenPegasus providers or clients, using only the externally

defined OpenPegasus interface, to continue to work with each version

upgrade of OpenPegasus.

Effective OpenPegasus 2.12.0 a new build variable was defined 

(PEGASUS_INTEROP_NAMESPACE) which allows an OpenPegasus builder to define

an alternate name for the Interop namespace to either "interop" or

"root/interop" (ex. PEGASUS_INTEROP_NAMESPACE = interop).  Once this

build variable is defined and OpenPegasus compiled, the actual name of the

interop namespace is what was defined in this varaible and all components

of OpenPegasus use this as the interop namespace name include the complete

OpenPegasus test suite.  The only name for the interop namespace will

be the name defined through this build variable.  This is the logical

approach for implementations starting a new repository.

In order to supexport PEGASUS_CLIENT_TRACE=keyword:keywordport users with

existing repositories, in 2.13.0,  migration of existing repositories

was integrated into the "repupgrade" utility to allow existing OpenPegasus

environments to smoothly move the server from use of the old name 

for the interop namespace "root/PG_InterOp" to 

the prefered name "interop".

NOTE: If the interop namespace

name is redefined with PEGASUS_INTEROP_NAMESPACE clients using the

"root/PG_InterOp" namespace will not connect with the updated version of

OpenPegasus. The OpenPegasus team searched for a solution to the issue

supporting the old and new name at the same time and concluded that there

were so many issues that it could not effectively be done.

<h3>Configure Script to Control OpenPegasus Builds (OpenPegasus

2.13.0)(Bug 9592)</h3>

OpenPegasus is moving from the use of environment variables to a configure

script to control build.  This is both to make it easier to define

the build variables, etc. and to be more compatibile with the Linux/Unix

standard build environment.  However, because OpenPegasus must build

on a number of platforms that do not support the full Linux/Unix

configuration tool set, this is an OpenPegasus defined configure

script.  The first very experimental version is part of OpenPegasu

2.13.0 but this version has a number of limitations (see the OpenPegasus

Bugzilla) and will be expanded in the next versions of OpenPegasus.

The goal is to replace the setting of most of the OpenPegasus build

environment variable with options in the pegasus/configure script where

those options are comatible with the Linux standard for defining configure

options and those options control the entire build process including placement

of output and choice of build options.

<h3>Tracing Client Requests and Responses(OpenPegasus2.13.0)</h3>

OpenPegasus has

long contained a hidden build controlled function to allow tracing at

the client through an environment variable

(PEGASUS_CLIENT_TRACE_ON).  In 2.13.0 this was a) make a permanent

part of of the environment (Bug 9564) and the calling convention

slightly changed

to make it simpler to use. The original format for the

environment variable was:

<pre class="bz_comment_text" id="comment_text_1">export PEGASUS_CLIENT_TRACE=keyword:keyword where the keyword was "con" | "log" | "both" This was changed to: keyword:keyword separately define Client input and output keyword: Client Input only :keyword Client Output Only keyword Client Input and output defined by keyword</pre>

so that the normal setup for a console output trace would be

<pre> export PEGASUS_CLIENT_TRACE=con</pre>

<h3>Information on IPV6 Support and OpenPegasus(PEP 291)(OpenPegasus

2.7.0)</h3>

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but

it was felt that the information below was worth repeating in subsequent

Release Notes

IPv6 Support for OpenPegasus is documented in

PEP 291</a>.

The IPv6 support in OpenPegasus is controlled by the PEGASUS_ENABLE_IPV6

build variable. The default for this variable is "true"; setting this to

'false' before building OpenPegasus will disable the IPv6 support.

The following subsections provide some information on IPv6 support for the

Linux and Windows platforms. Note that in the 2.6.1 release there is no

automatic run-time detection of IPv6 support on a platform by OpenPegasus.

If you build with PEGASUS_ENABLE_IPV6=true, your platform must support

IPv6 or you will get a build failure (missing header files), a run-time

bind() failure, or possibly some other failure. This applies to both the

CIM Server and Listener components. For more information on IPv6 support

for your specific platform, refer to the documentation for that platform.

All OpenPegasus externals that support eitcompilerher a hostname or an IP

address as input have been updated to allow an IPv6 address to be

specified. If the required input is just an IP address (eg. no optional or

required port number), then the IPv6 address must be specified without

brackets. For example, the OpenPegasus osinfo client (which returns

information about the OS running on a host system) takes separate host and

port options. In this case a host with an IPv6-configured network

interface would be specified as:

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>osinfo -h 3ffe:1:2:1 -p 5988</big></div>

But the cimcli command, which takes an optional "location" option

including an optional port number, requires the IPv6 address to be

delimited with brackets, for example:

<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns -l

[3ffe:1:2:1]</big></div>

or

<div style="margin-left: 40px;"><big>cimcli

ns -l [3ffe:1:2:1]:5989</big>

</div>

For more information on specifying IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF

RFC

2373 - IP Version 6 Addressing Architecture</a> and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF

RFC 2732 - Format for Literal IPv6 Addresses in URL's</a>.

<h4>IPv6 on Linux</h4>

Modern Linux distributions already contain IPv6-ready kernels, the IPv6

capability is generally compiled as a module, but it's possible that this

module is not loaded automatically on startup.

Note: you shouldn't use

kernel series 2.2.x, because it's not IPv6-up-to-date anymore. Also the

IPv6 support in series 2.4.x is no longer improved according to

definitions in latest RFCs. It's recommend to use series 2.6.x now.

To check whether your current running kernel supports IPv6, take a look

into your /proc filesystem. The entry /proc/net/if_inet6 must exist. A

short automated test looks like:

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>test -f /proc/net/if_inet6 && echo "Running

kernel is IPv6 ready"</big></div>

For more iSchema version default update to CIM 2.36nformation on enabling

IPv6 in the Linux kernel and configuring network interfaces, refer to <a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux

Documentation Project's IPv6 HOWTO</a>.

Warning: There is currently an

open issue with RedHat to address a problem that is seen intermittently on

RHEL5 and SLES10 systems. This problem is described in

<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus

bug 6586</a> and <a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat

bug

248052</a>, and manifests itself as an intermittent IPv6

socket failure. You should be aware that OpenPegasus with IPv6 enabled may

be significantly impacted in these environments.

<h4>IPv6 on Windows</h4>

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.

On Windows XP, you can use the ipv6.exe

tool to install, uninstall, and query your IPv6 configuration. For

example:

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>ipv6 install

ipv6 if</big></div>

Windows Vista and Windows Server 2008 support an integrated IPv4 and IPv6

implementation known as the Next Generation TCP/IP stack. Note that the

OpenPegasus IPv6 support has not yet been tested on Windows Vista or

Windows Server 2008.

For more information on installing, configuring, and using IPv6 on Windows

platforms, refer to the document <a href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx">IPv6 for Microsoft Windows: Frequently Asked Questions</a>.

<h4>Testing  OpenPegasus IPv6 support</h4>

As part of the OpenPegasus automated tests, the TestClient, g11ntest, and

IndicationStressTest test clients were modified to run tests using the

IPv6 loopback address (::1) if PEGASUS_ENABLE_IPV6=true.

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:

<big style="font-family: monospace;"> osinfo -h ::1</big></div>

<h2><a name="Compatibility_Considerations_">OpenPegasus Compatibility

Considerations</a></h2>

Support for forward-compatibility is a fundamental design principle for

the OpenPegasus project. As a community, our goal is for well-behaved

OpenPegasus providers or clients, using only the externally defined

OpenPegasus interface, to continue to work with a minor version upgrade of

OpenPegasus. However, there are certain classes of errors (e.g.,

non-compliance with a standard that significantly affects

interoperability) that may require the community to make potentially

incompatible changes. The following table contains a list of defects/fixes

that MAY impact, even well-behaved, OpenPegasus providers or clients when

upgrading to this OpenPegasus release.

<tbody>

<th bgcolor="#00ffff" width="10%">Bugzilla #</th>

<th bgcolor="#00ffff">Description</th>

</tr>

<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8830">Bug

8830</a></td>

<td align="left">Starting

with OpenPegasus 2.11.0 the requirement for providers (CMPI and C++) to

filter properties from instances has been relieved. The server will do

the filtering at the protocol adapter level. To avoid a negative impact

on performance the CIMInstance::filter() and

CMPIInstanceFT.setPropertyFilter() functions have been changed to a

NOP. This may be a change in behavior for provider relying in some

unknown way on the instance being filtered through these functions. To

allow users to actually filter properties from an instance in a

provider, a new function (CIMInstance::filterInstance()) will actually

filter properties from an instance exactly as the CIMInstance::filter()

did in previous versions of Pegasus. This is not required since the

CIMServer will do the filtering but allows the provider to prefilter

properties if it so desires, in particular where properties might be

very large or there would be a significant number of properties.

</td>

</tr>

<td><a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9369">Bug

9369</a>

</td>

<td align="left">NOTE: This bug

fixed in OpenPegasus 2.13.0. Reregistering of an

indication provider requires that the  cimserver be restarted

to send the enableIndication request to the providers. This issue

has existed starting with OpenPegasus 2.10 to  version 2.12.

If the cimserver is not restarted the indication will not be

enabled for the reregistered provider. </td>

</tr>

</tbody>

</table>

<h2>OpenPegasus Relationship to CIM/WBEM Standards</h2>

Pegasus was designed and implemented to comply with the DMTF CIM/WBEM

specifications The following table defines the level of the DMTF

specifications to which this version of Pegasus aims to conform today.

<tbody>

<tr>

<td bgcolor="#00ffff" width="33%">DMTF Specification</td>

<td width="25%" height="14">Add IO trace diagnostics to CIMClient</td>

<td bgcolor="#00ffff" width="33%">Specification Version</td>

<td width="25%" height="14">Implemented</td>

</tr>

<tr>

<td width="33%">DSP 0004 - CIM Infrastructure Specification</td>

<td width="25%" height="14">Statistical data change to use CIM classes</td>

<td width="33%">Version 2.3 Final, 4 October 2005</td>

<td width="25%" height="14">Deferred</td>

</tr>

<tr>

<td width="33%">DSP 0200 - CIM Operations over HTTP</td>

<td width="25%" height="14">Enhance operations performance</td>

<td width="33%">Version 1.4, 26 August 2013

<td width="25%" height="14">Deferred</td>

</td>

</tr>

<tr>

<td width="33%">DSP 0201 - Representation of CIM in XML</td>

<td width="25%" height="14">Security Plugin Enablement</td>

<td width="33%">Version 2.4.0 16 January 2014

<td width="25%" height="14">deferred</td>

</td>

</tr>

<tr>

<td width="33%">DSP 0202 - CIM Query Language Specification</td>

<td width="25%" height="14">Kerberos Based Security</td>

<td width="33%">1.0.0, preliminary, 9 December 2004</td>

</tr>

<tr>

<td width="33%">DSP 0205 - WBEM Discovery using SLP</td>

<td width="25%" height="14">Kerberos Based Security proposal to DMTF</td>

<td width="33%">1.0, preliminary, 27 January 2004</td>

<td width="25%" height="14">Deferred because of problems with Kerberos Specifications</td>

</tr>

<tr>

<td width="33%">DSP 0206 - WBEM SLP Template</td>

<td width="25%" height="14">Out of Process Providers</td>

<td width="33%">1.0.0, Preliminary, January 2004</td>

<td width="25%" height="14">Deferred</td>

</tr>

<tr>

<td width="33%">CIM Schema </td>

<td width="25%" height="14">SLP support</td>

<td width="33%">2.36.0 Final ( default build Schema) </td>

<td width="25%" height="14">Implemente but not compiled by default</td>

</tr>

<tr>

<td>DSP0226 - Web Services for Management

<td width="25%" height="14">Interop Classes Support</td>

</td>

<td width="25%" height="14">Implemented but not compiled by default</td>

<td>Version 1.1.1

</td>

</tr>

<tr>

<td>DSP0227 - WS-Management CIM Binding Specification

<td width="25%" height="14">SLP Client Integration</td>

</td>

<td width="25%" height="14">Implemented but not compiled by default</td>

<td>Version 1.2.0

</td>

</tr>

<tr>

<td>DSP0230 - WS-CIM Mapping Specification </td>

<td>Version 1.1.0

</td>

</tr><tr>

<td style="vertical-align: top;">DSP0212 - Filter Query Language

</td>

<td style="vertical-align: top;">Version 1.0.1, 22 August 2013

</td>

</tr>

</table>

<h2>List of Bugs Corrected</h2>

</tbody>

</table>

The current bug list for Pegasus is openly available on the OpenPegasus web site.

<h2><a name="Conformance with DMTF Specifications"></a>DMTF/SNIA SMI

As of the release of 2.3.0, the open bug list was as follows:

Profiles Supported</h2>

Today OpenPegasus includes support for several DMTF profiles including:

<ol>

<li>DMTF ProfileRegistration Version DSP 1033, Version 1.0.0</li>

<li>DMTF Indications DSP 1054, Version 1.1.0. Since this is effectively the same as the

SNIA SMI Indication profile it also supports this profile. This

profile is enabled by compiling OpenPegasus with the buld variable

PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

</li>

<li>SNIA Profile Registration 1.0.0

</li>

<li>SNIA Server 1.1.0 & 1.2.0

</li>

</ol>

<h2><a name="Conformance with DMTF Specifications">Conformance Exceptions

to DMTF Specifications</a></h2>

It is a major goal of the OpenPegasus project to both drive and utilize

the DMTF CIM/WBEM specifications.  However, today there are a number

of known differences.  As of this release, some of the differences

include the following:

<ol>

<li>Provider Registration

- Pegasus supports registration through a set of Pegasus Provider

registration classes rather than support the DMTF defined Provider

Qualifier. Pegasus will not support this qualifier in the future. See

the readme for more information on provider registration.  This is

not really a deviation from the specifications since there is no

specification or profile for provider registration today but is a

different method of registration than many CIM Servers and means that

the the provider qualifier is unused in Pegasus.</li>

<li>Lifecycle Indications -Today Pegasus supports process

iPegasusndications and lifecycle indications when defined specifically by

providers. Pegasus does not support lifecycle indications if they are

not defined by the provider or for changes to CIM Classes.

For more

information see the Pegasus CVS file:<a name="comtag_137">

pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

<li> IncludeQualifiers

option

on Instance Operations

- The DMTF specifications have deprecated the use of qualifiers on

instance operations with the 1.2 CIM Operations Over HTTP Specification (DSP0200) and

stated specifically that the client should NOT depend on the

includeQualifiers parameter of the CIM/XML instance operations

returning qualifiers.  Some CIM Client implementations expect

instances returned from the CIM Server to include the qualifiers

defined in the class definition (such as KEY qualifiers on

properties).   Pegasus today expects the provider to

complete the qualifiers on instances in accordance with the

specification and generally the interpretation is that Pegasus

applies class level qualifiers when the includeInstance parameter is

supplied on instance operations.  However, Pegasus today is

inconsistent in the return of qualifiers so that the user should NOT

depend on Pegasus accurately honoring the includeQualifier parameter

for instance operations.  In the future it is expected that

Pegasus will deprecate the use of qualifiers on instance operations

completely.  When Pegasus uses object normalization, the

normalizer does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.</li>

<li>LocalOnly option on instance Operations - With the 1.1

version of Specification for CIM Operations over HTTP, the definition

of the LocalOnly parameter for the GetInstance and Enumerate Instances

operations was modified. This change was incorrect, resulted in

reduced functionality and introduced a number of backward

compatibility issues. As a result of issues introduced by this change,

we strongly recommend that CIM Clients set LocalOnly = false and do

not rely on the use of this parameter to filter the set of set of

properties returned. See Appendix C of this specification for more

information.</li>

<li>MultiRequest CIM/XML Option

-  Pegasus does not support the DMTF defined MultiRequest

Operation option (See DSP0200).

</li>

<li>MOF Namespace Pragma -The

Pegasus compiler does not support the namespace pragma defined in DSP

0004. Namespaces for the OpenPegasus repository are defined through

arguments for the MOF Compiler

</li>

<li>CIMOperation Trailer - Pegasus implements chunking based on

the DSP0200 1.2.0 preliminary spec. including the operation trailer

defined in that specification Refer to bug <a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a>

for more details. This trailer was completely removed from the DSP0200

1.2 final specification as a non-compatible change so that if chunking

is used Pegasus is returning a noncompliant response to enumerate type

requests. </li>

<li>Whitespace in XML value Element

- Pegasus trims the leading and trailing whitespace from XML value

elements that are of the Type String.  This behavior is

documented in Pegasus bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8773">8773</a>

and there is a patch available for users.  However, since the

change is considered a change to behavior this will not be patched

until pegasus does a major version update. NOTE: There are some

documented bugs in Pegasus such as this that the OpenPegasus team

feels cannot be incorporated into the code until a major version

update.  These bugs are documented with the Bugzilla tag <big style="font-weight: bold;"><samp>"3.0_TARGET".</samp></big></li>

<li>modifyInstance operation behavior

in the Pegasus repository does not match the DMTF specification.

Under some conditions (ex. if no propertyList is supplied) it modifies

all properties rather than just the properties supplied with the

request thereby Nulling out existing values. See bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8752">8752</a>

for more information.</li>

<li>OpenPegasus Interop Namespace

- The default interop namespace name in OpenPegasus is

"root/PG_Interop".  In versions of OpenPegasus prior to 2.12.0

this could be changed during build by modifying a string definition in

the code. Effective version 2.12.0 this  has become a build option

with the build configuraton environment variable

PEGASUS_INTEROP_NAMESPACE = <name for this namespace> however,

the default if built without this change is still "root/PG_InterOp".

Effective with OpenPegasus 2.13.0 the reupgrade utility has been

extended to allow existing repositories to be converted from the use of

"root/PG_Interop" to "interop" (See discussion above).  The

default in the CVS source code is still "root/PG_InterOp".

</li>

<li>OpenPegasus WSMAN protocol on windows does not handle NaN, INF,

or -INFHowever, t (bug  <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=8836">8836</a>)

- If requests or responses include properties or parameters with

floating point property types (Real32 or Real64) with the special

states NaN, INF, or -INF on a Windows platform, the input is not

accepted because these special strings are not understood by the

decoder on Windows.</li>

<li>OpenPegasus outputs Nan, INF, -INF special values for Real32 and

Real64 property and Parameter types for the CIM/XML protocol -

(bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9392">9392</a>).

Today the DMTF Specification DSP0201 allows only numeric information

in the format definition for this type and does not all the special

strings Nan, etc. However, OpenPegasus actually outputs the special

strings if  that is what is defined in the internal values. 

OpenPegasus does not allow these special Strings on input however,</li>

<li>OpenPegasus does not handle covered properties - (bug <a href="http://bugzilla.openpegasus.org/show_bug.cgi?id=3571">3571</a>)

Covered properties (properties which have the same name in a

superclass and subclass without overridding the property in the

superclass) are not allowed in OpenPegasus. While the requirement for

this functionality was added to DSP0004 subsequent to version 2.4, the

general agreement is that the requirement itself is not supportable

and particularly not with the existing OpenPegasus APIs. 

Further, the requirement is expected to be removed in the future (i.e

CIM 3.0).</li>

<li>FQL Query Language

(bug 9956) incorporated has some limitations with respect to the DMTF

defined Query Language (does not support full regex defined in the

specification and does not support embedded instance comparison).

</li>

</ol>

138 bugs found.

<h2>OpenPegasus <a name="Supported Platforms">Supported

Platforms</a></h2>

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus

code base including a maintainer for the platform that will be willing to

regularly document issues and/or fix defects as the Pegasus code base is

changed.  Pegasus may be operable on other platforms (ex. Windows 98)

but without a group to provide the role of test and maintenance, correct

operation of  Pegasus cannot be assured.  In all cases,

including the active platforms, it is the responsibility of the entity

that packages and/or compiles OpenPegasus for shipment or deployment, to

read, and actively monitor the Pegasus Bugzilla database for a list of

</colgroup>

relevant defects that affect their platform.   The platforms

that are considered ported are shown in the two tables below.  The

<th colspan="1" width="30"><a

first table represents platform for which testing is done on a regular

href="file:///E:/DownloadsMay2002/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Pegasus+CLI+Commands&product=PegasusCIMOM&product=PegasusClient&product=PegasusCompiler&product=PegasusGeneral&product=PegasusJavaCIMClient&product=PegasusProvider&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&emailtype1=notregexp&email1=&emailtype2=substring&email2=&bugidtype=exclude&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&newqueryname=&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id">ID</a>

basis and reported to the Pegasus Nightly Build Test WEB Page. Those

</th>

platforms which have been ported but do not have test results that are

<th colspan="1" width="31"><a

current at the time of the release are reported in the second table.

</th>

Actively Supported Platforms (Nightly Tests Reported for this release)

<th colspan="1" width="22"><a

<tbody>

</th>

<th colspan="1" width="27"><a

Platform and

</th>

OS<o:p></o:p>

<th colspan="1" width="113"><a

</td>

</th>

Compilers<o:p></o:p>

<th colspan="1" width="1"><a

</td>

</tr>

</th>

<th colspan="1" width="957"><a

HP-UX<o:p>

</th>

PA_RISC and Itanium</o:p>

</tr>

</td>

HP aC++

B3910B<o:p></o:p>

</td>

</tr>

<td width="957">Weak association qualifier check missed </td>

Linux

</tr>

on Power<o:p></o:p>

</td>

gcc<o:p></o:p>

</td>

</tr>

<td width="957">Windows OS provider doesn't fill in CSName and Name keys </td>

zLinux<o:p></o:p>

</tr>

</td>

gcc<o:p></o:p>

</td>

</tr>

Linux Itanium<o:p></o:p>

<td width="957">cimom allows providers to deliver invalid properties </td>

</td>

</tr>

gcc<o:p></o:p>

</td>

</tr>

<td style="padding: 0.75pt;"> Linux

IA-32</td>

<td style="padding: 0.75pt;"> gcc (versions 3.xx, 4.7) clang(The clang compiler usage

<td width="957">Client API should support socks </td>

is considered production effective OpenPegasus 2.13.0)<o:p></o:p></td>

</tr>

Linux X86_64<o:p></o:p>

</td>

gcc (versions 3.xx, 4.7) clang(The clang compiler usage is considered production effective OpenPegasus 2.13.0)

</td>

<td width="957">Statistics MOF included in ManagedSystem Schema </td>

</tr>

<tr>

<td style="vertical-align: top;">XL C/C++ from z/OS

Version 1.7 and up</td>

<td width="957">Need a way to manage currently executing requests </td>

</tr>

<td width="957">HTTPConnection must return 413 response on oversized requ... </td>

</tr>

<td width="957">Deep Inheritance and Local Only Flags Do Not Work </td>

</tr>

<td width="957">CIMClassRep::addProperty() sets ClassOrigin incorrectly. </td>

</tr>

<td width="957">CIMDateTime::getDifference returns incorrect result for s... </td>

</tr>

<td width="957">Pegasus compiler converts Schema Qualifer decl to CLASS </td>

</tr>

<td width="957">ObjectPath MalformedObjectPath exceptions leak back throu... </td>

</tr>

<td width="957">cimserver writes on console even when started in daemon mode </td>

</tr>

<td width="957">There is no way to do pre-build or post-build stuff with ... </td>

</tr>

<td width="957">CGIClient.cpp changes '-' to '.' </td>

</tr>

<td width="957">src/Clients/ToMofClient/ToMofClient.cpp warning during build </td>

</tr>

<td width="957">warnings compiling src/Server/cimserver.cpp </td>

</tr>

<td width="957">Incomplete CIMObjectPath wen calling providers </td>

</tr>

<td width="957">Porting changes for HP-UX </td>

</tr>

<td width="957">Porting changes for IA64 Linux </td>

</tr>

<td width="957">Client requests time out with PERFINST enabled </td>

</tr>

<td width="957">MOF output for Reference values generates XML not mof </td>

</tr>

<td width="957">CIMObjectPath Legal Host name incomplete </td>

</tr>

<td width="957">Cimserver uses lots of cpu "idle time" when the cimserver... </td>

</tr>

<td width="957">Insufficient Code Coverage </td>

</tr>

<td width="957">Error in CIMClass Create on some Linux Platforms </td>

</tr>

<td width="957">Incorrect use of statistic macros </td>

</tr>

<td width="957">Compiler misses MOF syntax error in value </td>

</tr>

<td width="957">Security issues with CIMOMHandle </td>

</tr>

<td width="957">cimmof returns code of 0 on error </td>

</tr>

<td width="957">ComputerSystem provider does not set path in enumerateIns... </td>

</tr>

<td width="957">CIMDateTime::getDifference returns incorrect result on so... </td>

</tr>

<td width="957">setQualifier throws CIM_ERR_ALREADY_EXISTS </td>

</tr>

<td width="957">pegasus/src/Pegasus/Server/tests accidently disabled Feb '02 </td>

</tr>

<td width="957">dispatcher lookup optimization </td>

</tr>

<td width="957">cimconfig -s property=value -p allows you to set non-vali... </td>

</tr>

<td width="957">TestClient Failure - Associations </td>

</tr>

<td width="957">tomof client fails on call - cannot find repository </td>

</tr>

<td width="957">Condition doesn't CloseHandle() on _condition </td>

</tr>

<td width="957">typos throughout the code </td>

</tr>

<td width="957">Association test SampleFamilyProvider fails intermittently </td>

</tr>

<td width="957">cimserver silently creates new repositories </td>

</tr>

<td width="957">Test EnumerateClasses fails when classes are in a differe... </td>

</tr>

<td width="957">PropertyList parameter specified in the EnumerateInstance... </td>

</tr>

<td width="957">pegasus/mak/library-windows.mak should be using variables </td>

</tr>

<td width="957">cimserver does not report cimserver_planned.conf errors </td>

</tr>

<td width="957">Invalid XML return on what appears to be keepalive. </td>

</tr>

<td width="957">No method to recreate SSL certs, except reading the readm... </td>

</tr>

<td width="957">MOF Compiler sets ToInstance Flavor when ToSubclass is sp... </td>

</tr>

<td width="957">EnumerateInstance and EnumerateInstanceNames methods not ... </td>

</tr>

<td width="957">mu should build to $PEGASUS_HOME/bin </td>

</tr>

<td width="957">Posix signals can interrupt blocking calls and cause them... </td>

</tr>

<td width="957">"Pegasus CIM Server Demonstration" cannot enumerate clas... </td>

</tr>

<td width="957">SetProperty returns "CIM_ERR_NOT_SUPPORTED" </td>

</tr>

<td width="957">Multireq not supported </td>

</tr>

<td width="957">GetClass returns CIM_ERR_NOT_SUPPORTED with invalid args </td>

</tr>

<td width="957">CreateInstances errors with property types real32 and real64 </td>

</tr>

<td width="957">use of Tracer in ThreadPool test causes coredump when tra... </td>

</tr>

<td width="957">Compiler Errors in serveral Linux Providers </td>

</tr>

<td width="957">Definition of cimconfig parameters </td>

</tr>

<td width="957">Infinite re-acking of CIM_STOPPED message during shutdown. </td>

</tr>

<td width="957">Placement of the PEGASUS_HAS_PERFINST compile param </td>

</tr>

<td width="957">TestMakefile for Linux uses 'kill -9' to terminate cimser... </td>

</tr>

<td width="957">XMLParser removes whitespace </td>

</tr>

<td width="957">There is no inserter operation for Uint64 on the windows ... </td>

</tr>

<td width="957">Loading testrepository issues message stating loading CIM... </td>

</tr>

<td width="957">xml parsing problem regarding REFERENCECLASS </td>

</tr>

<td width="957">Corrupt newlines CVS repository </td>

</tr>

<td width="957">CIMOM Authentication on Windows XP </td>

</tr>

<td width="957">Adding TEST CASES to the String test bucket. </td>

</tr>

<td width="957">SampleFamilyProvider Shows Warnings in TestClient </td>

</tr>

<td width="957">System.cpp getSystemCreationClassName() returns empty </td>

</tr>

<td width="957">Coredump in Tracer </td>

</tr>

<td width="957">Gives internal server error( Error Code:500) while creati... </td>

</tr>

<td width="957">Message review/rewording </td>

</tr>

<td width="957">ProviderManager looks up instance provider for InvokeMethod </td>

</tr>

<td width="957">Dispatcher's result aggregation selects arbitrary exception </td>

</tr>

<td width="957">File open error lost in Repository </td>

</tr>

<td width="957">Remove DNSAdminDomain and NTPAdminDomain </td>

</tr>

<td width="957">mu does not build on Linux </td>

</tr>

<td width="957">cimserver hangs when subjected to bursts of individual re... </td>

</tr>

<td width="957">XmlReader accepts CLASSORIGIN="" </td>

</tr>

<td width="957">Pegasus DLLs on windows do not contain version numbers </td>

</tr>

<td width="957">MOF compiler does not convert escape characters </td>

</tr>

<td width="957">Redundant error message from WQLParser </td>

</tr>

<td width="957">wbem exec tests error </td>

</tr>

<td width="957">cimserver failure when running multiple client tests </td>

</tr>

<td width="957">tests/config.mak always outputs test passed even if failed </td>

</tr>

<td width="957">ComputerSystem_Linux Provider Generates File Error </td>

</tr>

<td width="957">Microsoft Visual C++ .NET compile issues </td>

</tr>

<td width="957">Unreachable error conditions in CIMOperationRequestDecoder </td>

</tr>

<td width="957">LocalizedProvider does not set path in enumerateInstances </td>

</tr>

<td width="957">Sample Association Provider Cannot Register </td>

</tr>

<td width="957">MOF Output generates error for Override flavor on qualifiers </td>

</tr>

<td width="957">FamilyProvider Needed in repositoryServer Make </td>

</tr>

<td width="957">Quesiton: use of cimobjectPath instead of CIMInstanceName... </td>

</tr>

<td width="957">Provider Interface Documentation (instance Provider) </td>

</tr>

<td width="957">Malformed Object path exception should have more information </td>

</tr>

<td width="894">IndicationService should be stopped before other services... </td>

</tr>

<td width="894">IndicationHandlerService sends incorrect response type </td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this release (No

current Nightly Build Test Results)

<tbody>

Platform and

OS<o:p></o:p>

</td>

</colgroup>

Compilers<o:p></o:p>

<th colspan="1" width="31"><a

</td>

</tr>

</th>

<tr>

<th colspan="1" width="31"><a

<td style="padding: 0.75pt;"> Windows XP, Windows

Vista, Windows 7, Windows Server 2008 </td>

</th>

<td style="padding: 0.75pt;"> Microsoft Visual C++

<th colspan="1" width="22"><a

Compilers 2003 - 2010.. Note: Visual C++ Ver. 6 no longer being

regular tested.Note that today there are some open issues with

</th>

the Windows. </td>

<th colspan="1" width="28"><a

</tr>

</th>

<td style="padding: 0.75pt;"> MacOS version 10.3 and

<th colspan="1" width="112"><a

higher</td>

</th>

</tr>

<th colspan="1" width="107"><a

<tr>

<td style="vertical-align: top;"><big>Solaris

</th>

8</big></td>

<th colspan="1" width="957"><a

<td style="vertical-align: top;"><big>GNU  2.95.3,  Sun CC

compiler V 5.8. Note that the latest thread patch (108993) may

</th>

be required. (see Pegasus bug 4632)</big>

</tr>

</td>

</tr>

<tr>

<td style="vertical-align: top;"><big>Solaris 9</big></td>

<td style="vertical-align: top;"><big>GNU  2.95.3, Sun WorkShop

6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big>

</td>

</tr>

<td width="957">IndicationService should call _terminate before handle_Ci... </td>

<tr>

</tr>

<td><big>HP OpenVMS 8.3 or later Alpha</big></td>

<td><big>HP C++ V7.3-009 or later required

for OpenVMS Alpha</big></td>

</tr>

<tr>

<td><big> HP OpenVMS 8.3 or later

IA64</big></td>

<td><big>HP C++ V7.3-023

<td width="957">IndicationService needs to handle provider enable notific... </td>

or later required on

</tr>

OpenVMS IA64</big></td>

</tr>

<tr>

Windows 2000

</td>

<td style="padding: 0.75pt;"> Microsoft Visual C++

Ver.  6 and Microsoft .Net compiler version. Works on

<td width="957">IndicationService should not accept value of Other for On... </td>

VC .NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being

</tr>

regularly tested.</td>

</tr>

<tr>

<td style="padding: 0.75pt;"> Windows 2003 </td>

<td style="padding: 0.75pt;"> Microsoft Visual C++

Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++

Ver. 6 no longer being regular tested. </td>

<td width="957">IndicationService should honor FailureTriggerTimeInterval </td>

</tr>

<td width="957">IndicationService should send DisableIndications request ... </td>

</tr>

<td width="957">IndicationService should handle DateTimeOutOfRangeExcepti... </td>

</tr>

<td width="957">Eliminate all repository access by Indication Service on... </td>

</tr>

<td width="957">Spelling Mistake in cimserver.passwd </td>

</tr>

<td width="957">For Linux Release-only Use rpath-link </td>

</tr>

<td width="957">Timing Window in Trace Code causes CIM Server fault </td>

</tr>

<td width="957">Remove unneccessary line from Linux IA64 from Platform_LI... </td>

</tr>

<td width="957">Unreachable condition in HTTPConnection2::_handleReadEvent </td>

</tr>

<td width="957">Instance not found when using CIMOMHandle::getInstance() </td>

</tr>

<td width="957">Inappropriate string match in getAssociatorNames() </td>

</tr>

<td width="957">WQLSelectStatement is only valid on first call to evaluat... </td>

</tr>

<td width="957">For M-POST request, CIMServer sends Incorrect Extention ... </td>

</tr>

<td width="957">enableIndications called multiple times </td>

</tr>

<td width="957">Fixes needed for OS/400 Authentication (V2.3) </td>

</tr>

<td width="957">Remove deprecated interfaces </td>

</tr>

<td width="957">CIMObjectPath to handle "http://" </td>

</tr>

<td width="957">Solaris build using gcc broken </td>

</tr>

<td width="957">getInstance() calls using CIMClient class result in 'inva... </td>

</tr>

<td width="957">Sample/familyprovider did not honor propertylist. </td>

</tr>

<td width="957">CIMRepository </td>

</tr>

<td width="957">cimmof error when tring to dynicall add a mof to the repo... </td>

</tr>

<td width="957">Allow any form for destination for an indication </td>

</tr>

<td width="957">ProviderManager2 only routes to Default PM </td>

</tr>

<td width="957">ThreadPool deadlock </td>

</tr>

<td width="957">slpclient has unresolved externals </td>

</tr>

<td width="957">Logger traces of xml written to standard log. Should prob... </td>

</tr>

<td width="957">InstanceDecl test should test removeQualifier </td>

</tr>

<td width="957">Request being sent to wrong provider - Client timeout </td>

</tr>

<td width="957">openpegasus.org-wbem-2.2.spec fails due to SLP absence </td>

</tr>

<td width="957">Indication subscription memory leaks </td>

</tr>

<td width="957">Java Client, numeric keybindings changed to strings </td>

</tr>

<td width="957">Indication provider does not be disabled properly </td>

</tr>

<td width="957">CIMON not verifying that the instance exist </td>

</tr>

<td width="957">Double error text from cim opperation errors </td>

</tr>

<tr>

<td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td>

<td><big>CC Compiler Sun Studio 5.11</big></td>

</tr>

</tbody>

</table>

<h3>Platform patches </h3>

The following is a list known of

<h2>Documentation</h2>

platform patches Pegasus requires.

The following documentation is available for the this Pegasus release:

<ol>

<li> RHAS 2.1 needs the update to

fix Red Hat Bugzilla 98815.

</li>

<li> RHEL 4.4 multithreading bug in getpwuid-r could cause a CIM

Server failure (Bugzilla 6232). This is fixed in RHEL 4.5

</li>

<li> Red Hat and SUSE Linux multiple versions - multithreaded client

intermittently fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red

Hat bug 248052)</li>

<li> OpenSLP Version 2.0 - This release of OpenSLP requires the

patches for OpenSLP version 2.0 documented above.</li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can be

found at: <a href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</a>

Further information regarding Pegasus support on HP platforms can be found

at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.

<h2><a name="PEGASUS Bugs">Pegasus Defects</a></h2>

The OpenPegasus Bugzilla database documents defects found in Pegasus

and  is available through the following link:  <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus

bugzilla database</a>.   Effective with the start of the

OpenPegasus 2.6 work, ALL changes to the OpenPegasus CVS tree are

documented through bugs. Therefore all source code changes to OpenPegasus

are documented through bugs providing a complete history of changes and

the reasons for those changes.  Bugs reports are filed not only for

bugs and their corresponding fixes but also as part of the process of

committing new code representing the work on PEPs done for OpenPegasus 2.6

and all subsequent versions.  Therefore, a search of the OpenPegasus

Bugzilla base for bugs with the tag for a particular version (ex.  <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED">2.6.0_APPROVED</a>,

2.6.1_APPROVED</a>, <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>,

etc) will yield all changes to the Pegasus CVS tree for that OpenPegasus

release.

     - Changes for this release (bugs Tagged

2.14.0_APPROVED). The link is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.13.0_APPROVED">

Pegasus 2.13.0_APPROVED bug list.</a>

<h2><a name="Pegasus Release Control and Version Definition Documentation">Release

Control

and Version Definition Documentation</a></h2>

The OpenPegasus project is controlled largely through the CVS repository

and a set of documents (PEPs) that serve both as the definition and review

mechanism for new and modified Pegasus functionality and for the

definition and documentation of releases.

The following documentation defines the characteristics of this Pegasus

release. The documents are available in the OpenPegasus CVS

repository.

<ul>

<li>Build and Installation - Readme in the Pegasus Root Directory</li>

<li> OpenPegasus Release Definition/Status - (See Wiki Section <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_12_x">OpenPegasus

<li>Operation - Readme in the Pegasus Root Directory</li>

2.13.x

<li>APIs - See the header files and the HTML documentation that is on the web site.</li>

Release Status</a>) - A

<li>Utilities - A combination of help generally available with the -h option for the command

section in the Pegasus wiki is used throughout the development of

and HTML documentation for most of the tools.</li>

this version as the control point for functionality that will go

<li>API usage documentation - The best API usage documentation is the existing utilities and

into the release and points to all of the PEPs that represent the

test programs.  In particular the Common/tests unit tests contain extensive examples

Pegasus  functionality changes for this version of Pegasus. </li>

of the use of the Common APIs.</li>

OpenPegasus

Build and Configuration Options  for Selected Platforms -  In previous versions of Pegasus this

information was  released as a Pegasus PEP. Starting with

Pegasus 2.9.0 the information is located in the OpenPegasus CVS

repository as <big style="font-weight: bold;"> pegasus/doc/BuildAndReleaseOptions.html</big>.

<li> OpenPegasus External Interfaces -The

list of the OpenPegasus interfaces that are considered external

and therefore "frozen". Unless an exception is explicitly approved

by the Steering Committee all subsequent releases of Pegasus MUST

continue to support these interfaces. Interfaces not explicitly

listed in this document, should be considered as internal and

subject to change.In previous Pegasus releases this information

was available as a separate PEP. Starting with Pegasus 2.9.0 this

information is integrated into the Pegasus repositoryas  pegasus/doc/EnternalInterface.html.</li>

<li> OpenPegasus  SDK Packaging Definition - Defines

the recommended set of files for inclusion in the OpenPegasus SDK.

Starting with Pegasus release 2.11.0, this document is available

in the Pegasus CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>.

In previous Pegasus releases this document was made available as s

separate Pegasus PEP document rather than in the CVS repository.

</li>

<li> Pegasus  Runtime Packaging Definition - Defines

the recommended set of files for inclusion in this OpenPegasus

release. Starting with Pegasus release 2.11.0, this idocument

contained in the CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/RuntimePackaging.html</samp></big>.

In previous releases this was made available as a seperate Pegasus

PEP document rather than in the CVS repository.  </li>

<li>Pegasus Release Notes -

PEP 368 - (This document

is located in the approved PEP repository and the OpenPegasus

source tree root directory (<big>pegasus/ReleaseNotes.htm</big>)</li>

</ul>

<h2><a name="General Documentation">General OpenPegasus Documentation</a></h2>

<hr>

L.P.; IBM Corp.; The Open Group

Permission is hereby granted, free of charge, to any person obtaining a

The following documentation is available for the this Pegasus release:

copy  of this software and associated documentation files (the "Software"),

to deal in the Software without restriction, including without limitation the rights to

use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the

<li class="MsoNormal" style="color: black;">Utilities - A

Software, and to permit persons to whom the Software is furnished to do so, subject to the

combination of help generally available with the --help option for

following conditions:

each command and HTML documentation for most of the tools.<o:p></o:p>

</li>

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE

<li class="MsoNormal" style="color: black;">API and  usage

INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE SOFTWARE IS

documentation - See the header files and the HTML

PROVIDED  "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,

API documentation that is on the web site. The best API usage

INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

documentation is the existing utilities and test programs and the

PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE

examples in the API documentation.  In particular the

FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR

Common/tests unit tests contain extensive examples of the use of the

OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER

Common APIs. </li>

DEALINGS IN THE SOFTWARE.

<li class="MsoNormal" style="color: black;">Building and Debugging

Providers - Readme.html in the Pegasus source tree Root

Directory, API documentation, and documentation from the Pegasus

</body>

Technical Workshop which is available on the Pegasus web site.

</html>

</li>

<li class="MsoNormal" style="color: black;">Building and Debugging

Clients -API documentation and the documentation on the

Pegasus Technical Workshop which is available on the Pegasus web site.

</li>

<li class="MsoNormal" style="color: black;">PEPs -The

features of Pegasus that have been installed in this and the previous

few versions are defined by Pegasus PEPs that are available on the

OpenPegasus web site.  While these are the original design

documents largely and use in the process of defining and approving the

overall characteristics of new functionality, they serve as a guide to

the design and implementation of these features. </li>

<li class="MsoNormal" style="color: black;">OpenPegasus

WIKI - This WIKI is maintained both for the use of the

development team and as a user information resource.  The wiki

can be accessed at <a href="https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start">https://wiki.opengroup.org/pegasus-wiki/doku.php?id=start</a></li>

</ul>

<hr>Licensed to The Open Group (TOG) under one or more contributor license

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this

work for additional information regarding copyright ownership. Each

contributor licenses this file to you under the OpenPegasus Open Source

License; you may not use this file except in compliance with the License.

Permission is hereby granted, free of charge, to any person obtaining a

copy of this software and associated documentation files (the

"Software"), to deal in the Software without restriction, including

without limitation the rights to use, copy, modify, merge, publish,

distribute, sublicense, and/or sell copies of the Software, and to

permit persons to whom the Software is furnished to do so, subject to

the following conditions:

The above copyright notice and this permission notice shall be included

in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY

CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,

TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

</div>

</body></html>

Legend:

Removed from v.1.1
changed lines
	Added in v.1.21

No CVS admin address has been configured