1© 2003, Cisco Systems, Inc. All rights reserved.
Why CIM? CIM in Grid Standards
Andrea Westerinen, Cisco
March, 2004
222© 2003, Cisco Systems, Inc. All rights reserved.
What’s the Problem with Management Data?
• Not all data is created equalCheck boxes that indicate “management data provided” areNOT enough
• Each technology (and sometimes each productoffering) represents its management data in adifferent way
Creating its own semantics, terminology, data structures andprotocols
• Management is NOT the area for differentiation butfor conformance
Uniqueness costs the customers in design time,normalization, …
333© 2003, Cisco Systems, Inc. All rights reserved.
What’s the Problem When Managing Resources?
• Not about:Protocols
Although they are easier to define
Or new technologies
XML, YML, ZML
Or interfaces/APIs
• All of these convey “how to communicate” butnothing about the data
“What is communicated?”
“How is the data analyzed/used?”
444© 2003, Cisco Systems, Inc. All rights reserved.
What Do End Users and Businesses CareAbout?
$
$$
555© 2003, Cisco Systems, Inc. All rights reserved.
End to End Management
• Sharing information andaccess to data
• Data retention andavailability
• Communication /transmittal of information
• Processing of necessarytasks
666© 2003, Cisco Systems, Inc. All rights reserved.
Differing Perspectives
• End User – Distributed processes, policies anddata
Security concerns
Data to be retained and retrieved as quickly as possible
• Vendors – Lots of individual productsSoftware – Application and services (for ex, database,storage, tape backup, security, …)
Hardware – Computer, networking, …
• Each vendor knows their product, not their placein the bigger picture
• The end user needs to know each product, ANDthat product’s place in supporting the business
777© 2003, Cisco Systems, Inc. All rights reserved.
An Ideal World
• Complete description of the managedenvironment
Scalable from the “big picture”
Going to the component level only when necessary
Standardized semantics
• Emphasis on applying “interoperableknowledge” to the managed environment
• Requires:Common information model to describe and organizethe managed environment
Policies to manage the system (May or may not beautomated)
888© 2003, Cisco Systems, Inc. All rights reserved.
What’s a Solution?
• Work toward documented common concepts andcommon model (-> CIM)
ComputerSystem, StorageVolume, ProtocolEndpoint,Collection, …
This is possible - In most parts of the world, “Where isthe bathroom?” is understood
• Goal to have “one size fits all” - a basicdictionary for management
• Define documented “translations” into othermodels and languages
Support for different environments and languages,such as WSDL
999© 2003, Cisco Systems, Inc. All rights reserved.
But Is Information Modeling Possible?
• “The Semantic Web”, Scientific American, May2001 (Berners-Lee, Hendler and Lassila)
• “Human language thrives when using the sameterm to mean somewhat different things, butautomation does not.”
Clowns, business addresses and PO Boxes
• “Human endeavor is caught in an eternal tensionbetween the effectiveness of small groups actingindependently and the need to mesh with thewider community. A small group … produces asubculture whose concepts are not understoodby others. Coordinating actions across a largegroup, however, is painfully slow and takes anenormous amount of communication.”
101010© 2003, Cisco Systems, Inc. All rights reserved.
How Does CIM Complement GGF OGSA?
• Description of relationships (dependencies,component structures, etc.)
• Management and modeling of resources
• End to end context for management data
• Management of the OGSA architected servicesFunctional vs management interfaces
• Automated mapping from model definition toXML Schema/WSDL/WS-RF/…
111111© 2003, Cisco Systems, Inc. All rights reserved.
Standards Bodies Cooperation (J. Nick, IBM)
Web Services Description
Common Web Services
BusinessTo
Business
EnterpriseApplicationIntegration
Other Resource
ModelsCIM
Model Manageability Capabilities
Descriptions
Manageable Resources
Other Management Services Management Common Web Services
Service Level Managers
Utility Business Services
Management
OASIS (WSDM)
GGF WorkingGroups
OASIS
OASISW3C
DMTF
DMTF
GGF WorkingGroups
GGF OGSAArchitected Services
DMTF Manages the Services
DMTF Manages the Services
121212© 2003, Cisco Systems, Inc. All rights reserved.
Multi-Tiered, Iterative Modeling
Conceptual Model
From Domain Experts
Universal
Information Model
UML
UML
WS-RF
Rendering
??
Rendering
131313© 2003, Cisco Systems, Inc. All rights reserved.
Model Unification
1. Model proposals from GGF, SNIA and
other stds
3. Model proposals unified in DMTF
7. Model published by DMTF;Storage componentsincorporated in SNIA’s SMI-S;model used in GGF’s gridservices architecture, …
2. Submissionof Models
4. Feedback
8. Industry feedback
Web services architecture (W3C),Mgmt Web services (OASIS), …
5. Proposal acceptableto all orgs
6.Buildingblocks4. Feedback
141414© 2003, Cisco Systems, Inc. All rights reserved.
DMTF Alliance Partners Working on This Today
• BladeS – Blade server environment
• CompTIA – Diagnostics and help desk/support
• InTAP, Japan – Interoperability and protocols
• itSMF - ITIL
• NAC – IT-related issues, esp RBAC, identity, use ofdirectories, …
• NIST – General modeling and policy
• Open Group – Open Source, applications, Unix modeling, …
• SNIA – Storage environment
• TMF – Telco environment
151515© 2003, Cisco Systems, Inc. All rights reserved.
Open-Source Implementations
• SNIA’s SMI-S and SMI-Lab (formerly CIM-SAN)
• WBEMSource/The Open Group
Pegasus and Pegasus-J (aka SNIA ObjectManager)
• Java WBEM Services
• OpenWBEM
• SBLIM (Standards Based Linux Instrumentation forManageability) and CMPI (Common ManageabilityProgramming Interface)
• http://www.wbemsource.org/
• http://www-124.ibm.com/sblim/index.html
161616© 2003, Cisco Systems, Inc. All rights reserved.
Mappings from Other Standards
• SMBIOS (System Management BIOS)
• MIBs - IETF
• MIFs - DMI
• ITU concepts – X series
• TMF – eTOM, SID and other models
• ANSI T10 (Storage)
• JSR77 (AppServer)
Explicit in model via MappingStrings qualifier
171717© 2003, Cisco Systems, Inc. All rights reserved.
CIM Coverage
Database
Application Server
Applications and Services
Operating System
Systems, Devices/Storage, …
Network
Use
rs a
nd
Sec
uri
ty
Po
licy
Su
pp
ort
Man
agem
ent
Infr
astr
uct
ure
CIM
181818© 2003, Cisco Systems, Inc. All rights reserved.
CIM Basics
• Object oriented paradigm
• Focus on well-defined concepts, but with aview to extensibility
• Technology neutral - Semantics only
191919© 2003, Cisco Systems, Inc. All rights reserved.
DMTF Working Groups
• Applications/Metrics
• Architecture
• Behavior and State
• Database
• Networks
• Policy
• Security Protection and Management
• Server Management
• Support
• System and Devices
• User and Security
• Utility Computing
• WBEM Interoperability/Events
202020© 2003, Cisco Systems, Inc. All rights reserved.
Example of CIM’s Use – CIM-SAN/SMI-LabDemos
• October 2002, April 2003 and October 2003
• CIM-SAN1
17 vendors integrated 32 products creating 97 points ofinteroperability
Physical inventory information (disk drives, cache, front andback end ports) for disk arrays
• CIM-SAN2
Added logical inventory (LUNs and other storageinformation) and extended the modeling to cover otherdevice types such as tape libraries, NAS systems and FCswitches
• SMI-Lab3
22 participating companies integrating 40 products andcreating more than 300 points of interoperability
Added key functionality like: Volume management andconfiguration reporting
212121© 2003, Cisco Systems, Inc. All rights reserved.
SMI-Lab3 Participants
• AppIQ, Brocade, Cisco Systems, CNT, ComputerAssociates, CreekPath Systems, EMC, FujitsuSoftek, Hitachi Data Systems, HP, IBMCorporation, Invio Software, LEGATO Software,LSI Logic Corporation, McDATA, NetworkAppliance, QLogic Corporation, SeagateTechnology, Storability Software, StorageTek,Sun Microsystems, VERITAS Software
222222© 2003, Cisco Systems, Inc. All rights reserved.
Vendors Shipping/Soon to Ship CIM Today
• Brocade – CIM Fabric management
• Cisco – CIM-based database design for inventory, Storagemodeling, CiscoWorks interface
• Dell - CIM in OpenManage Server Administrator for Dell PowerEdgeservers and Dell PowerVault NAS servers, and OpenManage ClientInstrumentation for Dell Latitude, Dell OptiPlex and Dell Precisionclient systems
• EMC – Instrumentation/providers for Symmetrix storage arrays,CLARiiON storage arrays and Celerra NAS system (indevelopment), and clients for EMC Control Center (enterprise-widestorage management) and EMC VisualSAN (mid-range storagemanagement) in 2004
• HP - www.hp.com/go/wbem highlights the HP (serverside) CIM/WBEM solutions including HP WBEM Services for HP-UXand Linux, HP-UX 11iv2 for HP Integrity Servers (includes WBEMProviders), HP WBEM Providers for Linux on Integrity Servers, HPServicecontrol Manager and HP System Insight Manager / Also, seewww.hp.com/go/devsmi-s for details on CIM/SMI-S as the standardinterface for HP’s storage products
232323© 2003, Cisco Systems, Inc. All rights reserved.
Vendors Shipping/Soon to Ship CIM Today
• IBM - iSeries (OS/400) support for CIM in 2004, pSeries (AIX)Pegasus delivered as part of the Linux toolbox CD, CIM deliveredwith and used as foundation for IBM Director, CIMinstrumentation/providers are available to all Windowsmanagement applications, IBM contributes to OpenPegasusproject, and storage products support CIM (specifically, ESS(Shark), SAN Volume Controller, TotalStorage SAN File System,Tivoli Storage Resource Manager, and TotalStorage's new MultipleDevice Manager products)
• Intel - http://www.intel.com/design/servers/ISM/ highlights Intel’sServer Management CIM/WBEM solutions (version 6.0 and greater),and CIM instrumentation shipped with Intel LAN adapters as part of“Intel PROSet for Wired Connections”
• Microsoft – Windows Management Instrumentation
• Oracle – Enterprise Manager 10g
• SMARTS – InCharge Suite for problem analysis (ICIM for IT andbusiness modeling)
242424© 2003, Cisco Systems, Inc. All rights reserved.
Vendors Shipping/Soon to Ship CIM Today
• Sun - Enterprise Storage Manager (SAN Manager), Solaris WBEMServices (full instrumentation of Solaris), SMC (a systemmanagement utility), and all disk arrays will include CIM/SMI-Smanagement providers and clients (near future)
• VEIO – VEIO 1000, entire instrumented and managed applicationenvironment is CIM-based
• Veritas - CIM/SMI-S interface to its Command Central product stackin the first half of 2004, and CIM/SMI-S interface to VolumeManager in 2004
• WBEM Solutions - SDK Pro, J WBEM Server, and C WBEM Server(near future, for embedded environments)
252525© 2003, Cisco Systems, Inc. All rights reserved.
Profiles
• Collection of CIM elements and behavior rules representing aspecific area of management
Detailed information/recipe for management
• Relevant to customers to tie instrumentation to clients
• Components:
Description
Required/supporting standards and other profiles
Methods
Discovery
Instance Diagram
Client Considerations
Instrumentation Requirements
Required CIM Elements
Required and Recommended Properties for CIM Elements
262626© 2003, Cisco Systems, Inc. All rights reserved.
CIM V3
• Maintain CIM v2.x semantics
• Additional data types (unions, structs, enum,embedded object)
• UML 1.3+ with canonical rendering in XMI
• Simplified model with Top, single consistent keystructure, removal of deprecated classes