UNIVERSIT DOTTAWA IEEE NM Workshop-98, Kazi Farooqui.. UNIVERSITY - - PDF document

IEEE NM Workshop-98, Kazi Farooqui.. 1

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA Policy-Driven DISTRIBUTED MANAGEMENT ARCHITECTURES (Towards Open Distributed Management Architecture) “Integrating Management and Distributed Object Technology” Kazi Farooqui (farooqui@csi.uottawa.ca) Department Of Computer Science, University of Ottawa, Ottawa K1N 6N5, Canada.

IEEE NM Workshop-98, Kazi Farooqui.. 2

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ Model for Distributed Management:

☞ Synergy of:

• 1. Existing Management Models

+

• 2. Distributed System Architectures such as RM-ODP.

☞ WHAT ODP Concepts + Principles + Architectural Frame-

work can be used to enhance the OSI Management Model towards a “Distributed Management Model”? Figure 1. Integration of Distributed Object Technology in Network Management Models

• 1. Integrating Management Models and ODP Model

DISTRIBUTED OBJECT TECHNOLOGY (ODP, CORBA, ANSAware) NETWORK MANAGEMENT MODELS (OSI Management, TMN) DISTRIBUTED MANAGEMENT MODELS (ODMA)

IEEE NM Workshop-98, Kazi Farooqui.. 3

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ Why DISTRIBUTED OBJECT TECHNOLOGIES:

☞ Management Activity: Inherently DISTRIBUTED in nature. ☞ Management Applications: Advanced DISTRIBUTED PRO-

CESSING APPLICATIONS.

☞ Management Platforms: Require numerous DISTRIBUTED

PROCESSING functions (Transaction, Replication, Group, Event Distribution, Location Transparency, etc.) ❑ How does ODP Help...........

☞ GENERIC: A Generic Architectural Framework for Distrib-

uted Systems Development (Concepts + Architectural Princi- ples + Distributed Processing Functions).

☞ META-STANDARD: Applicable to Different Application

Domains (Telecommunications, Network Management, Manufacturing, etc.)

☞ DISTRIBUTED OBJECT MODEL: A Technology-Indepen-

dent Model for the Development of Distributed Object-Based Systems.

☞ STRUCTURING PARADIGM: Different Viewpoints pro-

vide clear separation of concerns and focus on specific man- agement aspects. (De-coupling of Management Applications and Management Platform).

• 2. MOTIVATION

IEEE NM Workshop-98, Kazi Farooqui.. 4

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ Limitations of the OSI Management Model:

☞ Primitive Point-to-Point Model. (Support for traditional

Point-to-Point Management Activity).

☞ Tied to a specific Communication Platform (CMIS/CMIP).

(Tight coupling between management operations and com- munications infrastructure). ❑ Towards Distributed Management Models.......

☞ Object-Machines for Configurable Distributed Management

Platforms.

☞ Hierarchical Management Models. ☞ De-coupled Management Applications and Management

Platforms.

☞ Policy-Driven Management Models. ☞ Management Domains.

• 3. State of the Art......

IEEE NM Workshop-98, Kazi Farooqui.. 5

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA

IEEE NM Workshop-98, Kazi Farooqui.. 6

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA

TECHNOLOGY ARTIFACTS OF Management-SERVICES & Management-DISTRIBUTED PLATFORMS Enterprise Model Information Model Computational Model Engineering Model Management Enterprise Model Management Information Model Management Computational Model Management Engineering Model ODP Generic Model Inheritance & Specialization (of Concepts, rules, structures)

Figure 2. ODP Modelling of Management Systems

Management Architecture

IEEE NM Workshop-98, Kazi Farooqui.. 7

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ FOCUS is on:

☞ Preliminary COMPUTATIONAL and ENGINEERING

Models of OSI Management. (Start with Bits and Pieces of Computational and Engineering Modelling of Manage- ment).

☞ ODP Computational Model: A Framework for the Definition

• f Management Application as a Distributed Object World

