You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Bryan Rosander (JIRA)" <ji...@apache.org> on 2017/04/20 20:22:04 UTC

[jira] [Assigned] (MINIFI-272) Hierarchical C2 support

     [ https://issues.apache.org/jira/browse/MINIFI-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Rosander reassigned MINIFI-272:
-------------------------------------

    Assignee: Bryan Rosander

> Hierarchical C2 support
> -----------------------
>
>                 Key: MINIFI-272
>                 URL: https://issues.apache.org/jira/browse/MINIFI-272
>             Project: Apache NiFi MiNiFi
>          Issue Type: New Feature
>            Reporter: Bryan Rosander
>            Assignee: Bryan Rosander
>         Attachments: c2-integration-test.png
>
>
> MINIFI-238 introduced a C2 server that MiNiFi agents can poll for new configuration files.  In order for this to be useful on a larger scale, we'll need a way to structure the servers such that they are reachable by the edge nodes while still having a central place from which to distribute changed configuration.
> To that end, a delegating configuration provider should allow for arbitrary hierarchical structures of C2 servers.
> A docker-compose integration test that simulates several different possible network and delegation configurations will help to prove out the concept.
> Attached is an image of the integration test topology.  There is a central cluster network where the authoritative C2 server resides.  There is a node able to connect directly to it in the edge1 network.  There is a delegating C2 server that bridges the cluster and edge2 networks.  The edge2 server listens for http requests and delegates over https.  There is a node on the edge3 network that requests directory from the authoritative C2 server through a squid proxy.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)