IPaddr2 considers a cloned ip on lo as a cluster ip about resource-agents

[llaurent]

I've just been testing it. https://github.com/llaurent/resource-agents/compare/RA_323
It does resolve my original issue (as a consequence the ip is now removed from lo when the resource is stopped)

up to you guys :)

[dmuhamedagic]

@kskmori: Keisuke-san, can you please take a look at this. You were recently, and not so recently, into IPaddr2 :) Thanks!

[kskmori]

I'm not familiar with cluster IPs so I want opinions from the cluster IP users.

• Is it safe to assume that cluster IPs will never used on the loopback?
• Is it safe to assume that the valid use case of cloned IPaddr2 with no cluster IPs is only for the loopback?

If we can assume both, @llaurent 's patch can be merged but I'm not sure if this is correct.
Otherwise we might need to introduce another flag to switch those use cases.

BTW, in my use cases of LVS/DR, I always configure the backend IPs on lo statically via the system configuration (such as ifcfg-*), that is , no Pacemaker resources for them.