Hi Andrew,
the emphasis lies on ' reasonably'... ;-)
I'll see whether someone can show hints.
Best regards
Andreas
-Ursprüngliche Nachricht-
Von: Andrew Beekhof [mailto:and...@beekhof.net]
Gesendet: Montag, 15. April 2013 05:49
An: The Pacemaker cluster resource manager
Betreff: Re:
Hi Andrew,
thank you for your answers (to all of my questions).
My problem is, I have both nodes down. Now I have to
start one node without the other. And I know that
the cluster is configured to stonith. How do I change
the meta attribute of the stonith device without
starting the one node and
On 15/04/2013, at 3:38 PM, Yuichi SEINO wrote:
> Hi,
>
> 2013/4/8 Andrew Beekhof :
>> I'm not 100% sure what the best approach is here.
>>
>> Traditionally this is done with resource agents (ie. ClusterMon or ping)
>> which update attrd.
>> We could potentially build it into attrd directly, b
Hi,
2013/4/8 Andrew Beekhof :
> I'm not 100% sure what the best approach is here.
>
> Traditionally this is done with resource agents (ie. ClusterMon or ping)
> which update attrd.
> We could potentially build it into attrd directly, but then we'd need to
> think about how to turn it on/off.
>
>
On 15/04/2013, at 1:01 AM, Daniel Bareiro wrote:
>
> Hi all!
>
> I'm testing Pacemaker+Corosync cluster with KVM virtual machines. When
> restarting a node, I got the following status:
>
> # crm status
>
> Last updated: Sun Apr 14 11:50:00 2013
> Last change: Sun Apr 14 11:49:54
On 12/04/2013, at 4:58 PM, Andreas Mock wrote:
> Hi all,
>
> another question rised up while reading documentation concerning
> 2-node-cluster under RHEL6.x with CMAN and pacemaker.
>
> a) In the quick start guide one of the things you set is
> CMAN_QUORUM_TIMEOUT=0 in /etc/sysconfig/cman to g
On 12/04/2013, at 5:45 PM, Rainer Brestan wrote:
> OK, and where is the difference between 1.1.8 and 1.1.7.
Prior to 1.1.8 the local node flushed its value immediately, which caused the
CIB to be updated too soon (compared to the other nodes).
Since the whole point of attrd is to try and have
On 12/04/2013, at 11:10 PM, Pavlos Parissis wrote:
> Hi
>
> I am doing a rolling upgrade of pacemaker from CentOS 6.3 to 6.4 and
> when 1st node is upgraded and gets 1.1.8 version it doesn't join the
> cluster and I ended up with 2 clusters.
>
> In the logs of node1 I see
> cluster-infrastruct
On 14/04/2013, at 5:52 PM, Andreas Mock wrote:
> Hi all,
>
> can someone tell me what the pcs equivalent to
> crm configure erase is?
>
> Is there a pcs cheat sheet showing the common tasks?
> Or a documentation?
"pcs help" should be reasonably informative, but I don't see anything equivale
On 12/04/2013, at 11:35 PM, Brian J. Murrell wrote:
> On 13-04-10 07:02 PM, Andrew Beekhof wrote:
>>
>> On 11/04/2013, at 6:33 AM, Brian J. Murrell
>> wrote:
>>>
>>> Does crm_resource suffer from this problem
>>
>> no
>
> Excellent.
>
> I was unable to find any comprehensive documentation
On 14/04/2013, at 6:47 PM, Andreas Mock wrote:
> Hi all,
>
> in a two node cluster (RHEL6.x, cman, pacemaker)
> when I startup the very first node,
> this node will try to fence the other node if it can't see it.
> This can be true in case of maintenance. How do I avoid
> this startup fencing
On 15/04/2013, at 7:31 AM, Pavlos Parissis wrote:
> On 12/04/2013 09:37 μμ, Pavlos Parissis wrote:
>> Hoi,
>>
>> As I wrote to another post[1] I failed to upgrade to 1.1.8 for a 2 node
>> cluster.
>>
>> Before the upgrade process both nodes are using CentOS 6.3, corosync
>> 1.4.1-7 and pacemak
On 12/04/2013 09:37 μμ, Pavlos Parissis wrote:
> Hoi,
>
> As I wrote to another post[1] I failed to upgrade to 1.1.8 for a 2 node
> cluster.
>
> Before the upgrade process both nodes are using CentOS 6.3, corosync
> 1.4.1-7 and pacemaker-1.1.7.
>
> I followed the rolling upgrade process, so I st
On 14/04/2013 10:47 πμ, Andreas Mock wrote:
> Hi all,
>
>
>
> in a two node cluster (RHEL6.x, cman, pacemaker)
>
> when I startup the very first node,
>
> this node will try to fence the other node if it can't see it.
>
> This can be true in case of maintenance. How do I avoid
>
> this star
Hi all!
I'm testing Pacemaker+Corosync cluster with KVM virtual machines. When
restarting a node, I got the following status:
# crm status
Last updated: Sun Apr 14 11:50:00 2013
Last change: Sun Apr 14 11:49:54 2013
Stack: openais
Current DC: daedalus - partition with quorum
Version
Thanks for the informations. I give it a try monday and gave you a feedback.
2013/4/12 Felix Zachlod :
> Hello Joseph!
>
>> -Ursprüngliche Nachricht-,
>> Von: Joseph-Andre Guaragna [mailto:joseph-an...@rdmo.com]
>> Gesendet: Freitag, 12. April 2013 17:19
>> An: pacemaker@oss.clusterlabs.
Hi all,
in a two node cluster (RHEL6.x, cman, pacemaker)
when I startup the very first node,
this node will try to fence the other node if it can't see it.
This can be true in case of maintenance. How do I avoid
this startup fencing temporarily when I know that the
other node is down?
Hi all,
can someone tell me what the pcs equivalent to
crm configure erase is?
Is there a pcs cheat sheet showing the common tasks?
Or a documentation?
Best regards
Andreas
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http:
18 matches
Mail list logo