DMTF Standards Overview WBEM and CIM September 18, 2002

1
DMTF Standards Overview WBEM and CIMSeptember
18, 2002

• Andrea Westerinen
• Julie Schott
• Cisco Systems

2
Topics for Discussion

• WBEM Overview
• CIM, the Common Information Model
• xmlCIM, CIMs XML encoding
• CIM Operations over HTTP
• References
• Questions

3
WBEM

• Web-Based Enterprise Management
• A set of management and Internet standard
  technologies developed to unify the management of
  enterprise computing environments

4
WBEM Architecture(Client-Server)
WBEM Client
WBEM / CIM Ops over HTTP
WBEM / CIM Ops over HTTP
WBEM / CIM Ops over HTTP
5
WBEM Operational Overview

• CIM Client
• Interacts with a CIM Server by issuing CIM
  Operation Message Requests and receiving/processin
  g CIM Operation Message Responses
• CIM Server
• Server that receives and processes CIM Operation
  Message Requests and issues CIM Operation Message
  Responses
• CIM Object Manager (CIMOM)
• Central component of the CIM Server responsible
  for the communication between other components
• Provider
• Instruments one or more aspects of the CIM
  Schema, reflecting the real world

Client
CIM-XML
CIM Server
CIM-XML Protocol Adapter
CIM-XML Indication Handler
CIM Object Manager (CIMOM)
Provider(s)
Provider(s)
Managed Element
6
WBEM Technologies

• CIM Schema
• XML DTD to encode the Schema
• CIM Operations over HTTP
• HTTP/1.0 and /1.1 encapsulation
• Synchronous message request and response Simple
  and multiple methods supported
• Publish/subscribe mechanism for Indications
  (event notifications)
• Extrinsic (methods on a class) and intrinsic
  (model operations) methods are defined Get,
  Create, Delete, Modify, Enumerate,

7
WBEM Environment
Data Description
CIM
HTTP Access
xmlCIMTransport Encoding
8
CIM

• Common Information Model
• Core Specification
• Meta-model and high level concepts
• Language definition (MOF, Managed Object Format)
• Core and Common Models
• Object oriented design
• 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 encouraged

9
Definition of an Information Model
An abstraction and representation of the entities
in a managed environment - their properties,
operations, and relationships. It is independent
of any specific repository, application,
protocol, or platform.
10
Customers Mgmt Information Stack
Policy
Management Infrastructure
Users and Security
Support
CIM
11
CIMs OO Approach

• Model the world in terms of objects
• An object is an abstraction, consisting of a set
  of related data and behaviors
• An object is treated by the system as a named
  entity that has a set of characteristics
  (properties and methods), behavior, and a unique
  identity
• Also describe relationships
• Inheritance hierarchies refine and specialize the
  attributes and behavior of a group of objects
• Association hierarchies relate objects to each
  other
• Have standard, inheritable methods

12
Modeling Example
Switch (Physical Aspects)
LogicalElement
PhysicalElement
Cisco-SpecificClass Extensions
PhysicalPackage
System
ServiceAccessPoint
Card
ComputerSystem
ProtocolEndpoint
Extensions for MIB Properties, Internal Port
Properties, Etc.
Switch(Logical Aspects)
Port (Switch Address)
UnitaryComputerSystem
13
Models in CIM

• Core
• Physical
• System
• Device
• Network
• Policy
• User and Security
• Applications and Metrics
• Database
• Event
• Interoperability
• Support

14
WBEM Environment
Data Description
CIM
HTTP Access
xmlCIMTransport Encoding
15
xmlCIM

• Standard way to represent CIM information using
  XML
• CIM DTD (Document Type Definition)
• Meta-Schema mapping
• Simple Straight forward
• Requires only one DTD
• CIM Messages
• Protocol independent!

16
xmlCIM Example
ltCLASS NAME"CIM_LogicalPort" SUPERCLASS"CIM_Logi
calDevice"gt ltQUALIFIER TRANSLATABLE"true"
NAME"Description" TYPE"string"gt ltVALUEgtThe
abstraction of a port or connection point of a
Device. This object should be instantiated
when the Port has independent management
characteristics from the Device that includes it.
Examples are a Fibre Channel Port and a
USB Port. This class would not be instantiated
for an Ethernet Port which is not managed
independently of the EthernetAdapter.lt/VALUEgt
lt/QUALIFIERgt ltPROPERTY NAME"Speed"
TYPE"uint64"gt ltQUALIFIER TRANSLATABLE"true"
NAME"Description" TYPE"string"gt
ltVALUEgtThe speed of the Port in Bits per
Second.lt/VALUEgt lt/QUALIFIERgt ltQUALIFIER
TRANSLATABLE"true" NAME"Units" TYPE"string"gt
ltVALUEgtBits per Secondlt/VALUEgt
lt/QUALIFIERgt lt/PROPERTYgt ltPROPERTY
NAME"MaxSpeed" TYPE"uint64"gt ltQUALIFIER
TRANSLATABLE"true" NAME"Description"
TYPE"string"gt ltVALUEgtThe max speed of the
Port in Bits per Second.lt/VALUEgt
lt/QUALIFIERgt ltQUALIFIER TRANSLATABLE"true"
NAME"Units" TYPE"string"gt ltVALUEgtBits per
Secondlt/VALUEgt lt/QUALIFIERgt
lt/PROPERTYgt lt/CLASSgt
17
WBEM Environment
Data Description
CIM
HTTP Access
xmlCIMTransport Encoding
18
CIM Operations over HTTP

• Protocol Independent!
• Support for single or multiple operations
• Types of Operations
• Data
• Meta Data
• Queries
• Methods

HTTP header
Xml/Cim payload
19
Operations Profiles
20
HTTP Operations Example
M-POST /cimom HTTP/1.0 Content-Type
text/xmlcharsetUTF-8 Accept text/xml,
application/xml Man http//www.dmtf.org/cim/mappi
ng/http/v1.0ns48 48-CIMProtocolVersion
1.0 48-CIMOperation MethodCall 48-CIMMethod
GetClass 48-CIMObject root2Fcimv2 User-Agent
Java1.2.1 Host edoc5-pc Content-length
445 lt?xml version"1.0" encoding"UTF-8"?gt ltCIM
DTDVERSION"2.0" CIMVERSION"2.0"gt ltMESSAGE
ID"200012411044581" PROTOCOLVERSION"1.0"gt
ltSIMPLEREQgt ltIMETHODCALL
NAME"GetClass"gt ltLOCALNAMESPACEPATHgt
ltNAMESPACE NAME"root" /gt
ltNAMESPACE NAME"cimv2" /gt
lt/LOCALNAMESPACEPATHgt ltIPARAMVALUE
NAME"ClassName"gt ltCLASSNAME
NAME"cim_logicalport" /gt lt/IPARAMVALUEgt
lt/IMETHODCALLgt lt/SIMPLEREQgt
lt/MESSAGEgt lt/CIMgt
21
DMTF and WBEM References

• DMTF DMI, CIM, SMBIOS, ASF, WBEM and DEN
  Standards and Standard Publications
  http//www.dmtf.org/standards/index.php
• DMTF Standard Publications http//www.dmtf.org/s
  tandards/published_documents.php
• DMTF Developer Conference presentations (June
  2002) http//www.dmtf.org/devcon/devcon02/
• DMTF Marketplace - http//www.dmtf.org/about/marke
  t.php
• Open Source CIM Implementations
  http//www.wbemsource.org

22
?
?
Questions And Discussion
?
23
Backup Slides

1. DMTF Technical Working Groups and Development
   Process
2. How CIM Is Expressed (MOF, UML and XML)

24
DMTF Technical Working Groups
Technical Committee
Interoperability/ Events Chair Sun
Chair Andrea Westerinen, Cisco
System/Devices Chair Cisco
Board Members Intel, Microsoft, Cisco, Sun,
Tivoli/IBM, Compaq, Dell, HP, 3Com, BMC,
NEC, Oracle, Novell, Symantec Alliance
Partners, WG Chairs
Database Chair Oracle
Applications/Metrics (Previously DAP) Chair
TOG
User/Security Chair IBM
DEN/ LDAP Mapping Chair Cisco
Networks Chair Cisco
Policy/SLA Chair IBM
Support/Help Desk Chair CSI
Several new WGs under discussion
Desktop Mgmt Interface Chair HP
PreOS Chair Intel
25
DMTF Development Process

• Five phases in the release of DMTF Specifications
  and Schema
• Development by Working Groups
• Member Comment
• Company Review
• Preliminary Standard
• Final Standard
• All additions and updates to standards submitted
  as Change Requests to the appropriate WG and then
  forwarded to the Technical Committee

26
How Is CIM Expressed?

• MOF - Managed Object Format (ASCII or Unicode)
• VISIO for UML (Unified Modeling Language)
• 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)
• Whitepapers

27
MOF Example
Qualifiers
Class Name and Inheritance
Properties
Methods
28
UML/Visio Example
ASSOCIATIONS
INHERITANCE
AGGREGATION (A kind of association)
METHODS