the open group and manageability: an overview presentation december 1999 karl schopmeyer chair tog...
Post on 19-Jan-2016
216 Views
Preview:
TRANSCRIPT
The Open Group and Manageability:An Overview
PresentationPresentationDecember 1999December 1999
Karl SchopmeyerChair TOG Management
Program Groupk.schopmeyer@opengroup.org
What is Happening Today?
Information is one of the Keys to Management— A common Information Model
The customer wants management in his terms— Applications Management
— Service Management
— Business Level Management
The Customer wants Enterprise Management, not just Point Management -- Service Management, not just Technology Management
Management is Big Business The Suppliers are beginning to work together
Enterprise Management (EM) and The Open Group
Open Enterprise Systems Management is a strategic objective for TOG
Technical and program group devoted to Enterprise Management
A meeting forum for suppliers and users A partner with other Standards forums
— Ex. DMTF
Operational ManagementOperational Management
Configuration ManagementConfiguration Management
ProblemProblem ManagementManagement
ChangeChange ManagementManagement
ServiceManagement
ESM Objectives
Encourage,support and create EFFECTIVE standards in Enterprise Systems Management
Help advance the art of Enterprise Systems Management
Communicate between users and suppliers Help the suppliers understand user requirements Help users understand management and open
management solutions
Help users understand the art, practice, and standards of Distributed Systems Management
Technology
EducationBusiness
ESM Organization
The Program Group (Open attendance)— Users and suppliers working together to:
advance open enterprise management
Technical Working Groups— Preparation of one technology
— Specifications, Reference Code, testing, etc.
Business Working Groups— Business support for a technology area to encourage market
adoption Branding, Certification, Marketing, documentation
Enterprise Management Program - Strategy
Build on current program activities, supporting technology deployment— Software license use management (XSLM)— Application response management (ARM)— Universal management installation agent (UMIA)— Application Information and Control (AIC) (Was AMI)— Work With WEB Based Enterprise Management (WBEM)
New programs with an overall coherence— Manageability (Major New Initiative)
— Service Management
— Business approach to programs— Concept to market adoption
Current Work
License Management (XSLM Work Group)
Universal Management Installation (UMIA Work Group)
Service Management (Interest Group)
Application Response Monitoring (ARM Business Group)
CIM Schema extensions for UNIX (Work Group)
AIC (Application Instrumentation and Control) Fast Track
Manageability (Interest Group)
Open Manageability
The objective of the Manageability Initiative is to provide:
— A set of standard interfaces and standard service standard interfaces and standard service definitionsdefinitions for manageability components (interfaces between management agents and the managed entities) such as events, inventory, etc.
— A manageability architecturemanageability architecture into which these APIs and services can fit and which is based on the use of CIM as the common data
Manageability Background
There are NO effective ways to instrument for most managed entities today— No common SNMP agent instrumentation tools— No API to generate events
No way for applications to cooperate in management No real interfaces to get information to and from
management systems. Many, multiple and often competing agents
Management today tries to work through whatever information
it can get through external exploration
Manageability is:
Manageability is the ability to be managed
Manageability defines how managed entities communicate with management functions
Manabeabilitiy is a major interface between different constituencies— Manager – Management Systems
— Managee (Managed entity) – Entity to be managed (OS, applications, middleware, components, etc.
ManagerManager ManageeManagee
Manageability
Management vs. Manageability
Management: Manageability:
Management
Manageability
Product
Do management for their product (IT resource)
Management Product
Management
Manageability
Product
Deliver management software for other vendors’ products
Definitions or instrumentation that make a particular IT resource manageable.
Capabilities that takes advantage of these definitions to actually perform the activities associated with managing IT resources.
Separate Manageability & Management
Some Rules of Management
Capturing correct information and knowing what to do with it key to good management— Higher level management will require higher level information
— Consistent information semantics must be established and preserved
Management is low priority in software development— Management is not important to the app developer
— If it is difficult, don’t do it
Management means touching everything in the environment, not just some things
Today we manage in a hostile environment— We take information, it is not given
Manageability brings together:
Management system suppliers— Need information to manage
Software Providers (Applications and Middleware)— Instrument software for management
OS suppliers— OS instrumentation for management— Market advantage through effective application instrumentation
Customers— Need the information – Information not available today— Want simple and effective tools that integrate efficiently
But – Why hasn’t thisBut – Why hasn’t this been done before?been done before?
We must remember that
Different priorities and objectives— Manageability (Instrumentation)
Simplicity for developers Stability and long life Multiple interface paradigms
— Management Suppliers Flexibility – Functionality will grow Rich information capture
— Customers Interoperability
The Manageability concept lacks an owner— Who feels it is important enough to solve the problem?
— Everybody wants something, nobody wants to do it
Some Key Characteristics
Key characteristics
— Separate elements with loosely coupled interfaces
— Provide interface with major Infrastructure (WEBM)
— Extensible interface
— Rich information model
— Support required for multiple management system architectures (SNMP, WBEM, proprietary, etc.)
Manageability needs
Manageability needs today:—The managed components be instrumented
—There should be a common API(s) so that these managed components can communicate with the managing systems independently of management solution
—Service definitions so the managed components and management system have common understanding of service management offers
—Common mechanism to define the information (CIM)
WBEM Managed System
Schema</
xmlCIM>
DataData&&
SchemaSchemaCIM Object ManagerCIM Object Manager
HTTP(S) Server
Applications Drivers OS
Supplier of management
data
DMI(CI)
Operating SystemSpecif
ic
Provider Service
Transport EncodingTransport Encoding AccessAccess
Data Data DescriptionDescription
Manageability Framework
DataData&&
SchemaSchemaUMIA
ApplicationsApplicationsApplicationsApplicationsApplications
Schema
</xmlCIM>
Provider Service
Interoperability serviceHTTP(S)
JMX AIC DMI OSSIARM
CIM Object ManagerCIM Object ManagerPIPEPIPE
Manageability Framework
Interoperability Layer— HTTP-XML
— LDAP-XML
— Corba
— (D)COM
CIM Object Manager— CIM Schema
Pipe (high speed /Bulk Data) Managed Services
— API (Java, C++, etc.) ARM Events
— Schema ARM Events Etc.
Services— Schema
— Api Inventory Performance Events Application Management Service Levels Status etc.
Manageability needs
Manageability needs today:— The managed components be instrumented
— Their be standard API sets so that the managed components can communicate independent of management solution
— Service definitions so the managed components and management system have common understanding of services management offers
— Common mechanism to use the information (ex. CIM)
Disjoint pieces of Manageability
No “APIs” that can provide the interface(s) that an applications can instrument to— ex. Never established a common API even for Events
No clear definition of manageability services No clear statement and business case for manageability Multitude of competing agents that are often
incompatible No clear roadmap No buy in from all vendors
Manageability Framework Goals
An optioned framework that covers all pervasive, mobile,desktop, servers computing systems
Provides for at least the minimal managed capabilities that allows any of the target systems to be managed
Framework must allow for a range of capabilities to cover all devices with a variety of capabilities
Objectives of the TOG Initiative
Define an architecture that will drive effective manageability
Establish standards for a Management Service Provider layer
Integrate existing specifications into a larger whole Provide an effective interface with Common
Management Infrastructures (ex. WBEM) Provide specifications for specific components of the
manageability instrumentation
A Manageability Framework
Common Manageability Provider Service
ARM
WBEM SNMP
DMIAIC XSLM XML
Plugins ForInterfaces
Plugins ForInterfaces
OSOS AppsApps
Plugins ForManagement
Interfaces
Plugins ForManagement
Interfaces
CommonServicesCommonServices
ManagementInfrastructureManagementInfrastructure
MiddlewareMiddlewareManagedEntities
Management
Manageability Challenges
Get all parties to the table
— Major Management Suppliers
— Smaller Management suppliersSmaller Management suppliers
— Application suppliersApplication suppliers
— OS suppliersOS suppliers
— Users
Figure out who can drive this program
— Management suppliers, App suppliers, etc.?
Management of existing apps is still high value solution
Manageability in TOG Today
Already delivering Manageability pieces
— XSLM – Client APIs for license management
— ARM – Client APIs for transaction information
— UMIA – Tool to aid agent installation
BUT
— Not coherent
— There is no architecture
— There is no industry leadership for the concepts
How can we Accomplish This?
GreenField – Create new standards— Positive – We get exactly what we want
— Negative - Long and difficult
FastTrack existing technologies— Positive – Moves them into the TOG domain
— Negative – Minimum possibility to integrate
Work from existing donated base technologies and specifications— Positive – We can modify the starting points together
— Negative – There is a real work effort
— Note: We can control what we get through RFIs
Common Provider Services
Open Manageability
XSLM
AIC
ARM UMIA
ManageabilityProgram
XSLM ARM
X
AIC
•Common Infrastructure•Compatible•Common view of services
Y Z
Open ManageabilityOpen ManageabilityUmbrellaUmbrella
UMIA
From IndividualComponents
Initiative Status today
Agreement on the need and base requirements Looking at alternate technologies Initiating architecture Working with several technologies
— Java JMX
— XML based instrumentation
Integrating Manageability with— Application run-time CIM Schema development
— TOG AIC extension to integrate with CIM, etc.
top related