Christian Kreibich a622e28eab Management framework: more resilient node shutdown upon deployment ... When agents had to terminate existing Zeek cluster nodes at the beginning of a new deployment, they so far used their internal state to look up the nodes and fired off requests to the Supervisor to shut these down. This has a problem: when an agent restarts unexpectedly, it has no internal state, and when it then tries to create nodes that already exist, the Supervisor complains with error messages. To avoid this, the agent now tears down all Supervised nodes other than agents and controllers. In order to do so, it first needs to query the Supervisor for the current node status, which means there are now two such status requests: one upon deployment, and one during get_nodes requests. In order to disambiguate these contexts in the SupervisorControl::status_request/response transactions, we use the finish() callback in the corresponding request state to continue execution as needed.		2022-06-21 17:22:45 -07:00
..
__load__.zeek	Management framework: enable stdout/stderr reporting	2022-05-31 12:55:21 -07:00
api.zeek	Management framework: agents now skip re-deployment of current config	2022-06-21 17:22:45 -07:00
boot.zeek	Management framework: switch default network visibilities	2022-06-08 15:00:19 -07:00
config.zeek	Management framework: make agents support zeek-archiver invocations	2022-06-14 12:32:17 -07:00
main.zeek	Management framework: more resilient node shutdown upon deployment	2022-06-21 17:22:45 -07:00