Distributed Systems Management• What is management?

• Strategic factors (planning, control)• Tactical factors (how to do support the strategy practically).

• Handling planning/control/configurations – being able to adapt to changes.

• Manual and Automatic elements.

The management (life) cycle

What should be managed?• Configuration management• Fault management• Accounting management• Performance management• QoS management• Security management• Name and directory management

• Tools:• Remote operation execution• Management Information Storage• Even reporting• Log control

System Management Architectures

• What management architectures are you using in your project?

Managed objects• Management Interface in addition to the functional interface• Can be a structure outside a hardware unit

• Operation: requests on the objects (aqtion, information)• Results (response)• Notifications (unsolicited)

MIB: Management Information Base

Management Functions

• Configuration• Fault• Performance / QoS• Accounting• Security• Naming

Configuration management• For example Network Configuration

• Information (graphical) to administrator• Discovery of topology• Automated / manual reconfiguration or updates

• Other HW/SW Configuration issues

• State: up or down?• Status: e.g. load or other internal state of an object• Relation: Relations to other objects

Fault management• Detecting and solving errors… • Notifications of (faults, failures, errors).

• - and what comes after notification?• Notification / alarm may be brought along with information about the faulty situation.• Solving the errors – reconfiguration, replacement of equipment, other actions.• Fault diagnosis or test after problems have been solved.

• Fault prevention – e.g. warning about faulty equipment…

Performance / QoS management• Performance: What is the distinction between monitoring and management?• Step 1: Monitoring speed, latency, progress of processes. Comparing monitored valures to desirable or required ones. Actions/alarms in case of specification violations.• Congestion, overloads, assisting the (capacity) planning.• What countermeasures to take in case of violations???

Accounting management• Monitoring usage of e.g. bandwidth and other ressources (like disk space, processor power).

• Construction of statistics• Can be used for accounting, i.e. charging the users depending on their usage of ressources (ISP, Telephony providers, storage providers, ….).

• Different kinds of monitoring:

Security management• From the management point of view, it is much about monitoring events – for example intruisions, abuse, violation of specifications.

Naming management• Keeping track of names, updating, organising, …• Not trivial in a highly dynamic (and possibly mobile) environment

Strategic Management• The strategy is the highest level of management• Deals with policies and pricinples.• Decisions concerning how to handle different situations, from a ”political” rather than technical point of view.

• E.g. what should happen in case of security violations, or if a user is using more ressources than he is supposed to do?• E.g. how should quota for disk space, CPU power etc. be allocated?

• The strategical management has the long-term view of the system.

• Strategical management -> Tactical Management (-> Operational management).

• The strategical management should be explicitly described (as opposed to implicitly assumed ).

Tactical Management• Based on the strategic management• Example: Strategic management has defined how to handle disk quotas. The tactical management will deal with how to execute these policies. Could also be the implementation of back-up procedures.• Are more technical than the strategic management – and shorter-termed.

Centralising or decentralising?• Should the management be distributed, and how?• A Distributed system can very well be centrally managed (which is often the simplest, especially if the system is homogeneous).

• Example: Network management• Centralized management may be impossible in geographically dispersed and heterogeneous systems. • How about the scalability?

• Integrated management – a ”third way” which is basically centralized. Still unmature, but potential useful for many systems including c2c systems, sensor networks, …

A generic management model• To describe the different management models….

• Scalability can be supported by hierarcies and/or cooperation

•As in all other protocol stacks: proxies

Centralized management model• Islands of management (with or without coordination)

Integrated management model•Nice simple figure, but tool integration platform is not simple… different distributed-systems models can be applied here as well.

Decentralized management model•Nice simple figure, but tool integration platform is not simple… different distributed-systems models can be applied here as well.

OSI management model• … may be simplified by ODP management model.

Monitoring models• acquisition, processing, dissemination, presentation (at management consoles).