[Bro] bro cluster in containers

[Azoff, Justin S]

> On Jun 4, 2018, at 9:25 AM, Maerz, Stefan A. <maerzsa at ornl.gov> wrote:
> 
> My question is whether or not broctl can be made to gracefully handle the rapid elastic characteristics of container orchestration — for example can I add/remove bro worker nodes/containers without doing a “broctl deploy” or “broctl restart”? I’m sure I can just restart the service, but that seems like a disruptive and non elegant solution.

It wouldn't need to, broctl would not be used at all in this environment.

— 
Justin Azoff