>>> Dejan Muhamedagic <[email protected]> schrieb am 04.08.2011 um 18:32 in
>>> Nachricht
<[email protected]>:
> Hi,
>
> On Thu, Aug 04, 2011 at 05:45:16PM +0200, Ulrich Windl wrote:
> > Hi!
> >
> > Some RAs support OCF_CHECK_LEVEL (e.g. ocf:heartbeat:Raid1). However the
> OCF_CHECK_LEVEL is not advertised in the metadata. Also, OCF_CHECK_LEVEL is
> not a global parameter (wouldn't make much sense).
> >
> > So obviously using the crm_gui one can add OCF_CHECK_LEVEL for some
> resource, and that seems to work.
> >
> > So far, so good. Now I tried to add more resources without an
> OCF_CHECK_LEVEL using the crm command line. I added the new resources to a
> group that contained resources using OCF_CHECK_LEVEL.
>
> OCF_CHECK_LEVEL is to be defined on a per-monitor basis, like
> this:
>
> primitive ...
> op monitor OCF_CHECK_LEVEL=10 interval=...
[...]
So, is a configuration like the following incorrect?
primitive prm_c11_as_1_raid1 ocf:heartbeat:Raid1 \
params raidconf="/etc/mdadm/mdadm.conf" raiddev="/dev/md15"
OCF_CHECK_LEVEL="1" \
operations $id="prm_c11_as_1_raid1-operations" \
op start interval="0" timeout="20s" \
op stop interval="0" timeout="20s" \
op monitor interval="60" timeout="60s"
Ulrich
P.S. Moving the issue to the linux-ha list as requested.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
