- Original Message -
> From: "Phil Frost"
> To: pacemaker@oss.clusterlabs.org
> Sent: Friday, June 15, 2012 7:28:37 AM
> Subject: Re: [Pacemaker] Confusing semantics of colocation sets
> (stopping resource stops others in colocation / order sets)
> On 06/14/2012 05:47 PM, Jake Smith wro
On 06/15/2012 11:55 AM, David Vossel wrote:
If resC is stopped
resource stop resC
then drbd_nfsexports is demoted, and resB and resC will stop. Why is
that? I'd expect that resC, being listed last in both the colocation
and
It is the order constraint.
Order constraints are symmetrical. I
- Original Message -
> From: "David Vossel"
> To: "The Pacemaker cluster resource manager"
> Sent: Friday, June 15, 2012 10:55:56 AM
> Subject: Re: [Pacemaker] stopping resource stops others in colocation /
> order sets
>
> - Original Message -
> > From: "Phil Frost"
>
- Original Message -
> From: "Phil Frost"
> To: pacemaker@oss.clusterlabs.org
> Sent: Thursday, June 14, 2012 1:19:05 PM
> Subject: [Pacemaker] stopping resource stops others in colocation / order
> sets
>
> I'm sure this is a typical novice question, but I've been dancing
> around
>
On 2012-06-15T14:13:59, "Stallmann, Andreas" wrote:
> Hi!
>
> I figure that many ocf agents use either “status” or “monitor” and sometimes
> both.
OCF only uses "monitor".
"status" is still around because many of the agents started out as LSB
init scripts, and many agents just have both. It's
Hi!
I figure that many ocf agents use either “status” or “monitor” and sometimes
both.
What does Pacemaker / crm expect?
Some examples:
- tomcat agent always returns OCF_SUCCESS on status: why ask, when you
always get the same answer
- tomcat agent returns OCF_NOT_RUNNING,
I...uh...don't really know what to say. Is that a bug, in that it is not
reasonable in any way? Or is it a feature, in that it can't be fixed in a
backwards compatible way?
Having literally just implemented some logic to handle these quirks today,
I would certainly hope that any changes to thi
On 06/14/2012 05:47 PM, Jake Smith wrote:
So it should be resC on top of resB on top of DRBD:master. I think of
collocation as being written in the reverse order of "order"
statement. That's why resources in groups start in the order they are
written and collocate in reverse from written order.
