view slides

15
DCML: The Missing Link in DCML: The Missing Link in IT Service Management IT Service Management J. Darrel Thomas Chief Technologist, Hosting Electronic Data Systems Corporation

Upload: billy82

Post on 17-Dec-2014

207 views

Category:

Education


0 download

DESCRIPTION

 

TRANSCRIPT

Page 1: View Slides

DCML: The Missing Link in IT DCML: The Missing Link in IT Service ManagementService Management

J. Darrel ThomasChief Technologist, Hosting

Electronic Data Systems Corporation

Page 2: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

Data Center Markup Language (DCML)

The only open, XML-based standard designed to achieve interoperability by providing a systematic, vendor-neutral way to describe an IT Service environment

Universal language that describes elemental, process, and service-oriented relationships between IT service entities and policies governing the management of such environments

Handles heterogeneous and semantic information required to manage at the service level

Page 3: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

The Problem DCML Helps Solve

IT Services Management requires a multi-dimensional approach

Mapping of interdependencies and inter-relationships at the elemental, process, and services level does not currently exist

Complex, heterogeneous environments require interchange standardization between management systems

DCML helps bridge this disparity using ontological and “like” meta-relationships

Page 4: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

Service Desk

Incident

Problem

Configuration

Change

Release

Service Level

Financial

Capacity

Continuity

Availability

IT Services Management Standardization Has Varying Domain-Based Initiatives to Address Its Dimensions…

Many standards have been or are being developed to address the INDIVIDUAL DOMAIN issues…

Servers(CIM-SMASH)

IPMIWS-*

Storage(CIM-SMIS)

WS-* InterfaceInterfaceElementalElemental

BusinessProcess

(BPEL, ebXML)

Application(.NET, Java, SOAWS, UDDI, etc.)

Industry(MDA, HIPPA, etc.)

IT Foundation(LDAP, SMTP, etc)

PurposefulInfrastructure

(WSDM2.0, WS-*)

OperatingSystems

(CIM-SMASH)

IT Domain-SpecificIT Domain-SpecificElementalElemental

Etc.

Network(CIM)

WSDM2.0, WS-*

Applications(CIM?)

WSDM2.0/WS-*

Service-OrientedService-Oriented

IT P

rocess F

ram

ew

ork

s &

Sta

nd

ard

s

(ITIL

, CO

BIT

, BS

15000, C

MM

I)

ITIntegral

Packaging(OGSA/I, etc.)

Page 5: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

But, There is STILL Confusion withPossibly The Most Important IT Services Dimension – Interrelationships, Configurations, and Dependencies…

Assistance?

Un/Planned Events?

Crises?

Relationships?

Adjustments?

Production-ize?

Guarantees?

$$$$?

Resourcing?

Recovery?

Accessibility?

This area still looms as the enterprise/service provider’s most important inhibitor for standardizing IT Services Management.

Servers Storage

InterfaceInterfaceElementalElemental

BusinessProcess

Application Industry Infrastructure

PurposefulInfrastructure

OperatingSystems

IT Domain-SpecificIT Domain-SpecificElementalElemental

Etc.

ElementalRelationships

OperationalIntelligence

ServiceDynamics

Network Applications

Service-OrientedService-OrientedIT P

rocess F

ram

ew

ork

s

ProcessDynamics

ITIntegral

Packaging

ITITDomain/ElementDomain/Element

RelationalRelational

Elemental Relationship Intelligence

Service-to-Element Relationship Intelligence

Page 6: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

Why Vocabularies, Semantics and Ontologies are Important to DCML

Provide a solution that facilitates automated reasoning about data - DCML documents do not merely describe static information about the simple state of an environment

Flexible enough to be applied at the framework specification level of DCML

The best choice for managing data center interdependency complexity, which DCML is intended to help solve

Page 7: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

The Framework

URI Unicode

XML Namespaces

RDF

RDF Schema

Ontology: OWL

Rules

Logic Framework

Proof

Trust

Sig

natu

re

Enc

rypt

ion

The Semantic WebTim Berners-Lee, DirectorW3C World Wide Web Consortium

From http://www.w3.org/2002/Talks/04-sweb/Overview.html

OntologyLayer

Page 8: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

Example: Server Provisioning Script

A service is being deployed and part of the deployment requires a web-server to be created. A service architect creates a service blueprint that specifies how the service is to be created – what servers it needs to construct the service and what software installed on these servers. This blueprint is codified in DCML. An automation system or tool orchestrates the construction of the service by passing along the blueprint (either in whole or in part) to various provisioning systems.

25 <owl:Class rdf:ID="LogicalServerBlueprint">26 <rdfs:subClassOf rdf:resource="&dcml;Configuration"/>27 <!-- Restrict os to cardinality of 1 -->28 <rdfs:subClassOf><owl:Restriction>29 <owl:onProperty rdf:resource="#os"/>30 <owl:cardinalityrdf:datatype="&xsd;nonNegativeInteger">1</owl:cardinality>31 </owl:Restriction></rdfs:subClassOf>32 </owl:Class>33 <owl:ObjectProperty rdf:ID="os">34 <rdfs:range rdf:resource="#OperatingSystem"/>35 </owl:ObjectProperty>36 <owl:ObjectProperty rdf:ID="package">37 <rdfs:range rdf:resource="#SoftwarePackage"/>38 </owl:ObjectProperty>

Page 9: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

Why OWL and RDF are a Good Fit for DCML

Conceptual Model – OWL captures knowledge of both current and future managed environments, and the policies and procedures governing the management of those environments (ie. two layers, a core schema and extension schemas)

Encoding Scheme – OWL allows DCML to be encoded into a concrete representation before it is exchanged with other management systems, written to a file, or transported by a protocol

Instance Document – RDF/XML provides an extensible and flexible structure to capture large data populations

Page 10: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

DCML Enables IT As A Service

Employees

Page 11: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

Example Use Case: Instrumenting ITIL

DCML could create dynamic instrumentation and interface relationship mapping for the ITIL Configuration Management process, Datacenter/Infrastructure CMDB, and standardization/modeling and specifications for Configuration Items (CIs), both discovered during runtime as well as created during development pre-production integration

Would enable ITIL to be electronically and standards-based within a ITIL-framed operational model

Could define a standards-based data format that allows disparate IT systems to implement ITIL Service Support and ICTIM processes and exchange information with each other.

Could give IT a concrete step for implementing ITIL and automating IT processes.

Page 12: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

Goals of DCML

Create standards-based information exchange data for disparate management systems

Instrument interrelationships and mappings to dynamically store and process configurations (CMDB, configuration entities/items)

Instrument best practices models and IT process frameworks, such as ITIL, in a form that can be used by customers

Provide a solution in pre-production CMDB (optimistic integration) and existing environments (existing configuration discovery) to help solve complex, real-world problems: incident management, CMDB population, disaster recovery/business continuity

Reduce cost, speed implementation and improve learning curve through iteration and reuse

Enable standards-based automation using meta-mapped aggregated relationships as exchange between disparate management systems

Further the vision of utility and grid computing

Page 13: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

Next Steps

DCML Member Section currently testing and validating the usage of semantics and vocabularies

Evaluating different approaches to describe the interchange relationships between the dimensions of IT Services management

Validating usage of DCML within installed base through end user reference implementations

Continuing to work with like-minded standards bodies

Page 14: View Slides

©2003-2005 DCML Member Section, All Rights Reserved

Thank You!

QUESTIONS AND ANSWERS