in the old versions, if simplely writing location constraints like:
one of the
Webserver(a master/slave resource) instantce will be promoted.but in the latest
version 1.1.5, it seems not work, both instances are in slave and never change
its state.who can tell me what to do?thank you
>> Hi, friends, I have a problem with Pacemaker 1.1.5.
>>
>> When I configure a master resource as usual, and set target-role=“Master”,
>> but all instances are in slave state, no instance is promoted to master
>> state.
>>
>> Who can tell me how to promote a instance to master?
>have your RA cal
Hi all I intend to use wwid as resource name which is 32bit, so are there any
limitations of resource name? 32bit is ok?___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http:
HI all
___
Pacemaker mailing list: Pacemaker@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://develo
Hi all.
I've got a task to remove some nodes from cluster to save some power and
found that it is not sufficient to follow
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-node-delete.html#s-del-ais
After pacemaker is then restarted on any another remaining node, remo
Hi,
29.05.2011 22:38, Digimer wrote:
> Hi all,
>
> I'd like to adapt my Node Assassin[1] device to support Pacemaker.
> Currently it supports RHCS and the agent is built to the
> FenceAgentAPI[2]. I'm hoping it can be fairly easily adapted to
> Pacemaker's specs.
Pacemaker has native support f
Hi all,
I'd like to adapt my Node Assassin[1] device to support Pacemaker.
Currently it supports RHCS and the agent is built to the
FenceAgentAPI[2]. I'm hoping it can be fairly easily adapted to
Pacemaker's specs.
Could someone point me to a guide or doc Pacemaker's STONITH API (if
the
