The Pegasus Project

1. The Pegasus Project December 4, 2000

2. Part I: Overview

3. What is Pegasus? Pegasus is a CIM reference implementation initiated by the Open Group�s Manageability Services Broker Working Group.

4. The Working Group Philosophy Manageability not management. No standards without implementation.

5. Manageability not management The working group�s objective is not to manage systems but to make them manageable by promoting a standard instrumentation environment. The actual management of systems is left to systems management vendors.

6. No standards without implementation The process of implementation provides a rigorous process for testing the validity of standards. Therefore all standards must be validated by implementation.

7. Key Pegasus Contributors Karl Schopmeyer (Tivoli Systems). Michael Brasher (BMC Software). William Blair (BMC Software). Heather Kreager (IBM). Martin Kirk (The Open Group).

8. BMC Experience Architect and project lead for Patrol�s CIM-like implementation on which the new Patrol line is based. That implementation (called the Common Object System) and CIM have similar facilities.

9. Lessons Learned from COS Must be Light Weight (COS Lite). Must be scaleable (SmartSockets). These must be plug in modules: Thread manager. Traffic encryption. Repository.

10. Key Characteristics Open source Portable C++ core Light weight

11. Comparison

12. Pegasus License Agreement Copyright (c) 2000 The Open Group, BMC Software, Tivoli Systems, IBM 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 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.

13. Goals of Pegasus Testbed for ideas and standards. Easy instrumentation of data. Support for many platforms. Define services standards*. Interoperability down to provider level*.

14. Part II: Architecture

15. Classical CIM Architecture

16. CIM Operations Get, Create, Modify, Delete, Enumerate classes, instances, qualifiers, and properties. Traverse associations. Invoke methods. Subscribe to events. Execute queries.

17. Pegasus Architecture

18. Component Interoperability In the classical architecture, interoperability is only supported between the client and server. In addition, the Pegasus architecture aims to support provider/server interoperability.

19. Provider/Server Interoperability Goal Write a provider once and run it under any CIM server implementation.

20. Provider/Server Interoperability Provider/Server Interoperability will be achieved in three ways: Participating in efforts to standardize the Provider/Server protocol. Proposing provider API standards. Writing adapters enabling Pegasus providers to run under other CIM servers.

21. In-Process and Out-of-process Providers It will be possible to develop a provider and compile it once and then configure it dynamically to run in-process (within the server process) or out of process (communicates with the server using either IPC or CIM/HTTP).

22. Services The core server components are organized into loadable modules called services. Standard APIs are defined for each service. Alternative implementations can be provided later without recompiling the Pegasus server.

23. Core Services Event service. Query engine service. Class repository service. Instance repository service. Thread service. Traffic Encryption service.

24. Repository Service Example One example of a core service is the repository. Pegasus provides a simple repository implementation (based on disk files). An alternative repository based on a commercial database may be implemented later.

25. Thread Service Example There will be a thread service: Pegasus will provide a thread service based on ACE wrappers. Alternative thread services can be implemented and plugged in.

26. Provider Adapters Provider adapters will be developed so that a provider developed using the Pegasus provider API, will also run under Microsoft�s WMI. There are no plans to do the same for Sun�s implementation.

27. Part III: Status and Plans

28. Existing Subsystems Phase-0 Container library. CIM objects. XML parser. CIM/XML encoding. TCP session layer. HTTP protocol. CIM/HTTP protocol*. Class repository. Phase-0 MOF compiler. Web interface*. Client library.

29. Planned Subsystems Phase-1 Instance repository Provider loading Provider dispatcher Associations Sample providers Authentication Thread manager Object editor Phase-2 Query Events Out-of-process providers Traffic encryption Provider adapters Internationalization