Hi Peter,
thanks again for your advice.
I agree with you: Putting sensitive data into host variables is one of
the best ways. I would do so, however, in this specific project, it
won't be possible (please don't ask for the reasons).
Using the director is a very elegant approach, and indeed t
Hi Valentin,
> - All agents/clients could/will receive this information due to config
> synchronization, no matter if they need these definitions or not.
correct. One might consider that an issue, depending on how many configurations
are affected.
My personal approach is to put as much of th
Hi Peter,
you are referring to one of two scenarios in my e-mail:
Placing configuration which affects multiple agents in all zones.
While I realize that global zones are perfect places to put such
configuration in, doing so comes with several disadvantages:
- All agents/clients could/will rec
Hi Valentin,
> Now, let's say I want to define a service which affects multiple clients in
> all zones. Those services need to be executed by the satellites.
> Where would you define this apply rule? In the global zone on the master?
> This would be "bad practice" IMHO, but I don't know any oth
Hi,
I am just wondering if anybody would have some ideas to share.
Best regards
Valentin
On 20.02.2017 19:03, Valentin Höbel wrote:
Dear list,
I built a demo setup with one master, several satellites and several
"clients" which are checked by the satellites. All satellites are
located withi
Dear list,
I built a demo setup with one master, several satellites and several
"clients" which are checked by the satellites. All satellites are
located within their own zone.
Master zone: "master"
Satellite zones: "dc1", "dc2", "dc3"
Global zone: "global-config"
The "clients" are located i
