User Tools

Site Tools


Welcome to DIDO WIKI

dido:public:ra:1.4_req:2_nonfunc:28_manageability:02_types Types of Manageability Functions


Return to Top

NI (formerly National Instruments) defines four basic manageability functions 1) described in the following Table:

Table 1: The kinds of Management Functions needed for Manageability
Kinds of Management Description
Health Monitoring, Logging, and Alerting During operations a key part of managing the system is the collection of metrics about the operations that indicate the health of the system.
  • Monitoring can include usage of Central Processing Unit (CPU), memory, energy, cache, heat, on-line and off-line storage, network connectivity, network loads of particular computers. In a distributed system, this also includes the metrics associated with the connectivity of the nodes that participate in the distributed system (i.e., the latency, lag, error rates, upload and download speeds, etc).
  • Information about the overall operations need to be handled. For example, data used to Trace, and Debug; provide Informational context; and alert to warnings, errors and fatal situations.
Configuration and Control

During the startup and sometimes during operations, the system needs to obtain configuration details and provide control over the systems as a whole or to the individual components. This becomes even more important in a system that is distributed on a system of nodes. 1)

  • Typical configuration management data are Internet Protocol Address (IP Address), network ports, environment paths to files, and maximum usage limits for things like CPU and disk space.
  • Typical commands are start, pause, resume and stop. Sometimes abort is also used to capture detailed dump files that can be used for analysis.
Deployment and Updates During operations,
  • There is sometimes a need for the efficient and sometimes automatic deployment of system resources such as web servers, application servers, DataBase Management System (DBMS), backups etc. This is useful when systems are made as a collection of other systems but is critical when managing distributed systems.
  • In addition, this kind of management needed during first-time installation of systems (i.e., wizards) but also in deployed systems for applying patches, performance, and feature updates.
Asset Discovery and Inventory In remote systems or especially in distributed systems, an accurate and timely discovery of the system or component needs to be made.
  • In truly distributed systems, this discovery needs to be dynamic and should easily adapt to new locations. In a distributed system this must also support the dynamic creation and destruction of nodes in the system network.
  • In complex systems deployed on a single computer there is a dependency on other components within the node. An inventory needs to be made of the components required as included in a package management description (i.e., manifest).
  • In a distributed system running on distributed nodes there is a need to understand the resources dedicated to the system. Having an automated inventory helps with asset management, containing cost controls, and scheduling maintenance or replacement of systems.

1) Note: The following example of how configuarions can become a manageability issue is from Candea 1)- The greatest manageability challenge is posed by stateful systems (e.g., databases, filesystems). By contrast, stateless applications (e.g., Web servers) require little configuration, can be scaled through mere replication, and are reboot-friendly. While one administrator can manage 100s to 1000s of Web servers, it takes approximately one administrator for each TB of data in a database. The number of knobs on stateful systems is overwhelming: the Oracle DBMS has 220 initialization parameters and 1,477 tables of system parameters, while its “Administrator's Guide” is 875 pages long.

DIDO Specifics

Return to Top

To be added/expanded in future revisions of the DIDO RA
What is Manageability?, 5 May 2019, National Instruments (NI), Accessed 25 July 2020,
dido/public/ra/1.4_req/2_nonfunc/28_manageability/02_types.txt · Last modified: 2021/08/11 11:36 by murphy
Translations of this page: