Pegasus An Open-Source CIMOM Implementation

Transcription

1 Pegasus An Open-Source CIMOM Implementation Karl Schopmeyer Chair, Open Group Enterprise Management Forum A presentation for the DMTF 2002 DevCon Tuesday 11 June 4:30 5:30 pm

2 Agenda Overview -What (and why)is Pegasus? The Pegasus Environment The Pegasus Software Architecture Pegasus Status Today The Pegasus Project A Challenge for the Future DMTF 2002 Developers' Conference June 10-13, 2002 Page 2

3 1. Overview DMTF 2002 Developers' Conference June 10-13, 2002 Page 3

4 What is Pegasus? Pegasus is an open-source reference implementation of the DMTF WBEM specifications Pegasus is a work project of the TOG Enterprise Management Forum Pegasus is a platform for building application management Pegasus is a function-rich, production-quality opensource implementation designed to be used in high volume server implementations. DMTF 2002 Developers' Conference June 10-13, 2002 Page 4

5 Why Produce Pegasus? Demonstrate manageability concepts. Provide additional standards for WBEM Provide a working implementation of WBEM technologies Provide an effective modular implementation Support other Open Group manageability standards Base Platform for Open Group Application management Projects Help make WBEM real Pegasus was Initiated in 2000 by the Open Group in collaboration with: BMC Software IBM Tivoli Systems DMTF 2002 Developers' Conference June 10-13, 2002 Page 5

6 Key Pegasus Objectives Open Source Standards Based Portable Pegasus Continuity Efficient And Lightweight Production Quality Modular And Extensible DMTF 2002 Developers' Conference June 10-13, 2002 Page 6

7 Manageability not management Pegasus Working Group Philosophy 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 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 DMTF 2002 Developers' Conference June 10-13, 2002 Page 7

8 Open Source Code and documentation freely available Open Group and Source Forge MIT source license Open to contributions No commitment to Open Group to use code DMTF 2002 Developers' Conference June 10-13, 2002 Page 8

9 Portable Designed for multi-platform, multi-os, multi-compiler implementation Platforms ported today UNIX (AIX, HPUX, Solaris, Tru-Unix) Linux Windows Platforms (NT, 2000, 9x) Compaq Himalaya (Tandem) DMTF 2002 Developers' Conference June 10-13, 2002 Page 9

10 Efficient and Lightweight Core written in C++ Designed for execution efficiency Designed to be production-quality solution DMTF 2002 Developers' Conference June 10-13, 2002 Page 10

11 Standards Based Based on DMTF CIM and CIM-XML specifications Open Group is active partner in DMTF Growth through participation in specification growth Commitment to continue DMTF compliance DMTF 2002 Developers' Conference June 10-13, 2002 Page 11

12 Modular and Extensible Minimize core object broker. Maximize extensibility through plug-in components Component types Providers Provider interfaces Clients Repositories (additional repository handlers) Manageability service extensions Protocol Adapters Modules (extend and modify core functions) Modularity is key to doing parallel development and allowto extensibility DMTF 2002 Developers' Conference June 10-13, 2002 Page 12

13 Project for Continued Development WBEM will continue to develop functionality and standards Open Group will develop application management partly around Pegasus Pegasus Development will continue beyond current versions Integrate contributions Add basic new functionality Etc. DMTF 2002 Developers' Conference June 10-13, 2002 Page 13

14 The Open Group Enterprise Management Forum Projects include: Pegasus Ex-SNIA Java Based open-source Implementation Application Management APIs ARM AIC Software Licensing Standards QoS Task Force User/Supplier interaction forum to advance QoS and Service Level Standards Working with DMTF, IETF, TMN DMTF 2002 Developers' Conference June 10-13, 2002 Page 14

15 2. The Pegasus Environment DMTF 2002 Developers' Conference June 10-13, 2002 Page 15

16 Pegasus Architecture Interoperable* MOF MOF Compiler Compiler Consumers Consumers Clients CIM/HTTP CIM Server Standard Interfaces Services Interoperable* CIM/HTTP In-Process Consumers Consumers Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 16