interacting by invoking Operations/Notifications at Interfaces in a “distribution-transparent” manner. Identification of:

• 1. Management Application Components.
• 2. Multiple Interfaces of Components.
• 3. Interactions between Interfaces (Operations, Notifica-

tions).

• 4. Environment Constraints on Management Components

and their Interactions.

☞ ODP Engineering Model: A Framework for the Definition of

an Object-Based Distributed Management Platform. Modular Platform Support for Management Applications and of their interactions:

• 1. Communications-Support Infrastructure.
• 2. Transparency Support Infrastructure.
• 3. Domain-Specific Support Infrastructure.
• 4. Support for Management Policies.
• 5. Dynamic and Flexible Management Infrastructure.
• 4. To Start.........

IEEE NM Workshop-98, Kazi Farooqui.. 8

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ What does ODP Computational Model offer to Management Model:

☞ Basic Object Model. ☞ Interaction Model. ☞ Type Model. ☞ Binding Model.

• 5. Basic Computational Modelling of OSI Management

IEEE NM Workshop-98, Kazi Farooqui.. 9

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ BASIC OBJECT MODEL: Figure 3. Management Object

☞ A Management Object offers multiple interfaces in different

roles.

☞ Roles are associated not with Objects but with their

Interfaces.

☞ Management Object may act as “Manager” on one inter-

face and as “Managed Object” on another interface.

☞ Supports the Modelling of “Hierarchical Management

Applications”:

• 1. Hierarchy of managers managing a set of distributed

managed objects.

• 2. Delegation of responsibility from a manager to a sub-
• manager. (Delegation of Management).

management

• bject

Legend: : manager role interface : managed role interface : application-specific role

IEEE NM Workshop-98, Kazi Farooqui.. 10

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ INTERACTION MODEL: Figure 4. Objects Interact by Operation Invocations OR Notifications at their Interfaces.

☞ Management Application is an object-based distributed

application.

☞ Application components interact by sending operation

invocations (ODP Interrogations) or notifications (ODP Announcement) at their interfaces.

☞ Management Interfaces specify:

• 1. signature: management operations and notifications.
• 2. behavior: ordering of operations and notifications =

Protocol between interacting management interfaces.

• 3. environment constraints: QoS, Distribution Transparency,

etc. (Notifications be delivered within 5 msec.) (Notifications be delivered to a group of managers). (Operations to be delivered to all or none of managed interfaces).

Computational Interface Template

Distribution-Transparent Interaction

Management Object Management Object

IEEE NM Workshop-98, Kazi Farooqui.. 11

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA Figure 5. Distributed Management Computational Model

☞ Distributed Management Computational Model is Backwards

compatible with the existing Point-to-Point OSI Management Model:

• 1. Managing System:
• a. Management Object = single-interface object with “man-

ager role”.

• 2. Managed System:
• a. Management Object = Agent Object with a “managed

role” interface and a “manager role” interface.

• b. Managing System “manager interface” is bound to the

“managed interface” of Agent Object.

• c. Agent offers a local “manager interface” bound to MO

mco mco mco mco mco mco mco mco mco mco

manager

agent

MO MO MO MO

Managed system. Managing system. Legend Manager Interface. Managed Interface. Application Specific Interface. MIB mco: management computational object MIB: Management Information Base

IEEE NM Workshop-98, Kazi Farooqui.. 12

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ TYPE MODEL: Figure 6. Type Model: Interactions based on interface type matching.

☞ Management Applications are complex applications which

can be created out of available components.

☞ A repository of management components and their interface

types enables faster application creation.

☞ Management Application creation/composition based upon

type-checked (late) binding of (interfaces of) application components.

☞ substitutability of one application (component) by another.

(A manager interface can be substituted by its sub-type).

☞ Current ODP Type Model: Based on operation signature

• compatibility. Subtyping can be extended to QoS compatibil-

ity and behavior compatibility to meet the needs of manage- ment applications.

M-CO1 M-CO2 M-CO3

