Management Architectures DMTF Desktop Management Interface

1
Management Architectures DMTF Desktop Management
Interface
II
Part
2
DMTF Desktop Management Interface
Chapter 8
3
Learning Objectives

• Architecture and Organizational Model
• Information Model
• Communication Model
• Functional Model
• Chapter Summary

4
Architectural and Organizational Model

• DMI (Desktop Management Interface
• DMI as bridge to gap between proprietary device
  interfaces and standardized management
  architectures
• DMTF (Desktop Management Task Force) Undertook
  the integration of heterogeneous workstation
  computers with all their components into an
  integrated management
• DMTF was founded in 1992 as an association of HW
  and SW manufacturers
• Version 1 of DMI was published in 1994
• Version 2 of DMI was published in 1996 with
  remote access to the management entity
• Architectural and Organizational Model

5
Architectural and Organizational Model

• Architectural and Organizational Model
• The key element of AOM architecture is the
  service provider (SP)
• SP mediates between the managed resources of a
  workstation computer and the managing units
• SP represent an entity with functions comparable
  to those of an SNMP master agent
• SP receives queries and requests from remote
  applications over RPC at an interface called
  management interface
• Management Information Format (MIF) describe the
  resources at this interface
• SP processes requests or passes them to the
  managed components
• The component interface (CI) executes the request

6
Information Model

• Information Model
• DMTF IM is similar to the Internet SMI
  (structure of management information).
• Management Information Format
• The orientation of the IM, management information
  format (MIF) accounts for the differences between
  IM-MIF and the Internet SMI
• MIF contains specifications for the technical
  implementation of the cooperation between
  components and the SP
• A component is described in the MIF file that is
  transferred to the SP during registration
• The file contains all the static properties of
  the component that the SP is able to supply upon
  request
• The component description is structured as a list
  of attribute groups, follow by a list of tables
• DMTF two standard groups

7
Management Information Format

• DMTF two standard groups
• Definitions within the DMI architecture
• specification for the generation of uniform
  basic attributes
• Configuration of the SP itself
• Guarantee that a minimum amount of information is
  available for each component
• Definition of asynchronous event messages
• Definitions of working groups for specific
  component classes to ensure that uniformity
  exists in the basic groups for multivendor
  components
• Example of an IMF Definition (Page. 237)

8
Information Model

• Standardized Attribute Groups
• DMTF working groups standardized the following
  concrete attribute groups
• The systems standard group definition MIF
  Covers components of t he servers (hardware,
  processors main memory, cache, BIOS, video
  adapters, I/O interfaces, etc.)
• The mass storage standard group MIF definition
  covers large number of technical and detailed
  attributes and statistics on storage (HD, tape
  drives, CD ROMs, DVDs, etc)
• The monitor MIF definition - groups covers
  information on monitors (horizontal and vertical
  resolutions and refresh frequencies)
• The software standard group definition serves
  as the basis for the management of applications
  (software packages old and new)
• The cost of ownership MIF definition covers
  technical definitions for commercially relevant
  data such as prices, warranty periods,
  maintenance information, and leasing contracts.

9
Communication Model

• CM
• DMI-CM provides ways that allow the SP to
  exchange management information with the
  components and management applications
• Component Interface (not recommended because of
  its inefficiency)
• Interface to Management Applications
• Management interface of the SP make possible the
  communication with local and remote management
  applications
• SP functions provided to management application
  over the MI server are
• Attribute access operations allow the execution
  of a single operation to several attributes
• Administration operation registration and
  unregistration of applications for receiving
  event messages

10
Communication Model

• CM Interface to Management Applications
• SP functions provided to management application
  over the MI server are
• Inventory operations used by an application to
  obtain information about existing components, to
  add new ones and delete existing ones
• Manipulation of meta data the addition of new
  attribute groups
• Functional Model (FM)
• DMI FM is used for subscription and filtering of
  messages.

11
Communication Model

• CM
• Functional Model (FM)
• DMI FM is used for subscription and filtering of
  messages.
• FM two stages for subscribing and filtering of
  messages
• Stage 1 the management application requests all
  messages of the service provider
• Stage 2 if stage 1 is successful, the
  management application uses filter definition to
  request selected messages from components during
  stage 2.

12
Summary
Key Terms

• Review your slide notes in details
• All covered chapters

13
Next
Web-Based Management Architectures
Chapter 9