Overview of the Pegasus CIM/WBEM Implementation

Transcription

1 Overview of the Pegasus CIM/WBEM Implementation July 24 th 2002 Karl Schopmeyer Chair Open Group Entermprise Mgt. Forum Version 1.1, 18 July /25/2002 1

2 Agenda CIM/WBEM Overview Overview -What (and why)is Pegasus? The Pegasus Environment The Pegasus Software Architecture Pegasus Status Today The Pegasus Project 7/25/2002 2

3 1.CIM and WBEM 7/25/2002 3

4 The Management Standards Groups DMTF DMI SNMP CIM / WBEM The Open Group Unix Management Standards CMIP Application Management Standards CIM / WBEM IETF SNMP TMF CMIP OSS/NG DMI WBEM 7/25/2002 4

5 7/25/ Management Environment Today Service Layer Service Layer & Infrastructure Infrastructure Managed Managed Resource Resource Definition Definition Physical Physical managed managed objects objects Management Management application application GDMO GDMO Fault Fault Config Config Perf Perf Telecom Telecom devices devices Private Private Application Application systems systems Fault Fault Config Config Perf Perf Desktop Desktop systems systems MIF MIF Fault Fault Config Config Perf Perf Network Network devices devices MIB MIB Fault Fault Config Config Perf Perf CMIP CMIP Private Private DMI DMI SNMP SNMP

6 A Management Problem Example: Managing a Fibre Channel SAN Computer system and its devices Storage enclosures Hubs and switches Manageability difficult, not unique to Fibre Channel Different data standards (SNMP, DMI, SES, ) Different terminology Proprietary MIBs Missing data (topologies and dependencies) 7/25/2002 6

7 WBEM Architectures WBEM Data Description DMI </xml/cim> Transport Encoding Discovery HTTP Access 7/25/2002 7

8 Why CIM? Enterprise-wide management Wide breadth of objects + name scoping Repository independent Unifies and extends existing standards (SNMP, X.500, ) OO design Abstraction, inheritance, ability to classify Reduces complexity, provides predictability Well-defined locations and usage semantics for classes and associations Extensibility via subclassing Associations depict relationships Dependencies, topologies, aggregations, scoping,... Standard, inheritable methods 7/25/2002 8

9 What Is CIM? Object-oriented data model Core Specification Meta -model, high level concepts and language definitions Core and Common Models Core Model contains info applicable to all management domains Common Models address specific domains - Systems, Devices, Applications, Networks, Users,... Subclass from the Core Model Models overlap and cross-reference Vendor extensions allowed 7/25/2002 9

10 What Is WBEM? Web-Based Enterprise Management Model to present and organize data Use of XML and HTTP Data Description CIM </xmlcim> Transport Encoding HTTP Access 7/25/

11 DMTF WBEM Components CIM Specification V2 Meta Model CIM Schema v2.7 (900+ classes) Extension Schema System Apps Interoperability Specifications CIM Operations over HTTP CIM XML Network Core Users Device 7/25/

12 The Major Schemas Today Core System Devices Networks Applications (today lifecycle) Metrics (orginally for ARM support) User Policy (was originated as service) Databases Dormant Unix System Extensions Support 7/25/

13 WBEM Architecture (Client-Server) Computer CIMOM WBEM / CIM Ops over HTTP WBEM Client CIM Providers WBEM / CIM Ops over HTTP WBEM / CIM Ops over HTTP Server Network Router CIMOM CIMOM CIM Providers CIM Providers 7/25/

14 What does CIM/WBEM Provide? Abstractions of Managed objects A common semantic for objects Rich set of defined objects Relationships between objects Interoperability between management components. 7/25/

15 WBEM Architecture Components Information Model CIM Schema (Core, System, ) Communication Model CIM Operations over HTTP Transport Encoding Cim-xml CIM/XML mapping Event Model CIM indications (new in CIM 2.5) CIM Object Manager (CIMOM) Operation Routing Result Aggregation Repository Class and Instance Persistence Resource Providers Instrumentation subagents CIM Client Provider CIM Server CMI P CMIP Objects Management Applications cim-xml Transport CIM Object Manager Resource Providers SNMP SNMP MIBs RPC DMI MIFs CIM Listener Schema Inter net CIM Objects 7/25/

16 Interoperability Characteristics XML encoding Definition for each operation HTTP Transport HTTP 1.0 and 1.1 Common Operations Semantics Data Meta data Queries? Methods CIM Client CIM Server Managed Resources Managed Resources 7/25/2002 Managed Resources Managed Resources 16 Managed Resources Managed Resources

