PEP

PEP #: 15

TITLE: Pegasus 2.2 Release Definition

Version : 1.13

Authors: Denise Eckstein

State: Accepted

Approvals Required: Architecture Team and Steering Committee

Type: Release Definition

Created: 02/01/03

Version History:

Version	Date	Author	Change Description
1.0	02/01/03	Denise Eckstein	Initial Submission
1.1	02/09/03	Denise Eckstein	Changed title of section 4 from "Release Metrics" to "Quality Metrics" Changed title of section 4.2 from "Test Coverage" to "Code Coverage" Added Process Requirements 2.1.1, 2.1.2, and 2.1.3 Removed requirement 2.2.5 (i.e, "Frozen API") and added to requirement 2.2.1 Removed word "subsystem" and clarified requirements in 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.6, 2.2.7, 2.2.8 Added requirements 2.2.9 (Mike Day), 2.3.1 (Karl), 2.4.1 (Mike Day), 2.4.2 (Mike Day). Lowered Code Coverage goals for FC. Removed definition of Defect Density from section 4.3. Added reference to PEP 14 for definition of Quality Metrics. Added Defect Density metrics. Added February 28 as 85% FC date.
1.2	02/11/03	Denise Eckstein	Add PEP column to each of the requirement tables. Added Subscription to requirement 2.2.2 Added HP as the Sponsor to 2.2.7 Added MUST Priority and IBM as the Sponsor to 2.2.9, 2.4.1, 2.4.2 Updated description in 2.4.2 Added item 2.4.3 (cimmof enhancements) Added item 2.4.4 (Upgrade to 2.7) Added item 2.4.5 (SLP) Added item 2.4.6 (Digest Authentication) Added item 2.4.7 (Provider Manager rewrite) Added item 2.4.8 (HTTPConnection+ rewrite) Added item 2.4.9 (RPM Packages) Added item 2.4.10 (CIMOM Handle) Added item 2.4.11 (Multiple Listen Sockets) Added item 2.4.12 (Unix Domain Sockets) Added item 2.4.13 (HUP Signal Handler)
1.3	02/15/03	Denise Eckstein	Added PEPs 5, 37 to item 2.2.1 Marked item 2.2.7 (DMTF SQL Compatiblity) DEFERRED, pending DMTF Specification approval. Added OpenVMS as a supported platform. Added PEP "Not Numbered" to item 2.4.7 (Provider Manager Rewrite) Added PEP 33 to item 2.4.9 (Linux Packaging) Added PEP 29 to item 2.4.10 (CIMOM Handle) Moved RSO date from 2/15/03 to 2/24/03. Moved FC date from 3/10/03 to 3/31/03. Moved CTC date from 4/14/03 to 5/12/03. Moved SR date from 4/21/03 to 5/19/03.
1.4	02/22/03	Denise Eckstein	Added OS/400 as a support platform (Chuck Carmack) Changed Priority of 2.4.1 (Query) from MUST to HIGH WANT Added item 2.4.14 (Add support for CMPI) Added item 2.4.15 (Add support for Provide2 API) Added PEP 38 to item 2.4.7 (Provider Manager) Modified description of 2.4.7 to reflect PEP 38. Tracking "Provider2 Support" requirement under item 2.4.15. Added PEP 30 to item 2.4.5 (SLP) Added Approval Date to Requirement Tables Added reference to PEP 40 (External Interface Defintion) in section 1.3. Removed PEP 7, from item 2.4.3 (MOF Compiler). PEP 7 has been withdrawn. Added PEP 39 to item 2.4.8. Noted that PEP 39 has been withdrawn. Assigned TOG as owner of 2.4.4 (Upgrade to CIM Schema 2.7). Added item 2.4.16 (InterOp Schema Providers). Moved RSO date from Feb. 24 to March 10. RSO requires that all MUST PEPs have been approved.
1.5	03/01/03	Denise Eckstein	Added the following bullet to Release Contraints Section: All new development MUST be compliant and MUST NOT regress compliance with the following DMTF Specifications: Specification for CIM Operations over HTTP, version 1.1. Representation of CIM in XML, version 2.1. XML DocumentType Definition, version 2.1. CIM Schema 2.7 based on the following input from Diane Olsen. "Client interoperability: Pegasus V2.2 interoperates with any CIM client that supports CIM-XML version xxx (fill in). OR could state it this way: Pegasus V2.2 supports CIM clients xxx, yyy, zzz (fill in - example, SNIA Version x.y). (Typically this is the specific clients that have been through interoperability testing)." Change item 2.4.6 Digest Authentication from WANT to MUST. (Diane Olsen) Added Windows 2000 and Windows XP as a support platform (Tony Fiorentino) Assigned PEP 42 to 2.4.4 (Upgrade to CIM Schema 2.7). Assigned PEP 43 to 2.4.3 (MOF Compiler). Assigned PEP 44 to 2.4.2 (Logging).
1.6/1.7	03/08/03	Denise Eckstein	Added AIX as a support platform (Kim Tran) Changed incorrect reference to PEP 35 to PEP 37 in item 2.2.1. Listed IBM as Sponsor for item 2.4.6 (Digest Athentication). Added "Approval Date" of 3/7 for PEP 33 in Item 2.4.9 (RPM Packages). Added "Approval Date" of 3/7 for PEP 19 in Item 2.4.11 (Multiple Listen Sockets). Added "Approval Date" of 3/7 for PEP 20 in Item 2.4.12 (Unix Domain Sockets). Added PEP #45 (MOF Compiler Usage Scenarios) to Item 2.4.3. Change item 2.4.14 "Add support for CMPI" from MUST to HIGH WANT.
1.8	03/16/03	Denise Eckstein	Update 2.4.6 (Digest Authentication) requirement per Diane Olson's comment: "MD5 digest authentication is added to Pegasus server (not the Pegasus CIM client), with an implementation provided for OS/400 only." Added PEP #50 to item 2.4.6 (Digest Authentication) Added zOS to Supported Platforms (Marek Szermutzky) Added "PEP Submittal Window Closed" Milestone Moved RSO Date to March 25 Marked item 2.2.8 as "Deferred" Removed PEP #10 from item 2.4.3 (MOF Compiler) Removed PEP #13 from item 2.4.4 (CIM Schema 2.7) Correction: item 2.4.4 (CIM Schema 2.7) should have referred to PEP 42 not PEP 40. Added "Approval Date" of 3/11 for PEP 42 in item 2.4.4. Added "Approval Date" of 3/11 for PEP 38 in item 2.4.7. Added "Approval Date" of 3/11 for PEP 29 in item 2.4.10. Added "Approval Date" of 3/11 for PEP 43 in item 2.4.3.
1.9	03/23/03	Denise Eckstein	Added Linux IA32 to Supported Platforms (Ed Boden) Added "Pending 2.2 RSO" comment for PEP 15 in item 2.1.2. Added "Approval Date" of 3/20 for PEP 37 in item 2.2.1. Added "Approval Date" of 3/20 for PEP 16 in item 2.2.2 and 2.4.4. Added "Approval Date" of 3/20 for PEP 25 in item 2.2.6. Added "Approval Date" of 3/20 for PEP 44 in item 2.4.2. Added "Approval Date" of 3/18 for PEP 50 in item 2.4.6. Added item 2.4.17 (PEP 47 - Dynamic Message Routing). Added "Approval Date" of 3/18 for PEP 47 in item 2.4.17. Added PEP 52 to item 2.4.16 (Implementing instances for CIM_Interop ObjectManager and CIM_Namespace classes). Marked Approval for PEP 45 has HIGH WANT - DEFERRED. Added PEP 52 to item 2.4.5 (Support for SLP).
1.10	04/07/03	Denise Eckstein	Added "Approval Date" of 04/04 for PEP 30 in item 2.4.5. Added "Approval Date" of 04/04 for PEP 52 in item 2.4.5 and 2.4.16.
1.11/1.12	04/07/03	Denise Eckstein	Modified the sentence "Please refer to PEP 14 for the definition of Pegasus Quality Metrics" to "Please refer to PEP 14 (Pegasus Release Milestones) for the definition of Pegasus Quality Metrics and Milestones." Marked PEP 5 as Withdrawn in item 2.2.1 Replaced PEP 5 with PEP 47 in item 2.2.9 Added "Approval Date" of 3/18 for PEP 47 in item 2.2.9. Added PEP 53 (Logging Enhancements Code Point Table) to item 2.4.2 Mark item 2.4.6 (Digest Authentication) as Deferred Indefinitely. Removed IBM as the sponsor. Changed Priority to NOT REQUIRED. Replaced "Date" Column in Schedule table with "Planned Date", "Revised Date", and "Actual Date" Columns. Changed RSO Revised Date to April 11, 2003. Changed FC Revised Date to April 30, 2003. Changed CTC Revised Date to May 26, 2003. Changed SR Revised Date to June 2, 2003. Changed item 2.4.15 (Add support for Provider2 API) from MUST to HIGH WANT.
1.13	04/20/03	Denise Eckstein	Added "Approval Date" of 4/11 for PEP 53 in item 2.4.2. Added "Approval Date" of 4/11 for PEP 15 in item 2.1.2. Change State to "Accepted". RSO Approved 4/14 with exceptions for PEPs 1, 2 and 12. (Steering Committee Decision - 4/14/03).