IEEE NM Workshop-98, Kazi Farooqui.. 13

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ BINDING MODEL: Figure 7. Multi-Manager / Multi-Managed Object Binding.

☞ Support for management application-specific interaction pat-

tern between multiple managers and managed objects.

☞ Binding Objects enable complex binding structures to be sup-

ported between management application components. (Mul- ticasts of Notifications issued by an Event Forwarding Discriminator to multiple managers).

☞ Applications have control on configuration and quality of

service of the complex binding (Add / Delete Managed Objects from the configuration). M-CO-3 M-CO-2 M-CO-1 M-CO-4 BINDING OBJECT Configuration Management Interface QoS Management Interface

IEEE NM Workshop-98, Kazi Farooqui.. 14

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ What does ODP Engineering Model offer to Management Model:

☞ Model of an Object-Based Distributed Platform:

• 1. Concepts, Rules, Structuring Framework (of nodes, cap-

sules, clusters, objects) for the organization of a Manage- ment Platform that supports execution and interaction of Management Application Components.

☞ Distribution Transparency Support Mechanisms:

• 1. An engineering framework of “transparency support mech-

anisms” for the provision of location transparency, migra- tion transparency, transaction transparency, group transparency etc. to the interactions between Management Application components.

☞ Model of a Configurable and Policy-Driven Platform.

• 6. Basic Engineering Modelling of OSI Management

IEEE NM Workshop-98, Kazi Farooqui.. 15

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ Basic Engineering Concepts of OSI Management:

• 1. Basic Engineering Object: Engineering representation of

“management computational object”. Figure 8. Computational Object and Cluster: A powerful modelling paradigm.

• 2. Cluster: A group of related management objects at a node. (A

set of related managers synchronized via internal interfaces and accomplishing a common management function OR a set

• f MOs related to different aspects of a single resource).
• 3. Cluster Manager: Part of Agent Functionality.
• 4. Capsule: A group of “management clusters” with unrelated

management responsibilities.

• 5. Capsule Manager: A Super-Agent.
• 6. Nucleus: Access to CMIP communication facility.

mco

m5 m1 m3 m2 m4

meo meo meo meo

m1 m2 m3 m4 m5

Legend: mco: management computational

• bject

meo: management engineering

• bject

IEEE NM Workshop-98, Kazi Farooqui.. 16

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA

• 7. Node: An open system consisting of both manager and man-

aged interfaces.

• 8. Stub Object: A marshalling/information modification func-

tionality that transforms management operations into mes- sages that are exchanged as CMIP PDUs.

• 9. Binder Object: Support for Distribution Transparencies.
• 10. Protocol Object: CMIP and the underlying stack of OSI/TCP-

IP communication protocols.

• 11. Channel: A configuration of stubs, binders and protocol
• bjects between manager and managed interfaces is the key to

the design of a policy-driven management platform.

IEEE NM Workshop-98, Kazi Farooqui.. 17

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ Extending the current OSI Management Model:

☞ Engineering Functions clubbed in the Agent:

• 1. Scoping (performed in a local system)
• 2. Filtering (performed in a local system)
• 3. Synchronization (performed in local system).
• 4. Event Notification
• 5. Object Management.

☞ Scope of these functions can be extended in a “distributed

management context:

• 1. Scoping -----> ODP Group Function.
• 2. Synchronization -----> ODP Transaction Function
• 3. Event Notification -----> ODP Event Notification Function
• 4. Object Management -----> Cluster Manager/Capsule Man-

ager

IEEE NM Workshop-98, Kazi Farooqui.. 18

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ SCOPING:

☞ Scoping can be performed on Managed Objects (MIBs) in

multiple systems using the “ODP Group” concept. Figure 9. Grouping and Scoping in a Distributed Management System.

☞ MIBs on distributed systems are organized as an “ODP

Group” with Base-Level MOs as members.

☞ A management operation multicast by a manager is received

by all group members.

☞ Group Invocation: Addressing and selection of base-level

MOs in different systems.

☞ Scoping: Selection of MOs in the Local System.