17 How Is CIM Schema Defined? MOF - Managed Object Format (ASCII or Unicode) VISIO for UML (Unified Modeling Language) Whitepapers XML - extensible Markup Language XML grammar can be used to describe CIM metaschema, Detailed in DTD (Document Type Defn) DTD defines tags such as CLASS, INSTANCE and QUALIFIER Associations are described via an ASSOCIATION.CLASS tag (Distinguished because they include references as properties) 7/25/

18 Managed Object Format (MOF) [Abstract, Description ( "An abstraction or emulation of a hardware entity, that may " "or may not be Realized in physical hardware.... ") ] class CIM_LogicalDevice : CIM_LogicalElement {... Class Name and Inheritance Qualifiers (Meta data) [Key, MaxLen (64), Description ( "An address or other identifying information to uniquely " "name the LogicalDevice.") ] string DeviceID; [Description ( "Boolean indicating that the Device can be power " "managed....") ] boolean PowerManagementSupported; [Description ( "Requests that the LogicalDevice be enabled (\"Enabled\" " "input parameter = TRUE) or disabled (= FALSE)....)" ] uint32 EnableDevice([IN] boolean Enabled);... }; Methods Properties 7/25/

19 UML/Visio Example ASSOCIATIONS Dependency * * ManagedElement INHERITANCE Product * ProductParentChild * 0..1 ProductPhysicalElements * ManagedSystemElement * Component Collection * MemberOfCollection * GGREGATION A kind of association) METHODS * PhysicalElement LogicalElement 7/25/ * Logical Identity *

20 XML Example <?XML Version= 1.0?> <!DOCTYPE CIM SYSTEM > <CIM VERSION= 2.0 > <CLASS NAME= ManagedSystemElement > <QUALIFIER NAME= abstract > </QUALIFIER> <PROPERTY NAME= Caption TYPE= string > <QUALIFIER NAME= MaxLen TYPE= sint32 > <VALUE>64</VALUE> </QUALIFIER> </PROPERTY> <PROPERTY NAME= Description TYPE= string > </PROPERTY> <PROPERTY NAME= InstallDate TYPE= datetime > <QUALIFIER NAME= MappingStrings TYPE= string > <VALUE>MIF.DMTF ComponentID </VALUE> </QUALIFIER> </PROPERTY> <PROPERTY NAME= Status TYPE= string > <QUALIFIER NAME= Values TYPE= string ARRAY= TRUE > <VALUE>OK</VALUE> <VALUE>Error</VALUE> <VALUE>Degraded</VALUE> <VALUE>Unknown</VALUE> </QUALIFIER> </PROPERTY> </CLASS> </CIM > 7/25/

21 CIM Operations Intrinsic Operations Create, Modify, Delete Qualifiers Classes Instances Properties Invoke Query Extrinsic Operations Execute Methods CIM Operation Requests CIM CIM Clients CIM CIM Server CIM Operation Responses <instance> GetInstance ( [IN] <instancename> InstanceName, [IN,OPTIONAL] boolean LocalOnly = true, Providers [IN,OPTIONAL] boolean IncludeQualifiers = false, [IN,OPTIONAL] boolean IncludeClassOrigin = false, [IN,OPTIONAL,NULL] 7/25/2002 string PropertyList [] = NULL 21

22 CIM Indications ( Events ) Indication Types Process Process Indications Indications External External Events Events Lifecycle Lifecycle indications indications Changes Changes to to CIM CIM Objects Objects Indication Indication Subscription Subscription Object Object CIM Client 1 1 Subscription CIM Listener 4 4 Indication Handler CIM Server Indication Handler SNMP Export Indications CIM CIM Indication Indication Handler Handler Object Object CIM CIM Filter Filter Object Object 2 2 Filter Indication Provider Indication Provider 3 Produce Indications Based on Filter 7/25/

23 Query Language - WQL SQL based Query Language Used in: CIM Indication Filters CIM Queries (CIM Operation) 4 levels of Language 1 Simple queries from single tables 2 Adds DELETE INSERT UPDATE 3 Add complex expressions and specific data constructs 4 Add Joins, etc. Subset Subset of of SQL SQL supports supports queries queries in in the the form form SELECT SELECT <row <row set> set> FROM FROM <table <table list> list> WHERE 7/25/2002 WHERE <selection <selection expression> expression> 23

24 Industry Work Microsoft s WMI (Windows Mgmt Instrumentation) Sun s WBEM Services Cisco s CiscoWorks2000 and LDAP mapping Coordinated development with IETF Policy Framework IPsec Policy The Open Group Unix and software modeling Pegasus (Manageability Services Broker) open source 7/25/

25 Industry Work SNIA (Storage Networking Industry Association) Fibre Channel and Tape / Storage Library modeling and media management Disk Resource Management - CIM prototype CIM Object Manager open source (Now Open Group) WBEMSource (open source) initiative Applications and instrumentation for the various object managers 7/25/

26 2. Pegasus Overview 7/25/

27 What is Pegasus? Open-source implementation of the DMTF WBEM specifications Work project of the Open Group Enterprise Management Forum Pegasus is primarily volunteer labor but through company commitments, not just individuals Platform for building application management Pegasus is a function-rich, production-quality opensource implementation designed to be used in high volume server implementations. 7/25/

28 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 7/25/2002 IBM Tivoli Systems 28

29 Key Pegasus Objectives Open Source Standards Based Portable Pegasus Continuity Efficient And Lightweight Production Quality Modular And Extensible 7/25/

30 Pegasus Working Group Philosophy Manageability not management The Pegasus 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 7/25/

31 Open Source Code and documentation freely available Open Group and Source Forge MIT source license Minimal Demands on licensee No GPL demands License used for X-Windows Open to contributions But process controlled to keep strategy No commitment to Open Group to Use code Contribute code Royalty Free But in a controlled environment 7/25/

32 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) OS 400* Z/OS* MultiPlatform Build Only Make and compiler required to build Multiple Compilers on most platforms GNU compilers preferred 7/25/

