[ClusterLabs] FEEDBACK WANTED: possible deprecation of nagios-class resources

[Ken Gaillot]

Hi,

Thanks for the feedback, it's very helpful to hear about a real-world
use case.

At this point (and for any remaining 2.1 releases), the only effect is
a warning in the logs when nagios resources are configured. Eventually
(probably next year), there will be a 2.2.0 or 3.0.0 release, and we
can consider dropping support then.

The idea was that since nagios resources were first introduced, better
solutions (such as Pacemaker Remote and bundles) have emerged for
particular use cases. Being able to reduce how much code needs to be
maintained can be a big help to developers, so if the remaining use
cases aren't widely needed, it can be worthwhile to drop support.

The main use case where nagios resources can still be helpful is (as
you mentioned) when a VM or container image can't be modified.

The alternative would be to write a custom OCF agent for the image.
Basically you could take the usual OCF agent (VirtualDomain, docker,
podman, etc.) and change the monitor action to do whatever you want. If
you have an existing nagios check, you could even just call that from
the monitor action, so it would be just a few lines of coding.

If custom agents are not convenient enough, we could consider "un-
deprecating" nagios resources if there is demand to keep them.

On Fri, 2023-06-30 at 10:51 +0800, Mr.R via Users wrote:
> Hi Ken Gaillot
> 
>     There are a few questions about nagios,
>     In pacemaker-2.1.6, the nagios-class resource may be deprecated.
> Is it now or phased out? In some cases, if the machine being
> monitored cannot be modified, nagios can solve the problem.  Is it
> deprecated because there are fewer application scenarios? and will be
> there an alternative resource template?
> 
>     thanks,
-- 
Ken Gaillot <kgaillot at redhat.com>