> On 01 Dec 2015, at 14:26, Jayapandian Ponraj <pandian...@gmail.com> wrote: > > Hi, > > I have been trying to setup an architecture where the configuration of the > nodes/servers is in the servers themselves and then propagated to the master > internally by icinga. I have a few questions in this regard. > > 1) Is there a way to auto accept the config from satellite nodes without > running `icinga2 node update-config` on the master? > If yes can you point me in the right direction. >
No. > 2) Is there any kind of auth mechanisms for satellite nodes, similar to the > auth mechanisms in place for API requests. SSL certificates and common name (how that works, see the “cluster naming convention” chapter in the docs). > > 3) Is there any client which can read my host and service object and then > transform them into API queries. Am looking for some client which can run as > a daemon/periodically, which reads local config and pushes them out to the > master via API calls. That doesn’t make sense to me. Why bother reading config files if you could fetch them from your own backend? Kind regards, Michael > > Thanks in advance > > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users -- Michael Friedrich, DI (FH) Senior Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | michael.friedr...@netways.de ** OSDC 2016 - April - netways.de/osdc ** ** OSBConf 2016 - September - osbconf.org ** _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