33 Efficient and Lightweight Core written in C++ Designed for execution efficiency Custom xml parser No STL Minimal Templates, etc. Designed to be production-quality solution Message/Queue based multithreaded Architecture 7/25/

34 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 7/25/

35 Modular, Extensible, Flexible Minimize core object broker. Maximize extensibility through plug-in components Component types Providers Standard Provider interfaces Clients Connection local and cim-xml Repositories (additional repository handlers) Manageability service extensions Protocol Adapters Modules (extend and modify core functions) Modularity is key to doing parallel development and to extensibility 7/25/

36 Project for Continued Development WBEM will continue to develop functionality and standards Open Group will develop application management partly around Pegasus Pegasus is a project, not just a technology Pegasus Development will continue beyond current versions Integrate contributions Add basic new functionality Grow with DMTF/Open Group standards Light Weight Versions are part of our vision 7/25/

37 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 7/25/

38 3. The Pegasus Environment 7/25/

39 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 7/25/2002 Application Application 39

40 Pegasus Architecture Interoperable MOF MOF Compiler Compiler Interoperable* Consumers Consumers Clients CIM/HTTP CIM/HTTP CIM Server Standard Interfaces Services Consumers Consumers Providers 7/25/

41 CIMOM Capabilities Respond to Operations defined in CIM Operations spec. Create, Modify, Delete operations on Class, Instance, Property, Qualifier Manage Providers Install, register, load Interface for Operations and Indications 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) 7/25/

42 4. The Pegasus Software Architecture 7/25/

43 Major CIM/WBEM Components Client Client CIM Clients Cim-xml Protocol (standard) CIM Server / CIM Object Manager Repository Client Client CIM Providers Provider Interface (Language APIs) 7/25/

44 CIM Object Manager Capabilities Protocols Encoding Encoding Messages Messages Security plugins Authentication Authentication Access Access Control Control Traffic Traffic Providers Management Management Interfaces Interfaces Core Core Server Server Capabilities Capabilities Network TCP Communications System Interfaces (Files, etc.) Containers Thread/Process Management Message/Queuing Option Configuration Logging Signal Handling Service Configuration Authentication Access Control Module Control Operating System CIM CIM Objects Implementation Objects Objects Accessors Accessors WBEM Processing Operations Operations Indications Indications Repositories Classes Classes Instances Instances Indication Handlers Management Management 7/25/

45 Pegasus Server Today Components CIM-XML Indication handler SNMP Indication handler Server Core TCP Communications System Interfaces (Files, etc.) Containers Thread/Process Management Message/Queuing Option Configuration Logging Signal Handling Service Configuration Authentication Access Control Module Control C++ CIM Objects CIM processing Operations, Indications Security (basic, digest) CIM-XML protocol Repository Internal Providers Services Processing Provider Mgr C++ Provider Mgr C Providers Providers Providers 7/25/

