[ClusterLabs] Q: Is there any plan for pcs to support corosync-notifyd?

[Ken Gaillot]

On Tue, 2021-03-16 at 13:24 +0100, damiano giuliani wrote:
> Could be an idea to  let your cluster start it on all your nodes
> 
> Br

That does sound like a good idea. That way the cluster can monitor it
(with the equivalent of systemctl status) and restart it if needed, and
constraints can be used if some other resource depends on it. Something
like:

pcs resource create notifyd systemd:corosync-notifyd clone

> On Tue, 16 Mar 2021, 09:58 井上和徳, <kazunori_inoue at newson.co.jp> wrote:
> > Hi!
> > 
> > Cluster (corosync and pacemaker) can be started with pcs,
> > but corosync-notifyd needs to be started separately with systemctl,
> > which is not easy to use.
> > 
> > # pcs cluster start --all
> > rhel83-1: Starting Cluster...
> > rhel83-2: Starting Cluster...
> > rhel83-3: Starting Cluster...
> > # ssh rhel83-1 systemctl start corosync-notifyd
> > # ssh rhel83-2 systemctl start corosync-notifyd
> > # ssh rhel83-3 systemctl start corosync-notifyd
> > 
> > Is there any plan for pcs to support corosync-notifyd?
> > 
> > Regards,
> > Kazunori INOUE
-- 
Ken Gaillot <kgaillot at redhat.com>