Steven,
Are you planning on recording/taping it if I want to watch it later?
Thanks,
Bob
From: Steven Dake sd...@redhat.com
To: pcmk-cl...@oss.clusterlabs.org
Cc: aeolus-de...@lists.fedorahosted.org; Fedora Cloud SIG
cl...@lists.fedoraproject.org;
-order-fs-after-drbd2 inf: glance-repos-fs-group:stop
ms_drbd:demote ms_drbd:stop glance-repos:stop
I called out the stop of DRBD before the stop of LVM. The syslog attached
previously is for this configuration.
Thanks,
Bob
From: Bob Schatz bsch
glance-order-fs-after-drbd2 inf: glance-repos-fs-group:stop
ms_drbd:demote ms_drbd:stop glance-repos:stop
I called out the stop of DRBD before the stop of LVM. The syslog attached
previously is for this configuration.
Thanks,
Bob
From: Bob Schatz bsch
=1310768814
I will let everyone know how testing goes.
Thanks,
Bob
- Forwarded Message -
From: Bob Schatz bsch...@yahoo.com
To: pacemaker@oss.clusterlabs.org pacemaker@oss.clusterlabs.org
Sent: Wednesday, July 20, 2011 1:38 PM
Subject: [Pacemaker] Fw: Configuration for FS over DRBD over LVM
Hi,
I am trying to configure an FS running on top of DRBD on top of LVM or:
FS
|
DRBD
|
LVM
I am using Pacemaker 1.0.8, Ubuntu 10.04 and DRBD 8.3.7.
Reviewing all the manuals (Pacemaker Explained 1.0, DRBD 8.4 User Guide, etc) I
came up with this Pacemaker
Andrew,
Comments at end with BS
From: Andrew Beekhof and...@beekhof.net
To: Bob Schatz bsch...@yahoo.com
Cc: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Sent: Fri, April 15, 2011 4:28:52 AM
Subject: Re: [Pacemaker] Question regarding
Andrew,
Thanks for responding. Comments inline with Bob
From: Andrew Beekhof and...@beekhof.net
To: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Cc: Bob Schatz bsch...@yahoo.com
Sent: Tue, April 12, 2011 11:23:14 PM
Subject: Re
I am running Pacemaker 1.0.9 and Heartbeat 3.0.3.
I started a resource and the agent start method returned OCF_ERR_INSTALLED.
I have fixed the problem and I would like to restart the resource and I cannot
get it to restart.
Any ideas?
Thanks,
Bob
The failcounts are 0 as shown below and
/ha.d/resource.d/startstop when heartbeat starts)
2. This problem seemed to occur most frequently when I went from 4
master/slave
resources to 6 master/slave resources.
Thanks,
Bob
- Original Message
From: Bob Schatz bsch...@yahoo.com
To: The Pacemaker cluster resource manager pacemaker
:42 AM, Bob Schatz bsch...@yahoo.com wrote:
I am running Pacemaker 1.0.9.1 and Heartbeat 3.0.3.
I have a master/slave resource with an agent.
When the resource hangs while doing a promote, the resource returns
OCF_ERR_GENERIC.
However, all this does is call demote on the resource, restart
I am running Pacemaker 1.0.9.1 and Heartbeat 3.0.3.
I have a master/slave resource with an agent.
When the resource hangs while doing a promote, the resource returns
OCF_ERR_GENERIC.
However, all this does is call demote on the resource, restart the resource on
the same node and then retry
Florain,
Comments below with [BS]
Thanks,
Bob
- Original Message
From: Florian Haas florian.h...@linbit.com
To: pacemaker@oss.clusterlabs.org
Sent: Mon, December 6, 2010 7:25:28 AM
Subject: Re: [Pacemaker] OCF RA dev guide: final heads up
Hello Bob,
On 2010-12-03 20:12, Bob Schatz
Florian,
Thanks for writing this!
I already found one or two errors related to return codes in my agent based on
your document. :)
I have not read the entire document but I do have these comments:
1.Does this document apply to all versions of the agent framework or only
certain
pLunch this week?brbrbr/p
pSent from Yahoo! Mail on Android/p
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started:
I am using 1.0.9.1 of Pacemaker.
I have applied the fix for bug 2477 and it is not working for me.
I started with this: # crm_mon -n -1 Last updated: Mon Nov 8
09:49:07 2010 Stack: Heartbeat Current DC: mgraid-mkp9010repk-0
(f4e5e15c-d06b-4e37-89b9-4621af05128f) - partition
at 6:39 PM, Bob Schatz bsch...@yahoo.com wrote:
Yes it does.
Ok. Could you create a bugzilla for this please? I'll make sure it gets fixed.
Here is output from a different cluster which is at the same 1.0.9.1 Pacemaker
version.
# crm_mon -n -1
Last updated: Wed Aug 25 09:35:51
, Aug 24, 2010 at 12:37 AM, Bob Schatz bsch...@yahoo.com wrote:
I would like to find the master node for a resource.
On 1.0.9.1, when I do:
# crm resource status ms-SSWD-WCAW30019072
resource ms-SSWD-WCAW30019072 is running on: box-0
resource ms-SSWD-WCAW30019072 is running on: box
I would like to find the master node for a resource.
On 1.0.9.1, when I do:
# crm resource status ms-SSWD-WCAW30019072
resource ms-SSWD-WCAW30019072 is running on: box-0
resource ms-SSWD-WCAW30019072 is running on: box-1
This does not tell me if it is master or slave.
I found
and -INFINITY master score
Hi,
On Thu, Aug 12, 2010 at 12:54:10PM -0700, Bob Schatz wrote:
I upgraded to Pacemaker 1.0.8 since my application consists of Master/Slave
resources and I wanted to pick up the fix for setting negative master scores.
Why not to 1.0.9.1?
[BS] Because when I checked
On 1.0.6 and 1.0.8 I use to do this to create a primitive:
crm configure primitive SS1 ocf:omneon:ss params ss_resource=SS1 \
ssconf=${CONFIG_FILE} op monitor interval=3s role=Master \
timeout=7s op monitor interval=10s role=Slave timeout=7 \
op stop timeout=100 op
: match_graph_event:
Action SSJ5AMGG90106M6T:0_post_notify_promote_0 (45) confirmed on mgraid-mgg
90106m6t-1 (rc=0)
Thanks,
Bob
- Original Message
From: Bob Schatz bsch...@yahoo.com
To: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Sent: Fri, August 13
I upgraded to Pacemaker 1.0.8 since my application consists of Master/Slave
resources and I wanted to pick up the fix for setting negative master scores.
I am now able to set negative master scores when a resources starts and is
SLAVE
but can't be promoted. (The reason I want this is the
22 matches
Mail list logo
