On 2013-05-13 11:54, Michael Schwartzkopff wrote:
> Hi,
>
>
>
> I experienced a strange phenomena when setting up DRBD 8.4.2 with
> pacemaker 1.1.9.
>
>
>
> I can set up a dual primary DRBD manually without any problems. Now shut
> down one node, i.e. I demote the DRBD and the shut is "down
- Original Message -
> From: "Lindsay Todd"
> To: "The Pacemaker cluster resource manager"
> Sent: Monday, May 13, 2013 4:35:47 PM
> Subject: Re: [Pacemaker] Migrating VMs that depend on other VMs
>
> The "whitebox container implementation", is that the ability to manage
> resources
The "whitebox container implementation", is that the ability to manage
resources inside the VMs from the same ha-cluster that is managing the VM
instances, i.e., the pacemaker-remote agent? I've not tried that; so far
I've stuck to the stock SL6.4 RPMs... But that could help help some --
dependen
On 2013-05-10T02:18:36, John McCabe wrote:
> I ended up getting sbd up and running as an interim solution - but I'd
> really like to be able to stick with a fencing agent thats got a future in
> RHEL where possible. Is the expectation/intention that all fencing agents
> be compatible with pacemak
- Original Message -
> From: "Vladislav Bogdanov"
> To: pacemaker@oss.clusterlabs.org
> Sent: Monday, May 13, 2013 2:19:07 PM
> Subject: Re: [Pacemaker] Migrating VMs that depend on other VMs
>
> 13.05.2013 19:28, Lindsay Todd wrote:
> > Folks: On my cluster built on SL6.4, I need to
13.05.2013 19:28, Lindsay Todd wrote:
> Folks: On my cluster built on SL6.4, I need to deploy some VMs that
> depend on other VMs:
>
> * db0 has no dependendencies
> * ldap01,ldap02 require db0 to be running -- ordering constraint, but
> no collocation (other than we'll use a collocation c
Seems that it requires now the lifetime
crm node standby node1 forever
The error message is just nonsense.
Rainer
Gesendet: Montag, 13. Mai 2013 um 13:53 Uhr
Von: "Michael Schwartzkopff"
An: pacemaker@oss.clusterlabs.org
Betreff: [Pacemaker] crm subshell 1.2.4 incompatible to pacemaker 1
Folks: On my cluster built on SL6.4, I need to deploy some VMs that depend
on other VMs:
- db0 has no dependendencies
- ldap01,ldap02 require db0 to be running -- ordering constraint, but no
collocation (other than we'll use a collocation constraint to recommend
ldap01, ldap02 run on d
Le 09/05/2013 16:40, Steven Bambling a écrit :
I'm having some issues with getting some cluster monitoring setup and
configured on a 3 node multi-state cluster. I'm using Florian's blog
as an example
http://floriancrouzat.net/2013/01/monitor-a-pacemaker-cluster-with-ocfpacemakerclustermon-ando
On 05/13/2013 10:03 AM, Diego Remolina wrote:
Hi,
I was wondering if anybody can tell me what is the best way to replicate
the following crm commands in pcs. It seems pcs cannot do any
collocation rules using groups (or I just do not know how to properly do
it). I was also not able to figure out
Hi,
I was wondering if anybody can tell me what is the best way to replicate
the following crm commands in pcs. It seems pcs cannot do any
collocation rules using groups (or I just do not know how to properly do
it). I was also not able to figure out how to colocate a drbd resource
on the con
Hi,
crm tells me it is version 1.2.4
pacemaker tell me it is verison 1.1.9
So it should work since incompatibilities are resolved in crm higher that
version 1.2.1. Anywas crm tells me nonsense:
# crm
crm(live)# node
crm(live)node# standby node1
ERROR: bad lifetime: node1
Any ideas?
--
Dr. Mi
Hi,
I experienced a strange phenomena when setting up DRBD 8.4.2 with pacemaker
1.1.9.
I can set up a dual primary DRBD manually without any problems. Now shut down
one node, i.e. I demote the DRBD and the shut is "down".
When I start the cluster on the first node everything if fine. The CRM d
Hello,
On May 10, 2013, at 4:02 , Dalho PARK wrote:
> Hello,
> I’m trying to compile pacemaker on SmartOS and having error during make.
> Does anyone has already successfully compiled on SmartOS?
Sorta.
I spent some time making pkgsrc ports for libqb (0.14.4), corosync (2.3.0),
pacemaker (1.
14 matches
Mail list logo