Dear list,
while working with Icinga2, I noticed several characteristics regarding
the Icinga2 API and the config sync via API.
A short introduction to a setup:
2 masters, sharing the zone "master"
3 satellite zones with 2 or 1 satellite with parent zone "master"
New configuration is deployed in the following ways:
(1) Objects via HTTPS POST to master:5665
(2) Directly creating new files at master:/etc/zones.d/satellite1/
(3) Via Director
Sometimes I noticed that the relevant satellite server performs no
Icinga2 reload or restart.
We assume:
- restart/reload on getting a config package (2)(3)
- no restart/reload on getting a config object (1)
But on the other hand, sometimes there is no reload/restart on changing
Config Packages via editing files on the master (2)
Is there a golden rule when Icinga2 performs a reload or restart (or
none of them) after receiving new configuration?
Best regards
Tilo
--
Tilo Mey
open*i GmbH
Talstraße 41 70188 Stuttgart Germany
tel +49-711-953370-77 fax +49-711-953370-99
www.openinfrastructure.de
Geschäftsführer Tilo Mey
Amtsgericht Stuttgart, HRB 729287, Ust-IdNr DE264295269
Volksbank Stuttgart EG, BIC VOBADESS, IBAN DE75600901000340001003
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
