Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

WHY a flow matrix?


Numerous components are embedded in the ONAP architecture. 

...

The main objective is then to authorize only pre configured flows on specific ports.


  • Inter-components flows

All flows defined between components defined as project by ONAP.

...

The flows remain within the components .This would - ONAP project.

For instance for DCAE component, a flow between the collector (VES) sub_component and DCAE_lifecycle_manager.


WHEN a flow matrix?

A flow matrix should be established for each ONAP project.

It should be reviewd at each major release of the component.


HOW a flow matrix?

This may be too complicated to address all flows for a given project.

As a first step, external flows should be considered, and then the 2 other categories.

This file enables to provide information for each flow:


ParameterValue
namename of the ONAP project e.g. DCAE.
sub_components:
        - name:
real name of the sub component e.g. dcae-snmptrap-collector
external_server_side:in external server side list only ingress (external -> ONAP) traffic
type:nodePort
external_communication:N/A





























 - : 
#
#


- description: SNMP trap
id: dcae_1
#which component initiates the communication.
communication_initiator: any component sending SNMP either internally to ONAP platform or externally e.g. xNF.
#which component is the dest of the communication.
communication_receipt: N/A
#protocol: at least level 4 or higher, to be specified if applicable.
protocol: snmp #to be specified if applicable
version: #to be specified if applicable
exposed_pod_port: 6162 #to be specified if applicable
exposed_port: 30470 #to be specified if applicable
encryption: none
#data_exchanged: specifies the file format, the main exchanged information.
data_exchanged: snmp trap information
#to specify whether the component hosts a TLS sever or a TLS client (yes or no), if applicable.
tls_server: N/A
tls_client: N/A
flow_direction: incoming