https://github.com/nmsa/tma-framework-k

Component K - Trustworthiness Monitoring & Assessment Framework
https://github.com/nmsa/tma-framework-k

knowledge measurements trustworthiness

Last synced: about 1 year ago
JSON representation

Component K - Trustworthiness Monitoring & Assessment Framework

• Host: GitHub
• URL: https://github.com/nmsa/tma-framework-k
• Owner: nmsa
• License: apache-2.0
• Created: 2018-04-09T16:22:08.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2022-12-16T14:50:28.000Z (over 3 years ago)
• Last Synced: 2025-06-26T15:51:57.347Z (about 1 year ago)
• Topics: knowledge, measurements, trustworthiness
• Language: Java
• Size: 410 KB
• Stars: 0
• Watchers: 5
• Forks: 5
• Open Issues: 14
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Knowledge Component @ TMA Framework

The `TMA_Knowledge` component stores measurements data, and stores and manages information about the application architecture, resources and assets available and their possible adaptations.

The star schema envisaged for the ATMOSPHERE TMA framework is shown below. The fact table `Data` contains the basic numerical facts obtained from the readouts collected by the probes and the dimensions include all the different perspectives needed to characterize those numerical facts. 

![Data model to be used in knowledge for data related to trustworthiness metrics](https://github.com/eubr-atmosphere/tma-framework/blob/master/architecture/diagrams/TMA-K_DataModel/TMAF-K_ConceptualDataModel_Measurements.jpg)

The dimensions are as follows: 

* `resource` -- describes the resources and assets that constitute the deployed system and may include further information)

* `probe` -- stores information about all the probes in the system

* `description` -- refers to the types of measurements/events collected (e.g. execution time, memory allocated, CPU in use, response time) and constitutes the monitoring system vocabulary

* `time` -- describes the moment when each observation was collected

Each row on the fact table is linked to one (and only one) row in each dimension.

## Registration of Actuators

The `TMA_Knowledge` component provides an interface to the administrator of the system to add a new actuator. It will allow the TMA Framework to know which actuators can actuate on the system. Additionally, the administrator can also register all the possible actions through a different interface.

![Knowledge Usage Sequence Diagram](https://github.com/eubr-atmosphere/tma-framework/blob/master/architecture/diagrams/TMA-E/TMA-E_Registration.jpg)

Initially, the administrator has to generate a public key to each actuator that will be used to authenticate when performing the adaptation operations. This has to be done only once, and it will be used to TMA to interact with the system.

Each administrator also needs to register each actuator through an authentication synchronous message, in which he/she will receive both the credentials and the public key. All communication is performed over REST services. 

The administrator needs to register all actions that can be performed by an actuator. This will allow TMA to decide what to do based on the list of available operations.

### Message Format for Actuator Registration

The message to be submitted to the `TMA_Knowledge` follow the `JSON` schema specified in [tma-k_schema](interface/atmosphere_tma-k_schema.json), which is currently in the version `0.1`. This should be used to notify TMA about the existence of the Actuator.

The figure below presents a representation of this schema, which is also explained below.

*![Knowledge Register Schema](interface/tma-k_register.png)Format of the data to be provided to the knowledge component.*

Each message includes:

* `address` -- an objet with the information about the ActuatorAPI

	* `url` --- the URL of where the operations are available. All actions will be available through this URL, which will direct the actuation to the proper operation

* `PubKey` -- generated once by the ActuatorAPI

### Message Format for Actions Registration

Additional, the following message should be sent to `TMA_Knowledge` to store all the possible actions. It follows the `JSON` schema specified in [tma-k_schema-actions](interface/atmosphere_tma-k_schema-actions.json), which is currently in the version `0.2`.

The figure below presents a representation of this schema, which is also explained below.

*![Knowledge Register Schema](interface/tma-k_actions.png)Format of the data to be provided to the knowledge component to add the actions.*

Each message includes:

* `actions` -- a list of actions provided by the Actuator

	* `action` -- name of the action to be performed. This will be used to inform the ActuatorAPI about which action to be performed

	* `resourceId` -- identifies the resource in which the adaptation can be performed

	* `configuration` -- list of expected attributes to execute the operation

		* `key` -- name of the configuration attribute

		* `value` -- value of the configuration attribute

One example can be seen [here](interface/atmosphere_tma-k_actions-example.json).