>> Suggestion: `zeekcl`, Zeek (Command-Line) CLlient.
>
> "zeekcl" is very close to "zeekctl", which could lead to confusion.
> "zcl" maybe?
>
>> Is use of Python still desirable for other reasons? Otherwise, I
>> lean
>> towards `zeekcl` being C++.
>
> No particular preference from my side, I
On Thu, Jun 18, 2020 at 7:45 AM Vlad Grigorescu wrote:
> My main concern was Broker version incompatibilities between the
> newly-installed zcl, and the running cluster, which I think would be
> addressed by that (i.e. to stop a cluster, you stop the supervisor service on
> the manager, and
On Thu, Jun 18, 2020 at 12:11 AM Robin Sommer wrote:
> For (1), the above applies: we'll rely on standard sysadmin processes
> for updating. That means you'd use "zeekcl" to shutdown the cluster
> processes, then run "yum update" (or whatever), then use "zeekcl"
> again to start things up again.
Thanks Robin, that helps.
On Thu, Jun 18, 2020 at 2:11 AM Robin Sommer wrote:
>
> There are two parts here: (1) deploying the Zeek installation itself,
> and (2) deploying any configuration changes (incl. new Zeek scripts).
>
> For (1), the above applies: we'll rely on standard sysadmin
On Thu, Jun 18, 2020 at 03:32 +, Vlad Grigorescu wrote:
> As a concrete example, what does a cluster upgrade look like?
The idea is to handle this more like other system services: you'll be
in charge of getting the new Zeek version onto all your systems
yourself, using whatever method you
> Suggestion: `zeekcl`, Zeek (Command-Line) CLlient.
"zeekcl" is very close to "zeekctl", which could lead to confusion.
"zcl" maybe?
> Is use of Python still desirable for other reasons? Otherwise, I lean
> towards `zeekcl` being C++.
No particular preference from my side, I can see either.