17 CIMOM Capabilities Respond to Operations defined in CIM Operations spec. Create, Modify, Delete operations on Class, Instance, Property, Qualifier Handle Provider Registration Forward Requests to Providers, repositories, etc. Read/Write access to Management Information Maintain Class/Instance Information Traversal of Associations Use of WBEM Query Language Syntax/Semantic checking (with Qualifiers) Available Implementations Microsoft (in Windows2000), Sun WBEM SDK, SNIA, Open Group Pegasus, DMTF 2002 Developers' Conference June 10-13, 2002 Page 17

18 Key Interoperability Interfaces Manageability to Manager Multiple management systems Common open manageability Object Manager / Providers Multiple Providers Encourage common providers Enterprise Management Enterprise Management Management System Management System Console Console CIM CIM Object Manager Provider / Resource Interface Protect Applications Make application management easy CIM CIM Providers Application Application Application Application Application Application Application Application DMTF 2002 Developers' Conference June 10-13, 2002 Page 18

19 The CIM Operations CIM CIM Operations Consumers Consumers Clients Standard Interfaces Interoperable* CIM/HTTP CIM Object Mgr Interoperable* CIM/HTTP In-Process Services Repository Repository Consumers Consumers Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 19

20 Operations Routing Class Operations Routed to the Class Repository Instance Operations To Provider if Provider Qualifier exists To Instance repository if no Provider Instance routing at Class Level Today Issues Routing at instance level DMTF 2002 Developers' Conference June 10-13, 2002 Page 20

21 The CIM Indications Interoperable* Consumers Consumers Clients CIM/HTTP Standard Interfaces SNMP, SNMP, cimxml, cimxml, etc. etc. Indication Handlers CIM Object Mgr Interoperable* CIM/HTTP In-Process Services Repository Repository Indicators Consumers Consumers Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 21

22 Modularity and Extensibility Providers Grow with DMTF provider concepts Provider Interfaces Protocol Adapters (connectors) Client - Xml-cim today (Soap, etc. in future) Provider, service, repository, etc. Modules Modularize core so it can be extended and modified through attachable modules Manageability Service Extensions Think super providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 22

23 Building A Modular Manageability CIM CIM Client Connector Connector Environmnent CIM CIM Client XML-CIM Module Module Module Module Module Module Module Module Connector Connector Core Object Broker Connector Connector Service Service Extension Service Extension Service Extension Service Extension Service Extension Service Extension Service Extension Extension Repository Repository Undefined Provider Connector Connector Provider... Resources Resources Resources DMTF 2002 Developers' Conference June 10-13, 2002 Page 23

24 Pegasus Manageability Consumers Providers Broker Providers Resource CIMOM Environment Management Management System System Consumers XML/CIM Management Gateways Connector System Connector Apps CIM CIM Object Object Broker Broker Provider Registration Service Registration Request Routing Securiy AIC AIC Provider ARM Provider Apps OS Etc. Application Application Consumer Consumer SNMP Provider... Services core*** additional Class Class Repository Repository Instance Instance Repository Repository DMTF 2002 Developers' Conference June 10-13, 2002 Page 24 Interface For Spec

25 Provider 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. Goal Write a provider once and run it under any CIM server implementation. Provider/Server Interoperability: Participating in efforts to standardize the Provider/Server protocol. Proposing provider API standards. Writing adapters enabling Pegasus providers to run under other CIM servers. Adapters enabling other providers to run under Pegasus DMTF 2002 Developers' Conference June 10-13, 2002 Page 25

26 Important Provider Interfaces SUN WBEM Provider Interface Java based Classes, etc. similar to Pegasus C Provider Interface Sun has a specification here. We will support multiple provider interfaces and language bindings. DMTF 2002 Developers' Conference June 10-13, 2002 Page 26

