Component’s Interactions Clause Samples

Component’s Interactions. The Security Enablers component interacts with the following component of the RAINBOW platform. Policy Editor Policy Editor compiles the set of attestation policies, including configuration properties to be verified during deployment and operation of Interacting Component Description cloud-native components. These will be deployed and enforced through the Deployment Manage. Deployment Manager It deploys and enforces the attestation policies to be verified by the RAINBOW security and trust enablers.

Component’s Interactions. The Resource and Application-level Monitoring component interacts with the following component of the RAINBOW platform. Orchestration Lifecycle Manager It provides monitoring configuration (e.g., monitoring metrics, metrics collection periodicity) and knowledge about the topology of the underlying infrastructure and application services. The monitoring data is published to the High-Performance Queue component and can be accessed by other components of the RAINBOW platform (e.g., Analytics Engine, Storage Manager).

Component’s Interactions. The Policy Editor component interacts with the following component.

Component’s Interactions. The Service Graph Editor component interacts with the following component. Service Graph Repository Repository that exposes an API that manages the application graphs and their constraints.

Component’s Interactions. The mesh routing protocol stack is in essence a peer-to-peer component. As such it can communicate with any node in the fog deployment in order to perform neighbour- identification, overlay establishment, cluster-head election and path discovery. It should be clarified that the communication of each node with the centralized orchestration entity is achieved through the cluster-head.

Component’s Interactions. The orchestration Lifecycle Manager component interacts with the following components. Deployment Manager Deployment manager triggers a new instance of the Orchestration Loop and receives all the necessary information in order to start the deployment and maintenance procedure. Orchestrator Repository It saves and fetches the current and previous orchestration loop states respectively. Resource and Application-level Monitoring It provides to the Orchestrator the necessary resource and application level monitoring metrics. Resource Manager It supplies information about the resources that are currently available/allocated on each node. This is crucial for determining the appropriate node for scheduling.

Component’s Interactions. The resource manager interacts mainly with two other RAINBOW components: Resource and application-level monitoring It supplies current resource usage data. Orchestration Lifecycle Manager It contains the scheduler, which is responsible for selecting the appropriate nodes for deploying the workload, based on the available and allocated resources reported by the resource manager.

Component’s Interactions. The Analytics Engine interacts with the following modules of the RAINBOW platform: Resource Manager The Analytics Engine communicates with the Resource Manager for two reasons. The first one is to retrieve information about the underlying infrastructure, which includes metadata about the resource capacities and capabilities of each fog node (e.g., ARM-v7 processor, 16 GB memory, GPU-accelerated). This information is used by the Analytics Engine module for finding a close to optimal execution plan of the analytics on the underlying resources. The second reason is to ask the resource manager to instantiate the necessary analytic agents that process the analytic tasks. Resource and Application-level Monitoring The Analytics Engine communicates with the Resource and Application-level Monitoring for retrieving raw monitoring data to compute analytics results and also publish the query results for other RAINBOW components. It also retrieves metadata about metrics structure, size, partitions and their location. These data are processed by the Analytics Engine to generate an efficient plan of execution. The second reason for communicating with the Data Storage and Sharing module is to store or update the analytic results which can be shared with other applications. The functionalities of the Analytics Engine will be offered through an API which can be accessed by other RAINBOW components (e.g., Resource Orchestrator) through the RAINBOW platform. The API will provide a uniform way for creating, editing, deleting and updating analytics queries, and access to analytics query results.

Component’s Interactions. The Deployment Manager component interacts with the following component. Pre-Deployment Constraint Solver Connects to the Deployment Manager to receive and solve the hard and soft constraints introduced from the applications and their components Orchestration Lifecycle Manager Receives from the Deployment Manager all the necessary data and settings for its deployment. The data are provided by the Orchestrator Repository.