Managed System-1 Managed System-2 Managed System-3 ODP Group Scoping MIB MIB MIB

IEEE NM Workshop-98, Kazi Farooqui.. 19

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ SYNCHRONIZATION:

☞ In a distributed management model, manager requires a man-

agement operation performed atomically on all MOs distrib- uted on different open systems.

☞ Synchronization can be performed on Managed Objects

(MIBs) in multiple systems using the “ODP Transaction” concept. Figure 10. Transaction in a Distributed Management System

☞ Management operations emitted by the manager are inter-

cepted by the Transaction Function.

☞ Transaction Protocol is carried over CMIP using M-Action

PDUs between the involved manager and managed systems.

☞ Local Synchronization is performed by LSF.

Manager Agent MO MO MO MO CMIP CMIP OSI Protocol Stack OSI Protocol Stack TF TF To other Managed Systems LSF (M) (S) Legend: TF: Transaction Function M/S:Master / Subordinate LSF: Local Synchronization Function

IEEE NM Workshop-98, Kazi Farooqui.. 20

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ EVENT NOTIFICATION & OBJECT MANAGEMENT: Figure 11. Event Notification and Object Management Function in the ODP Framework

☞ Both the MOs (in different systems) and the Manager sub-

scribe to the “ODP Event Notification Function” to send and receive events.

☞ ODP Cluster/Capsule Manager perform the object manage-

ment functions such as MO creation, deletion, checkpointing, deactivation and reactivation.

☞ IN ALL THESE CASES AGENT WORKS AS AN INTER-

CEPTOR OF MANAGEMENT OPERATIONS.

CMIP CMIP OSI Protocol OSI Protocol CPM/ CLM ENF MO MO MO MO Agent Manager To other Clusters To other Clusters Event Logging Event Notification Object Management Event Notification Legend: CPM: Capsule Manager CLM: Cluster Manager ENF: Event Notification Function Stack Stack

IEEE NM Workshop-98, Kazi Farooqui.. 21

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ Basic Components

• 1. Monitoring: To obtain information from management

interfaces of physical resources

• 2. Domains: To group management objects and to partition

responsibility.

• 3. Policy: To permit the behavior of automated managers to be

modified without re-implementation. ❑ Management Domain A “set of objects” which are related because a certain part of their “behavior” is controlled by the same “authority” (e.g. tele- com stakeholder) under a set of “management policies”.

• Autonomy (Authority)
• Policy
• Behavior/Aspect
• Addressing Unit

X-Aspect Management Domain, Y-Aspect Management Domain “Start_Test() on all domain members for which the predicate “x- attribute > n” is true.”

• 7. Policy-Driven Distributed Management Models

IEEE NM Workshop-98, Kazi Farooqui.. 22

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ Why Domains

• 1. To group the objects related to a particular service or function.
• 2. To group the objects to which a policy applies.
• 3. To specify boundaries of management responsibility or

authority.

• 4. To provide a “naming context” in which managers may assign

local names of their choice to the objects they manage.

• 5. To reflect organizational, geographic or network structure.

❑ Domain Membership

• 1. Create a domain
• 2. Delete a domain
• 3. Add an object
• 4. Delete an object
• 5. List members
• 6. Change member name
• 7. Query domain’s parents.

IEEE NM Workshop-98, Kazi Farooqui.. 23

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ Policy-Driven Management

• 1. Mechanisms vs. Policies: Separation of “management policy”

from “Automated Managers” which interpret the policies.

• 2. Specification of Policies: High-level Specification of manage-

ment goals using some Policy Specification Notations.

• 3. Interpretation of Polices: Interpretation of policies into man-

agement actions.

Figure 12. Policy-Driven Management: Managers interpret Policy to perform management

policy

• bject

interpret

• perations

notifications replies manager

• bject

managed

• bject

physical resource application specific interfaces OMI Legend: OMI: Object Management Interface : Manager Interface : Managed Interface PAI MPI PRI MPI PRI: Physical Resource Interface MPI: Management Policy Interface PAI: Policy Administration Interface

