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

[Vince Gabriel]

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?

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

 
 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100825/1e7ff75d/attachment.html>