Pegasus Enhancement Proposal (PEP)
PEP #: 083
Title: Release Notes, Pegasus 2.2
Version: 1.4
Created: 6 June 2003
Authors: Karl Schopmeyer
Status: Accepted
Version History:
Version | Date | Author | Change Description |
---|---|---|---|
1.0 | 6 June 2003 | Initial Submission | |
1.1 | 10 June 2003 | K. Schopmeyer | Expand and incorporate comments received for first version |
1.2 | 11 June 2003 | K. Schopmeyer | Corrections from Discussion 10 June Architecture Team Telecon |
1.3 | 17 June 2003 | K. Schopmeyer | Corrections from Telecon 13 June and comments on previous version. |
1.4 | 18 June 2003 | K. Schopmeyer | Minor Corrections. Passed ballot with these corrections. |
Abstract: This document defines the release notes that are available with the Pegasus 2.2 release.
The Pegasus 2.2 release is available as a source release in both ZIP and TAR formats. The release can be downloaded from the OpenPegaus Web site at www.openpegasus.org.
In addition, the release is available through Pegasus CVS as the branch tag RELEASE_2_2_0-branch. This defines the current released version of Pegasus 2.2 . In addition, the following tags exist for the release. RELEASE_2_2_0-root which defines the initial release point of Pegasus 2.2 and the point at which it branched from the trunk.. Other tags may exist to mark release candidate snapshots, etc. These will be announced on the web site and the Pegasus mailing list.
The instructions for acquiring the released code are on the WEB site. Installation instructions are part of the readme in the root of the source tree.
The OpenPegasus project is currently not providing binary releases. However, binary releases may be available of selected ports and are documented on the OpenPegasus web site.
There may be point releases to the Pegasus 2.2 release and these will be announced on the Pegasus web site.
The overall level of functionality in the Pegasus environment is as follows:
CIM Server
CIM Operations
- Class Operations (get, delete, modify, enumerate) - Operational
- Instance Operations (get, delete, modify, enumerate) - Operational
- Association Operations (reference, referencenames, associators, associatornames - Operational NOTE: The provider interfaces are still considered experimental today and may be modified or extended for Pegasus 2.3, particularly for possible performance improvements.
- Methods- Operational
- Query operation (Not implemented)
Indications
Process indications are operational in the Server. This includes support for subscriptions, filters, and indication handlers, the provider API for indications and the CIMXML indication handler. A second Pegasus sever can be use as an Indication client. However, the Client indication support is incomplete and completion is planned for Pegasus 2.3.
Query Language
The query language today is based on WQL and is implemented and used for filters. However, the executeQuery operation has not been implemented pending the availability of a standard DMTF Query language.
Class Repository
This release includes the XML based file/directory Class repository.
Instance Repository
This release includes an XML based file/directory Instance repository. The instance repository is used as the default repository unless a flag is set disabling this repository for client operations
Security
- Basic Security (Note that Digest based security is not implemented)
- SSL support - SSL is implemented in Pegasus using the OpenSSL libraries. Pegasus does not provide the OpenSSL libraries but SSL can be used on any platform that supports OpenSSL
Platform Management Functions
- Configuration through the defined configuration parameters.
- Daemon operation on all supported platforms
Providers
There are a number of standard providers available in Pegasus release. This includes providers in the following:
Internal Providers
- __Namespace provider - Serves the __Namespace class to allow manipulation of namespaces.
- Subscription Classes Providers - These provide subscription, filter, and indication handler processing.
- Provider registration Providers - This provide registration of providers using the PG_Provider classes.
- ConfigProvider - Manages Pegasus configuraton information.
- UserAuthProvider - Manages password, etc.
- ShutdownProvider - Provides support for Pegasus shutdown.
Generic
Generic OperatingSystem provider. See the directory src/Providers/generic.
Test/Sample
See the directories src/Providers/TestProviders and src/Sample for more information about test and sample providers.
Managed System Providers
ComputerSystem, DNSAdmin, DNSService, Operating System, Process, Processor. For more information on these providers see the documentation for each provider in the directory src/Providers/ManagedSystem
CIMOM Statistics Providers
IBMStatisticalData - This is an early version of the work that became CIM_StatisticalData
Linux Specific Providers
There are a number of providers in this category including DiskDrive, CDROMDrive, Interrupt, IOPOrt, IPROute, NetworkAdapter, Operating System, PCI Controller, PRocessor, ProviderData, ProviderSupport, SoftwareElement. For more information about these providers see the documentation in the directory src/Providers/linux
CIM_Schema
The default CIM_Schema loaded with the Pegasus 2.2 release is the DMTF CIM 2.7 Final release. In addition, Pegasus includes a number of local classes defined for Pegasus. These are visible in the Schemas directory.
Pegasus MOF Compiler
Pegasus implements a MOF compiler that can operate either at the client interface (cimmof) or directly interfacing with a CIM repository (cimmofl). There were new commands implemented in the Pegasus 2.2 compiler to support class replacement.
Note that use of cimmofl to manipulate instances in the repository bypasses any provider that is registered to serve the instances and simply installs the instances in the instance repository; this may result in corruption if providers are using the repository. Use of cimmofl to manipulate instances served by a registered providers is therefore discouraged. Use of cimmof rather that cimmofl is encouraged
Client Tools
Pegasus CIM Server Adminstration
Information client tools
These tools provide information on the objects managed by the server.
Test support Tools
Pegasus InterfaceAPIs
The Client and Provider API are frozen and at the same level as Pegasus version 2.1. This set of interfaces is listed in PEP 40 available from the web site. This includes the following major functions
The functions are documented in their respective header files and HTML documentation based on the information in the header files extracted with the doc++ tool will be available on the OpenPegasus web site.
Each Pegasus release lists as supported platforms those hardware/software platforms that have recognized ports for the Pegasus code base including a maintainer for the platform that will be willing to regularly assure that the port is maintained as the Pegasus code base is changed. Pegasus may be operable on other platforms (ex. Windows 98) but without a group to provide the role of test and maintenance, the Pegasus project cannot assure operation. The supported platforms for Pegasus release 2.2 are:
Platform and OS | Compilers |
AIX 5.2 | VisualAge C++ Version 5.0.2.3 |
HP-UX | HP aC++ B3910B |
Linux Itanium | gcc |
Linux IA-32 | gcc (versions 2.9x and 3.xx) |
Windows 2000 | Microsoft Visual C++ Ver 6 |
Windows XP | Microsoft Visual C++ Ver. 6 |
Generally Pegasus tries to conform to the CIM specifications. It is a major goal of the OpenPegasus project to both drive and utilize the specifications. However, today there are a number of differences. As of Pegasus 2.2, some of the differences include the following:
1. Provider Registration - Pegasus supports registration through a set of Provider registration classes and does not support the Provider Qualifier.
2. Indications. Today Pegasus supports process indications but does not include any specific support for lifecycle indications.
3. Today Pegasus provides alternatives to some of the classes in the Interop Schema including CIM_StatisticalData and Pegasus 2.2 does not include CIM_Namespace support (__Namespace is supported).
Each Pegasus release is defined through the Pegasus PEP Process and there is a specific PEP that defines the changes that go into each release. The defining PEP for Pegasus 2.2 is PEP 15 which is viewable on the Pegasus WEB site. In addition, each release includes Bug corrections. Generally all of the changes should be defined by either the PEPs or the bugs closed for the release.
Some of the major changes for this release include:
In addition, the Pegasus Project implemented a number of procedures and processes to gain further control of the project.
The detailed list of enhancements is defined through the Pegasus PEPs. Detailed information on each enhancement is available in the PEP which is available on the Pegasus WEB site. The PEPs defined for Pegasus 2.2 include (NOTE: This list includes both those implemented and those deferred or withdrawn):
PEP # | PEP Description | Actual Date | Comments |
---|---|---|---|
0 | PEP#000-Template for Creating PEPs | Adopted | |
1 | Pegasus Project Enhancement Proposals - Guidelines and the Approval Process | Adopted | PEP Process introduced into Pegasus 2.2 process. |
2 | Pegasus Bug Tracking and Bug Fix Commitment Process | Deferred | Deferred to Pegasus 2.3. |
3 | Platform Maintainers Process and Procedures | Deferred | Deferred to Pegasus 2.3. |
4 | Managing CVS Test and Build | Deferred | Deferred to Pegasus 2.3. |
5 | Indications Improvements | Withdrawn | Replaced by PEP 47. |
6 | Pegasus Architecture Process | Deferred | Deferred to Pegasus 2.3. |
7 | CIMMOF Improvements | Withdrawn | Replaced with PEP 43 and 45. |
8 | Runing CIM Server as a Service on Windows | January 25, 2003 | |
9 | CVS Branch Merge proposal for Pegasus 2.2. | Withdrawn | Replaced by PEP 46 |
10 | N/A | Withdrawn | PEP Number Skipped. |
11 | Adding Support for XML Character References | Feb 11, 2003 | |
12 | Finish Association Provider Interface and Testing | Pending for Pegasus 2.2 | |
13 | Upgrading to use CIM 2.6 and 2.7 Schemas | Withdrawn | Plan to replace with a series of class specific PEPs (e.g., 42 and 52). |
14 | Pegasus Release Milestones | Adopted | Milestones introduced into Pegasus 2.2 release process. |
15 | This PEP defines Pegasus Release 2.2. | Adopted | See version history section of this PEP for status. |
16 | Replacement of PG_ |
April 25, 2003 | |
17 | Merge-local: Add containers for indication subscription and delivery parameters | Feb 12, 2003 | |
18 | Merge-local: Modification of WQL classes to use CIMName | Feb 12, 2003 | |
19 | Merge-local: Support for Multiple Listen Sockets | March 11, 2003 | |
20 | Merge-local: Local Connections Using Unix Domain Sockets | March 11, 2003 | |
21 | Merge-local: Add HUP Signal Handler | March 11, 2003 | |
22 | Merge-local: Windows Time/Date Order Reversal in getCurrentASCIITime() | Feb 21, 2003 | |
23 | Merge-local: Consolidation of SSLDir Files | Feb 21, 2003 | |
24 | Merge-local: Provider Registration Consistency | March 24, 2003 | |
25 | Merge-local: Add a simple display consumer to test indications | March 28, 2003 | |
26 | Merge-local: RT_IndicationProvider Enhancement | Feb 26, 2003 | |
27 | Merge-local: Custom hash table hash and equal function objects to support case-sensitivity of namespace names. | Feb 25, 2003 | |
28 | Enhancements of osinfo to support remote connections. | March 7, 2003 | |
29 | Pegasus CIMOMHandle | ||
30 | SLP Support in Pegasus 2.2 | Deferred | Deferred to Pegasus 2.3 |
31 | Merge-local - Incorrect error message generated during Authentication failure. | March 7, 2003 | |
32 | Merge-local: HP-UX IA64 and Linux IA64 platforms to only use PAM based Authentication. | March 13, 2003 | |
33 | Enhancement to Red Hat IA32 and IA64 RPM (packaging and distribution) files | March 13, 2003 | |
34 | Enhanced support for doc++ in SDK head files | March 12, 2003 | |
35 | Add support for /dev/random in SSLContext | March 13, 2003 | |
36 | Merge-local: Add ipinfo client. | April 1, 2003 | |
37 | Indication API Support Commitment | Plan to submit SDK directories once FC has been achieved and the 2.2 API enhancements have been tested. | |
38 | Proposal to Enhance Provider Manager in Pegasus 2.2 | April 17, 2003 | |
39 | Improvements to HTTPConnection/Monitor in Pegasus 2.2 | Withdrawn | Changes will be submitted through Bugzilla process. |
40 | Pegasus External Interface Definition | Plan to submit SDK directories once FC has been achieved and the 2.2 API enhancements have been tested. | |
41 | Modifications for successful build on zOS USS | ||
42 | Update to CIM Schema Version 2.7 | April 29, 2003 | The DMTF plans to release an update, 2.7.2, to the CIM 2.7.1 Schema. Plan to move to this version as soon as it is available. |
43 | cimmof - Updating Class Definitions | April 29,2003 | |
44 | Logging Enhancements | March 27, 2003 | |
45 | MOF Compiler Scenarios | Deferred | Deferred to Pegasus 2.3 |
46 | Proposal (2nd alt) to merge working branches in Pegasus Open-source CVS Repository | Adopted | Process used for mday-2-0-patches branch merge. |
47 | Dynamic Message Routing and Late Binding in Pegasus 2.2 | May 1, 2003 | One additional change, dependent on PEP 12, is still pending. |
48 | Merge openpegasus.org-wbem-rh32-2.2.spec into openpegasus.org-wbem-2.2.spec | March 19, 2003 | |
49 | Wbemexec enhancement to verify trust store validation result | March 19, 2003 | |
50 | MD5 Digest Authentication | Deferred | Deferred Indefinitely |
51 | Configuration Property Cleanup | March 25, 2003 | |
52 | Adding the CIM_Interop Classes to Pegasus | Deferred | Deferred |
53 | Logging Enhancements Code Points Table | April 10, 2003 | |
54 | Changing IBMStatisticalData to CIMStatisticalData Classes | Deferred | Deferred to Pegasus 2.3 |
55 | Update Software License to reflect correct years of our copyright and list of contributors | Pending for Pegasus 2.2 |
Some of the work that was specifically planned for Pegasus 2.2 did not make the cut. As shown in the table above this includes the following:
In addition, a number of problems were corrected in this release. The list of problems corrected/closed includes the following:
ID | Sev | Pri | Plt | Owner | State | Result | Summary |
---|---|---|---|---|---|---|---|
12 | Compiler accepts qualifier declaractions that already exist | ||||||
31 | Handle absent/null ClassName and String parameters | ||||||
35 | CIMOM need to timeout waiting for authentication challeng... | ||||||
55 | Add appropriate Version tag to all classes in ManagedSyst... | ||||||
59 | CIMServer core dumps when simultaneous clients connect to it | ||||||
61 | Subscription tests intermittently fail with core dump. | ||||||
97 | cimom doesn't look in /opt/wbem/providers/lib for provide... | ||||||
98 | repository won't be default instance provider on enumInst... | ||||||
103 | Pegasus Namespace creation/deletion is Incompatible with ... | ||||||
107 | CIMServer died while testing NameSpace operations(05/21/02) | ||||||
117 | Info. logging in ConfigManager related files to be change... | ||||||
119 | cimserver does not use 'cimserver_planned.conf' when 'cim... | ||||||
124 | SUSE 8.0 tries to bind to wrong port | ||||||
125 | Bad formatting on HTTP Header Namespace Fields | ||||||
135 | Client Response decoder does not handle EMPTY tag | ||||||
136 | PEGASUS requires a objectpath tag on associatorsnames res... | ||||||
137 | Null Value datetime on received XML causes exception | ||||||
142 | CIMOMHandler use from a provider makes cimserver lock | ||||||
143 | CIMObjectPath parsing fails if objectname has ':' character | ||||||
145 | make repository does not take dependences into account in... | ||||||
152 | The ccimoperationrequestdecoder namespace vs cimobject te... | ||||||
166 | Casting an OperationContext object to an IdentityContaine... | ||||||
167 | TestBase64 takes a long time to complete on Tru64 | ||||||
172 | SIGABRT when CLI's call exit( ) | ||||||
173 | Porting changes for OS/400 | ||||||
174 | Associators fn throwing exception "not Implemented" | ||||||
175 | TheadPool Fails occasionally | ||||||
176 | Bugs in cimconfig | ||||||
177 | Bugs in cimprovider | ||||||
178 | Command line bugs in cimmof | ||||||
179 | Multiple calls to Providers for any association query | ||||||
180 | cimserver starts in the wrong port if wbem-http already i... | ||||||
181 | Association providers are not invoked | ||||||
182 | Compilation fails in System.h | ||||||
183 | Compile error in cimserver_unix.cpp, cimserver_os400.cpp | ||||||
184 | Compile Errors | ||||||
185 | Unrecognized config property: start | ||||||
186 | ThreadPool test dies on Semaphore::wait() exception | ||||||
187 | WHERE Clause Properties Incorrectly Removed From Indication | ||||||
188 | SELECT Clause Is Ignored | ||||||
189 | Indication Contents Are Incorrect | ||||||
190 | Change Consumer Shared Library Major Version Number for H... | ||||||
191 | Memory Error in Indication Response Handler | ||||||
192 | install/remove/start/stop options should work on Windows ... | ||||||
193 | Incorrect message on bad cimserver option | ||||||
194 | General error response on associator and reference cim op... | ||||||
195 | Common mutex in HTTPConnection may cause deadlock | ||||||
197 | HTTP method not set correctly in all responses | ||||||
198 | Shared library major version number must be updated | ||||||
199 | cimserver core dumps on HP-UX when using PAM with trusted... | ||||||
201 | Bug in IBM_CIMOMStatDataProvider | ||||||
204 | Compile error in PERFINST code | ||||||
205 | Inconsistent Provider Registration MOF | ||||||
207 | CIMObject Header Not URI-Safe | ||||||
208 | Modify PEGASUS_SSLCLIENT_CERTIFICATEFILE to define client... | ||||||
209 | SSLContext does not configure OpenSSL to use the client t... | ||||||
214 | Build problems under GCC 3.2 (RedHat 8) | ||||||
215 | Use Environment Variables for Redhat IA32 | ||||||
216 | Versioning of Linux Shared Libraries Does Not Work | ||||||
218 | CIMClient::disconnect / HTTPConnector::disconnect memory ... | ||||||
219 | cimXML for Indication Delivery Uses Outdated Specification | ||||||
220 | Indication Service no longer should check select or where... | ||||||
221 | Typos in sample indication provider files | ||||||
222 | cimserver core dumps when multiple threads call OpenSSL f... | ||||||
223 | ProviderManager deadlock during provider initialization | ||||||
224 | Excessive number of open files when running cimmof on CIM... | ||||||
225 | cimconfig aborts on bad argument value | ||||||
226 | Remove unnecessary include files from cimmofClient.cpp | ||||||
227 | System::is_absolute_path does not consider slash differen... | ||||||
228 | FileSystem::getAbsolutePath is incorrect on Windows | ||||||
229 | IPC test fails unnecessarily | ||||||
230 | Change "severity" property to "logLevel" | ||||||
231 | Linux OperatingSystem provider leaks file handles | ||||||
232 | ThreadPool hangs intermittently on Windows | ||||||
233 | logLevel is not properly initialized | ||||||
234 | Debug messages printed to console in Thread.cpp | ||||||
235 | Inconsistent error message in XmlReader | ||||||
236 | server.pem and client.pem have expired certificates | ||||||
238 | Signal code is platform-specific | ||||||
239 | HPUX Provider libraries need to be changed to .so/.sl | ||||||
240 | Performance Enhancement For The Provider Disable and Enable | ||||||
241 | Memory leak in CIMDateTime | ||||||
242 | Wrong status code returned by the Server to the client. | ||||||
244 | Incorrect coupling of remote privileged access and namesp... | ||||||
245 | Providers link with libpegserver | ||||||
248 | When certificate was in trust store and ssl verify callba... | ||||||
251 | Minor Makefile Changes | ||||||
252 | STRIPCRS option is not working correctly | ||||||
253 | pegasus_sleep() mishandles fractional seconds | ||||||
254 | maxWaitTime code did not get called in cimserver_unix.cpp | ||||||
255 | RT_IndicationProvider Defines Duplicated Properties | ||||||
256 | Code in the ExportClient is obsolete | ||||||
257 | OpenSSL locking callbacks not initialized | ||||||
258 | Incorrect conversion from char to Char16 in String.cpp | ||||||
260 | Compile error in reg_table.cpp | ||||||
261 | need additional compile and link flags for GCC use of dyn... | ||||||
262 | Compile error in ThreadWindows.cpp | ||||||
264 | Enable Indications for Linux | ||||||
265 | Enable Strong Encryption for Linux | ||||||
266 | Build fails in ProviderModule.h |
268 | code for PEP 17, bugzilla 197 removed | ||||||
269 | ProcessIndicationProvider cannot unload | ||||||
270 | ProcessorProviderTestClient Link Failing | ||||||
271 | TestMakefile bugs on linux | ||||||
272 | Command line utilities use a different configuration than... | ||||||
273 | Local Domain Socket Path Missing for Linux | ||||||
274 | Control characters in CIM data cause response truncation | ||||||
275 | Unable to load providers | ||||||
276 | MSVC compilation failure in Provider directory | ||||||
277 | Client::connect_local() does not work on linux when using... | ||||||
278 | cimserver -s does not shut down cimserver | ||||||
280 | Provider Registration Manager does not update hash table ... | ||||||
282 | Pegasus cimmof compiler does not correctly handle default... | ||||||
284 | sscanf failing to return conversion error on Linux IA-32 | ||||||
287 | Duplicate definition of ROOT in config.mak should be rem... | ||||||
288 | CLIClientLib compile failure | ||||||
289 | Sample providers are not registered | ||||||
290 | MessageTypeToString() returns incorrect results | ||||||
291 | CLI test client compile error | ||||||
292 | Resolve SSL Header File Conflict | ||||||
293 | uninitialized variable in provider manager | ||||||
295 | make repositoryServer fails - Namespace Provider not found | ||||||
297 | dynamic class routing table does not route to association... | ||||||
299 | Update PegasusVersion.h for release 2.2 | ||||||
300 | 'cimserver -s' returns control to the user before cimser... | ||||||
301 | provider manager merge lost CMPI adapter | ||||||
302 | Modify openpegasus.org-wbem-2.2.spec for CIM27 mofs | ||||||
303 | Running "make tests" fails while using TestMakefile | ||||||
304 | Cannot have multiple cimserver CIMOMs running as a window... | ||||||
305 | Remove extra -aE option from makefiles when final CIM27 i... | ||||||
307 | Using the PEGASUS_REMOVE_DEPRECATED | ||||||
308 | Threadpool - uninitialized value | ||||||
309 | Authentication Failure return wrong error message | ||||||
310 | pegasus/src/Clients/CLITestClients/CLIClientLib build fai... | ||||||
311 | pegasus/src/Clients/CLITestClients/CLI/CLI.cpp build failure | ||||||
312 | osinfo incorrectly formats datetime value | ||||||
313 | ConfigManager Test Failure - Unrecognized config property... | ||||||
314 | Client Test fails - Person class not found | ||||||
315 | No try block around configurtion property get (Maximum br... | ||||||
320 | cimprovider -r -m dose not unload the provider | ||||||
321 | Compile error building ProviderMoulde.cpp | ||||||
325 | Add handler for TERM signals | ||||||
327 | TestMakefile and mak/buildMakefile need updates for windows | ||||||
332 | logic error in Provider::tryTerminate |
The following documentation is available for the Pegasus 2.2 release:
There are a number of known bugs in the Pegasus 2.2 release. The following list of known open bugs as of the CVS branch for Pegasus 2.2 is in the following table. Note that this list will change as bugs are fixed and probably new bugs found. To get the latest bug status for Pegasus, use the OpenPegasus bug manager (Bugzilla) which is can be found at http://cvs.rdg.opengroup.org/bugzilla/
66 bugs found.
ID | Sev | Pri | Plt | State | Result | Summary | |
---|---|---|---|---|---|---|---|
323 | TestClient Failure - Associations | ||||||
18 | WQLParser::parse returns parse error on valid query after... | ||||||
246 | Security issues with CIMOMHandle | ||||||
212 | Cimserver uses lots of cpu "idle time" when the cimserver... | ||||||
263 | The pegasus client has a rapid memory leak and causes the... | ||||||
134 | Pegasus Compiler puts VALUE.OBJECT around qualifier Decl | ||||||
141 | ObjectPath MalformedObjectPath exceptions leak back throu... | ||||||
298 | dispatcher lookup optimization | ||||||
285 | TestStopwatch Occassionally Fails with an Assert | ||||||
90 | Deep Inheritance and Local Only Flags Do Not Work | ||||||
168 | Incomplete CIMObjectPath wen calling providers | ||||||
171 | DateTime key properties are not handled properly | ||||||
328 | datetime value parsing handling of interval format | ||||||
250 | _MakeAddress() returns FALSE when given an IP address whi... | ||||||
319 | CIMQualifier::getPropagated() returns Uint32 instead of B... | ||||||
331 | undefined CIMSERVER_START_FILE | ||||||
318 | RPM SPEC file (openpegasus.org-wbem-2.2.spec ) is outdat... | ||||||
92 | UTF8 Characters on XML input and XML output | ||||||
93 | UTF8 input to compiler | ||||||
70 | Client API should support socks | ||||||
146 | There is no way to do pre-build or post-build stuff with ... | ||||||
89 | HTTPConnection must return 413 response on oversized requ... | ||||||
101 | The requestUri may need to be pruned of the host name. | ||||||
63 | Indication Service should not respond to request until re... | ||||||
126 | CIMDateTime::getDifference returns incorrect result for s... | ||||||
279 | CIMDateTime::getDifference returns incorrect result on so... | ||||||
326 | Use calloc for PAM response memory allocation | ||||||
133 | Pegasus compiler converts Schema Qualifer decl to CLASS | ||||||
211 | CIMObjectPath Legal Host name incomplete | ||||||
283 | PEGASUS_ASSERT in /src/Pegasus/Client/CIMOperationRespons... | ||||||
28 | Locale information not passed through system | ||||||
196 | Memory leak in MessageQueueService | ||||||
202 | Porting changes for HP-UX | ||||||
203 | Porting changes for IA64 Linux | ||||||
206 | Client requests time out with PERFINST enabled | ||||||
267 | ComputerSystem provider does not set path in enumerateIns... | ||||||
281 | setQualifier throws CIM_ERR_ALREADY_EXISTS | ||||||
120 | CIMClassRep::addProperty() sets ClassOrigin incorrectly. | ||||||
42 | Windows OS provider doesn't fill in CSName and Name keys | ||||||
144 | cimserver writes on console even when started in daemon mode | ||||||
148 | CGIClient.cpp changes '-' to '.' | ||||||
237 | Incorrect use of statistic macros | ||||||
249 | cimmof returns code of 0 on error | ||||||
316 | Return code of cimserver is always zero. | ||||||
317 | Startup script for RedHat - rpm/wbem1.rh7 is not complian... | ||||||
247 | ssl verify callback results are ignored when certificate ... | ||||||
329 | tomof client fails on call - cannot find repository | ||||||
330 | incorrect usage of htons in systemunix.cpp | ||||||
286 | Error information is no longer returned on failure to loa... | ||||||
210 | MOF output for Reference values generates XML not mof | ||||||
217 | Error in CIMClass Create on some Linux Platforms | ||||||
243 | Compiler misses MOF syntax error in value | ||||||
213 | Insufficient Code Coverage | ||||||
294 | Indication Service: conditional jump or move depends upon... | ||||||
54 | Need license info in ManagedSystem provider registration ... | ||||||
306 | cimconfig -s property=value -p allows you to set non-vali... | ||||||
3 | Weak association qualifier check missed | ||||||
30 | Reference keys of reference type cannot be parsed | ||||||
71 | Statistics MOF included in ManagedSystem Schema | ||||||
149 | src/Clients/ToMofClient/ToMofClient.cpp warning during build | ||||||
150 | warnings compiling src/Server/cimserver.cpp | ||||||
296 | pegasus/src/Pegasus/Server/tests accidently disabled Feb '02 | ||||||
322 | readme.txt file is outdated | ||||||
324 | Add system error message to trace message on failed syste... |
The Pegasus 2.2 release is maintained as a branch to the Pegasus CVS. The branch name is RELEASE_2_2_0-branch. There will be bug correction work done against the branch, corrections installed in the branch, and incremental releases of the branch in parallel with the work on Pegasus 2.3.
It will be the responsibility of any developer doing bug fixes on the Pegasus 2.2 branch to document the bugs in Pegasus Bugzilla reports and also to insure that the bug is corrected in the Pegasus 2.3 release. We will not attempt to merge any changes from Pegasus 2.2 back to 2.3 on a project basis.
Incremental releases with bot CVS tagging and snaphshots of the code will be created when the sufficient bugs have been corrected that the project and users feel that it is necessary to create the snapshot. The list of bug fixes will be documented for each incremental release.
The Pegasus project uses Bugzilla to report bugs, define requested enhancements, and manage work on bugs. The bug reporting system is open to anybody and it is not required to be a member of the Pegasus project to submit bugs to this system. We sincerely hope that all Pegasus users will use this bug reporting system to report Pegasus bugs.
The Bug reporting system can be accessed via the Pegasus Web site or directly via the Pegasus Bugzilla BugList. When reporting bugs, please be a specific as possible, reporting the pegasus version, problem definition, environment (ie. system, OS, etc.). If a potential solution is defined for the problem, please document the solutions and provide a patch file if possible. Please be sure to note the the Pegasus version number 2.2 on any bugs submitted to Pegasus Bugzilla.
Copyright (c) 2003 BMC Software; Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open Group
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.