Abstract: This PEP defines Pegasus Release 2.2.

1.0 Release Overview

1.1 Product Objectives

Create a freely available, highly portable, production quality C++ implementation of the DMTF WBEM Standard.

1.2 Release Objectives

Invest in the definition and integration of a core set of processes to improve predictablity and quality of Pegasus Releases.
Deliver the core set of components required to support Indication subscription, generation, processing, filtering and delivery.
Deliver the core set of components required to support Association Operators.

1.3 Release Constraints

Unless explicitly approved as an exception, this release

MUST NOT regress functionality
MUST NOT regress quality
MUST be backward compatible with 2.1 developed Providers and Clients.
Refer to PEP #40 for a list of external interfaces.
All new development MUST be compliant and MUST NOT regress compliance with the following DMTF Specifications:
- Specification for CIM Operations over HTTP, version 1.1.
- Representation of CIM in XML, version 2.1.
- XML DocumentType Definition, version 2.1.
- CIM Schema 2.7

2.0 Requirements

2.1 Process Requirements

ID	Description	Priority	Sponsor	PEPs	Approval Date DDMMYY
2.1.1	Drive definition and effective implementation of PEP process.	MUST	TOG	1	1 - Exception Granted
2.1.2	Drive understanding and adoption of common Release Milestone terminology and metrics.	MUST	HP	14, 15	14 - 140203 15 - 110403
2.1.3	Drive definition and adoption of a process for Defect Tracking and Resolution.	MUST	IBM	2	2 - Exception Granted

