On Thu, 8 May 2014 09:58:41 +1000
Andrew Beekhof wrote:
> > node $id=131 vm01
> > node $id=132 vm02
> > (snip)
> >
> > Is the method of setting up ID of the node which has not
> > participated in a cluster using a corosync stack like this?
>
> I don;t know how crmsh works, sorry
$id= maps di
Hi All,
I composed Master/Slave resource of three nodes that set quorum-policy="freeze".
(I use Stateful in Master/Slave resource.)
-
Current DC: srv01 (3232238280) - partition with quorum
Version: 1.1.11-830af67
3 Nodes configured
9 Resources configured
Online:
For anyone submitting features, nothing changes.
However if you're submitting a fix for something you want fixed in 1.1.12, it
would be highly appreciated if they were against the 1.1 branch :-)
-- Andrew
signature.asc
Description: Message signed with OpenPGP using GPGMail
_
On 8 May 2014, at 12:38 am, K Mehta wrote:
> I created a multi state resource ms-2be6c088-a1fa-464a-b00d-f4bccb4f5af2
> (vha-2be6c088-a1fa-464a-b00d-f4bccb4f5af2).
>
> Here is the configuration:
> ==
> [root@vsanqa11 ~]# pcs config
> Cluster Name: vsanqa11_12
> Corosync
On 7 May 2014, at 7:53 pm, Yusuke Iida wrote:
> Hi, Andrew
>
> I would also like to describe the node which has not participated in a
> cluster to a crmsh file.
>
> I understood that uuid was required for a setup of a node as follows
> from this mail thread.
>
> # cat node.crm
> ### Cluster O
- Original Message -
> From: "Andrew Beekhof"
> To: "The Pacemaker cluster resource manager"
> Sent: Wednesday, May 7, 2014 1:31:27 AM
> Subject: [Pacemaker] Pacemaker 1.1.12 - Release Candidate 1
>
> As promised, this announcement brings the first release candidate for
> Pacemaker 1.1.1
I created a multi state resource ms-2be6c088-a1fa-464a-b00d-f4bccb4f5af2
(vha-2be6c088-a1fa-464a-b00d-f4bccb4f5af2).
Here is the configuration:
==
[root@vsanqa11 ~]# pcs config
Cluster Name: vsanqa11_12
Corosync Nodes:
Pacemaker Nodes:
vsanqa11 vsanqa12
Resources:
Maste
On 7 May 2014, at 8:31 pm, Greg Murphy wrote:
> Thanks Andrew, much appreciated.
>
> I’ll try upgrading to 1.11 and report back with how it goes.
At this point it may even be worth trying the .12 release candidate
>
>
>
> On 07/05/2014 01:20, "Andrew Beekhof" wrote:
>
>>
>> On 6 May 201
Thanks Andrew, much appreciated.
I’ll try upgrading to 1.11 and report back with how it goes.
On 07/05/2014 01:20, "Andrew Beekhof" wrote:
>
>On 6 May 2014, at 7:47 pm, Greg Murphy wrote:
>
>> Here you go - I’ve only run lrmd for 30 minutes since installing the
>>debug
>> package, but hopefu
Hi, Andrew
I would also like to describe the node which has not participated in a
cluster to a crmsh file.
I understood that uuid was required for a setup of a node as follows
from this mail thread.
# cat node.crm
### Cluster Option ###
property no-quorum-policy="ignore" \
stonith-enable
Am Mittwoch, 7. Mai 2014, 10:27:27 schrieb Wengatz Herbert:
> Hi there!
>
> I have the honour to introduce pacemaker on vmWare Clients at my company.
>
> I have already worked with several other cluster techniques (including Sun
> Cluster, Veritas, Fujitsu Primecluster, old Heartbeat, etc.) Thus
Hi there!
I just came across http://clusterlabs.org/quickstart.html
Maybe this will be enough. - Sorry for bothering!
Yours,
Herbert
Von: Wengatz Herbert
Gesendet: Mittwoch, 7. Mai 2014 10:27
An: 'pacemaker@oss.clusterlabs.org'
Betreff: [Pacemaker] Pacemaker with vmWare
Hi there!
I have the
Hi there!
I have the honour to introduce pacemaker on vmWare Clients at my company.
I have already worked with several other cluster techniques (including Sun
Cluster, Veritas, Fujitsu Primecluster, old Heartbeat, etc.)
Thus I'm looking for a sort of "5-Minute-Guide" into using Pacemaker on vmWa
13 matches
Mail list logo
