Pegasus Enhancement Proposal (PEP)


PEP #: None

Title: Addendum to Release Notes for Pegasus 2.9

Created: 16 September 2010

Authors: Karl Schopmeyer

Status:  draft

Version History:

 

 

 

 

 1.0

16 September 2010

Karl Schopmeyer

Initial Submission 













       

Abstract: This document addendum defines additional information to the Pegasus Release Notes for Pegasus Release 2.9 (PEP 345 and ReleaseNotes.htm in CVS) for the 2.9.2 release of the OpenPegasus CIM Server.  It is provided because there are changes to functionality and behavior between this release and the previous 2.9 releases. This document does not duplicate information in PEP 345 (Release Notes for Pegasus 2.9.  This information.was released as an addendum to the Release Notes to highlight these behavior/functionality differences. There is no ReleaseNotes addendum document for the Pegasus 2.9.1 release.

 Contents

  1. Addendum to OpenPegasus Functionality of This Release

Addendum to 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.9.0 is a major release and Pegasus 2.9.2 is a point release, extending the previous Pegasus release in selected areas as described this 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 Release 2.9.2

PEP/BUG # Description of Change Posted PEP
Version
PEP 356 Provider Module Grouping
 1.1
Bug 8811
 Move Pegasus config files to /etc
 8811

PEP 356 - The Provider Module Grouping will be formally introduced in Pegasus 2.11 but was felt to be important and so is being backported to earlier releases.  This feature provides for running different provider modules under the same pegasus out-of-process provider-agent. To control this behavior this it adds a property (ModuleGroupName) to the Pegasus Provider Registration class PG_ProviderModule and extends the Pegasus utility cimprovider to allow setting/modifying the group into which a provider module is set. See Pegasus  bug 8789 for details of the patch that implements this functionality.  Note that this will be introduced in the nest point release of Pegasus 2.10 also.

Bug 8811 - Pegasus originally kept configuration files in /var/lib/Pegasus but distributions (ex. RHEL, SUSE, ...) put all configuration files into /etc directory.  This patch makes /etc the configuration file location for Pegasus Linux Source releases.

Prior to upgrading OpenPegasus, the administrator should back up the files listed below. The first directory contains the OpenPegasus configuration files and SSL certificate files. The second directory contains the repository files. The third file contains any cimserver configuration properties that take effect on cimserver startup.

Pegasus 2.5.1+/2.6.X /2.7.X/2.8.X/2.9.X/2.10.X Directory Structure
    /etc/Pegasus
   /var/lib/Pegasus/repository
   /var/lib/Pegasus/cimserver_planned.conf

Pegasus 2.4.3 Directory Structure
    /etc/opt/tog-pegasus
    /var/opt/tog-pegasus/repository
   /var/opt/tog-pegasus/cimserver_planned.conf

NOTE: All changes between Pegasus 2.9.0 and Pegasus 2.9.2 can be reviewed by searching the Pegasus Bugzilla for the keywords: 2.9.1_APPROVED and 2.9.2_APPROVED.


Licensed to The Open Group (TOG) under one or more contributor license agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this work for additional information regarding copyright ownership. Each contributor licenses this file to you under the OpenPegasus Open Source License; you may not use this file except in compliance with the License.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.