27 In-Process and Out-of of-process Providers Today Pegasus based on shared Library Providers Extend to Internal Providers IPC based Providers Providers in Remotes systems Objectives: Write Provider once and compile/link for different environments Technique Use connectors as basis for provider/cimom communication Issues Security, discovery DMTF 2002 Developers' Conference June 10-13, 2002 Page 27

28 Manageability Service Extensions Super Providers Access to the Core Broker Examples Indication Subscription service. Class repository service. Instance repository service. DMTF 2002 Developers' Conference June 10-13, 2002 Page 28

29 Connectors (Protocol Adapters) Functions Adapt to different protocols Characteristics Protocol Encoding Security Discovery Examples Xml-CIM Local Protocols Soap WMI Corba environment interface External Corba Environment Corba Corba Connector Connector Xml-cim Xml-cim Client Client Xml-cim Xml-cim Connector Connector Pegasus Core Pegasus Pegasus Provider Provider Connector Connector Soap Soap Client Client Soap Soap Connector Connector Remote Provider DMTF 2002 Developers' Conference June 10-13, 2002 Page 29

30 Pegasus Interfaces Common Interface base for Clients, providers, services, connectors Based on CIM Operations over HTTP Additional functions for each interface Interfaces separated from implementation CIM CIM Client Connector Connector Connector Connector Core Object Broker Service Service Extension Service Extension Service Extension Service Extension Service Extension Service Extension Service Extension Extension Repository Repository Provider DMTF 2002 Developers' Conference June 10-13, 2002 Page 30

31 3. The Pegasus Software Architecture DMTF 2002 Developers' Conference June 10-13, 2002 Page 31

32 Introduction

33 Major Components Client Client CIM Clients CIM Server Repository Client Client CIM Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 33

34 Topics Communication. Representation of CIM Elements. The Client Interface. The CIM Object Manager. The Provider Interface. The Repository Interface. DMTF 2002 Developers' Conference June 10-13, 2002 Page 34

35 Communication

36 Pathways of Communication Client Client CIM Clients CIM Server CIM Repository Client Client CIM Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 36

37 Component Location A component may be located in one of three places with respect to the CIM Server. In-process. Local out-of-process (on the same machine). Remote out-of-process (on another machine). For example, a provider may be in-process, local, or remote. DMTF 2002 Developers' Conference June 10-13, 2002 Page 37

38 Component Location in Pegasus Today Client Provider Repository In-Process Local Remote X X X DMTF 2002 Developers' Conference June 10-13, 2002 Page 38

39 Possible Communication Mechanisms Components could potentially communicate with the CIM Server using the following mechanisms: CIM/HTTP (remote). Proprietary TCP-based protocol (remote). Direct call (in process). Shared memory (local). Named pipes (local). DMTF 2002 Developers' Conference June 10-13, 2002 Page 39

40 Communication Mechanisms in Pegasus Client Provider Repository In-Process Local Remote CIM/HTTP Direct Call Direct Call DMTF 2002 Developers' Conference June 10-13, 2002 Page 40

41 Client Communication Uses CIM/HTTP as sole protocol. Asynchronous socket I/O. An efficient XML parser. Fast enough to eliminate the need for a proprietary protocol. DMTF 2002 Developers' Conference June 10-13, 2002 Page 41

42 An Efficient XML Parser No memory heap usage during parsing. Modifies message in place to avoid copying. Non-validating parser ( loose validation ). DMTF 2002 Developers' Conference June 10-13, 2002 Page 42

43 HTTP Implementation Uses asynchronous socket I/O in conjunction with message queues to achieve optimal throughput. Provides entry points to adding web server capabilities such as putting and getting of documents (to support remote upgrade and deployment later on). DMTF 2002 Developers' Conference June 10-13, 2002 Page 43

44 Proposals Support out-of-process providers (local and remote). Support out-of-process repositories (local and remote). Location independent provider development. DMTF 2002 Developers' Conference June 10-13, 2002 Page 44

45 Representation of CIM Elements Representing CIM Elements in Pegasus with C++

46 CIM Data Types in C++ Uint8 Sint8 Uint16 Sint16 Uint32 Sint32 Uint64 Sint64 Real32 Real64 Boolean Char16 String CIMDateTime CIMReference DMTF 2002 Developers' Conference June 10-13, 2002 Page 46

47 CIM Values in C++ CIM values (property, parameter, and qualifier values) are represented using the CIMValue class. This class: Encapsulates a union of all CIM data types. Has a type member indicating the type currently being represented. Provides access/modifier methods overloaded for each CIM data type. DMTF 2002 Developers' Conference June 10-13, 2002 Page 47

48 CIM Elements in C++ CIMClass CIMInstance CIMProperty CIMMethod CIMParameter CIMQualifierDecl CIMQualifier DMTF 2002 Developers' Conference June 10-13, 2002 Page 48

49 Class Declaration Example (Part 1) Consider the following MOF class declaration: class Alarm { [key] uint64 id; string message = none ; }; This class is defined in C++ as follows: CIMClass alarmclass( Alarm ); CIMProperty id( id, Uint32(0)); id.addqualifier(cimqualifier( key, true)); CIMProperty message( message, none ); alarmclass.addproperty(id); alarmclass.addproperty(message); Or more succinctly like this: CIMClass alarmclass( Alarm ); alarmclass.addproperty(cimproperty( id, Uint32(0)).addQualifier(CIMQualifier( key, true))).addproperty(cimproperty( message, none )); DMTF 2002 Developers' Conference June 10-13, 2002 Page 49

50 Property Iteration Example: The properties of a class may be iterated like this: CIMClass c; for (Uint32 i = 0, n = c.getpropertycount(); i < n; i++) { CIMProperty p = c.getproperty(i); } DMTF 2002 Developers' Conference June 10-13, 2002 Page 50

51 The Client Interface

52 The Client Interface Client Client CIM Clients CIM Server Repository Client Client CIM Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 52

53 The Client Interface A C++ interface for interacting with the Pegasus Server (or any CIM Server). Uses CIM/HTTP to communicate. Provides a method for each CIM operation defined in the CIM Operations over HTTP, V1.0 specification. DMTF 2002 Developers' Conference June 10-13, 2002 Page 53

54 The CIM Operations GetClass GetInstance DeleteClass DeleteInstance CreateClass CreateInstance ModifyClass ModifyInstance EnumerateClasses EnumerateClassNames EnumerateInstances EnumerateInstanceNames ExecQuery Associators AssociatorNames References ReferenceNames GetProperty SetProperty GetQualifier SetQualifier InvokeMethod DMTF 2002 Developers' Conference June 10-13, 2002 Page 54

55 CIM Operation Example CIM Operations Specification Pegasus Class Method <instance> GetInstance ( [IN] <instancename> InstanceName, [IN,OPTIONAL] boolean LocalOnly = true, [IN,OPTIONAL] boolean IncludeQualifiers = false, [IN,OPTIONAL] boolean IncludeClassOrigin = false, [IN,OPTIONAL,NULL] string PropertyList [] = NULL ) virtual CIMInstance getinstance( const String& namespace, const CIMReference& instancename, Boolean localonly = true, Boolean includequalifiers = false, Boolean includeclassorigin = false, const Array<String>& propertylist = NULL_PROPERTY_LIST); DMTF 2002 Developers' Conference June 10-13, 2002 Page 55

56 Client Connection Example A client connects to the CIM Server on the host called saturn at port 5988 like this: Selector selector; CIMClient client(&selector); client.connect( saturn:5988 ); DMTF 2002 Developers' Conference June 10-13, 2002 Page 56

57 GetClass Example A client gets a class like this: CIMClass alarmclass = client.getclass( root/cimv2, Alarm ); DMTF 2002 Developers' Conference June 10-13, 2002 Page 57

58 Client Proposals Asynchronous Interface APIs Interface independent of local/remote client DMTF 2002 Developers' Conference June 10-13, 2002 Page 58

