----- Original Message -----
From: "Vivek Goyal" <vgoyal(a)redhat.com>
To: "Marek Grac" <mgrac(a)redhat.com>
Cc: "Martin Perina" <mperina(a)redhat.com>, kexec(a)lists.fedoraproject.org
Sent: Monday, March 31, 2014 11:22:03 PM
Subject: Re: [PATCH 1/6] fence_kdump for generic clusters v3: Rename FENCE_KDUMP_CONFIG
On Mon, Mar 31, 2014 at 10:55:32AM +0200, Marek Grac wrote:
> On 03/28/2014 06:11 PM, Vivek Goyal wrote:
> >>So in following patches, I will introduce new options in kdump.conf. With
> >>patches kdump will not use /etc/fence_kdump_nodes file (this will be
> >>with fence_kdump_nodes option in kdump.conf). But not to break Pacemaker
> >>during Pacemaker fence_kdump configuration content of
> >>will be read and store into fence_kdump_args in kdump.conf in initial
> >Marek, are you particular about maintaining this file. No package owns
> >this file so asking user to create this file and provide options here
> >sounds bad.
> >Do you mind if we change it and ask user to specify options in
> >/etc/kdump.conf using fence_kdump_args options.
> Fence agents do not use configuration files at all and they are not
> dependent on pacemaker or any other cluster software. So this change
> will not have any impact on them. imho the pacemaker team is the one
> who should answer your questions.
Would you know who should I talk to in pacemaker team?
Marek send me those names from Pacemaker team: Andrew Beekhof or David Vossel, I will
send them email today.