740 likes | 855 Views
Application Model & Metrics Model Update June 2001. Version 1.00 13 June. Karl Schopmeyer The Open Group k.schopmeyer@opengroup.org. This presentation is dedicated to Heather Kreger and all of the work she has done to move application management forward. Agenda.
E N D
Application Model&Metrics ModelUpdateJune 2001 Version 1.00 13 June Karl Schopmeyer The Open Group k.schopmeyer@opengroup.org This presentation is dedicated to Heather Kreger and all of the work she has done to move application management forward DMTF Developers Conference
Agenda • The Objectives of Application Management • The Original Model – Life Cycle Management • The Metrics Model • The Work Today • Managing Running Applications • Directions and Futures . DMTF Developers Conference
The Objectives of Application Management • Life-Cycle Management of Applications • Distribution, installation, etc. • Management of running Applications, Services, Business Applications • Performance Information, Executing Operations, State of the application, etc. DMTF Developers Conference
A Short History of the Group • Application Model – Lifecycle • One of the first models finished (1999) • DAP • Model finished 2000 • Application RunTime • Group initiated 2000 • First Submission CIM V2.5 • Merge with DAP (common Metrics) 2001 • In process now DMTF Developers Conference
Major Participants • Mark Johnson (Tivoli) • Heather Kreger (IBM) • Alex Keller (IBM) • Takaki Kuroda (Hitachi) • Vijay Machiraju (Hewlett Packard) • Mike Reynolds (BMC Software) • Karl Schopmeyer (The Open Group, Tivoli) • John Sweitzer (Tivoli Systems) • AndreaWesterinen (Cisco Systems) DMTF Developers Conference
Consumed By Consumed By Management Tool Produce OperatingSystems Install Utility System Based Software Inventory User’s of the Application Model Application Developers and Providers Produced By Hand Application Development Tool Produced using tools like change management tools. CIM-based Application Management Information Software Distribution, Dependency Checking, Change Management Systems Systems Systems DMTF Developers Conference
The Existing Models Application Management Model DMTF Developers Conference
Product Service Application System Software Feature Software Element Application Model Overview Execution Service Unit of Acquisition Application Model Core Model Collect Features into Business System ProductSoftwareFeature ApplicationSystemSoftwareFeature SoftwareFeatureSoftwareElements Unit of Component Management Unit of Deployment DMTF Developers Conference
Software Element Software Elements • The Unit of Deployment • Installed and uninstalled • Represent a collection of files and associated details that are individually managed • Abstracted to Software Features This is what actually gets installed DMTF Developers Conference
Software Feature Software Feature • Unit of component management • Components meaningful to consumer or user of the application • Reflect functions or roles of a component of an application • Ex. Trading client, quote server, etc. This is what the user sees DMTF Developers Conference
Product Software Product • Unit of acquisition • Implies agreement between consumer and supplier • License, support, warrantee, … This is what we pay for DMTF Developers Conference
Application System Application Systems • Collect features into business systems • Support a business function • Collections of software features from one or more products combined to fulfill business function This is how the managers would like to view the environment DMTF Developers Conference
Life-Cycle Management Application Management Model the Application Life-Cycle DMTF Developers Conference
Application Life Cycle • Critical states in process of transition from development to operational • Applies to lowest-level component • Software Elements • States Deployable Installable Executable Running DMTF Developers Conference
Deployable Installable Executable Running States Details Platform NT Windows 95 Solaris HPUX • Number • Conditions • Actions ... Refining Software Element Software Element DMTF Developers Conference
In-State In-State In-State In-State Next State Next State Next State Next State In-State Conditions are characteristics of an environment that contains an element. Next-State Conditions are characteristics that need to be true in the target environment for the next state of a software element. Software Element Conditions Installable State Executable State Running State Deployable State Conditions Conditions Conditions Conditions Conditions are situations that are expect to exist or not exist in an environment DMTF Developers Conference
Software Element Conditions DMTF Developers Conference
Software Element Conditions DMTF Developers Conference
Next State Next State Next State Next State Uninstall Uninstall Uninstall Uninstall Next State Actions create a software element in a particular state. Uninstall Actions properly remove a software element Software Element Actions Installable State Executable State Running State Deployable State Actions Actions Actions Actions Actions are a sequence of operations DMTF Developers Conference
Running Deployable Installable Executable Software Element Actions DMTF Developers Conference
Software ElementChecks Action Check More on the Model Phase Software Element SoftwareElementAction SoftwareElementState ActionSequence Direction DMTF Developers Conference
Deployable Installable Evaluating Deploying Executable Running Diagnosing Configuring Resource Life Cycle Planning Operating Current Modeling work is focused on the “Running Application Requirements” DMTF Developers Conference
Application Management Model The DAP Model - Measuring Performance DMTF Developers Conference
DAP Working Group • DAP = Distributed Application Performance • DAP model incorporated into Schema in Schema 2.3 or 2.4 • DAP work to merge with runtime application work group. DMTF Developers Conference
DAP Charter • Define common model for standard runtime behavior of distributed applications in heterogeneous environments • Includes quality of service objects • Relate to other CIM models • Evolve standard methods to populate the model • Develop a unifying model for a unit of work DMTF Developers Conference
DAP Status • Define common model for standard runtime behavior of distributed applications in heterogeneous environments • Includes quality of service objects [DONE] • Relate to other CIM models [TBD??] • Evolve standard methods to populate the model • Will DAP ever do this? • Emphasis has been on compatibility with existing interfaces (ARM in particular), rather than defining new ones • Unifying model for a unit of work [DONE] DMTF Developers Conference
Unifying concept for a unit of work • A unit of work can be many things, such as: • Batch job • User-initiated interactive operation • Transaction executed by a TP Monitor • Short server transactions, such as a database read DMTF Developers Conference
Thoughts on naming • Why is the term “Unit of Work” used instead of “Transaction”? • “Transaction” can imply specific behavior, such as commit and rollback • Batch jobs and similar units of work are not often thought of as “transactions” DMTF Developers Conference
Major schema classes • Definition of unit of work type • Instances of these unit of work types that have started executing • Common measurements are properties • Definition of metrics associated with the unit of work • Values of metricsNote: what has also been added since the last version was the asociation to CIM_ManagedSystemElementfrom the CIM Core Schema. DMTF Developers Conference
Managed Element CIM_ Logical Element Logical Element performs UOW Logical Element UOW Definition UOW Definition Sub UOW Definition UOW Metric Definition Started UOW w Metric Definition UOW UOW Metric Metric Value Sub UOW DMTF Developers Conference
NEW DMTF Developers Conference
Unit Of WorkDefinition • Defines a type of work • Examples: • Update account balance • Backup file system • Query data server • Execute subroutine/method DMTF Developers Conference
UOW DefinitionProperties • ID - 16 bytes long [key] • Use of OSF UUID is recommended • MAC address (or substitute) • Current date and time • Counter to handle high-frequency allocations • A clock sequence and related state to handle the retrograde movement of clocks. • Name • Context (such as application name) DMTF Developers Conference
Unit of Work • Represents a UOW that has started (and maybe completed) executing • Always associated to its definition • Weak association with propagated key • This provides separation of the namespace to avoid collisions DMTF Developers Conference
Unit of WorkMeasurements • Response time or elapsed time (if still executing) • Status • Active • Suspended • Completed (with unknown state) • Completed Good • Completed Failed • Completed Aborted • Metrics (in a separate class) DMTF Developers Conference
Unit of WorkProperties • ID [key] • UOW ID [key, propagated] • User Name [or ID or context or ???] • Start time • Elapsed time since UOW started (response time if complete) • Status DMTF Developers Conference
Associationsbetween UOWs • UOW may be associated to other units of work (parent or children) • Ex: a server UOW may be the child of the client UOW that invoked it • Association can be at either or both of two levels • Between UOW definitions • Between UOW instances DMTF Developers Conference
Associations toLogical Elements • A UOW instance may be associated to the Logical Element that performs it • Examples: • Computer system/processor • Printer • Application system DMTF Developers Conference
Associations toLogical Elements-2 • A UOW definition may be associated to another logical element • Semantics of the association are not specified DMTF Developers Conference
MetricDefinition • The Class • Defines metrics associated with a unit of work • Even if defined, a value may not be provided at all times • Properties • ID [key] • Name • Data type (sint32, uint64, string, …) • Calculable (What type of calculations, if any, are OK: none, sum, no sum) • Units (bytes, files, milliseconds, …) • Validity (start/middle/stop) [??] DMTF Developers Conference
Metric • Contains the actual value at any point in time • Value is a string so it can contain any of the several data types • Constraint on Metric Definition: • Must be associated to the same UOW Definition to which the UOW is weakly associated DMTF Developers Conference
Application Management Model Managing Operational Applications DMTF Developers Conference
Running Application Requirements Running Application Requirements have many interpretations. • They can focus on the “Resource View”… • Model the operational issues for an application in isolation. • They can focus on the “Service View”… • Model the operational issues of a service for a user • They can focus on the “Business View”… • Model the operational issues for an application that is part of a business process. DMTF Developers Conference
Run Time Relationships Events Monitors (Thresholds) Metrics Application Description Operations Heartbeat Configuration Information Exerciser Running Application Ingredients DMTF Developers Conference
Leverage: How does the Core Model classes for Configuration and Setting fit into the requirements? Scope: How does one express the existence of a setting before values are known? Configuration Information Classes: What classes can have configuration information? (Product, Software Feature, Software Element, Services, etc.) Operations: What assumptions does a particular approach make about how configuration is changed? (method call, property value, etc.) More Details for Configuration Information DMTF Developers Conference
Leverage: How does the DAP Model relate? Scope: How does one express the existence of a metrics before values are known? Classes: What classes can have metrics? Does the answer change for resource/service/business views? Policy: How does the policy model impact metrics? Metrics More Details for Metrics DMTF Developers Conference
Leverage: Can runtime operations be expressed using the CIM method concept? Scope: How does one express the existence of an operation? Classes: What classes can have runtime operations? (Product, Software Feature, Software Element, Services, etc.) Parameters: What are the type of parameters? Operations More Details for Operations DMTF Developers Conference
Issues with Managing Apps • There are so many of them • There is no single clear model for the organization of Applications • Application structure and architecture varies widely • Moving from static to dynamic applications and relationships DMTF Developers Conference
The State of the Model • Metrics Model • Preliminary defined • Operations Model • Preliminary Defined • Configuration Information • In Process • State Management • Preliminary Discussion • Incremental Changes Passed Schema 2.5 DMTF Developers Conference
Modeling Metrics • Step 1 -Started with an independent Model • Step 2 –Realized commonality with DAP • Step 3 – Blended two in to Metrics work group • Step 4 – Blended metrics back into Runtime Apps • Status Today • Preliminary model defined • Needs documentation DMTF Developers Conference