pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.17 and 1.17.4.3

version 1.17, 2010/03/26 13:20:35

version 1.17.4.3, 2013/07/20 18:32:34

Line 1

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

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

<style>

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

</style>

Line 961

Line 965

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]-->

<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml>

<o:DocumentProperties>

<o:Author>IBM_User</o:Author>

<o:LastAuthor> </o:LastAuthor>

<o:Revision>4</o:Revision>

<o:TotalTime>211</o:TotalTime>

<o:Created>2004-04-05T14:13:00Z</o:Created>

<o:LastSaved>2004-04-12T16:03:00Z</o:LastSaved>

<o:Pages>1</o:Pages>

<o:Words>5026</o:Words>

<o:Characters>28651</o:Characters>

<o:Company>IBM</o:Company>

<o:Lines>238</o:Lines>

<o:Paragraphs>67</o:Paragraphs>

<o:CharactersWithSpaces>33610</o:CharactersWithSpaces>

<o:Version>10.4219</o:Version>

</o:DocumentProperties>

</xml><![endif]--><!--[if gte mso 9]><xml>

<w:WordDocument>

<w:SpellingState>Clean</w:SpellingState>

<w:GrammarState>Clean</w:GrammarState>

<w:Compatibility>

<w:ApplyBreakingRules/>

</w:Compatibility>

<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>

</w:WordDocument>

</xml><![endif]--></head>

Pegasus

OpenPegasus Enhancement

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

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

PEP #: 366

PEP #: 355

Title: Release

Notes for OpenPegasus version 2.10.0

Notes for OpenPegasus version 2.13.0

Created: 18 July

2013

Created: 21 January 2010

Authors: Karl

Authors: Karl Schopmeyer

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>

1.0<o:p></o:p>

</td>

11 July 2013

21 January 2010

</td>

Karl Schopmeyer

Karl Schopmeyer

</td>

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

Initial

Submission <o:p>

</o:p>

</td>

</tr>

<tr>

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

</td>

<td style="padding: 0.75pt;" align="center" height="21">11 July 2013

</td>

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

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

Schopmeyer

</td>

<td style="padding: 0.75pt;" height="21"> Remove PEP 353 and 354 from

<td style="padding: 0.75pt;" height="21">Minor editorial updates

list and point to repository.Clean up PEP list</td>

before review

</td>

</tr>

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

</td>

<td style="padding: 0.75pt;" align="center" height="21">16 July 2013

</td>

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

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

Schopmeyer

</td>

<td style="padding: 0.75pt;" height="21">Update with comments from

1.01. See bug 9611. Add new section"Notes on SpecificOpenPegasus

Functionality"

</td>

</tr>

<tr>

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

</td>

<td style="padding: 0.75pt;" align="center" height="21">18 July 2013

<td style="padding: 0.75pt;" align="center" height="21">25 March 2010</td>

</td>

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

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

</td>

<td style="padding: 0.75pt;" height="21">Respond to HP comment about some confusion with the comment to bug 8830 in the compatibility Considerations section

<td style="padding: 0.75pt;" height="21">Incorporate comments from Vote on

</td>

this PEP - This version approved</td>

</tr>

</tr>

</tbody>

</table>

Abstract: This document defines the release notes for the

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

Abstract: This document defines the release notes for the 2.13.0

to summarize the characteristics of this release, point to other

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

summarize the characteristics of this release, point to other

documentation that defines the release in more detail, and provide

additional information about this release that is not available in the

other Pegasus documentation.

<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

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

Functionality of This Release</a></li>

of This Release</a></li>

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

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

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

Considerations</a></li>

to CIM/WBEM Standards</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>

Release

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

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

Documentation</a></li>

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

</ol>

<h2>Availability

<h2>Availability of this Release</h2>

of this Release</h2>

This release is available in a number of forms including:

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

These can be downloaded from the OpenPegasus

downloaded from the OpenPegasus Web

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

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

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

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

OpenPegasus web site that can be used to build binaries for most LSB-compliant RPM-based Linux distributions and versions.</li>

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

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

distributions and versions.</li>

release and

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

subsequent snapshots that are made available in the Pegasus CVS are

release and subsequent snapshots that are made available in the

defined on the OpenPegasus CVS repository web page (see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

Pegasus CVS are defined on the OpenPegasus CVS repository web page

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

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

snapshots page</a>.</li>

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 <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus

WEB site</a>.

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

Installation instructions are part of the README in the root of the

WEB

Pegasus source

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

tree.

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>

<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

Pegasus overall status by release is defined by  a

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

<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>

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

that is available on the OpenPegasus web site .  That web page shows the

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

Pegasus users and developers the status of the various features found in Pegasus

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

using a simple color coded key (white, red, yellow, green) and a description of

each feature.Pegasus 2.10.0

OpenPegasus 2.13.0 is a major release, extending the previous Pegasus

is a major release, extending the previous Pegasus release in selected

release in selected areas as described in the Pegasus  PEP defining

areas as described in the Pegasus  PEP defining this release

this release .

.

NOTE: OpenPegasus releases are categorized as follows:

The major areas of development for this release  were as follows. For

<ul>

more information access the PEP for each change defined:

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

release includes major functionality change and  incompatible

Table of Major Changes for this Release

behavior changes and/or incompatible public API changes,

</li>

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

includes new functionality but maintains behavior and public API

compatibility,

</li>

<li>3rd number changes (2.13.0 to 2.13.1) - Revision(also called point

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

</ul>

ALL changes for each release are documented in the

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

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

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

this minor release can be viewed through  this link to the

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

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

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

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

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

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

The major areas of development including both enhancements and bug fixes

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

represent only those features incorporated in bugs without PEPS that are

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

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

Table of Major

Changes for this Release. Please review  Bugzilla 2.13.0

Enhancements and approved(above) for a complete list

<tbody>

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

<th bgcolor="#00ffff" width="128">Posted PEP Version</th>

<th bgcolor="#00ffff" width="128">Posted PEP

Version</th>

</tr>

<tr>

<td align="left" width="75%">WS-Management Support in CIM Server - Phase II.

<td>Fixed issues where Pegasus compiler converted Schema Qualifer

NOTE: This is an update of the same PEP number that incorporated

decl to CLASS</td>

WS_Management changes to Pegasus 2.9.0 to incorporate more WS_Management

<td>

functionality.</td>

</td>

</tr>

<tr>

2.2</a> </td>

<td style="text-align: center;"> 5904

</td>

<td>Fixed issue that could cause server error if providers

return  associator or ref responses with no keys in path</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Support Writing indications to local file. Note that this is

primarily a development and debug extension.

</td>

<td>

</td>

</tr>

<tr>

<td>Remove the PEGASUS_VENDOR_HP build variable</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Enhance repupgrade utility to support "interop" namespace (see

note below)

</td>

<td><a href="https://collaboration.opengroup.org/pegasus/pp/documents/24686/PEP304.htm">PEP

304, Version 1.6</a>

</td>

</tr>

<tr>

</td>

<td>Support clang compiler in Production Build

</td>

<td>

</td>

</tr>

<tr>

<td align="left" width="75%">Extend CIMCLI to create/modify instances with other features</td>

</td>

<td>Add more supplemental help info to cimconfig CLI tool that views

and sets runtime parameters

</td>

<td>

</td>

</tr>

<tr>

<td style="vertical-align: top; text-align: center;"><a title="9478" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9478">9478

</a>and others

</td>

<td style="vertical-align: top;">Fixed issues involving compiled

unused variable warnings and set compiler defaults to make these

warnings a build error.

</td>

</td>

</tr>

<tr>

</td>

<td>Clean up  issues with building with static libraries

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Reduce static code size (Note: several bug fixes contributed to

this reduction) (see 9555, 9560, 9557, 9558, 9580)

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Log rotation configuration variable to set max file size (see

below for more info)

</td>

<td>

</td>

</tr>

<td align="left" width="75%">Single-Memory-Object for CMPI structure</td>

</td>

<td align="left" width="75%">Remove compile option

PEGASUS_CLIENT_TRACE_ENABLE (now always compiles) </td>

</td>

</tr>

<tr>

</td>

<td>Fix issues requiring restart of cimserver  if indication

provider reregistered

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Initial configure script for OpenPegasus (Experimental, see below)

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Update env_var_LINUX.status and env_var_HPUX.status to change

some build defaults

</td>

</td>

</tr>

<tr>

<td>Modify environment variable definition that controls client

tracing (See below)</td>

<td>

</td>

</tr>

<tr>

</td>

<td align="left" width="75%">Add support for PUSH_WITH_ACK delivery

mode for WSMAN indications

</td>

<td style="text-align: center;" width="128">PEP 365

</td>

</tr>

<tr>

<td>Change default Schema version to use CIM Schema 2.36</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Replace custom atomic operations with GCC built-in atomic

operations(see below for more comments)

</td>

<td>

</td>

</tr>

<td style="text-align: center;" width="7%"><a title="9635" href="http://bugzilla.openpegasus.org/show_bug.cgi?id=9635">9635</a>,

<td align="left" width="75%">Separate Internal Modules from Common Library</td>

</td>

<td align="left" width="75%">IPV6 support for OpenPegasus slp using

OpenSLP 2.0 (See OpenSLP 2.0 issues documented below)

</td>

1.1</a></td>

</td>

</tr>

<tr>

<tr><td style="text-align: center;">PEP 350</td><td>Multi CIMOM support on

</td>

same OS </td><td style="text-align: center;">

<td>Support for ARM 64 CPU by adding platform definition

(Experimental because of limited testing)

1.0</a></td></tr><tr><td style="text-align: center;">

</td>

<a name="comtag_90">repupgrade utility enhancement to

</td>

update SystemName property in indication filter/handler and

ObjectManager instances</a> </td><td style="text-align: center;"> </td></tr><tr align="center">

<a name="comtag_95">Indication service can be

disabled/enabled dynamically</a> </td>

</tr>

<tr>

</td>

<td>Fix connection between indication handlers and IndicationService

so that OnFatalErrorPolicy works

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Expand reporting of errors from PAM so detailed PAM errors reported.

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Allow remote update of expired user password for PAM session

based authentication

</td>

<td>

</td>

</tr>

<tr>

</td>

<td>Role-based authorization extension for CMPI providers

</td>

<td>

</td>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality change status

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

The status of several components of Pegasus functionality change status

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

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

release to this release</a> on the

that

<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>.

have

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

Finally, a significant number of internal changes and corrections were made

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

under the control of the Pegasus bugzilla bug system. See the bug section below

Status WEB Page</a>.

for more information.

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

<h3>Information on  IPv6 Support (PEP 291)</h3>

OpenPegasus Functionality Changes</h2>

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but it

This section documents specific issues that the OpenPegasus team feels are

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

important to OpenPegasus users with the current release (and possibly

Notes

older releases).

IPv6 is short for "Internet

Protocol

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

Version 6". IPv6 is the "next generation" protocol designed by the IETF

2.13.0)(bug 9550)</h3>

to replace the current version Internet Protocol, IP Version 4

As of OpenPegasus 2.13.0, two new runtime variables have been added:

("IPv4"). IPv6 Support for OpenPegasus is documented in <a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">

PEP

   * traceFileSizeKBytes -  Defines the size of the

291</a>.

tracefile in kilobytes. The trace file will be rolled once its size

The IPv6 support in OpenPegasus is

exceeds the specified size.

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this

   * numberOfTraceFiles - Specifies the number of the tracefiles

variable is "true"; setting this to

for rolling where the default is 3.

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

</h3>

As of 2.13.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

The following subsections provide some information on IPv6 support for the

some information on IPv6 support for the Linux and Windows platforms.

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

Note that in the 2.6.1 release there is no automatic run-time detection

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

of IPv6 support on a platform by OpenPegasus. If you build with

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

PEGASUS_ENABLE_IPV6=true, your platform must support IPv6 or you will

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

get a build failure (missing header files), a run-time bind() failure,

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

or possibly some other failure. This applies to both the CIM Server and

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

Listener components. For more information on IPv6 support for your

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

specific platform, refer to the documentation for that platform.

All OpenPegasus externals that support eitcompilerher a hostname or an IP

All OpenPegasus externals that

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

support either a hostname or an IP address as input have been updated

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

to allow an IPv6 address to be specified. If the required input is just

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

an IP address (eg. no optional or required port number), then the IPv6

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

address must be specified without brackets. For example, the

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

OpenPegasus osinfo client (which returns information about the OS

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

running on a host system) takes separate host and port options. In this

interface would be specified as:

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>

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

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

3ffe:1:2:1 -p 5988</big></div>

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

But the cimcli command, which

delimited with brackets, for example:

takes

an optional "location" option including an optional port number,

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

requires the IPv6 address to be delimited with brackets, for example:

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

<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 style="margin-left: 40px;"><big>cimcli

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

</div>

For more information on

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

specifying

RFC

IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP Version

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

6 Addressing Architecture</a>

RFC 2732 - Format for Literal IPv6 Addresses in URL's</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

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

contain IPv6-ready kernels, the

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

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

module is not loaded automatically on startup.

that this module is not loaded automatically on startup.

Note:

Note: you shouldn't use

you shouldn't use kernel series 2.2.x, because it's not

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

IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no

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

longer improved according to definitions in latest RFCs. It's recommend

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

to use series 2.6.x now.

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

To check whether your current

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

running

short automated test looks like:

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>

<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

For more information on

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

enabling

IPv6 in the Linux kernel and configuring network interfaces, refer to

<a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux

Documentation Project's IPv6 HOWTO</a>.

Warning:

Warning: There is currently an

There is currently an open issue with RedHat to address a problem that

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

is seen intermittently on RHEL5 and SLES10 systems. This problem is

RHEL5 and SLES10 systems. This problem is described in

described in

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

bug 6586</a>

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

bug

and

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

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

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

bug 248052</a>,

be significantly impacted in these environments.

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

Microsoft provides supported IPv6 implementations for Windows Server 2003,

2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service

Windows XP with Service Pack 1 (SP1), Windows XP with Service Pack 2

Pack 2 (SP2), and Windows CE .NET 4.1 and later.

(SP2), and Windows CE .NET 4.1 and later.

On Windows XP, you can use the ipv6.exe tool to install, uninstall, and

query

On Windows XP, you can use the ipv6.exe

your IPv6 configuration. For example:

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

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

IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack.

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

Note that the OpenPegasus IPv6 support has not yet been tested

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

on Windows Vista or Windows Server 2008.

Windows Server 2008.

For more information on

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

installing, configuring, and using IPv6 on Windows platforms, refer to

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

the document

<h4>Testing  OpenPegasus IPv6 support</h4>

IPv6

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

for Microsoft Windows: Frequently Asked Questions</a>.

IndicationStressTest test clients were modified to run tests using the

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

<h4>Testing your OpenPegasus IPv6

support</h4>

You can also perform manual tests using the IPv6 loopback or a real

As part of the OpenPegasus

IPv6-configured network interface. For example, using the IPv6 loopback on

automated tests, the TestClient, g11ntest, and IndicationStressTest

a system with OpenPegasus running on the WBEM standard http port of 5988:

test clients were modified to run tests using the IPv6 loopback address

(::1) if PEGASUS_ENABLE_IPV6=true.

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

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

You can also perform manual

Considerations</a></h2>

tests

Support for forward-compatibility is a fundamental design principle for

using the IPv6 loopback or a real IPv6-configured network interface.

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

For example, using the IPv6 loopback on a system with OpenPegasus

OpenPegasus providers or clients, using only the externally defined

running on the WBEM standard http port of 5988:

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

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

osinfo -h ::1</big></div>

non-compliance with a standard that significantly affects

<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2>

interoperability) that may require the community to make potentially

Support for forward-compatibility is a fundamental design principle for the

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

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

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

Providers or Clients, using only the externally defined OpenPegasus interface,

upgrading to this OpenPegasus release.

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 defect

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>

</tr>

</tr>

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

8830</a></td>

</tr>

<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

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

CIM/WBEM Standards</h2>

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

Pegasus was designed and implemented to comply with the DMTF

specifications The following table defines the level of the DMTF

CIM/WBEM specifications The following table defines the level of the

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

DMTF specifications to which this version of Pegasus aims to conform

today.

<tbody>

<tr>

Line 1484

Line 1732

</tr>

<tr>

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

<td width="33%">2.22.1 Final,  22 Oct 2009( default) </td>

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

</tr>

<tr>

<td>DSP0226 - Web Services for Management

</td>

<td>Version 1.1.1

</td>

</tr>

<tr>

<td>DSP0227 - WS-Management CIM Binding Specification

</td>

<td>Version 1.2.0

</td>

</tr>

<tr>

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

<td>Version 1.1.0

</td>

</tr>

</tbody>

</table>

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

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

Exceptions to

Profiles Supported</h2>

DMTF Specifications</a></h2>

It is a major goal

Today OpenPegasus includes support for several DMTF profiles including:

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

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

through a set of Pegasus Provider registration classes rather than

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

support the DMTF defined Provider Qualifier. Pegasus will not support

SNIA SMI Indication profile it also supports this profile. This

this qualifier in the future. See the readme for more information on

profile is enabled by compiling OpenPegasus with the buld variable

provider registration.  This is not a deviation from the

PEGASUS_ENABLE_DMTF_INDICATION_SUPPORT.

specifications but is a different method of registration than many CIM

</li>

Servers and means that the the provider qualifier is unused in Pegasus.</li>

<li>SNIA Profile Registration 1.0.0

<li>Indications -Today Pegasus supports process

</li>

indications and lifecycle indications when defined specifically by

<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

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

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

For more

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

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

<li>

<li> IncludeQualifiers

IncludeQualifiers

option

option on Instance Operations

on Instance Operations

- The DMTF specifications have deprecated the use of qualifiers on

The DMTF specifications have deprecated the use of qualifiers on

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

instance operations with the 1.2 CIM Operations Specification and

stated specifically that the client should NOT depend on the

includeQualifiers parameter of the CIM/XML instance operations

returning qualifiers. 

returning qualifiers.  Some CIM Client implementations expect

Some CIM Client implementations expect instances

instances returned from the CIM Server to include the qualifiers

returned

defined in the class definition (such as KEY qualifiers on

from the CIM Server to include the qualifiers defined in the class

properties).   Pegasus today expects the provider to

