pcs versions 0.9.26 and 0.9.90
pacemaker versions 1.1.8 and 1.1.10
Which pcs versions are expected to work with which pacemaker versions ?
Regards,
Kiran
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
hello everyone
I have 4 resource agents A B C and D.
A B C should run on the same node, but D should mutex with any of A B C.
The following is my configure, is it correct?
crm configure collocation ABC INFINITY: A B C
crm configure collocation D-mutex-ABC -INFINITY: D (A B C)
please give my
What I understand from globally-unique=false is as follows
Agent handling the resource does exactly same processing on all nodes. For
processing this resource, agent on all nodes will use exactly same
resources (files, processes, same parameters to agent entry points, etc).
In case of my
I am sorry to get back to this topic, but I'm genuinely curious:
Why is demote an option for the ticket loss-policy for
multi-site-clusters but not for the normal no-quorum-policy of local
clusters? This seems like a missing feature to me.
Best regards
Christian
2014-04-07 9:54 GMT+02:00
Hello,
I am dealing with a three-node multi-site cluster using pacemaker and
corosync. The third node is a quorum-only node.
The three nodes form a single cluster and are connected using corosync over
the internet (using VPN tunnels). Of cource, using corosync over the
internet and using a third
Hi all
We are working on HA solutions for OpenStack(-related) services and figured
out that sometimes we need clones to be notified if one of the cluster
nodes running clone instances goes offline. E.g., we need this information
to make RabbitMQ AMQP broker cluster to forget this node until it
Hello Andrew and cluster folks!
In the last month we are experiencing some weird problem with cib process in
one of our nodes
('gandalf'), it's a 4-node cluster. Brief description:
After some undetermined reason (we still can't figure out why) it begins
looping infinitely and
consuming 100%
On 26 May 2014, at 5:15 pm, K Mehta kiranmehta1...@gmail.com wrote:
pcs versions 0.9.26 and 0.9.90
pacemaker versions 1.1.8 and 1.1.10
Which pcs versions are expected to work with which pacemaker versions ?
I think for the most part, all versions will work together.
There may be the odd
On 27 May 2014, at 5:48 am, Gabriel Gomiz ggo...@cooperativaobrera.coop wrote:
Hello Andrew and cluster folks!
In the last month we are experiencing some weird problem with cib process in
one of our nodes
('gandalf'), it's a 4-node cluster. Brief description:
After some undetermined
On 26 May 2014, at 9:56 pm, K Mehta kiranmehta1...@gmail.com wrote:
What I understand from globally-unique=false is as follows
Agent handling the resource does exactly same processing on all nodes. For
processing this resource, agent on all nodes will use exactly same resources
(files,
On 27 May 2014, at 1:16 am, Vladimir Kuklin vkuk...@mirantis.com wrote:
Hi all
We are working on HA solutions for OpenStack(-related) services and figured
out that sometimes we need clones to be notified if one of the cluster nodes
running clone instances goes offline. E.g., we need this
On 26 May 2014, at 10:47 pm, Christian Ciach derein...@gmail.com wrote:
I am sorry to get back to this topic, but I'm genuinely curious:
Why is demote an option for the ticket loss-policy for
multi-site-clusters but not for the normal no-quorum-policy of local
clusters? This seems like a
On 26 May 2014, at 4:56 pm, K Mehta kiranmehta1...@gmail.com wrote:
[root@vsanqa10 ~]# rpm -qa | grep pacemaker; rpm -qa | grep libqb; rpm -qa |
grep corosync; rpm -qa | grep cman; uname -a; cat /etc/redhat-release
pacemaker-libs-1.1.8-7.el6.x86_64
pacemaker-cluster-libs-1.1.8-7.el6.x86_64
Hi All,
The attrd_updater command ignores the dampen parameter and updates an
attribute.
Step1) Start one node.
[root@srv01 ~]# crm_mon -1 -Af
Last updated: Tue May 27 19:36:35 2014
Last change: Tue May 27 19:34:59 2014
Stack: corosync
Current DC: srv01 (3232238180) - partition WITHOUT quorum
So is globally-unique=false correct in my case ?
On Tue, May 27, 2014 at 5:30 AM, Andrew Beekhof and...@beekhof.net wrote:
On 26 May 2014, at 9:56 pm, K Mehta kiranmehta1...@gmail.com wrote:
What I understand from globally-unique=false is as follows
Agent handling the resource does
On 05/27/14 08:07, Andrew Beekhof wrote:
On 26 May 2014, at 10:47 pm, Christian Ciach derein...@gmail.com wrote:
I am sorry to get back to this topic, but I'm genuinely curious:
Why is demote an option for the ticket loss-policy for
multi-site-clusters but not for the normal
On 27 May 2014, at 2:37 pm, K Mehta kiranmehta1...@gmail.com wrote:
So is globally-unique=false correct in my case ?
yes
On Tue, May 27, 2014 at 5:30 AM, Andrew Beekhof and...@beekhof.net wrote:
On 26 May 2014, at 9:56 pm, K Mehta kiranmehta1...@gmail.com wrote:
What I understand
On 27 May 2014, at 3:12 pm, Gao,Yan y...@suse.com wrote:
On 05/27/14 08:07, Andrew Beekhof wrote:
On 26 May 2014, at 10:47 pm, Christian Ciach derein...@gmail.com wrote:
I am sorry to get back to this topic, but I'm genuinely curious:
Why is demote an option for the ticket loss-policy
No reason. Need to know which combination is expected to work.
using 0.9.26 with new 1.1.10 pacemaker
and 0.9.90 with old pacemaker has issues in resource deletion.
Below is the commands executed on 0.9.26 with 1.1.10 pacemaker
[root@vsanqa11 tmp]# rpm -qa | grep pcs; rpm -qa | grep pacemaker;
19 matches
Mail list logo
