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 works
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 ocf:pacemake
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 compute
Hello and thanks very much for your suggestions. On monday I will send you
my pacemaker configuration.
At this time I monitor nova-compute systemd resource rather than ocf
resource. Nova compute systemd resource is monitored very well when the
pacemaker remote compute node is marked online in the
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] https
Thanks Curtis.
I have already tried "pcs resource cleanup" but it cleans fine all
resources but not remote nodes.
Anycase on monday I'll send what you requested.
Regards
Ignazio
Il 13/Mag/2017 14:27, "Curtis" ha scritto:
On Fri, May 12, 2017 at 10:23 PM, Ignazio Cassano
wrote:
> Hi Curtis, at t
On Fri, May 12, 2017 at 10:23 PM, Ignazio Cassano
wrote:
> Hi Curtis, at this time I am using remote pacemaker only for controlli ng
> openstack services on compute nodes (neutron openvswitch-agent,
> nova-compute, ceilometer compute). I wrote my own ansible playbooks to
> install and configure al
Hi Curtis, at this time I am using remote pacemaker only for controlli ng
openstack services on compute nodes (neutron openvswitch-agent,
nova-compute, ceilometer compute). I wrote my own ansible playbooks to
install and configure all components.
Second step could be expand it for vm high availabi
