Pegasus
Enhancement Proposal (PEP)
PEP #: 305
Title: Release Notes for OpenPegasus 2.6.1
Created:
Authors: Dave
Sudlik
Status: approved
Version History:
|
|
|
|
1.0 |
|
Dave Sudlik |
Initial
Submission. Updates for 2.6.1 (from 2.6) are highlighted in
this color. |
1.1 |
8 August 2007 |
Dave Sudlik |
Updates from review |
Abstract: This document defines the release notes for the
2.6.1 release of the OpenPegasus CIM Server. The purpose of this PEP is
simply to summarize the characteristics of this release, point to other
documentation that defines the release in more detail, and provide
additional information about this release that is not available in the
other Pegasus documentation.
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.
Pegasus 2.6.1 is a "point"
release, extending Pegasus 2.6 in
selected areas. Normally an OpenPegasus "point" release does not
contain major new pieces of functionality, but in this case one new PEP
was added for IPv6 support, the description of which has been added to
these Release Notes.
The major areas of development for this release were as follows. For more information access the documented PEP:
Table of Major Changes for this Release
PEP | Description | Posted PEP Version |
---|---|---|
291 | OpenPegasus
Support for IPv6: Stage 1 |
1.2 |
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.
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. Setting this to
'true' before building OpenPegasus will enable the IPv6 support. In
2.6.1 this variable will default to 'false' to omit the IPv6 support.
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:
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:
or
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:
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: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.9 Final, Jan. 2005 ( default) 2.13.1 (available in pegasus CVS) |
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:
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.
MultiRequest Oprations - Pegasus does not support the DMTF defined MultiRequest Operation option.
MOFCompiler namespace pragma - The Pegasus compiler does not support the namespace pragma.
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 |
Compilers |
HP-UX |
HP aC++ B3910B |
Linux on Power |
gcc |
zLinux |
gcc |
Linux Itanium |
gcc |
Linux IA-32, 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 (aka
v7.1) |
Windows XP |
Microsoft
Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1 |
MacOS version 10.2 and higher | gcc 3.3, gcc 4.01 |
HP OpenVMS Alpha |
HP C++ V7.3-009 for OpenVMS Alpha and above |
HP OpenVMS IA64 | HP C++ V7.2-021 on OpenVMS IA64 and above |
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 |
The following is a list of platform
patches Pegasus requires.
RHAS
2.1 needs the update to fix Red Hat Bugzilla 98815.
Further information regarding Pegasus support on IBM platforms can be found at: http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm
Further information regarding Pegasus support on HP platforms can be found at: http://www.hp.com/go/wbem.
The Pegasus bugzilla database documents any defects found in Pegasus and is available through the following link: OpenPegasus bugzilla database. Note that all changes committed for this release have been marked with the keyword 2.6.1_APPROVED so that all changes for this release can be found with the following bug search. Effective with the start of the Pegasus 2.6 work, all changes to the CVS tree were documented through bugs. Thus bugs were filed not only for bugs and their corresponding fixes but also as part of the process of committing new code representing the work on PEPs done for Pegasus 2.6. Therefore, a search of the bugzilla base for bugs with the tag 2.6.1_APPROVED will yield all changes to the Pegasus RELEASE_2_6-branch CVS branch since Pegasus 2.6.0.
- Changes for Pegasus 2.6.1 point release (bugs Tagged 2.6.1_APPROVED)
Pegasus
2.6.1_APPROVED bug list
The Pegasus project is controlled largely through a set of documents (PEPs) that serve 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 the
Pegasus 2.6 release. These PEPs are available as
OpenPegasus
Approved PEPs.
For this 2.6.1 point release,
only
this document, the 2.6.1 Release Notes, was updated. All other
references should be back to the 2.6 release PEPs.
The following documentation is available for the this Pegasus release:
Copyright (c) 2006 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:
THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION
NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE
SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.