definition (such as KEY qualifiers on properties).   Pegasus

complete the qualifiers on instances in accordance with the

today expects the provider to complete the qualifiers on instances in

specification and generally the interpretation is that Pegasus

accordance with the specification and generally the interpretation is

applies class level qualifiers when the includeInstance parameter is

that Pegasus applies class level qualifiers when the includeInstance

supplied on instance operations.  However, Pegasus today is

parameter is supplied on instance operations.  However, Pegasus

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

today is inconsistent in the return of qualifiers so that the user

depend on Pegasus accurately honoring the includeQualifier parameter

should NOT depend on Pegasus accurately honoring the includeQualifier

for instance operations.  In the future it is expected that

parameter for instance operations.  In the future it is expected

Pegasus will deprecate the use of qualifiers on instance operations

that Pegasus will deprecate the use of qualifiers on instance

completely.  When Pegasus uses object normalization, the

operations completely.  When Pegasus uses object normalization,

normalizer does apply qualifiers to returned instances if the

the normalizer does apply qualifiers to returned instances if the

includeQualifiers operation parameter is set.</li>

includeQualifiers operation parameter is set.</li><li>LocalOnly option on instance

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

Operations - With the 1.1 version of Specification for CIM

version of Specification for CIM Operations over HTTP, the definition

Operations over HTTP, the definition of the LocalOnly parameter for the

of the LocalOnly parameter for the GetInstance and Enumerate Instances

GetInstance and Enumerate Instances operations was modified. This change

operations was modified. This change was incorrect, resulted in

was incorrect, resulted in reduced functionality and introduced a

reduced functionality and introduced a number of backward

number of backward compatibility issues. As a result of issues

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

introduced by this change, we strongly recommend that CIM Clients set

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

LocalOnly = false and do not rely on the use of this parameter to

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

filter the set of set of properties returned. See Appendix C of this

properties returned. See Appendix C of this specification for more

specification for more information.</li>

information.</li>

<li>

<li>MultiRequest CIM/XML Option

MultiRequest Operations - Pegasus

-  Pegasus does not support the DMTF defined MultiRequest

does not support the DMTF defined MultiRequest Operation option.

Operation option (See DSP0200).

</li>

<li>

<li>MOF Namespace Pragma -The

MOF Compiler namespace pragma - The

Pegasus compiler does not support the namespace pragma defined in DSP

Pegasus compiler does not support the namespace pragma.

0004. Namespaces for the OpenPegasus repository are defined through

arguments for the MOF Compiler

</li>

<li>CIMOperation Trailer - Pegasus implements

<li>CIMOperation Trailer - Pegasus implements chunking based on

chunking

the DSP0200 1.2.0 preliminary spec. including the operation trailer

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>

defined in that specification Refer to bug

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

<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> for more details.

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

This trailer was completely removed from the DSP0200 1.2 final specification

is used Pegasus is returning a noncompliant response to enumerate type

as a non-compatible change so that if chunking is used Pegasus is returning

requests. </li>

a noncompliant response to enumerate type requests.

<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>

</ol>

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

Platforms</a></h2>

Each OpenPegasus release lists as 'active' platforms those

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus code base

hardware/software platforms that have recognized ports for the Pegasus

including a maintainer for the platform that will be willing to regularly

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

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

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

Pegasus may be operable on other platforms (ex. Windows 98) but without a group

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

to provide the role of test and maintenance, correct operation of  Pegasus

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

cannot be assured.  In all cases, including the active platforms, it is the

operation of  Pegasus cannot be assured.  In all cases,

responsibility of the entity that packages and/or compiles OpenPegasus for

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

shipment or deployment, to read, and actively monitor the Pegasus bugzilla

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

database for a list of relevant defects that affect their platform.  

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

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

relevant defects that affect their platform.   The platforms

The first table represents platform sofr which testing is done on a regular

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

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

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

which have been ported but do not have test results that are current at the time

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

of the release are reported in the second table.Actively Supported Platforms (Nightly Tests Reported for this release)

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

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

Actively Supported Platforms (Nightly Tests Reported for this release)

<tbody>

Platform and

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

</td>

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

</td>

</tr>

HP-UX<o:p> PA_RISC and

HP-UX<o:p>