2.2 Indication Requirements

ID	Description	Priority	Sponsor	PEPs	Approval Date DDMMYY
2.2.1	Deliver components and API definitions required to support Indication Providers.	MUST	HP	5, 37	5 - Withdrawn 37 - 200303
2.2.2	Deliver functional, DMTF compatible Indication Subscription, Filtering & Processing components.	MUST	HP	16, 18	16 - 200303 18 - 110203
2.2.3	Deliver components required to support CIM-XML Indication Delivery.	MUST	HP	NR	Defect fixes only.
2.2.4	Support a mechanism to pass Subscription information to Indication Providers.	MUST	HP	17	17 - 110203
2.2.6	Deliver sample Indication Consumer and Indication Provider	MUST	HP	25, 26	25 - 200303 26 - 140203
2.2.7	Modify existing Pegasus WQL implementation to be compatible with DMTF CQL specification.	HIGH WANT	HP	NR	Deferred
2.2.8	Deliver SNMP Indication Handler.	WANT		NR	Deferred
2.2.9	Need the ability to used providers as low-level Indication Handlers. Such a provider would then process the Indication and deliver it to higher-level, more complete Indications Handlers. E.g., to a CIM-XML Indication Handler. The rationale behind this requirement is to allow low-level handling of Indications in their native CIMInstance format as an intermediate step. This gives developers more flexibility in processing Indications. It allows experimentation with Indication Handlers without modifying the CIM Indication Schema.	MUST	IBM	47	47 - 180303

2.3 Association Operator Requirements

