Pegasus Enhancement Proposal (PEP)

PEP #: 306

Title: Release Notes for OpenPegasus 2.7.0

Created: 3 October 2007

Authors: Karl Schopmeyer

Status:  draft

Version History:






 3 October 2007

Karl Schopmeyer

Initial Submission

1.1 8 October 2007 Karl Schopmeyer Incorporate data from 2.6.1 release notes. Fix per comments in 1.0
1.2 11 October 2007 Karl Schopmeyer Comments from V 1.1 and add existing document links. Add pep 302 to enhancements
1.3 15 October 2007 Karl Schopmeyer Add final links

Abstract: This document defines the release notes for the 2.7.0 release of the OpenPegasus CIM Server. The purpose of this PEP is to summarize the characteristics of this release, point to other documentation that defines the release in more detail, and provide additional information about this release that is not available in the other Pegasus documentation.


  1. Availability of this Release
  2. OpenPegasus Functionality of This Release
  3. Compatibility Considerations
  4. Relationship to CIM/WBEM Standards
  5. OpenPegasus Supported Platforms
  6. Conformance with DMTF Specifications
  7. OpenPegasus Bugs
  8. OpenPegasus Release Control and Version Definition Documentation
  9. General Documentation

Availability of this Release

This release is available in a number of forms including:

The instructions for acquiring the released code are on the Pegasus WEB site. Installation instructions are part of the README in the root of the Pegasus source tree.

OpenPegasus Functionality for This Release

Pegasus overall status by release is defined by  a Feature Status WEB Page that is available on the OpenPegasus web site .  That web page shows the Pegasus users and developers the status of the various features found in Pegasus using a simple color coded key (white, red, yellow, green) and a description of each feature.

Pegasus 2.7.0 is a major release, extending Pegasus 2.6 in selected areas as described in the Pegasus  PEP defining this release . 

The major areas of development for this release  were as follows. For more information access the PEP for each change defined:

                      Table of Major Changes for this Release

PEP # Description of Change Posted PEP
284 Add Platform support IBM i5/PASE - Portable Application Solutions Environment (PASE) 1.6
286 Reduce the Amount of CIM Server code that runs Privileged (Privilege Separation) 1.8
291 Add Support for IPv6 - Stage 1 (Note: This functionality was made available but normally disabled Pegasus 2.6.1) 1.2
62 Add IPV6 Support for SNMP Indication Handler and include NET-SNMP indication handler in Linux RPM 1.1
130 Enable Remote CMPI for Windows 1.2
302 Enhanced Log File Support 1.0
258 Add support for certificate-based authentication audit logging 1.5
Bugzilla 6466 Add two new trace components to facilitate triage of indication delivery issues Bug 6466

The status of several components of Pegasus functionality change status between Pegasus versions. Features that have changed status can be identified by a change in color from the previous release to this release on the Feature Status WEB Page.

Finally, a significant number of internal changes and corrections were made under the control of the Pegasus bugzilla bug system. See the bug section below for more information.

Information on  IPv6 Support (PEP 291)

IPv6 is short for "Internet Protocol Version 6". IPv6 is the "next generation" protocol designed by the IETF to replace the current version Internet Protocol, IP Version 4 ("IPv4"). IPv6 Support for OpenPegasus is documented in PEP 291.

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 either a hostname or an IP address as input have been updated to allow an IPv6 address to be specified. If the required input is just an IP address (eg. no optional or required port number), then the IPv6 address must be specified without brackets. For example, the OpenPegasus osinfo client (which returns information about the OS running on a host system) takes separate host and port options. In this case a host with an IPv6-configured network interface would be specified as:

osinfo -h 3ffe:1:2:1 -p 5988

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:

cimcli ns -l [3ffe:1:2:1]


cimcli ns -l [3ffe:1:2:1]:5989

For more information on specifying IPv6 addresses, refer to IETF RFC 2373 - IP Version 6 Addressing Architecture and IETF RFC 2732 - Format for Literal IPv6 Addresses in URL's.