59 The CIM Object Manager

60 The Pegasus CIMOM Client Client CIM Clients CIM Server Repository Client Client CIM Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 60

61 Request Lifecycle Incoming Request Outgoing Response 1. Receive TCP Message Channel Channel 8. Transmit TCP Message 2. Process HTTP Request Protocol Protocol 7. Form HTTP Response 3. Decode from XML Encodings Encodings 6. Encode to XML 4. Dispatch Request Dispatcher Repository Aggregator 5. Aggregate Resul Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 61

62 CIMOM Modules Channel - Implements transport mechanism (e.g., TCP). Protocol - Implement application protocol (e.g., HTTP). Encodings - Implements encoding and decoding of messages (e.g., CIM-XML). Dispatcher - Dispatches messages to provider(s)/repository. Repository - Implements CIM Repository. Aggregator - Aggregates results. DMTF 2002 Developers' Conference June 10-13, 2002 Page 62

63 Module Concept The internal CIMOM architecture is being refined into a set of modules. Each module handles part of the request lifecycle. Alternative implementations may be provided for each module type. New module implementations can be used to modify or refine the behavior of the CIMOM and to facilitate porting. DMTF 2002 Developers' Conference June 10-13, 2002 Page 63

64 Module Implementations Channel - provide a named-pipe implementation. Protocol - provide a proprietary binary protocol. Encodings - provide a binary encoding scheme. Repository - provide a relational-based implementation. Traffic Encryption - SSL implementation. Authentication Challange and response DMTF 2002 Developers' Conference June 10-13, 2002 Page 64

65 Queued Operation Model Internal representation of operations/indications is messages Major components are queue driven Mapped to direct interfaces (ex. getclass) at provider manager. Message manager controls flows, proiorities, etc. Advantages Efficiency Threading Extensible interfaces Flow Control DMTF 2002 Developers' Conference June 10-13, 2002 Page 65

66 Module Definition and Loading Modules implement one of the module interfaces (e.g., Repository). Modules are configured as dynamic libraries. Modules listed in modules file. Modules loaded by CIMOM on startup. DMTF 2002 Developers' Conference June 10-13, 2002 Page 66

67 Local Destination CIM-XML Indication handler SNMP Indication handler Client Interface (cim-xml today) Authentication Repository Indication Handler Manager Acceptor Http Delegator XML XML Decoder Encoder CIM XML Comm Module CIM Operations Processing subsystem Response Authorization generator Operations Request Processor PegasusMsgDispatcher Indication Consumer Manager Pegasus Module Organization xxx Http xxx Operations Response Processor Provider Mgr Subsystem provider provider provider Provider Manager Indication Import CIM Export Request Decoder CIM Export Request Processor Indication Consumer Manager Subscription Service and Indication Processor CIM Control Services Start/Stop Function Provider registration Function User/Auth. Function jj Jj Namespace Services Subsystem Formal Provider Interface Export Indication DMTF 2002 Developers' Conference June 10-13, 2002 Page 67

68 The Provider Interface

69 The Provider Interface Client Client CIM Clients CIM Server Repository Client Client CIM Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 69

70 The Provider Interface The provider interface is defined by the CIMProvider class. The provider interface has a method for each CIM operation in the CIM Operations over HTTP, V1.0 specification. CIMProvider is a base provider interface (more refined provider interfaces are being developed). DMTF 2002 Developers' Conference June 10-13, 2002 Page 70

71 CIMProvider Methods getclass() getinstance() deleteclass() deleteinstance() createclass() createinstance() modifyclass() modifyinstance() enumerateclasses() enumerateclassnames() enumerateinstances() enumerateinstancenames() execquery() Associators() associatornames() references() referencenames() getproperty() setproperty() getqualifier() setqualifier() invokemethod() DMTF 2002 Developers' Conference June 10-13, 2002 Page 71

