[Pacemaker] network interface as a cluster resource (solved with patch)

[Klaus Darilion]

I fixed a bug in the patch.

regards
Klaus

Am 10.03.2011 19:25, schrieb Klaus Darilion:
> Am 08.03.2011 13:32, schrieb Klaus Darilion:
>> Hi!
>>
>> Instead of adding a virtual IP address to an interface
>> (ocf:heartbeat:IPaddr2), how do I manage a physical interface? Are there
>> any special resource scripts?
> 
> Hi!
> 
> I tried to reuse ocf:heartbeat:IPaddr2 to manage and IP address as
> primary IP address on a certain interface. Basically
> ocf:heartbeat:IPaddr2 works, but there are problems if the interface is
> down but the IP address is configured.
>  1. the failure won't be detected
>  2. adding the IP will fail if the IP is already added
> 
> Thus this patch:
> 1. also checks if the interface is up, not only if the IP address is
> configured
> 2. before adding the IP address, it will delete the IP address if the
> address is already configured (on any interface, with any netmask). Thus
> the "add" will always work.
> 
> You might want to add it.
> 
> regards
> Klaus
> 
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch-IPaddr2-check-if-status.txt
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110310/dde4ff22/attachment-0004.txt>