Operax

Distributed Systems Manager

The DSM is a powerful generic SDK for distributed software management, handling any number of component installations onto any number of nodes. It supports scripted non-service-interrupting software updates, backups and restore.

The DSM provides WS access for performing runtime management actions and SNMP access for monitoring installed components. The open interfaces makes DSM a key facilitator for rapid integration with existing management systems.

The Distributed Systems Manager (DSM) provides system administrators with functionality for centralized deployment and management. Main features include:
• Template driven software and configuration management.
• Distributed remote software and configuration management.
• Software management includes installation, un-installation, update, backup and rollback.
• Fault and performance management.
• Automatic installation of third-party dependencies.
• Inventory of installed software systems.
The DSM supports all major manually initiated system management operations through the native web-based GUI.

The DSM Server consists of a core daemon utilizing an SQL database. The DSM provides a web interface called DSM GUI which connects to the DSM Server using an XML interface. The XML interface may also be used for scripting management actions. The GUI supports all basic administration tasks such as remote management and software configuration including installations, updates, configurations and backups as well as getting inventory reports and status information about the installed software.

The software distribution packages for the DSM consist of software components that come with one or more installation templates. A template describes the constellation of software components including dependencies and specific configuration/install instructions. Select installation templates to deploy the desired system. The DSM keeps an inventory of all installations made.

The external interfaces to the DSM are implemented with “agents” for southbound communication and “proxies” for northbound communication. After the target nodes are described to the DSM the deployment of the software components on the selected nodes are performed using a secure shell (SSH2) connection via the DSM Shell Agent. Runtime management of the software components is mainly performed via a Web Services (WS) interface. This interface is handled by the DSM WS Agent which in addition to configuration management is utilized for accessing performance counters and alarm tables.

The DSM Alarm Proxy listens to fault notifications over a Web Services (WS) interface from the installed software components and updates the status of the components accordingly. The DSM Server maintains a global alarm table based on these notifications. The Alarm Proxy can also be configured to generate SNMP traps to higher level management systems upon receiving notifications.

The DSM SNMP Proxy provides SNMP access to the DSM MIB. This MIB contains tables with read-only information about the installed software including a table with performance counters and alarms.

The DSM WS Proxy provides a northbound WSDM MUWS interface to the DSM object tree. Available via this interface are installed runtime configuration plugins.

Updated: Friday, 26 August 2011 10:10