Hello,
adding remote compute with:
pcs resource create computenode1 remote server=10.102.184.91
instead of:
pcs resource create computenode1 ocf:pacemaker:remote reconnect_interval=60
op monitor interval=20
SOLVES the issue when unexpected compute node reboot happens.
It returns online and
Hello again, meanwile I was connected to my lab, I read some documentation.
Adding remote compute with the following command:
pcs resource create computenode1 remote server=10.102.184.91
pcs property set --node computenode1 osprole=compute
instead of:
pcs resource create compute-1
Hello, this morning I connected to my office by remote to send information
you requested.
Attached here there are:
status: results of command pcs status
resources: results of command pcs resources
hosts: controllers /etc/hosts where I added aliases for compute nodes every
time I rebooted a
Hi,
This might not what exactly you are looking for... but... you may extend this.
In Masakari [0], we use pacemaker-remote in masakari-monitors[1] to
monitor node failures.
In [1], there is hostmonitor.sh, which will gonna deprecate in next
cycle, but straightforward way to do this.
[0]
