Thanks Honza. I have raised these on both upstream projects.
I will leave upto implementer how best this can be done, considering the
technical limitations you mentioned.
https://github.com/corosync/corosync-qdevice/issues/13
https://github.com/ClusterLabs/booth/issues/99
Thanks,
Rohit
On Thu,
Sorry, followed too much into the intermixing of two rather unrelated
things, when failure occurs and when quorum is lost. I've meant to
dedicate the comment solely to the latter, but managed to cross that
line. Corrections below:
On 8/13/20 12:32 PM, clusterl...@t.poki.me wrote:
wanted to
Hello,
wanted to point out one thing that occurred to me when thinking about
the paragraph below.
On 8/12/20 8:57 PM, Ken Gaillot wrote:
Similarly, Pacemaker offers the cluster-wide "no-quorum-policy" option
to specify what happens to resources when quorum is lost (the default
being to stop
Probably I didn't configure pacemaker resource properly, now it's OK.
---
crm configure show remote-db8-ca-3a-69-60-f4
node remote-db8-ca-3a-69-60-f4:remote \
attributes OpenStack-role=compute standby=off
primitive remote-db8-ca-3a-69-60-f4 ocf:pacemaker:remote \
params
Hi, guys,
I'm running SLES12 sp3 and pacemaker-remote-1.1.16-4.8.x86_64, a few
months ago, compute nodes of openstack are running well. But today when I
setup a new compute node, it's said,"
-
Aug 13 16:31:04 [43122] db8-ca-3a-69-60-f4 pacemaker_remoted: notice:
Hi Rohit,
Hi Honza,
Thanks for your reply. Please find the attached image below:
[image: image.png]
Yes, I am talking about pacemaker alerts only.
Please find my suggestions/requirements below:
*Booth:*
1. Node5 booth-arbitrator should be able to give event when any of the
booth node joins
Hi Honza,
Thanks for your reply. Please find the attached image below:
[image: image.png]
Yes, I am talking about pacemaker alerts only.
Please find my suggestions/requirements below:
*Booth:*
1. Node5 booth-arbitrator should be able to give event when any of the
booth node joins or leaves.