ID	Description	Priority	Sponsor	PEPs	Approval Date DDMMYY
2.3.1	Validate and complete the Association Provider API and functionality.	MUST	TOG	12	12 - Exception Granted

2.4 Other Requirements

ID	Description	Priority	Sponsor	PEPs	Approval Date DDMMYY
2.4.1	We need the ability to develop and deploy query providers after 2.2 is functionality complete. For this to be possible, we need to develop a sample query provider and test the execution paths within the 2.2 code to ensure that execute query, etc work within the CIMOM.	HIGH WANT	IBM
2.4.2	Need to expand the existing logging hooks to provide a full, configurable set of records that customers can use in the field to expedite customer support. This is an IBM requirement for 2.2. There are basically two parts - 1) send messages to the system logs for the platform (platform-specific work) 2) analyze the code to add more logging calls so that Pegasus can be serviced in the field.	MUST	IBM	44, 53	44 - 200303 53 - 110403
2.4.3	Changes to the MOF compiler to improve useability.	43 - MUST 45 - HIGH WANT	IBM	43, 45	43 - 110303 45 - DEFERRED
2.4.4	Upgrade to CIM Schema 2.7.	MUST	TOG	16, 42	16 - 200303 42 - 110303
2.4.5	Support for SLP.	MUST	IBM	30, 52	30 - 040403 52 - 040403
2.4.6	Digest Authentication. For this release, the requirement is to support MD5 digest authentication on the server side. Support for digest authentication on the client side is not required. This is an OS/400 requirement only.	NOT REQUIRED		50	Deferred Indefinitely
2.4.7	Provider Manager changes to improve performance and increase supportability. This includes support for loading and unloading providers.	MUST	IBM	38	38 - 110303
2.4.8	HTTP Connection+ rewrite to improve performance and increase supportability.	MUST	IBM	39	Withdrawn
2.4.9	RPM Packages for Red Hat IA32 and IA64.	MUST	HP	33	33 - 070303
2.4.10	Functional CIMOM Handle.	MUST	IBM	29	29 - 110303
2.4.11	Support for Multiple Listen Sockets.	MUST	HP	19	19 - 070303
2.4.12	Support for Unix Domain Sockets.	MUST	HP	20	20 - 070303
2.4.13	Add HUP Signal Handler.	HIGH WANT	HP	21	21 - 140203
2.4.14	Add support for CMPI (Common Manageabilty Programming Interface)	HIGH WANT	IBM
2.4.15	Add support for Provider2 API	HIGH WANT	IBM
2.4.16	Develop Providers for various InterOp classes.	MUST	TOG	52	52 - 040403
2.4.17	Dynamic Message Routing.	MUST	IBM	47	47 - 180303

3.0 Supported Platforms

Description	Sponsor
AIX	IBM
HP-UX PA-RISC	HP
HP-UX IA-64	HP
Linux IA-32	IBM
OpenVMS	HP
OS/400	IBM
Red Hat Linux IA-64	HP
Windows 2000	EMC
Windows XP	EMC
zOS	IBM

4.0 Quality Metrics

Please refer to PEP 14 (Pegasus Release Milestones) for the definition of Pegasus Quality Metric and Milestones.

4.1 Functional Test Passing

	Percent Passed
FC	80%
CTC	100%

4.2 Code Coverage

	Breadth	Depth
FC	70%	40%
CTC	95%	70%

4.3 Defect Density

	Blocker/Critical/Major	Normal	Minor/Trivial
FC (Goal/Acceptable)	1/2	3/5	5/10
CTC (Goal/Acceptable)	0/0	0/1	4/4

4.4 Continuous Hours of Operation (CHO)

	CHO
Acceptable	72

5.0 Schedule

Milestone	Planned Date	Revised Date	Actual Date	Comments
PEP Submittal Window Closed	March 19, 2003	March 19, 2003	March 19, 2003
RSO	March 25, 2003	April 11, 2003	April 14, 2003	RSO Exceptions for PEPS 1, 2, and 12.
FC	March 31, 2003	April 30, 2003
CTC	May 12, 2003	May 26, 2003
SR	May 19, 2003	June 2, 2003