Copyright 2008 Sun Microsystems

1. Introduction

   1.1. Project/Component Working Name:
        Pegasus CIMOM additional libraries and schemas

   1.2. Name of Document Author/Supplier:
        Author: Ken Davis

   1.3. Date of This Document:
        12/17/08

        1.3.1. Date this project was conceived:
               12/3/08

   1.4. Name of Major Document Customer(s)/Consumer(s):
        1.4.1. The PAC or CPT you expect to review your project:
               Solaris PAC
        1.4.2. The ARC(s) you expect to review your project:
               LSARC
        1.4.3. The Director/VP who is "Sponsoring" this project:
               scott.tracy@sun.com
        1.4.4. The name of your business unit:
               Storage Platform Software Group (SPSG)

   1.5. Email Aliases:
        1.5.1. Responsible Manager:
               ken.davis@sun.com
        1.5.2. Responsible Engineer:
               ken.davis@sun.com
        1.5.3. Marketing Manager:
               Margaret.Hamburger@sun.com
        1.5.4. Interest List:
               pegasus-l@openpegasus.org

2. Project Summary

   2.1. Project Description:
	 Add additional exported interfaces in the form of libraries and schemas to the Pegasus case 2008/040.

   2.2. Risks and Assumptions:
	 Libraries and schemas are needed by Pegasus utilities for proper operation.

3. Business Summary

   3.1. Problem Area:
	 Libraries and schemas listed here are required for the operation of Pegasus utilities 
	 delivered as part of the Pegasus case 2008/040, the CimpleWBEM 2008/690 
	 and KonkretCMPI 2008/689 cases.  

3.Market/Requester:
        Various Solaris OEMs and customers have developed and are developing
        applications and infrastructure. Internal groups (Amber Road,
        HoneyComb, AppIQ, Sysnet, etc.) will want to use the SDK, including proposed 
	 interfaces to develop providers and client applications.

   3.3. Business Justification:
        Needed to allow for Pegasus client and provider development, Pegasus 
	 utility operation and use of other OpenSolaris projects with dependencies on Pegasus.

   3.6. How will you know when you are done?:
        Installed pegasus libraries and schemas are added as exported interfaces for the Pegasus project.


4. Technical Description:

    4.1. Details:
	  Original Pegasus ARC case:  2008/040.  
	  Updating exported interfaces to include Pegasus libraries and schemas (below).

    4.2. Bug/RFE Number(s):
         None

    4.3. In Scope:
         See 4.1 above.

    4.4. Out of Scope:
	  Anything outside the modifications of interfaces proposed by this document.

    4.5. Interfaces (added):
        --------------------------------------------------------------------
        Exported                 Stability       Comments
        --------------------------------------------------------------------
	See the interfaces.txt document in case directory for interfaces being added to the Pegasus project.

    4.6. Doc Impact:
	  None.  Using current Pegasus docs.

    4.7. Admin/Config Impact:
	  None.

    4.8. HA Impact:
         N.A.

    4.9. I18N/L10N Impact:
	  None

    4.10. Packaging & Delivery:
	   Pegasus packages will be updated to reflect the interface changes proposed here.

    4.11. Security Impact:
	   None

    4.12. Dependencies:
          None

5. Reference Documents:
   LSARC/2008/040		http://sac.eng/Archives/CaseLog/arc/LSARC/2008/040/
   DMTF Web Site		http://www.dmtf.org/
   CIM Specification		http://www.dmtf.org/standards/

6. Resources and Schedule:

   6.1. Projected Availability:
	 NV_108

   6.2. Cost of Effort:
        Total: 1 person-week
        Breakdown:
		Determine required interface changes
		Update Pegasus packaging
		Test packages
		Create fasttrack for interface changes
		Submit SFW RTI

   6.3. Cost of Capital Resources:
        Unknown

   6.4. Product Approval Committee requested information:

        6.4.1. Consolidation or Component Name:
               SFW Consolidation

        6.4.3. Type of CPT Review and Approval expected:
               Standard

        6.4.4. Project Boundary Conditions:
               TBD

        6.4.5. Is this a necessary project for OEM agreements:
               No

        6.4.6. Notes:
               N.A.

        6.4.7. Target RTI Date/Release:
               NV_108

        6.4.8. Target Code Design Review Date:
               N.A.

        6.4.9. Update approval addition:
               N.A.

   6.5. ARC review type:
        FastTrack

   6.6. ARC Exposure:
        Open

7. Prototype Availability:

   7.1. Prototype Availability:
        N.A.

   7.2. Prototype Cost:
        N.A.