On Thu, Mar 13, 2014 at 02:47:08AM -0400, Martin Perina wrote:
Hi,
we want to integrate support for fence_kdump into oVirt project. Marek Grac pointed me to kexec-tools-2.0.4-23 which contains automatic configuration of fence_kdump from Pacemaker config.
Can you please explain how oVirt cluster is different from regular cluster. And why pacemaker is not usable.
Unfortunately for us, this support is tightly bound to Pacemaker, so I created attached patch,
Why pacemaker is not usable with Ovirt.
[..]
Behavior with this patch
when running 'kdumpctl restart' kdump detect if fence_kdump_send binary is installed and if so, it tries to:
a) It tries to detect is cluster is configured ('pcs' command is available). If so, it creates needed config files as described above in steps 1a) and 1b) b) If cluster is not configured, it tries to detect if /etc/sysconfig/fence_kdump and /etc/sysconfig/fence_kdump_nodes exist. If so, fence_kdump is marked as successfully configured and kdump continues with steps 1c) and 1d)
Who will generate /etc/sysconfig/fence_kudmp and how?
Thanks Vivek