Itanium</o:p>

PA_RISC and Itanium</o:p>

</td>

HP aC++ B3910B<o:p></o:p>

HP aC++

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

</td>

</tr>

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

Linux

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

</td>

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

Line 1623

Line 1958

</td>

</tr>

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

Linux IA-32</td>

IA-32</td>

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

gcc

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

(versions 3.xx, 4.xx)<o:p></o:p></td>

</tr>

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

</td>

gcc

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

(versions 3.xx, 4.xx)

</td>

</tr>

<tr>

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

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

1.7 and up</td>

Version 1.7 and up</td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this release (No

current Nightly Build Test Results

Platforms not Actively supported for this release (No

current Nightly Build Test Results)

<tbody>

Platform and

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

</td>

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

</td>

</tr>

<tr>

<td style="padding: 0.75pt;"> Windows XP

<td style="padding: 0.75pt;"> Windows XP, Windows

</td>

Vista, Windows 7, Windows Server 2008 </td>

<td style="padding: 0.75pt;"> Microsoft Visual C++

Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1.

Compilers 2003 - 2010.. Note: Visual C++ Ver. 6 no longer being

Note: Visual C++ Ver. 6 no longer being regular tested.

regular tested.Note that today there are some open issues with

the Windows. </td>

</td>

</tr>

<td style="padding: 0.75pt;"> MacOS version 10.3 and higher</td>

<td style="padding: 0.75pt;"> MacOS version 10.3 and

higher</td>

</tr>

<tr>

<td style="vertical-align: top;"><big>Solaris 8</big></td>

<td style="vertical-align: top;"><big>Solaris

<td style="vertical-align: top;"><big>GNU  2.95.3,  Sun

8</big></td>

CC compiler V 5.8. Note that the latest thread patch (108993) may be

<td style="vertical-align: top;"><big>GNU  2.95.3,  Sun CC

required. (see Pegasus bug 4632)</big>

compiler V 5.8. Note that the latest thread patch (108993) may

be required. (see Pegasus bug 4632)</big>

</td>

</tr>

<tr>

<td style="vertical-align: top;"><big>Solaris 9</big></td>

<td style="vertical-align: top;"><big>GNU  2.95.3, Sun

<td style="vertical-align: top;"><big>GNU  2.95.3, Sun WorkShop

WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big>

6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big>

</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

</tr>

Alpha</big></td></tr>

<tr>

<tr><td><big> HP OpenVMS 8.3 or later IA64</big></td><td><big>HP C++ V7.3-023 or

<td><big>HP OpenVMS 8.3 or later Alpha</big></td>

later required on OpenVMS IA64</big></td></tr>

<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

or later required on

OpenVMS IA64</big></td>

</tr>

<tr>

Windows 2000

</td>

<td style="padding: 0.75pt;"> Microsoft Visual C++

Microsoft Visual C++ Ver.  6 and Microsoft .Net compiler version. Works on VC .NET 2003 v7.1).

Ver.  6 and Microsoft .Net compiler version. Works on

NOTE: Visual C++ Ver. 6 no longer being regularly tested.</td>

VC .NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being

regularly tested.</td>

</tr>

<tr>

<td style="padding: 0.75pt;"> Windows 2003

<td style="padding: 0.75pt;"> Windows 2003 </td>

</td>

<td style="padding: 0.75pt;"> Microsoft Visual C++

Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++

Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1.

Ver. 6 no longer being regular tested. </td>

Note: Visual C++ Ver. 6 no longer being regular tested.

</tr>

<tr>

</td>

<td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td>

<td><big>CC Compiler Sun Studio 5.11</big></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>

Platform patches

<h3>Platform patches </h3>

The following is a list known of platform

The following is a list known of

patches Pegasus requires.

platform patches Pegasus requires.

<ol>

<li>

<li> RHAS 2.1 needs the update to

fix Red Hat Bugzilla 98815.

RHAS

</li>

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

<li>

Server failure (Bugzilla 6232). This is fixed in RHEL 4.5

RHEL 4.4 multithreading bug in

</li>

getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is fixed in

<li> Red Hat and SUSE Linux multiple versions - multithreaded client

RHEL 4.5</li>

intermittently fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red

<li>

Hat bug 248052)</li>

Red Hat and SUSE Linux

<li> OpenSLP Version 2.0 - This release of OpenSLP requires the

multiple versions -

patches for OpenSLP version 2.0 documented above.</li>

multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla

6586) (Red Hat bug 248052) </li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can

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

Further information regarding Pegasus support on HP platforms can be found

found at:

at: <a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.

<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 Pegasus bugzilla database documents any defects found in Pegasus

