...
High Level Architecture
OTI Architecture
OTI Data Flow via API (option 1)
OTI Data Flow via DMaaP-MR (option 2)
OTI Components
- OTI-event-proc can:
-Subscribe topology events ( vendor-based-format or common-format-event) from DMaaP-MR.
-Parse and process the event based on event-handler-template defined in Policy.
-Look up the xNF associated data collection tasks defined in policy.
-Generate ‘dcae-collection-event’ that includes xNF instance topology and associated collection tasks. The ‘dcae-collection-event’ will be in VES like standard format.
-POST the ‘dcae-collection-event’ to OTI-Handler via API (Option1). Or publish 'dcae-collection-event' to DMaaP-MR (option 2).
-Store the ‘dcae-collection-event’ into ONAP-PG DB.
-
- OTI-handler can POST/Dispatch the ‘dcae-collection-event’ to a defined Kubernetes Cluster in a DCAE region based on xNF location. There is a LB in each K8s cluster sends this xNF collection request to a corresponding collector mS based on the LB algorithm.
This will be useful for legacy microservices dependent on notification on OTI configuration change.
DCAE MS Impact
<include details for steps/interface agreement that MS should follow to leverage OTI feature>
...