1. Pegasus Status Update April 2001 25 April 2001 Karl Schopmeyer

2. Agenda Items  Status Today  Work Accomplished  Plans

3. Pegasus Status Today  Project  Code  Users  Events

4. Version 1.0 Release  Functions  Complete except  Events, Query, WQL  Includes  All CIM Operations  Working Providers  Client/services/provider interfaces  Full CIM model in C++  Class and Instance Repository  Sample clients and providers  Compiler

5. Version 1.0 (cont)  Platforms  Linux, Windows, AIX?, Compaq?  Compilers  gcc, Visual C++  Documentation  Combined user/developer manual  Availability  Source Snapshots and CVS  Binary Release for Windows/Linux

6. User Interest  Intel  Compaq  IBM  Novell

7. Planned Events  Work Group  Meeting about 14 May 2001  DMTF Interop  Presentations at Interop (about 8 June 2001)  Open Group Members Meeting, July 2001  Week of 16 July  Theme is Manageability

8. Accomplishments  Public Release  WEB Site  www.opengroup.org/management/pegasus www.opengroup.org/management/pegasus  Open mailing list  Public discussion Events  TOG Regional meetings

9. Plans  New Versions  Platforms  Working Together

10. Planned Major Enhancements  Security  WQL  Indications  Non-Blocking  Multiple Provider modes  Built in / DLL / Remote  Discovery  Interop Extensions  CIMOM Manageability  Connectors Architecture  Services Extensions  Provider Toolkit  Better Clients  Multiple Language Support  Modules  Async Interface

11. Security  Status today  No Security  Objectives  DMTF Level authentication  SSL encryption  ACLs internally

12. WQL  State Today  No ExecQuery Implementation  Objective  Implement WQL Level 1  Plans  CIM Operation May 2001  WQL – Summer 2001

13. Indications  State Today  Nothing Today  Objective  Implement in stages  Stage 1  Listener, Indication Service Manager  Stage 2  Provider extensions for indications

14. Provider Communications  State Today  Dynamic Library Providers  Simple Interface  Minimal Toolkit  Objectives  Multiple communication models  Clarify Interface and move to Specification  Create extensive toolkit

15. Interop Extensions  State Today  TBD  Objectives  Implement the changes being made by Interop work Group to provide CIMOM and Provider capabilities, registration, etc.

16. Non-Blocking Operations  State Today  All operations are blocked except for TCP receive  Objectives  Non-blocking operations on providers, services, repositories  Problems  Portablity of the model across systems  Must include locks also (repository and provider)

17. Discovery  State Today  Nothing  Objectives  Use Well-known port (ASAP)  Implement SLP as test  Work with Interop to get SLP standardized

18. Services  State Today  We are having problems defining the concept  Objective  Define services concepts  Refine with initial services  Service examples  Indication Manager  Indication Registration Manager  Etc.

19. Clients  State Today  Simple WEB based CGI Client  Objective  Browser/Edit Graphic Client  Demonstration clients for particular functions  CLI client – Command Line  Test Client  Special demonstration clients.  Scripting Client (ex. TCL)

20. Providers  State Today  Simple Interface  Couple of basic providers  Objectives  Test Providers  Provider Toolkit  Working Providers to demonstrate concepts  Scripting Provider

21. Connectors  Concept  Separate communications from core CIMOM  Provide pluggable communications  Provide language conversion  Today  We understand our concept  No implementation  Objectives  Create connector definition  Create CIM classes to represent connectors  Implement several connectors  Ex. Cim-xml, soap, toMOF, etc.

22. Async Interface  State Today  None  Objectives  Still trying to clarify requirements

23. Other areas for Discussion  Working as a Project  Open questions

24. Open Questions Today  Licensing and the WBEMSource  Creating a working test environment  We feature many unit tests  Will initiate Client/server tests when server becomes a daemon  Need to add compiler test environment.  Additional help