IEEE NM Workshop-98, Kazi Farooqui.. 24

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA Figure 13: Computational Model-1: Policy-Driven Managers

MO- 3

OMI

MO- 2

OMI

MO- 1

OMI

DMO

PMI MMI DMI PMI MMI DMI

DMO

PMI MMI DMI

MO- 4

OMI

MO- 5

OMI

MO- 6

OMI

MO- 7

OMI

sub-domain D-1 sub-domain D-2 Managed Domain-D Manager Object Policy Object OPR REP/NTF Domain Administration Authority Legend: OPR: Operation Invocation NTF: Notification Invocation REP: Reply Invocation MMI: Membership Management Interface PMI: Policy Management Interface DMI: Domain Management Interface OMI: Object Management Interface : Managed Interface : Manager Interface Manager Domain

IEEE NM Workshop-98, Kazi Farooqui.. 25

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA

Figure 14. Computational Model-2: Policy-Driven Managed Objects

MO- 3

OMI

MO- 2

OMI

MO- 1

OMI

DMO

PMI MMI DMI

DMO

PMI MMI DMI

DMO

PMI MMI DMI

MO- 4

OMI

MO- 5

OMI

MO- 6

OMI

MO- 7

OMI

sub-domain D-1 sub-domain D-2 Policy (P) Policy (P1) Policy (P2) Policy Conflict Resolver Policy Conflict Resolver

OPR NTF/REP OPR NTF/REP OPR NTF/REP OPR NTF/REP OPR NTF/REP OPR NTF/REP OPR NTF/REP OPR NTF/REP

MANAGER OBJECT Managed Domain-D Manager Domain Legend: OPR: Operation Invocation NTF: Notification Invocation REP: Reply Invocation MMI: Membership Management Interface PMI: Policy Management Interface DMI: Domain Management Interface OMI: Object Management Interface : Managed Interface : Manager Interface

IEEE NM Workshop-98, Kazi Farooqui.. 26

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA Figure 15. Policy Driven Manager and Managed Objects

C MI P G S M C MI P G S M C MI P G S M C MI P G S M C M I P G S M C M I P G S M C M I P G S M C M I P G S M Policy (P1) Policy (P2) PCR Policy (P3) Policy (P4) PCR MO-1 MO-2 MO-3 MO-4 Managed Domain M-1 M-2 M-3 M-4 Manager Domain Group Communication using Multicasting Protocols Engineering Support for Domains

sub-domain

sub-domain

Legend: M: Manager Object MO: Managed Object PCR: Policy Conflict Resolver Object GSM: Group Support Machine

IEEE NM Workshop-98, Kazi Farooqui.. 27

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ ODP Distribution Transparencies in the Management Model:

☞ Access Transparency: Management Applications invoke

CMIS service through standardized service primitives.

☞ Location Transparency: Requires location-independent nam-

ing model in the management domain.

☞ Migration Transparency: Highly dynamic mobile telecom-

munications environments.

☞ Transaction Transparency: Management Operations (such as

Suspend_Test(), Resume_Test(), Set_Attributes()) require all-or-nothing semantics in their execution.

☞ Group Transparency: Identical management operations on a

set of distributed Managed Objects.

☞ Persistence Transparency: Reactivate both manager and man-

aged objects when a notification or an operation is invoked

• n them.

IEEE NM Workshop-98, Kazi Farooqui.. 28

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA ❑ Management constitute a significant application domain of

• ODP. ODP Provides:

☞ Distributed Object Model. ☞ Modeling Frameworks (viewpoints). ☞ Interoperability Model. ☞ Distribution Transparency Model.

❑ Increasing convergence taking place between management models and distributed computing (such as ODMA).

☞ ODMA: Object-Based Management Architecture

Distributed Management Model Technology-Independent Management Policy-Driven Platform Configurable Platform. ❑ “Distributed-Object Computing Technologies” have a major role to play in the definition of tomorrows MANAGEMENT ARCHITECTURES.

• 7. CONCLUSION