[ClusterLabs] One cluster with two groups of nodes

Hi guys, nice to say hello here. I've been assigned with a very particular task: There's a pacemaker-based cluster with 6 nodes. A system runs on three nodes (group A), while the other three are hot-standby spares (group B). Resources from group A are never supposed to me relocated individually

Re: [ClusterLabs] Corosync OCFS2

Hello David, If you want to use OCFS2 with Pacemaker stack, you do not need ocfs2_controld in the new version. you do not need configure o2cb resource too. I can give you a crm demo in SLE12SP3 environment (actually there is not any change since SLE12SP1) crm(live/tb-node1)configure# show

[ClusterLabs] Corosync OCFS2

I'm trying to set up a 2 node cluster using OCFS2 with a Pacemaker and Corosync stack on Debian. I attempted to ocf:heartbeat:o2cb to satisfy the o2cb requirement of OCFS2, but found that the required daemon o2cb_controld.pcmk is not available for Debian because it was dependent on OpenAIS which

[ClusterLabs] Antw: monitor operation for ASTERISK on node_name: 7 (not running)

Hi! It may be worth the time to find out which command is used to monitor the status of asterisk. Then maybe run that command repeatedly in a shell loop to find out what it returns. I guess some thing is slow to respond; maybe jsut increase the timeout... Regards, Ulrich >>> Donat Zenichev

Re: [ClusterLabs] Hawk vs pcs Web UI

On Tue, 2017-11-07 at 10:30 -0600, David Kent wrote: > Hello, > > What is the difference between Hawk and the pcs Web UI? (Why are > there two projects, not one? Are they targeting different use cases?) > > I was surprised to see two Web UI implementations under the same > ClusterLabs umbrella.

[ClusterLabs] monitor operation for ASTERISK on node_name: 7 (not running)

Hi guys. I've just started to work with pacemaker and have a problem with monitored service. I've already configured three Active/Stand-by clusters with pacemaker. Running resources: IPaddr2 asterisk daemon bacula fd snmp daemon First and second cluster are working fine - I didn't notice any

Re: [ClusterLabs] boothd-site/boothd-arbitrator: WARN: packet timestamp older than previous one

Le mardi 07 novembre 2017 à 13:41 +0100, Dejan Muhamedagic a écrit : > Hi, > > On Mon, Nov 06, 2017 at 10:52:12AM +0100, Nicolas Huillard wrote: > > Hello, > > > > I have many of those above syslog messages from boothd (counting > > all servers, that's nearly 1 hundred per day). > > All sites