[ClusterLabs] pacemaker and fence_sanlock

Dear all, I'm just beginning to use pacemaker+corosync as our HA solution on Linux, but I got stuck at the stage of configuring fencing. Pacemaker 1.1.15, Corosync Cluster Engine, version '2.3.5.46-d245', and sanlock 3.3.0 (built May 10 2016 05:13:12) I have the following questions: 1.

Re: [ClusterLabs] Antw: Re: bug in crm shell (SLES11 SP4)? required parameters not checked

On 2016-05-11T08:02:56, Ulrich Windl wrote: > > $ crm help Checks > > $ crm options help check-frequency > > $ crm options help check-mode > > > > If none of these settings match Ulrich's preferences, maybe he > > could pledge his case to introduce more. > >

[ClusterLabs] Antw: Resource clone groups - resource deletion

Hi! I think the solution is switching from sequential dependencies in groups to parallel dependencies, separating in ordering and colocation In crm shell it is displayed as "order any inf: first ( then1 then2 )" and "colocation any inf: ( then11 then2 ) first". Would this help? We had a

Re: [ClusterLabs] install software in centos5

On 11/05/16 02:31 AM, Liu, Mark wrote: > Hello all, > > I want to install the pacemaker & corosync in the Centos5.x > server,but can't find the repo.who can tell me how to do this?Thank you. That is a very ill-advised course of action. If you must use HA on CentOS 5, use cman +

[ClusterLabs] Resource clone groups - resource deletion

Hi, I am building up a service for doing ALUA based iSCSI targets using pacemaker for configuration management and failover of target groups. This is done using our own developed resource scripts. To keep the config clean I have organised resources into groups - as I create resources they