pping.conf lets you spread the pping-task over several hosts via the use of groups_included and groups_excluded. We use this feature because we have some hosts only reachable through a tunnel.
The groups_included works fine: Our second pping-host only pings the host in the device group specified. But our main NAV host still pings all hosts, even though the exact same device group is listed in groups_excluded.
--Ingeborg
On Tue, 23 May 2023 09:24:41 +0200 (1 day, 23 hours, 7 minutes ago) Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
The groups_included works fine: Our second pping-host only pings the host in the device group specified. But our main NAV host still pings all hosts, even though the exact same device group is listed in groups_excluded.
I have no reason to believe it shouldn't work. The feature was contributed by the University of Oslo, and as far as I know, they are actively using it themselves. Cc: to Jan Sigurd, maybe he can comment.
That being said, the code that actually includes/excludes devices based on this setting has very poor test coverage: https://app.codecov.io/gh/Uninett/nav/blob/master/python/nav/ipdevpoll/datal...
-
Ingeborg Hellemo -
Morten Brekkevold