On Mon, Dec 6, 2010 at 5:18 PM, Ryan Steele wrote:
> I think I've found the problem - comments below.
>
> On 12/05/2010 08:26 PM, Ryan Steele wrote:
>>
>> Hi folks,
>>
>
> <...snip...>
>
>> crm(live)configure# primitive ResourceMonitor ocf:pacemaker:ClusterMon
>> params pidfile="/var/run/crm_mon.p
Hello,
As I understand there is no constraints on cluster options, correct?
Resource FOO should be started only after B is started and event E
happened. Currently E is a node attribute set by some BAR resource on
all nodes, which looks ugly.
It seems that making E a cluster attribute/option and se
Hi there,
I have a requirement to make a single node cluster primarily for resource
monitoring on the local node so that network load balancing from my front end
load balancers works correctly and the node in question fails out due to either
my public or private interface or both interfaces fai
Perhaps this gives you some inspiration? (be careful with the exclamation
marks, non-japanese people tend to dislike shouting in ads or promo vids)
Systems administrators have been using Heartbeat for years as a reliable
zero-downtime solution. Now, Heartbeat has evolved to the next level of hi