Target release
Epic
Document statusDRAFT
Document owner


Designer
Developers
QA

Goals

  • The hope is that we can standardize on one approach for both minifi and minifi-cpp.
  • Ideally that is the C2 Protocol with a shared/common server that is compatible with nifi, minifi, and minifi-cpp.

Background and strategic fit

per Kevin Doran

Here is a quick and dirty summary of the current state of things:

Method of deploying flownifi-minifi (java)nifi-minifi-cpp
manually author config.yml✔✔
nifi template xml -> minifi-toolkit -> config.yml✔❌
change ingestor✔ multiple impls❌
C2 Protocol❌✔

C2 Server Implementations that exist in Apache (i.e., not including any community or vendor solutions):


We would add a new C2 server implementation for this protocol which could be shared by nifi, minifi, and minifi-cpp, to align all these different flow runtime engines with the same C2 capabilities.

Assumptions

Requirements

#TitleUser StoryImportanceNotes
1
2



User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing