On Fri, Mar 27, 2009 at 15:18, Joe Bill wrote:
>
> --- On Tue, 3/24/09, foxyc...@yahoo.com wrote:
>
>> ... what command should I type to cause the cluster to
>> perform a "monitor" operation at a specific check level on
>> that resource, and return the appropriate OCF status of the
>> operation,
--- On Tue, 3/24/09, foxyc...@yahoo.com wrote:
> ... what command should I type to cause the cluster to
> perform a "monitor" operation at a specific check level on
> that resource, and return the appropriate OCF status of the
> operation, *without* the cluster reacting like triggering a
> failo
On Fri, Mar 27, 2009 at 13:54, Joe Bill wrote:
>
> --- On Fri, 3/27/09, Andrew Beekhof wrote:
>
I saw later that you want to prevent the cluster
from doing anything for the resource, simply set
is-managed=false for the resource in question.
>
>>> This is incorrect. I want the clust
--- On Fri, 3/27/09, Andrew Beekhof wrote:
>>> I saw later that you want to prevent the cluster
>>> from doing anything for the resource, simply set
>>> is-managed=false for the resource in question.
>> This is incorrect. I want the cluster to react to
>> everything BUT to this specific invoca
On Fri, Mar 27, 2009 at 10:30, Joe Bill wrote:
>
> --- On Thu, 3/26/09, Andrew Beekhof wrote:
>
>>> what command should I type to cause the cluster
>>> to perform a "monitor" operation at a specific check
>>> level on that resource, and return the appropriate
>>> OCF status of the operation,
--- On Thu, 3/26/09, Andrew Beekhof wrote:
>> what command should I type to cause the cluster
>> to perform a "monitor" operation at a specific check
>> level on that resource, and return the appropriate
>> OCF status of the operation, *without* the cluster
>> reacting like triggering a fai
On Tue, Mar 24, 2009 at 10:45, wrote:
>
> I've been wanting this for some time now and expecting pacemaker would
> include it in it's newer versions. But I've checked the latest pacemaker 1.0
> distribution fresh of the day, and unfortunately have found nothing in it
> indicating if this is po
Joe Bill wrote:
> Hi Dominik!
>
> dk at in-telegence wrote:
>>> I'd love to see something like:
>>>
>>> # crm_resource -m check_level resource_id
>>> ..
>> This should be possible:
>>
>> export OCF_ROOT=/usr/lib/ocf
>> export OCF_RESKEY_=
>> export OCF_RESKEY_=
>> $OCF_ROOT/resource.d// monitor
>>
Hi Dominik!
dk at in-telegence wrote:
>> I'd love to see something like:
>>
>> # crm_resource -m check_level resource_id
>> ..
>
>This should be possible:
>
>export OCF_ROOT=/usr/lib/ocf
>export OCF_RESKEY_=
>export OCF_RESKEY_=
>$OCF_ROOT/resource.d// monitor
>echo $?
Thanks, but I'm afraid y
>> I'd love to see something like:
>>
>> # crm_resource -m check_level resource_id
>> ..
I forgot to add that a -f option switch to cause the failover if the monitor
operation failed would be cool too.
___
Pacemaker mailing list
Pacemaker@o
foxyc...@yahoo.com wrote:
> I've been wanting this for some time now and expecting pacemaker would
> include it in it's newer versions. But I've checked the latest pacemaker 1.0
> distribution fresh of the day, and unfortunately have found nothing in it
> indicating if this is possible.
>
> - R
11 matches
Mail list logo