72 Example of modifyinstance() The provider developer derives from CIMProvider and overrides the modifyinstance() method. class MyProvider : public CIMProvider { }; virtual void MyProvider::modifyInstance( const String& namespace, CIMInstance& modifiedinstance) { // Modify the instance here! } DMTF 2002 Developers' Conference June 10-13, 2002 Page 72

73 Provider Registration and Loading Providers are configured as dynamic libraries with an entry point function for creating the provider instance. Provider / Class association controlled by provider registration (install instance of provider registration classes) Provider is loaded on demand (when instances of that class are requested). DMTF 2002 Developers' Conference June 10-13, 2002 Page 73

74 Provider Interfaces Provider interfaces exist for the following Provider Types: Instance provider Method provider Query provider Event provider Association provider DMTF 2002 Developers' Conference June 10-13, 2002 Page 74

75 Provider Managers Provider Interface Managers map the base provider interface onto one or more other provider interfaces. This scheme may be used to: Refine the base provider interface into several provider interfaces (as mentioned above). Convert from message based operations to direct call for the provider. Map the provider interface onto other language provider interfaces (e.g., Java, Perl, Tcl). DMTF 2002 Developers' Conference June 10-13, 2002 Page 75

76 Provider Proposals Interoperability with SUN Wbem providers proposal We are extending other interoperability ideas Pegasus Pegasus CIMOM CIMOM SUN SUN WBEM WBEM CIMOM CIMOM Microsoft Microsoft CIMOM CIMOM Pegasus Pegasus Providers Providers SUN SUN WBEM WBEM Providers Providers Microsoft Microsoft WMI WMI Providers Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 76

77 The Repository Interface

78 The Repository Interface Client Client CIM Clients CIM Server Repository Client Client CIM Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 78

79 The Repository Interface Defines the interface to manipulating the CIM repository. Alternative implementations of this interface may be provided. Pegasus provides a simple default implementation. DMTF 2002 Developers' Conference June 10-13, 2002 Page 79

80 Default Repository Implementation Each CIM Class object is stored in its own file. Instance objects stored in single file for each class CIM objects are encoded as XML in files. Namespaces are represented using file system directories. Single reader/writer at a time. Example: the class X (subclass of Y) which resides in the root/cimv2 namespace would be stored in this file: <repository_root>/root#cimv20/classes/x.y DMTF 2002 Developers' Conference June 10-13, 2002 Page 80

81 Default Repository Limitations Adequate for classes and qualifiers (which tend to be few). Okay for a few hundred instances. Not intended to scale to thousands of instances (uses a lot of disk space due to internal fragmentation). Good for scenario in which a few instances come from the repository and many instances come from providers. DMTF 2002 Developers' Conference June 10-13, 2002 Page 81

82 Proposed Repository Implementation A new repository implementation is under consideration to improve scalability: Encode objects in binary on disk (rather than XML). This will reduce size by three to one. Combine like objects into a single file rather than separate files (this will reduce internal fragmentation). Provide a fast indexing scheme for keys (disk hashing or B+- Trees). This will improve lookup time. DMTF 2002 Developers' Conference June 10-13, 2002 Page 82

83 Alternative Repository Modules Repository modules may be developed to achieve a highly scalable repository. Possibilities include: Basing repository on a relational database. Basing repository on Unix DB. Making the repository remote. Improving space utilization of existing implementation by storing objects in binary format (rather than as XML). DMTF 2002 Developers' Conference June 10-13, 2002 Page 83

84 4. The Pegasus Project Today And Tomorrow DMTF 2002 Developers' Conference June 10-13, 2002 Page 84

85 Status Today Version 1 complete (Beta Level Code) Includes CIMOM including HTTP Server and CIM-xml Protocol Provider interfaces and dispatch Repository with Instances, Classes, Associations C++ CIM Object Model representation Admin and support functions MOF Compiler Client Interface and test clients Test providers Integrated unit and client server tests (regression) Version 2 Functionally Complete Provider manager Provider Registration Add CIM Indications processing Threading, message queue based model Security Production functions (Startup, stop, provider replacement, configuration, etc.) In Process Today Stability Testing Version 2.x Summer/fall 2002 DMTF 2002 Developers' Conference June 10-13, 2002 Page 85

86 The Components Today Browsing Client Test Test Clients Compiler Cim-Xml Cim-Xml Indication Indication Handler Handler SNMP SNMP Indication Indication Handler Handler Instance Pegasus CIM Repository CIM Object Manager Class Repository C++ C++ C Provider Interface Manager Adapter C++ C++ Providers DMTF 2002 Developers' Conference June 10-13, 2002 Page 86

87 Pegasus Who s Who The Pegasus Contributors IBM Compaq HP BMC The Pegasus Users Today IBM Compaq HP IBM IBM Commitment Commitment IBM IBM has has chosen chosen CIM/Wbem CIM/Wbem as as the the strategic strategic technology technology for for hardware hardware platform platform instrumentation instrumentation and and manageability manageability of of all all server server platforms. platforms. Pegasus Pegasus is is the the CIMOM CIMOM that that IBM IBM has has selected selected to to include include with with eserver eserver platforms platforms in in and and beyond. beyond. During During IBM IBM is is planning planning on on maintaining maintaining and and contributing contributing to to Pegasus Pegasus for for the the Linux, Linux, Windows, Windows, AIX, AIX, OS/400 OS/400 and and System System operating operating environments. environments. DMTF 2002 Developers' Conference June 10-13, 2002 Page 87

88 The Functions Today CIMOM Functions Class and Instance Security Threading Queued execution model Async CIM Operations APIs Modular Services C++ Provider Manager Provider Control WBEM Functions Provider Registration CIM Operations Indications (Process) Clients Test Clients Providers In-Process Test Sample Implementations OS ComputerSystem Platforms Unix (AIX, HP-UX, Tru-UNIX Compaq Himyla Linux Windows Current with CIM 2.6 DMTF 2002 Developers' Conference June 10-13, 2002 Page 88

89 Planned Extensions CIMOM Functions Indications (Lifecycle) Increased Modularity Enhance Service Configuration Additional Provider Managers C Provider Interface Java Provider Interface Out-of-Process Providers WBEM Functions Discovery CIMOM Object Manager Characteristics Clients Object Browser Test Clients Protocol Adapters Add protocol Adapters Providers Test Extend Generic Providers Platforms Easier portability More platforms DMTF 2002 Developers' Conference June 10-13, 2002 Page 89

90 5. More Information DMTF 2002 Developers' Conference June 10-13, 2002 Page 90

91 Open Group The Enterprise Managenemt Forum The Pegasus Web Site and code The ex-snia web site and code DMTF 2002 Developers' Conference June 10-13, 2002 Page 91

92 Other Manageability Projects AIC Application and Control AIC as a Pegasus Provider ARM Applications Response Measurement ARM and DMTF DAP Information as Pegasus Provider Other possible Providers JMX (Java) SNMP DMI WMI DMTF 2002 Developers' Conference June 10-13, 2002 Page 92

93 Implementations Open Source and WBEM Pegasus (The Open Group) Ex-SNIA CIMOM (The Open Group) Caldera (Linux) Sun WBEM Services Working towards Commonality through a new Consortium WBEMSource Consortium DMTF 2002 Developers' Conference June 10-13, 2002 Page 93

94 WBEMSource Consortium Create an an environment of of opensource WBEM implementations Create common interfaces and and APIs Create an an environment of of conformance WBEMsource Hosted by The Open Group Create a library of of providers and and tools Create commonality between implementations and and integrate different implementations. Members Members Include: Include: Sun, Sun, Compaq,HP, Compaq,HP, IBM, IBM, Tivoli, Tivoli, Open Open Group, Group, SNIA, SNIA, Caldera, Caldera, Novell, Novell, Nokia, Nokia, Intel Intel DMTF 2002 Developers' Conference June 10-13, 2002 Page 94

95 6. QUESTIONS? DMTF 2002 Developers' Conference June 10-13, 2002 Page 95