46 Building A Modular Manageability Environmnent CIM CIM Client Connector Connector CIM CIM Client XML-CIM Module Module Module Module Module Module Module Module Connector Connector Core Object Broker Services 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... 7/25/ Resources

47 Local Destination CIM-XML Indication handler SNMP ndication 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 Authorization Operations Request Processor PegasusMsgDispatcher Indication Consumer Manager Response generator Operations Response Processor Provider Manager Indication Import CIM Export Request Decoder CIM Export Request Processor Indication Consumer Manager Export Indication Subscription Service and Indication Processor CIM Control Services Start/Stop Function Provider registration Function User/Auth. Function jj Jj Namespace Services Subsystem Provider Mgr Subsystem Formal Provider Interface 7/25/2002 provider provider 47 egasus Module Organization xxx Http xxx

48 5. The Pegasus Project Today And Tomorrow 7/25/

49 Pegasus Project In Context Core System Development Incremental Function growth Compaq, IBM, HP Join V2 Release July 2002 V1 Core Development V2 Multi Thread Server Development V 2.1 SDK, Clean Up V 2.2 Multiple Functions /25/

50 The Pegasus 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 7/25/2002 Current with CIM

51 Planned Extensions CIMOM Functions Lifecycle Indications Increased Modularity Enhance Service Configuration Additional Provider Managers C Provider Interface Java Provider Interface Out-of-Process Providers External Providers WBEM Functions Discovery CIMOM Object Manager Mgt. (Interop Schema) Chunking Specifications C Provider Interface Standard (Sept 02) C++ Provider Interface standard (Oct 02) Security (pluggable and extra security) WMI Mapping Clients Object Browser Test Clients Real SDK Protocol Adapters Add protocol Adapters Providers Test Providers Extend Generic Providers Create real SDK Platforms Easier portability More platforms Testing Extend Unit and System tests 7/25/

52 A Pegasus Lite Project Two Solutions Lighten existing Pegasus (6 mm ext) 1 2 MB Lightweight core/model (15 mm est) KB Today requirements vary widely Footprint System resources Functionality Either or both doable but requires commitment Membership in Pegasus community Better definition of requirements Possibly specific extension projects This will be incremental Both solutions will probably exist with later merge. 7/25/

53 Portability of Pegasus Any GNU based environment is easy Minimal tools required C++ compiler GNU Make Project Provides one make portability tool Compiler issues Minor compiler differences Exceptions, templates Environment issues Threads support Most ports one week or less 7/25/

54 Planned Standards C++ Provider API Pegasus Internal Review of all APIs in process Release SDK with Pegasus 2.1 Sept 2002 Review as Standard Q C Provider API Draft available today for review Formal review cycle (~Spetember 2002) C++ Client API In parallel with C++ Provider API Need not clear today (Java, etc. for Clients) Except for provider/clients. 7/25/

55 Pegasus State Today 120,000 Lines of executable code Ported to at least 5 platforms man years effort to date Components already used in multiple applications Major usage commitment from HP and IBM First integrated use this year 7/25/

56 The Components Today Test Code 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 7/25/

57 Pegasus Who s Who The Major Pegasus Contributors IBM Compaq HP BMC 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 to Pegasus for the Linux, Windows, AIX, OS/400 and System 390 operating environments. The Pegasus Users Today IBM Compaq HP BMC 7/25/2002 contributing to Pegasus for the Linux, Windows, AIX, 57

58 Managing The Pegasus Project Open Group Sponsors the Project, Web sites, CVS, etc. Creates standards for APIs Environment for user understanding Steering Committee Management Sets strategy, priorities, release commitments Tools Web Site Contributors Teleconferences Contribute via change requests, code, doc. Group Mail Change Requests Users CVS Take documentation, source, binary Project Manager DMTF / DMTF Work Groups Stadandards, Interoperabiliity 7/25/

59 Managing The Pegasus Project DMTF DMTF Work Groups Major Contributors (HP, IBM, ) Open Group Pegasus Steering Committee Bugzilla CVS Repository Change Requests Other 7/25/2002 Contributors And Users 59

60 Working With the Pegasus Project Using the Code Free for use Contributing to the Project Outside contributors In Company Specific financed projects Contrbute via patches or authorized developers Join the Steering Committee Influences priorities, commitments, releases. We want and NEED participation from users and Potential users 7/25/

61 Open Group The Enterprise Managenemt Forum The Pegasus Web Site and code The ex-snia web site and code 7/25/

62 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 7/25/

63 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 7/25/

64 6. QUESTIONS? 7/25/