...
DCAE MOD is composed of a mix of components developed by AT&T the ONAP team and other components taken from the Apache Nifi project and modified for appropriate use.
...
Following is MOD internal component architecture
Onboarding API
It is a component developed by AT&T used to onboard models/components/microservices (spec files) into DCAE MOD.
genprocessor
It has been developed by AT&T in Java. This project is This is a Java project and offers a tool to experiment with generating generate a Nifi Processor POJO from a DCAE component spec.
...
This component taken from the Apache Nifi project, is a REST API that provides an interface to a registry with operations for saving, versioning, reading NiFi flows and components.
Distributor API
It is a component developed by AT&T using written in the Flask framework in Python. It is a HTTP API to manage distribution targets for DCAE design. Distribution targets are DCAE runtime environments that have been registered and are enabled to accept flow design changes that are to be orchestrated in that environment.
...
For more information on how some of the main NiFi concepts map to FBP, check out https://nifi.apache.org/docs/nifi-docs/html/overview.html
Runtime API
It is a component developed by AT&T written in Java’s Spring Boot framework. It is a HTTP API to support runtime environment for DCAE-MOD. It has two major functionalities:
- It accepts changes on the flow-graph via fbp protocol
- It generates and distributes blueprints based on the change made on the flow-graph
Blueprint Generator
Developed by AT&T, this tool allows the user to create a blueprint from a component spec json fileThis tool allows the user to create a blueprint from a component spec json file. This tool is used by the runtime api.
...