The OpenPegasus Bugzilla database documents defects found in Pegasus

and  is available through the following link:  <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla

and  is available through the following link:  <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus

database</a>.

bugzilla database</a>.   Effective with the start of the

Effective with the start of the Pegasus 2.6 work, all changes to the

OpenPegasus 2.6 work, ALL changes to the OpenPegasus CVS tree are

CVS tree are documented through bugs.  Bugs reports are filed not

documented through bugs. Therefore all source code changes to OpenPegasus

only for bugs and

are documented through bugs providing a complete history of changes and

their corresponding fixes but also as part of the process of committing

the reasons for those changes.  Bugs reports are filed not only for

new code

bugs and their corresponding fixes but also as part of the process of

representing the work on PEPs done for Pegasus 2.6 and all subsequent

committing new code representing the work on PEPs done for OpenPegasus 2.6

versions.  Therefore, a search of

and all subsequent versions.  Therefore, a search of the OpenPegasus

the Open Pegasus bugzilla base for bugs with the tag for a particular

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>,

version

(ex. 

2.6.0_APPROVED</a>,

2.6.1_APPROVED</a>,

2.6.1_APPROVED</a>, <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>,

<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>, etc) will yield all changes to

etc) will yield all changes to the Pegasus CVS tree for that OpenPegasus

the Pegasus CVS tree for that Pegasus release.

release.

     - Changes for this release (bugs Tagged

2.10.0_APPROVED). The link is <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.10.0_APPROVED">

2.13.0_APPROVED). The link is <a href="http://bugzilla.openpegasus.org/buglist.cgi?keywords=2.13.0_APPROVED">

Pegasus 2.10.0_APPROVED bug list.</a>

Pegasus 2.13.0_APPROVED bug list.</a>

<h2><a name="Pegasus Release Control and Version Definition Documentation">Release

<h2><a name="Pegasus Release Control and Version Definition Documentation">Release Control and Version Definition Documentation</a></h2>

Control

and Version Definition Documentation</a></h2>

The Pegasus project is controlled largely through the CVS repository and a set of documents

The OpenPegasus project is controlled largely through the CVS repository

(PEPs) that serve both as the definition and review mechanism for new and

and a set of documents (PEPs) that serve both as the definition and review

modified Pegasus functionality and for the definition and documentation

mechanism for new and modified Pegasus functionality and for the

of releases.The following documentation defines the characteristics of this

definition and documentation of releases.

Pegasus release. The PEPs are available at

The following documentation defines the characteristics of this Pegasus

OpenPegasus Approved PEPs.</a><ol>

release. The documents are available in the OpenPegasus CVS

repository.

<li>

<ul>

OpenPegasus Release Definition/Status -  </li>No PEP (See Wiki Section <a href="http://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_9_x">OpenPegasus 2.10.x Release Status</a>) - A

<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

section in the Pegasus wiki is used

2.13.x

throughout the development of this version as the control point for

Release Status</a>) - A

functionality that will go into the release and points to all of the PEPs that

section in the Pegasus wiki is used throughout the development of

represent the Pegasus  functionality changes for this version of Pegasus.

this version as the control point for functionality that will go

into the release and points to all of the PEPs that represent the

Pegasus  functionality changes for this version of Pegasus. </li>

OpenPegasus  Build and Configuration

OpenPegasus

Options  for Selected

Build and Configuration Options  for Selected Platforms -  In previous versions of Pegasus this

Platforms -

information was  released as a Pegasus PEP. Starting with

<a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/*checkout*/pegasus/doc/BuildAndReleaseOptions.html?rev=1.18">CVS Respository Build And Release Options Document</a> -

Pegasus 2.9.0 the information is located in the OpenPegasus CVS

In previous versions of Pegasus this

repository as <big style="font-weight: bold;"> pegasus/doc/BuildAndReleaseOptions.html</big>.

information was  releases as a Pegasus PEP. Starting with Pegasus 2.9.0

the information is located in the OpenPegasus CVS repository as <big>

<li> OpenPegasus External Interfaces -The

pegasus/doc/BuildAndReleaseOptions.html</big>.</li>

list of the OpenPegasus interfaces that are considered external

and therefore "frozen". Unless an exception is explicitly approved

<li>

by the Steering Committee all subsequent releases of Pegasus MUST

OpenPegasus External Interfaces -

continue to support these interfaces. Interfaces not explicitly

listed in this document, should be considered as internal and

CVS Repository External Interfaces Document</a>- THE list of the

subject to change.In previous Pegasus releases this information

OpenPegasus interfaces that are considered external and therefore "frozen".

