SYSTEM MANAGEMENT IN OPENCLOVIS SAFPLUS PLATFORM

Introduction

OpenClovis SAFplus Platform provides a comprehensive platform and system management and component manageability. In the context of the OpenClovis SAFplus Platform, system management specifically refers to managing the various components and resources within that platform. This article delves into the key elements of system management within OpenClovis.

 

Components of Manageability

OpenClovis includes several key components that work together to ensure effective system management. Manageability comprises the following components:

1. Clovis Object Repository (COR):

The Clovis Object Repository (COR) is an in-memory, object-oriented distributed repository service enabled with system modeling constructs.

  • Data Management Capabilities: COR implements meta-data management as well as data management and supports object creation, deletion, query, indexing, and distribution.
  • High Availability: COR is updated in the active System Controller instance and an exact replica is maintained in the System Controller Standby to provide high availability.
  • Transient Attributes: COR supports transient attributes, allowing for real-time tracking of the latest value of this attribute.

2. Alarm Manager (AM):

The Alarm Manager (AM) is responsible for configuring and handling alarms within the system.

  • It provides support for alarm soaking, masking, alarm hierarchies, and correlation of the alarms before publishing.
  • It stores the information for all the alarms being published until it is cleared.
  • It provides the functionality of reporting the alarm from the south bound entity.

3. Fault Manager (FM):

The Fault Manager (FM) provides a structured approach to managing faults within the system

  • Hierarchical Fault Management: It prioritizes faults to ensure that the critical faults are addressed before the normal or the low-priority faults.
  • FM policy: The actions to be taken on receiving a fault are controlled by the FM policy associated with the faults.

4. Transaction Manager (TM):

The OpenClovis Transaction Manager (TM) is an infrastructure service.

  • It provides the 2-phase commit transaction semantics. Along with this it provides two libraries: the client library and the agent library.
  • Supports re-startable transactions: It tracks the participants and provides ACID semantics to ensure that all the participants are updated properly, or will rollback to previous state.

5. Provisioning Library:

The OpenClovis Provisioning Library manages all aspects of the various hardware and software resources on the system.

  • It keeps track of all the resources the component owns and manages. It also monitors any resources created or deleted during runtime.
  • It propagates the attributes to the corresponding hardware resource as well as fetches the value of the runtime attributes from the component.

6. Mediation Library:

The OpenClovis Mediation Library acts like a gateway between external management agents (like SNMP, CLI, and OpenClovis SAFplus Platform components) and the OpenClovis platform.

  • It translates requests from external management tools (e.g., SNMP, CLI) into actions that the OpenClovis system can execute.
  • The extensible plug-in architecture allows the external management agents to control the configuration and operation of the various managed objects within the system.

7. The OpenClovis Simple Network Management Protocol (SNMP):

The OpenClovis Simple Network Management Protocol (SNMP) sub-agent provides the flexibility to manage both platform and non-platform hardware, OpenClovis Information Model, and the alarms present in the system.

  • It can manage the attributes of an MO that includes a get, set, or notification.

 

Attributes of Managed Objects

Managed Objects (MOs) are the core units of management within OpenClovis, representing the various resources in the system. Each MO encompasses attributes that define its properties and behaviors.

Types of Attributes:

  • Configuration Attribute: These attributes are used to store the configuration information about the managed resource. They are typically writable from management interfaces unless it is marked as initialized.
  • Runtime Attributes: These attributes reflect the dynamic state of a resource and are updated by the Object Implementer (OI). They are not writable from the management station.


End-to-End Manageability

OpenClovis emphasizes end-to-end manageability, ensuring components interact to provide the resource management and fault reporting capability to the SAFplus Platform middleware.

  • Northbound and Southbound Interfaces: The system supports interactions through northbound interfaces (for user interactions) and southbound interfaces (for communication with managed resources).
  • Alarm Reporting and Fault Handling: The system is designed to report failures and manage alarms effectively, ensuring quick responses to issues.


Conclusion

In summary, system management within the OpenClovis context focuses on providing a structured, robust framework for managing the lifecycle, performance, and reliability of both hardware and software components. The integration of various management components ensures that the system can respond to changes and faults effectively, maintaining high availability and performance standards.

Other support, please send email to support@openclovis.org.