Hi everybody
I'm trying to build a cluster with pacemaker, corosync, DRBD and KVM on
Debian Squeeze.
If I just use DRBD and KVM with the ocf:linbit:drbd and
ocf:heartbeat:VirtualDomain Agents
everything works quite well including live migration and Node standby.
STONITH is not configured
yet
On 2011-02-18 09:24, Stefan Schneebeli wrote:
Hi everybody
I'm trying to build a cluster with pacemaker, corosync, DRBD and KVM on
Debian Squeeze.
If I just use DRBD and KVM with the ocf:linbit:drbd and
ocf:heartbeat:VirtualDomain Agents
everything works quite well including live migration
Hi Florian
Thank you for you fast reply!
But I don't get the point why it changes to this behavior. What is the
difference
to migrate a VM alone and together with an IP Address?
Regards,
Stefan
On 18.02.2011 09:35, Florian Haas wrote:
On 2011-02-18 09:24, Stefan Schneebeli wrote:
Hi
Hi Andrew,
Thank you for comment.
If you need detailed information, give me communication.
Should be enough in the bug, i'll follow up there
All right.
Thanks!
Hideo Yamauchi.
--- On Tue, 2011/2/15, Andrew Beekhof and...@beekhof.net wrote:
On Tue, Feb 15, 2011 at 3:01 PM,
hi guys
while doing some testing on my cluster and restarting my web resource i came
across an issue where the resource would eventually not start after multiple
stops and starts through crm
if i want to stop and start my resource should i stop the group and not the
individual resource if its in
Does this include the BladeCenter serial number?
Will
-Original Message-
From: pacemaker-requ...@oss.clusterlabs.org
[mailto:pacemaker-requ...@oss.clusterlabs.org]
Sent: Thursday, February 17, 2011 10:52 AM
To: pacemaker@oss.clusterlabs.org
Subject: Pacemaker Digest, Vol 39, Issue 53
Hello *,
I have an interesting problem at a customer installation site:
1. The failover on node failure (unplugging the power cords) takes about 20s.
2. The failover on network outage (unplugging the network cable of the active
node) takes about 40s.
The setup is as follows:
heartbeat 3.0.3
Hi,
On Fri, Feb 18, 2011 at 12:43:19PM +, paul harford wrote:
hi guys
while doing some testing on my cluster and restarting my web resource i came
across an issue where the resource would eventually not start after multiple
stops and starts through crm
Won't start why? Because of an
Hi,
On Fri, Feb 18, 2011 at 02:45:13PM +0100, Frederik Schüler wrote:
Hello *,
I have an interesting problem at a customer installation site:
1. The failover on node failure (unplugging the power cords) takes about 20s.
2. The failover on network outage (unplugging the network cable of
I am attempting to write my own resource agent to support postgres WAL log
shipping. My PostgreSQL primitive is currently stuck in a FAILED state due
to a bug in the resource agent script that I have fixed, but I don'
___
Pacemaker mailing list:
[Sorry for the partial message I sent earlier. Here's the full one.]
I am attempting to write my own resource agent to support postgres WAL log
shipping. My PostgreSQL primitive is currently stuck in a FAILED state due
to a bug in the resource agent script that I have fixed, and I can't figure
I added a primitive to my cluster without setting a timeout:
root@trustcentric2:~# crm configure primitive PostgreSQL
ocf:trustcentric:postgresql
WARNING: PostgreSQL: default timeout 20s for start is smaller than the
advised 120
WARNING: PostgreSQL: default timeout 20s for stop is smaller than
On Fri, Feb 18, 2011 at 11:17 AM, Jody McIntyre jo...@trustcentric.com wrote:
I added a primitive to my cluster without setting a timeout:
root@trustcentric2:~# crm configure primitive PostgreSQL
ocf:trustcentric:postgresql
WARNING: PostgreSQL: default timeout 20s for start is smaller than
On Fri, Feb 18, 2011 at 11:29 AM, Vadym Chepkov vchep...@gmail.com wrote:
crm configure property default-action-timeout=120s
Will that set the default for all primitives? I just want to change
PostgreSQL.
Alternately I could change the default but then I'd want to change ClusterIP
to be
Hi,
On Fri, Feb 18, 2011 at 10:59:52AM -0500, Jody McIntyre wrote:
[Sorry for the partial message I sent earlier. Here's the full one.]
I am attempting to write my own resource agent to support postgres WAL log
shipping.
Did you consider improving the existing resource agent? We do
accept
This will change the global timeouts. If you just want to change the
settings for one resource, type crm configure edit to edit your
configuration directly (and even without xml :-). Search your resource
and add the appropriate intervals- like this:
primitive PostgreSQL [...] \
op start
On Fri, Feb 18, 2011 at 11:41 AM, Dejan Muhamedagic deja...@fastmail.fmwrote:
I am attempting to write my own resource agent to support postgres WAL
log
shipping.
Did you consider improving the existing resource agent? We do
accept contributions. But we also dislike duplicating effort and
On Fri, Feb 18, 2011 at 11:43 AM, Uwe Ritzschke
uwe.ritzschk...@cms.hu-berlin.de wrote:
This will change the global timeouts. If you just want to change the
settings for one resource, type crm configure edit to edit your
configuration directly (and even without xml :-). Search your resource
correct me if I'm wrong, but this seem to me simply active-passive. You
define a resource for each IP address and stick it with higher
preference to each individual node, with a lower score to the other
node. When one node goes down, it takes the other IP.
quite simple actually.
On 02/18/11
19 matches
Mail list logo