IPv6 on Linux

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

test -f /proc/net/if_inet6 && echo "Running kernel is IPv6 ready"

For more information on enabling IPv6 in the Linux kernel and configuring network interfaces, refer to The Linux Documentation Project's IPv6 HOWTO.

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 Pegasus bug 6586 and RedHat bug 248052, 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.

IPv6 on Windows

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:

ipv6 install
ipv6 if

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 IPv6 for Microsoft Windows: Frequently Asked Questions.

Testing your OpenPegasus IPv6 support

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:

osinfo -h ::1

Compatibility Considerations

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 defect fixes that MAY impact, even well-behaved, OpenPegasus Providers or Clients when upgrading to OpenPegasus 2.7.0.

Bugzilla # Description
6476 HP-UX only: Introduction of the "explicit" keyword in CIMClass.h and CIMInstance.h may introduce a compile error in some code. Specifically, a compiler-supplied automatic conversion from CIMObject type to CIMClass or CIMInstance has been removed. The cast operation must be explicitly specified.

WIPCR00430 recommends an unquoted charset parameter in Content-type header. See the writeup in this bug for a discussion of the validation of the charset parameter in various OpenPegasus releases. In 2.7 we perform "extended" validation that should ignore differences based on whitespace or quotes. The CR recommendation is to not use quotes on the charset parameter, but only at a time when it is expected that all CIMOMs have been updated to accept the charset parameter with or without quotes.


The MOF Compiler now rejects some property values that are invalid according to the DMTF specification that it previously accepted.

OpenPegasus Relationship to CIM/WBEM Standards

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.

DMTF Specification Specification Version
DSP 0004 - CIM Infrastructure Specification Version 2.3 Final, 4 October 2005
DSP 0200 - CIM Operations over HTTP 1.2.0, preliminary, 9 December 2004
DSP 0201 - Representation of CIM in XML 2.2.0, preliminary, December 2004
DSP 0202 - CIM Query Language Specification 1.0.0, preliminary, 9 December 2004
DSP 0205 - WBEM Discovery using SLP 1.0, preliminary, 27 January 2004
DSP 0206 - WBEM SLP Template 1.0.0, Preliminary, January 2004
CIM Schema 2.13.1 Final, Jan. 2005 ( default)

Conformance Exceptions to DMTF 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 known differences.  As of this release, some of the differences include the following:

  1. 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 a deviation from the specifications but is a different method of registration than many CIM Servers and means that the the provider qualifier is unused in Pegasus.
  2. Indications -Today Pegasus supports process indications and lifecycle indications when defined specifically by providers. Pegasus does not support lifecycle indications if they are not defined by the provider or for changes to CIM Classes.  For more information see the Pegasus CVS file:  pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm.
  3. IncludeQualifiers option on Instance Operations  - The DMTF specifications have deprecated the use of qualifiers on instance operations with the 1.2 CIM Operations Specification.  Some CIM Client implementations expect instances returned from the CIM Server to include the qualifiers defined in the class definition (such as KEY qualifiers on properties).   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.

  4. 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.
  5. MultiRequest Operations - Pegasus does not support the DMTF defined MultiRequest Operation option.

  6. MOF Compiler namespace pragma - The Pegasus compiler does not support the namespace pragma.

  7. Pegasus implements chunking based on the DSP0200 1.2.0 preliminary spec. including the operation trailer defined in that specification Refer to bug 6760 for more details.

OpenPegasus Supported Platforms

Each OpenPegasus release lists as 'active' platforms those hardware/software platforms that have recognized ports for the Pegasus code base including a maintainer for the platform that will be willing to regularly document issues and/or fix defects as the Pegasus code base is changed.  Pegasus may be operable on other platforms (ex. Windows 98) but without a group to provide the role of test and maintenance, correct operation of  Pegasus cannot be assured.  In all cases, including the active platforms, it is the responsibility of the entity that packages and/or compiles OpenPegasus for shipment or deployment, to read, and actively monitor the Pegasus bugzilla database for a list of relevant defects that affect their platform.   The platforms that are considered 'active' for this Pegasus release are:

Platform and OS



HP aC++ B3910B

Linux on Power




Linux Itanium


Linux IA-32 gcc (versions 2.9x, 3.xx, 4.xx)

Linux X86_64

gcc (versions 2.9x, 3.xx, 4.xx)

Windows 2000

Microsoft Visual C++ Ver.  6 and Microsoft .Net compiler version. Works on VC .NET 2003 v7.1). NOTE: Visual C++ Ver. 6 no longer being regularly tested.
Windows XP, Windows 2003

Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1. Note: Visual C++ Ver. 6 no longer being regular tested.
MacOS version 10.3 and higher gcc 4.01
HP OpenVMS 8.3 or later Alpha  HP C++ V7.3-009 or later required for OpenVMS Alpha
HP OpenVMS 8.3 or later IA64 HP C++ V7.3-023 or later required on OpenVMS IA64
Solaris 8 GNU  2.95.3,  Sun CC compiler V 5.8. Note that the latest thread patch (108993) may be required. (see Pegasus bug 4632)
Solaris 9 GNU  2.95.3, Sun WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09

Platform patches

The following is a list known of platform patches Pegasus requires.

  1. RHAS 2.1 needs the update to fix Red Hat Bugzilla 98815.

  2. RHEL 4.4 multithreading bug in getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is fixed in RHEL 4.5

  3. Red Hat and SUSE Linux multiple versions - multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla 6586) (Red Hat bug 248052)

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

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

Pegasus Defects

The Pegasus bugzilla database documents any defects found in Pegasus and  is available through the following link:  OpenPegasus bugzilla database.   Effective with the start of the Pegasus 2.6 work, all changes to the CVS tree were documented through bugs.  Bugs reports were filed not only for bugs and their corresponding fixes but also as part of the process of committing new code representing the work on PEPs done for Pegasus 2.6 and all subsequent versions.  Therefore, a search of the Open Pegasus bugzilla base for bugs with the tag for a particular version (ex.  2.6.0_APPROVED, 2.6.1_APPROVED, 2.7.0_APPROVED) will yield all changes to the Pegasus CVS tree for that Pegasus release.

     - Changes for Pegasus 2.7.0 release (bugs Tagged 2.7.0_APPROVED)  Pegasus 2.7.0_APPROVED bug list

Release Control and Version Definition Documentation

The Pegasus project is controlled largely through a set of documents (PEPs) that serve both as the definition and review mechanism for new and modified Pegasus functionality and for the definition and documentation of releases.

Specifically the following PEPs define the characteristics of this Pegasus release. These PEPs are available at OpenPegasus Approved PEPs.

  1. PEP 296 - OpenPegasus Release Definition - This PEP is used throughout the development of this version as the control point for functionality that will go into the release and points to all of the PEPs that represent the Pegasus  functionality changes for this version of Pegasus.
  2. PEP 292 -  OpenPegasus  Build and Configuration Options  for Selected Platforms
  3. PEP 293 - OpenPegasus 2.7 External Interfaces - Lists the public interfaces for clients and providers that are considered external and therefore "frozen".
  4. PEP 294 - OpenPegasus  SDK Packaging Definition - Defines the recommended set of files for inclusion in the OpenPegasus SDK
  5. PEP 295 - Pegasus  Runtime Packaging Definition - Defines the recommended set of files for inclusion in this OpenPegasus release.
  6. PEP 306 - Pegasus Release Notes (This document located in the approved PEP repository and the OpenPegasus source tree root directory)

General Documentation

The following documentation is available for the this Pegasus release:



Copyright (c) 2007 EMC Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open Group; VERITAS Software Corporation; Intel Corp.

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: