[Pacemaker] Fixed! - Re: Problem with dual-PDU fencing node with redundant PSUs

[Lars Marowsky-Bree]

On 2013-06-28T10:20:56, Digimer <lists at alteeve.ca> wrote:

> >> primitive fence_n01_psu1_off stonith:fence_apc_snmp \
> >>         params ipaddr="an-p01" pcmk_reboot_action="off" port="1"
> >> pcmk_host_list="an-c03n01.alteeve.ca"
> >> primitive fence_n01_psu1_on stonith:fence_apc_snmp \
> >>         params ipaddr="an-p01" pcmk_reboot_action="on" port="1"
> >> pcmk_host_list="an-c03n01.alteeve.ca"
> > 
> > So every device twice, including location constraints? I see potential
> > for optimization by improving how the fence code handles this ... That's
> > abhorrently complex. (And I'm not sure the 'action' parameter ought to
> > be overwritten.)
> 
> Andrew said yesterday that this will no longer be the case as of 1.1.10.
> From then on, 'action="..."' will be honoured.

But that will not help you. Because you need to *still* have two
separate fence actions for this fence topology thing to work, so a
global action won't help; or am I missin something?

> > Glad you got it working, though.
> 
> I've debated writing a "fence_apc_multi" that takes "reboot" and two or
> more PDU addresses/ports and does the break out for you.

That is so ugly, please, no :-(

> This would make the pacemaker config a lot cleaner, but that solution
> would work for APC agent only. A "fix" in stonith would be portable to
> all agents.

Exactly.


Regards,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde