-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updating Database Model (Quality Model, Adapatation Plan) (#7)
* Data models for Metrics. * Fixing the type of the primary key of the Quality Model * JSON files with the formats of the messages * Updating diagrams of the data models (metrics)
- Loading branch information
Showing
28 changed files
with
74 additions
and
4 deletions.
There are no files selected for viewing
Binary file not shown.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+25.9 KB
architecture/diagrams/TMA-K_DataModel/TMAF-K_ConceptualDataModel_Actuators.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+34.8 KB
architecture/diagrams/TMA-K_DataModel/TMAF-K_ConceptualDataModel_Measurements.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+62.8 KB
architecture/diagrams/TMA-K_DataModel/TMAF-K_ConceptualDataModel_Metrics.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+47.2 KB
architecture/diagrams/TMA-K_DataModel/TMAF-K_ConceptualDataModel_Metrics.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+54.1 KB
architecture/diagrams/TMA-K_DataModel/TMAF-K_ConceptualDataModel_Planning.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+50.9 KB
architecture/diagrams/TMA-K_DataModel/TMAF-K_ConceptualDataModel_Planning.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Trustworthiness Monitoring & Assessment Framework | ||
|
||
The communication between the components from the `MAPE-K` is done mainly by the `FaultTolerantQueue`, according to the [figure below](../architecture/diagrams/TMA-Platform_Detailed_Architecture.jpg). | ||
|
||
*![High level architecture of TMA Framework](../architecture/diagrams/TMA-Platform_Detailed_Architecture.jpg) Architecture and interfaces of the trustworthiness platform.* | ||
|
||
The [`TMA_Analyze`](#tma_analyze) component is responsible for continuously listening to the `TMA_Knowledge` microservice, calculate the trustworthiness scores and, store them on the database. An item is added to the `planning` queue from the `FaultTolerantQueue` in order to the [`TMA_Planning`](#tma_planning) starts checking the rules. The format of the message is a [JSON](interface/atmosphere_tma-p_schema.json) according to the image below: | ||
|
||
*![JSON Format read by TMA_Planning](interface/atmosphere_tma-p_schema.png) Format of the JSON message to be read by the TMA_Planning component* | ||
|
||
The `metricId` indicates that a new value for the corresponding metric was calculated and stored in the database, in the moment stored on `timestamp`. | ||
|
||
The [`TMA_Planning`](#tma_planning) microservice is responsible for executing the verification rules that will produce a set of adaptations that will be consolidated in an "adaptation plan" to achieve the required goals, or to recover the desired levels of trustworthiness. This is done by continuously polling the messages from the `planning` queue. If an adaptation is needed, an "adaptation plan" is stored in the database with the set of actions. | ||
|
||
*![Conceptual Data Model used by the Planning component](../architecture/diagrams/TMA-K_DataModel/TMAF-K_ConceptualDataModel_Planning.jpg) Conceptual Data Model used by the Planning component.* | ||
|
||
An adaptation plan is stored in the `Plan` table, and it is always related to the `MetricData` that dispatched the adapation. The set of actions and the order of execution is stored in the `ActionPlan` table, and it is related to an `Action`, which will be performed by the correspondent `Actuator`. In case the actions need parameters, their values are stored in the `ConfigurationData` table. | ||
|
||
The communication of [`TMA_Planning`](#tma_planning) is done by the `execute` queue, which will receive a [JSON](interface/atmosphere_tma-e_schema.json) message with the plan identifier. | ||
|
||
*![JSON Format read by TMA_Execute](interface/atmosphere_tma-e_schema.png) Format of the JSON message to be read by the TMA_Execute component* | ||
|
||
Finally, the [`TMA_Execute`](#tma_execute) microservice runs the adaptation plan using the deployed actuators on the target layers. This component is continuously polling the messages from the `execute` queue. When a plan is added, the list of actions is obtained from the [`TMA_Knowledge`](#tma_knowledge), with the order of execution and the parameters values. | ||
|
||
(nmsa: CHECK IF THIS CONTENT SHOULD REPLACE THE SECTION FROM THE MAIN PAGE) | ||
|
||
(REVIEW THE LINKS TO THE SUB-MODULES) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
{ | ||
"title": "tma-e_schema_0_1", | ||
"$id": "http://atmosphere-eubrazil.eu/tma-e_schema_v0.1.json", | ||
"$schema": "http://json-schema.org/draft-07/schema#", | ||
"type": "object", | ||
"properties": { | ||
"planId": { | ||
"$id": "/properties/planId", | ||
"type": "integer", | ||
"default": -1, | ||
"minimum": 0 | ||
} | ||
}, | ||
"required": [ | ||
"planId" | ||
] | ||
} | ||
|
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
{ | ||
"title": "tma-ac_schema_0_1", | ||
|
||
"$id": "http://atmosphere-eubrazil.eu/tma-_aschema_v0.1.json", | ||
"$schema": "http://json-schema.org/draft-07/schema#", | ||
"type": "object", | ||
"properties": { | ||
"metricId": { | ||
"$id": "/properties/metricId", | ||
"type": "integer", | ||
"default": -1, | ||
"minimum": 0 | ||
}, | ||
"timestamp": { | ||
"$id": "/properties/timestamp", | ||
"type": "integer", | ||
"default": -1, | ||
"minimum": 0 | ||
} | ||
}, | ||
"required": [ | ||
"metricId", | ||
"timestamp" | ||
] | ||
} |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Submodule tma-framework-a
updated
42 files
Submodule tma-framework-e
updated
42 files
Submodule tma-framework-k
updated
35 files
Submodule tma-framework-m
updated
47 files