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.
Unfortunately for us, this support is tightly bound to Pacemaker, so I created attached
patch,
which adds support for manual configuration of fence_kdump:
1) Current status without this patch (kexec-tools-2.0.4-23)
- when running 'kdumpctl restart' kdump detects if fence_kdump_send command
is installed
and if so, it tries to:
a) Create /etc/sysconfig/fence_kdump file with command line parameters for
fence_kdump_send.
These parameters are extracted from cluster configuration using 'pcs
cluster' command
b) Create /etc/fence_kdump_nodes file with list of hosts to send fence_kdump
notification to.
These hosts are also extracted from cluster configuration using 'pcs
cluster' command
c) If these two files are successfully created, kdump tries to configure network
to be able
to reach all hosts defined in /etc/fence_kdump_nodes
d) Install these two config files into kdump's kernel initramfs
2) 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)
Is it possible to integrate such patch into kexec-tools RPM?
We would like to integrate fence_kdump support into oVirt 3.5 which should be released in
May,
so before this to happen, we need kexec-tools RPM with this patch to be available for RHEL
6 and
Fedora 19/20.
Thanks
Martin Perina