was available as a separate PEP. Starting with Pegasus 2.9.0 this

Unless an exception is explicitly approved by the Steering Committee all

information is integrated into the Pegasus repositoryas  pegasus/doc/EnternalInterface.html.</li>

subsequent releases of Pegasus MUST continue to support these interfaces.

Interfaces not explicitly listed in this document, should be considered as

<li> OpenPegasus  SDK Packaging Definition - Defines

internal and subject to change.

the recommended set of files for inclusion in the OpenPegasus SDK.

Starting with Pegasus release 2.11.0, this document is available

In previous Pegasus releases this information was available as a separate

in the Pegasus CVS repository as <big style="font-weight: bold;"><samp>pegasus/doc/SDKPackaging.html</samp></big>.

PEP. Starting with Pegasus 2.9.0 this information is integrated into the

In previous Pegasus releases this document was made available as s

Pegasus repository as  pegasus/doc/EnternalInterface.html.

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

<li>

release. Starting with Pegasus release 2.11.0, this idocument

OpenPegasus  SDK Packaging Definition - </li>

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 352</a> - Defines the

PEP document rather than in the CVS repository.  </li>

recommended set of files for inclusion in the OpenPegasus SDK

<li>Pegasus Release Notes -

PEP 364 - (This document

is located in the approved PEP repository and the OpenPegasus

<li>

source tree root directory (<big>pegasus/ReleaseNotes.htm</big>)</li>

Pegasus  Runtime Packaging Definition -

</ul>

PEP 351</a> - </li>Defines the

<h2><a name="General Documentation">General OpenPegasus Documentation</a></h2>

recommended set of files for inclusion in this OpenPegasus release.

The following documentation is available for the this Pegasus release:

<li>Pegasus Release Notes -  PEP 355

- (This document is located in the

approved PEP

repository and the OpenPegasus source tree root directory (<big>pegasus/ReleaseNotes.htm</big>)

</li>

</ol>

<h2><a name="General Documentation">General Documentation</a></h2>

The following documentation is available for the this Pegasus

release:

<li class="MsoNormal" style="color: black;">Utilities - </li>A

combination of help generally available with the --help option for each

<li class="MsoNormal" style="color: black;">Utilities - A

command and HTML documentation for most of the tools.<o:p></o:p>

combination of help generally available with the --help option for

each command and HTML documentation for most of the tools.<o:p></o:p>

</li>

<li class="MsoNormal" style="color: black;">API and  usage

<li class="MsoNormal" style="color: black;">API and  usage

documentation - See the header files and the HTML

documentation - </li>See the header files and the HTML  API

API documentation that is on the web site. The best API usage

documentation that is on the web site. The best API usage documentation

documentation is the existing utilities and test programs and the

is the existing utilities and test programs and the examples in the API

examples in the API documentation.  In particular the

documentation.  In particular the Common/tests unit tests contain

Common/tests unit tests contain extensive examples of the use of the

extensive examples of the use of the Common APIs.

Common APIs. </li>

<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

<li class="MsoNormal" style="color: black;">Building and Debugging

Technical Workshop which is available on the Pegasus web site.

Providers - </li>Readme.html in the Pegasus source tree Root Directory, API

</li>

documentation, and documentation from the Pegasus Technical Workshop

<li class="MsoNormal" style="color: black;">Building and Debugging

which is available on the Pegasus web site.

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

<li class="MsoNormal" style="color: black;">Building and Debugging

Clients - </li>API documentation and the documentation on the Pegasus

Technical Workshop which is available on the Pegasus web site.

<li class="MsoNormal" style="color: black;">PEPs - </li>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.

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

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this

this work for additional information regarding copyright ownership.

work for additional information regarding copyright ownership. Each

Each contributor licenses this file to you under the OpenPegasus Open

contributor licenses this file to you under the OpenPegasus Open Source

Source License; you may not use this file except in compliance with the

License; you may not use this file except in compliance with the License.

License.

Permission is hereby granted, free of charge, to any person obtaining a

copy of this software and associated documentation files (the "Software"),

copy of this software and associated documentation files (the

to deal in the Software without restriction, including without limitation

"Software"), to deal in the Software without restriction, including

the rights to use, copy, modify, merge, publish, distribute, sublicense,

without limitation the rights to use, copy, modify, merge, publish,

and/or sell copies of the Software, and to permit persons to whom the

distribute, sublicense, and/or sell copies of the Software, and to

Software is furnished to do so, subject to the following conditions:

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

Line 1893

Line 2212

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.17
changed lines
	Added in v.1.17.4.3

No CVS admin address has been configured