On 2012-12-04T20:38:54, Fabian Herschel <[email protected]> wrote:
> I am not sure if that will really help you - but in my cluster (ok
> older pacemaker version) I ahve the following to define a master slave
> resource:
>
> primitive rsc_sap_HA0_ASCS00 ocf:heartbeat:SAPInstance \
> operations $id="rsc_sap_HA0_ASCS00-operations" \
> op monitor interval="11" role="Slave" timeout="60" \
> op monitor interval="13" role="Master" timeout="60" \
> params \
> InstanceName="HA0_ASCS00_sapha0as" \
> START_PROFILE="/usr/sap/HA0/SYS/profile/HA0_ASCS00_sapha0as" \
> ERS_InstanceName="HA0_ERS10_sapha0er"
> ERS_START_PROFILE="/usr/sap/HA0/SYS/profile/HA0_ERS10_sapha0er"
>
> ms msl_sap_enqrepl_HA0 rsc_sap_HA0_ASCS00 \
> meta clone-max="2" target-role="Started" master-max="1" \
> is-managed="true"
>
> So I have a defined operation role="Master" on the primitive but NOT a
> targe-role="Master" on the Master/Slave.
Specifying target-role="Master" is completely different from specifying
a role=Master/Slave on an operation.
The former defines that you want the cluster to promote the resource to
Master (setting it to "slave" would prevent the resource from reaching
master state, just like "stopped" would prevent it from being started at
all).
The latter defines that you want to run different monitor operations per
role.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
