The current model for Bus Controller support of Mirror Maker assumes a single provisioning API which is used to start/stop MM, and manage the associated whitelist.  Furthermore, topics have a flag which allows the designer to indicate the direction of message replication between 2 or more MR clusters.

A kubernetes-style deployment of MM will likely introduce a pod for each replication pair of kafka instances, to be deployed near the target instance, and provisioned via a ConfigMap.

So, Bus Controller needs to be modified to support the ONAP deployment model, and the ECOMP deployment model (until ECOMP DMaaP is deployed in kubernetes).