[Pacemaker] Help controlling target-role additions to the cib after a start or stop of a resource?

[Andrew Beekhof]

On Wed, Aug 25, 2010 at 5:49 PM, Vince Gabriel <vinceg at sgi.com> wrote:
> The primitive below is part of a group. If the resource (HA1-ip) is
> start/stop independently of its group, the target-role="Started" is added to
> the CIB. Is there a way to prevent that from happening?

No.

>
> primitive HA1-ip ocf:heartbeat:IPaddr2 \
>
>         operations $id="HA1-ip-operations" \
>
>         op monitor interval="60s" timeout="30s" on-fail="restart"
> start-delay="0" \
>
>         op start interval="0" timeout="90" on-fail="restart"
> requires="fencing" \
>
>         op stop interval="0" timeout="100" on-fail="fence" \
>
>         params ip="10.10.10.33" nic="eth0" cidr_netmask="24" \
>
>         meta resource-stickiness="1" migration-threshold="1"
> target-role="Started"
>
> Thanks,
>
> -Vince
>
> --
>
> Vince Gabriel
>
> Field Technical Analyst
>
> SGI
>
> office: 361.729.9151
>
> cell:  409.392.8083
>
>
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>